Embed Size (px)
Citation preview
Integrating JD Edwards Enterprise One and Oracle Service Bus
Overview This tutorial demonstrates how Oracle Service Bus (OSB) makes a service callout to a JD Edwards Enterprise One web service. OSB then routes the response to the appropriate business service, using content based routing. Use Case Incoming loan applications at a financial services company are routed through OSB to determine the appropriate business service to process the application, depending on the applicant’s credit limit. OSB makes a service callout to JD Edwards Enterprise One to obtain the credit limit. If the credit limit is <= $100k, the application is routed to the “regular-loan” business service for processing; all other applications are routed to the “jumbo-loan” business service. The tutorial uses a file system to represent the two business services. Prerequisites 1. Oracle Service Bus 3.0 installation, available at Oracle BEA Product Downloads. 2. Access to JD Edwards Enterprise One 8.12/8.97, including a Business Services server. 3. JD Edwards setup to generate the WSDL for the published web service (see Section
VIII). Time to complete: Approximately 2 hours.
2
I. Initial setup................................................................................................................ 3
II. Create the WSDL resources....................................................................................... 6 III. Create the "Credit-info" Business Service .................................................................. 8
IV. Create the Proxy Services ........................................................................................ 13
V. Create the "regular-loan" and "jumbo-loan" Business Service .................................. 17 VI. Proxy Services Configuration: Part 1 ...................................................................... 23
VII. Proxy Services Configuration: Part 2 ...................................................................... 34
VIII. JD Edwards Enterprise One configuration............................................................. 37 IX. Testing ................................................................................................................... 37
X. Summary................................................................................................................. 38
3
I. Initial setup
1. In the Console Change Center, click Create to create a new session.
2. Select Project Explorer.
3. Enter ALSB-JDE as shown in the Project Name field. 4. Click Add Project.
4
5. The ALSB-JDE project is created and listed in the Project Explorer as shown. To create the relevant project folders, click ALSB-JDE to open the associated project page.
6. Enter WSDL in the New Folder Name field and click Add Folder.
7. Repeat Step 6 to create two additional folders named BusinessService and
ProxyService as shown.
5
6
II. Create the WSDL resources
1. Click on WSDL.
2. In the Create Resource drop down list (in the right hand frame), select WSDL.
3. Enter RI_CustomerManager as the Resource Name. 4. Click Browse to navigate to the location of the WSDL file that was created earlier (see
Section VIII). 5. Click Save to create the WSDL resource.
7
6. Confirmation that the WSDL was successfully created.
8
III. Create the "Credit-info" Business Service
1. Click on BusinessService.
2. Choose Business Service in the Create Resource drop down list.
3. Enter Credit-info as the Service Name. 4. Select WSDL Web Service. 5. Click Browse.
9
6. The Select a WSDL page is displayed. The web service is based on the WSDL resource
that was created earlier. Select RI_CustomerManager.
7. Click on RI_CustomerManagerHttpPort. 8. Click Submit.
10
9. Click Next. 10. Choose http from the Protocol drop down list.
11. Click on the Edit icon as indicated by the cursor location.
12. The Endpoint URI gets populated with the specified name.
13. Click Next. 14. Accept the default entries (by clicking Next) in the next two screens:
• HTTP Transport Configuration
• SOAP Binding Configuration
11
15. We are now at the Create a Business Service Summary page. Click Save.
12
16. Confirmation that the business service was created.
13
IV. Create the Proxy Services
1. Click on ProxyService.
2. In the Create Resource drop down list (in the right hand frame), select Proxy Service.
14
3. Enter credit-rating as the Service Name. 4. In Service Type, select Business Service, and then click Browse.
5. The Select Business Service page is displayed. The proxy service is based on the Business
Service that was created earlier. Select Credit-info. 6. Click Submit.
15
7. This brings us back to the General Configuration Page. Click Next.
8. Accept the default settings (by clicking Next in each screen) for:
• Transport Configuration
• HTTP Transport
• Operation Selection
16
9. We are now at the Proxy Service Summary page, click Save to register the service.
10. Confirmation that the credit-rating service was created successfully.
17
V. Create the "regular-loan" and "jumbo-loan" Business Service
1. Click on BusinessService.
2. Choose Business Service in the Create Resource drop down list.
18
3. Enter regular-loan as the Service Name. 4. Select Any XML Service. 5. Click Next.
6. Choose file from the Protocol drop down list. Click Next.
19
7. Specify the location of the Endpoint URI as file://d/temp/regular-loan 8. Click Add., followed by Next.
9. Enter .xml as the suffix. 10. Click Next.
20
11. The Summary page for "regular-loan" should read as shown. Click Save.
12. Repeat steps 1-11 to create another Business Service with these two changes:
• Replace regular-loan with jumbo-loan in Step 3.
• Specify the location of the Endpoint URI as file://d/temp/jumbo-loan in Step 7.
Note: The other remaining steps are to be repeated as-is.
21
13. The Summary page for "jumbo-loan" should read as shown. Click Save.
14. Click Activate.
22
15. Click Submit.
23
VI. Proxy Services Configuration: Part 1
1. In the Change Center, click Create to create a new session.
2. Select Resource Browser in the Operations pane.
3. In the Actions column for the credit-rating Proxy Service, click on the Edit Message
Flow icon as indicated by the cursor location.
24
4. Click on credit-rating and select Add Pipeline Pair.
5. Click on Response Pipeline and select Add Stage.
25
6. Click on stage and select Edit Name and Comments.
26
7. Enter process-loan as shown. 8. Click Save.
27
9. Click on process-loan, and select Edit Stage.
10. Click on the Add an Action link, and select Communication > Publish Table.
28
11. Click on <Expression> to bring up the XQuery/XSLT Expression editor.
12. Click on Variable Structures.
13. Select body from the Select Structure drop-down list.
29
14. Navigate to amountCreditLimit in $body - getCustomerCreditInfo (response).
15. Click Copy Property.
16. Click Validate, followed by Save.
30
17. Select <= in the Operator drop down list. 18. Enter 100000 in the text box (we configure the routing table such that applications with
credit limit <=100000 are routed to the regular-loan business service). 19. Click on <Service>
20. Select regular-loan and Submit.
21. Select Add an Action > Message Processing > Assign.
31
22. Click on <Expression>
23. Click Variable Structures.
24. Select body from the Select Structure drop-down list.
25. Navigate to entityId as shown.
32
26. Click Copy Property.
27. Click Validate, followed by Save.
28. Enter customer-id the variable text box.
29. Click on the Assign icon. Select Add an Action > Message Processing > Insert.
30. Click on <Expression> to bring up the XQuery Editor.
33
31. Enter <file:fileName>{$customer-id}</file:fileName> 32. Click Validate, followed by Save.
33. Choose as first child of in the drop down list as shown. 34. Click <XPath> to bring up the XPath Expression Editor.
35. Enter ./ctx:transport/ctx:request/tp:headers 36. Click Validate, followed by Save.
37. Enter outbound in the variable text box as shown.
34
VII. Proxy Services Configuration: Part 2
We now configure the "jumbo-loan" business service. 1. Click the Case icon, select Insert Default Case.
2. Select <Service>.
3. Choose jumbo-loan and click Submit.
35
4. Click on the Assign icon in the Request Actions for regular-loan and select Copy.
5. Click on the Add an Action icon in the Request Actions for the Default Case and select
Paste Action.
6. Repeat Steps 4 and 5 (copy/paste) for the Insert action. Verify that the Default routing
appears as shown.
36
7. Select Save All.
8. Click Activate.
9. Click Submit.
Note: The two business processes (regular-loan and jumbo-loan) have identical processing steps in this example for ease of implementation.
37
VIII. JD Edwards Enterprise One configuration
Refer to Sections 1 and 2 in "Query JD Edwards Enterprise One Customer Credit using Oracle BPEL Process Manager" tutorial for instructions on creating a WSDL for the Customer Master business service.
IX. Testing
1. Click on Resource Browser in the left panel of the OSB Console.
2. This brings up the Summary of Proxy Services page (in the right hand frame). 3. Click on the Launch Test Console icon in the Actions column for credit-rating as
indicated by the cursor location.
4. Browse to locate the payload file and click Execute (at the top of the screen).
38
5. The output from the service callout to JD Edwards Enterprise One is depicted below.
Note the values of amountCreditLimit (50021) and the entityId (4242).
6. As the CreditLimit is <= 100000, it is routed to the normal-loan business process. This
business process redirects the response to the <entityId>.xml file. Verify that the file 4242.xml is created in the specified directory (/temp/normal-loan).
X. Summary
This tutorial demonstrates how OSB makes a service callout to a JD Edwards Enterprise One web service. OSB then routes the response to the appropriate business service, using content based routing.
