Administering Satellites Guide and Reference

Post-Deployment Phase

After the group's satellites are deployed, the model office reflects the current state of a typical group satellite, though some differences may exist between the model office and a satellite. For example, the hardware configuration or the operating system may be different on the model office.

Because the model office is configured to run one version of the end-user application that is being used by the group satellites, you can use the model office to re-create the problems that occur on a production satellite. This means that you can use the model office to define and test fix batches to correct these problems.

The model office is vital, as it provides existing tools, like the Control Center, a working and representative database against which to operate. You can generate scripts using the SmartGuides, notebooks, and windows of the Control Center against the model office. You then submit the scripts for execution against the model office and examine the changes caused by them, without affecting any production satellites. When you are satisfied with the results that the scripts produce, you can add the scripts to the group batches (or to a fix batch), as required. The scripts will be executed by the group satellites when they synchronize.

You should take backup images of the model office. If a change you make while testing a fix batch for a group satellite produces unexpected results, you can use the backup image to restore the model office. After the model office is restored, it will be at a known state, and you can try a different fix. See Chapter 9, Recovering the Satellite Environment for more information.

Using the Model Office System During the Post-Deployment Phase

When your users begin to use the production satellites to run the application, unanticipated problems can occur. For example, a performance problem could occur. Because the model office represents the deployed satellites, you can use it to investigate the problem, and to develop a test script to correct it.

• Using tools such as the Control Center and the Command Line Processor, you can examine the model office and determine which changes are required to address a production problem.
• You can use the Control Center to make changes to the model office to correct problems. Instead of using the Control Center tools to complete the changes, use the Show SQL and Show Command options to generate and save scripts. You can then create a new test level of the batches for the application version, and add the scripts to the setup, update and cleanup batches, as required. The next time the model office synchronizes, it will execute the new batch steps. You can determine the effect of the changes by reviewing the execution logs, and by using the Control Center tools to examine the model office. If the changes are correct, the next step would be to promote the test level to production for the production satellites to execute.

The model office has already executed the batches that you promoted to production. When the rest of the group satellites next synchronize and execute the new batch steps, the model office will represent the group satellites that are at the same application version. If another problem occurs, you can again use the model office to investigate the problem, and to develop and test scripts to correct the problem.

[ Top of Page ]