You run a test synchronization to ensure that a satellite can connect to, and is recognized by, the DB2 control server. Before a test synchronization can be done, a number of different pieces of information must be created on both the DB2 control server, and on the satellite from which the test synchronization will be executed. The following sections describe how to:
You use a variety of windows and notebooks in the Satellite Administration Center to prepare the DB2 control server for satellite synchronization. The description that follows provides an overview of the recommended steps and the order in which they should be performed. For detailed information about any of the windows or notebooks referenced in this section, refer to the online help provided with the Satellite Administration Center.
Before you can use the Satellite Administration Center, ensure that a satellite control database is cataloged on the Control Center. If the DB2 control server is on the same machine as the Control Center, the DB2 control server instance, and the satellite control database, SATCTLDB, are automatically cataloged. If the DB2 control server is running on a different machine than the Control Center, you must catalog the system, the DB2 control server and the satellite control database on the Control Center. For information about performing this task, see Chapter 4, Cataloging Instances and Databases.
The Satellite Administration Center is enabled when the Control Center detects that any of the cataloged instances contain a satellite control database. You can open the Satellite Administration Center from the pop-up menu associated with the instance that contains the satellite control database, or from the pop-up menu associated with the satellite control database. You can also open it from the Control Center tool bar. For information about using the Satellite Administration Center, refer to the online help provided with it.
| Note: | You should only administer the satellite environment from the Satellite Administration Center. |
See Chapter 13, DB2 Control Server Planning and Installation for information about installing and setting up the DB2 control server.
In the satellite environment, you administer groups of satellites, and not individual satellites. This basic principle also applies to the authentication that is required to access the DB2 control server and the satellite control database. All the satellites of the group use a group-level user ID and password when they connect to the satellite control database for synchronization.
To set up the DB2 control server to enable satellite synchronization:
Notes:
You specify this same user ID and password either when you install DB2 on a satellite that will belong to the group, or when you run a synchronization test for the first time from the satellite. The satellite requires the user ID and password so that it can authenticate with the DB2 control server. Each satellite that belongs to the group will use the same user ID and password to authenticate with the DB2 control server for the purpose of synchronization. For more information, see Setting up the Satellite Authentication File.
The next task is to grant privileges to the tables in the satellite control database. You will need to grant table privileges both to the user ID that the group satellites use to connect to the DB2 control server, and to administrative and help-desk staff.
You use standard DB2 authentication and authorization mechanisms to control access to the satellite control database. For more information about how to grant privileges to tables, refer to the description of the GRANT statement in the SQL Reference. You can also use the Privileges notebook in the Control Center to grant privileges on the tables. For information about using this notebook, refer to the online help that is available from it. For general information about DB2 security, refer to the description of how to control database access in the Administration Guide.
The sections that follow describe why you need to grant table privileges, and provide guidance on the types of privileges that you should consider granting to the different types of users. In addition, information is provided about the type of privileges that you should grant on the stored procedures that are part of the DB2 control server.
Each group of satellites uses one authentication credential to both connect to the DB2 control server, and to access the tables of the satellite control database. You specify the name of this authentication credential when you create the group. See Creating a Group for more information.
The authentication credential, as described in Chapter 3, Authentication in the Satellite Environment, is the combination of a user ID and a password. You can use the Edit Group window to see the name of the authentication credential that the group satellites use to access the DB2 control server. You can use the Edit Authentication window to obtain the user ID that is associated with the authentication credential.
You must grant appropriate table privileges to the user ID of the group-level authentication credential so that the group satellites can access the tables in the satellite control database when they synchronize. Tables and Authorizations lists the recommended authorities that you should grant to this user ID for the satellite control tables. To simplify the administration of the privileges, you can create a group at the operating system level to contain the user ID associated with the authentication credential for each group. If you use an operating system group, you can grant and manage database and table privileges for the operating system group, instead of having to manage the privileges for each user ID for each group of satellites. To set up and manage the privileges:
If you change the user ID that the group satellites use to access the DB2 control server and the satellite control tables, add it to the operating system group to ensure that this user ID has the appropriate table privileges.
If you change the password that is associated with the user ID that the group satellites use to synchronize, the user ID's table privileges are not affected.
In your organization, you may have staff who require administrative authority to the satellite control database, SATCTLDB. If you have a help desk, likely the help-desk staff also require access to the satellite control database. You should consider using two operating system groups to control access to the satellite control database, one for administrative staff, and one for help-desk staff. If you use groups, you can grant and manage database and table privileges for two groups, instead of having to manage the privileges of each user separately. To set up and manage the privileges for the administrative staff:
You can create a group for your help-desk staff following a similar procedure. Tables and Authorizations lists the minimum recommended authorities that you should grant to the group to which the help-desk staff belong. Depending on your requirements, the recommendations in Tables and Authorizations may be too restrictive, as it only enables the help-desk staff to view information when they use the Satellite Administration Center. For example, if you want help-desk staff to be able to use the Satellite Administration Center to fix satellites, the group for the help-desk staff requires the following table privileges:
| Note: | For information about these tables, refer to the following Web site:
www.software.ibm.com/data/db2/library/satellite |
You may want the help-desk staff to use the Satellite Administration Center to perform other tasks as well. For example:
In the following table, recommendations for privileges granted to the tables in the satellite control database are provided. Before granting these privileges, you must grant the CONNECT privilege on the SATCTLDB database to:
| Note: | A blank cell in the following table indicates that no privilege is required for the table in the satellite control database. |
| Table Name | Privilege for Group Authentication Credential | Privilege for Help-Desk Staff Group |
|---|---|---|
| TARGET_AUTH | SELECT | SELECT |
| TARGETS | SELECT | SELECT |
| GROUPS |
| SELECT |
| SCRIPTS | SELECT | SELECT |
| SUCCESS_CODES | SELECT | SELECT |
| SUCCESS_RELATIONS | SELECT | SELECT |
| BATCHES | SELECT | SELECT |
| BATCH_STEPS | SELECT | SELECT |
| APP_VERSIONS |
| SELECT |
| GROUP_BATCHES | SELECT | SELECT |
| SATELLITES | SELECT, UPDATE | SELECT |
| GROUP_APPVER_PARMS | SELECT | SELECT |
| SAT_APPVER_PARMS | SELECT | SELECT |
| GROUP_SUBSCR_SETS |
| SELECT |
| GRP_HOR_DATASLICES | SELECT | SELECT |
| SAT_HOR_DATASLICES | SELECT | SELECT |
| LOG | INSERT | SELECT |
| Note: | When you create the authentication credential that the satellites use to
synchronize in test mode, you can set up the user ID to have minimal access to
the tables in the satellite control database. For example, you can
grant this user ID the SELECT privilege on only the SATELLITES, TARGET_AUTH,
and TARGETS tables. Consider doing this if, for example, you want to
use a different authentication credential for the test synchronization than
for a synchronization session in which the satellites execute group
batches.
If the satellites are enabled to execute the group batches when they synchronize in test mode, they will download the group-level user ID and password that they require to authenticate with their DB2 control server for synchronization. |
For information about the table privileges required for data replication, refer to the description of how to set up the replication environment in the Replication Guide and Reference.
The following table lists the bind files and stored procedures, and the
type of privileges that you should grant on them to your groups.
| Bind File or Stored Procedure | Privilege for Administrative Group | Privilege for Group Authentication Credential | Privilege for Help-Desk Staff Group |
| DB2SATCS | REBIND/EXECUTE | EXECUTE |
|
| DB2PROM | EXECUTE |
|
|
The next step is to create a new group. The group will consist of related satellites that share characteristics such as the database definition and the application that runs on the satellites. When you create the group, you must specify the authentication credential that you created in Creating the User ID for Satellite Synchronization. The satellites in the group will use this authentication credential when they synchronize.
To perform this task, use the Create Group window. You specify the name of the authentication credential required for synchronization in the Authentication name field.
| Note: | You cannot create a group without specifying an authentication credential for it. |
The next step is to create the test satellites that will belong to the group. You will use these test satellites to perform the synchronization test. Later, you will use them to test the group batches.
Use the Create Satellite notebook to create the satellites. When you create a satellite, you must specify an identifier for it. This identifier must match the value that exists on the satellite. For more information, see Setting the DB2SATELLITEID Registry Variable.
You can use the subgroup attribute of satellites to further categorize the satellites. The subgroup can identify different regions, or any other grouping that you require. You specify the subgroup attribute in the Subgroup field of the Create Satellite notebook. You can also use the subgroup attribute to control the staging of a deployment. For example, you could enable one subgroup to synchronize before enabling the other subgroups.
When satellites are created, they are production satellites by default, and they are not enabled to execute batches.
The next task is to make the satellites test satellites. To perform this task:
The satellites are now test satellites, but still cannot execute the group batches. You will enable these satellites to execute the group batches when you test the group batches.
Before a satellite can connect to the DB2 control server, three different sets of information must be set up on the satellite: the authorization file, the application version, and the satellite ID. You can set up this information either when you install the satellite, or later.
The satellite authentication file, satadmin.aut, is created either when you install DB2 Satellite Edition with the control server synchronization component, or when the first test synchronization is run from the satellite. During the installation process, you can supply a user ID and password that will be used to connect to the satellite control database on the DB2 control server when the satellite synchronizes. If you supply this information during installation, the satadmin.aut file is created and the user ID and password stored in it. If you do not provide the user ID and password during installation, you will be prompted for them the first time you run the db2sync -t command to perform a synchronization test. At this time the file will be created and the authentication credentials stored in the file.
For information about the db2sync command, see db2sync - Start DB2 Synchronizer.
When a satellite synchronizes, it passes its application version to the DB2 control server. The DB2 control server uses this information, in conjunction with the group that the satellite belongs to, to determine which of the group's application-version batches the satellite will execute. The application version allows you to support multiple versions of the end-user application within a group, which enables you to perform a staged deployment of a new version of the application. For more information, see Installing a New Version of an Application and Application Versions.
You can specify the application version of the satellite when you install DB2 Satellite Edition with the control server synchronization component. You can also specify the application version when you install the end-user application on the satellite. If you specify the application version when you install the end-user application, the install program must call either the db2SetSyncSession API or the db2sync -s command to record the application version. For more information about the db2SetSyncSession API, refer to the Administrative API Reference. Also see Setting the Application Version on the Satellite. For more information about the db2sync command, see db2sync - Start DB2 Synchronizer.
| Note: | The application version is case sensitive. |
You may find it more convenient to supply the application version when you install your initial test satellites. In a large production environment, you should specify the application version when you install the end-user application.
When a satellite synchronizes, it passes the its ID to the DB2 control server. The satellite ID is determined as follows:
The DB2 control server verifies that the same value is recorded in the satellite control database. You create the satellite ID entry in the satellite control database when you create the satellite using the Create Satellite notebook in the Satellite Administration Center. For more information, see Creating Test Satellites. The satellite ID must be recorded on both the satellite and in the satellite control database before synchronization can occur. Having the satellite ID on both the satellite and in the satellite control database ensures that only known satellites can synchronize.
If you do not want to use the logon ID as the satellite ID, you can set the value of the DB2SATELLITEID registry variable when you install DB2 Satellite Edition with the control server synchronization component. If you do not specify this registry variable during installation, you must specify it before synchronization can occur.
To set this registry variable, use the db2set command on the satellite as follows:
db2set DB2SATELLITEID='identifier' -i instance_name
Where:
Notes:
The db2set command can be issued from the operating system command line, or from an application program, for example, an installation program for the end-user application. For more information about the db2set command, refer to the Command Reference.
For information about installing DB2 Satellite Edition, see Chapter 14, Planning for DB2 Satellite Edition Installation and Chapter 15, Installing DB2 Satellite Edition.
When you are finished setting up the DB2 control server and your test
satellites, you should ensure that the configuration information in the
satellite control database and on the satellite is both correct, and
consistent.
| Configuration Information | Satellite Control Database | Satellite |
|---|---|---|
| Satellite ID | Create the ID using the Create Satellite notebook. You can view the ID using the satellite details view. | The satellite ID can be either the user's logon ID, or the value of the DB2SATELLITEID registry variable on the satellite. |
| Authentication credential required for synchronization | Create the authentication credential using the Create Authentication window, and associate the credential with the group when you create the group. | The file satadmin.aut must exist on the satellite. Create the file using the db2sync -t command. Alternatively, you can specify the user ID and password when you install DB2 Satellite Edition with the control server synchronization component. |
| Application version | Create using Create Application Version window. | Set the application version on the satellite using either the db2sync -s command, or the db2SetSyncSession API. You can also specify the application version when you install DB2 Satellite Edition with the control server synchronization component on the satellite. |
In addition, the versions of DB2 on both the DB2 control server and the satellite must be compatible. See Incompatible Versions of DB2 on the Satellite and the DB2 Control Server for details.
You have now set up and configured the DB2 control server, and one or more test satellites. You are at the point at which you can run a test synchronization. To test the synchronization capability of the satellite:
db2sync -t
The DB2 Synchronizer opens in test mode.
The Connect to Control Database window opens if you did not specify the user ID and password that the satellite requires to synchronize when you installed DB2 Satellite Edition.
The Catalog Control Database window opens if the satellite control database is not yet cataloged at the satellite.
When you select the DB2 control server instance, the Host name and Service name fields are automatically updated with the values for that instance.
If the list of systems returned by DB2 discovery does not include the system on which the DB2 control server resides, you must enter the host name for the system in the Host name field, and the port number in the Service name field. Then click OK.
If all the information specified at the DB2 control server and at the satellite matches, and the satellite control database is correctly cataloged, the test synchronization will succeed. The next major task is to create the test batches that set up the database definition and data for the first version of the end-user application, then to test these batches.
[ Top of Page ]