Oracle® Application Server Adapter for J.D. Edwards OneWorld User's Guide 10g Release 2 (10.1.2) B14059-03 |
|
![]() Previous |
![]() Next |
This chapter describes how to use OracleAS Adapter Application Explorer (Application Explorer) to define a target to connect to a J.D. Edwards OneWorld system, view system objects, and create XML schemas and Web services. This chapter also explains how to configure an event adapter.
This chapter discusses the following topics:
Establishing a Connection (Target) for J.D. Edwards OneWorld
Creating and Testing a Web Service (BSE Configurations Only)
To start Application Explorer:
Start the server where Application Explorer is deployed.
From the Windows Start menu, select Programs, OracleAS_home Adapters, and then Application Explorer.
On Windows, iaexplorer.bat
is located under OracleAS_home
\adapters\application\tools
, where OracleAS_home
is the directory where Oracle Application Server is installed.
On UNIX, load the iwae script, iwae.sh
, located under OracleAS_home
/adapters/application/tools
, where OracleAS_home
is the directory where Oracle Application Server is installed.
Application Explorer starts. You can now define new targets to your Enterprise Information System (EIS).
Before a repository configuration can be created, you must configure OracleAS Adapter Business Services Engine (BSE). You need not configure the Connector for J2CA because the ra.xml
file is configured automatically during installation.
After BSE is deployed to Oracle Application Server, you can configure it through the BSE configuration page.
To configure BSE:
Display the following page in your browser:
http://hostname:port/ibse
Where hostname
is the host name of Oracle Application Server andport
is the HTTP port for Oracle Application Server.
For example,
http://localhost:7777/ibse
Note: The first time you access this page, it may take time to load. |
Log on when prompted.
When first installed, the user ID and the password are:
User name: iway
Password: iway
The BSE configuration page is displayed.
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.
Note: The Repository URL field specifies where the file system repository is located. To use a database repository, you must enter the repository connection information. For the initial verification, use a file system repository. See "Configuring an Oracle Repository" for information on switching to a database repository. |
Click Save.
To configure BSE system settings:
Display the BSE configuration page by entering the following URL in a browser:
http://hostname:port/ibse/IBSEConfig
Where hostname
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 in the following figure.
Configure the system settings according to the information in the following table.
The following image shows the Security pane of the BSE configuration page.
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.
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".
Configure the repository settings according to the information in the following table.
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:
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.
Open a command prompt and navigate to the setup directory. Its default location on Windows is:
OracleAS_home
\iWay55\etc\setup
For other platforms, navigate to the corresponding location.
This directory contains SQL to create the repository tables in the following file:
iwse.ora
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:
Execute the iwse.ora
SQL statement on the machine where the database is installed.
Copy the jcatransport.properties
file to the following directory:
OracleAS_home\adapters\application\config\jca_sample
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
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%
Before you use Application Explorer with OracleAS Adapter for J.D. Edwards OneWorld, you must create a repository configuration. You can create two kinds of repository configurations, Web services and J2CA, depending on the container to which the adapter is deployed. During design time, the repository is used to store metadata created when using Application Explorer to configure adapter connections, browse EIS objects, configure services, and configure listeners to listen for EIS events. The information in the repository is also referenced at runtime.
A default J2CA repository is created for the default ManagedConnectinFactory. The name of this configuration is jca_sample
.
See "Adapter Features" for more information.
To create a repository 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:
Right-click Configurations and select New.
The New Configuration dialog box is displayed.
Enter a name for the new configuration (for example, myConfig) and click OK.
The New Configuration dialog box is displayed.
In the iBSE URL field, accept the default URL or replace it with a different URL using the following format:
http://hostname:port/ibse/IBSEServlet
Where hostname
is the machine where your application server resides.
Click OK.
A node representing the new configuration appears beneath the root Configurations node.
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:
Right-click Configurations and select New.
The New Configuration dialog box is displayed.
Enter a name for the new configuration (for example, myConfig) and click OK.
In the Home field, enter a path to your J2CA configuration directory where the repository, schemas, and other information are stored. This configuration directory is located as follows:
OracleAS_home\adapters\application
Click OK.
A node representing the new configuration appears beneath the root Configurations node.
To connect to a BSE or J2CA configuration:
Right-click the configuration to which you want to connect, for example, myConfig.
Select Connect.
Nodes appear for Adapters, Events, and Business Services (also known as Web services). The Business Services node is only available for BSE configurations. If you are connected to a J2CA configuration, you will not see the Business Services node. The following is an example of a BSE configuration named myConfig:
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 can now define new targets to J.D. Edwards OneWorld.
Part of the application definition includes adding a target for the adapter. Setting up the target in Application Explorer requires information which is specific to the target.
To browse the available Master Business Functions (MBF), you must first define a target to the system you use. After you define the target, it is automatically saved. You must connect to the system every time you start Application Explorer or after you disconnect.
When you launch Application Explorer, the left pane displays (as nodes) the application systems supported by Application Explorer, based on the adapters that are installed.
To connect to an application system for the first time, you must define a new target.
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.
Right-click the JDEdwards node and select Add Target.
The Add Target dialog box is displayed.
Perform the following steps:
Click OK.
The JDE One World dialog box appears.
In the Repository tab, enter the path to the GenJava repository in the Repository directory field.
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. |
From the Schema style list, select ELEMENT_STYLE or ATTRIBUTE_STYLE.
Click the Logon tab and enter the appropriate information for your target type based on the information in the following table. Fields marked with an asterisk are required.
Click OK.
After the extraction finishes, the new target, JDEConnection, appears under the JDEdwards node.
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:
Expand the Service Adapters node.
Expand the JDEdwards node.
The disconnected target is displayed.
Click the target name (for example, JDEConnection) under the JDEdwards node.
Click the Logon tab on the right.
The Logon tab displays the values you entered for connection parameters.
Verify your connection parameters.
Provide the correct password.
Right-click the target name and select Connect.
The x icon disappears, indicating that the node is connected.
Disconnecting from J.D. Edwards OneWorld
Expand the Adapters node.
Expand the JDEdwards node.
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.
Editing a Target
In the left pane, ensure that the target you wish to edit is disconnected.
Right-click the target and select Edit.
A window is displayed that enables you to edit the existing connection parameters.
Modify the target information.
Click OK.
Deleting a Target
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.
To delete a target:
Expand the Adapters node.
Expand the JDEdwards node.
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 J.D .Edwards Interoperability Guide Release OneWorld XE.
To execute an MBF, the adapter must receive a request document through the J.D. Edwards OneWorld ThinNet API. The agent processes the request and sends an XML response document indicating the result. Application Explorer creates both the XML request schema and the XML 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.
Connect to a J.D. Edwards OneWorld target as described in "Connecting to a Defined J.D. Edwards OneWorld Target".
Expand the Services node.
Expand the node of the MBF for which you want to create the schema.
Expand and then select the node beneath the MBF.
The following image shows the tabs that appear on the right.
Click the parameters tab to view the parameter information.
Click Request Schema to view the request schema information.
Click Response Schema to view the response schema information.
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 runtime options.
See Also: J.D. Edwards Interoperability Guide for OneWorld Xe |
The procedure for generating WSDL (Web Service Definition Language) for request-response (outbound) services differs from that of generating WSDL for event notification (inbound) J2CA services of the adapter. Each procedure is described in detail in the following sections.
Generating WSDL for Outbound Interaction
To generate a WSDL file for request-response service:
Start Application Explorer and connect to a defined J.D. Edwards target.
Expand Services, JDEJAVA_CFIN, and then B0100033. Select GetEffectiveAddress.
Right-click GetEffectiveAddress.
The following menu is displayed.
Select Create Outbound JCA Service (Request/Response).
The Export WSDL dialog box is displayed.
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 underOracleAS_home \adapters\application\wsdls\ . The WSIL browser in JDeveloper will display the full tree structure of your WSDL hierarchy. |
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:
Create a channel in Application Explorer under the J.D. Edwards events node.
Start the channel.
Important: Do not restart the BPEL PM Server or Oracle Application Server after the channel is started.
Send an inbound message from J.D. Edwards OneWorld.
Capture the inbound message payload in the log file located under OracleAS_home
\adapters\application\config\jca_sample\log
Alternatively, you can create a port with the File protocol under Event in Application Explorer to dispose the event message to the file system.
Use a third party tool such as XMLSpy to create the XSD schema using the XML payload captured in the previous step.
Verify that orabpel-adapters.jar
is in your classpath.
Open a command prompt and change directory to: OracleAS_home
\adapters\application\tools
Run obadapter.bat
to set the environment.
Enter the following command to generate WSDL:
java oracle.tip.pc.infra.wsil.IWayWSILBrowser jcaHome\jcaConfig adapter target channel schemaPrefix wsdlFileName
Where:
jcaHome
is the path to your J2CA configuration. For example, OracleAS_home
\adapters\application\
jcaConfig
is the JCA configuration created in Application Explorer. The default is jca_sample
.
adapter
is the name of the adapter. For example, JDEdwards.
target
is the name of the adapter target you created under Adapter in Application Explorer
channel
is the name of the channel you have created under Event in Application Explorer
schemaPrefix
is the prefix of the XSD schema. The schema file must be in the same directory where the Java command is executed, for example, OracleAS_home
\adapters\application\tools
wsdlFileName
is the name of the WSDL file being created in this procedure
For example:
I:\oracle\AS\adapters\application\tools>java oracle.tip.pc.infra.wsil.IWayWSILBrowser I:\oracle\AS\adapters\application\ jca_sample JDEdwards JDE JDE SalesOrder SalesOrder.wsdl
Note: 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. |
Stop the channel in Application Explorer.
Note: You can organize your WSDL files in subfolders, creating your own WSDL hierarchy structure. Create the folders underOracleAS_home \adapters\application\wsdls\ . The WSIL browser in JDeveloper will display the full tree structure of your WSDL hierarchy. |
The WSDL you generate using Application Explorer is used in a BPEL process as a Partner Link. This is described in detail in "J.D. Edwards OneWorld Event Integration".
You can generate a Web service (also known as a business service) using Application Explorer. You can explore the business function repository and generate Web services for the functions you want to use with the adapter. The following procedure uses an example called BusinessUnitExistenceCheck.
Note: In a J2EE Connector Architecture (J2CA) implementation, Web services are not available. When the adapters are deployed to use J2CA, the Common Client Interface (CCI) provides integration services. |
Creating a Web Service
To create a Web service for a business function:
Expand the JDEdwards node and then the Services node.
Expand the MBF, B1000012, also called BusinessUnitExistenceCheck.
Right-click the node from which you want to create a business service and select Create Web Service.
The Create Web Service dialog box is displayed.
You can add the business function as a method for a new Web service or as a method for an existing one.
From the Existing Service Names list, select either <new service> or an existing service.
In the Service Name field, specify a service name if you are creating a new service. This name identifies the Web service in the list of services under the Business Services node.
Enter a description for the service (optional).
Click Next.
Perform the following steps:
In the License Name field, select one or more license codes to assign to the Web service. To select more than one, hold down the key and click licenses.
In the Method Name field, enter a descriptive name for the method or accept the default name.
In the Description field, enter a brief description of the method (optional).
In the DTD Directory field, specify a location where the Web service will be saved. If you wish to select a location different than the default, click Browse and navigate to the desired location.
Click OK.
Application Explorer switches the view to the Business Services node, and the new Web service appears in the left pane.
Testing a Web Service
After a Web service is created, you can test it to ensure it functions properly. A test tool is provided for testing the Web service.
To test a Web service:
Click the Business Services node to access your Web services.
Expand the Services node.
Select the name of the business service you want to test.
The business service name appears as a link in the right pane.
In the right pane, click the named business services link.
The test option appears in the right pane. If you are testing a Web service that requires XML input, an input field appears.
Enter the appropriate input.
Click Invoke.
Application Explorer displays the results.
Identity Propagation
If you test or execute a Web service using a third party XML editor, for example XMLSPY, the Username and Password values that you specify in the SOAP header must be valid and are used to connect to J.D. Edwards OneWorld. The user name and password values that you provided for J.D. Edwards OneWorld during target creation using Application Explorer are overwritten for this Web service request. The following is a sample SOAP header that is included in the WSDL file for a Web service:
<SOAP-ENV:Header> <m:ibsinfo xmlns:m="urn:schemas-iwaysoftware-com:iwse"> <m:service>String</m:service> <m:method>String</m:method> <m:license>String</m:license> <m:disposition>String</m:disposition> <m:Username>String</m:Username> <m:Password>String</m:Password> <m:language>String</m:language> </m:ibsinfo> </SOAP-ENV:Header>
You can remove the <m:disposition>
and <m:language>
tags from the SOAP header, since they are not required.
Events are generated as a result of activity in a database or in an application system. You can use events to trigger an action in your application. For example, an update to a database can reflect an update to customer information. If your application must perform when this happens, your application is a consumer of this event.
After you create a connection to your application system, you can add events using Application Explorer. To create an event, you must create a port and a channel.
Note: If you are using a J2CA configuration, you must create a new channel for every event and select this channel when you generate WSDL. Additionally, you are not required to create or configure ports for use with BPEL Process Manager. See "J2CA Filtering Port Option for Integration with BPEL Process Manager" for details on using ports under a J2CA configuration. |
A port associates a particular business object exposed by the adapter with a particular disposition. A disposition is a URL that defines the protocol and location of the event data. The port defines the end point of the event consumption. For example, you can use the MSMQ protocol to route the result of a Purchase Order update in the J.D. Edwards OneWorld system to a queue hosted by your application server. See "Creating and Editing an Event Port" for more information.
A channel represents configured connections to particular instances of back-end systems. A channel binds one or more event ports to a particular listener managed by the adapter. See "Creating and Editing a Channel" for more information.
Note: Oracle Containers for J2EE (OC4J) currently conforms to J2CA 1.0, which does not call for event capabilities. When conforming to J2CA 1.0, only service interactions are supported. |
You create event ports from the Events node in Application Explorer.
The following procedure describes how to create an event port for RMI from the Events node using Application Explorer. You can switch between a BSE and a J2CA deployment by choosing one or the other from the menu in the upper right of Application Explorer.
Expand the Events node.
Expand the JDEdwards node.
Right-click Ports and select Add Port.
The Add Port dialog box is displayed.
Perform the following steps:
Enter a name for the event port.
Provide a brief description (optional).
In the URL field, specify a destination file to which the event data is written update the RMI URL. For example:
rmi://myRMI_host:1099;RemoteObject=EISAPP
The following table defines the parameters for the RMI disposition.
Parameter | Description |
---|---|
host | The name of the machine where the EISAPP adapter will be started. |
port | The RMI port on which the iWay bridge is listening. The RMI port is specified in the adapter.ini file of the EISAPP adapter. The default RMI port is 1099. |
RemoteObject | Remote Object is the InterConnect adapter name (EISAPP). This InterConnect EISAPP adapter starts the iWay bridge and the RMI server. The name must be in uppercase. |
Click OK.
The port appears under the ports node in the left pane. In the right pane, a table appears that summarizes the information associated with the event port you created.
You are ready to associate the event port with a channel. For more information, see "Creating and Editing a Channel" .
To edit an event port using Application Explorer:
Expand the Event Adapters node.
Expand the JDEdwards node.
Right-click the event port you want to edit and select Edit.
The Edit Port pane is displayed.
Make the necessary edits and click OK.
This feature provides the option to use event ports when using OracleAS Adapter for J.D. Edwards OneWorld with BPEL PM under a J2CA configuration. Without this feature, all messages from a particular channel are forwarded to the endpoint and then to the BPEL PM Server. In this case, no schema validation takes place. With the filtering feature, you have the option to associate an event schema to a port that you create and configure in Application Explorer. In this case, at runtime the message is validated against the event schema and only the validated event message is forwarded to the endpoint. If the event message does not match the event schema that is associated to the port, then an error message is written to the log and the event message is ignored.
The following procedure describes how to create a channel for your event. All defined event ports must be associated with a channel.
Note: If you are using a J2CA configuration, you must create a new channel for every event and select this channel when you generate WSDL. Creating a channel is required for both BSE and J2CA configurations. |
Creating a Channel
To create a channel:
Expand the JDEdwards node.
The ports and channels nodes appear in the left pane.
Right-click Channels and select Add Channel.
The Add Channel dialog box is displayed.
Perform the following steps:
Enter a brief description.
From the disposition Protocol list, select TCP Listener.
Important: If you are using BPEL Process Manager with a J2CA configuration without the optional port feature, skip the following two steps. See "J2CA Filtering Port Option for Integration with BPEL Process Manager".
Select an event port from the list of available ports. To select more than one, hold down the Ctrl key and select the ports.
Click >> to transfer the port(s) to the list of selected ports.
Click Next.
The TCP Listener dialog box is displayed with the Basic tab active. Perform the following steps:
Enter the parameters that are specific to your J.D. Edwards environment.
Click the preparser tab.
Enter the required parameters.
The following table lists the parameters with their descriptions. Parameters with an asterisk are required.
For additional parameters, see your J.D. Edwards OneWorld Administrator.
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 using 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. |
Right-click the channel node and select Start.
The channel becomes active.
The X over the icon disappears.
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
In the left pane, locate the channel you want to edit.
Right-click the channel and select Edit.
The Edit channels pane is displayed.
Make the required changes to the channel configuration and click Finish.
Deleting a Channel
To delete a channel:
OracleAS 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.
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.
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 adapters_home
\etc\jde
, where adapters_home
is OracleAS_home
\adapters\application\
. For example:
C:\OraHome_1\adapters\application\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)
.
See "Creating the iwoevent.cfg File" and "Adding Connection Information" for more information on this file.
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 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.
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. If the integration server is unavailable or some exception occurs, the OneWorld Event listener saves the event information in a file called batch.log
. After the server becomes available, the listener sends the information. All log information is saved in a file called iwoevent.log
.
To create the iwoevent.cfg
file:
On the J.D. Edwards OneWorld Server, create an iwoevent.cfg
file in the defined directory. See "Adding Connection Information" for information about the contents of this file.
Create an environment variable, IWOEVENT_HOME
, to point to the directory containing the iwoevent.cfg
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
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. A sample iwoevent.cfg
file is installed on the J.D. Edwards server and is in the root path. 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.
The alias section of the configuration file contains the connection information required to send transactions to specific servers. 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 OracleAS Adapter for J.D. Edwards OneWorld (required).
port
is the port defined for OracleAS Adapter for J.D. Edwards OneWorld (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.
Adding Connection Information to iwoevent.cfg
To add connection information to the iwoevent.cfg file:
Add the server and port entries to the iwoevent.cfg
file.
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.
The following is a sample entry from 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.JDESOW=edamcs1t,edamcs2 trans.JDEPOOUT=edamcs1