Configuring the connector

Adapters have two types of configuration properties: standard configuration properties and adapter-specific configuration properties. You must set the values of some of these properties before running the connector.

You configure connector properties from Connector Configurator (when WebSphere MQ Integrator Broker is the integration broker) or from Connector Configurator, which is accessed from System Manager (when ICS is the integration broker). For detailed configuration information, see Appendix B, Using Connector Configurator or the Connector Development Guide for Java.

Standard connector properties

Standard configuration properties provide information that all connectors use. See Appendix A, Standard configuration properties for connectors for documentation of these properties.

Important:
Because this connector supports all integration brokers, configuration properties for all brokers are relevant to it.
Note:
Because this connector is single-threaded, it cannot take advantage of the AgentConnections property.

Table 2 provides information specific to this connector about configuration properties in the appendix.


Table 2. Property Information Specific to This Connector

Property Note
CharacterEncoding This connector does not use this property.
Locale Because the connector has been internationalized, you can change the value of this property. See release notes for the connector to determine currently supported locales.

Important:
WebSphere MQ Integrator Broker does not support multiple locales. Ensure that every component of your installation (for example, all adapters, applications, and the integration broker itself), are set to the same locale.
Note:
The Portal Infranet adapter supports the DuplicateEventElimination property. To enable the DuplicateEventElimination property, set the DuplicateEventElimination atribute to true.For more details about the DuplicateEventElimination properyt, see Appendix A, Standard configuration properties for connectors.
Note:
Because this connector supports all integration brokers, configuration properties for all brokers are relevant to it.

Connector-specific properties

Connector-specific configuration properties provide information needed by the connector at runtime. Connector-specific properties also provide a way of changing static information or logic within the connector without having to recode and rebuild the connector.

Table 3 lists the connector-specific configuration properties for the connector. See the sections that follow for explanations of the properties.

Table 3. Connector-specific configuration properties

Name Possible values Default value Required
Application password Password of user account
Yes
ApplicationUserName Name of user account
Yes
CommentFail Event table comment for failed events Fail No
CommentSucceed Event table comment for successful events Succeed No
DatabaseInfo jdbc:oracle:thin@ CWENGTEST:1521:
portaldb
Server-host name, Portal database port number, and the name of the database. Yes
DbName Oracle Listener name
Yes
DbPassword Database password
Yes
DbUser Database user name pin Yes
DriverClass Driver class name of the database
No
InfDatabase String 0.0.0.1 Yes
InfHost Host machine name and port //CWENGTEST1:11960 Yes
InfLogFile Name of log file InfConnection.txt Yes
InfranetConnections Number of Infranet connections the connector opens for connection pooling 5 Yes
InfService String service\admin_client 1 Yes
InfType 0 or 1 1 Yes
InfVersion Version of the Infranet application
Yes
PollQuantity Number of events to pick up 1 No
UseDefaults true or false false No

Application password

Password for WebSphere business integration system user account.

ApplicationUserName

Name of the user account for the connector.

CommentFail

Event table comment in case of a fail. Default value is Fail.

CommentSucceed

Event table comment in case of a success. Default value is Succeed.

DatabaseInfo

This property defines the URL that would be used by the JDBC driver to make a connection to the database.

Example:

jdbc:oracle:thin:@CWENGTEST1:1521:portaldb

Please refer to the JDBC documentation for specific formats of the URL

DbName

Oracle Listener name for the Infranet database.

DbPassword

Database password.

DriverClass

Driver class name of the database.

For Oracle set:

oracle.jdbc.driver.OracleDriver

For db2 set: COM.ibm.db2.jdbc.app.DB2Driver if the DB2 database is on the same machine that the connector is going to run. UseCOM.ibm.db2.jdbc.net.DB2Driver if the DB2 database and connector are on different machines.

If the DriverClass is not set, the adapter uses oracle.jdbc.driver.OracleDriver as the default value.

DbUser

Database user name, usually pin.

InfDatabase

String in Infranet form. The default value is 0.0.0.1.

InfHost

Host machine name and port, for example, //engtest2:11960. The default value is //CWENGTEST1:11960.

InfLogFile

Name of file to use as default log. The default value is InfConnection.txt.

InfranetConnections

This property is used to define the number of connections the connector opens with the Infranet application for connection pooling. The connector maintains the assigned number of connections. When a business object process requires a connection, it allocates one from the pool. That connection is then removed from the available pool and added to the busy pool. When the business object process is complete, the connection is removed from the busy pool and added back to the available pool. Using connection pooling in this way increases efficiency in performance because the connection does not need to be opened and closed for each business process.

Note:
If this property is not set, the connector will throw the following exception when the connector is started: NumberFormatException

InfService

String, usually service\admin_client 1. This is the default value.

InfType

Connection type. The only possible values are 0 or 1. The default value is 1.

InfVersion

Version of the Infranet application.

PollQuantity

Number of event picked up in a single poll. Default value is 1.

UseDefaults

If UseDefaults is set to true or not set, the connector checks whether a valid value or a default value is provided for each isRequired business object attribute. If a value is provided, the Create succeeds; otherwise, it fails.

If the parameter is set to false, the connector checks only for valid values; the Create operation fails if valid values are not provided.

The default value is false.

Copyright IBM Corp. 1997, 2004