JD Edwards EnterpriseOne Tools

Messaging Queue Adapter Configuration Guide

Release 9.1 for WebSphere MQ Guide on Windows

E21984-04

November 2015

Describes how to configure the Messaging Queue Adapter.

JD Edwards EnterpriseOne Tools Messaging Queue Adapter Configuration Guide, Release 9.1 for WebSphere MQ Guide on Windows

E21984-04

Copyright © 2011, 2015, Oracle and/or its affiliates. All rights reserved.

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable:

U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.

This software or hardware and documentation may provide access to or information about content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement between you and Oracle.

Contents

Preface

- Audience

- Documentation Accessibility

- Related Documents

- Conventions

1 Introduction

- 1.1 Accessing Minimum Technical Requirements

- 1.2 Creating Outbound WebSphere MQ Queues For Real-Time Events

- 1.2.1 Prerequisites

2 Setting Up Inbound and Outbound IBM WebSphere MQ Queues for Z Events Only: Step 1

- 2.1 Configuring the JD Edwards EnterpriseOne Server Components

- 2.2 Communicating Between Systems - Starting up Channels And Listeners

- 2.3 Working with WebSphere MQ Queue Manager Commands

3 Configuring the JD Edwards EnterpriseOne Server jde.ini File for Z Events Only: Step 2

4 Setting Up UBE Queues for Z Events Only: Step 3

- 4.1 Setting up the JD Edwards EnterpriseOne Server to Support Multiple UBE Queues

- 4.2 Setting Up the Client to Support the R00460 Subsystem UBE

5 Configuring the Interoperability Features for Z Events Only: Step 4

- 5.1 Setting Up Flat File Cross-Reference

- 5.2 Setting Up Data Export Controls

- 5.3 Setting Up the Sales Order Entry Application

- 5.4 Configuring the Address Book Revisions Application

- 5.5 Configuring the Address Book Master Business Function

6 Restarting the Services: Step 5

7 Running the R00460 Subsystem for WebSphere MQ for Z Events Only: Step 6

- 7.1 Starting the R00460 Subsystem

- 7.2 Viewing Subsystems Running on a Server

- 7.3 Terminating Subsystems

- 7.4 Verifying Event Delivery

Preface

Welcome to the JD Edwards EnterpriseOne Tools Configuration for Messaging Queue Adapter for IBM WebSphere MQ on Windows Guide.

Audience

This document is intended for system administrators and consultants who are responsible for installing and managing JD Edwards EnterpriseOne.

Documentation Accessibility

For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.

Access to Oracle Support

Oracle customers that have purchased support have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.

Related Documents

You can access related documents from the JD Edwards EnterpriseOne Release Documentation Overview pages on My Oracle Support. Access the main documentation overview page by searching for the document ID, which is 876932.1, or by using this link:

https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=876932.1

To navigate to this page from the My Oracle Support home page, click the Knowledge tab, and then click the Tools and Training menu, JD Edwards EnterpriseOne, Welcome Center, Release Information Overview.

This guide contains references to server configuration settings that JD Edwards EnterpriseOne stores in configuration files (such as jde.ini, jas.ini, jdbj.ini, jdelog.properties, and so on). Beginning with the JD Edwards EnterpriseOne Tools Release 8.97, it is highly recommended that you only access and manage these settings for the supported server types using the Server Manager program. See the JD Edwards EnterpriseOne Tools Server Manager Guide.

Conventions

The following text conventions are used in this document:

Convention

Meaning

boldface

Boldface type indicates graphical user interface elements associated with an action, or terms defined in text or the glossary.

italic

Italic type indicates book titles, emphasis, or placeholder variables for which you supply particular values.

monospace

Monospace type indicates commands within a paragraph, URLs, code in examples, text that appears on the screen, or text that you enter.

1 Introduction

Oracle's JD Edwards EnterpriseOne Adapter for WebSphere MQ enables you to connect third-party applications to JD Edwards 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 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 WebSphere MQ is a JD Edwards EnterpriseOne product that can be licensed and installed independently. You use this adapter to connect JD Edwards EnterpriseOne with any system that can implement the IBM WebSphere MQ messaging protocols, including 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.

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

Access the current Minimum Technical Requirement (MTR) listing from Customer Connection. You can access the MTRs through multiple entry points. This path and link are one example: Navigation: Customer Connection, Implement, Optimize + Upgrade, Optimization Guide, Supported Platforms, EnterpriseOne:

http://www.peoplesoft.com/corp/en/iou/platforms/enterpriseone

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 "Creating an 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.

1.2.1 Prerequisites

See Accessing Minimum Technical Requirements.

2 Setting Up Inbound and Outbound IBM WebSphere MQ Queues for Z Events Only: Step 1

IBM WebSphere MQ is a queue messaging system that requires a sender and receiver relationship. One side of IBM WebSphere MQ is installed on Oracle's JD Edwards EnterpriseOne server while the related side is installed on another physical or logical machine. The setup on the JD Edwards EnterpriseOne server enables JD Edwards EnterpriseOne to receive inbound messages from a third-party application or system and to place outbound messages in a queue for processing by a third-party application or system. Refer to the applicable IBM documentation for instructions on installing IBM WebSphere MQ on other machines.

The procedures described in this section assume you have already installed the IBM product WebSphere MQ onto your JD Edwards EnterpriseOne server.

You set up your enterprise server so that the system can receive inbound messages from a third-party application or system and then place responses, in the form of outbound messages, in a queue for processing by the third-party application or system.

In addition to information about setting up your JD Edwards EnterpriseOne server, this section also provides examples for the following:

- Communicating between the JD Edwards EnterpriseOne WebSphere MQ Server and the Non-JD Edwards EnterpriseOne IBM WebSphere MQ Server.

- Working with IBM WebSphere MQ Queue Manager commands.

2.1 Configuring the JD Edwards EnterpriseOne Server Components

Inbound to JD Edwards EnterpriseOne and Outbound to a Third-Party Application

You set up your JD Edwards EnterpriseOne server so that EnterpriseOne can receive an inbound message from another system or application and respond by placing an outbound message in the outbound queue. Complete these tasks:

- Create and start IBM WebSphere MQ Queue Manager.

- Create MQ local queues.

- Create a MQ remote queue.

- Create a MQ local sender channel.

- Create a MQ local receiver channel.

- End the IBM WebSphere MQ Queue Manager.

Caution:
The names of queues and channels in IBM WebSphere MQ are case-sensitive. Be sure to use capital letters as specified in this document. You can specify any name for a queue or channel. However, it is important that the queue names you create match the queue names you specify in the jde.ini file on the JD Edwards EnterpriseOne server.

To create and start IBM WebSphere MQ Queue Manager:

1. From the DOS Prompt, change the directory or specify the directory, using this command:
Program Files\WebSphere MQ\Bin

2. Execute the this command to create the Queue Manager:
CRTMQM JDE_QMGR

This establishes a queue manager that is not the default queue manager.

3. Execute this command to start the Queue Manager:
STRMQM JDE_QMGR

To create MQ local queues:

You must create these local queues:

- INBOUND.Q

- SUCCESS.Q

- ERROR.Q

- DEFRES.Q

- OUTBOUND.Q.XMIT

From the MQ command line environment, at the same DOS prompt where you started the Queue Manager:

1. Use this command to start the IBM WebSphere MQ command:
RUNMQSC JDE_QMGR

2. The display returns this:
Starting IBM WebSphere MQ Command

3. To create the local queues, run these IBM WebSphere MQ commands:

DEFINE QLOCAL(INBOUND.Q)    DEFPSIST(YES)    DESCR('Queue for messages into JD Edwards EnterpriseOne')
DEFINE QLOCAL(SUCCESS.Q)    DEFPSIST(YES)    DESCR('Queue for successful messages in JD Edwards EnterpriseOne')
DEFINE QLOCAL(ERROR.Q)    DEFPSIST(YES)    DESCR('Queue for error messages in JD Edwards EnterpriseOne')
DEFINE QLOCAL(DEFRES.Q)    DEFPSIST(YES)    DESCR('Queue for responses if not in message in JD Edwards EnterpriseOne')
DEFINE QLOCAL('OUTBOUND.Q.XMIT')    DEFPSIST(YES)    USAGE(XMITQ)  DESCR('Transmit queue to WCS system')

To create the MQ remote queue:

From the MQ command line environment, enter this command to create a single MQ remote queue:

DEFINE QREMOTE(OUTBOUND.Q) DEFPSIST(YES)
XMITQ(OUTBOUND.Q.XMIT)  RNAME(ECE_IN2MQI)
RQMNAME(ECE_MQI_QMGR) DESCR('ECE out bound queue to WCS system')

Note:
ECE_IN2MQI is the third-party remote queue name and ECE_MQI_QMGR is the third-party queue manager name.

To create a MQ local sender channel:

From the MQ command line environment, enter this command to create a MQ local sender channel:

DEFINE CHANNEL('OW2MQI_CHL') CHLTYPE(SDR) TRPTYPE(TCP)
CONNAME(name_of_Commerce_Integrator_server)
XMITQ(OUTBOUND.Q.XMIT) DISCINT(0) DESCR('Sender channel to WCS system')

To create a MQ local receiver channel:

From the MQ command line environment, enter this command to create a MQ local receiver channel:

DEFINE CHANNEL('MQI2OW_CHL') CHLTYPE(RCVR) TRPTYPE(TCP)
DESCR('Receiver channel from WCS system')

To end the IBM WebSphere MQ command mode:

When you are finished creating the queues and channels, enter this command from the DOS prompt in the MQ command line environment to exit the RUNMQSC console program:

END

2.2 Communicating Between Systems - Starting up Channels And Listeners

You must set up communications between the JD Edwards EnterpriseOne IBM WebSphere MQ server (functioning on the JD Edwards EnterpriseOne server) and the third-party IBM WebSphere MQ server. This section provides example tasks for setting up communications. The example communications setup uses these sequenced and machine dependent steps:

- Start the Queue Manager on the third-party IBM WebSphere MQ Server.

- Start the Queue Manager on the JD Edwards EnterpriseOne IBM WebSphere MQ Server.

- Start the channel on the third-party IBM WebSphere MQ Server.

- Start the channel on the JD Edwards EnterpriseOne IBM WebSphere MQ Server.

Note:
The first time you start your communications channels, you might need to manually start the sender channel on the local machine and then manually start the receiver channel on the remote machine. After the initial start of the channels, when you start the sender on the local machine, the receiver on the remote machine should automatically start.

To start the queue manager on the third-party WebSphere MQ server:

On the third-party IBM WebSphere MQ server:

1. At a DOS prompt, enter this command to start the Queue Manager:
STRMQM ECE_MQI_QMGR

2. At the same DOS prompt, enter this command to start the listener:
start/min runmqlsr -m ECE_MQI_QMGR -t TCP

This action creates a minimized DOS prompt window. Do not close this window.

Note:
ECE_MQI_QMGR is the third-party queue manager name.

To start the queue manager on the JD Edwards EnterpriseOne IBM WebSphere MQ server:

On the JD Edwards EnterpriseOne IBM WebSphere MQ server:

1. At a DOS prompt, enter this command to start the Queue Manager:
STRMQM JDE_QMGR

2. At the same DOS prompt, enter this command to start the listener:
start/min runmqlsr -m JDE_QMGR -t TCP

This action creates a minimized DOS prompt window. Do not close this window.

To start the channel on the non-JD Edwards EnterpriseOne IBM WebSphere MQ server:

In order to issue the start channel command on the non-JD Edwards EnterpriseOne IBM WebSphere MQ server, you must be in the WebSphere MQ command mode.

On the non-JD Edwards EnterpriseOne IBM WebSphere MQ server:

1. From the IBM WebSphere MQ command mode, enter this command at the same DOS prompt you used to start the queue manager:
RUNMQSC ECE_MQI_QMGR

Note:
ECE_MQI_QMGR is the third-party queue manager name.

2. Enter these commands to start the WebSphere MQ to EnterpriseOne channels:

START CHANNEL(MQI2OW_CHL)
START CHANNEL(OW2MQI_CHL)

3. Enter this command to exit the WebSphere MQ command mode:
END

To start the channel on the JD Edwards EnterpriseOne IBM WebSphere MQ server:

In order to issue the start channel command on the JD Edwards EnterpriseOne IBM WebSphere MQ server, you must be in the WebSphere MQ command mode.

On the JD Edwards EnterpriseOne IBM WebSphere MQ server:

1. From the IBM WebSphere MQ command mode, enter this command at the same DOS prompt you used to start the queue manager:
RUNMQSC JDE_QMGR

2. Enter these commands to start the IBM WebSphere MQ to JD Edwards EnterpriseOne channels:

START CHANNEL(OW2MQI_CHL)
START CHANNEL(MQI2OW_CHL)

3. Enter this command to exit the WebSphere MQ command mode:
END

2.3 Working with WebSphere MQ Queue Manager Commands

This table provides example commands that you can use when working with IBM WebSphere MQ Queue Manager:

Caution:
The names of queues and channels in IBM WebSphere MQ are case-sensitive. Be sure to use capital letters as specified in this document. You can specify any name for a queue or channel. However, it is important that the queue names you create match the queue names you specify in the jde.ini file on the JD Edwards EnterpriseOne server.

Command

Description

STRMQM JDE_QMGR

Start the queue manager.

ENDMQM -i JDE_QMGR

End the queue manager. The -i switch means immediately.

RUNMQSC JDE_QMGR

Start using WebSphere MQ commands.

Display QL(qname.Q)

Display the local queue.

Clear QL(qname.Q)

Clear the local queue.

END

Stop using WebSphere MQ commands.

AMQSBCG qname.Q JDE_QMGR

Run the browse queue command. This does not remove the message.

START CHANNEL(channel_name)

Start the channel.

STOP CHANNEL(channel_name)

Stop the channel.

Start/min runmqlsr -m JDE_QMGR -t TCP

Start a listener.

RESET CHL (channel_name)

Reset a channel that has become inactive.

3 Configuring the JD Edwards EnterpriseOne Server jde.ini File for Z Events Only: Step 2

Note:
Make sure that Oracle's JD Edwards EnterpriseOne services are stopped until after you make the requisite changes to the jde.ini file on the JD Edwards EnterpriseOne server.
Be sure to restart the ICI machine after the IBM WebSphere MQ installation in order to set the system environment variables.

This table shows the settings for the JD Edwards EnterpriseOne server jde.ini file:

Parameter

Description

[SECURITY]
User=JDE

Password=JDE

You must have these values set in order for JD Edwards EnterpriseOne to accept messages.

[JDENET_KERNEL_DEF17]

You must update the DEF value to next number. For JD Edwards EnterpriseOne, this value is 17.

krnlName=MQSI Kernel

dispatchDLLName=mqsadapt.dll

dispatchDLLFunction=_JDEK_DispatchMQSeriesProcess@28

maxNumberOfProcesses=1

numberOfAutoStartProcesses=1

This value can be set for 1 through n, where n is the number of processes you have defined. When this value is 1 or more, the MQSI kernel automatically starts when JD Edwards EnterpriseOne is initialized. You must use this setting when you use the IBM WebSphere MQ adapter with JD Edwards EnterpriseOne.
If the value of this setting is 0, the MSMQ kernel does not automatically start upon initialization of JD Edwards EnterpriseOne.

Parameter

Description

[MQSI]

These settings are for the header information on the message that is required for Commerce Integrator.

QMGRName=JDE_QMGR
QInboundName=INBOUND.Q

QErrorName=DEFRES.Q

QOutboundName=OUTBOUND.Q

The name of the queues can be any name but must match the names you specify in the IBM WebSphere MQ queue setup.

TimeoutWaitInterval=15

MaxBufferLength=100000

This value is measured in bytes. The maximum value that you can set for the MaxBufferLength setting is 100,000,000. The default value is 100,000. You should not use the maximum value, as this can cause performance issues. You can use the IBM WebSphere MQ tools to determine the average size of a message and then set the MaxBufferLength value based on your needs.

CreateHeader=YES
JDEOrderStatusCode=JDESOOUT

JDECustomerCode=JDEAB

JDEItemPriceCode=JDEPRICE

JDEItemQtyCode=JDEIL

NCOrderStatusCode=JDE.IC.F4201Z1

NCCustomerCode=JDE.IC.F0101Z2

NCProductPriceCode=JDE.IC.F4106NC

NCProductQtyCode=JDE.IC.F41021Z1

If you use the adapter without IBM WebSphere Commerce Integrator, you can specify the create header as equal to No and you should set the IBM WebSphere Commerce Integrator-specific parameter settings in the MQSI section to blank. This includes the four parameters prefixed by JDE and four parameters prefixed by NC.

AppGroup=NNJDE

OWHostName=host_name

You must specify a host name. The name you specify is the machine used to create the net message to trigger the outbound adapter. This is the server on which JD Edwards EnterpriseOne resides.

4 Setting Up UBE Queues for Z Events Only: Step 3

You must set up at least two UBE queues. This is required because Oracle's JD Edwards EnterpriseOne Adapter for IBM WebSphere MQ relies on the use of a subsystem UBE (R00460). Like all subsystem UBEs, R00460 operates in a permanent processing mode that consumes the queue in which it runs. No other UBE jobs running on the server can operate in the same queue. As a result, you must define at least two UBE queues where one queue is dedicated to normal UBE processing and the other is dedicated to the JD Edwards EnterpriseOne Adapter for IBM WebSphere MQ subsystem.

This section describes the following:

- Modifying the jde.ini on the JD Edwards EnterpriseOne server to support multiple UBE queues.

- Modifying the jde.ini on the JD Edwards EnterpriseOne client to submit the UBE subsystem request.

4.1 Setting up the JD Edwards EnterpriseOne Server to Support Multiple UBE Queues

To support multiple UBE queues on the JD Edwards EnterpriseOne server, you might need to modify the jde.ini file. Ensure the following settings are correct:

Parameter

Description

[NETWORK QUEUE SETTINGS]
UBEQueues=2

UBEQueue1=ONEWORLD

UBEQueue2=QBATCH

The following values should be added or modified where:
UBEQueues= Defines the number of UBE queues that are defined on this JD Edwards EnterpriseOne server. In this example, two queues are defined.

UBEQueue1= Defines the name of the first UBE queue. In this example, the queue name is ONEWORLD.

UBEQueue1= Defines the name of the second UBE queue. In this example, the queue name is QBATCH.

4.2 Setting Up the Client to Support the R00460 Subsystem UBE

If you submit or start the R00460 subsystem UBE from a JD Edwards EnterpriseOne Windows client, you must temporarily modify the client's jde.ini file. The temporary modification is required so that the client can direct the R00460 subsystem UBE to the appropriate UBE queue name. After the client submits or starts the R00460 subsystem UBE, you must undo the temporary change so that the client can regain access to normal UBE submissions to the server-based UBE queue.

On the client machine from which you want to submit or start the R00460 subsystem UBE, ensure the following jde.ini settings are correct:

Parameter

Description

[NETWORK QUEUE SETTINGS]
UBEQueue=

UBEQueue= Defines the name of the local or server-based UBE queue.
If you want the client to start or submit the R00460 subsystem, enter a value that corresponds with the value set by the UBEQueue1= on the JD Edwards EnterpriseOne server.

If you want the client to use the normal server-based UBE processing queue, enter a value that corresponds with the equivalent value for that queue on the JD Edwards EnterpriseOne server. In the example presented in this guide, the name of the normal UBE processing queue is QBATCH.

Caution:
Any time you modify settings in the jde.ini file on the client, you must exit and restart JD Edwards EnterpriseOne in order for those changes to become effective.

5 Configuring the Interoperability Features for Z Events Only: Step 4

You can use Z, real-time, or XAPI events to receive transactions from Oracle's JD Edwards EnterpriseOne. To use real-time events, you must set up your system as indicated in the JD Edwards EnterpriseOne Tools Interoperability Guide, and you must set up events as indicated in the JD Edwards EnterpriseOne Applications Real-Time Events Implementation Guide.

Z event outbound processing uses interface table (Z-table) processes supported by JD Edwards EnterpriseOne applications. The outbound processes available to you vary depending on which JD Edwards EnterpriseOne release you use. If you use interface tables for transaction-specific outbound processing, you must perform configuration tasks such as setting up processing options and setting up data export controls.

This section provides guidance for setting up the data export controls and also provides examples for setting up JD Edwards EnterpriseOne applications that support Z event processing. The application examples include the following:

- Setting Up Flat File Cross-Reference (P47002)

- Setting Up Data Export Controls

- Setting Up the Processing Options for the Sales Order Master Business Function (P4210).

- Setting Up the Processing Options for Address Book Revisions (P01012).

- Setting Up the Processing Options for the Address Book Master Business Function (P0100041).

See Also:

- JD Edwards EnterpriseOne Applications Real-Time Events Implementation Guide

- Events chapters in the JD Edwards EnterpriseOne Tools Interoperability Guide

5.1 Setting Up Flat File Cross-Reference

When you enable Z events, you also update the Flat File Cross-Reference (F47002) table. The transaction type that you entered in the processing option maps to table F47002 to determine which interface tables to use to retrieve the information. You use the Flat File Cross-Reference program (P47002) to update table F47002.

To set up a flat file cross reference:

Refer to the JD Edwards EnterpriseOne Applications Data Interface for Electronic Data Interchange Implementation Guide for instructions on setting up the flat file cross-reference application.

5.2 Setting Up Data Export Controls

You must create a Data Export Control (F0047) record for each transaction type. The record specifies the vendor-specific UBE or function to call to process the transaction. For example, for transaction type JDESOOUT you must set up a record for each order type that you want to export.

To set up data export controls:

On the JD Edwards EnterpriseOne Menu, select JD Edwards EnterpriseOne Menus > Order Management > Sales Order Management > Sales Order Advanced & Technical Ops > Sales Interoperability > Data Export Controls.

An alternative way to access the Data Export Controls program is to type P0047 on the Fast Path.

This table provides the values for fields:

Form Element

Description

Trans

The values you specify in this field must match the values you have configured for JD Edwards EnterpriseOne outbound processing in the various EnterpriseOne applications. These are example transaction types:
JDEAB

JDEIL

JDEPRICE

JDESOOUT

Or Ty

The values you specify in this field must match the values that are required for your system. For example, for WCS the following order types are required:
JDESOOUT S4

JDESOOUT SO

Seq

1.00

UBE Name

Leave the field blank.

Version

Leave the field blank.

Function Name

_MQOutboundNotify@36.

Function Library:

x:\JDEdwardsOneWorld\ddp\B9\system\bin32\MQNotify.dll
where "x" is a variable drive letter for your JD Edwards EnterpriseOne server.

Execute for Add:

1

Execute for Update:

1

Execute for Delete:

1

Execute for Inquiry:

1

Flat File Export Mode:

0

External Database Export Mode

0

External API Export Mode:

0

Launch Immediately

1

5.3 Setting Up the Sales Order Entry Application

You set up the JD Edwards EnterpriseOne Sales Order Entry (P4210) program to enable it for interoperability operations.

To set up the processing options for the Sales Order Entry:

On EnterpriseOne Menu, select JD Edwards EnterpriseOne Menus > Order Management > Sales Order Management > Daily Processing > Sales Order Processing > click the arrow to the right of Sales Order Detail and then select Values > on Processing Options, select Interop from the Select Tab options.

1. To define the transaction type, type JDESOOUT in the Transaction Type field.

2. To define before or after image processing, enter the appropriate value in the Before/After Image Processing field.

3. Click OK.

5.4 Configuring the Address Book Revisions Application

You set up the JD Edwards EnterpriseOne Address Book Revision (P01012) program to enable it for interoperability operations.

To set up processing options for Address Book Revisions:

On the JD Edwards EnterpriseOne Menu, click JD Edwards EnterpriseOne Menus > Foundation Systems > Address Book > Daily Processing > click the arrow to the right of Address Book Revisions and then select Values > on Processing Options, select the Versions tab.

1. On Processing Options, type INTOP in the Address Book MBF (P0100041) Version field.

2. Click OK.

3. On Work With Addresses, click Close.

5.5 Configuring the Address Book Master Business Function

You set up the Address Book Master Business Function (P0100041) to enable interoperability operations.

To set up the processing options for the Address Book Master Business Function:

1. Type IV in the Fast Path.

2. On Interactive Versions -- Work With Versions, type P0100041 in the Application field, and then click Find.

3. Select INTOP, and then select Processing Options from the Row menu.
If there is not a version called INTOP, select version ZJDE0001 and copy it. Call the new version INTOP and click OK.

4. On Processing Options, select the Outbound tab.

5. Type JDEAB in the Transaction Type field.

6. To define before or after image processing, enter the appropriate value in the Before/After Image Processing field.

7. Click OK.

8. Click Close.

6 Restarting the Services: Step 5

After you have completed the IBM WebSphere MQ queue setup and the various associated configuration tasks (including configuring the jde.ini file), you must stop and restart the NT Services on Oracle's JD Edwards EnterpriseOne server.

To stop the NT Services:

Access the JD Edwards EnterpriseOne server.

1. From the Control Panel, select Services.

2. Select JDE E900 Network, then Stop.

To restart the NT Services

Access the JD Edwards EnterpriseOne server:

1. From the Control Panel, select Services.

2. Select JDE E900 Network, and then Start.

3. Successfully complete a PORTTEST.

7 Running the R00460 Subsystem for WebSphere MQ for Z Events Only: Step 6

The R00460 subsystem monitors the IBM WebSphere MQ queues for messages and manages Oracle's JD Edwards EnterpriseOne side of the queues. After the R00460 subsystem is started, you can verify that the subsystem is running. You can also review the job record for the subsystem. After the records have been processed, you must manually terminate the subsystem job.

Caution:
After the records have been processed, instead of ending the job, subsystem jobs look for new data in the data queue. Subsystem jobs run until you terminate them.

See Also:

- "Managing EnterpriseOne Subsystems" in the JD Edwards EnterpriseOne Tools System Administration Guide

7.1 Starting the R00460 Subsystem

The R00460 subsystem must be manually started. Usually the system administrator or manager-level user is responsible for this task.

To start the R00460 subsystem:

1. Type BV in the Fast Path.

2. On Work With Batch Versions, type R00460 in the Batch Application field, and then click Find.

3. Select version XJDE0001, and then click Select.

4. On Version Prompting, click Submit.

5. On Report Output Destination, select the destination option for your report, and then click OK.

7.2 Viewing Subsystems Running on a Server

You use Work With Servers to determine which subsystems are currently running or waiting on a particular server. The running subsystems are identified by report number and version.

To view subsystems running or waiting on a server:

On the JD Edwards EnterpriseOne Menu, select JD Edwards EnterpriseOne Life Cycle Tools > System Administration Tools > System Administration Tools > Data Source Management > Work With Servers.

1. On Work With Servers, click Find to locate all servers or use the query by example row to locate a specific server.

2. Select the server with which you want to work.

3. From the Row menu, select Subsystem Jobs.

4. On Work With Server Jobs, click one of the following options:

- Processes
A process is a subsystem that is waiting for work. This is identified by an S (subsystem job) value in the Job Type field.

- Waiting Jobs
Waiting jobs are report jobs that are queued for a subsystem. This is identified by an R (subsystem record) value in the Job Type field.

All currently running JD Edwards EnterpriseOne subsystems are displayed. The status of each subsystem is shown by codes in the following fields:

- Job Type
This field indicates whether the status is a subsystem record or a subsystem job. Valid values are:

R or subsystem record

S or subsystem job

- Job Status
W - subsystem record waiting

P - subsystem record processing

E - subsystem record to end the job

R - subsystem job running

7.3 Terminating Subsystems

You must manually terminate subsystem jobs. Two methods of termination are available:

- Stopping a subsystem job causes it to terminate after it finishes processing the current record. Additional unprocessed records in the F986113 table will not be processed, and no new records can be written. Essentially the unprocessed records will be lost; that is, the process that initiated the record is not notified that the record was not processed.

- Ending a subsystem job causes it to terminate after processing all of the existing subsystem records. No new records can be written to the F986113 table.

To stop subsystems:

On the JD Edwards EnterpriseOne Menu, select JD Edwards EnterpriseOne Life Cycle Tools > System Administration Tools > System Administration Tools > Data Source Management > Work With Servers.

1. On Work With Servers, click Find.

2. Select the server in the detail area, and then select Subsystem Jobs from the Row menu.

3. On Work With Subsystems, locate a running subsystem.

4. Select the running subsystem that you want to stop, and then select Stop Subsystem from the Row menu.

5. On End Subsystem Job, click OK.

To end subsystems:

On the JD Edwards EnterpriseOne Menu, select JD Edwards EnterpriseOne Life Cycle Tools > System Administration Tools > System Administration Tools > Data Source Management > Work With Servers.

1. On Work with Servers, click Find.

2. Select the server in the detail area, and then select Subsystem Jobs from the Row menu.

3. On Work With Subsystems, locate a running subsystem.

4. Select the running subsystem that you want to end, and then select End Subsystem Job from the Row menu.

5. On End Subsystem Job, click OK.

7.4 Verifying Event Delivery

Once finished with the installation, you should verify the event delivery. Use the IBM WebSphere MQ Explorer to select the queue that you created to received JD Edwards EnterpriseOne events. Right-click the queue and select Browse Messages to display the messages.

See "Verifying Event Delivery" in the JD Edwards EnterpriseOne Tools Interoperability Guide.

Oracle Legal Notices

Copyright Notice

Copyright © 1994-2018, Oracle and/or its affiliates. All rights reserved.

License Restrictions Warranty/Consequential Damages Disclaimer

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

Warranty Disclaimer

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

Restricted Rights Notice

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable:

U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.

Hazardous Applications Notice

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Trademark Notice

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.

Third-Party Content, Products, and Services Disclaimer

This software or hardware and documentation may provide access to or information about content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement between you and Oracle.

Pre-General Availability Draft Documentation Notice

If this document is in public or private pre-General Availability status:

This documentation is in pre-General Availability status and is intended for demonstration and preliminary use only. It may not be specific to the hardware on which you are using the software. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to this documentation and will not be responsible for any loss, costs, or damages incurred due to the use of this documentation.

Private Pre-General Availability Draft Documentation Notice

If this document is in private pre-General Availability status:

The information contained in this document is for informational sharing purposes only and should be considered in your capacity as a customer advisory board member or pursuant to your pre-General Availability trial agreement only. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality described in this document remains at the sole discretion of Oracle.

This document in any form, software or printed matter, contains proprietary information that is the exclusive property of Oracle. Your access to and use of this confidential material is subject to the terms and conditions of your Oracle Master Agreement, Oracle License and Services Agreement, Oracle PartnerNetwork Agreement, Oracle distribution agreement, or other license agreement which has been executed by you and Oracle and with which you agree to comply. This document and information contained herein may not be disclosed, copied, reproduced, or distributed to anyone outside Oracle without prior written consent of Oracle. This document is not part of your license agreement nor can it be incorporated into any contractual agreement with Oracle or its subsidiaries or affiliates.

Documentation Accessibility

For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.

Access to Oracle Support

Oracle customers that have purchased support have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.