Connectors have two types of configuration properties: standard configuration properties and connector-specific configuration properties. You must set the values of these properties before running the connector. As you enter the configuration values, they are saved in the repository.
To configure the connector properties, use one of the following tools:
For more information about Connector Configurator, see Appendix B, Connector Configurator.
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. Changes to some connector configuration properties, such as AgentTraceLevel, are dynamic, taking effect immediately. Changes to other connector properties are static, requiring component restart or system restart after a change. To determine whether a property is dynamic or static, refer to the update method column in Connector Configurator.
Standard configuration properties provide information that all connectors use. For detailed information about these properties, see Appendix A, Standard configuration properties for connectors.
Connector-specific configuration properties provide information needed by the connector at run time. They also provide a way of changing static information or logic within the connector without having to recode and rebuild it.
The following table lists the connector-specific configuration properties
for the connector. These properties are required. For
explanations of the properties, see the sections that follow.
Name | Description | Default value |
---|---|---|
ApplicationPassword | Password for the connector's user account | none |
ApplicationUserName | Name of the connector's user account | none |
BOSupportMode | Flag indicating business object categories supported; possible values are: generic, message-specific, and mixed | mixed |
ConsumeMO | Name of the metaobject used for performing the CONSUME-stored procedure call for request processing. | none |
DatabaseURL | URL of the Retek database | none |
JDBCDriver | Name of the JDBC driver class |
oracle. jdbc.driver. OracleDriver
|
KeyMO | Name of the metaobject that allows the user to configure the primary key for Retek generic business objects, for event sequencing purposes. | none |
MaxDBCConnections | Maximum number of database connections in the connection pool | 100 |
MaxRetries | Maximum number of times the connector will retry to retrieve and process an event | 3 |
ThreadMetaObjects | List of names of the metadata objects for the polling threads | none |
XMLDataHandler | Class name for the XML data handler used to process the payload | com.cross worlds.DataHandlers. text.xml |
XMLDataHandlerMO | Name of the metaobject for the XML data handler | MO_Data
Handler_ Default XMLConfig |
Password for the connector's user account in the Retek application. It is used to connect to the database.
There is no default value.
Name of the connector's user account in the Retek application. It is the ID used to connect to the database.
There is no default value.
Flag indicating business object categories supported.
Possible values are:
The default value is mixed.
Name of the metaobject used for performing the CONSUME-stored procedure call for request processing. Leave it blank if no extra parameters are required for the CONSUME call specific to this application.
There is no default value.
Name of the database server to connect to, in the following format:
protocol:subprotocol:DatabaseServerName:database:port#
There is no default value.
Name of the JDBC driver class.
The default value is jdbc.driver.OracleDriver.
Name of the metaobject that allows the user to configure the primary key for Retek generic business objects, for event sequencing purposes.
There is no default value.
Maximum number of database connections in the connection pool.
The default value is 100.
Maximum number of times the connector will retry to retrieve and process an event.
The default value is 3.
List of names of the metadata objects for the polling threads. You can leave it blank for an instance that only performs request processing.
There is no default value.
Class name for the XML data handler used to process the payload.
The default value is com.crossworlds.DataHandlers.text.xml.
Name of the metaobject for the XML data handler.