Administering Satellites Guide and Reference

Cataloging Instances and Databases on the Model Office

The sections that follow describe how to catalog instances and databases, both remote and local, on the model office. Ensure that you catalog the instances and databases on each model office that you use.

Cataloging Remote Instances and Databases

When a satellite synchronizes, it connects to the satellite control database at the DB2 control server. To connect (and consequently to synchronize), the satellite must have catalog entries for the DB2 control server instance and the satellite control database in its node and database directories.

When the satellite downloads scripts from the DB2 control server to execute, the DB2 instance or database that is the execution target must already be cataloged on the satellite. For replication this would include:

• All replication sources and targets.
• All replication control servers. The database alias names used on the model office must match the database alias names that are defined in the instance of the Control Center.

You can use two methods to catalog the instances and databases that are remote to the model office:

• You can issue DB2 catalog commands through the CLP to catalog the remote instances (nodes) and databases.

  If you use the catalog command, you must ensure that the instance and database alias names that you specify for the command match those that are recorded in the instance of the Control Center. These names are the same names that you use when you create execution targets in the Satellite Administration Center. One simple way to ensure that the names recorded at the model office match those recorded at the Control Center is to write a script that issues the catalog commands. You then run the script on both the Control Center instance and the model office instance. As an alternative, you can also use the Show Command button on the different Control Center windows that you use to catalog instances and databases to display the catalog command, then save the command to a file which you can later execute on the model office.

• You can export a client profile to a file from the instance of the Control Center. You then import this file on the model office. The file contains the information that is required to create the node and database directory entries on the model office.

  Importing the client profile from the Control Center provides one major advantage: you ensure that the instance and database alias names are identical to those in the instance of the Control Center. You use these names when you use the Satellite Administration Center to create execution targets. See Using a Client Profile to Perform Cataloging on the Model Office for more information.

You may have to catalog other nodes and databases on the model office, for example, if your user will be using the satellite as a client to access another DB2 system. You can create entries in the node and database directories on the model office by using the catalog tcpip node and the catalog database commands. For more information, refer to the Command Reference.

Using a Client Profile to Perform Cataloging on the Model Office

To use a client profile to perform cataloging on the model office, perform the following steps.

Note:

The procedure that follows applies to the Windows NT environment.

1. On the system where you are running the Control Center:
   1. Start the Client Configuration Assistant. Click Start and select Programs -> DB2 for Windows -> Client Configuration Assistant. You use the Client Configuration Assistant to create a client profile file. This file contains information to catalog the required target instances and databases on the model office.
   2. Click Export.
   3. On the Select Export Option window, select Customize and click OK.
   4. On the Customize Export window, select the databases that you require as targets on the model office. Do not select the database that is on the model office. Deselect Client settings and CLI/ODBC common parameters.

      Note:

      If you are running the Control Center on the same system as the DB2 control server and the satellite control database, do not select the SATCTLDB database. If you do, the satellite control database will be set up on the model office as a local database.

   5. Click OK.
   6. On the Export Client Profile window, type a name for the file and specify the directory to store the file in.
   7. Click OK.

      The client profile file is saved under the name and location that you specified. You now make the file available to the model office by importing it to the model office.

2. On the model office:
   1. Open a command window.
   2. Issue the db2cfimp file_name command to import the client profile file.

For more information about the db2cfimp command, refer to the Command Reference.

Note:

If you are running the Control Center on the same system as the DB2 control server and the satellite control database, and you followed the note associated with step 1d, you did not select the satellite control database, SATCTLDB. As a result, you will have to catalog the DB2 control server instance, DB2CTLSV, and the SATCTLDB database on the model office using the catalog tcpip node and catalog database commands. For more information about these commands, refer to the Command Reference.

Cataloging Local Instances

If any local instance on the model office will be used as an execution target, you must also catalog this instance on the model office using the same name that you used when you cataloged the instance on the Control Center. Specifically, you must map the instance name used on the Control Center to the actual local instance name using the catalog local node command.

For example, assume that the name that was given to the local instance when it was created is DB2 (On Windows NT, DB2 is the default instance that is created by the installation program). Also assume that you called the DB2 instance on the model office SALESINS when you cataloged it on the Control Center. Because SALESINS is the execution target of scripts that you want to run against the local instance called DB2, you must run the following command on the model office:

  CATALOG LOCAL NODE SALESINS INSTANCE DB2

This command makes SALESINS an alias for DB2 on the model office.

Completing the Setup of the Model Office

As you begin to use the model office during your development phase, you may set up ODBC/CLI values, and modify the database manager configuration values and DB2 registry variables to represent a production environment. You can transfer these configuration values, in addition to the cataloged entries for instances and databases, to your test and production satellite systems using the db2cfexp and db2cfimp commands. For more information, see the sections that follow and Chapter 10, Performing a Mass Deployment.

[ Top of Page ]