Quantcast
Channel: SCN : All Content - All Communities
Viewing all articles
Browse latest Browse all 3363

SAP Mobile platform landscape

$
0
0

Hello,

 

I need some information about the typical system landscape to deploy for an on premise environment.

I'm used to the "old fashioned" SAP business suite applications where we provide some "DEV / QA / PRD" landscape in order to support the development , customizing and technical maintenance strategies.

 

So far, I understand that the mobile platform relies on several systems, divided in several components & servers,  depending on the mobile scenario to set up in an enterprise.

Mine is rather common I think, and will be based on SAP Mobile 3.0. platform + Afaria + Fiori & gateway.

 

Now my question is : does it make sense to have a kind of "DEV / QAS / PRD" system landscape for these softwares ?

I mean will I have to set up this "SAP Mobile 3.0. platform + Afaria + Fiori & gateway" 3 times for each DEV / QA and PRD ?

I can see an advantage to this on an adminstration perspective, should I need to update / upgrade the software, but it seems a little luxurious to have so much systems only for this purpose.

Does it make sense for application development ? Ie, whenever someone develops an application, does it go from DEV to QAS and PRD like in an "STMS like"  way ?


My last question is, is there a need for system copies in these environments ?

If so , are there any documentation around this ?


So far, the conclusion to which I come, from my admin perspective is I'd like to set up some DEV/PRD fashion landscape mainly for my "admin" maintenance strategy. Should I need to apply patches on any of thses components, I do it on my DEVs landscape befor pushing it in prod.


I thank you for the answers you could provide and documentation you could point me to .


Best regards,

Steve.



Viewing all articles
Browse latest Browse all 3363

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>