cancel
Showing results for 
Search instead for 
Did you mean: 

Any backup strategy or guidelines for SAP Mobility apps

Former Member
0 Kudos

Hi Team,

We are currently in the process of helping a Client define and implement backup strategies for the SAP Mobility apps currently running here.

Hence, wanted to know if there is standard SAP documentation or guide to follow which deals with a proper backup strategy (e.g. strategy for source code backup, backup of working apps in development and production, backup of SUP 2.3 and SMP 3.0 etc. so  that we can revert back to the last version of the working app incase needed) for SAP Mobility apps like SAPUI5, Agentry/Syclo (e.g. SAP Work Manager 6.0...), Fiori apps, SAP Afaria and so on.

We found the below link for SUP backup. Similarly, are there any other documents for Agentry/Syclo apps, Afaria, SMP 3.0 and so on...
http://scn.sap.com/people/stephen.dick/blog/2012/12/04/sup-backup-and-restore-process

Any inputs on this front would be highly appreciated.

Regards,
Aaron D'C

Accepted Solutions (1)

Accepted Solutions (1)

Jitendra_Kansal
Product and Topic Expert
Product and Topic Expert
0 Kudos

IMO its up to you how you want to go with it. Well,

for source code, you may have a GIT repository (or some shared repository stuff) and can maintain it version wise. like 0.1, 0.2 ,....so on . There also you can see which version was uploaded (to repository)on which date..

For applications on-boarded to SMP (Admin cockpit), again it totally depends. What we have been doing (in general), before on-boarding, we ask project team to share all required info like app id name, type (hybrid/native/agentry), backend, push notification etc in an excel sheet format and .ini file (for offline) if required.

We dont bother much for DEV system, but for QA and PROD we are strictly following this approach.

Along with that, we have also taken sort of screenshot of the SETTINGS done in Admin cockpit.

SYSTEM, security profile, SAML, Database, JVM,CONNECTORS etc. You can also EXPORT apps from Admin cockpit locally.

For Integration gateway project, anyway it will be there in Eclipse workspace repository. so it is always backed up.

Lets wait to hear other's views.

Regards,

JK

Answers (4)

Answers (4)

Jitendra_Kansal
Product and Topic Expert
Product and Topic Expert
0 Kudos

For SMP security profiles,

For every security profile, there are two related xml files e.g. admin.xml and admin-role-mapping.xml

Lets say you have created a new 'test' security profile in SMP, this is what happens in the background:

test1.xml.0 is a initial template file that gets created when the profile is first created. It is immediately updated with the configuration specified. If you were to update the profile subsequently, you will see that a backup of the profile content is created as test1.xml.1 etc before it is updated. This is done so that the administrator can revert to a previous version if needed. When the profile is deleted all these backup files are left untouched (i.e., not deleted) and only the test1.xml and test1-role-mapping.xml are deleted. This is again to facilitate the recovery of the profile if it were deleted accidentally.


Regards,

JK


PS: I had asked SAP about .xml.0 file and this is what they responded with. worth sharing.

Former Member
0 Kudos

Thanks Jitendra,

Quite informative.

And I presume that for Fiori apps (standard/custom apps), the backup of ECC (already been taken here) alone should suffice...correct?

Regards,

Aaron D'C

Former Member
0 Kudos

Thanks All,

This list is quite exhaustive and covers most of my queries..

A few of the steps mentioned for SMP 3.0 like export the app locally and the re-import it at a later stage (whenever needed) are already being followed by us.

Just a quick question,

Whats the back-up strategy for Agentry standard/customized apps?

Say if you have a Work Manager 6.0 and SUP 2.3. Do we take the backup of the SUP 2.3 and eClipse project separately or just taking the backup in SUP 2.3 should suffice?

OR is there any other way to take backups for Agentry apps - standard/customized?

Regards,
Aaron D'C

Jitendra_Kansal
Product and Topic Expert
Product and Topic Expert
0 Kudos

Whats the back-up strategy for Agentry standard/customized apps?

Say if you have a Work Manager 6.0 and SUP 2.3. Do we take the backup of the SUP 2.3 and eClipse project separately or just taking the backup in SUP 2.3 should suffice?

OR is there any other way to take backups for Agentry apps - standard/customized?

Looping Agentry experts

Regards,

JK

mark_pe
Active Contributor
0 Kudos

Aaron,

For Agentry and custom apps, the backup strategy is to have a golden zip created that contains all the needed information for your mobile app. In essence, all the required files that can be used in SMP 2.3 during deployment or publishing should be created.

So normally you may have a different zip file for QA, Prod and Dev but it has to be within the zip files.

So if something goes wrong with SMP 2.3, you can easily redeploy the custom/Agentry apps that is contained in the zip file in the SAP Control Center (SCC).

The step above is in addition to what you normally do for backing up your servers. Some customers just back up to a specific date and can revert based on that date.

The backup that I am talking about is freezing the application zip file that contains everything that can make the app working from scratch by just redeploying the Agentry app in the SCC.

Hope this helps.

Regards,

Mark Pe
SAP Platinum Support Engineer

Former Member
0 Kudos

Thanks Mark,

That clears most of the confusion over Agentry apps. Creating the golden application.zip (containing the entire agentry project including the source code) and then using it to re-deploy the entire agentry app via SCC seems like the most viable option and effective option here.

Just a quick question here...
Say if I want to import the golden application.zip (e.g. Agentry WM 6.0 project) from SCC 2.3 to SMP 3.0, would it ease the migration effort of Agentry apps to SMP 3.0 and can be easily done.

This should work right considering the fact that the golden application.zip from SCC 2.3 is a container that contains the entire Agentry project,

-Regards,
Aaron D'C

mark_pe
Active Contributor
0 Kudos

Aaron,

There are Java files that are not compatible between 2.3 versus 3.0. So you need to create an equivalent 3.0 golden zip file with the compatible files  (ini, Java and others).

Regards,

Mark Pe

SAP Platinum Engineer

Former Member
0 Kudos

Hi Mark,

Thanks!

So that means directly migrating from SCC 2.3 to SMP 3.0 even with the golden application.zip of SCC 2.3 would be difficult.

Then the only option left with us would be to reinstall all the Agentry apps (e.g. Work Manager 6.0) freshly on SMP 3.0 (i.e. by
1.) creating the Application ID in SMP 3.0, 2) importing the Agentry.ini file in eClipse and 3) finally publishing the same) rather than using the existing golden application.zip of SCC 2.3.

Am I correct?

Regards,

Aaron D'Cunha

mark_pe
Active Contributor
0 Kudos

Aaron,

Hi. There are some Java that you also need to use that replaces your server.class with the SMP 3.0 compatible one.

There are some documents on upgrades available in SCN.

Example:


Regards,
Mark Pe
SAP Platinum Support Engineer

Agentry PDF file on upgrade. This should be somewhere in the first link above. Just in case you cannot find it,this version is the final draft prior to going live. There may be some mods to it since it was written.

https://mdocs.sap.com/mcm/public/v1/open?shr=bhGDc37d3lOqaWJkVWu-d1uQOeVSPvu4TRJC1Td55Hw

bill_froelich
Product and Topic Expert
Product and Topic Expert
0 Kudos

Aaron,

In addition to the Java changes needed to operate under SMP3, for Agentry apps moving to SMP3 there is a change in the client communication protocol that from ANGEL to Websockets over HTTPS.  This necessitates you importing your current golden app into the SMP3 Agentry Editor and re-publishing out as a new golden copy to deploy to the SMP3 server.

Generally speaking for major version updates you should import and republish your definitions.

--Bill

Former Member
0 Kudos

Thanks Mark/Bill.

-Regards,
Aaron D'C

former_member190800
Contributor
0 Kudos

has good points.  An additional comment on the source code:  when possible, it is recommended to use dependency management systems (Cocoapods, Maven) to integrate the SAP SDK libraries into you mobile application projects.  This significantly simplifies the upgrade process for utilizing new service packs, which tend to come every few months with fixes and updates.

Former Member
0 Kudos