A Configuring J.D. Edwards OneWorld for Outbound Transaction Processing

J.D. Edwards OneWorld enables you to specify outbound functionality for Master Business Functions (MBF). The following topics describe how to enable outbound transaction processing in J.D. Edwards OneWorld and how to modify the jde.ini file for XML support.

Specifying Outbound Functionality for a Business Function
Modifying the OneWorld jde.ini File

Specifying Outbound Functionality for a Business Function

You can specify outbound functionality for business functions and manage the flow of data. You enable outbound transaction processing using a processing option that controls how a transaction is written.

Outbound Transaction Processing

To process outbound data, you use the:

Data Export Control table
Processing Log table

The Data Export Control table manages the flow of the outbound data to third-party applications. The Processing Log table contains all the information about the OneWorld event.For more information on configuring J.D. Edwards OneWorld for outbound processing, see "Detailed Tasks for OneWorld Operations" in the J.D. Edwards Interoperability Guide for OneWorld XE.

Enabling Outbound Transaction Processing

To enable outbound transaction processing:

Right-click the application that contains the processing options for the Master Business Functions of the transaction.

For a list of these options, see Appendix B of theJ.D. Edwards Interoperability Guide for OneWorld XE.
From the shortcut menu, select Prompt for Values. Click either the Outbound tab or the Interop tab.Enter the transaction type.

The OneWorld Event listener processes only the after image for the business function.You are not required to set the before image function.

The Data Export Control Table and the Processing Log Table

The Data Export Control table manages the flow of the outbound data to third-party applications. OneWorld allows the subscription of multiple vendor-specific objects for an interoperability transaction. The records in the Data Export Control table are used to determine the vendor-specific objects to call from the Outbound Subsystem batch process (R00460) or the Outbound Scheduler batch process (R00461).The Processing Log table contains all the information about the OneWorld event including the transaction type, order type, and sequence number from the Data Export Control table.

Using the Export Controls

To use the data export controls:

On the Work With Data Export Controls pane, click Add.
Enter values in the Transaction Type and Order Type fields.For each detail row, enter either a batch process name or version or a function name and the library.To launch the vendor-specific object for an add or insert, enter 1.
For the update, delete, and inquiry actions, enter 1.
In the Launch Immediately column, enter 1.
Click OK.

Modifying the OneWorld jde.ini File

Because OracleAS Adapter for J.D. Edwards OneWorld uses XML for the transfer of information to and from J.D. Edwards OneWorld, you must configure the OneWorld environment to support XML. You can do this easily by modifying the OneWorld jde.ini file.

Modifying a jde.ini File for XML Support

The following is an example of how to modify a jde.ini file to implement XML support.

Add the following blocks:

[JDENET_KERNEL_DEF6];krnlName=CALL OBJECT KERNEL;dispatchDLLName=jdekrnl.dll
;dispatchDLLFunction=_JDEK_DispatchCallObjectMessage@28
;maxNumberOfProcesses=10
;numberOfAutoStartProcesses=0
krnlName=CALL OBJECT KERNEL
dispatchDLLName=XMLCallObj.dll
dispatchDLLFunction=_XMLCallObjectDispatch@28
maxNumberOfProcesses=10
numberOfAutoStartProcesses=0
[JDENET_KERNEL_DEF15]
krnlName=XML TRANSACTION KERNEL
dispatchDLLName=XMLTransactions.dll
dispatchDLLFunction=_XMLTransactionDispatch@28
maxNumberOfProcesses=1
numberOfAutoStartProcesses=1

The parameters containing an underscore (_) and @28 are for Windows operating systems only. For other operating systems, replace the parameters with the values in the following table.

Operating System	Call Object dispatch DLLName	XML Trans dispatch DLLName
AS400	XMLCALLOBJ	XMLTRANS
HP9000B	libxmlcallojb.sl	libxmltransactions.lo
Sun or RS6000	libxmlcallojb.so	libxmltransactions.so

Change the following block:

[JDENET]serviceNameListen=6009serviceNameConnect=6009maxNetProcesses=5maxNetConnections=400
maxKernelProcesses=50
maxKernelRanges=15
netTrace=1
ServiceControlRefresh=5
MonitorOption=0 0 0 0 0 0 0 0

Change maxKernelRanges to 15.

For more information on establishing your J.D. Edwards OneWorld environment for XML support, see "Setting the jde.ini File for XML" in the J.D. Edwards Interoperability Guide for OneWorld XE.