Configuring the adapter

The connector component of the adapter has two types of configuration properties: standard configuration properties and application-specific configuration properties. You must set the values of these properties before running the connector.

Standard configuration properties

To configure standard connector properties, use the Connector Configurator tool. Details are given in Appendix C, "Connector Configurator".. This tool provides a graphical user interface for configuring the connector. Click on 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 saves the values in the adapter repository (for ICS) or generates a configuration file and places it in the adapter's local repository (for WebSphere MQ Integrator Broker or WebSphere Application Server).

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.

Application-specific configuration properties

Application-specific connector configuration properties provide information 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. Click the Application Config Properties tab to add or modify configuration properties. For more information, see Appendix C, "Connector Configurator". .

Table 8 lists the application-specific configuration properties for the connector, along with their descriptions and possible values.


Table 8. Application-specific configuration properties for Ariba Buyer

Property Description Possible values Default value Required
Nodes The Ariba Buyer node
names and fully qualified
machine names
<url1>:Node1;
<url2>:Node2;...
<urln>:NodeN
None Yes
ConnectorPort The connector RMI port Any open port - must
match the value specified in
the Parameters.table file
2226 Yes
ChannelPort The channel RMI port Any open port - must
match the value specified in
the Parameters.table file
2225 Yes
DateFormats Specifies valid date formats.
For more details, see
"DateFormat" below.
<format>;<format>;... EEE MMM dd
HH:mm:ss z
yyyy;M/d/yy;
M/d/yyyy;
M-d-yy;
M-d yyyy;
yyyyMMdd
No





VariantMappings Correlates user-defined
variant names with specific
ERP types. Maps variant
and partition-specific
business object names to a
more generic business
object name.
<variant name>=<variant
type prefix>;<variant
name>=<variant type
prefix>;...
None No
BOLocale Specifies the locale of a
business object. For more
details, see "BOLocale"
below.
Any valid locale specification;
for example, en_US, ja_JP,
or de_DE.


If a given value is invalid,
the system default locale
is used.

None No

DateFormat
For more information on valid date formats, which are determined by the Java API, see the website http://java.sun.com/j2se/1.3/docs/api/java/text/SimpleDateFormat.html

BOLocale
This is a hierarchical property, which you can use as follows:

Copyright IBM Corp. 1997, 2003