| Oracle® Application Server Adapter for J.D. Edwards OneWorld User's Guide 10g Release 3 (10.1.3.4.0) Part Number E14197-01 |
|
|
View PDF |
| Oracle® Application Server Adapter for J.D. Edwards OneWorld User's Guide 10g Release 3 (10.1.3.4.0) Part Number E14197-01 |
|
|
View PDF |
OracleAS Adapter for J.D. Edwards OneWorld integrates seamlessly with Business Process Execution Language (BPEL) Process Manager to facilitate Web service integration. Oracle BPEL Process Manager is based on the Service-Oriented Architecture (SOA). It consumes adapter services exposed as Web Service Definition Language (WSDL) documents.
This chapter includes the following topics:
Overview of Adapter Integration with Oracle BPEL Process Manager
Invoking Adapter Request-Response Service from Oracle BPEL Process Manager
To integrate with Oracle BPEL Process Manager, OracleAS Adapter for J.D. Edwards OneWorld must be deployed in the same OC4J container as Oracle BPEL Process Manager. The underlying adapter services must be exposed as WSDL files, which are generated during design time in Oracle Application Server Adapter Application Explorer (Application Explorer) for both request-response (outbound) and event notification (inbound) services of the adapter. See "Generating WSDL (J2CA Configurations Only)" for more information.
The generated WSDL files are used to design the appropriate BPEL processes for inbound or outbound adapter services. A completed BPEL process must be successfully compiled in JDeveloper and deployed to a BPEL server. Upon deployment to the BPEL server, every newly built process is automatically deployed to the Oracle BPEL Console, where you run, monitor, administer BPEL processes, and listen to adapter events.
When using the adapter with Oracle BPEL Process Manager installed on OracleAS BPEL PM home directory is OC4J_SOA, located as follows:
OracleAS_home\j2ee\OC4J_SOA
See Also:
Oracle Application Server Adapter Concepts
Oracle BPEL Process Manager Developer's Guide
During installation, OracleAS Adapter for J.D. Edwards OneWorld is deployed as a J2CA 1.0 resource adapter within the OC4J J2CA container. The adapter must be deployed in the same OC4J container as Oracle BPEL Process Manager.
See Also:
Oracle Application Server Adapter ConceptsThe following tools are required to complete your adapter design-time configuration:
OracleAS Adapter Application Explorer (Application Explorer)
Oracle JDeveloper BPEL Designer (JDeveloper) or Eclipse
Note:
The examples in this chapter demonstrate the use of JDeveloper.Before you design a BPEL process, you must generate WSDL using Application Explorer. See "Generating WSDL (J2CA Configurations Only)" for more information. The WSDL generated in Application Explorer is used in the BPEL process as Partner Links.
The purpose of an XML namespace is to allow the deployment of XML vocabularies (where element and attribute names are defined) in a global environment and to reduce the risk of name collisions in a given document when vocabularies are combined. Qualified namespaces are used for stricter schema validation. In documents conforming to this specification, element and attribute names appear as qualified names. Syntactically, they are either prefixed names or unprefixed names. An attribute-based declaration syntax is provided to bind prefixes to namespace names and to bind a default namespace that applies to unprefixed element names. These declarations are scoped by the elements on which they appear so that different bindings may apply in different parts of a document. Processors conforming to this specification must recognize and act on these declarations and prefixes.
In the 10.1.3.1.0 SOA release, the recommendations for BPEL integrations is to perform stricter name space validations. As a result, Application Explorer generates Web services for the back-end with the namespace marked as “Qualified”. During testing or usage phases of this service by BPEL, the request XML document that is used should adhere to the schema and WSDL document. Once again, it is important to remember that the namespaces are qualified. To further understand this point, the difference is illustrated with the following example:
Input XML for BPEL based on unqualified namespaces:
<?xml version='1.0' encoding='utf-8' ?><jdeRequest type="callmethod" user="PSFT" pwd="PSFT" environment="DV810" session=""><callMethod name="GetEffectiveAddress"> <params> <param name="mnAddressNumber">1001</param> </params></callMethod></jdeRequest>
Input XML for BPEL based on qualified namespaces:
<jdeRequest xmlns="urn:iwaysoftware:jde/services/CALLBSFN/AddressBook/GetEffectiveAddress" type="callmethod" session="" sessionidle=""><callMethod runOnError="" trans="String" name="GetEffectiveAddress" app="string" returnNullData="yes"> <params> <mnAddressNumber>1001</mnAddressNumber> </params> <onError abort="Yes"/> </callMethod></jdeRequest>
Note: If you are passing an unqualified input against a WSDL document that is expecting qualified namespaces, BPEL will throw the exception as “Unable to process input xml...."
An outbound BPEL process consists of PartnerLink, Invoke, and Assign process activities. You must first create a new Application Server connection, Integration Server connection, and a synchronous BPEL process template.
Create a New Application Server Connection
To create a new Application Server connection:
Display the connections by clicking the Connections Navigator tab at the top of the upper left pane in JDeveloper.
Right-click Application Server and select New Application Server Connection.
The Create Application Server Connection - Welcome dialog box is displayed.
Click Next.
The Create Application Server Connection - Step 1 of 4: Type dialog box is displayed.
Specify a unique name and select a connection type for your Application Server connection and click Next.
The Create Application Server Connection - Step 2 of 4: Authentication dialog box is displayed.
Specify a valid user name and password for the Application Server you want to connect to.
Select Deploy Password.
Click Next.
The Create Application Server Connection - Step 3 of 4: Connection dialog box is displayed.
Select the Single Instance connection option.
Enter localhost as the host name and 6003 for the OPMN port.
Enter home as the OC4J instance name
Click Next.
The Create Application Server Connection - Step 4 of 4: Test dialog box is displayed
Click Test Connection.
When the test is complete and the connection is successful, a Success! message appears in the status area.
Click Finish.
Your newly created Application Server connection is displayed in the Connections Navigator tab under the Application Server node.
Create a New Integration Server Connection
To create a new Integration Server connection:
Display the connections by clicking the Connections Navigator tab at the top of the upper left pane in JDeveloper.
Right-click Integration Server and select New Integration Server Connection.
The Create Integration Server Connection - Welcome dialog box is displayed.
Click Next.
The Create Integration Server Connection - Step 1 of 3: Name dialog box is displayed.
Specify a unique name and click Next.
The Create Integration Server Connection - Step 2 of 3: Connection dialog box is displayed.
Select an Application Server connection, which is already created.
Enter localhost as the host name and 8888 for the port number.
Select Add host name to the list of proxy exceptions and click Next.
The Create Integration Server Connection - Step 3 of 3: Test Connection dialog box is displayed.
Click Test Connection.
When the test is complete and the connection is successful, a Success! message appears in the status area.
Click Finish.
Your newly created Integration Server connection is displayed in the Connections Navigator tab under the Integration Server node.
Testing Outbound BPEL and ESB Processes
The BPEL console enables the testing of deployed BPEL processes. Once a process is deployed, you can manage, monitor, and run an end-to-end scenario using the Initiate tab in the console. The OracleAS Adapter for J.D. Edwards OneWorld is certified for testing using the XML Payload option and the option of running using Through Java Delivery API. It is recommended that developers use this method for testing the OracleAS Adapter for J.D. Edwards OneWorld.
When testing an outbound BPEL process from the BPEL console or an outbound ESB process from the Enterprise Manager console, do not use the XML envelopes that are generated by these consoles. Instead, remove them and use the XML payloads that are generated from the schemas, which conform to the WSDLs for namespace qualifications.
The ESB data flows can be tested using the Enterprise Manager console. When creating an ESB data flow and interactions, the Web services are created and registered with the Oracle Application Server. For more information on creating an ESB outbound process, see Chapter 5, "ESB Integration Examples".
This topic illustrates J.D. Edwards service integration. The design-time and run-time procedures are described below.
Generating WSDL for Request/Response Service
To generate WSDL for outbound interaction:
Start Application Explorer and connect to a defined J.D. Edwards target.
Expand Services, JDEJAVA_CFIN, B0100033, and then 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 for the file.
The .wsdl file extension is added automatically.
Ensure that qualified is selected as the element form, which is the default.
Click OK.
The WSDL file is created.
Creating a BPEL PM Server Connection
Before you design an outbound BPEL process, you must configure a new Application Server and Integration Server connection in Oracle JDeveloper. For more information, see Chapter 4, "Integration with Oracle BPEL Process Manager".
Creating a BPEL Project for a Synchronous BPEL Process
To create a BPEL Project for a synchronous BPEL process:
At the top of the upper left pane, click the Applications Navigator tab and select an application. If an application does not exist, then you must create an application.
Right-click the application and select New Project.
The New Gallery window is displayed.
From the Items list, select BPEL Process Project and click OK.
The BPEL Project Creation Wizard - Project Settings dialog box is displayed.
Perform the following steps:
Specify a name for the BPEL project, for example, JDE_Service.
The Namespace field is updated automatically.
From the Template list, select Synchronous BPEL Process.
Click OK.
Designing the BPEL Process for GetEffectiveAddress (Outbound Service)
From the Services pane on the right, drag and drop a PartnerLink to the visual editor.
The Create Partner Link dialog box is displayed.
Click the Service Explorer icon (second icon from the left preceding the WSDL File field).
The Service Explorer dialog box is displayed.
Expand your new connection under Adapter Services, followed by adapters, and then applications.
The WSDL tree displayed in the Service Explorer dialog box lists any WSDL files you have created using Application Explorer. The WSDL tree is generated by a WSDL servlet, which is automatically deployed as part of the BPEL Server installation.
Select GetEffectiveAddress_invoke.wsdl and click OK.
The WSDL File field in the Create Partner Link dialog box displays the name and location of the selected WSDL file. The Partner Link Type field specifies the PartnerLink defined in the WSDL file.
Perform the following steps:
Leave the My Role field unspecified. The role of the PartnerLink is null, as it will be synchronously invoked from the BPEL process.
From the Partner Role list, select the default value GetEffectiveAddressRole. This is the role of the BPEL process.
Click OK.
Select Save from the File menu.
From the Process Activities pane on the right, drag an Invoke activity to the visual editor and place it between the Receive activity (receiveInput) and the Reply activity (replyOutput).
The Invoke process activity is shown in the following diagram view.
Drag the right arrow from Invoke_1 and connect it to the JDE_Service_PL PartnerLink.
The Edit Invoke dialog box is displayed.
Perform the following steps:
Click OK.
Drag an Assign process activity and drop it between receiveInput and JDE_GetEffectiveAddress.
The following image shows the new Assign activity in JDeveloper visual editor.
Double-click the Assign activity icon.
The Assign dialog box is displayed.
In the Copy Operation tab, click Create and select Copy Operation.
The Create Copy Operation dialog box is displayed.
In the From pane, expand Variables, then inputVariable, and then highlight payload.
In the To pane, expand Variables, then JDE_GetEffectiveAddress_GetEffectiveAddress_InputVariable, and then highlight input_GetEffectiveAddress.
Your Create Copy Operation dialog box should look as follows:
To close the Create Copy Operation dialog box and the Assign dialog box, click OK.
From the Process Activities pane on the right, drag another Assign activity to the visual editor and place it between the Invoke activity (JDE_GetEffectiveAddress) and the Reply activity (replyOutput).
Double-click the Assign activity icon and click Create.
Map JDE_GetEffectiveAddress_GetEffectiveAddress_OutputVariable, output_GetEffectiveAddress to outputVariable, payload.
Verify that you have mapped all variables as follows:
Click OK, and then click OK again.
Select Save from the File menu.
You have completed the design of your BPEL process.
Deploying the BPEL Process for GetEffectiveAddress (Outbound Service)
JDeveloper deploys BPEL processes directly to Oracle BPEL Console.
To deploy your BPEL process in JDeveloper:
Select Deploy, then Your BPEL PM Server connection, and then Deploy to default domain.
The deployment process starts automatically.
Observe the Messages log at the bottom of the window.
The Messages log displays the deployment status. In this example, it shows a successful deployment message for the process.
If deployment was not successful, click the Compiler tab to view all error and warning messages generated during the deployment process.
The OracleAS Adapter for J.D. Edwards OneWorld request-response service is used to create, delete, update, query back-end data, and to call back-end workflows and transactions. The following section describes how to invoke the adapter synchronous request-response service, also referred to as Outbound Interaction, and how to manage the process in Oracle BPEL Console.
Manage the Deployed Outbound Process in Oracle BPEL Console
JDeveloper deploys the developed process directly to the Oracle BPEL Console, which enables you to run, monitor, and administer BPEL processes.
To invoke adapter request-response service:
Start the Oracle BPEL Console by entering the following URL in a browser:
http://host:port/BPELConsole
Provide a valid user name and password.
The Oracle BPEL Console main page is displayed. All deployed BPEL processes are listed in the Dashboard tab.
This tab provides a more detailed view of each deployed process.
Click the J.D. Edwards outbound process link.
The Manage window provides options for managing this BPEL process. Do not change any of the following default settings.
Click the Initiate tab.
The Initiate tab enables you to test your BPEL process.
Perform the following steps:
From the Initiating a test instance list, select XML Source.
Select the Java through delivery API link in the right side of the test area.
Enter the following code in the text area provided for XML input:
<?xml version="1.0" encoding="UTF-8"?> <jdeRequest type="callmethod"><callMethod name="GetEffectiveAddress" runOnError="no"><params><param name="mnAddressNumber">99999</param><param name="jdDateBeginningEffective"/><param name="cEffectiveDateExistence10"/><param name="szAddressLine1"/><param name="szAddressLine2"/><param name="szAddressLine3"/><param name="szAddressLine4"/><param name="szZipCodePostal"/><param name="szCity"/><param name="szCountyAddress"/><param name="szState"/><param name="szCountry"/><param name="szUserid"/><param name="szProgramid"/><param name="jdDateupdated"/><param name="szWorkstationid"/><param name="mnTimelastupdated"/><param name="szNamealpha"/></params><onError abort="yes"/></callMethod></jdeRequest>
Click Post XML Message.
Click the Instances tab, and then click the Audit tab to view the response received from the J.D. Edwards OneWorld system.
See Also:
Oracle Application Server Adapter ConceptsThis example illustrates how OracleAS Adapter for J.D. Edwards OneWorld integrates with J.D. Edwards OneWorld to receive event data. The design-time and run-time configuration procedures are outlined in the following sections.
Before you design a BPEL process using JDeveloper, you must create a separate channel for every J2CA event and select that channel when you generate WSDL for inbound interaction using Application Explorer.
Note:
If two or more events share the same channel, event messages may not be delivered to the right BPEL process.Creating a Channel in Application Explorer
To create a channel:
Right-click the Channels node, and select Add Channels.
The Add Channel dialog box is displayed.
In the Name field, enter a descriptive name for the channel.
In the Description field, enter a description (optional).
Click Next.
The dialog box is displayed for the selected listener.
Enter the port number of the channel in the Port Number field.
Enter the location of the server in the Host/IP Binding field.
Select the Synchronization type from the Synchronization Type list.
Select Is Length Prefix for events that send data which 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.
Select Is XML for events that send data back in XML format. No preparser is required.
Select Is Keep Alive to maintain a continuous communication between the event transaction and the channel.
Enter values based on the table.
Click OK.
The channel is created and displayed under the Channels node. An X over the icon indicates that the channel is currently disconnected.
Generating WSDL for Event Notification (Command Prompt Only)
You cannot generate WSDL for J.D. Edwards OneWorld event notification using Application Explorer. To generate WSDL from the command prompt, you must perform the following steps.
Important: You can create inbound J2CA service only if the node you have selected supports events.
To generate a WSDL file for J.D. Edwards OneWorld event notification:
Create a channel in Application Explorer under the J.D. Edwards events node. See "Creating a Channel in Application Explorer".
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\iwaf_jca15.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. On UNIX platforms, run Jbadapter.bat.
Enter the following command to generate WSDL:
java com.iwaysoftware.af.container.tools.wsdl.IWayWSILBrowser jcaHome adapter target channel schemaPrefix wsdlFileName
Where:
jcaHome is the path to your J2CA configuration. For example, OracleAS_home\adapters\application\
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\config\jca_sample\schemas\JDEdwards\bvision02
wsdlFileName is the name of the WSDL file being created in this procedure
For example:
C:\soaga\adapters\application\config\jca_sample\schemas\JDEdwards\bvision02>java com.iwaysoftware.af.container.tools.wsdl.IWayWSILBrowser c:\soaga\adapters\application\ JDEdwards bvision02 JDE PO purchaseorder.wsdl
Once the command is successfully executed, the following output will be shown in the command window:
Running Inbound WSDL generation tool... -> user.dir = C:\soaga\adapters\application\config\jca_sample\schemas\JDEdwards\bvision02 -> Generating WSDL... -> Done. -> Writing WSDL 'c:\soaga\adapters\application\\wsdls\purchaseorder.wsdl' to disk... -> Done.
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 file is created. You can now create a BPEL process that uses the WSDL as Partner Link. As the BPEL process is deployed, the channel is activated from BPEL PM. Then, after you send an inbound message from J.D. Edwards OneWorld, the message will be received by the channel started by BPEL PM. These procedures are described in detail in the following sections.
Creating a BPEL PM Server Connection
Before you design a BPEL process, you must configure a new Application Server and Integration Server connection in Oracle JDeveloper. For more information, see Chapter 4, "Integration with Oracle BPEL Process Manager".
Designing the BPEL Project for the SalesOrder Inbound Service
To design a BPEL project for inbound interaction:
At the top of the upper left pane, click the Applications Navigator tab and select an application.
Right-click the application and select New Project.
The New Gallery window is displayed.
From the Items list, select BPEL Process Project and click OK.
The BPEL Project Creation Wizard - Project Settings dialog box is displayed.
Perform the following steps:
Specify a name for the BPEL project.
The Namespace field is updated automatically.
From the Template list, select Empty BPEL Process.
Click OK.
From the Services pane on the right, drag and drop a PartnerLink to the visual editor.
The Create Partner Link dialog box is displayed.
Click the Service Explorer icon (second icon from the left preceding the WSDL File field).
The Service Explorer dialog box is displayed.
Expand your new connection under Adapter Services, followed by adapters, and then applications.
The WSDL tree displayed in the Service Explorer dialog box lists any WSDL files you have created using Application Explorer. The WSDL tree is generated by a WSDL servlet, which is automatically deployed as part of the BPEL Server installation.
Select SalesOrder.wsdl and click OK.
The Create Partner Link dialog box is displayed.
The WSDL File field displays the name and location of the selected WSDL file. The Partner Link Type field specifies the PartnerLink defined in the WSDL file.
Perform the following steps:
Click Apply, and then click OK.
The new PartnerLink appears in the visual editor.
From the Process Activities pane on the right, drag a Receive activity to the visual editor and place it in the designated placeholder labeled Drop Activity Here.
Connect the Receive activity to the JDE_event PartnerLink.
The Edit Receive dialog box is displayed.
Perform the following steps:
Specify a name for the Receive Activity, for example, Receive_SalesOrder.
Click the first icon to the right of the Variable field, then click OK in the Create Variable dialog box that is displayed.
Verify that the Create Instance check box is selected.
Click Apply.
The Receive dialog box should no longer display any warnings or errors.
Click OK.
Select Save from the File menu.
Deploying the BPEL Project for the Inbound Service
Select Deploy, then Your BPEL PM Server connection, and then Deploy to default domain.
The deployment process starts automatically.
Events are generated by activity in a database or in an application system. You can use events to trigger an action in your application. See "Configuring an Event Adapter" for more information on event configuration.
Triggering an Event in J.D. Edwards OneWorld
To trigger an event in J.D. Edwards OneWorld:
Log in to your J.D. Edwards OneWorld system.
In the Fast Path field of the J.D. Edwards OneWorld Explorer window, type G4211 and press Enter.
Right-click Sales Order Detail (P4210).
Select Prompt for, and then Values.
The Processing Options dialog box is displayed.
Perform the following steps:
Click the Interop tab.
In the Transaction Type field, type JDESOOUT.
Verify that the value in the Before/After Image Processing Blank field is 1.
Click OK.
The Sales Order Detail - (Customer Service Inquiry) window is displayed.
Click the Add icon (third icon from left).
Enter the values as shown in the following screen.
To move to a different field, use the Tab key on your keyboard.
Enter a value for Quantity Ordered and Item Number.
For example:
Click the first field in the second row and allow a few seconds for processing.
Click OK.
An event is triggered in the J.D. Edwards OneWorld system.
Log in to Oracle BPEL Console at
http://host:port/BPELConsole
Provide a valid user name and password.
Recently received run-time events are displayed in the Instances tab.
Click your J.D. Edwards event instance, and then click Audit to see the received event message.
|
 Copyright © 2007, 2009, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|