Intermediate Step Execution of the Mobile Client Rollout Manager 

The activities performed by the Mobile Client Rollout Manager can be categorized into the following steps:

...

       1.      Common steps

The steps that are common to all the rollout or replacement sites are listed below:

¡        Read stationary site details

¡        Check the inbound queue of the stationary site for pending records

¡        Release selected sites for reuse

¡        Clean the outbound queue on the CRM server for selected sites

¡        Stop the ConnTrans NT Service

¡        Run ConnTrans application

¡        Start the extract for selected sites

¡        Backup the database

¡        Start the ConnTrans NT Service

       2.      Restore Database

       3.      Assign site

       4.      Invoke ConnTrans

The following figure illustrates the above mentioned steps that are involved during the execution of the Mobile Client Rollout Manager:

All these steps are automatically executed in the above mentioned sequence when you rollout or replace laptops by using the Mobile Client Rollout Manager. However, if an error occurs during the execution of any of the steps, you have to repeat all the four steps, which is a time consuming process.

The Mobile Client Rollout Manager is enhanced to allow you to execute from an intermediate step in which the error occurred. You can execute the application from any intermediate step starting from step 2 till step 4. As a result, the overall performance improves during the rollout of laptops.

During the rollout or replacement of laptops, if an error occurs in the assignment of sites (step 3), you can execute the application again from step 3. As a result, you do not have to repeat steps 1 and 2.

You can execute the application from an intermediate step only through the command line. The command line options are enhanced to execute the application from an intermediate step. For more information, see Executing Mobile Client Rollout Manager from the Command Line.

When you execute the application from an intermediate step:

·        All the preceding steps must have been executed for that site.

·        All the succeeding steps are automatically executed. Therefore, you cannot execute an intermediate step only.

·        All the sites are executed from the same step. Therefore, you cannot execute different sites from different steps. For example, the Mobile Client Rollout Manager cannot simultaneously perform the database backup of Site A and Restoration of the database for Site B.

If you execute the application from an intermediate step, the same is indicated in the stationary site log file and the site specific log files (if enabled).