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:
- cwportal.jar
- .profile
- Files for the event notification mechanism:
fm_crossworlds.so,
event_code.txt, crossworlds.cnf, and
pin_notify_cw
- Startup script for the UNIX version of the connector:
start_Portal.sh
- Note:
- The startup script for the Portal Infranet adapter is called from the generic
connector manager script. When you click Install from the Connector
Configurator (WebSphere MQ Integrator Broker as the integration broker), or
the Connector Configuration screen of System Manager (ICS as the integration
broker), the Installer creates a customized wrapper for this
connector manager script. When the connector works with ICS, use this
customized wrapper to start and stop the connector. When the connector
works with WebSphere MQ Integrator Broker, use this customized wrapper only to
start the connector; use mqsiremotestopadapter to stop the
connector.
- The $ProductDir/connectors/Portal/dependencies
directory contains the following files needed by the connector:
- custom_opcode.h
- custom_opcode_mem_map
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:
To configure the connector on an AIX system, follow these instructions in
order:
- Log in to the AIX system with the DB2 user ID used for the instance for
Portal Infranet, for example, db2instl.
- 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
- 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
- Log off.
- Log in to the AIX system as pin (create a pin user
account if necessary).
- 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.
- Enter the following command:
db2 connect to DB_name user pin using pin
Example:
db2 connect to CWPortal user pin using pin
- Enter the following command:
dbw bind database.bnd
- Enter the following command:
db2 disconnect all
- Add the following line to the .profile file of user
pin:
export DB2DBDFT=DB_name
Example:
export DB2DBDFT=CWPortal
- Log off pin.
- Log in to the AIX system as user cwadmin, which is used to
start up the connector.
- 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.
- 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
- Log off cwadmin.
- Log in to the AIX system as pin.
- 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.
- Copy the file custom_opcode.h to
$INFRANET/include.
- Copy the files custom_opcode_mem_map to
$INFRANET/lib.
- 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
- 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.
- Make sure that the $LIBRARY_PATH variable contains the
$INFRANET/lib path so that the system can recognize the
.so files.
- Copy the following files into the directory $CW_PORTAL_PATH,
for example, /opt/portal/6.2/sys/cm:
- crossworlds.cnf -- This file contains configuration
information for the event module.
- event_code.txt -- This file contains descriptions of
Infranet events that the event module uses to generate entries in the
WebSphere business integration system event table.
- 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.
If you are using DB2 as your database and AIX as your operation system,
follow these instructions to configure the Portal Infranet application:
- Stop and restart the Infranet application. Make sure that
$INFRANET/bin is in the $PATH variable. Follow
these steps:
- Stop Infranet with this command:
stop_all
- 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
- Kill any running Infranet processes with this command:
kill -9 PID
- Restart Infranet with the following command:
start_all
- 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.
- Verify that Infranet is running by entering the following command:
ps -ef | grep portal
- 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
- Verify that the pin.conf file includes:
- 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.
- 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.
- 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.
- 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.
If you are using Oracle as your database, follow these instructions to
configure the connector:
- Log into the UNIX system as pin. Create this account if
necessary.
- 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.
- 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
- Place the following files in the $INFRANET/lib directory:
- fm_crossworlds.so. This file contains the
triggers for the events.
- libdatabase.so. This file facilitates database
connection.
- libtrace.so. This is a trace file.
Note that UNIX 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
connector.so files.
- Copy the following files into the directory
$CW_PORTAL_PATH.
- crossworlds.cnf. This file contains configuration
information for the event module.
- event_code.txt. This file contains descriptions
of Infranet events that the event module will use to generate entries in the
WebSphere Business Integration Adapter event table.
- 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.
- Stop and restart the Infranet application. Make sure that
$INFRANET/bin is in the $PATH variable. Follow
these steps:
- Stop Infranet with this command:
stop_all
- 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
- Kill any running Infranet processes with this command:
kill -9 <PID>
- Restart Infranet with the following command:
start_all
- 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
- Verify that Infranet is running by entering the command ps -ef|grep
portal.
- 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.
- 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.
- 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.
- 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".
