Integrate a sales order validation process between SAP and Siebel using WebSphere Process Server and WebSphere Adapters

Transcription

1 Integrate a sales order validation process between SAP and Siebel using WebSphere Process Server and WebSphere Adapters Qian Li Jin jinql@cn.ibm.com Staff Software Engineer IBM June, 2007 Copyright International Business Machines Corporation All rights reserved. This article describes how to develop a sample business scenario using IBM WebSphere Process Server (hereafter called Process Server) and WebSphere Adapters. The scenario is a sales order validation process, in which a front-end Siebel system and a back-end SAP system interact with the Business Process Execution Language (BPEL) module in Process Server. The article will introduce the common steps involved in analyzing the business requirements and integrating existing enterprise information systems to build a complex and interactive business process. The article describes: 1. The basic steps of analyzing and building a business process 2. How to integrate data and operations between a SAP and Siebel system using adapters 3. How to create a Siebel event table and Siebel trigger and set up a Siebel adapter inbound interaction 4. How to integrate the process using BPEL 5. How to update the data for better performance You should have basic knowledge of business integration, Process Server, WebSphere Adapters and WebSphere Integration Developer (hereafter called Integration Developer).

2 Introduction...3 Business scenario overview...3 Building an IT solution for the business process...4 Step 1: Understand the business process from a technical view...4 Step 2: Clarify the interactions for the scenario...5 Step 3: Design the Data Format and Transformation...5 Implement the sales order process scenario...6 Step 1: Set up the development and testing environment...6 Step 1. Check Integration Developer and its integrated test environment...7 Step 2. Set up the J2C authentication configurations...7 Step 3. Set up the dependency files for connecting to the SAP and Siebel systems... 8 Step 4. Prepare test data...8 Step 5. Enable the Siebel Account Status field...10 Task 2: Set up the Siebel inbound environment...11 Step 1. Create the data structure of the event table in Siebel Step 2. Create the new page tabs Step 3. Activate the event table...14 Step 4. Create the Siebel trigger...15 Step 5. Compile the projects and reload the Siebel server...17 Step 6. Create the view for the event table in the Siebel Web client...18 Task 3: Design the scenario interactions and create the modules...19 Task 4: Generate the business objects and adapter component binding Step 1: Generate the outbound Siebel sales order business object...22 Step 2: Generate the outbound Siebel Account business object Step 3: Generate the inbound Siebel sales order business object...27 Step 4: Generate the outbound SAP sales order BAPI business object...27 Step 5: Generate the outbound SAP material BAPI business object...29 Step 6: Simplify the Siebel business objects...29 Step 7. Create the generic Business Object for BPEL...29 Task 5: Create the mediations...31 Step 1. Create the interfaces for the BPEL component...31 Step 2. Create the data maps Step 3. Create the interface maps...42 Task 6: Implement the BPEL process for the business logic...45 Step 1. Create the BPEL component Step 2. Design and implement the BPEL logic...46 Deploy and run the sales order process scenario...57 Task 1: Deploy the sales order process scenario...58 Task 2: Run the sales order process scenario with invalid input data...58 Task 3: Run the sales order process scenario with correct input data...60 Task 4: Uninstall the modules...61 Conclusion Resources About the author... 62

3 Introduction This article describes how to develop a sample business scenario using Process Server and WebSphere Adapters. Business integration enables business flexibility through the integration of systems, data, applications, processes and people across and beyond an enterprise. It helps enterprises to reduce complexity, extend existing IT systems and dynamically respond to changing business conditions. This article introduces a sample business scenario, then describes an end-to-end solution using WebSphere Business Integration V6 products. It shows you the steps necessary to implement the solution. Sample code is provided for download. Business scenario overview Let s look at a scenario in which a company has two existing enterprise information systems to store data and process business logic. One is Siebel 7.8, which is used to store customer information and is also used by the front-end sales team to place customer orders. The other is SAP R/3, which is used to manage the back-end manufacture and storage system. Figure 1. Sales Order Scenario - Business Requirement The company now has a requirement to build an integrated sales order process. The main process is to verify a sales order created in Siebel and create a corresponding sale order record in SAP. The detailed requirement is described below. The sales person logs into the Siebel sales application's Web client and enters the sales order information. When the sales order is submitted to Siebel system, the business integration process should get the required data, and start the order validation, which includes the following steps: 1. Verify the customer s good credit rating from the Siebel system. 2. Verify that the company has sufficient inventory for the order from the SAP system.

4 If the verification is successful, a new sales order record is created in SAP with the corresponding information. If the verification fails, no record is created in SAP. Whether or not the verification is successful, the sales order record in the Siebel system is updated with the required information. This enables the sales person to get the status of the order. Building an IT solution for the business process This section introduces the simple steps to build an IT solution for this business scenario. If the business process were complex, the IT architect or integration developer could use WebSphere Business Modeler to model the business logic and interaction styles. But in this case, the business process is simple, so directly designing IT solution is reasonable. We ll use WebSphere Business Integration V6 products to implement this solution. Process Server V6.0.2 works as the runtime environment for the business process. Since the existing Enterprise Information Systems (EIS), in this case Siebel and SAP, need to be integrated in the business process solution, we ll use WebSphere Adapter for Siebel V6.02 and WebSphere Adapter for SAP V6.0.2 as the adapters between the runtime environment and the EIS. Figure 2. Sales Order Scenario - Integrated Architecture Step 1: Understand the business process from a technical view The first step to building an IT solution is to understand the business process from a technical perspective. Try to rewrite the business process from a technical perspective, as follows: The sales person logs onto the Siebel sales application s Web client and enters the sales order information. When the sales order record is submitted to Siebel, an inbound event is triggered. The Siebel order business object is retrieved by the Siebel Adapter and forwarded to a BPEL process component in Process Server. Upon receiving the sales order business object, the BPEL process retrieves the customer s credit rating from Siebel using the Siebel Adapter. If the customer s credit rating is poor, the order is rejected. Otherwise the BPEL process uses the SAP Adapter to check SAP s inventory for the

5 product being ordered. If the product is in stock and has sufficient quantity, a new sales order is created in SAP and the corresponding sales order in Siebel is updated to indicate success. If SAP indicates insufficient inventory, no sales order is created in SAP and the Siebel sales order business object is updated to indicate insufficient inventory. The sales person can see the status of his or her sales order from the Siebel Web client, and can act accordingly. Step 2: Clarify the interactions for the scenario As you can see, Process Server, WebSphere Adapter for SAP and WebSphere for Siebel are required to implement this business process. A Process Server BPEL component is used to hold the business logic and process. This component connects to SAP and Siebel using the corresponding adapters. The SAP and Siebel Adapters are responsible for the interactions between Process Server and the SAP or Siebel systems. Based on the above scenario description, following are the necessary interactions in the scenario: The Siebel Adapter retrieves a sales order record from the Siebel system and passes it to the Process Server BPEL component. The Siebel Adapter inbound feature is used to implement this. The BPEL component, which holds the business logic, uses the Siebel Adapter outbound feature to check the credit and update the sales order status in Siebel system. The BPEL component uses the SAP Adapter Outbound BAPI feature to check the inventory and create an order record in SAP system. Step 3: Design the Data Format and Transformation Before trying to implement the integration scenario, you need to design how to handle the data. WebSphere Process Server uses the Service Data Object (SDO) model to represent the business data in the integration environment. The format of data in Siebel and SAP is quite different. This data needs to be transformed to SDO format in order to be handled by the Process Server. Following are some important design decisions made for the scenario data: What data will we use in Siebel? In this scenario, the Business Object Order and Business Object account in Siebel are needed for checking the credit and updating the sales order status. We ll use the Siebel Adapter Enterprise Metadata Discovery (EMD) to automatically generate the Business Object (BO) Schema. What data and interaction will we use in SAP?

6 The scenario requires that we check the material inventory and create the order in the SAP system. Therefore, we ll use BAPI_MATERIAL_AVAILABILITY and BAPI_SALESORDER_CREATEFROMDAT2 to interact with SAP. We ll use the SAP Adapter to generate the business object schema related to the BAPIs automatically. What data will we use in BPEL component? The business objects generated from Siebel and SAP system are usually big, and include many fields and child business objects. Since only some of the fields in the business object are required for the BPEL component, it is recommended that you create a generic business object (GBO) in the BPEL component that contains only the required field and data. This will improve the efficiency. How do we transfer data between different formats? Based on the above description, the following business objects are generated: Siebel Order, Siebel Account, SAP Material, SAP Order, BPEL Generic BO. We ll use the Process Server data map to transfer data between these BOs. Implement the sales order process scenario This section introduces the steps for implementing the scenario. You need to complete the following tasks to implement the scenario: 1. Set up the development and test environment 2. Set up the Siebel inbound environment 3. Design the scenario interactions and create the modules 4. Generate the data, including the BOs and Adapter component binding 5. Create the mediations, including the data map, interface, and interface map 6. Implement the BPEL process for the business logic The set-up tasks (1 and 2) include preparation and required configurations for both the development environment and the EIS environments. For tasks 3-6, the sample project interchange file, which includes all the scenario code, is available for download. You can import that file directly into the Integration Developer workspace. As some of the steps are complex, it is recommended that you directly import the artifacts, rather than creating them from scratch. Step 1: Set up the development and testing environment We ll use Integration Developer to develop and test the scenario, so the first step is to configure the development and testing environment. Then, we need to create some test data in the EISs.

7 Step 1. Check Integration Developer and its integrated test environment Start Integration Developer and ensure that you can start the Process Server test environment. Figure 3. Start WebSphere Process Server Step 2. Set up the J2C authentication configurations Complete the following steps to create the Java 2 Platform, Enterprise Edition (J2EE) Connection (J2C) authentication data entries, which are needed by the adapters for connecting to the EIS systems: 1. Open the WebSphere Application Server administrative console and log in as shown: 2. Select Security => Global security => JAAS Configuration => J2C Authentication data. 3. In the J2C authentication data entries dialog, click New to create new entry. 4. Specify SIEBEL as the Alias, and enter the User ID and Password for the Siebel Server, as shown in Figure Repeat steps 1-3 to create another J2C authentication data entry with SAP as Alias, and specify the User ID and Password for the SAP system. Figure 4. Create the J2C Authentication Data Entries

8 Step 3. Set up the dependency files for connecting to the SAP and Siebel systems Before using the SAP Adapter and Siebel Adapter, some dependency files are needed to connect to the corresponding SAP and Siebel systems. You can usually find these files on the machines on which the SAP and Siebel systems are installed. To find and set up these files, do the following: 1. Close Integration Developer, if it is open. 2. Find the following files on the Siebel server: Siebel.jar SiebelJI_enu.jar 3. Copy both jar files to <WID_DIR>\runtimes\bi_v6\lib. (<WID_DIR> is the directory in which WebSphere Integration Developer is installed. 4. Find the following files on the SAP server: sapjco.jar sapjcorfc.dll librfc32.dll MSVCP71.DLL msvcr71.dll 5. Copy the sapjco.jar file to <WID_DIR>\runtimes\bi_v6\lib. (<WID_DIR> is the directory in which WebSphere Integration Developer is installed.) 6. Copy all four DLLs to <WID_DIR>\runtimes\bi_v6\bin. 7. Copy all four DLLs to <WID_DIR>\eclipse\jre\bin. 8. Remember where you put these dependency jars, as you ll need them later when running adapter enterprise metadata discoveries. Step 4. Prepare test data Since this scenario integrates a sales order process in SAP and Siebel, we need to align some data. In a real application, we would likely create a static table to store and map key field values between different EIS systems. However, in our scenario, for simplicity the keys between SAP and Siebel are manually entered as the same value. The Account Name in Siebel is equal to the Customer Number in SAP, and the Product Name in Siebel is equal to the Material Number in SAP. 1. In the Siebel Web client Siebel Sales, select the Account view, and create a new Account record with as Account Name, as shown in Figure 5.

9 Figure 5. Create account record in Siebel 2. In the SAP client, enter the short cut /nfd01 to create a new customer with as the Customer Number, as shown in Figure 6. Figure 6. Create customer record in SAP 3. In the Siebel Web client Siebel Sales, select Navigate => Site Map => Administration => Product, and create a new Product record with as the Product Name, then click Release, as shown in Figure 7. Figure 7. Create product record in Siebel system 4. In the SAP client, enter the short cut /nmm01 to create a new material with as the Material Number, as shown in Figure 8.

10 Figure 8. Create material record in SAP Step 5. Enable the Siebel Account Status field In Siebel 7.8.2, the Business Component Account has a field Account Status that we need to use to check the account status. By default, this field is not active, so we need to activate it manually by doing the following: 1. In the project panel of Siebel Tools, lock the Account project. 2. Navigate to the Business Components panel, and select the Account business component. Select the Fields sub-panel, and find the Account Status field. Check Force Active for the Account Status field, as shown in Figure 9. Figure 9. Activate the Account Status field in Siebel 3. Click Save All in Siebel Tools to save these changes.

11 4. Stop the two services related to Siebel server as shown in Figure 10. Figure 10. Stop the services related to Siebel 5. In Siebel Tools, select Menu => Tools => Compile Projects. In the Object Compiler panel, select Locked projects to compile and set the Siebel Repository file to the Siebel server directory <SiebelServerDir>\OBJECTS\ENU\siebel.srf. Then click Compile. 6. After compiling is done, close Siebel Tools. Then copy the updated Siebel siebel.srf file to the Siebel Web client directory and the Siebel Tools directory and overwrite the old files: <SiebelWebClientDirectory>\OBJECTS\ENU\siebel.srf <SiebelToolsDirectory>\OBJECTS\ENU\siebel.srf 7. Start the two services related to the Siebel server. Task 2: Set up the Siebel inbound environment When a sales person creates a sales order in the Siebel Web client, the Siebel Adapter inbound function is used to trigger the business process. In order to use this function, we need to create an event table and a trigger in the Siebel server. If a new sales order record is created, the Siebel trigger will create the corresponding record in the event table. The Siebel Adapter then gets the records from the event table and sends the retrieved business object to BPEL to process. Complete the steps in this section to create the event table and trigger in the Siebel server. Step 1. Create the data structure of the event table in Siebel When Siebel Adapter V6.0.2 is installed, the IBM2.sif file can be directly imported into Siebel Tools. The data structure of event table can then be automatically created. You can also create event table definition manually. We ll describe both methods here, and you can choose which one to use. Import IBM2.sif to automatically generate the event table: 1. Open Siebel Tools and select Tools => Import from Archive. 2. Click Yes when prompted. 3. Select the following archive file to import. (Modify the directory as needed to reflect where the Siebel Adapter is installed.): C:\IBM\ResourceAdapters\Siebel\Adapter\Siebel\samples\Event_pkg\IBM2.sif 4. Click Next to accept all default settings. 5. Click Yes/Finish to process the import.

12 Figure 11. Import the artifacts into Siebel Create the event table manually: 1. In Siebel Tools, create a new project called IBM2 and lock it. 2. Create a new table called CX_IBM2 containing the columns and attributes shown in Figure 12:

13 Figure 12. Create the Siebel event table 3. Create a new Business Component named IBM2 based on the CX_IBM2 table, as shown in Figure 13. Figure 13. Create the Siebel business component for the event table

14 4. Create a new business object named IBM2, which will use the business component IBM2 as the primary business component. 5. Create a new applet named IBM2 for Business Component IBM2. 6. Create a new view named IBM List View too for business object IBM2 and associate the view with the applet IBM2. 7. Create a new screen named IBM2 and associate it with the view IBM List View too. Step 2. Create the new page tabs In the Application panel of Siebel Tools, select Siebel Sales Enterprise and select Tools => Lock Project. Then, create a new Page Tab as shown in Figure 14: Figure 14. Create a view for the Siebel event Step 3. Activate the event table The event table needs to be activated before it will work. 1. In the Table panel of Siebel Tools, select CX_IBM2 and click Apply. 2. In the dialog that displays, enter user name and password of the Siebel database table owner in the Database User and Database User Password fields. Leave the default values for all other fields, and click Apply. 3. Click Activate in the Table panel, as shown in Figure 15.

15 Figure 15. Activate the Siebel event table Step 4. Create the Siebel trigger The trigger will be used to create the inbound event automatically when a Siebel order record is created. 1. In the Business Component panel of Siebel Tools, right-click Order Entry - Orders and select Edit Server Scripts. 2. Select escript in the dialog that displays. 3. In the Script Editor panel, implement the following functions, as shown in Figure 16 and described below. Figure 16. Develop the Siebel trigger script In general => declarations, enter the following: var verb=null; var forcreate=false; In BusComp => BusComp_PreNewRecord, enter the following: function BusComp_PreNewRecord () { verb="create"; forcreate=true; return (ContinueOperation); } In BusComp => BusComp_PreDeleteRecord, enter the following:

16 function BusComp_PreDeleteRecord () { var EventBO=new BusObject; var EventBC; { var RowId = this.getfieldvalue("id") EventBO=TheApplication().GetBusObject("IBM2"); EventBC=EventBO.GetBusComp("IBM2"); EventBC.SetViewMode(AllView); EventBC.ActivateField("Event Id"); EventBC.ActivateField("Object Name"); EventBC.ActivateField("Object Key"); EventBC.ActivateField("Event Type"); EventBC.ActivateField("Priority"); EventBC.ActivateField("Status"); EventBC.ActivateField("Description"); EventBC.NewRecord(NewAfter); EventBC.SetFieldValue("Object Name", BOOrderEntryU40SalesU41BCOrderEntryU45OrdersBG"); EventBC.SetFieldValue("Object Key", "Id="+RowId); EventBC.SetFieldValue("Event Type", "Delete"); EventBC.SetFieldValue("Priority", "1"); EventBC.SetFieldValue("Status", "0"); EventBC.SetFieldValue("Description", "Order Event"); } return (ContinueOperation); } In BusComp => BusComp_WriteRecord, enter the following: function BusComp_WriteRecord () { var EventBC; var EventBO = new BusObject; { var RowId = this.getfieldvalue("id"); var Created_ts = this.getfieldvalue("created"); var Updated_ts = this.getfieldvalue("updated"); { var theverb=""; if(verb == "Create") { theverb = "Create"; verb=null; } else { theverb = "Update"; } EventBO = TheApplication().GetBusObject("IBM2"); EventBC = EventBO.GetBusComp("IBM2"); EventBC.SetViewMode(AllView); EventBC.ActivateField("Event Id"); EventBC.ActivateField("Object Name"); EventBC.ActivateField("Object Key"); EventBC.ActivateField("Event Type");

17 EventBC.ActivateField("Priority"); EventBC.ActivateField("Status"); EventBC.ActivateField("Description"); EventBC.NewRecord(NewAfter); EventBC.SetFieldValue("Object Name", "BOOrderEntryU40SalesU41BCOrderEntryU45OrdersBG"); EventBC.SetFieldValue("Object Key", "Id="+RowId); EventBC.SetFieldValue("Event Type", theverb); EventBC.SetFieldValue("Priority", "1"); EventBC.SetFieldValue("Status", "0"); EventBC.SetFieldValue("Description", "Order Event"); EventBC.WriteRecord(); } } } 4. Save all the scripts by clicking Save All in Siebel Tools. Step 5. Compile the projects and reload the Siebel server. 1. Stop the two services related to Siebel server. Figure 17. Stop the services related to Siebel 2. In Siebel Tools, select Menu => Tools => Compile Projects. 3. In the Object Compiler panel, select Locked projects to compile and set the Siebel Repository file to the Siebel server directory <siebelserverdir>\objects\enu\siebel.srf. Then click Compile, as shown in Figure 18. Figure 18. Compile the Siebel objects 4.

18 4. After compiling is complete, close Siebel Tools, and copy the updated siebel.srf file to the Siebel Web client directory and the Siebel Tools directory and overwrite the old files: < SiebelWebClientDirectory>\OBJECTS\ENU\siebel.srf < SiebelToolsDirectory>\OBJECTS\ENU\siebel.srf 5. Start the two services related to the Siebel server. Step 6. Create the view for the event table in the Siebel Web client We need to create a view in the Siebel Web to display the content of event table. 1. Select Siebel Web Client => Siebel Sales, then select Navigate => Site Map => Administration Application => Views. 2. In the Views panel, create a new view named IBM List View too. 3. Select Siebel Web Client => Siebel Sales, then select Nevigate => Site Map Administration Application => Responsibilities. 4. In the Responsibility panel, create a new responsibility named IBM Responsibility. Associate the IBM List View too view with the responsibility in the bottom left sub-panel. Then, add the Siebel server user IDs, which are used by the Siebel Adapter, to the bottom right sub-panel, as shown in Figure 19: Figure 19. Create a responsibility for the Siebel event table view 5. Log out and restart the Siebel Sales Web client. The IBM2 tab is shown correctly as shown in Figure 20.

19 Figure 20. Siebel event table view Task 3: Design the scenario interactions and create the modules As described, we ll use a BPEL component to hold the business logic. The following interactions are needed between BPEL component and the adapters: The Siebel Adapter inbound function is used to get the new Siebel order record, and send the data to the BPEL component. The Business Object Interface of the Siebel adapter is used for this interaction. The BPEL component checks the credit information by calling the Siebel adapter outbound business object interface. The BPEL component updates the Siebel order status by calling the Siebel adapter outbound business object interface. The BPEL component checks the material information by calling the SAP adapter outbound BAPI interface. The BPEL component creates a new order record in the SAP system by calling the SAP adapter outbound BAPI interface. This scenario needs three components: a BPEL component, a Siebel Adapter component and a SAP Adapter component. In an SOA scenario, you would probably want to put each component in a separate modules to facilitate re-use. But in our scenario, for the sake of simplifying development, all the components will be implemented in one business integration module. Because business objects in EISs like Siebel and SAP are usually big and complex, but the BPEL component needs only a few fields of the business objects, we ll create some mediation components to transfer the interfaces and data between BPEL components and adapter binding instances. Figure 21 show the overall connections and interactions between one BPEL component, five adapter binding instances, and five mediation components, or interface maps.

20 Figure 21. Business process module Two modules are needed to implement the scenario. One is a business integration module, which is used to store all BPEL, mediation and adapter components. The other is the Java project, which will include Adapter Foundation Classes (AFC). In this scenario, the CWYBS_AdapterFoundation.jar file is needed by the BPEL component as utility classes. Complete the following steps to create the modules: 1. Launch WebSphere Integration Developer and select a new workspace. 2. Switch to the Business Integration perspective. Right-click the left pane and select New => Module. 3. In the New Module dialog, specify OrderProcess as the module name and click Finish. 4. Switch to the Java perspective and create a Java project called CWYBS_AdapterFoundation. 5. Right-click the CWYBS_AdapterFoundation project, and select Import. 6. Select File System. 7. Navigate to the CWYBS_AdapterFoundation.jar file and click Finish. 8. Right-click the CWYBS_AdapterFoundation project, and select Properties. 9. In the Properties dialog, go to the Java Build Path section. 10. On the Libraries tab, click Add JARs. 11. Select CWYBS_AdapterFoundation.jar, and click OK. 12. Switch to the Business Integration perspective, right-click OrderProcess, and select Open Dependencies. 13. Add the CWYBS_AdapterFoundation project into the Java dependency list of OrderProcess module, as shown in Figure 22:

21 Figure 22. Setup dependencies for the business module 14. Click Save All to save all files. 15. From the Integration Developer menu, select Project => Build All. Task 4: Generate the business objects and adapter component binding Before implementing the business logic, you must first define the data types. In this section, we ll describe how to design and generate the data types. Since the order process in our scenario is integrated between SAP and Siebel, we need to retrieve the data types

22 from the two systems. Both SAP Adapter and Siebel Adapter provide Enterprise Metadata Discovery (EMD) tools to generate the data types and adapter binding instances automatically. We will also manually design a generic business object to store the interaction data in BPEL process. Step 1: Generate the outbound Siebel sales order business object 1. First, import the Siebel resource adapter. In Integration Developer, select Menu => File => Import. 2. Select RAR as the file to import. 3. Click Browse, and select the Siebel adapter CWYEB_SiebelAdapter.rar, then click Finish. 4. Switch to the Java perspective. Right-click the imported Siebel Adapter module and select Properties. 5. In the Java Build Path dialog, add two dependency jar files (Siebel.jar and SiebelJI_enu.jar) for Siebel, and click OK, as shown in Figure 23. Figure 23. Add dependency files for the Siebel Adapter 6. Select Menu => Project => Build All. 7. Switch to the Business Integration perspective. Right-click the OrderProcess module and select New => Enterprise Service Discovery. 8. In the Enterprise Service Discovery dialog, select WebSphere Adapter for Siebel and click Next. 9. In Configure Settings for Discovery Agent dialog, enter the connect string, language, user name, password properties for connecting to the Siebel

23 server. Select Siebel Business Objects for Siebel Metadata Type, then click Next, as shown in Figure 24. Figure 24. Configure settings for Enterprise Metadata Discovery 10. In the Find and Discovery Enterprise Service dialog, set the Query to Filter=Order, and click Execute Query, as shown in Figure 25:

24 Figure 25. Siebel business object tree 11. In the metadata tree, navigate to Order Entry (Sales), click Add to import list, then click Next. 12. Specify the following values on the Configure Object dialog: ServiceType: Outbound Namespace: BO Location: SiebelOrder Leave the default values for all other fields, then click Next. 13. Siebel EMD now generates the service files and business objects. After finishing, the Generate Artifacts dialog displays, as shown in Figure 26. Specify the following values: Module: OrderProcess Folder: SiebelOrder J2C Authentication Data Entry: widnode/siebel Leave the default values for all other fields, then click Finish.

25 Figure 26. Configuration dialog for generating artifacts The Siebel Order business object and the related adapter outbound binding instance are generated, as shown in Figure 27.

26 Figure 27. Generated adapter binding instances and business objects Step 2: Generate the outbound Siebel Account business object In the above step, we imported the Siebel Adapter into the project, so we can now use the Siebel EMD. We ll use the same steps as in Step 1 to generate the Siebel Account business object and the related adapter outbound binding instance, with the following exceptions: 1. In the Find and Discover Enterprise Service dialog, select Account ESP as the Siebel business object to import. 2. In Configure Object dialog, specify the following values: ServiceType: Outbound Namespace: BO Location: SiebelAccount 3. In Generate Artifacts dialog, specify the following values: Module: OrderProcess Folder: SiebelAccount J2C Authentication Data Entry: widnode/siebel

27 Step 3: Generate the inbound Siebel sales order business object Follow the same steps as in Step 1 to generate the Siebel sales order business object and the related adapter inbound binding instance, with the following exceptions: 1. In the Find and Discover Enterprise Service dialog, select Order Entry (Sales) as the Siebel business object to import. 2. In Configure Object dialog, specify the following values: ServiceType: Inbound Namespace: BO Location: SiebelOrder 3. In the Generate Artifacts dialog, specify the following values: Folder: SiebelOrder J2C Authentication Data Entry: widnode/siebel Step 4: Generate the outbound SAP sales order BAPI business object Complete the following steps to import the SAP Adapter into the project: 1. In Integration Developer, select Menu => File => Import. 2. Select RAR as the file to import. 3. Click Browse and select the SAP adapter CWYAP_SAPAdapter_Tx.rar file, then click Finish. 4. Switch to the Java perspective, and right-click the imported Siebel Adapter module and select Properties. 5. In the Java Build Path dialog, add the dependency jar file sapjco.jar for Siebel, then click OK. 6. Click Menu => Project => Build All. 7. Switch to the Business Integration perspective. Right-click the OrderProcess module and select New => Enterprise Service Discovery. 8. In the Enterprise Service Discovery dialog, select WebSphere Adapter for SAP and click Next. 9. In the Configure Settings for Discovery Agent dialog, specify the following values based on the SAP system and leave all the other fields as default, then click Next: UserName Password SAP Client SAP Application Server host SAP Interface: BAPI 10. In the Find and Discover Enterprise Services dialog, click the Execute Query. 11. In the metadata tree, navigate to RFC => Discover by Name and click Filter. 12. In the Filter dialog, specify BAPI_SALESORDER* as the filter value, and click OK. 13. In the metadata tree, expand RFC => Discover By Name (Filtered), and select the BAPI name BAPI_SALESORDER_CREATEFROMDAT2, then click Add to import list, as shown in Figure 28:

28 Figure 28. SAP BAPI object tree 14. In the pop-up dialog, check Use Field Name to generate attribute(s), and click OK. Then click Next. 15. Specify the following values in the Configure Object panel, then click Next: Object Location: SapOrder NameSpace: Business Object name: SapOrder Operations: Create 16. SAP EMD generates the service files and business objects. After finishing, the Generate Artifacts dialog displays. Specify the following values: Module: OrderProcess Folder: SapOrder Name: SAPOutboundInterface_Order J2C Authentication Data Entry: widnode/sap Leave the default values for all other fields, then click Finish.

29 The SAP sales order BAPI business object and the related adapter outbound binding instance are now generated. Step 5: Generate the outbound SAP material BAPI business object Since we ve imported the SAP Adapter into the project, we can now use the SAP EMD. Follow the same steps as in Step 4 to generate the SAP material BAPI business object and the related adapter outbound binding instance, with the following exceptions: 1. In Find and Discover Enterprise Service dialog, select BAPI_MATERIAL_AVAILABILITY to import. 2. In Configure Object dilaog, specify the following values: Object Location: SapMaterial NameSpace: Business Object Name: SapMaterial Operations: Retrieve 3. In the Generate Artifacts dialog, specify the following values: Module: OrderProcess Folder: SapMaterial Name: SAPOutboundInterface_Material J2C Authentication Data Entry: widnode/sap Step 6: Simplify the Siebel business objects In the above steps, we generated the Siebel business objects are generated. As we ve discussed business object structure may be very complex with many child business objects related to a parent business object. Since we only need part of the business objects for our scenario, complete the following steps to simplify the business objects for efficiency: 1. Double-click BOOrderEntryU40SalesU41BCOrderEntryU45Orders to open the Business Obejct editor. 2. Find the two child business objects, BOOrderEntryU40SalesU41BCAccount and BOOrderEntryU40SalesU41BCOrderEntryU45LineItems. Keep these business objects, and delete all the other child business objects related to the BOOrderEntryU40SalesU41BCOrderEntryU45Orders business object. Step 7. Create the generic Business Object for BPEL The generic business object will be used in BPEL module to store the common values, which are needed by the integration process. It will be much smaller than the Siebel and SAP Business Objects to improve the efficiency. 1. Switch to the Business Integration perspective, right-click Data Types and select New => Business Object.

30 2. In the pop-up dialog, specify the following values and click Finish: Folder: GBO Name: OrderProcessGBO 3. Once the business object is created, right-click it and select Add attributes, as shown in Figure 29: Figure 29. Add attributes to the business object 4. Add the attributes shown in the following table: Field Name Type Description OrderName string The order name Quantity string The number of product in the order ProductName string The product name in the order MainPhone string The contact phone of the order customer SiebelAccountId string The ID of the account in Siebel, which is used to process the order SiebelOrderId string The ID of the order in Siebel SAPOrderNumber string The ID of the order in SAP CustomerNumber string The ID of the customer in SAP SapMaterialQuantity string The material stocks in SAP SiebelAccountStatus string The account status in Siebel, which is used to process the order SiebelOrderStatus string The order status in Siebel 5. In the left pane, right-click OrderProcessGBO and select Create a Business Graph to create a business graph for the business object. 6. Save all your changes and build the projects.

31 Task 5: Create the mediations In our scenario, there are five interactions between the BPEL module and adapters. By using the adapter EMDs, five adapter binding instances, or interfaces, are automatically generated. Correspondingly, five interfaces are needed by the BPEL module to connect to adapters, and give interface maps are needed to work as mediations between BPEL and the adapters. Since the BPEL module and adapters have different business object types, data maps will be created to transform the data. These data maps are needed by the interface maps. In this section, we ll create the necessary interfaces, data maps, interface maps. Step 1. Create the interfaces for the BPEL component For the BPEL component, we ll manually create five wsdl interfaces. One is used by the Siebel Adapter inbound binding to call the BPEL process. The rest are used by BPEL to call the Siebel and SAP Adapter outbound functions. To create the wsdl inbterfaces, do the following: 1. In the Business Integration perspective, select Interfaces and right-click OrderProcess, then select New => Interface. 2. In the pop-up dialog, specify the interface name, and click Finish. 3. In the Interface editor, add Request-Response Operation or One Way Operation, as shown in Figure 30. The former has a return value and the latter does not. Figure 30. Create the interfaces Interface Name 4. Edit the interface as follows, using the values in the following table. Add operations and change the operation names. Add an input variable and change the input variable name and type. Add an output variable and change the output variable name and type. Operation Name Input Variable Name Input Variable Type Output Variable Name Output Variable Type OrderProcessBPEL OrderProcess OrderGBO OrderProcessGBOBG RetOderGBO OrderProcessGBOBG CheckSiebelAccount Retrieve orderbg OrderProcessGBOBG retorderbg OrderProcessGBOBG CheckSapMaterial Retrieve orderbg OrderProcessGBOBG retorderbg OrderProcessGBOBG

32 UpdateSiebelOrder ApplyChanges SiebelOrderBG BOOrderEntryU40SalesU RetOrderUpdate OrderProcessGBOBG 41BCOrderEntryU45Orde rsbg CreateSapOrder Create orderbg OrderProcessGBOBG saporderret OrderProcessGBOBG Step 2. Create the data maps The following table shows the data transformation map requirements in this scenario. First we ll describe the common steps for creating a data map, then describe the detailed steps to create the data maps for our scenario. Source BO Destination BO Description Generic BO SAP Material BO Used in checking the SAP Material stocks Generic BO SAP Order BO Used in creating the Order in SAP Generic BO Siebel Account BO Used in checking the Account credit in Siebel Generic BO Siebel Order BO Used in updating the Order status in Siebel SAP Material BO Generic BO Used to map the return the SAP Material business object to the generic business object SAP Order BO Generic BO Used to map the return SAP Order business object to the generic business object Siebel Account BO Generic BO Used to map the return Siebel Account business object to the generic business object Siebel Order BO Generic BO Used to map the inbound Siebel Order business object to the generic business object Siebel Order BO Generic BO (2) Used to map the return Siebel Order business object to the generic business object Complete the following steps to create a data map: 1. In the Business Integration perspective for the OrderProcess module, right-click Mapping => Data Maps and select New => Business Object Map. 2. In the Business Object Map dialog, specify the following values and click Next: Folder: The directory of data map file Name: The data map name 3. In the Business Object Map dialog, specify the following values and click Finish: Inputs: The source business object of the data map Outputs: The destination business object of the data map

33 4. Design the data map. Several types of data transformation are defined in the data map. Some of the types that we ll use in our scenario are described in following table: Data Transformation Type Assign Description Give a static value to the field. How to create an instance Right-click on the field of the destination business object, and select Create Transform => Assign. This creates an Assign transformation for the field. Switch to Properties at the bottom, and left-click on the Assign. In the Details dialog, specify the values to assign to the field.

34 Move Join Move one field value of the source business object to one field of the destination business object. Join several source field values into one destination field value. Click and hold the left button in the source field, drag the line to the destination field, then release the button. Click and hold the left button in the source child business object, and drag the line to the destination child business object. Then left-click the item and select Join as the data transformation type. Then, wire other source fields into the Join item. Custom Java code to transfer complex data. There are two types of custom transformations: Visual and Java. In the Visual mode, you can write Java code by dragging graphic components. Click and hold the left button in the source child business object, and drag the line to the destination child business object. Then left-click the item and select Custom as the data transformation type. You can now wire multiple source and destination fields into the data transformation. When this is done, left-click Custom. The Properties dialog displays. There are two ways to edit the custom transformation.

35 In the Java mode, the input and output variables are automatically generated, you only need to input any required code. Submap Refer another data map to map child business objects. In the Visual mode, you can use the Writing and Developing Java code by drawing function. The elements in the Visual mode are either variable or method. You need to wire variable to method to run this method with input parameters. After you re finished drawing, switch to Java mode to see the automatically generated Java code. Note that after changing code in Java mode, you cannot switch back to Visual mode. Click and hold the left button in the source child business object, and drag the line to the destination child business object, then release. You can now create a Submap operation. Switch to the Properties dialog. Here you can set another data map as the submap for mapping the child business objects. 5. After finishing the data map design, save all files. Use the common steps described above to create the data maps we need for our scenario. Create the data map for Siebel Order BO to Generic BO: Folder: DataMap Name: SiebelOrderToGBO Inputs: BOOrderEntryU40SalesU41BCOrdersBG

36 Outputs: OrderProcessGBOBG Data Transformation Type Source business object (child business object) 1. Move BOOrderEntryU40SalesU41B COrderEntryU45OrderBG => BOOrderEntryU40SalesU41B COrderEntryU45Order 2. Move BOOrderEntryU40SalesU41B COrderEntryU45OrderBG => BOOrderEntryU40SalesU41B COrderEntryU45Order 3. Move BOOrderEntryU40SalesU41B COrderEntryU45OrderBG => BOOrderEntryU40SalesU41B COrderEntryU45Order 4. Move BOOrderEntryU40SalesU41B COrderEntryU45OrderBG => BOOrderEntryU40SalesU41B COrderEntryU45Order 5. Move BOOrderEntryU40SalesU41B COrderEntryU45OrderBG => BOOrderEntryU40SalesU41B COrderEntryU45Order 6. Custom Note: See Java code below. BOOrderEntryU40SalesU41B COrderEntryU45OrderBG => BOOrderEntryU40SalesU41B COrderEntryU45Order => OrderEntryU45LineItems 7. Move BOOrderEntryU40SalesU41B COrderEntryU45OrderBG => BOOrderEntryU40SalesU41B COrderEntryU45Order 8. Move BOOrderEntryU40SalesU41B COrderEntryU45OrderBG Source Fields Destination business object (Child business object) Id OrderProcessGBOBG => OrderProcessGBO OrderNumber OrderProcessGBOBG => OrderProcessGBO AccountId OrderProcessGBOBG => OrderProcessGBO MainPhoneNum ber OrderProcessGBOBG => OrderProcessGBO Account OrderProcessGBOBG => OrderProcessGBO OrderProcessGBOBG => OrderProcessGBO Status OrderProcessGBOBG => OrderProcessGBO verb OrderProcessGBOBG verb Destination Fields SiebelOrderId OrderName SiebelAccountId MainPhone CustomerNumber Quantity ProductName SiebelOrderStatus Custom Java code (6): java.util.list BOOrderEntryU40SalesU41BCOrderEntryU45OrdersBG_BOOrderEntryU40SalesU4 1BCOrderEntryU45Orders_OrderEntryU45LineItems = (java.util.list)boorderentryu40salesu41bcorderentryu45ordersbg_boordere ntryu40salesu41bcorderentryu45orders_orderentryu45lineitems; java.lang.string OrderProcessGBOBG_OrderProcessGBO_Quantity = (java.lang.string)orderprocessgbobg_orderprocessgbo_quantity; java.lang.string OrderProcessGBOBG_OrderProcessGBO_ProductName = (java.lang.string)orderprocessgbobg_orderprocessgbo_productname; commonj.sdo.dataobject lineitem = (commonj.sdo.dataobject) ( BOOrderEntryU40SalesU41BCOrderEntryU45OrdersBG_BOOrderEntryU40SalesU 41BCOrderEntryU45Orders_OrderEntryU45LineItems.get(0)); //commonj.sdo.dataobject product = lineitem.getdataobject("prodpromname");

37 OrderProcessGBOBG_OrderProcessGBO_ProductName = lineitem.getstring("product"); OrderProcessGBOBG_OrderProcessGBO_Quantity = lineitem.getstring("quantityrequested"); The finished data map should look like Figure 31: Figure 31. Data map for Siebel Order BO to Generic BO Create the data map for Siebel Order BO to Generic BO (2): Folder: DataMap Data Map Name: SiebelOrderToGBO_2 Source BO: BOOrderEntryU40SalesU41BCOrderEntryU45OrderBG Destination BO: OrderProcessGBOBG Data Transformation Type Source BO (Child BO) Source Fields Destination BO (Child BO) 1. Move BOOrderEntryU40SalesU41B COrderEntryU45OrderBG => BOOrderEntryU40SalesU41B COrderEntryU45Order 2. Move BOOrderEntryU40SalesU41B COrderEntryU45OrderBG Id OrderProcessGBOBG => OrderProcessGBO verb OrderProcessGBOBG verb Destination Fields SiebelOrderId Create the data map for Siebel Account BO to Generic BO: Folder: DataMap Data Map Name: SiebelAccountToGBO Source BO: BOAccountU45ESPBCAccountBG Destination BO: OrderProcessGBOBG Data Source BO (Child BO) Source Fields Destination BO (Child Destination

38 Transformation Type 1. Move BOAccountU45ESPBCAccou ntbg => BOAccountU45ESPBCAccou nt BO) AccountStatus OrderProcessGBOBG => OrderProcessGBO Fields SiebelAccountStatus Create the data map for SAP Material BO to Generic BO: Folder: DataMap Data Map Name: SiebelMaterialToGBO Source BO: SapSapMaterialWrapperBG Destination BO: OrderProcessGBOBG Data Transformation Type Source BO (Child BO) Source Fields Destination BO (Child BO) 1. Move SapSapMaterialWrapperBG => SapSapMaterialWrapper => SapBapiMaterialAvailability QuantityAvailabl eatplantlevel OrderProcessGBOBG => OrderProcessGBO Destination Fields SapMaterialQuantity Create the data map for SAP Order BO to Generic BO: Folder: DataMap Data Map Name: SAPOrderToGBO Source BO: SapSapOrderWrapperBG Destination BO: OrderProcessGBOBG Data Transformation Type Source BO (Child BO) Source Fields Destination BO (Child BO) 1. Move SapSapOrderWrapperBG => SapSapOrderWrapper => SapBapiSalesorderCreatefrom dat2 NumberOfGener ateddocument OrderProcessGBOBG => OrderProcessGBO Destination Fields SapOrderNumber Data Transformation Type Create the data map for Generic BO to Siebel Order BO: Folder: DataMap Data Map Name: GBOToSiebelOrder Source BO: OrderProcessGBOBG Destination BO: BOOrderEntryU40SalesU41BCOrderEntryU45OrderBG Source BO (Child BO) Source Fields Destination BO (Child BO) Destination Fields Notes 1. Assign BOOrderEntryU40SalesU41 Verb Value = Update

39 2. Move OrderProcessGBOBG => OrderProcessGBO 3. Join OrderProcessGBOBG => OrderProcessGBO SiebelOrderId SapOrderNumber BCOrderEntryU45OrderBG BOOrderEntryU40SalesU41 BCOrderEntryU45OrderBG => BOOrderEntryU40SalesU41 BCOrderEntryU45Order BOOrderEntryU40SalesU41 BCOrderEntryU45OrderBG => BOOrderEntryU40SalesU41 BCOrderEntryU45Order Id Description DestValue= SapDocumentNum ber= +sourcevalue Create the data map for Generic BO to Siebel Account BO: Folder: DataMap Data Map Name: GBOToSiebelAccount Source BO: OrderProcessGBOBG Destination BO: BOAccountU45ESPBCAccountBG Data Transformation Type Source BO (Child BO) Source Fields Destination BO (Child BO) 1. Move OrderProcessGBOBG => OrderProcessGBO SiebelAccountId BOAccountU45ESPBCAcc ountbg => BOAccountU45ESPBCAcc ount Destination Field(s) Id Create the data map for Generic BO to SAP Order BO: Folder: DataMap Data Map Name: GBOToSapOrder Source BO: OrderProcessGBOBG Destination BO: SapSapOrderWrapperBG Data Transformation Type Source BO (Child BO) Source Fields Destination BO (Child BO) 1. Move OrderProcessGBOBG verb SapSapOrderWrapperBG verb 2. Assign SapSapOrderWrapperBG => SapSapOrderWrapper => SapBapiSalesorderCreatefro mdat2 3. Assign SapSapOrderWrapperBG => SapSapOrderWrapper => SapBapiSalesorderCreatefro mdat2 4. Assign SapSapOrderWrapperBG => SapSapOrderWrapper => SapBapiSalesorderCreatefro Destination Fields SalesOrgnizait on DistributionCh annel Division Notes Value= 0001 Value= 01 Value= 01

40 mdat2 5. Assign SapSapOrderWrapperBG => SapSapOrderWrapper => SapBapiSalesorderCreatefro mdat2 6. Move OrderProcessGBOBG => OrderProcessGBO 7. Custom OrderProcessGBOBG => OrderProcessGBO Custom Java code (7): OrderName ProductName CustomerNumbe r SapSapOrderWrapperBG => SapSapOrderWrapper => SapBapiSalesorderCreatefro mdat2 SapSapOrderWrapperBG => SapSapOrderWrapper => SapBapiSalesorderCreatefro mdat2 SalesDocumen ttype CustomerPurc haseordernum ber Value= TA The Java code is listed below. commonj.sdo.dataobject OrderProcessGBOBG_OrderProcessGBO = (commonj.sdo.dataobject)orderprocessgbobg_orderprocessgbo; java.lang.string OrderProcessGBOBG_OrderProcessGBO_ProductName = (java.lang.string)orderprocessgbobg_orderprocessgbo_productname; java.lang.string OrderProcessGBOBG_OrderProcessGBO_CustomerNumber = (java.lang.string)orderprocessgbobg_orderprocessgbo_customernumber; commonj.sdo.dataobject SapSapOrderWrapperBG_SapSapOrderWrapper_SapBapiSalesorderCreatefromda t2 = (commonj.sdo.dataobject)sapsaporderwrapperbg_sapsaporderwrapper_sapbapi SalesorderCreatefromdat2; commonj.sdo.dataobject itemsin = SapSapOrderWrapperBG_SapSapOrderWrapper_SapBapiSalesorderCreatefromda t2.createdataobject("saporderitemsin"); commonj.sdo.dataobject partners = SapSapOrderWrapperBG_SapSapOrderWrapper_SapBapiSalesorderCreatefromda t2.createdataobject("saporderpartners"); itemsin.setstring("salesdocumentitem","000010"); itemsin.setstring("materialnumber", OrderProcessGBOBG_OrderProcessGBO_ ProductName); itemsin.setstring("plant","0001"); itemsin.setstring("targetquantityinsalesunits","1"); partners.setstring("partnerfunction","ag"); partners.setstring("customernumber1", OrderProcessGBOBG_OrderProcessGB O_CustomerNumber); The finished data map should look like Figure 32:

41 Figure 32. Data map for Generic BO to SAP Order BO Data Transformation Type Create the data map for Generic BO to SAP Order BO: Folder: DataMap Data Map Name: GBOToSapMaterial Source BO: OrderProcessGBOBG Destination BO: SapSapMaterialWrapperBG Source BO (Child BO) Source Fields Destination BO (Child BO) 1. Move OrderProcessGBOBG => OrderProcessGBO ProduceName SapSapMaterialWrapperBG => SapSapMaterialWrapper => SapBapiMaterialAvailabilit y 2. Assign SapSapMaterialWrapperBG => SapSapMaterialWrapper => SapBapiMaterialAvailabilit y 3. Assign SapSapMaterialWrapperBG => SapSapMaterialWrapper => SapBapiMaterialAvailabilit y 4. Assign SapSapMaterialWrapperBG => SapSapMaterialWrapper => SapBapiMaterialAvailabilit y Destination Fields MaterialNumb er Plant UnitOfMeasur efordisplay ItemNumber Notes Value= 0001 Value= EA Value=

42 Step 3. Create the interface maps As mentioned earlier, we need give interface maps for this scenario. In this section, we ll first describe the common steps for creating an interface map, then we ll describe the detailed steps to create the interface maps for this scenario. To create an interface map, complete the following steps: 1. In the Business Integration perspective of the OrderProcess module, right-click the Mapping => Interface Maps, and select New => Interface Map. 2. In the Interface Map dialog, specify the folder and interface map names, and click Next. 3. In the following Interface Map dialog, select the source interface and destination interface, and click Finish. 4. In the Interface Map editor, wire the source operation to the destination operation, as shown in Figure 33. Figure 33. Create the interface map 5. Left-click on the line to open the parameter mapping editor. Then, wire the input of the source operation to the input of the destination operation, and wire the output of the destination operation to the output of the source operation, as shown in Figure 34. Figure 34. Map the operations between interfaces 6. If the parameters of the source and destination interface has the same data type, the Move type can be used to transfer data. However, if they have the different data type, you ll need to use another method, such as a data map, to map between two parameters. In this case, you can use existing data maps. Click one item in the line of Parameter mappings, and switch to the Properties dialog at the bottom, then select map as the parameter mapping type.

43 Figure 35. Map the parameters between operations 7. Switch Details and select the proper data map, as shown in Figure 36: Figure 36. Parameter mapping configuration 8. After completing the interface map design, save all files. Using the common steps described above, create the interface maps needed for our scenario. All the interface maps will be in the folder InterfaceMap. Create the SiebelInboundOrderToOrderProcessBPEL interface map Figure 37. The SiebelInboundOrderToOrderProcessBPEL interface map Input Data Map: SiebelOrderToGBO

44 Create the OrderProcessBPELToSiebelOutbountOrder interface map Figure 38. The OrderProcessBPELToSiebelOutbountOrder interface map Output Data Map: SiebelOrderToGBO_2 Create the OrderProcessBPELToSiebelOutboundAccount interface map Figure 39. The OrderProcessBPELToSiebelOutboundAccount interface map Input Data Map: GBOToSiebelAccount Output Data Map: SiebelAccountToGBO

45 Create the OrderProcessBPELToSapOutbountMaterial interface map Figure 40. The OrderProcessBPELToSapOutbountMaterial interface map Input Data Map: GBOToSapMaterial Output Data Map: SapMaterialToGBO Create the OrderProcessBPELToSapOutboundOrder interface map Figure 41. The OrderProcessBPELToSapOutboundOrder interface map Input Data Map: GBOToSapOrder Output Data Map: SapOrderToGBO Task 6: Implement the BPEL process for the business logic The BPEL component holds the business logic for our scenario. It will get the input from the Siebel inbound module, and call other modules based on the requirements. The basic logic is: If the Siebel Inbound Event type is not Create, throw an exception. If the Siebel order status is not New or Open, throw an exception. Check Siebel Order Account status. If it is not Active, update the Siebel Order with the Account check error message. Check SAP Material storage. If it does not meet the order s requirement, update the Siebel Order with the storage check error message. If the above checks are passed, create a SAP Order record based on the Siebel Order record, and update the Siebel Order with a successful processed message.

46 In this section, we ll describe how to design and implement the BPEL component. Step 1. Create the BPEL component 1. In the Business Integration perspective for the OrderProcess module, right-click Business Logic => Processes, and select New=>Business Process. 2. In the New Business Process dialog, specify OrderBPEL as the folder name and OrderProcessBPEL as the BPEL name, then click Finish. 3. In the Business Integration perspective for the OrderProcess module, doubleclick Assembly Diagram to display the BPEL component, as shown in Figure 42: Figure 42. BPEL component in the assembly diagram 4. Add the OrderProcessBPEL interface to the BPEL component by clicking the +I icon. 5. Add the references: CheckSiebelAccount, CheckSapMaterial, UpdateSiebelOrder, CreateSapOrder to the BPEL component by clicking the +-> icon. 6. Save all files and build all the projects. Step 2. Design and implement the BPEL logic 1. Double-click the BPEL component to open the BPEL editor. 2. On the lefthand side of the BPEL editor, you ll see icons for some components that you can add to the BPEL process, as shown in Figure 43. For our scenario, we need the following components: Invoke Invoke other modules Assign Assign value to variable Snippet Some Java code Choice Switch cases based on the conditions Throw Throw an exception

47 Figure 43. BPEL editor components 3. Check the Siebel Inbound event. The Choice component is used to do this check. Create a Choice called Check Verb And Status. Then Add two Cases and one Otherwise to the choice, shown in Figure 44: Figure 44. BPEL design - Check verb and status The first case is check successful. Edit this case in the Properties dialog pane at the bottom. For this case, draw Java code as shown in Figure 45. Figure 45. Implementation of verb and status check

48 For the second case, draw Java code as shown in Figure 45, and add a follow-up Throw component as shown in Figure 46. Figure 46. Case condition of checking the verb Figure 47. Throw component for the incorrect verb For the Otherwise branch of the checking, create a Throw component. Figure 48. Throw component for incorrect order status 4. After passing the verb and order status checks, the next step is to check the Siebel Account status.

49 Figure 49. BPEL design Check Siebel account As shown in Figure 49, the Invoke component CheckSiebelAccount is called to retrieve the account record from Siebel server. It uses the CheckSiebelAccount interface and the Retrieve operation. The parameters are shown in Figure 50: Figure 50. Configuration for checking Siebel account Create a snippet called PrintedOutAccountStatus to print the status out for monitoring, as shown in Figure 51. Figure 51. Snippet for printing out message

50 Now create another Choice component named CheckAccountStatus to check whether the Siebel account is active or not. There is one case and one otherwise under the choice. The case holds the successful conditions as shown in Figure 52. Figure 52. Case conditions for checking Siebel account If the account status is not active, the BPEL process will go to otherwise. The otherwise branch first uses the snippet to set the change summary for the Siebel order, then updates the Siebel order with an error message. The snippet named SetChangeSummary contains the following code, which tells the Siebel order initiator that the order is not accepted because of the failure of the account check: {// print to log System.out.println(siebelOrderBG); } {// print to log System.out.println(orderGBOBG); } try { commonj.sdo.dataobject order = com.ibm.j2ca.base.adapterboutil.createbusinessobject( " esu41bcorderentryu45ordersbg", "BOOrderEntryU40SalesU41BCOrderEntryU45OrdersBG"); siebelorderbg = order.getcontainer(); commonj.sdo.dataobject gbo = ordergbobg.getdataobject("orderprocessgbo"); commonj.sdo.changesummary cs = com.ibm.j2ca.base.adapterboutil.getchangesummary(siebelorderbg); cs.beginlogging(); order.setstring("id", gbo.getstring("siebelorderid")); order.setstring("status", "Credit Failure"); order.setstring("description", "Credit Failure - Account is not active"); order.setstring("comments", "Credit Failure - Account is not active"); cs.endlogging(); } catch(java.lang.exception e) { e.printstacktrace(); }

51 Next an Invoke component named SiebelOrderUpdate_FailedNotify is called to update the Siebel Order record. It will use the UpdateSiebelOrder interface and the ApplyChanges operation. Set the parameters as shown in Figure 53. Figure 53. Configuration for updating the Siebel order 5. Check SAP Material Storage. If the above two checks are passed, there is a final check in the SAP server to make sure that there is enough material storage in the SAP server. Figure 54. BPEL design - Check SAP material As shown in Figure 54, the Invoke component CheckSapMaterial is called to retrieve the SAP Material information. It uses the CheckSapMaterial interface and the Retrieve operation. The necessary parameters are shown in Figure 55:

52 Figure 55. Configuration for checking SAP material Then, the PrintOutMaterialStatus snippet is used to print the SAP Material information, as shown in Figure 56. Figure 56. Snippet for printing out message The CheckMaterialStatus choice is used to check whether the SAP material storage fits the requirement. The case is the successful condition with the following Java code: String value1 = materialret.getdataobject("orderprocessgbo").getstring("sapmaterialquan tity"); String value2 = materialret.getdataobject("orderprocessgbo").getstring("quantity"); Double v1 = new Double(value1); Double v2 = new Double(value2); return (v1.doublevalue() >= v2.doublevalue()); In case the SAP Material check fails, the BPEL process goes to otherwise. The otherwise branch first uses the snippet to set the change summary for the Siebel order, then updates the Siebel order with the error message. The SetChangeSummary snippet contains the following code, which tells the Siebel order initiator that the order is not accepted because of the failure of SAP material storage check:

53 {// print to log System.out.println(siebelOrderBG); } {// print to log System.out.println(orderGBOBG); } try { commonj.sdo.dataobject order = com.ibm.j2ca.base.adapterboutil.createbusinessobject( " esu41bcorderentryu45ordersbg", "BOOrderEntryU40SalesU41BCOrderEntryU45OrdersBG"); siebelorderbg = order.getcontainer(); commonj.sdo.dataobject gbo = ordergbobg.getdataobject("orderprocessgbo"); commonj.sdo.changesummary cs = com.ibm.j2ca.base.adapterboutil.getchangesummary(siebelorderbg); cs.beginlogging(); order.setstring("id", gbo.getstring("siebelorderid")); order.setstring("status", "Pending"); order.setstring("description", "Not enough materials in SAP"); order.setstring("comments", "Not enough materials in SAP"); cs.endlogging(); } catch(java.lang.exception e) { e.printstacktrace(); } Next the Invoke component SiebelOrderUpdate_FailedNotify is called to update the Siebel Order record. It uses the UpdateSiebelOrder interface and the ApplyChanges operation. Set the parameters as shown in Figure 57: Figure 57. Configuration for updating Siebel order 6. If all the checks are passed, create a SAP Order based on the Siebel Order.

54 Figure 58. BPEL design - Create SAP order record As shown in Figure 58, the Invoke component SapOrderCreate is called to create a SAP Order record. It uses the CreateSapOrder interface and the Create operation. Necessary parameters are shown in Figure 59: Figure 59. Configuration for creating SAP order record Then, the PrintOutSapDocumentNumber snippet is called to print out the SAP Order number, as shown in Figure 60. Figure 60. Snippet for printing out message

55 Next, an Assign component named AssignDocumentNumber is used to copy the value from sapcreateorderret => OrderProcessGBO => SAPOrderNumber to ordergbobg => OrderPrcessGBO => SAPOrderNumber, as shown in Figure 61. Figure 61. Assign SAP order number to business object Next, the SetChangeSummary snippet, shown below, is called to set the change summary for the Siebel Order, which tells the Siebel Order initiator that the order is accepted, including a successfully created SAP Order number. {// print to log System.out.println(siebelOrderBG); } {// print to log System.out.println(orderGBOBG); } try { commonj.sdo.dataobject order = com.ibm.j2ca.base.adapterboutil.createbusinessobject( " esu41bcorderentryu45ordersbg", "BOOrderEntryU40SalesU41BCOrderEntryU45OrdersBG"); siebelorderbg = order.getcontainer(); commonj.sdo.dataobject gbo = ordergbobg.getdataobject("orderprocessgbo"); commonj.sdo.changesummary cs = com.ibm.j2ca.base.adapterboutil.getchangesummary(siebelorderbg); cs.beginlogging(); order.setstring("id", gbo.getstring("siebelorderid")); order.setstring("status", "Approved"); order.setstring("description", "SapDocumentNumber="+gbo.getString("SAPOrderNumber")); order.setstring("comments", "SapDocumentNumber="+gbo.getString("SAPOrderNumber")); cs.endlogging();

56 } catch(java.lang.exception e) { e.printstacktrace(); } Finally, the Invoke component SiebelOrderUpdate is called to update the Siebel Order record to tell the initiator that the order is approved. It uses the UpdateSiebelOrder interface and the ApplyChanges operation. The parameters are set as shown in Figure 62: Figure 62. Configuration for updating Siebel order 7. The finished BPEL process looks like Figure 63: Figure 63. BPEL design - whole picture

57 8. Assemble all the components. After you ve finished designing and implementing all the modules, you need to wire them together in the Assembly Diagram. The BPEL module is the center of the whole process. It gets input from the Siebel Inbound module and calls the Siebel and SAP outbound modules to interact with SAP and Siebel. The interfaces and references may not match between callers and callees. In the above steps, we already created some interface maps to provide maps between interfaces and references, so we ll use those here. Figure 64. OrderProcess module assembly As you can see in Figure 64, the OrderProcessBPEL module wires to the OrderProcessBPELToSiebelOutboundAccount interface map, which then wires to SiebelOutboundInterface_Account. The rest are similar. 9. Compile the modules. You ve now finished with development. Save all the files and compile all the modules. 10. If necessary, you can export the project to an ear file by selecting Menu => File => Export. You can then later deploy this ear file to Process Server to run. Deploy and run the sales order process scenario In this section, we ll deploy and run our sales order process scenario.

58 Task 1: Deploy the sales order process scenario 1. Start Process Server. In the Business Integration perspective, select the Servers pane at the bottom. Right-click the WebSphere Process Server instance and select Start. When the status of the server shows Started, it means the server is successfully started. Figure 65. Start WebSphere Process Server 2. Deploy the project to the server. Right-click the server instance, and select Add and remove projects. 3. In the Add and Remove Projects dialog, select Add All and click Finish. 4. In the console window, look to see if the following message displays, which means the project is successfully deployed: Figure 66. Console output when starting Process Server 5. If needed, you can also deploy the scenario ear file by using the Application Server administrative console. Task 2: Run the sales order process scenario with invalid input data 1. Make sure that Process Server is started and the project is successfully deployed to the server. 2. In the Account dialog of the Siebel Sales Web client, create a new Account record, as shown in Figure 67. The Account Name is and Status is Inactive. Note that the Account Name needs to be equal to the Customer Number in the SAP system.

59 Figure 67. Create account record in Siebel 3. In the site map of the Siebel Sales Web client, navigate to Sales Orders and create a new Sales Order record. For the Account field, select the Account record , which we just created. Then, add the product as the line item of the order, and set the Status of the order to New, as shown in Figure 68. Figure 68. Create sales order record in Siebel 4. In the site map of the Siebel Sales Web client, select Menu => Save Record to save the record. 5. The Siebel server automatically creates an event in the Siebel inbound event table IBM2 using the trigger, as shown in Figure 69. Note that if the OrderProcessApp module is deployed and running, the Siebel inbound event will be quickly consumed by the module, and may not appear in the event table.

60 Figure 69. Order event created in event table 6. Start the OrderProcessApp module in Process Server. The Siebel inbound event is consumed and the BPEL process runs based on the designed features. 7. Navigate to the Sales Orders dialog. The Siebel Order record that we just created is updated with the credit check error message. The Status field displays Credit Failure and Description field shows Credit Failure Account is not Active, as shown in Figure 70. Figure 70. Siebel order updated with failure reason Task 3: Run the sales order process scenario with correct input data. 1. Follow the same steps as in Task 2, except that, when creating the Account record, set the Status to Active. 2. After the OrderProcesApp modul processes, navigate to the Sales Orders dialog. The Siebel Order record has a status of Approved and the SAP Order Document Number is shown in the Description field, as shown in Figure 71. Figure 71. Siebel order updated with successful message 3. Log in to the SAP client. Enter the shortcut /nva03 to check SAP orders, as shown in Figure 72.

61 Figure 72. Open SAP order navigator 4. Enter the SAP Order Document Number, which appears in the Siebel Sales Order Description field, and click Search. In Figure 73, you can see that the new SAP Order record wass successfully created based on the Siebel Order. Figure 73. SAP order is created Task 4: Uninstall the modules After testing the scenario, you can uninstall the modules for the scenario by completing the following steps: 1. In the Servers dialog of Integration Developer, right-click the server instance and select Add and remove projects. 2. In the Add and Remove Projects dialog, select Remove All and click Finish.

62 Conclusion In this article, you learned how to develop a sales order validation process scenario between SAP and a Siebel system using WebSphere Process Server and WebSphere Adapters. You learned how to set up the EIS environment, design the scenario, create the necessary modules, define the interfaces, generate the data types, and implement the business logic. You also tested the end-to-end scenario. Working through this example, you ve learned how you can get started designing and implementing business integration applications. Resources WebSphere Adapter Information Center WebSphere Process Server Information Center sps.doc/welcome_wps.html Redbook: WebSphere Adapter Development WebSphere Business Integration Zone WebSphere Business Process Management Zone About the author Qian Li Jin works as a software engineer at IBM China Development Lab. His job focuses on WebSphere Adapters and he is very interested in Business Integration technologies. You can reach Qian Li at jinql@cn.ibm.com.