Best Practice: SMP 3.0 / Agentry – Updating Cockpit, Deployment, Patching, Backup and Reversion
All Agentry users,
SAP and the Digital Business Service team proactively tries to share our learned lessons to the community to better assist the mobility users. In the route to a successful Agentry SMP 3.0 mobility deployment, we would like to share what is expected so that your team would know the best practice.
If the best practice steps are not followed here are the following symptoms that you may experience:
- Patching of fixes (ex: Work Manager or Inventory Manager) may not show up properly
- You will have a hard time reverting to a known good state (if backup or version control is not followed)
- Escalation by the customer to SAP may be seen but the root cause is tied to improper deployment by the customer/user
- There is a chance that you may be missing changes (deployment) or items may be not stored/saved properly in the SMP 3.0 cockpit
To prevent issues to occur, please follow the best practice deployment strategy as documented here:
SAP KBA # 2330407 – Deploying, Backing Up, Patching, Reversion and updating the SMP 3.0 cockpit for Agentry – Best Practice
We hope that by sharing this to the community, we can grow our mobility deployment faster and more efficient.
Thanks to all the SAP mobility users, designers and support for contributing our learned knowledge in the SAP Community Network (SCN).
SAP Platinum Support Engineer