2 Configuring OracleAS Adapter for J.D. Edwards One World

Configuring BSE

After BSE is deployed to Oracle Application Server, you can configure it through the BSE configuration page.

To configure BSE:

1. Display the following page in your browser:

   http://hostname:port/ibse
   
   

Where hostnameis the hostname of Oracle Application Server andportis the HTTP port for Oracle Application Server.

For example,

http://localhost:7777/ibse

2. When prompted, log on.

   When first installed, the user ID and the password are:

   • User name: iway

   • Password: iway

The BSE configuration page is displayed.

3. Ensure that the Adapter Lib Directory parameter specifies the path to the lib directory, for example:

   OracleAS_home\adapters\application\lib
   
   

After you specify the path, adapters in the lib directory are available to BSE.

4. For security purposes, enter a new password in the Admin Password field.

5. Click Save.

Configuring BSE System Settings

To configure BSE system settings:

1. Display the BSE configuration page by entering the following URL:

   http://hostname:port/ibse/IBSEConfig
   

WhereHostname is the machine where BSE is installed and port is the port number on which BSE is listening.

Note: The server to which BSE is deployed must be running.

The BSE configuration page is displayed, as shown inthe following figure.

Description of the illustration system.gif

2. Configure the system settings according to the information in the following table.

   1. Parameter	Description
      Language	Specify the required language.
      Adapter Lib Directory	enter the full path to the directory where the adapter jar files reside
      Encoding	Specify the default encoding from one of the following options: UTF-8 EBCDIC-CP-US ISO-88859-1 Shift JIS UNICODE
      Debug Level	Specify the debug level from one of the following options: None Fatal Error Warning Info Debug
      Number of Async. Processors	Select the number of asynchronous processors.

      
      

The following image shows the Security pane of the BSE configuration page.

Description of the illustration security.gif

3. Configure the security settings according to the information in the following table.

Parameter	Description
Admin User	Provide a BSE administrator ID.
Admin Password	enter the password associated with the BSE administrator ID.
Policy	Select the check box to enable policy security.

The following image shows the Repository pane of the BSE configuration page.

Description of the illustration repository.gif

BSE requires a repository to store transactions and metadata required for the delivery of Web services. For more information, see "Configuring a File System Repository" and "Configuring an Oracle Repository".

4. Configure the repository settings according to the information in the following table.

Parameter	Description
Repository Type	Select one of the following repositories from the list: Oracle. File. (Do not use a file repository for BSE in production environments.)
Repository URL	Enter the URL to use when opening a connection to the database.
Repository Driver	Provide the driver class to use when opening a connection to the database (optional).
Repository User	Enter the user ID to use when opening a connection to the database.
Repository Password	Enter the password associated with the user ID.
Repository Pooling	Select the check box to enable pooling.

5. Click Save.

Configuring a File System Repository

If you do not have access to a database for the repository, you can store repository information in an XML file on your local machine. However, a file system repository is less secure and efficient than a database repository. When BSE is first installed, it is automatically configured to use a file system repository.

Note: Do not use a file repository for BSE in production environments.

The default location for the repository on Windows is:

OracleAS_home\config\base\ibserepo.xml

On other platforms, use the corresponding location.

If you are using a file system repository, you are not required to configure any additional BSE components.

Configuring an Oracle Repository

To configure an Oracle repository:

1. Contact your database administrator to obtain an Oracle user ID and password to create the BSE repository.

   This user ID should have rights to create and modify tables as well as the ability to create and execute stored procedures.

2. Open a command prompt and navigate to the setup directory. Its default location on Windows is:

OracleAS_home\iWay55\etc\setup

For other platforms, see the corresponding location.

This directory contains SQL to create the repository tables in the following file:

iwse.ora

3. Enter the following command:

sqlplus userid/password @database @ iwse.ora

Configuring J2CA

During the J2CA deployment of OracleAS Adapter for J.D. Edwards OneWorld, OC4J generates a deployment descriptor called oc4j-ra.xml. This descriptor provides OC4J-specific deployment information for resource adapters. See Chapter 3, "OC4J Deployment and Integration" for more information on J2CA deployment and configuration.

No configuration changes are necessary if you are using the default file based repository with J2CA deployment.

Configuring a Database Repository for J2CA

To configure a database repository for J2CA:

1. Execute the iwse.ora SQL statement on the machine where the database is installed.

2. Copy the jcatransport.properties file to the following directory:

   OracleAS_home\adapters\application\config\jca_sample
   
   

3. Uncomment the following fields and enter details for them in the jcatransport.properties file. For example:

   iwafjca.repo.url=jdbc:oracle:thin:@90.0.0.51:1521:orcl
   iwafjca.repo.user=scott
   iwafjca.repo.password=scott1
   
   

4. Alter the JDBC driver path in Application Explorer's lcp. For example:

   lcp=..\lib\orabpel-adapters.jar;C:\jdev\jdbc\lib\classes12.jar;C:\jdev\jdbc\lib\nls_charset12.jar;%lcp%
   to
   lcp=..\lib\orabpel-adapters.jar;..\..\..\jdbc\lib\classes12.jar;..\..\..\jdbc\lib\nls_charset12.jar;%lcp%
   
   

Creating a Configuration for BSE

To create a configuration for BSE using Application Explorer, you must first define a new configuration.

Defining a New Configuration for BSE

To define a new configuration for BSE:

1. Right-click Configurations and select New.

   The New Configuration dialog box is displayed.

   
   Description of the illustration ibsenewconfig1.gif
   
   

2. Enter a name for the new configuration (for example, SampleConfig) and click OK.

   The New Configuration dialog box is displayed.

   
   Description of the illustration ibseconfig.gif
   
   

3. From the Service Provider list, select iBSE.

4. In the BSE URL field, accept the default URL or replace it with a different URL with the following format:

   http://hostname:port/
   
   

Where hostname is the machine where your application server resides.

5. Click OK.

   A node representing the new configuration appears beneath the root Configurations node.

   
   Description of the illustration newconfig1a.gif
   
   

Creating a Configuration for J2CA

To create a configuration for J2CA using Application Explorer, you must first define a new configuration.

Defining a New Configuration for J2CA

To define a new configuration for J2CA:

1. Right-click Configurations and select New.

   The New Configuration dialog box is displayed.

2. Enter a name for the new configuration (for example, myConfig) and click OK.

   
   Description of the illustration jcaconfig.gif
   
   

3. From the Service Provider list, select JCA.

4. In the Home field, enter a path to your J2CA configuration directory where the repository, schemas, and other information is stored, for example:

   OracleAS_home\adapters\application
   
   

5. Click OK.

   A node representing the new configuration appears beneath the root Configurations node.

   
   Description of the illustration newconfig1a.gif
   
   

Connecting to a New Configuration

To connect to a new configuration:

1. Right-click configuration to which you want to connect, for example, myConfig.

2. Select Connect.

Nodes appear for Adapters, Events, and Business Services (also known as Web services).

• Use the Adapters folder to create inbound interaction with J.D. Edwards. For example, you use the J.D. Edwards node in the Adapters folder to configure a service that updates J.D. Edwards.

• Use the Events folder to configure listeners that listen for events in J.D. Edwards OneWorld.

• Use the Business Services folder (available for BSE configurations only) to test Web services created in the Adapters folder. You can also control security settings for the Web services by using the security features of the Business Services folder.

You are now ready to define new targets to J.D. Edwards OneWorld.

Defining a Target to J.D. Edwards OneWorld

To connect to an application system for the first time, you must define a new target.

To define a target:

1. In the left pane, expand the Adapters node.

   The applications systems supported by Application Explorer appear as nodes based on the adapters that are installed.

2. Right-click JDEdwards node and select Add Target.

   The Add Target dialog box is displayed.

   
   Description of the illustration add_target.gif
   
   

   Perform the following steps:

   1. In the Name field, enter a descriptive name, for example, JDEConnection.

   2. In the Description field, enter a description for the target (optional).

   3. From the Target Type list, select JDE One World.

3. Click OK.

   The JDE One World dialog box appears.

   1. On the Repository tab, enter the path to the GenJava repository.

      This is the location of the Java files created by the GenJava program.

      
      

      Note: Generating agent schemas requires the GenJava repository. For more information on building the J.D. Edwards OneWorld Master Business Function repository, see the J.D. Edwards Interoperability Guide for OneWorld Xe.

      
      

   2. Click the Logon tab and enter the appropriate information for your target type based on the information in the following table. Fields with an asterisk are required.

   
   Description of the illustration logon_tab.gif
   
   

   Parameter	Description
   User id*	A valid user ID for J.D. Edwards OneWorld.
   User password*	The password associated with the user ID.
   JDE environment*	The J.D. Edwards OneWorld environment, for example, DU7333. For more information about this parameter, see your J.D. Edwards OneWorld documentation or ask your OneWorld system administrator.
   Application	XMLInterop or the application name in J.D. Edwards OneWorld. Optional.
   Server IP address*	The name of the server on which J.D. Edwards OneWorld is running. This can be the name of the server, for example, JDEOW, or its IP address, for example, 123.45.67.89.
   Server Port*	The port number on which the server is listening, for example, 6009.

   
   

4. Click OK.

   After the extraction finishes, the new target, JDEConnection, appears under the JDEdwards node.

   
   Description of the illustration jdeconnection.gif
   
   

   For information on how to create schemas for the adapter, see "Creating an XML Schema".

Connecting to a Defined J.D. Edwards OneWorld Target

To connect to a target:

1. Expand the Service Adapters node.

2. Expand the JDEdwards node.

   The disconnected target is displayed.

   
   Description of the illustration jde_jdeconnection1.gif
   
   

3. Click the target name (for example, JDEConnection) under the JDEdwards node.

   The Connection dialog box displays the values you entered forconnection parameters.

4. Verify your connection parameters.

5. Provide the correct password.

6. Right-click the target name and select Connect.

   The x icon disappears, indicating that the node is connected.

   
   Description of the illustration jde_jdeconnection2.gif
   
   

Disconnecting from J.D. Edwards OneWorld

To disconnect from a target:

1. Expand the Adapters node.

2. Expand the JDEdwards node.

3. Right-click the target to which you are connected (for example, JDEConnection), and select Disconnect.

   The x icon appears, indicating that the node is disconnected.

   
   Description of the illustration jde_jdeconnection1.gif
   
   

Editing a Target

To edit a target:

1. In the left pane, ensure the target you wish to edit is disconnected.

2. Right-click the target and select Edit.

   The Edit pane is displayed on the right.

3. Modify the target information.

4. Click OK.

Deleting a Target to J.D. Edwards OneWorld

You can delete a target, rather than just disconnecting and closing it. When you delete the target, the node disappears from the list of J.D. Edwards OneWorld targets in the left pane of the explorer.

1. Expand the Adapters node.

2. Expand the JDEdwards node.

3. Right-click the target to which you are connected (for example, JDEConnection), and select Delete.

   The node disappears from the list of available connections.

For information on how to view application system objects, see the J.D .Edwards Interoperability Guide Release OneWorld XE.

Creating a Request and a Response Schema

The following procedure explains how to create request and response schemas for a J.D. Edwards OneWorld business function. Application Explorer enables you to create XML schemas for this function.

1. Connect to a J.D. Edwards OneWorld target as described in "Connecting to a Defined J.D. Edwards OneWorld Target".

2. Expand the Services node.

3. Expand the node of the Master Business Function (MBF) for which you want to create the schema.

4. Expand and then select the node beneath the MBF.

   The following image shows the tabs that appear on the right.

   
   Description of the illustration jde_schema1.gif
   
   

5. Click the parameters tab to view the parameter information.

   
   Description of the illustration jde_parameters.gif
   
   

6. Click Request Schema to view the request schema information.

   
   Description of the illustration jde_schemarequest.gif
   
   

7. Click Response Schema to view the response schema information.

   
   Description of the illustration jde_schemaresponse.gif
   
   

Using GenJava to Generate a Schema

To create schemas for the adapter, you must use GenJava wrappers. You create the GenJava wrappers using the OneWorld utility called GenJava. You use Application Explorer to generate schemas against OneWorld GenJava wrappers. GenJava is supplied as a command line process with several run-time options. For more information on GenJava, see the J.D. Edwards Interoperability Guide for OneWorld Xe.

Generating Web Service Definition Language (WSDL) (J2CA configurations only)

The process of generating WSDL for request-response (outbound) services differs from that of generating WSDL for event notification (inbound) J2CA services of the adapter. See the following sections for more details.

Generating WSDL for Outbound Interaction

To generate a WSDL file for request-response service:

1. Start Application Explorer and connect to a defined J.D. Edwards target.

2. Expand Services > JDEJAVA_CFIN > B0100033, and select GetEffectiveAddress.

3. Right-click GetEffectiveAddress.

   The following menu is displayed.

   
   Description of the illustration wlae_exportwsdl.gif
   
   

4. Select Create Outbound JCA Service (Request/Response).

   The Export WSDL dialog box is displayed.

   
   Description of the illustration wlae_exportwsdl2.gif
   
   

5. Accept the default name and location for the file.

   The .wsdl file extension is added automatically. By default, the names of WSDL files generated for request-response services end with _invoke, while those generated for event notification end with _receive.

   
   

   Note: You can organize your WSDL files in subfolders, creating your own WSDL hierarchy structure. Create the folders under OracleAS_home\adapters\application\wsdls\. The WSIL browser in JDeveloper will display the full tree structure of your WSDL hierarchy.

   
   

6. Click OK.

   The WSDL file is saved in the specified location.

Generating WSDL for Inbound Interaction

You can create inbound J2CA service only if the node you have selected supports events. To generate a WSDL file:

1. Verify that orabpel-adapters.jar is in your classpath.

2. Run obadapter.bat to set the environment.

3. From the Windows Start menu, select OraBPELPM_Home > Oracle BPEL Process Manager > Developer Prompt.

4. At the prompt, enter the following command:

   java oracle.tip.pc.infra.wsil.IWayWSILBrowser jcaHome\jcaConfig adapter target channel schemaPrefix wsdlFileName
   
   

   Where:

   • jcaHome is the path to your J2CA configuration

   • jcaConfig is the directory where your J2CA configuration is saved

   • adapter is the name of the adapter

   • target is the name of the target you are connected to in Application Explorer

   • channel is the name of the channel you have selected in Application Explorer

   • schemaPrefix is the prefix of your schema

   • wsdlFileName is the name of your WSDL file

   For example:

   I:\oracle\AS\adapters\application\tools>java oracle.tip.pc.infra.wsil.IWayWSILBrowser
   I:\oracle\AS\adapters\application\
   jca_sample JDEdwards JDE_target JDE_channel SalesOrder SalesOrder.wsdl
   
   

It is good practice to append _receive to the names of WSDL files generated for event notification services. This will allow you to easily differentiate between them and those generated for request-response services.

Creating an Event Port

You must create event ports from the Events node in Application Explorer.

Creating a Channel

The following procedure describes how to create a channel for your event. All defined event ports must be associated with a channel.

To create a channel:

1. Click Event Adapters.

2. Expand the JDEdwards node.

   The ports and channels nodes appear in the left pane.

3. Right-click Channels and select Add Channel.

   The Add Channel dialog box is displayed.

   
   Description of the illustration jde_addchannel1.gif
   
   

   Perform the following steps:

   1. Enter a name for the channel, for example, NewChannel.

   2. Enter a brief description.

   3. From the Disposition Protocol list, select TCP Listener.

   4. Select an event port from the list of available ports. To select more than one, hold down the Ctrl key and select the ports.

   5. Click >> to transfer the port(s) to the list of selected ports.

4. Click Next.

   The TCP Listener dialog box is displayed with the Basic tab active. Perform the following steps:

   1. Enter the parameters that are specific to your J.D. Edwards environment.

   2. Click the preparser tab.

   3. Enter the required parameters.

   The following table lists the parameters with their descriptions. Parameters with an asterisk are required.

   Parameter	Description
   Host*	Name or URL of the machine where the database resides.
   Port Number*	Port on which the Host database is listening.
   Synchronization Type	Possible values are: RECEIVE_REPLY RECEIVE_ACK RECEIVE
   Is Length Prefix	For J.D. Edwards OneWorld events that send data back that is not in XML format. The TCP/IP event application must prefix the data with a 4-byte binary length field when writing the data to the TCP/IP port.
   Is XML	For J.D. Edwards OneWorld events that send data back in XML format. No preparser is required.
   Is Keep Alive	Maintains continuous communication between the event transaction and the channel.
   User id*	A valid user ID for J.D. Edwards OneWorld.
   User password*	The password associated with the user ID.
   JDE Environment*	The J.D. Edwards OneWorld environment, for example, DU7333. For more information about this parameter, see your J.D. Edwards OneWorld documentation or ask your OneWorld system administrator.
   Application	XMLInterop or the application name in J.D. Edwards OneWorld. Optional.
   Server IP address*	Name of the server on which J.D. Edwards OneWorld is running. This can be the name of the server, for example, JDEOW, or its IP address, for example, 123.45.67.89.
   Server port*	Port number on which the server is listening, for example, 6009.

   
   

   For additional parameters, see your J.D. Edwards OneWorld Administrator.

5. Click OK.

   The channel appears under the channels node in the left pane.

   An X over the icon indicates that the channel is currently disconnected. You must start the channel to activate your event configuration.

   
   

   Note: If you are planning to integrate OracleAS Adapter for J.D. Edwards OneWorld with BPEL Process Manager, do not start the channel, as it is managed by the BPEL PM Server. If you start the channel for testing and debugging purposes, stop it before runtime.

   
   

6. Right-click the channel node and select Start.

   The channel becomes active.

   
   Description of the illustration app_exp_channelactive.gif
   
   

   The X over the icon disappears.

7. To stop the channel, right-click the connected channel node and select Stop.

   The channel becomes inactive and an X appears over the icon.

Editing a Channel

To edit a channel:

1. In the left pane, locate the channel you want to edit.

2. Right-click the channel and select Edit.

   The Edit channels pane is displayed.

3. Make the required changes to the channel configuration and click Finish.

Deleting a Channel

To delete a channel:

1. In the left pane, locate the channel you want to delete.

2. Right-click the channel and select Delete.

   A confirmation dialog box is displayed.

3. To delete the channel you selected, click OK.

   The channel disappears from the list in the left pane.

The OneWorld Event Listener

Oracle Application Server 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 in conjunction 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.

Configuring the OneWorld Event Listener

The OneWorld Event Listener is installed as part of the basic installation. The OneWorld Adapter is automatically installed in the appropriate directory. If the integration server is not installed on the same computer as the J.D. Edwards application server, you must configure the OneWorld Event Listener. For more information, see the J.D. Edwards Interoperability Guide for OneWorld.

The OneWorld Event Listener is started by J.D. Edwards for specific business functions as configured in the OneWorld environment.The OneWorld Event listener includes the following components:

• The listener exit (IWOEvent).

  The file extension you use depends on your operating system, for example, for Windows, the exit is IWOEvent.dll.

• The listener configuration file (iwoevent.cfg).

• The outbound agent (XDJdeOutboundAgent).

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 outbound agent. The OneWorld Event listener is deployed under the J.D. Edwards OneWorld Server. The Java class for the OneWorld Event listener is called IWOEvent (the file extension depends on the operating system) and is case-sensitive.

Alias.aliasname={ipaddress|dsn}:port, trace={on|off}

trans.jdeTransactionName=alias1,alias2,aliasn

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.JDESOW=edamcs1t,edamcs2
trans.JDEPOOUT=edamcs1