Show Contents / Index / Search

Switching from Command-Line to Service Operations

Use this procedure if you currently run the Databridge Client 6.1 or later from a command line and want the service to run it, or if you need to add existing data sources to the service.

To operate the service on the Client machine, you'll need a specific directory structure, referred to as the service's working directory. You can use the Migrate program to create this directory.

Important! If you're in the process of upgrading your Databridge software, use the instructions in the Databridge Installation Guide for upgrading the Client.

To switch to the service based client (Windows)

  1. Set up the service's working directory. If you use the Client on Windows, you can run the Migrate program to do this. For more information, see "The Working Directory" in the Databridge Installation Guide.
  2. Install the Client Console that matches the version of Databridge Client software you use. For instructions, see the Databridge Installation Guide.
  3. Do one of the following:
    • If you use a text Client configuration file, complete the remaining steps.
    • If you use a binary Client configuration file (that is, you have not exported your configuration file to a text file to edit it), skip to step 4.
  4. From the data source directory, locate the config folder, and copy the text configuration file dbridge.cfg to a file named dbridge.ini.

    The following image shows an example of a working directory for a data source named "corporatedb".

    global db linked file template

  5. From a command prompt, go to the working directory for your data source, and run the dbutility IMPORT command. This creates a binary configuration file required by the service.
  6. Make sure that the Client service is running. From the Start menu, choose Control Panel > Administrative Tools > Services, double-click Attachmate Databridge [version] Client service, and click Start.
  7. Start the Client Console.
  8. Add a service, if you haven't already done so. For instructions, see the Client Console Help (Help > Help Contents).
  9. With the service selected, from the DataSource menu, select Advanced > Add Existing Data Source, type the data source name (for example, zdatabase), and then click OK.

To switch to the daemon based client (UNIX/Linux)

  1. Log on as the userid specified in the USERID parameter of the file globalprofile.ini. This is the same userid you currently use to run the command-line client.
  2. Set the current directory to the home or other directory to which you have write access and copy the script dbdaemon from the install directory to it. This allows you to make changes to the script.
  3. In an editor, open the script dbdaemon.
  4. Make sure that the environment variables (such as INSTALL_DIR, WORKING_DIR, ORACLE_HOME) are correct for your system and edit them as needed.
  5. Save and close the script.
  6. Start the daemon by typing the following:

    dbdaemon start

  7. To verify that the daemon is running use the ps command, which should produce output similar to the following:

    donaldduck@VMOPENSUS114-64:~> ps -ef | grep DBC

    donaldduck 1110 1 0 12:00 ? 00:00:00

    /opt/dbridge62/DBClntControl

  8. If the daemon doesn't start, in the script dbdaemon, make sure that the WORKING_DIR and INSTALL_DIR environment variables are correct. Also, check the service's working directory to determine if a file dbdaemon.log was created and if it contains any clues.
  9. Start the Client Console.
  10. Add a service, if you haven't already done so. For instructions, see the Client Console Help (Help > Help Contents).
  11. With the service selected, from the DataSource menu, select Advanced > Add Existing Data Source, type the data source name (for example, zdatabase), and then click OK.
  12. Type su to switch to the root user and then copy the script dbdaemon from the location you specified in step 5 to the following location:
    • (Linux/Solaris) /etc/init.d
    • (AIX) /etc/rc.d/init.d
    • (HP-UX only) /sbin/init.d
  13. To make the operating system automatically start the daemon whenever the system starts, consult the documentation for your operating system.