To install the connector for iSoft, you must perform the tasks described in the sections below.
This task, which includes installing the WebSphere business integration system and starting the integration broker, is described in the installation documentation for your broker and operating system.
This task includes installing the files for the adapter from the software package onto your system. See Installing the connector and related files.
Configuration of iSoft Commerce Suite server is done through an XML configuration file. By default, Commerce Server looks for the file icssvr.cfg in the local directory and executes any commands found inside. An iSoft Commerce Suite server can receive a message from a trading partner and dynamically route it to a queue based various factors, including on the mime type of the message it received. Event notification requires one queue per data format, resulting in fewer defined queues that the connector must poll.
In the following scenario, trading partner B sends an order to trading partner A. The iSoft Commerce Suite server has the ability to route messages to different queues based on a messages MIME type. The scenario uses messages which are created with the MIME type txt/xml. The adroute commands in icssvr.cfg_a route these messages to the COMPA.XML queue. iSoft Commerce Suite server A can also route any messages with a MIME type set to text/plain to COMPA.TXT. You can configure the connector to poll these queues and configure data handlers to process the MQ messages on a per queue basis. An XML data handler could process all messages in a specific XML queue, COMPA.XML, for instance, or a delimited data handler could be configured to process all messages in a text queue, like COMPA.TXT. Use the following commands in the icssvr.cfg file.
Following is a sample configuration file, with comments (the comments, indicated by /* in the sample, are for explanation in this document only; do not include comments in your actual configuration file).
The sample makes the following assumptions:
<xml>
<command>set -cnBT1</command>
<command>set -bhmq://wbia.queue.manager</command>
/* Configures Commerce Server to put all notifications in queue 'notifications'*/
<command>set -npmq://wbia.queue.manager/notifications -nf -ntW</command>
/* Configures Commerce Server to put all MDNs in queue 'mdns'*/
<command>set -rpmq://wbia.queue.manager/mdns</command>
/*Establishes a relationship so that any messages from trading partner 'B' to trading partner 'A' are put in queue 'b_to_a' */
<command>addpair A B http://127.0.0.1:4081/ http://127.0.0.1:4080/ b_to_a mq://wbia.queue.manager/b_to_a</command>
/*Establishes a persistent send command so that Commerce Server periodically polls queue 'a_to_b' for messages to be sent to trading partner 'B'. */
<command>send http MAILBOX MAILBOX -de -dsMAILBOXID=a_to_b -r -tC5s -tE230030415000000</command>
<command>send http MAILBOX MAILBOX -de -dsMAILBOXID=a_to_b -r -tC5s -tE230030415000000</command>
<command>start http://127.0.0.1:4081</command> </xml>
Before setting up specific queues, be sure that you have defined the queue manager, server connection channel, and listener that you will use to communicate with Commerce Server.
A typical implementation of the connector requires the creation of an outbound queue for delivering messages to Commerce Server, and at least three inbound queues that the connector will poll for business data events, MDNs, and notifications. For descriptions of these and more about setting up queues, see: Setting up queues.
This task requires that you use connector properties and meta-objects to specify the queues that will be used, the business objects that will be converted, and the data handlers that will be used. See Setting up request processing,Setting up event notification, and Configuring connector meta-objects.
Connectors have two types of configuration properties: standard configuration properties and connector-specific configuration properties. Some of these properties have default values that you do not need to change. You may need to set the values of some of these properties before running the connector. For more information, see Connector configuration properties.
When you configure connector properties for the adapter, make sure that:
Data handlers for converting MDNs and notifications into business objects are provided with the connector; a data handler for converting between business objects and the document format of the business data being exchanged (such as an XML data handler) may be available with the connector, or may need to be customized for your enterprise.
You must configure connector properties before startup. You must also modify the startup file.
Make sure you modify the start_connector script to point to the location of the client libraries. Do not install multiple versions of the client libraries or versions that are not up-to-date with your WebSphere MQ server. For more information, see "Startup file configuration"