Quick Beginnings for DB2 Connect Enterprise Edition

Configuring the SPM

This section describes the steps required to install the SPM on a DB2 Connect server or on a DB2 Universal Database server, and to configure remote clients and remote DB2 Universal Database servers. It also lists considerations that apply with respect to the location of the transaction manager database, which may reside:

At the DB2 Connect server (the recommended location)
At a DB2 server.

The following rules apply throughout the remainder of this section:

Notes:

For both the TM database and the SPM instance, when cataloguing them for remote client access ,the database alias must be the same as the database name.
Inbound connections from host or AS/400 database clients using two phase commit via SNA to Db2 Universal Database servers do not require a TM database, nor do they need such a database to be defined. The DB2 Syncpoint Manager maintains logs regarding inflight transactions. Information regarding these transactions can be obtained by connecting to the SPM as if it were a DB2 instance. Please note, however, it isnot a DB2 instance and hence does not appear in the output from thedb2ilist command.
If the SPM is on a different node to the TM database, then the SPM and the TM database need to be able to connect to each other. Hence each needs to be catalogued on the other workstation to permit these connections to occur.

Summary of Steps

Applications Which Use DB2 UDB to Coordinate the Multisite Update:

In this situation, only SNA connectivity requires the DB2 Syncpoint Manager. TCP/IP connectivity does not require the SPM for multisite updates.

On the workstation which has the DB2 Syncpoint Manager
This could be either Db2 Connect Enterprise Edition, DB2 Universal Database Enterprise Edition, or Db2 Universal Database Enterprise Edition - Extended.
1. Install DB2 Connect Enterprise Edition or DB2 Universal Database Enterprise Edition or Enterprise Edition - Extended in order to provide multisite update support with host or AS/400 database servers.
2. Create a database instance on the same system. For example, you can use the default instance DB2, or use the following command to create a new instance:
```
   db2icrt myinstance
```
3. Supply licensing information as required.
4. Create a TM database. Any DB2 Version 5 database can be used for this purpose. The TM database should be a local database on the DB2 Connect workstation. For example, to create the TM database, enter the following command in the command line processor:
```
   create Database TMB alias TMB
```
  The Database alias name must be the same as the actual database name.
  Note: If you have only DB2 Connect Enterprise Edition installed, you are licensed to create one database that can be used as the TM database.
5. If the TM database is local, update the TM_DATABASE Database Manager Configuration parameter with the name of the TM database. For example:
```
   update database manager configuration using tm_database TMB
```
6. If the TM database is remote, in order for the SPM to be able to access it during resync operations, you must catalog the TM database and node directory entries on the DB2 Connect workstation. For example:
```
   catalog tcpip node TMBNODE remote SERVERB server dbinst1c
   db2 catalog database TMB as TMB at node TMBNODE
```
  The Database alias namemust be the same as the actual database name.
  
  You must also perform the following steps at the TM database node, in order that it can connect to the location of the SPM. For example:
```
   catalog tcpip node SPMNODE remote SERVERD server dbinst1c
   db2 catalog database SPMNAME as SPMNAME at node SPMNODE
```
  The Database alias name must be the same as the actual database name.
7. configure SNA communications as required. See "Setting up SNA Communications for the DB2 Syncpoint Manager (SPM)".
  The configuration will be easier if the SPM_NAME value is the same as the LU name, and the SPM uses the same LU as the DB2 Connect workstation.
  On an AIX system, the SPM_NAME value must be same as the names of:
  1. The transaction program (TP) profile used by the SPM.
  2. The local side information profile used by the SPM.
  3. The SPM instance name on application requesters.
  Refer to Figure 23.
8. Determine the value to be specified for the SPM_NAME database manager configuration parameter, and optionally values for the SPM_LOG_FILE_SZ and SPM_MAX_RESYNC database manager configuration parameters if the defaults are not appropriate for your situation. See Database Manager Configuration Parameters for SPM for further details.
9. Update SPM_NAME on the DB2 Connect workstation/DB2 Universal Database server. For example, you can use the following command:
```
   update database manager configuration using spm_name SPMNAME
```
10. Ensure that the registry value db2comm includes the value APPC.
11. Stop and restart the database manager on the DB2 Connect workstation/DB2 Universal Database server to start the SPM LU for the first time.
12. For AIX SNA Server, ensure any Symbolic Destination Name configured to access the host or AS/400 database server uses the same LU as specified for the SPM_NAME.
On Each Remote DB2 Client which will access the Host or AS/400 database server
The database administrator must also perform the following steps at each system where a DB2 client will use DB2 Syncpoint services when accessing a host or AS/400 database server.
1. Update the TM_DATABASE Database Manager Configuration parameter with the name of the TM database. For example:
```
   update database manager configuration using tm_database TMB
```
2. Configure communications as required for the DB2 client to connect to the the DB2 Connect/DB2 UDB workstation.
3. If the TM database is remote, catalog the database directory entry for the TM database, and catalog the node entry for the location of the TM database. For example:
```
   catalog tcpip node TMBNODE remote SERVERB server db2inst1c
   db2 catalog database TMB as TMB at node TMBNODE
```
  The Database alias name must be the same as the actual database
  You should be able to connect to the TM database from the DB2 Client. name.
4. If the DB2 Syncpoint Manager (SPM) is remote, catalog the database directory entry for the SPM instance, and catalog the node entry for the location of the SPM. For example:
```
   catalog tcpip node SPMNODE remote SERVERD server db1inst1c
   db2 catalog database SPMNAME as SPMNAME at node SPMNODE
```
  The Database alias name must be the same as the actual database
  You should be able to connect to the SPM from the DB2 Client. name.
5. Stop and restart the database manager on the application requester.

Applications Which Use a TP Monitor to Coordinate the Multisite Update:

In this situation, SNA and TCP/IP connectivity requires the DB2 Syncpoint Manager. Both SNA and TCP/IP connectivity can be simultaneously supported by the DB2 Syncpoint Manager.

On the workstation which has the DB2 Syncpoint Manager
1. Install DB2 Connect Enterprise Edition or DB2 Universal Database Enterprise Edition or Enterprise Edition - Extended in order to provide multisite update support with host or AS/400 database servers.
2. Create a database instance on the same system. For example, you can use the default instance DB2, or use the following command to create a new instance:
```
   db2icrt myinstance
```
3. Supply licensing information as required.
4. If SNA connectivity
  1. Ensure that the registry value db2comm includes the value APPC.
  2. Configure SNA communications as required. See "Setting up SNA Communications for the DB2 Syncpoint Manager (SPM)".
    The configuration will be easier if the SPM_NAME value is the same as the LU name, and the SPM uses the same LU as the DB2 Connect workstation.
    On an AIX system, the SPM_NAME value must be same as the names of:
    1. The transaction program (TP) profile used by the SPM.
    2. The local side information profile used by the SPM.
    3. The SPM instance name on application requesters.
  Refer to Figure 23.
5. If TCP/IP connectivity
  You must ensure the DB2 TCP/IP Listener is activated. Do the following
  1. Ensure that the registry value db2comm includes the value TCPIP.
  2. Ensure the Database Manager Configuration parameter SVCENAME is set to the proper TCP/IP port.
6. Determine the value to be specified for the SPM_NAME database manager configuration parameter, and optionally values for the SPM_LOG_FILE_SZ and SPM_MAX_RESYNC database manager configuration parameters if the defaults are not appropriate for your situation. Ensure that the SPM_NAME value is unique within your network. See Database Manager Configuration Parameters for SPM for further details.
7. Update SPM_NAME on the DB2 Connect workstation/DB2 Universal Database server. For example, you can use the following command:
```
   update database manager configuration using spm_name SPMNAME
```
8. Stop and restart the database manager on the DB2 Connect workstation/DB2 Universal Database server to start the SPM for the first time.
9. For AIX Server, ensure any SNA Symbolic Destination Name configured to access the host or AS/400 database server uses the same LU as specified for the SPM_NAME.

Host or AS/400 Applications Which Access a DB2 Universal Database Server in a Multisite Update

In this situation, SNA connectivity is the only type supported. The DB2 Syncpoint Manager is required in order to permit multisite update. DB2 Universal Database does not support multisite update from host or AS/400 database clients using TCP/IP connectivity.

The database server which is being accessed from the host or AS/400 database client does not have to be local to the workstation which has the DB2 Syncpoint Manager. The host or AS/400 database client could connect to a DB2 UDB server using the DB2 Syncpoint Manager workstation as an interim gateway. This allows you to isolate the DB2 Syncpoint Manager workstation in a secure environment while the actaul DB2 UDB Servers are remote in your organisation. This also permits DB2 common server V2 database to be involved in multisite updates originating from host or AS/400 database clients.

The steps are as follwos:

On the workstation which has the DB2 Syncpoint Manager
1. Install DB2 Universal Database Enterprise Edition or Enterprise Edition - Extended in order to provide multisite update support with host or AS/400 database clients.
2. Create a database instance on the same system. For example, you can use the default instance DB2, or use the following command to create a new instance:
```
   db2icrt myinstance
```
3. Supply licensing information as required.
4. Ensure that the registry value db2comm includes the value APPC.
5. Configure SNA communications as required. See "Setting up SNA Communications for the DB2 Syncpoint Manager (SPM)".
  The configuration will be easier if the SPM_NAME value is the same as the LU name, and the SPM uses the same LU as the DB2 Connect workstation.
  On an AIX system, the SPM_NAME value must be same as the names of:
  1. The transaction program (TP) profile used by the SPM.
  2. The local side information profile used by the SPM.
  3. The SPM instance name on application requesters.
  Refer to Figure 23.
6. Determine the value to be specified for the SPM_NAME database manager configuration parameter, and optionally values for the SPM_LOG_FILE_SZ and SPM_MAX_RESYNC database manager configuration parameters if the defaults are not appropriate for your situation. See Database Manager Configuration Parameters for SPM for further details.
7. Update SPM_NAME on the DB2 Universal Database server. For example, you can use the following command:
```
   update database manager configuration using spm_name SPMNAME
```
8. Configure communications as required for this DB2 workstation to connect to remote DB2 UDB servers, if any.
9. Configure communications as required for remote DB2 UDB Servers to connect to this DB2 Syncpoint Manager workstation.
10. Stop and restart the database manager on the DB2 Universal Database server to start the SPM for the first time.
  You should be able to connect to the remote DB2 UDB servers from this DB2 Syncpoint Manager workstation.
On Each Remote DB2 UDB Server which will be accessed by the Host or AS/400 Database Client
The database administrator must also perform the following steps at each remote system where a DB2 UDB Server will be accessed by a host or AS/400 database client.
The remote DB2 UDB Server must have its communications support configured so that the remote DB2 Syncpoint manager can connect to it AND so that this DB2 UDB Server can connect to the remote DB2 Syncpoint Manager.
1. Configure communications as required for the remote DB2 Syncpoint Manager workstation to connect to this DB2 UDB Server.
2. Catalog the database directory entry for the remote DB2 Syncpoint Manager (SPM) instance, and catalog the node entry for the location of the SPM. For example:
```
   catalog tcpip node SPMNODE remote SERVERD server db1inst1c
   db2 catalog database SPMNAME as SPMNAME at node SPMNODE
```
  The Database alias name must be the same as the actual database
  You should be able to connect to the SPM from the DB2 Client. name.
3. Stop and restart the database manager on the application requester.

[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]

[ DB2 List of Books | Search the DB2 Books ]