1 Introduction

Oracle's JD Edwards EnterpriseOne Adapter for IBM WebSphere MQ enables you to connect third-party applications to EnterpriseOne by sending and receiving messages through IBM's WebSphere MQ messaging system. The adapter monitors an inbound queue for request and reply messages, performs the requested services, and places the results on outbound queues. The adapter also monitors JD Edwards EnterpriseOne for certain activities and publishes the results in an outbound message queue. All messages transported through IBM WebSphere MQ are in the form of XML documents.

The purpose of this document is to describe the configuration and operation of the adapter. A separate document, the JD Edwards EnterpriseOne Tools Interoperability Guide, in the chapter ”Understanding Messaging Queue Adapters” explains the design of the adapter, the formats of the documents, and the tasks necessary to create, modify, and process the XML documents in the Events chapters.

The JD Edwards EnterpriseOne Adapter for IBM WebSphere MQ is an EnterpriseOne product that can be licensed and installed independently. You use this adapter to connect the JD Edwards EnterpriseOne system with any system that can implement the IBM WebSphere MQ messaging protocols, including IBM WebSphere Commerce Suite (WCS), and produce and consume XML documents in the prescribed formats. The JD Edwards EnterpriseOne Adapter for WebSphere MQ exports and imports XML documents through WebSphere MQ in the prescribed formats.

Overview of three operations:

  1. Inbound transactions through calling BSFNs.

  2. Outbound Z events delivery through setting up EnterpriseOne Z events mechanism.

The remaining guide applies only to inbound and outbound using Z events.

  1. Outbound Real-Time events delivery through setting up EnterpriseOne Real-Time events mechanism.

1.1 Accessing Minimum Technical Requirements

Customers must conform to the supported platforms for the release as detailed in the JD Edwards EnterpriseOne Minimum Technical Requirements. In addition, JD Edwards EnterpriseOne may integrate, interface, or work in conjunction with other Oracle products. Refer to the following link for cross-reference material in the Program Documentation for Program prerequisites and version cross-reference documents to assure compatibility of various Oracle products: http://www.oracle.com/corporate/contracts/index.html

You can locate the JD Edwards EnterpriseOne Tools Release 9.2 Certifications from My Oracle Support.

To access JD Edwards EnterpriseOne Tools Release 9.2 Certifications:

  1. Navigate to My Oracle Support (https://support.oracle.com).

  2. Click the Certifications tab.

  3. Search for the product.

1.2 Creating Outbound WebSphere MQ Queues For Real-Time Events

If you are interested in receiving real-time events, real-time event queues must be created. The real-time event queue does not need to be created if you are not interested in receiving real-time events.

See Also:

”Creating a MSMQ Real-Time Event Queue” in the JD Edwards EnterpriseOne Tools Interoperability Guide.

This illustration shows the JD Edwards EnterpriseOne server with the IBM WebSphere MQ adapter.

This image is described in surrounding text.

Prerequisites

See Accessing Minimum Technical Requirements.

1.3 Configuring EnterpriseOne to Support WebSphere MQ Version 6.0 and Version 7.0

Note:

These steps are not needed for WebSphere MQ 8.0. Starting with Tools Release 9.1.5.7, only one version of these files are delivered, without a version number in the name. The libraries delivered without version names are only compatible with WebSphere MQ 8.0 starting with Tools Release 9.1.5.7 and cannot be used with older versions of WebSphere MQ. Conversely, the driver libraries with names ending in *_6 or *_7 cannot be used with WebSphere MQ 8.0.

To properly perform this task, you must be logged on as the UNIX user who starts JD Edwards EnterpriseOne services (for example, jde900).

  1. Use this command to change your directory:

    cd $SYSTEM/lib

  2. When using the 6.0 version of WebSphere MQ, create a soft link to the WebSphere MQ 6.0 version of the driver libraries. These file names end in *_6.so (use .sl instead of .so on HP-UX PA-RISC servers).

    ln -s libmqnotify_6.so libmqnotify.so

    ln -s libmqsadapt_6.so libmqsadapt.so

    ln -s libmqsrtdrv_6.so libmqsrtdrv.so

  3. When using the 7.0 version of WebSphere MQ, create a soft link to the WebSphere MQ 7.0 version of the driver libraries. These file names end in *_7.so (use .sl instead of .so on HP-UX PA-RISC servers).

    ln -s libmqnotify_7.so libmqnotify.so

    ln -s libmqsadapt_7.so libmqsadapt.so

    ln -s libmqsrtdrv_7.so libmqsrtdrv.so