Setting up the .ini file

The Gateway Event names are not hardcoded in the MetaSolv application, therefore CwGatewayServer uses an .ini file to determine which Business Object to retrieve based on the Gateway Event Name. You must create a text file with the .ini extension. This file must reflect the Gateway Event names in your MetaSolv application. The Gateway Event names must be linked to triggering tasks in the MetaSolv application. Changes to the names of Gateway Events in the MetaSolv Client also impact the Gateway Server.

Except the created events SendBillOrd and SendBillCust, any custom event names must use the following format in MetaSolv:

<MSLV Object Name>_<Verb Name>_ <Comment>

Where MSLV_Object_Name is the MetaSolv object name. The Verb_Name could be either Create of Update. Finally, Comment can be any string.

Note:
The .ini file is not required for the PSR Billing Gateway.

The format of entries in the .ini file is <Gateway_Event_Name><tab><Business_Object_Name>. For example:

PSR_CREATE_DD     MetaSolv_ServiceRequest

Testing the Gateway server

Use the following procedure to test the Gateway Server:

  1. Start the CwPSRGatewayServer, CwDLRGatewayServer, CwLSRGatewayServer, or the CwPSRBillingGateway server by running the runcwPSRgatewayserver.bat, runcwDLRgatewayserver.bat, runcwLSRgatewayserver.bat, and runcwpsrbillinggatewayserver.bat file on the MetaSolv Application Server machine.
  2. From the MetaSolv Client, send a Gateway Event that is registered with the server. If the Gateway Server is able to extract the event information and insert the event into the event table, a status of complete is sent.

Copyright IBM Corp. 1997, 2004