Installing the connector on a Windows system

The connector files are automatically installed with WebSphere Business Integration Adapter software. After installation, the installation directory %ProductDir%\connectors\Portal contains the following files needed by the connector:

The installation directory %ProductDir%\connectors\Portal\ dependencies\config_files contains the following files:

The installation directory %ProductDir%\connectors\Portal\include contains the following files:

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.

For more information on installing the connector component, refer to one of the following guides, depending on the integration broker you are using:

or the instructions in the sectionComprehensive install and uninstall instructions for adapters.

Installing and configuring the event mechanism

Infranet has an event mechanism that permits it to keep track of the actions that occur in the application. You must configure the event notification mechanism in Infranet before the connector can process event delivery. Follow these steps:

  1. Copy the following WebSphere Business Integration Adapter event module files:
  2. In %INFRANET%\sys\cm, edit the Connection Manager pin.conf configuration file so that the Connection Manager can execute the connector event facilities DLL, FmCw.dll. Add the following line to this file:

    - cm fm_module ..\..\lib\FmCw.dll fm_cw_pol_config_func - pin -- ops_fields_extension_file ..\..\lib\custom_opcode_mem_map

  3. Place the pin_notify_cw file in the %INFRANET%\sys\test directory. This file specifies which opcodes Infranet will call when specific events are raised. If any opcodes 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.
  4. Update the pin.conf file in %INFRANET%\sys\test to be something like the following:
    - nap cm ptr ip <Infranet_cm_machine> <port>
    

    For example:

    - nap cm ptr ip cwengtest 11960 
    

    where cwengtest is <Infranet_cm_machine> and <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.

  5. Copy the crossworlds.cnf environment configuration file to %INFRANET%\sys\cm. This file allows the event facilities module FmCw.dll to obtain information about the environment.

    If necessary, edit this file for your system. An example of the content for this file is:

    db user = pin 
    db password = pin 
    crossworlds id = 0.0.0.1 \service\admin_client 14088 
    log level = 3 
    log file = D:\pinlog.log
    

    where:

    db user Name of the user connecting to the Portal Infranet database.
    db password Password.
    crossworlds id POID representing the WebSphere Business Integration Adapter user in Portal Infranet.
    log level Number representing the log level:

    0 : No trace

    1 : Only Error

    2 : Error and Warning

    3 : Error, Warning, and Debug (all traces)

    log file Name of the log file.

    This file is interpreted as a hash table. The keywords are strings on the left of the equal sign, and the values are the strings on the right.

  6. Create an environment variable named CW_PORTAL_PATH that specifies the path to the crossworlds.cnf file.
  7. Restart Infranet services in this order:
  8. Load the pin_notify_cw file into the Infranet application using the following syntax:
    load_pin_notify .\pin_notify_cw 
    

    If errors occur, make sure that \bin directory is in the PATH so that the executable can be located. For error messages, check the pinlog.log in the execution directory.

Copyright IBM Corp. 1997, 2003