After installation and before startup, configure the adapter components as follows.
The JPO triggers require certain configuration properties to be set before they will work. To set these configuration properties, you have to edit the source code for each JPO.
The JPOs installed with the adapter for eMatrix are WBIEventLogger and InstallEventTables. After you have installed them, you must locate each JPO in the eMatrix Business Modeler and edit the source code.
The fields that need to be edited are listed below in Table 2.
Property name | Description | Default value |
---|---|---|
wbiPrefix |
The prefix used to provide all WebSphere Business Integration eMatrix meta-entities (types, attributes and policies) with their own namespace within eMatrix. The value specified for wbiPrefix in the connector configuration properties must match the wbiPrefix declared in the InstallEventTables and WBIEventLogger.java files. |
wbi_ |
vault | Name of the eMatrix vault in which new events
will be created.
Must match the value specified for the EventVault connector configuration property. |
WBI_Events |
adapterUser | The ID that the adapter uses when making requests
in the eMatrix
system. Must match the value specified for the ApplicationUserName connector configuration property. Important for preventing the "Ping-pong" effect (see below). |
adapter |
When the adapter modifies an object in the eMatrix system for which a trigger is assigned, that trigger may in turn generate a new event to be published back to the broker. The following mechanism prevents this from happening.
When a JPO is invoked, it receives a Context object that contains, among other things, the userID associated with the user who invoked the JPO. This user ID is set in the JPO property adapterUser. When it is triggered, the WBIEventLogger JPO checks the user ID it receives from the eMatrix Context object.
If the user was the adapter for eMatrix, the value of the JPO's adapterUser property will match the value of the connector's ApplicationUserName property. In this case, the JPO will ignore the event, and it is not logged. If the user IDs do not match, the JPO creates a new event.
The connector component of the adapter has two types of configuration properties: standard configuration properties, which apply to most adapters, and application-specific configuration properties, which apply only to your adapter. You must set the values of these properties before running the connector.
To configure the standard connector properties, use the Connector Configurator Express tool. Details are given in Appendix B. Connector Configurator Express. This tool provides a graphical user interface for configuring the connector. Select the Standard Config Properties tab to add or modify configuration properties.
When you have finished specifying values for the connector's configuration properties, Connector Configurator Express saves the values in the adapter repository for InterChange Server Express.
A connector obtains its configuration values at startup. During a run-time session, you may want to change the values of one or more connector properties.
To determine whether a property is dynamic or static, refer to the update method column in Connector Configurator Express.
Application-specific connector configuration properties provide information related to the application and needed by the connector at run time. They also provide a way for you to change static information or logic within the connector without having to recode and rebuild it.
To configure these properties, use Connector Configurator Express. Select the Application Config Properties tab to add or modify configuration properties. For more information, see Appendix B. Connector Configurator Express.
Table 3 lists the application-specific configuration properties for the connector, along with their descriptions and possible values.