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.