Connector configuration properties

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 Express 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 Express.

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.

Note:
When you set configuration properties in Connector Configurator Express, you specify your broker using the BrokerType property. Once this is set, the properties relevant to your broker will appear in the Connector Configurator Express window.

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 agent.

The table below lists the connector-specific configuration properties for the connector. See the sections that follow for explanations of the properties.

You must provide a value for the ApplicationName configuration property before running the connector.
Name Possible values Default value Required
ArchiveQueue Queue to which copies of successfully processed messages are sent queue://isoft. queuemanager/ISOFT.ARCHIVE No
CCSID Character set for queue manager connection null No
Channel MQ server connector channel
Yes
ConfigurationMetaObject Name of configuration meta-object
Yes
DataHandlerClassName Data handler class name com.isoft.DataHandlers. text.xml No
DataHandlerConfigMO Data handler meta-object MO_DataHandler_ Default Yes
DataHandlerMimeType MIME type of file text/xml No
DefaultVerb Any verb supported by the connector. Create
ErrorQueue Queue for unprocessed messages queue://isoft. queuemanager/ISOFT.ERROR No
HostName WebSphere MQ server
Yes
InDoubtEvents FailOnStartup Reprocess IgnoreLogError Reprocess No
InputQueue Poll queues queue://isoft. queuemanager/ISOFT.IN No
InProgressQueue In-progress event queue queue://isoft. queuemanager/ISOFT.IN_PROGRESS No
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
UnsubscribedQueue Queue to which unsubscribed messages are sent queue://isoft. queuemanager/ISOFT.UNSUBSCRIBE No
UseDefaults true or false false

ArchiveQueue

Queue to which copies of successfully processed messages are sent.

Default = queue://isoft.queue.manager/ISOFT.ARCHIVE

CCSID

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.

Channel

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.*

ConfigurationMetaObject

Name of static meta-object containing configuration information for the connector.

Default = none.

DataHandlerClassName

Data handler class to use when converting messages to and from business objects.

Default = com.isoft.DataHandlers.text.xml

DataHandlerConfigMO

Meta-object passed to data handler to provide configuration information.

Default = MO_DataHandler_Default

DataHandlerMimeType

Allows you to request a data handler based on a particular MIME type.

Default = text/xml

DefaultVerb

Specifies the verb to be set within an incoming business object, if it has not been set by the data handler during polling.

Default= Create

ErrorQueue

Queue to which messages that could not be processed are sent.

Default = queue://isoft.queue.manager/ISOFT.ERROR

HostName

The name of the server running WebSphere MQ.

Default = none.

InDoubtEvents

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.

InputQueue

Message queues that will be 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 will start up properly, print a warning message, and perform request processing only. It will perform 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 pollQuanity of 2, the connector will retrieve 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 pollQuanity 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:

  1. 1 message from MyQueueA
  2. 1 message from MyQueueB
  3. 1 message from MyQueueC
  4. 1 message from MyQueueA
  5. Skip MyQueueB since it's now empty
  6. 1 message from MyQueueC

Default = queue://isoft.queue.manager/ISOFT.IN

InProgressQueue

Message queue where messages are held during processing. You can configure the connector to operate without this queue by using CSM to remove the default InProgressQueue name from the connector-specific properties. Doing so prompts a warning at startup that event delivery may be compromised if the connector is shut down while are events pending.

Default= queue://isoft.queue.manager/ISOFT.IN_PROGRESS

PollQuantity

Number of messages to retrieve from each queue specified in the InputQueue property during a pollForEvents scan.

Default =1

Port

Port established for the WebSphere MQ listener.

Default = None.

UnsubscribedQueue

Queue to which messages that are not subscribed are sent.

Default = queue://isoft.queue.manager/ISOFT.UNSUBSCRIBED

Note:
*Always check the values WebSphere MQ provides since they may be incorrect or unknown. If so, please implicitly specify values.

UseDefaults

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.

Copyright IBM Corp. 1997, 2003