Connectors have two types of configuration properties: standard configuration properties and adapter-specific configuration properties. You must set the values of these properties before running the adapter.
You use Connector Configurator to configure connector properties:
A connector obtains its configuration values at startup. During a runtime 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 the Update Method column in the Connector Properties window of Connector Configurator.
Standard configuration properties provide information that all connectors use. See Appendix A, Standard configuration properties for connectors for documentation of these 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 agent.
Table 10 lists the connector-specific configuration properties for the connector. See the sections that follow for explanations of the properties.
Table 10. Connector-specific configuration properties
Name | Possible values | Default value | Required |
---|---|---|---|
ApplicationPassword | Login password | No | |
ApplicationUserName | Login user ID | No | |
ArchiveQueue | Queue to which copies of successfully processed messages are sent |
queue://crossworlds. queuemanager/MQCONN. ARCHIVE |
No |
CCSID | Character set for queue manager connection | null | No |
Channel | MQ server connector channel | Yes | |
ConfigurationMetaObject | Name of static configuration meta-object | Yes | |
DataHandlerClassName | Data handler class name |
com.crossworlds. DataHandlers.fix. FixDataHandler |
No |
DataHandlerConfigMO | Data handler meta-object |
MO_DataHandler_ Default_FIX |
Yes |
DataHandlerMimeType | MIME type of file |
fix |
No |
ErrorQueue | Queue for unprocessed messages |
queue://crossworlds. queuemanager/MQCONN. ERROR |
No |
HostName | WebSphere MQ server | Yes | |
InDoubtEvents |
FailOnStartup Reprocess Ignore LogError |
Reprocess |
No |
InputQueue | Poll queues |
queue://crossworlds. queuemanager/MQCONN.IN |
No |
InProgressQueue | In-progress event queue |
queue://crossworlds. queuemanager/MQCONN. IN_PROGRESS |
Yes |
PollQuantity | Number of messages to retrieve from each queue specified in the InputQueue property |
1 |
No |
Port | Port established for the WebSphere MQ listener | Yes | |
ReplyToQueue | Queue to which response messages are delivered when the connector issues requests |
queue://crossworlds. queuemanager/MQCONN. REPLYTO |
No |
UnsubscribedQueue | Queue to which unsubscribed messages are sent |
queue://crossworlds. queuemanager/MQCONN. UNSUBSCRIBE |
No |
UseDefaults | true or false | false |
Password used with UserID to log in to WebSphere MQ.
Default = None.
If the ApplicationPassword is left blank or removed, the connector uses the default password provided by WebSphere MQ.*
User ID used with Password to log in to WebSphere MQ.
Default = None.
If the ApplicationUserName is left blank or removed, the connector uses the default user ID provided by WebSphere MQ.*
Queue to which copies of successfully processed messages are sent.
Default = queue://crossworlds.queue.manager/MQCONN.ARCHIVE
The character set for the queue manager connection. The value of this property should match that of the CCSID property in the queue URI; see Queue Uniform Resource Identifiers (URI).
Default = null.
MQ server connector channel through which the connector communicates with WebSphere MQ.
Default = none.
If the Channel is left blank or removed, the connector uses the default server channel provided by WebSphere MQ.*
Name of static meta-object containing configuration information for the connector. For more on static and dynamic meta-objects, see "Meta-object attributes configuration".
Default = none.
Data handler class to use when converting messages to and from business objects.
Default = com.crossworlds.DataHandlers.fix.FixDataHandler
Meta-object passed to data handler to provide configuration information.
Default = MO_DataHandler_Default
Allows you to request a data handler based on a particular MIME type.
Default = fix
Queue to which messages that could not be processed are sent.
Default = queue://crossworlds.queue.manager/MQCONN.ERROR
The name of the server hosting WebSphere MQ.
Default = none.
Specifies how to handle in-progress events that are not fully processed due to unexpected connector shutdown. Choose one of four actions to take if events are found in the in-progress queue during initialization:
Default = Reprocess.
Message queues that are polled by the connector for new messages. The connector accepts multiple semi-colon delimited queue names. For example, to poll the following three queues: MyQueueA, MyQueueB, and MyQueueC, the value for connector configuration property InputQueue would equal: MyQueueA;MyQueueB;MyQueueC.
If the InputQueue property is not supplied, the connector starts up properly, prints a warning message, and performs request processing only. It performs no event processing.
The connector polls the queues in a round-robin manner and retrieves up to pollQuantity number of messages from each queue. For example, if pollQuantity equals 2, and MyQueueA contains 2 messages, MyQueueB contains 1 message and MyQueueC contains 5 messages, the connector retrieves messages in the following manner:
Since we have a pollQuantity of 2, the connector retrieves at most 2 messages from each queue per call to pollForEvents. For the first cycle (1 of 2), the connector retrieves the first message from each of MyQueueA, MyQueueB, and MyQueueC. That completes the first round of polling and if we had a pollQuantity of 1, the connector would stop. Since we have a pollQuantity of 2, the connector starts a second round of polling (2 of 2) and retrieves one message each from MyQueueA and MyQueueC--it skips MqQueueB since it is now empty. After polling all queues 2x each, the call to the method pollForEvents is complete. Here's the sequence of message retrieval:
Default = queue://crossworlds.queue.manager/MQCONN.IN
Message queue where messages are held during processing.
Default= queue://crossworlds.queue.manager/MQCONN.IN_PROGRESS
Number of messages to retrieve from each queue specified in the InputQueue property during a pollForEvents scan.
Default =1
Port established for the WebSphere MQ listener.
Default = None.
Queue to which response messages are delivered when the connector issues requests.
Default = queue://crossworlds.queue.manager/MQCONN.REPLYTO
Queue to which messages that are not subscribed are sent.
Default = queue://crossworlds.queue.manager/MQCONN.UNSUBSCRIBED
On a Create operation, if UseDefaults is set to true, 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 operation succeeds. If the parameter is set to false, the connector checks only for a valid value and causes the Create operation to fail if it is not provided. The default is false.