Configuring the adapter 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 fm_crossworlds.so file in the $INFRANET/lib directory. . This file contains the triggers for the events.

    Note that UNIX is case sensitive, so if 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_pol_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 Starting the connector.

Copyright IBM Corp. 1997, 2004