162 Implementing EDI Solutions
Provide values for the six data elements of this business object and click OK.
This will bring you back to the main window of the test connector. Select the new business
object in the tree structure and click Request -> Send.
Figure 3-63 Business object being sent
Open WebSphere MQ Explorer and browse the queue POACKQ, which should contain an
XML message representing this business object. However, if the WebSphere MQ Trigger
Monitor is still running, your message might be consumed already and you may need to
inspect the output queues of WebSphere Data Interchange. And, if TPI Server is still running,
your message might be gone to a trading partner.
This completes the basic integration of the InterChange Server in a solution with WebSphere
Data Interchange. The collaboration can now be extended to include ports to real back-office
applications and at this time, you will probably need to develop some maps to map business
objects.
3.5.5 Inbound flow
The previous sections described in detail the integration process for the outbound flow. The
steps to integrate CrossWorlds in the inbound flow are quite similar.
Business object
First, we again need a business object to represent the incoming purchase order. The DTD,
listed in Example 3-11 on page 135, can be imported in the InterChange Server using the
XML ODA as described in 3.5.1, “Creating business objects” on page 150.
Important: Since this business object will result in a message that will be processed by
WebSphere Data Interchange, you should provide data that makes sense for WebSphere
Data Interchange. Setting a random value for TargetPartnerID will likely result in an
unprocessed document within WebSphere Data Interchange.
Chapter 3. Implementing multi-product AS/2 communication with trading partners 163
Specify the following values for the PO DTD:
򐂰 Root element: PO
򐂰 Top Level element: PO
򐂰 BOPrefix: PO
The MQSeriesInbound Connector
The next step is to create an additional MQSeries Connector. Perform the following steps:
1. Copy and paste the existing MQSeriesConnector object in the folder Connectors in the
CrossWorlds System Manager. Name it MQSeriesInboundConnector.
2. Open a file browser and find the directory MQSeries in the connectors directory of the
CrossWorlds installation. Copy the whole directory and name it MQSeriesInbound.
3. Open the folder Connectors in the Start menu and copy and paste the existing shortcut
MQSeries Connector as MQSeriesInbound Connector.
4. Open the properties of this new short-cut and update the field Target:
D:\CrossWorlds\connectors\MQSeriesInbound\start_MQSeries.bat MQSeriesInbound cw_studenta
-cD:\CrossWorlds\connectors\MQSeriesInbound\MQSeriesAgentConfig.cfg
MQSeries has been replaced three times with MQSeriesInbound. Also update the field
Start in to the name of the new directory:
D:\CrossWorlds\connectors\MQSeriesInbound\
5. Define a new queue AP/MQSERIESINBOUNDCONNECTOR/CW_STUDENTA on the
queue manager used by the ICS. Replace CW_STUDENTA with the name of your ICS.
6. Restart the ICS. After the restart, verify that the connector is running using the
CrossWorlds System Manager.
7. Start the connector agent using the shortcut in the Programs folder and verify that the
Agent State in the System Monitor is Active.
Open the PortConnector object and update the supported business objects. Include business
object PO_PO in the list and be sure to check the field Agent Support.
Creating meta-objects
Once you have verified that the new connector can be started, proceed with the definition of
meta-objects. Open the meta-object MO_DataHandler_WDIXML_Config and save it as
MO_DataHandler_CWXML_Config. Make the following changes:
򐂰 Provide the path to the location of the DTD and the file name
򐂰 Set the BOPrefix to PO
Define meta-object MO_CWXML_Config. You can copy the meta-object
MO_WDIXML_Config. Rename the field POACK_POResponse to PO_PO.
Define meta-object MO_DataHandler_Inbound_Default. You can copy it from
MO_DataHandler_Default. For the MIME type text/xml, set the field type to
MO_DataHandler_CWXML_Config.
Open the connector object MQSeriesInboundConnector and switch to the tab Application
Config Properties. Set the value of the property DataHandlerConfigMO to
MO_DataHandler_Inbound_Default. Set the value of the property ConfigurationMetaObject to
MO_CWXML_Config. Set the value of the property InputQueue to
queue://cw_studenta.queue.manager/purchase.orders. Save the changes and restart the
connector.

Get Implementing EDI Solutions now with O’Reilly online learning.

O’Reilly members experience live online training, plus books, videos, and digital content from 200+ publishers.