A Configuring J.D. Edwards OneWorld for Outbound and Inbound Processing

Using the GenJava Development Tool (Outbound Processing)

This section describes how to use the GenJava development tool, which is used to create Java wrappers for accessing the J.D. Edwards OneWorld business functions. The OracleAS Adapter for J.D. Edwards OneWorld uses these wrappers to call the J.D. Edwards OneWorld business functions.

J.D. Edwards OneWorld provides a Java Generation tool called GenJava that you can use to expose OneWorld business functions externally as Java class files. A J.D. Edwards OneWorld system administrator usually runs the GenJava tool.

During GenJava operation, you must specify a library of business functions, for example CALLBSFN. GenJava creates the associated Java class files for the business functions and related data structures. GenJava also compiles the business functions, generates Java documents, and packages them into two .JAR files. One .JAR file contains Java classes and the second .JAR file contains Java documents.

For example, if the business function library you specified in GenJava is CALLBSFN, you will find the following files in the <install>\system\classes directory or any user-specified directory redirected by GenJava:

• JDEJAVA_CALLBSFN.xml

• JDEJAVA_CALLBSFNInterop.jar

• JDEJAVA_CALLBSFNInteropDoc.jar

Once they are generated, these library files must be added to the CLASSPATH.

GenJava also provides access to J.D. Edwards OneWorld business functions by generating pure Java interfaces for these business functions. GenJava can be generated from a thick client or a deployment server.

Running GenJava

GenJava is located in the <install>\system\bin32 directory. You run GenJava from the command line. There are several GenJava command options that are available.

The following command generates Java wrappers for Category 1 (Master Business Functions), Category 2 (Major Business Functions), Category 3 (Minor Business Functions), and Category - (Uncategorized Business Functions) in the CALLBSFN library:

GenJava /Cat 1 /Cat 2 /Cat 3 /Cat - CALLBSFN

The following command runs with a JDEScript file and prompts a J.D. Edwards OneWorld log on window, where you must enter a valid user ID, password, and environment:

GenJava /cmd .\AddressBook.cmd

The contents of the resulting AddressBook.cmd file are shown as follows:

define library CALLBSFNloginlibrary CALLBSFNinterface AddressBookimport B0100031import B0100019import B0100032import B0100002import B0100033buildlogout

GenJava generates the wrappers (CALLBSFNInterop.jar, CALLBSFNInteropDoc.jar, and CALLBSFN.xml) in Java for all business functions that are imported in the script file.

Specifying Inbound Functionality for a Business Function

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

Configuring J.D. Edwards OneWorld Inbound Processing

This section describes how to configure J.D. Edwards OneWorld inbound processing using the J.D. Edwards OneWorld Enterprise Server.

Configuring Custom Functions

To configure custom functions:

1. Create a folder called Outbound under the JDE structure on the JDE Enterprise Sever, for example:

   \\ JDEdwards\E812\DDP\Outbound
   

2. Copy the iwoevent.dll and iwoevent.cfg files in the new Outbound folder.

   The following is a sample iwoevent.cfg file that is provided as an example:

   common.trace=onalias.iwserv14=172.30.162.48:1236, trace=ontrans.JDESOOUT=iwserv14
   

   Currently, the OracleAS Adapter for J.D. Edwards OneWorld supports 100 entries (alias names) in the configuration file.

3. Create a folder using the alias names that are specified in the iwoevent.cfg file under the following directory:

   \\ JDEdwards\E812\DDP\Outbound
   

4. Make the following changes to your environment variables:

   1. Create a new variable called JAVA_HOME.

   2. Set this to the location of your JDK installation location, for example, D:\jdk1.3.

   3. Add the following to your PATH variable:

      %JAVA_HOME%\bin; %JAVA_HOME%\jre\bin; %JAVA_HOME%\jre\bin\classic;
      

   4. Create a new variable called IWOEVENT HOME.

      The value should be set to the full path of the Outbound directory, for example:

      D:\JDEdwards\E812\DDP\Outbound
      

5. Modify [JDENET_KERNEL_DEF6] in the JDE.INI file, which is located in the \\system\bin32 directory on the JDE Enterprise Server, by adding the following section:

   [JDENET_KERNEL_DEF15]krnlName=XML TRANSACTION KERNELdispatchDLLName=XMLTransactions.dlldispatchDLLFunction=_XMLTransactionDispatch@28maxNumberOfProcesses=1numberOfAutoStartProcesses=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

   
   

Subscribing to Inbound Transactions

The flow of inbound data to third parties is controlled through the Data Export Controls application. For each transaction type and order type, one or more records can be defined with different function names and libraries.

1. Type P0047 in the Fast Path field and press Enter.

   
   

   The Work With Data Export Controls window opens.

   
   

2. Click Add.

   The Data Export Control Revisions window opens. Notice that the sequence (Seq) number automatically increments for each new line.

   
   

3. Perform the following steps:

   1. Type JDESOOUT in the Transaction field.

   2. Type SO in the Order Type field.

   3. Type NotifyOnUpdate in the first row of the Function Name column.

   4. Type the absolute path to the location of the iwoevent.dll file in the first row of the Function Library column, for example:

      D:\JDEdwards\E812\DDP\Outbound\iwoevent.dll
      

   5. Type 1 in the first row of the Execute for Add column if you want the notifications for add/insert.

   6. Make the same decision for update, delete, and inquiry and type 1 in the appropriate column.

   7. Type 1 in the Launch Immediately column to launch the Outbound Subsystem batch process (R00460).

4. Click OK.

   
   

Starting the Outbound Scheduler Subsystem Process (R00460)

Once you have finished defining one or more records for each transaction type and order type, you must manually start the outbound scheduler subsystem process.

1. Type BV in the Fast Path field and press Enter.

   
   

   The Work With Batch Versions - Available Versions window opens.

   
   

2. Type R00460 in the Batch Application field and click Find.

   
   

3. Select Interoperability Generic Outbound Subsystem UBE (XJDE0001) and click Select.

   The Version Prompting window opens.

   
   

4. Click Submit.

   
   

5. Navigate to the last screen and click OK.

Verifying the Subsystem Process

This section describes how to verify the outbound scheduler subsystem processs.

1. Type WSJ in the Fast Path field and press Enter.

   
   

   The Work With Server (Subm Jobs) window opens.

   
   

2. Select a corresponding server from the table.

3. Click Row from the menu bar and select Subsystem Jobs.

   
   

4. Click Find.

   
   

5. Verify that R is listed in the Job Status column.

Configuring P4210 (Sales Order) to Trigger an Event

This section describes how to configure a P4210 (Sales Order) to trigger an event.

1. Type IV in the Fast Path field and press Enter.

   
   

   The Interactive Versions window opens.

   
   

2. Type P4210 in the Interactive Application field and click Find.

   
   

3. Select a document version from the table, for example, RIS0001 - Sales Order Entry - SO Order Type.

4. Click Row from the menu bar and select Processing Options.

   The Processing Options dialog box opens.

   
   

5. Click the Interop tab.

6. Type JDESOOUT in the Transaction Type field.

7. Add Sales Order.

Verifying the Configuration Steps

This section describes how to verify the configuration steps by updating F0046.

1. Type P0046 in the Fast Path field and press Enter.

   
   

   The P0046 - Work With Processing Log window opens.

   
   

2. Click Find.

   The following data is displayed.

   
   

3. Search for the corresponding transaction.

   The iwoevnt.log file is created in the following directory:

   \\iwJDE812\JDEdwards\E812\DDP\system\bin32
   

   The iwoevent.log file is created in the outbound folder where the iwoevent.dll and iwoevent.cfg files are located. The following is an example of the event log file:

   Event call begin...Server time      : Tue May 27 07:23:55 2008userId           : JDE       batchNumber      : 15205          transactionNumber: 103494                lineNumber       : 1.000000transactionType  : JDESOOUTsequenceNumber   : 1.000000Request xml:========================<? xml version="1.0" encoding="UTF-8"?><jde><request><connection><dsn /><user /><password /><sp><proc>JDESOOUT</proc><data><ediUserId>JDE       </ediUserId><ediBatchNumber>15205          </ediBatchNumber><ediTransactionNumber>103494                </ediTransactionNumber></data></sp></connection></request></jde>========================