The integration channel must be configured for two purposes:
The integration channel configuration properties provide the information necessary for the channel to communicate with the connector at run time. These properties are set in the Parameters.table text file, located in the Ariba Buyer installation directory:
\Ariba\app\Buyer\Server\config
To configure the integration channel properties, open the Parameters.table file and enter the property values.
Table 9 lists the required configuration properties, along with a
description and possible value for each one.
Table 9. Application-specific configuration properties for the integration channel
Property | Description | Possible values | Default value | Required |
---|---|---|---|---|
ConnectorURL |
The hostname of the machine on which the connector is running |
Fully qualified machine name or IP address | localhost | Yes |
ConnectorPort | The connector RMI port |
Any open port - must match the value set for the connector | 2226 | Yes |
ChannelPort | The channel RMI port |
Any open port - must match the value set for the connector | 2225 | Yes |
MetadataRepos |
The location where generated meta-data will be stored |
Relative from \Ariba\app\Buyer\Server or a fully qualified directory path |
"/channels/ IBM/metadata"; | Yes |
Each integration event must be configured before it can be sent through the integration channel. Events are configured in two configuration files, MessageDefinition.table and MessageConfiguration.table.
Ariba Buyer supplies a number of out-of-the-box integration events, which are listed in the Ariba Buyer Configuration Reference Guide. However, events that are not configured on the integration channel will not be sent through the adapter for Ariba Buyer.
The MessageDefinition.table file contains general information for each integration event in a given ERP variant type. Ariba Buyer supplies a table entry for a base set of out-of-the-box integration events for each of these variants.
The MessageConfiguration.table file contains more specific information, including channel-specific data, for each integration event in a given partition. An entry for each event must be created in this table.
A sample MessageConfiguration.table entry is shown below.
PurchaseOrderPush={ Channel={ Name=IBM; Operation="Update Elements Only"; Verb=Retrieve; Timeout=300000; }; LoggingName=PurchaseOrderEvent; MessageParameters={ Request={ MergedSchemaName="ariba.integration.param.PurchaseOrderPush"; Parameters={EventSource="ibmcsvp:PO:SAP3.1H";}; SchemaName=ariba.integration.param.SimpleParams; }; }; TopicName=PurchaseOrderPush; ExecutionNode="Node2"; };
Every MessageConfiguration.table entry contains a section for
channel parameters, shown as the first subentry in the example above. Table 10 lists the valid parameters and values for the integration
channel.
Table 10. Event configuration parameters for the integration channel
Parameter | Description | Possible values |
---|---|---|
Name | Specifies the ERP integration channel name. | IBM |
Operation |
Specifies the operations that Ariba Buyer can perform. Refer to "Business object verbs" for more details. |
Create, Delete, Load, "Load And Delete", Update, "Update And Delete", "Update Elements Only" |
Verb |
Specifies the operations that the destination application can perform. Refer to "Business object verbs" for more details. |
Create, Delete, Retrieve, Update ABUpdate, Load, Update_And_Delete, Update_Elements_Only |
Timeout |
Specifies the timeout for an Ariba Buyer event process. The value is designated in milliseconds. |
Whole number >=0 Default value is 0, which means no timeout for that event. |
EventSource |
Uniquely identifies data associated with this event. This parameter is required only for Subscribe events. |
Any string value; maximum length 50 characters. Must be unique for each partition, and may not be changed between integration events. |
For complete details on configuring the other parameters for integration events, refer to the Ariba Buyer Configuration Reference Guide.