Upgrade Environment Setup 

Purpose

This process describes how you can set up the environment for sending upgrades to mobile clients via the CRM Server. 

Process Flow

       1.      The transport landscape is setup. You must do the following:

                            a.      Install Transport services using the Transport Configurator.

                            b.      Enter the ID of the repository in the CRM Server table WBTRREP.

                            c.      Test the connection to the CRM Server.

For more information about steps on testing the connection, refer to Appendix D of the Installation, Upgrade and Deployment Guide - Mobile Repository Server Configuration. (CRMMobileClientInstallationGuide.PDF). This document can be downloaded from the documentation folder of the Mobile Client installation CD.

       2.      All mobile clients must be subscribed to Workbench publications. This includes:

                            a.      Workbench Language Independent

                            b.      Workbench Language Dependent

Mobile clients must be connected to the CRM Server using the R/3 field value (MANDT), as the Transport Agent. Flow definitions are generated on the CRM Server in the context of the client value, for the following upgrade related BDocs:

...

                            a.      WB_BLOB_LD_WRITE

                            b.      WB_BLOB_LI_WRITE

                            c.      WB_CL_WRITE

                            d.      SERV_TRANS_WB

       3.      Recent patches must be applied. For more information, refer to the Collection Note 624842 for the Mobile Upgrade Console 4.0.

       4.      The enitre loop is tested by sending a sample upgrade (containing a single file) to a mobile client via the CRM Server.

       5.      An application upgrade is sent containing application changes. You do this by using the standard upgrade units shipped by SAP and deploy this on a test mobile client. The upgrade units relevant to the application upgrade are:

                            a.      UI Changes

Deploys the  changes made to the User Interface Layer of the application. Includes files generated by the SAP Mobile Application Studio.

                            b.      BOL Changes

Deploys the  changes made to the Business Object Layer and the messages of the application. Includes files generated by the SAP Mobile Application Studio.

                            c.      BDoc changes

Deploys changes made to the BDocs of the application. This includes the TPS.net file generated by the Client Console.

                            d.      Table Index Changes

Deploys changes made to the Table structure of the application. This includes the TableIndexScripts.txt file file generated by the Client Console.

       6.      The upgrade is tested before it is sent to Productive mobile clients. For more information, see Creation of Upgrades in the System Landscape.