3 Connecting to Applications

Transcription

1 3 Connecting to Applications 3 Connecting to Applications Prerequisites Introduction Pega, the Widget Supplier Mega, the Widget Procurer Create Requisition What is being done? High Level Steps Steps in Detail Test Receive PO What is being done? High Level Steps Test Prerequisites Chapter One Lab complete, working and deployed. 3.2 Introduction SOA and Oracle Service Bus server running.. Note: The solution for this chapter can be found in /home/oracle/soaosb/solutions/chap-3. To run the solution, you must deploy the SOA Composites from Chapter 1. You can either complete Chapter 1 or deploy the composites from /home/oracle/soa-osb/solutions/chap-3 directory. First deploy the OSB configuration jar and then deploy the SOA composites. In this chapter, you will learn to use Oracle Service Bus to Virtualize Application Services through JCA Adapters such as Oracle ebusiness Suite, Siebel, PeopleSoft etc. Mediate access to data in the Database along with Protocol bridging Employees at Mega Corporation use the Employee Self Service portal to submit Requisition requests for items required to carry on their job functions. Once the Requisition gets approved, Purchase Order is generated for the Requisition. The Purchase Order is then submitted to the Supplier, Pega Corporation. Supplier validates the requestor s Credit Card, approves the Purchase Order if required, and fulfills the Order. Section 3.1 Page 1 of 34

2 OSB 11gR1 Workshop Mega Corporation has implemented the Requisition process in Oracle ebusiness Suite. Supplier, Pega Corporation, has implemented the Purchase Order process in Oracle SOA Suite. Overview of the business processes at work between Mega, on the left, with Procure to Pay business process, interfacing with Pega, on the right, with Order-to-Cash business process Pega, the Widget Supplier In Chapters One and Two, we introduced Oracle Service Bus in the Pega Corporation s IT infrastructure to streamline credit card validation. Pega needed to provide a better quality of service to its Widget consumers like Mega Corporation. Oracle Service Bus brought more robustness and scalability to Pega and allowed it to contract new Credit Card Vendors without impact to the business. Pega also leveraged Servcie Result Caching to improve quality of service to check status on outstanding orders Mega, the Widget Procurer In this chapter, we will introduce Oracle Service Bus in the Mega Corporation s IT to help scale its Integation. Mega Corporation has decided to leverage Oracle Service Bus, a key component of the Oracle SOA Suite, to virtualize the application services in Oracle ebusiness Suite and mediate Supplier Purchase Order processes. This initiative is driven to create a Shared Services Infrastructure, using Oracle Service Bus, which is a key requirement to scale and reap the benefits of SOA. Hence, Oracle Service Bus is used to: 1. Virtualize the Requisition process in Oracle ebusiness Suite. OSB will virtualize the service to insert the Requisition request from Employees using the Employee Portal to allow quick on-ramping of other sources of requisitions Section 3.2 Page 2 of 34

3 For the purpose of the Lab, Oracle ebusiness Suite is simulated using the Oracle DB the steps are similar for other JCA Adapters. 2. Retrieve the Purchase Order generated by Oracle ebusiness Suite from the Database before Routing the transformed Purchase Order request to the Supplier POProcessing Composite Service in Oracle SOA Suite. For the purpose of the lab, the Purchase Order is created in the database We will divide this chapter into two sections. In the first section, you will build the Create Requisition flow, and in the second section you will build the Receive PO flow. 3.3 Create Requisition Note: The solution for this section can be found in /home/oracle/soaosb/solutions/chap-3/chap-3a-solution-sbconfig.jar What is being done? In this section, you will create a HTTP Proxy Service that receives requisition from clients. This Proxy Service routes the requisition to a JCA DB Business Service, which inserts the requisition into the database. Following steps will be performed 3. JDeveloper - Create JCA DB Adapter files to insert the requisition into the database 4. OSB Console - Import JCA DB Adapter files. Create a JCA DB Business Service, using the imported JCA DB Adapter files, to insert requisition into DB. 5. OSB Console - Create HTTP Proxy Service, which routes the requisition to the JCA DB Business Service. Section 3.3 Page 3 of 34

4 OSB 11gR1 Workshop High Level Steps Create Database Adapter artifacts in JDeveloper We will create DB Adapter artifacts to insert requisition into DB 6. Create new SOA Application in JDeveloper a. Application Name: OSBDemo b. Directory: /home/oracle/jdeveloper/mywork/osbdemo c. Project Name: DBArtifacts d. Directory: /home/oracle/jdeveloper/mywork/osbdemo/dbartifacts e. Project Technologies: SOA f. Empty Composite 7. Adding the database adapter a. Drag and Drop Database Adapter from Component Palette to External References swim lane b. DbAdapter (Outbound) Service Name: createrequisition c. Create Database Connection with details: Connection Name: SOADemo Connection Type: Oracle (JDBC) Username: SOADEMO Password: soademo Save Password: Checked Enter Custom JDBC URL: Unchecked Driver: thin Host Name: localhost JDBC Port: 1521 (or the port number of your database) SID: soa11gdb (or the SID of your database) d. JNDI Name: eis/db/soademo e. Operation Type: Perform an Operation on a Table. Check Insert Only f. Import OSB_REQUISITION table (search for %OSB% in the Query) g. Define Primary key: REQID Import Database Adapter artifacts into Oracle Service Bus 8. Log into Oracle Service Bus console 9. Create Session 10. Add Project: Requisition Section 3.3 Page 4 of 34

5 11. Create Folder: Resources (under the project Requisition) 12. Navigate to the folder Resources by clicking on it in the table 13. Create Resource: Bulk - Resources from URL URL: file:/home/oracle/jdeveloper/mywork/osbdemo/dbartifacts/createrequisition_db.j ca Resource Name: createrequisition_db Resource Type: JCA Binding 14. Click Next, followed by Import 15. Resulting resources after Import Requisition/Resources/createRequisition_db JCA Binding Requisition/Resources/createRequisition WSDL Requisition/Resources/xsd/createRequisition_table XML Schema Requisition/Resources/createRequisition-or-mappings XML Document Create Business Service from Database Adapter JCA File 16. Create Folder: BusinessServices (under the project Requisition) 17. Navigate to the folder Resources (under the project Requisition) 18. Click Action Icon for the createrequisition_db JCA Binding to generate a WSDL and Service for this JCA Binding Resource. 19. Generate the service in Requisition/BusinessServices folder 20. Resulting resources Requisition/BusinessServices/createRequisition_db Business Service Requisition/BusinessServices/createRequisition_db - WSDL Create Proxy Service for Business Service 21. Create Folder: ProxyServices under Requisition project 22. Navigate to the folder ProxyServices (under the project Requisition) 23. Add Proxy Service to this folder Service Name: createrequisition to this folder Select Create From Existing Service Business Service: Requisition/BusinessServices/createRequisition_db Click Next Protocol: http Click Next Section 3.3 Page 5 of 34

6 OSB 11gR1 Workshop Click Last Save Update Proxy Service Message Flow 24. Add Report action to report the Requisition a. Click on to edit Message Flow for the createrequisition Proxy Service b. Add Pipeline Pair c. Add Stage to Request Pipeline d. Edit Stage to add Report. Report $body with search keys Key Name: REQ_ID Key Value: XPATH./cre:OsbRequisitionCollection/cre:OsbRequisition/cre:reqid in variable body Steps in Detail Create Database Adapter artifacts in JDeveloper We will create DB Adapter artifacts to insert requisition into DB 25. Create new SOA Application in JDeveloper. Select New Application as shown below 26. In the Create SOA Application Step 1 of 3 dialog specify the following: a. Application Name: OSBDemo b. Directory: /home/oracle/jdeveloper/mywork/osbdemo c. Application Template: SOA Application d. Click Next Section 3.3 Page 6 of 34

7 27. In the Create SOA Application Step 2 of 3 dialog specify the following Project Name: DBArtifacts Directory: /home/oracle/jdeveloper/mywork/osbdemo/dbartifacts Project Technologies: SOA Click Next Section 3.3 Page 7 of 34

8 OSB 11gR1 Workshop 28. In the Create SOA Application Step 3 of 3 dialog pick Empty Composite and click Finish 29. In the Composite Editor, Drag and Drop Database Adapter from Component Palette to External References swim lane 30. Adapter Configuration Wizard Step 2 of 4 a. Service Name: createrequisition b. Click Next Section 3.3 Page 8 of 34

9 31. In the Adapter Configuration Wizard Step 3 of 4, click on to create a new Database Connection. 32. In the Create Database Connection dialog specify the following details: a. Connection Name: SOADemo b. Connection Type: Oracle (JDBC) c. Username: SOADEMO d. Password: soademo e. Save Password: Checked f. Enter Custom JDBC URL: Unchecked g. Driver: thin h. Host Name: localhost i. JDBC Port: 1521 (or the port number of your database) j. SID: soa11gdb (or the SID of your database) k. Click Test Connection l. Click OK Section 3.3 Page 9 of 34

10 OSB 11gR1 Workshop 33. In the Adapter Configuration Wizard Step 3 of 4, specify a. Connection: SOADemo b. JNDI Name: eis/db/soademo c. Click Next Section 3.3 Page 10 of 34

11 34. In Adapter Configuration Wizard Step 4 of 5, specify a. Operation Type: Perform an Operation on a Table. b. Check Insert Only c. Click Next Section 3.3 Page 11 of 34

12 OSB 11gR1 Workshop 35. In Adapter Configuration Wizard Step 5 of 5 click Import Tables 36. In the Import Tables dialog specify a. Schema: SOADEMO b. Name Filter: %OSB% c. Click Query Section 3.3 Page 12 of 34

13 37. From the Available Tables select OSB_REQUISITION table and move Selected by clicking on 38. Click OK Section 3.3 Page 13 of 34

14 OSB 11gR1 Workshop 39. In Adapter Configuration Wizard Step 5 of 10 click Next 40. In Adapter Configuration Wizard Step 6 of 10 a. Define Primary key by selecting REQID b. Click Next 41. Click Finish Import Database Adapter artifacts into Oracle Service Bus 42. Log in to OSB console at Create a session. Section 3.3 Page 14 of 34

15 44. Add Requisition project if it does not already exist. 45. Create folder Resources under Requisition project (if it does not already exist) 46. While in the Resources folder, from the Create Resource drop down select Resources from URL: 47. In the Load Resources from URL screen specify a. URL: file:/home/oracle/jdeveloper/mywork/osbdemo/dbartifacts/createrequisition _db.jca (this step is much easier in Eclipse IDE where there is a Browse action to choose the file using Explorer) b. Resource Name: createrequisition_db Section 3.3 Page 15 of 34

16 OSB 11gR1 Workshop c. Resource Type: JCA Binding d. Click Next 48. Click Next then click Import 49. Activate the changes. Click Activate and then Click Submit Create Business Service from Database Adapter JCA File 50. Create a session. 51. Create folder Business Services under the Requisition project. 52. While the current folder is Resources, click Action Icon for the createrequisition_db JCA Binding. 53. This launches the Generate WSDL and Service dialog. In this dialog box, select BusinessServices folder as the target folder to create the new resources in. You can Section 3.3 Page 16 of 34

17 leave the defaults for the WSDL and Business Service name. 54. Click Generate. Two resources (Business Service and WSDL) have been created automatically in the BusinessServices folder. Navigate to that folder to verify this Create Proxy Service for Business Service 55. Navigate up to the Requisition project root level by clicking on Requisition in the project structure tree. 56. Create folder ProxyServices.(if it does not already exist) 57. Initiate the process to create a Proxy Service in this folder. 58. Name the proxy service createrequisition. 59. You are going to base this proxy service configuration on the Business Service specification that was just created. If you recall, that Business Service was generated automatically from a jca adapter you created in JDev. To create the proxy service based the existing Business Service definition, in the Create from Existing Service section, click the Business Service radio button, and then the Browse button. Section 3.3 Page 17 of 34

18 OSB 11gR1 Workshop 60. Click the radio button for the createrequisition Business Service then click Submit. 61. Now you need to set the protocol for this proxy service to http. Because the proxy service is built on the Business Service specification, its protocol is jca. You need to change that to http.. To do this, click the Next button. 62. Select http from the list of available protocols, then click Next. 63. On the next page click the Last button because we are accepting the inherited and default values for the remaining proxy service configuration settings. 64. Finally, go the the bottom of the page and click Save. If you don t all your changes will be lost. 65. Last, Activate the changes. Click Activate and then click Submit Update Proxy Service Message Flow 66. Start a new session. Section 3.3 Page 18 of 34

19 67. Go to the Requisition project ProxyServices folder. 68. Open the proxy service message flow for editing for createrequisition. 69. Click the start node and select Add Pipeline Pair. 70. Click the Request Pipeline node and Add Stage. 71. Click the stage and edit the stage. Section 3.3 Page 19 of 34

20 OSB 11gR1 Workshop 72. Add a Report action. 73. Use these parameters to complete the Report action configuration as shown. a. Report: $body b. Key Name: REQ_ID c. Key Value:./cre:OsbRequisitionCollection/cre:OsbRequisition/cre:reqid (make sure namespace prefix is correct) d. in variable: body Note: Instead of typing the XPath for Key Value you can do the following Select Variable Structures from the left side options, pick body from the drop down and expand the structure of $body insert (request) to select reqid as shown below. Section 3.3 Page 20 of 34

21 This will show the XPath in the Property Inspector on right bottom as shown below. You can copy the XPath from Property Inspector into the XPath text area or click on Copy Property (right side on the same line as Property Inspector) as shown below to copy the content from Property Inspector to the XPath text area. 74. Activate the session click Activate and then click on Submit Section 3.3 Page 21 of 34

22 OSB 11gR1 Workshop Test 75. To test the createrequisition proxy service, launch the test console by clicking on the icon under Actions after navigating to Resource Browser followed by Proxy Services. 76. Load the sample input from /home/oracle/soa-osb/input/small.txt & click Execute 77. You should see the following response (one-way invocation, hence no response). Section 3.3 Page 22 of 34

23 78. View Message Reporting data a. Go to Oracle Service Bus Console. b. Navigate to Operations followed by Message Reports. c. Date Range: All d. You will see the following report. The requisition is entered into the database table OSB_REQUISITION. You can query the OSB_REQUISITION table to see the inserted row. 3.4 Receive PO Note: The solution for this section can be found in /home/oracle/soaosb/solutions/chap-3/chap-3b-solution-sbconfig.jar What is being done? In this section, you will create JCA DB Proxy Service that polls for new Purchase Orders in the Database and Routes the transformed Purchase Order to a HTTP Business Service, which invokes the POProcessing SOA Composite for Purchase Order processing. Section 3.4 Page 23 of 34

24 OSB 11gR1 Workshop Following steps will be performed 79. JDeveloper - Create JCA DB Adapter files to poll the Database for new Purchase Orders. 80. OSB Console - Import JCA DB Adapter files. Create JCA DB Proxy Service to poll for single Purchase Order. Transform and route the Purchase Order to the business service created in the next step. 81. OSB Console - Create HTTP Business Service to invoke the POProcessing SOA Composite High Level Steps Create Database Adapter artifacts in Jdeveloper 1. Creating new SOA Application (You can jump to Step 2 if the SOA Application is already created as part of the Create Requisition section) a. Application Name: OSBDemo b. Directory: /home/oracle/jdeveloper/mywork/osbdemo c. Project Name: DBArtifacts d. Directory: /home/oracle/jdeveloper/mywork/osbdemo/dbartifacts e. Project Technologies: SOA f. Empty Composite 2. Adding the database adapter a. Drag and Drop Database Adapter from Component Palette to Exposed Services swim lane b. DbAdapter (Inbound) Service Name: receivepo c. Choose Connection SOADemo or Create Database Connection with details (Jump to d if SOADemo connection exists): Section 3.4 Page 24 of 34

25 i. Connection Name: SOADemo ii. Connection Type: Oracle (JDBC) iii. Username: SOADEMO iv. Password: soademo v. Save Password: Checked vi. Enter Custom JDBC URL: Unchecked vii. Driver: thin viii. Host Name: localhost ix. JDBC Port: 1521 (or the port number of your database) x. SID: soa11gdb (or the SID of your database) d. JNDI name: eis/db/soademo e. Operation Type: Poll for New or Changed Records in a Table f. Import OSB_PURCHASEORDER table (search for %OSB%) make note on hitting query button, selecting table, and adding to selected list g. Define Primary key: ID h. Note on bypassing relationships panel and attribute filtering i. After Read: Delete the Row(s) that were Read j. Finish k. Save all (always a good thing in IDE) Import Database Adapter artifacts into Oracle Service Bus 1. Log into Oracle Service Bus console 2. Create Session 3. Add Project: POProcessing 4. Create Folder: Resources (under the project POProcessing) 5. Navigate to folder Resources (under the project POProcessing) by clicking on the folder name 6. Create Resource: Resources from URL a. URL: file:/home/oracle/jdeveloper/mywork/osbdemo/dbartifacts/receivepo _db.jca b. Resource Name: receivepo_db c. Resource Type: JCA Binding 7. Click Next, followed by Import Section 3.4 Page 25 of 34

26 OSB 11gR1 Workshop 8. Resulting resources after the Import a. POProcessing/Resources/receivePO_db JCA Binding b. POProcessing/Resources/receivePO WSDL c. POProcessing/Resources/xsd/receivePO_table XML Schema d. POProcessing/Resources/receivePO-or-mappings XML Document Create Proxy Service from Database Adapter JCA File 1. Create Folder: ProxyServices under POProcessing project 2. Navigate to folder POProcessing/Resources by clicking on folder Resources 3. Click on the Generate WSDL and Service for this JCA Binding Resource Action Icon for the receivepo_db JCA Binding 4. Generate service in POProcessing/ProxyServices folder 5. Resulting resources a. POProcessing/ProxyServices/receivePO_db Proxy Service b. POProcessing/ProxyServices/receivePO_db - WSDL Import WSDL for POProcessing Composite Service in SOA Suite This WSDL will be used later to create the OSB Business Service 1. Navigate to folder POProcessing/Resources 2. Create Resource from URL a. URL: (replace host name appropriately) b. Resource Name: receivepo_soa c. Resource Type: WSDL 3. Click Next, followed by Import 4. Resulting resources after Import c. POProcessing/Resources/XMLSchema_<someNumber> schema a. POProcessing/Resources/receivePO_SOA - WSDL Create Business Service from WSDL 1. Create Folder BusinessServices under the project POProcessing 2. Navigate to folder BusinessServices (under the project POProcessing) by clicking on the folder name 3. Create Resource: Business Service (in this folder) a. Service Name: receivepo Section 3.4 Page 26 of 34

27 b. WSDL Web Service: POProcessing/Resources/receivePO_SOA i. (port): execute_pt c. Click Submit d. Click Next e. Protocol: http f. Click Next g. Click Last h. Click Save Complete Proxy Service Message Flow First step is to create a Route action routing to the business service invoking the SOA composite service receivepo. 1. Select Message Flow for POProcessing/ProxyServices/receivePO_db proxy service 2. Add Route 3. Edit Route 4. Add an Action -> Communication -> Routing: a. Pick business service: POProcessing/BusinessServices/receivePO a. Operation: execute b. Click Save Second step is to add Pipeline Pair with 5. Report action to report the Purchase Order from Database a. Add Pipeline Pair above route node b. Add Stage to Request Pipeline c. Edit Stage d. Add an Action -> Reporting -> Report 1. Report: $body 2. Add Key 1. Key Name: DB_ID 2. Key Value:./rec:OsbPurchaseorderCollection/rec:OsbPurchaseorde r/rec:id in variable body 3. Click Save 6. Transform Purchase Order from Database to the format of the Purchase Order required by the SOA receivepo service Section 3.4 Page 27 of 34

28 OSB 11gR1 Workshop a. Select stage1, Add Stage b. Edit stage2 c. Add Assign action (1) - Select Message Processing->Assign action to select Purchase Order from the Database PurchaseOrderCollection 1. Assign $body/rec:osbpurchaseordercollection/rec:osbpurchaseorde r to dbpo 2. Click Save 3. Click Save All d. Add Assign action (2) to transform Database Purchase Order to SOA Purchase Order. We will use a XQuery resource to perform this transformation 1. Create Xquery Resource 1. Select POProcessing/Resources by clicking on the folder name 2. Create Resource: Resources from URL 2. Add Assign to Stage 2 a. URL: file:/home/oracle/soa-osb/solutions/chap- 3/dbPO_to_soaPO.xq b. Resource Name: dbpo_to_soapo c. Resource Type: XQuery d. Click Next, followed by Import 1. Navigate to POProcessing/ProxyServices/receivePO_db 2. Select to see Message Flow 3. Select stage2,, Edit Stage 4. Add Assign action: Select the Assign action added in Step c,, right-click, select Message Processing->Assign action 5. Assign: - Click on XQuery Resources. Browse to select POProcessing/Resources/dbPO_to_soaPO a. Variable Names And Bindings: osbpurchaseorder1 - $dbpo b. Click Save c. to variable soapo e. Add Assign action (3) Select the Assign action added in Step d, rightclick, select Message Processing->Assign. Add soap-env:body wrapper around SOA Purchase Order and assign to $body as shown below Section 3.4 Page 28 of 34

29 1. Assign <soap-env:body>{$soapo}</soap-env:body> to body 2. Click Save 7. Report action to report payload sent to SOA receive PO service a. Select stage2, Add Stage b. Select stage3, Edit Stage c. Add an action: Reporting->Report: 1. Expression - $body 2. Click Save 3. Click Add a key 1. Key Name: SOA_ID 4. Click <XPath> 1. Add (User Defined) Namespace (as shown below): a. Prefix: ord b. URI: c. Click Add Section 3.4 Page 29 of 34

30 OSB 11gR1 Workshop 2. In the XPath Expression Editor text area enter./ord:purchaseorder/ord:id 3. Click Save 5. in variable body 6. Click Save 7. Click Save All 7. Activate Session by clicking on Activate in Change Center Section 3.4 Page 30 of 34

31 Add optional Description and click Submit Test You will test the receivepo proxy service indirectly by using the createrequisition proxy service. createrequisition proxy service inserts the Requisition into the Database. The Requisition table in the database is configured with a trigger that populates the Purchase Order table when a new Requisition is inserted into the Requisition table. The receivepo proxy service polls the Purchase Order table in the database for new Purchase Orders, transforms the Purchase Order to the format required by the SOA receivepo composite service, and sends the transformed Purchase Order to the SOA receivepo composite service from processing. Hence, the test for receivepo proxy service begins with invoking the createrequisition proxy service to create a Requisition. 1. To test the createrequisition proxy service, navigate to the Requisition project. Launch the test console by clicking on the icon under Actions after navigating to Resource Browser followed by Proxy Services. Section 3.4 Page 31 of 34

32 OSB 11gR1 Workshop 2. Load the sample input from /home/oracle/soa-osb/input/small.txt & click Execute 3. You should see the following response Section 3.4 Page 32 of 34

33 4. Verifying the test was successful 1. In Oracle Service Bus console go to Operations followed by Message Reports a. You will see one message report from the createrequisition proxy service and two message reports from receivepo proxy service. You can look at the detail to make sure the content looks correct 2. Next, verify two files are written to /home/oracle/scratch. These files are written by POProcessing & ConsumeJMSFulfillment composites respectively (sort by time) a. order_<#>.txt Section 3.4 Page 33 of 34

34 OSB 11gR1 Workshop b. write_fulfill_<#>.txt 3. Click on POProcessing Composite in the Enterprise Manager, Fusion Middleware Control. Select the composite instance from the Dashboard tab. You will see the following trace Success You are done with Chapter 3! Section 3.4 Page 34 of 34