You set up your satellite environment much like you set up replication for any other environment. The only difference with satellite is that you set it up in stages. Administrators need to do the following things to set up replication for the satellite environment:
This section discusses both of these steps.
To create the replication environment:
Use the DB2 Control Center to create your control tables and define your replication sources and subscription sets. For more information on how to create control tables and define replication sources and subscription sets with the DB2 Control Center, see Setting up your replication environment.
When you are sure that your replication test environment is running correctly, promote your replication sources and subscription sets. The promote function takes the parameters of defined replication sources and subscription sets from the replication test environment and re-creates the identical replication setup for the replication production environment. For more information about the promote function, see Copying your replication configuration to another system.
After you create the replication environment, you must set up the satellite environment, and generalize the subscription sets for the satellite environment. For more information on setting up your satellite environment, see the Administering Satellites Guide and Reference.
To set up the satellite environment:
To define a group, use the Satellite Administration Center. The Satellite Administration Center is a tool that provides centralized administrative support for satellites.
You must create satellites to be members of the group that you just created. For more information about how to create satellites, see the Administering Satellites Guide and Reference.
An application version is the set of setup, update, and cleanup batches that are associated with a specific version of an application that runs on the satellites of a group. If an application changes on the satellite that requires changes to the underlying database configuration, you must create a new application version to set up and maintain the new configuration. For more information about how to create an application version, see the Administering Satellites Guide and Reference.
You cannot perform data replication on the satellite environment until a subscription set is generalized. When you generalize a subscription set, parameters for the satellite environment are automatically defined in script files. These script files are based on a pre-existing replication configuration and are used to setup and invoke replication for satellites. For more information about generalizing a subscription set, see the Administering Satellites Guide and Reference.
You can deploy the same replication configuration for thousands of satellites that execute the same application version. You can also deploy customized replication definitions for individual satellites.
Perform this step only if you did not specify the type of database recovery that you want on the satellite at installation time. If capturing data and database roll-forward recovery are required, set LOGRETAIN=RECOVERY. If capturing data is required without database roll-forward recovery, set LOGRETAIN=CAPTURE. When LOGRETAIN=CAPTURE, the Capture program will automatically call the PRUNE LOGFILE command when it completes its cycle. For more information about database recovery and considerations for using circular or archival logging, see the DB2 Administration Guide.
The Apply program obtains the user IDs and passwords required for replication as follows: