Parameter

Optional / Mandatory

Description

StartupOption

Mandatory

Indicates the startup option in which the Rollout Manager must be executed. You can specify one of the following values:

·        /Replacement

Executes the application in the replacement mode

·        /Rollout

Executes the application in the rollout mode

·        /LPTRestoresite

Executes the application from the restoration of the application database from the stationary site till ConnTrans is invoked (Step 4) for all the mobile client rollout sites. For more information, see Intermediate Step Execution of the Mobile Client Rollout Manager.

·        /LPTAssignsite

Executes the application from the assignment of site till ConnTrans is invoked (Step 4) for all the mobile client rollout sites. For more information, see Intermediate Step Execution of the Mobile Client Rollout Manager.

·        /LPTConnTrans

Invokes ConnTrans on all the replacement laptops for the mobile client sites that are already assigned.

This parameter is applicable only for the mobile client sites that are already assigned. Therefore, you cannot specify this parameter for the rollout sites.

MW

Mandatory

The Middleware parameters that must be provided to connect to the CRM server.

F

Mandatory

The site name and the machine name of the laptop that is being used to start the Rollout Manager. This information must be stored in a .txt file and the name of this file is given as a parameter when starting the command line option.

Within the .txt file, the semicolon must be used as a separator between the site name and the machine name.

Each line in the text file would correspond to a particular rollout/replacement site information.

I

Optional

Specifies the file to which messages are to be logged. If not provided then the default application log settings are used. The default application log can be found at <NT Username>\temp\Rolloutlog.txt

NoConnTrans

Optional

Specifying this parameter will not start ConnTrans by default on all laptops.

DecentralizedLog

Optional

Creates individual log files for each rollout site in addition to the centralized log file. In such a case, the centralized log file contains information related to the stationary site only. The site specific information is logged to the individual log files. This allows the administrator to monitor individual sites and perform the required action (if any).The individual site specific log files are stored in the same location where the centralized log file is stored. The naming convention of the site specific log files is <centralized log filename>_<site name>.TXT.

You can also enable decentralized logging by using the DecentralizedLog registry key that is available under HKEY_CURRENT_USER\SOFTWARE\SAP\MSA\MW\MCRM. However, this key is not available by default. It is created when you execute the application for the first time either through the UI or the command line.

Therefore, if you do not specify this parameter (the next time you execute the application), the value of the registry key is used. However, if you specify this parameter, the value of the registry key is ignored.