Replication Guide and Reference

Setting up the mobile client

You define replication sources and subscription sets in the same way that you define replication source and subscription sets in the nonmobile replication process. The unique situation created in the mobile environment is that the mobile client might not always be connected to the Control Center. When the control server is disconnected from the Control Center, you must find a way to get replication source and subscription set information to the mobile client.

There are two possible ways to distribute the replication source and subscription set information needed to run a mobile replication scenario. Each of these methods has restrictions. The examples below are for replication from a DB2 source. If you are replicating from a non-IBM source, use the DataJoiner Administration Tool instead of the DB2 Control Center.

• Install the DB2 Control Center on the laptop. While the mobile client is connected to the source server, define replication sources and subscription sets.

• Define replication sources and subscription sets using the Control Center on another server, save and customize the SQL files, download the files via diskette or FTP, and run the SQL files on the mobile client.

  1. Define replication sources and subscription sets at the Control Center by connecting to the source server.

  2. Save and edit the generated SQL files. Customize the values for the CONTROL_SERVER, CNTL_ALIAS, SOURCE_SERVER, and TARGET_SERVER columns of ASN.IBMSNAP_SUBS_SET table to match those on the mobile client.

  3. Transfer the customized SQL files and DPCNTL.UDB file to the mobile client via a diskette or by downloading the information.

  4. Run the DPCNTL.UDB files on the mobile client.

  5. Run the customized SQL files on the mobile client.

[ DB2 List of Books | Search the DB2 Books ]