Upgrade Creation: Production
System 
Purpose
This process describes the creation of upgrades for mobile clients in the production system.
Process Flow
...
1. The MAR Update program imports the application changes made by SAP. This results in the update of the Mobile Application Repository(MAR). If you have made changes to SAP objects, the update may result in collisions. Do not resolve these collisions now.
2. Development workstations and the repository server (containing the MAR and Transport Services) are upgraded with the latest binaries. When you upgrade the development workstations, additional elements like the Sales Pricing Engine that needs to be sent to the mobile clients as a part of the upgrade is installed.
3. Change lists that were released in the Development system, are imported into the MAR of the Production System. This is manually triggered using the Transport Agent.
4. Baselines of the MARs in the Test and Production systems are compared using the Baseline Comparison tool. The two MARs should be identical.
5. Bring down the CRM Server by holding all the queues. This requires you to do the following:
a. 'Deregister' all the queues on the server (Inbound, Outbound, R/3, ASCII Adapter and so on).
b. Ensure all the Replication and Realignment queues complete processing (there are 5 queues). After these queues show 0 (Zero) entries. You need to put these entries on hold too (by deregistration).
6. Import the Change Request, containing the BDoc / Table changes, from the CRM Server of the Test system to the CRM Server of the Production system. The CRM Middleware Support Package Manager is used for this process.
7. BDoc and Table index meta data is generated. This is done using the Client Console (Table Script Generator). This is based on a list of Tables and BDocs that were modified on the CRM Server due to the application of the upgrade/support package to the CRM Server.
8. A new application is generated using MAS. The generated application is tested in the Production system. In order to complete the test, the application database – IDES, needs to be updated with the information and TPS .net file generated by the Table Script Generator (described earlier). If the test is unsuccessful, the code must be corrected in the Development or Test system. Once again, the changes must be transported to the Production system and tested again.
9. The Upgrade is tested using the Mobile Upgrade Deployer. This requires you to:
a. Select the required upgrade units (supplied by SAP, or created by you) in the Upgrade Console Wizard and create a package (this puts the upgrade packages into the file system in the selected folder).
b. Deploy this package to upgrade the test client. This is done on the Test mobile client. Test the application after the deployment. Alternatively, you can send the upgrade to the Test mobile client connected to the CRM Server in the test system.
10. The upgrade is sent to mobile clients in the Production system. This requires you to do the following:
a. Login to the MAR in the Production system.
b. Using the same upgrade units which were used for the successful test, send the upgrade via the CRM Server using the Mobile Upgrade Console. This will result in the upgrade being sent to the CRM Server in the Production system and eventually the mobile clients will also receive the upgrade.
After this step, the first entries in all the outbound queues on the CRM Server will contain the upgraded BDocs.
11. Bring the CRM Server again to a productive status (by opening all the queues that were put on hold).
See also: