DB2 Connect Quick Beginnings for Linux**

Using the Control Center to Enable Multisite Updates

You can use the Control Center to provide multisite updates. The procedure is simple, and is outlined below. For more information about the multisite update configuration process, including how to configure your system manually, refer to the online Connectivity Supplement.

Starting the Multisite Update Wizard

From the Control Center, click the [+] sign to expand the tree view. With the right mouse button, select the instance that you wish to configure. A pop-up menu opens. Select Multisite Update --> Configure menu item.

Wizard Steps

The Wizard provides a notebook-type interface. Each page of the wizard will prompt you for certain information about your configuration. The pages are shown below in the order in which you will encounter them.

Step  1.
Specify a Transaction Processor (TP) monitor.
This field will show the defaults for the TP monitor you have enabled. If you do not want to use a TP monitor, select Do Not Use a TP Monitor.
Step  2.
Specify the communications protocols you will use.
Step  3.
Specify a Transaction Manager database.
This panel defaults to the first database you connect to (1ST_CONN). You can leave this default or select another catalogued database.
Step  4.
Specify the types of database servers involved in the update, and also whether or not TCP/IP is to be used exclusively.
Step  5.
Specify the Syncpoint Manager settings.
This page will only appear if the settings on the previous page indicate that you need to use DB2's Syncpoint Manager in a multisite update scenario.

Testing the Multisite Update Feature

Step  1.
Select the instance with the right mouse button and choose the Multisite Update --> Test menu option from the pop-up menu. The Test Multisite Update window opens.
Step  2.
Select the databases you want to test from the available databases in the Available databases list box. You can use the arrow buttons in the middle to move selections to and from the Selected databases list box. You can also change the selected userid and password by directly editing them in the Selected databases list box.
Step  3.
When you have finished your selection, click OK at the bottom of the window. The Multisite Update Test Result window opens.
Step  4.
The Multisite Update Test Result window shows which of the databases you selected succeeded or failed the update test. The window will show SQL codes and error messages for those that failed.

[ Top of Page | Previous Page | Next Page ]

Step 1.	Specify a Transaction Processor (TP) monitor. This field will show the defaults for the TP monitor you have enabled. If you do not want to use a TP monitor, select Do Not Use a TP Monitor.
Step 2.	Specify the communications protocols you will use.
Step 3.	Specify a Transaction Manager database. This panel defaults to the first database you connect to (1ST_CONN). You can leave this default or select another catalogued database.
Step 4.	Specify the types of database servers involved in the update, and also whether or not TCP/IP is to be used exclusively.
Step 5.	Specify the Syncpoint Manager settings. This page will only appear if the settings on the previous page indicate that you need to use DB2's Syncpoint Manager in a multisite update scenario.

Step 1.	Select the instance with the right mouse button and choose the Multisite Update --> Test menu option from the pop-up menu. The Test Multisite Update window opens.
Step 2.	Select the databases you want to test from the available databases in the Available databases list box. You can use the arrow buttons in the middle to move selections to and from the Selected databases list box. You can also change the selected userid and password by directly editing them in the Selected databases list box.
Step 3.	When you have finished your selection, click OK at the bottom of the window. The Multisite Update Test Result window opens.
Step 4.	The Multisite Update Test Result window shows which of the databases you selected succeeded or failed the update test. The window will show SQL codes and error messages for those that failed.