Connectors have two types of configuration properties: standard configuration properties and connector-specific configuration properties. You must set the values of some of these properties before running the connector.
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, take effect immediately. Changes to other connector properties require component restart or system restart after a change. To determine whether a property is dynamic (taking effect immediately) or static (requiring either connector component restart or system restart), refer to your integration broker's administration utility. For instance, if you are using WebSphere InterChange Server, see the Update Method column in the Connector Properties window of the System Manager.
If you are using WebSphere MQ Integrator Broker as the integration broker, you configure connector properties from the Connector Configurator. If you are using WebSphere InterChange Server as the integration broker, you configure connector properties from Connector Designer, which you access from System Manager.
Standard configuration properties provide information that all connectors use. See Appendix A, Standard configuration properties for connectors for documentation of these properties.
Adapter-specific configuration properties provide information needed by the connector at run time. Adapter-specific properties also provide a way of changing static information or logic within the connector agent without having to recode and rebuild the agent.
Table 3 lists the adapter-specific configuration properties for the
connector. See the sections that follow for explanations of the
properties.
Table 3. Adapter-specific configuration properties
Name | Possible values | Default value | Required |
---|---|---|---|
ArchiveProcessed | true/false |
true |
|
ArchiveTableName | Name of archive table |
xworlds_archive_events |
|
DatabaseURL |
metasolv:weblogic:oci:metasolv | No default value | Yes |
EventDBBrand | JDBC driver database type | Oracle |
|
EventDBPassword | Event database password | oracle |
|
EventDBUsername | Login to event database username | internal |
|
EventTableName | Name of event table | xworlds_events |
|
JDBCDriverClass | Specifies the class name of the driver weblogic.jdbc.oci.Driver | No default value | Yes |
MaxEvents | Number of events per poll | 25 |
|
MSLVPassword | MetaSolv server password | asap |
|
MSLVPSRIORfile | The API uses IOR files to route events to/from the MetaSolv application | H:\PSRSERVER.ior |
|
MSLVUserName | Username for MetaSolv server | asap | No |
ORB.<property name> | The ORB vendor specific properties that would be used by the connector to initialize the ORB. | com.inprise.vbroker.orb.ORB | Yes |
Specifies whether the connector archives events for which there are no current subscriptions. Set this property to true to cause events to be inserted into the archive table after they are deleted from the event table.
Name of the archive table. The default value is xworlds_archive_events.
URL String for accessing the WebSphere business-integration system's database. There is no default value. URL should follow the Oracle thin driver's format as the default driver is Oracle thin driver.
Database type for the JDBC Driver. The default value is Oracle.
Password for the login into the event table database. The default value is asap.
User name for the login into the event table database. The default value is asap.
Name of event queue table. The default value is xworlds_events.
Class name of the JDBC driver. Use to connect to the database where event and archive tables reside.
Maximum number of event processes during one poll. The default value is 25.
Password for the login into the MetaSolv server. The default value is asap.
Path to the PSR Server's IOR file.
Username for the login into the MetaSolv server. The default value is asap.
The ORB vendor specific properties that would be used by the connector to initialize the ORB. E.g. the property org.omg.CORBA .ORBClass would be named as "ORB. org.omg.CORBA.ORBClass". The number and names of such properties would depend on the ORB specific vendor. All the properties that start with "ORB." will be treated by the connector as orb properties and would be used in ORB initialization.