Installing the ADSI component

The ADSI component is supplied as an installp image on a CD-ROM (SK2L-1782). You use the smitty command of the System Management Interface Tool (SMIT) to install the software from the CD-ROM. See the “Installing the Blueworx Voice Response Software” procedure in the Blueworx Voice Response for AIX: Installation information.

To install the ADSI component, perform the following steps:

  1. Login to AIX: Login as root and type the following command to export your display:
    export DISPLAY= :0
  2. Load the CD-ROM (SK2L-1782).
  3. Install the component: Follow the instructions that are given in “Installing the Blueworx Voice Response Software” in the Blueworx Voice Response for AIX: Installation information and use the SMIT to install dirTalk.ADSI from the CD-ROM.
  4. From the user account from which you control Blueworx Voice Response (normally dtuser), ensure that the exported path environment variable contains $CUR_DIR/ca/ADSI_dir.

    Add this directory to the $PATH statement in the .profile file by inserting the following statement immediately after the statement that invokes vae.setenv:

    export PATH=$PATH:$CUR_DIR/ca/ADSI_dir::

    This means that, after you restart Blueworx Voice Response, the FDM and SDC script files can be dynamically recompiled (see ADSI custom server properties), and the ADSI compiler can be invoked from any directory.

  5. Import ADSI.imp: From the Blueworx Voice Response Welcome window, click Applications —> Applications to open the Applications window.

    Then click Application —> Import —> Replace —> File to import ADSI.imp from /usr/lpp/dirTalk/sw/adsi.

    When the import is complete, click View —> Refresh_Now to see the imported objects.

    The ADSI custom server and the state tables are imported into the ADSI application.

    The adsicomp compiler is stored in the $CUR_DIR/ca/ADSI_dir directory.

    For more information about using the application windows, see the Blueworx Voice Response for AIX: Designing and Managing State Table Applications information.

  6. Create the ADSI script directory: The ADSI script directory is created for you when you install the Blueworx Voice Response base fileset. In versions of IBM WebSphere Voice Response before Version 2.2, ADSI script files were stored in this directory, which is not backed up by the usual Blueworx Voice Response save and restore tools. So, if you use this directory, you must back it up yourself.

    It is better that you store ADSI files in $CUR_DIR/ca/ADSI_dir, which is backed up by the standard save and restore tools.

  7. Starting the ADSI custom server: To start the ADSI custom server, from the Blueworx Voice Response Welcome Window:
    1. Click Operations —> Custom Server Manager .
    2. Click the Run Status of ADSI.
    3. Click Start.

      The Run Status changes to WAITING. A process ID (PID) is filled in.

  8. Starting the ADSI custom server automatically: The ADSI custom server is set to start automatically whenever the system is restarted. To stop this happening:
    1. Click Operations —> Custom Server Manager.
    2. Click the IPL Status of ADSI.
    3. Click AutoStart Off.

Done: You are now ready to use the ADSI component. Use the sample application, ADSI_Banking, to check whether the ADSI component is operating correctly. For information on how to do this, see The sample application: ADSI banking.

ADSI on a single system image (SSI) cluster

If you are deploying the ADSI component on an SSI cluster of Blueworx Voice Response machines, you need import only the ADSI custom server that is on the database server machine.

The $CUR_DIR/ca/ADSI_dir directory is stored on the voice server machine, and is available to all the client machines, because it is NFS-mounted on those machines. Ensure that the $CUR_DIR/adsi directory is empty; this is not NFS-mounted on the client machines. By ensuring that all your ADSI SDC and FDM files are stored in $CUR_DIR/ca/ADSI_dir, you ensure that they are available to all client machines in the cluster.

Do not compile ADSI objects dynamically on an SSI cluster, or in any production environment.