Installing the connector on a UNIX system

To install the connector on a UNIX system, run the Installer for IBM WebSphere Business Integration Adapter. After installation, the installation directory $ProductDir/connectors/Portal/dependencies contains the following files needed by the connector:

Verify that the following files are installed in the $ProductDir/lib directory:

Note:
The WBIA.jar corresponds to ADK 2.2.0. If you are using older versions of ADK, refer to the "Connector Development Guide" on getting the corresponding WBIA.jar.

To configure the connector on a UNIX system, follow these steps, depending on your database software and operating system:

Configuring the connector in an AIX/DB2 environment

To configure the connector on an AIX system, follow these instructions in order:

As DB2 user

  1. Log in to the AIX system with the DB2 user ID used for the instance for Portal Infranet, for example, db2instl.
  2. Enter the following command:

    db2 catalog tcpip node local_DB2_hostname remote remote_DB2_hostname 
    server DB2_instance_portnumber
    

    Example:

    db2 catalog tcpip node db2host remote db2host server 50000

  3. Enter the following command:

    db2 catalog database DB_name as DB_name at node DB2_hostname
    

    Example:

    db2 catalog database CWPortal as CWPortal at node db2hos

  4. Log off.

As user "pin"

  1. Log in to the AIX system as pin (create a pin user account if necessary).
  2. Copy the file db2profile into user pin's home directory, and add the line ../db2profile to the .profile file to execute the shell script file db2profile before starting the connector.

    The file is located in the directory sqllib, in the home directory of the account that was used to install Portal Infranet for DB2, for example, /home/db2instl/sqllib.

    Copy the file database.bnd from $COSSWORKDS/connectors/Portal/dependencies/config_files/DB2 to user pin's home directory.

  3. Enter the following command:

    db2 connect to DB_name user pin using pin
    

    Example:

    db2 connect to CWPortal user pin using pin

  4. Enter the following command:

    dbw bind database.bnd

  5. Enter the following command:

    db2 disconnect all

  6. Add the following line to the .profile file of user pin:

    export DB2DBDFT=DB_name
    

    Example:

    export DB2DBDFT=CWPortal

  7. Log off pin.

As user "crowding"

  1. Log in to the AIX system as user cwadmin, which is used to start up the connector.
  2. Execute the shell script file db2profile before starting the connector.

    The file is located in the directory sqllib, in the home directory of the account that was used to install Portal Infranet for DB2, for example, /home/db2instl/sqllib.

    Copy the file connector_manager_Portal from $ProductDir/connectors/Portal to $ProductDir/connectors/bin.

  3. Change the directory to $ProductDir/connectors/Portal. In the file start_Portal.sh, change the following line:

    PORTAL_HOME=/opt/portal/6.1

    to an appropriate value:

    PORTAL_HOME=PortalInfranet_home_dir

    Example:

    /opt/portal/6.2

  4. Log off cwadmin.

As user "pin"

  1. Log in to the AIX system as pin.
  2. Copy the Infranet files pcm.jar and pcmext.jar into $ProductDir/connectors/Portal/dependencies. These files are located in the $INFRANET/jars directory of the Infranet server.
  3. Copy the file custom_opcode.h to $INFRANET/include.
  4. Copy the files custom_opcode_mem_map to $INFRANET/lib.
  5. Copy the .profile file into pin's home directory, for example, /home/pin. If necessary, modify the .profile file to reflect the environment variables set in your system. Make any changes using a text editor such as vi. When the environment variables are correct, load them into the system by typing the following command at the command prompt:

    ../.profile

  6. Copy the file fm_crossworlds.so to the $INFRANET/lib directory. This file contains the triggers for the events.

    Note:
    AIX is case-sensitive, so if the files are not found, verify that all directory and file names have the proper case.

    Make sure that the $LIBRARY_PATH variable contains the $INFRANET/lib path so that the system can recognize the .so files.

  7. Make sure that the $LIBRARY_PATH variable contains the $INFRANET/lib path so that the system can recognize the .so files.
  8. Copy the following files into the directory $CW_PORTAL_PATH, for example, /opt/portal/6.2/sys/cm:

  9. Place the pin_notify_cw file in the $INFRANET/sys/test directory. This file contains the names of the connector events. If any events need to be added or deleted, follow the standard format of the file. Note that /event encapsulates all subclasses, such as /event/customer and /event/status.

Configuring Portal Infranet application in an AIX/DB2 environment

If you are using DB2 as your database and AIX as your operation system, follow these instructions to configure the Portal Infranet application:

  1. Stop and restart the Infranet application. Make sure that $INFRANET/bin is in the $PATH variable. Follow these steps:
    1. Stop Infranet with this command:

      stop_all

    2. Check that all Infranet processes are stopped by typing the following command. Note the process numbers (PID) of any running Infranet processes.

      ps -ef | grep protal

    3. Kill any running Infranet processes with this command:

      kill -9 PID

    4. Restart Infranet with the following command:

      start_all

  2. In the $CM directory, add the following line to the pin.conf file in the fm_required section:

    -cm fm_module $INFRANET/lib/fm_crossworlds.so fm_cw_config -pin

    Be sure to type the full directory path for $INFRANET.

  3. Verify that Infranet is running by entering the following command:

    ps -ef | grep portal

  4. Change the directory to $INFRANET/sys/test, open the pin.conf file, and check that the file has a line similar to the following:

    nap_cm_ptr ip Infranet_cm_machine cm_port
    

    Example:

    nap_cm_ptr ip roadrunner 11960

    where roadruner is Infranet_cm_machine and 11960 is cm_port

  5. Verify that the pin.conf file includes:
  6. nap login_type 1 nap login_name root.0.0.0.1 nap login_pw password

    This identifies the login information for connection to Infranet. If there is no pin.conf file in the directory, copy one onto the directory.

  7. Load configuration information into the Infranet application by entering the command:

    load_pin_notify pin_notify_cw

    The response should read successful. If another response is shown, check pin_notify_cw. This file contains the opcodes that Infranet calls when specific events occur. Note that pin_notify_cw should be located in the same directory as the load_pin_notify executable.

  8. In the $INFRANET_VAR/cm directory, check the log file and verify that there is a core in the $CM, for example, cm started at "Tue Jul 9 20:49:37 2002" in cm.pinlog. Start up the Infranet Administrator.
  9. To test the connector, enter or modify an account and check the event table xworlds_events for the proper event entry. Because this results in a dummy event, delete the event entry after testing is complete.

Configuring the connector in an Oracle environment

If you are using Oracle as your database, follow these instructions to configure the connector:

  1. Log into the UNIX system as pin. Create this account if necessary.
  2. Copy the Infranet files pcm.jar and pcmext.jar into $ProductDir/Connector/Portal/dependencies. This file is located in the infranet/jars directory on the Infranet 6.1.0 server.
  3. Copy the .profile file into the pin user's home directory, for example /home/pin. If necessary, modify the .profile file to reflect the environment variables set in your system. Make any changes using a text editor such as vi.

    When the environment variables are correct, load the environment variables into the system by typing the following command at the command prompt:

    source .profile
    
  4. Place the following files in the $INFRANET/lib directory:

    Note that UNIX is case sensitive, so if the files are not found, verify that all directory and file names have the proper case.

  5. Make sure that the $LIBRARY_PATH variable contains the $INFRANET/lib path so that the system can recognize the connector.so files.
  6. Copy the following files into the directory $CW_PORTAL_PATH.
  7. Place the pin_notify_cw in the $INFRANET/sys/test directory. This file contains the names of the connector events. If any events need to be added or deleted, follow the standard format of the file. Note that /event encapsulates all subclasses, such as /event/customer, /event/status.
  8. Stop and restart the Infranet application. Make sure that $INFRANET/bin is in the $PATH variable. Follow these steps:
    1. Stop Infranet with this command:
          stop_all
      
    2. Check that all Infranet processes are stopped by typing the following command. Note the process numbers (PID) of any running Infranet processes.
      ps -ef|grep portal
      
    3. Kill any running Infranet processes with this command:
      kill -9 <PID>
      
    4. Restart Infranet with the following command:
             start_all    
      
  9. In the $CM directory, edit the file pin.conf to add the following line in the fm_required section. Be sure to type the full directory path for $INFRANET.
        - cm fm_module $INFRANET/lib/fm_crossworlds.so fm_cw_config -pin 
    
  10. Verify that Infranet is running by entering the command ps -ef|grep portal.
  11. Change directory to $INFRANET/sys/test, open the pin.conf file, and check that the file has a line similar to the following.
    - nap cm ptr ip Infranet_cm_machine cm_port
    

    For example:

    - nap cm ptr ip roadrunner 11960 
    

    where roadrunner is Infranet_cm_machine and cm_port is 11960.

    In addition to the above statement, the pin.conf file should include:

    - nap login_type 1 
    - nap login_name root.0.0.0.1
    - nap login_pw password 
    

    This identifies the login information for a connection to Infranet. If there is no pin.conf file in the directory, copy one into the directory.

  12. To load configuration information into the Infranet application, enter the command:
        load_pin_notify pin_notify_cw
    

    The response should read successful. If another response is shown, check the pin_notify_cw. This file contains the opcodes that Infranet will call when specific events occur. Note that pin_notify_cw should be located in the same directory as the load_pin_notify executable.

  13. In the $INFRANET_VAR/cm directory, check the log file and verify that there is a core in the $CM and then start up the Infranet Administrator.
  14. To test the connector, enter or modify an account and check the event table xworlds_events for the proper event entry. Since this results in a dummy event, the event entry needs to be deleted once testing is complete.

To start the connector, see "Connector startup".

Copyright IBM Corp. 1997, 2003