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:
Note that %INFRANET% is in the Infranet home directory.
- cm fm_module ..\..\lib\FmCw.dll fm_cw_pol_config_func - pin -- ops_fields_extension_file ..\..\lib\custom_opcode_mem_map
- 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.
If necessary, edit this file for your system. An example of the content for this file is:
db name = oracle1 db string = NYNON 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 name | For DB2, db_name is the server-name or a host-variable which contains the server name. For Oracle, db_nameis the host variable. |
db string | Name of database. (It is only reguired if you are uisng Oracle as your database. |
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.
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.