Skip to content

Installing Databridge Host

This chapter includes instructions for installing and upgrading Databridge Host software on the MCP server.

Note

Before You Upgrade Databridge Host
Please note the following:

The SAMPLE files are overwritten by the installation. If you have modified these files, make backup copies before you run Databridge Installation WFL. If you changed SYMBOL/DATABRIDGE/SUPPORT, note the changes you made and make the corresponding changes to the new SYMBOL/DATABRIDGE/SUPPORT.

You can use Accessory parameter files from earlier versions with this release. If the current version includes new options you want to use, you can add them by typing them into your existing parameter file.

Install Databridge Host

The installation process for Hot Fixes, Updates and Service Packs for the host software in 7.0 has been simplified. Hotfixes will be supplied in a container file that has a name similar to the base release (e.g. DB70-01-Hotfix). To apply the patch, follow the same procedure as you did when installing the base release. Run the install WFL to install the software.

In this new installation process a patch will replace all files previously installed rather than only the changed files. If the base release isn't installed you can directly install a patch without having to first install the base release.

To install Databridge Host

  1. Sign on to a privileged usercode

    You can no longer use the install WFL to install Databridge to a nonprivileged usercode.

  2. Upload Databridge container to the host

    Upload the DB70-00-BASE file using a file transfer tool capable of binary/image transfers to the privileged usercode where Databridge is to be installed.

    This DB70-00-BASE file replaces the IMAGE and DISKINSTALL files used in prior releases. The DISKINSTALL image is still available, and can be uploaded and utilized to get the install WFL. Note that, the install WFL can also be extracted from the DB70-00-BASE file, which makes this file redundant. The file DISKINSTALL will not be provided in the next release.

  3. Unwrap the Databridge installation WFL (WFL/DATABRIDGE/INSTALL)

    To extract the install WFL from the file DB70-00-BASE, enter the following CANDE command:

    WFL UNWRAP *WFL/DATABRIDGE/INSTALL AS WFL/DATABRIDGE/INSTALL OUTOF DB70-00-BASE

  4. Start the Databridge Installation WFL.

    If you want to install the Databridge software to a different pack family than primary pack of your FAMILY substitution statement (FAMILY DISK = primarypack

    OTHERWISE secondarypack) use the following command instead.

    START WFL/DATABRIDGE/INSTALL ("DATABRIDGE", "otherpack")

    Most WFLs are copied with a SAMPLE node in the title. They will also be copied without the SAMPLE node using the ADD command so that first-time installations will have WFL files with the standard name but existing WFL files are not replaced. Parameter files, like DATA/SERVER/SAMPLE/CONTROL, are also copied without the SAMPLE node if the file doesn't already exist.

  5. For first-time installations, edit the DBServer control file (DATA/SERVER/CONTROL). Otherwise, skip to step 8.

    1. (Optional) Change TCP/IP Port = 11367 (the default) to the port you want to use.

    2. Change SOURCE <datasourcename> to the name of the data source that the client will use.

    3. Change Database = (<usercode>)DESCRIPTION/<databasename> ON <packname> to reflect the usercode/location of the description file for the database to be replicated.

  6. If you are upgrading, do the following:

    1. Bring down the Databridge Server using the AX QUIT command.

    2. Recompile your tailored support libraries by entering the following command (replacing usercode, databasename, and pack with your values):

    START WFL/DATABRIDGE/COMP ("SUPPORT", "(usercode)databasename ON pack")

    For more information on recompiling, see the Databridge Host Administrator's Guide.

Start the Databridge Server:

START WFL/DATABRIDGE/SERVER

Note

  • If your database uses guardfiles, you can include Databridge under database guardfile validation. See Set Up Guardfiles.
  • For information about security options, see "Databridge Security" in the Databridge Host Administrator's Guide.

After You Upgrade

Make sure to recompile any tailored support libraries. See the Databridge Host Administrator's Guide.

The DMSII Support library is compiled automatically after you upgrade. However, you can save time by manually compiling this library before you start replicating. For instructions, see Chapter 3, "DMSII Support" of the Databridge Host Administrator's Guide.

Set Up Guardfiles

If your database uses guardfiles, Databridge can be included under database guardfile validation. For validation of guardfiles to work, the relevant guardfile must specify read access (RO) for the Databridge Accessory and/or the usercode under which the Databridge Accessory is running.

In addition, the Databridge Engine (DBEngine) must have read access to the actual database guardfile. You can accomplish this in one of the following ways:

  • Run the Databridge Accessory under the usercode that owns the guardfile. For example, if the guardfile is (PROD)GUARDIAN/FILE, run the Accessory under the PROD usercode.

  • Change the security of the guardfile to PUBLIC IN.

  • Make sure that DBEngine is a privileged program. DBEngine is marked as a privileged program on the release media.

    Note

    Access to the guardfile itself is enforced by the MCP. Therefore, even if you make the database visible to the Accessories, you must still give DBEngine read access to the guardfile, as explained above.

Databridge Components and Guardfiles

Databridge Accessories and the Databridge Server Workers (but not the Databridge Server itself) must have read access to the database (physical or logical) they are using. No other rights are necessary. DBInfo and GenFormat require read access to the physical database. DBInfo uses the physical (versus a logical) database when searching for a quiet point.

Databridge DMSII Support

The Databridge DMSII Support library must have OPENINQUIRY, OPENUPDATE, and FIND access to the physical database. OPENUPDATE allows the extract routines to generate a small amount of audit when doing an OFFLINE clone.

Here's an example of a guard file fragment for a physical database. In this example, the fictional site has Databridge software installed under the (DB) usercode on the family named DBPACK and the database DESCRIPTION file is called (PROD)DESCRIPTION/BANKDB ON DMSPACK.

PROGRAM (DB)OBJECT/DATABRIDGE/DBINFO ON DBPACK = RO;
PROGRAM (DB)OBJECT/DATABRIDGE/GENFORMAT ON DBPACK = RO;
PROGRAM (DB)OBJECT/DATABRIDGE/DMSIISUPPORT/BANKDB/PROD ON DBPACK = RW,
DMVERBS = (OPENINQUIRY, OPENUPDATE, FIND);

The DMVERBS list for the physical database prevents any actual updating because DELETE, STORE, etc., are not allowed.

If you are using DBTwin or the DMSII Client, the DMSII Support library on the secondary system must have updating access as well and in that case the DMVERBS list should be omitted entirely.

Accessories and Databridge Server Workers

The Accessories and Databridge Server Workers (but not the Databridge Server itself) must be listed in the guardfile that protects the database they will be using. However, if they use a logical database instead of a physical database, put these entries in the guardfile that protects the logical database.

Here's an example of guardfile fragments for a physical or logical database. (In this example, Databridge is installed under the (DB) usercode on the family named DBPACK and Databridge Clients run on hosts called IPADDRESS1 and IPADDRESS2.)

PROGRAM (DB)OBJECT/DATABRIDGE/SPAN ON DBPACK = RO;
PROGRAM (DB)OBJECT/DATABRIDGE/SNAPSHOT ON DBPACK = RO,
PROGRAM (DB)OBJECT/DATABRIDGE/LISTER ON DBPACK = RO;
PROGRAM (DB)OBJECT/DATABRIDGE/AUDITTIMER ON DBPACK = RO;
PROGRAM (DB)DBSERVER/WORKER/1 ON IPADDRESS1 = RO;
PROGRAM (DB)DBSERVER/WORKER/1 ON IPADDRESS2 = RO;
PROGRAM (DB)DBSERVER/WORKER/2 ON IPADDRESS1 = RO;
PROGRAM (DB)DBSERVER/WORKER/2 ON IPADDRESS2 = RO;

If you allow more than two Databridge Server Workers to run concurrently, add entries like the ones above with the appropriate number for the last node.