This appendix describes how to configure Oracle Application Adapter for J.D. Edwards OneWorld.
This appendix contains the following topics:
This section describes the settings that are required in the JDE.INI file for the XML call object kernel (outbound and inbound processing).
The JDE.INI file is located in the following directory on the Enterprise Server:
\\system\bin32
Open the JDE.INI file and modify the [JDENET_KERNEL_DEF6] and [JDENET_KERNEL_DEF15] sections as follows:
[JDENET_KERNEL_DEF6]krnlName=CALL OBJECT KERNELdispatchDLLName=XMLCallObj.dlldispatchDLLFunction=_XMLTransactionDispatch@28maxNumberOfProcesses=1numberOfAutoStartProcesses=1
[JDENET_KERNEL_DEF15]krnlName=XML TRANSACTION KERNELdispatchDLLName=XMLTransactions.dlldispatchDLLFunction=_XMLTransactionDispatch@28maxNumberOfProcesses=1numberOfAutoStartProcesses=1
The parameters containing an underscore (_) and @28 are for Windows NT 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 |
Note:
The J.D. Edwards OneWorld installation for version B7333(XE) does not include [JDENET_KERNEL_DEF15]. As a result, if you are using version B7333(XE), you must manually add it to the jde.ini file. For all other J.D. Edwards OneWorld versions, [JDENET_KERNEL_DEF15] is included with the installation.Oracle Application Adapter for J.D. Edwards OneWorld Event Listener is designed specifically to provide J.D. Edwards approved access to your OneWorld business events. The OneWorld Event Listener refers to a specialized application that runs with OneWorld business functions and is called by the OneWorld application system.
The OneWorld application system provides the Event Listener with the information required to retrieve the event information for only the desired events. For information about configuring the OneWorld environment, see the J.D. Edwards Interoperability Guide for OneWorld.
The OneWorld Event Listener is called directly from the OneWorld application and is passed a Z-file record identifier. This identifier then generates a request document that is passed to the server for processing. The server retrieves the event information from the J.D. Edwards OneWorld system and propagates the information for integration with other application systems.
The OneWorld Event Listener is installed as part of the Oracle Application Adapters installation. The OneWorld Event Listener supports TCP/IP and HTTP protocols.
The OneWorld Event Listener is invoked by J.D. Edwards for specific transactions as configured in the OneWorld environment.
The OneWorld Event Listener includes the following components:
The listener exit (IWOEvent), located under the \etc\jde directory. For example:
C:\oracle\Middleware\home_0309\Oracle_SOA1\soa\thirdparty\ApplicationAdapters\etc\jde\iwoevent.dll
The file extension varies depending on your operating system:
For Windows, the exit is iwoevent.dll.
For Sun Solaris, the exit is libiwoevent.so.
For HP-UX, the exit is libiwoevent.sl.
For AS/400, the exit is iwaysav.sav.
For IBM AIX, the exit is libiwoevent.so.
The listener configuration file (iwoevent.cfg), which must be created by the user.
The OneWorld Event listener exit is the function that passes the key fields for a record in the OneWorld outbound transaction tables to the integration server for processing by the inbound Oracle Application Adapter for J.D. Edwards OneWorld. The OneWorld Event listener is deployed under the J.D. Edwards OneWorld Enterprise Server. The Java class for the OneWorld Event listener is called IWOEvent (the file extension depends on the operating system) and is case-sensitive.
Create a folder called Outbound under the JDE structure on the JDE Enterprise Sever, for example:
\\JDEdwards\E812\DDP\Outbound
Copy the iwoevent.dll file in the new Outbound folder.
Create an environment variable, IWOEVENT_HOME, to point to the directory containing the iwoevent.dll file.
On Windows: Add IWOEVENT_HOME to the system environment variables.
On UNIX: Add the following command to your start-up script:
export IWOEVENT_HOME =/directory_name
On the J.D. Edwards OneWorld Server, create an iwoevent.cfg file in the defined directory, IWOEVENT_HOME.
The OneWorld Event listener requires connection information for the associated adapter to initiate events properly. This information is contained in the iwoevent.cfg file. You must create this file and add the connection information to it. The OneWorld Event Listener requires connection information for the associated integration server to function properly. This information is contained in the iwoevent.cfg file. The iwoevent.cfg file has three distinct sections:
Common
The common section of the configuration file contains basic configuration options. Currently, only the trace option is supported.
To set the trace option, select on or off.
common.trace=on|off
Where on sets the tracing to on and off sets the tracing to off. Off is the default value.
By default, the OneWorld Event listener supports TCP/IP. To activate the HTTP protocol for this listener, add the following line:
common.http=on
The alias section of the configuration file contains the connection information required to send transactions to specific servers. Currently, the Oracle Application Adapter for J.D. Edwards OneWorld supports 100 entries (alias names) in the configuration file.
The alias values to these entries are as follows:
Alias.aliasname={ipaddress|dsn}:port, trace={on|off}
aliasname is the symbolic name given to the connection.
ipaddress|dsn is the IP address or DSN name for the server containing Oracle Application Adapter for J.D. Edwards OneWorld (required).
port is the port defined for Oracle Application Adapter for J.D. Edwards OneWorld in the TCP channel configuration (required).
trace={on|off} sets the tracing to on for the particular alias.
Trans
The trans section of the configuration file contains transaction information required to route J.D. Edwards OneWorld transactions to specified servers. If a particular J.D. Edwards OneWorld transaction is not defined to an alias, it is sent to all aliases. The trans values to these entries are as follows:
trans.jdeTransactionName=alias1,alias2,aliasn
Where jdeTransactionName is the JDE-defined name for the outbound transaction and alias1,alias2,aliasn is the list of aliases to which the transactions are sent.
The following is a sample entry for iwoevent.cfg that supplies connection information:
common.trace=on alias.edamcs1=172.1.1.1:3694 alias.edamcs1t=172.1.1.1:3694, trace=on alias.edamcs2=222.2.2.2:1234 trans.JDESOOUT=edamcs1t,edamcs2 trans.JDEPOOUT=edamcs1
Create a folder using the alias names that are specified in the iwoevent.cfg file under the defined directory, IWOEVENT_HOME. For example:
\\JDEdwards\E812\DDP\Outbound\edamcs1
After OneWorld starts the OneWorld Event listener, the listener accesses the configuration file, called iwoevent.cfg (case-sensitive). Based on the information in the configuration file, the listener sends the event notification to the integration server. All log information is saved in a file called iwoevent.log. The iwoevent.log file is created in the outbound folder where the iwoevent.dll and iwoevent.cfg files are located.