Set up and configuration of the event notification mechanism for the iSoft
connector requires completion of the following tasks:
- In the connector configuration property InputQueue, add the names of the
queues that the connector will poll. For example, assuming that you
have set up a queue named "b_to_a" for delivering data document messages from
Commerce Server to your integration broker, and that you have set up queues
named "mdns" and "notifications." The connector will poll these
queues; you add the names of the queues in the InputQueue property as
follows:
b_to_a;mdns;notifications
- Create a static meta-object that defines the business objects that the
connector will receive, the queues from which they will be taken, and the
data-handlers that will process the business objects from each queue.
For each business object defined in the meta-object, specify values for the
DataHandlerMimeType, the InputQueue, and the InputFormat. If any one of
these values is not specified for a given business object, the connector will
use the default data handler (as specified in the standard connector
configuration properties) to process that business object.
In general, all business objects that will be published as events (this
includes MDN's, notifications, and any documents to be received from
trading partners) should be defined in this static meta-object.
- Note:
- In this meta-object, you must specify every possible business object that the
connector might need to convert from the messages that will appear in the
specified queue. If the data handler attempts to convert a message to a
business object that is not specified in this meta-object, the connector will
fail.
For more information on defining and using a static meta-object, see Configuring connector meta-objects "Meta Object Attributes Configuration" later in this
guide.
- Create a data-handler configuration meta-object for mapping of
data-handler mime-types ("text/xml", "text/mdn", etc.) to actual
data-handler classes. See the Data Handler Guide for structure and
syntax. In the adapter configuration properties, set the value of
DataHandlerConfigMO to the name of this meta-object.
- For all business objects that will be published as events, you can
optionally include a dynamic meta-object containing an
attribute--InputQueue--that tells the integration broker the name of
the queue from which the event was retrieved. Depending on the
configuration of Commerce Server, the name of the queue can provide
information about the origin or purpose of the message. The value of
the InputQueue attribute is populated when the connector publishes the
event.
In addition to the above elements, your implementation should include
collaborations (for the ICS integration broker) or message flows (for a WMQI
integration broker) that subscribe to the business objects that will be
published by the adapter.
