4 Integration With BPEL Service Components in the Oracle SOA Suite

Oracle Application Adapter for Siebel integrates seamlessly with Business Process Execution Language (BPEL) Process Manager to facilitate Web service integration. Oracle BPEL Process Manager is based on the Service-Oriented Architecture (SOA). It consumes adapter services exposed as Web Service Definition Language (WSDL) documents.

This chapter contains the following topics:

• Overview

• Deployment of Adapter

• Configuring a New Application Server Connection

• Designing an Outbound BPEL Process for Service Integration

• Designing an Inbound BPEL Process for Event Integration

Overview

To integrate with Oracle BPEL Process Manager, Oracle Application Adapter for Siebel must be deployed in the same WLS container as Oracle BPEL Process Manager. The underlying adapter services must be exposed as WSDL files, which are generated during design time in Oracle Adapter Application Explorer (Application Explorer) for both request-response (outbound) and event notification (inbound) services of the adapter. For more information, see "Generating WSDL (J2CA Configurations Only)".

The generated WSDL files are used to design the appropriate BPEL processes for inbound or outbound adapter services. A completed BPEL process must be successfully compiled in Oracle JDeveloper and deployed to a BPEL server. Upon deployment to the BPEL server, every newly built process is automatically deployed to the Oracle Enterprise Manager console, where you run, monitor, administer BPEL processes, and listen to adapter events.

Deployment of Adapter

During installation, Oracle Application Adapter for Siebel is deployed as a J2CA 1.0 resource adapter within the WLS container. The adapter must be deployed in the same WLS container as Oracle BPEL Process Manager.

Configuring a New Application Server Connection

To configure a new Application Server connection in Oracle JDeveloper:

1. Open Oracle JDeveloper on your system.

2. From the menu bar, click View and select Application Server Navigator, as shown in Figure 4-1.

   Figure 4-1 Application Server Navigator Option

   
   Description of "Figure 4-1 Application Server Navigator Option"
   
   

   The Application Server tab is displayed, as shown in Figure 4-2.

   Figure 4-2 Application Server Tab

   
   Description of "Figure 4-2 Application Server Tab"
   
   

3. Right-click Application Servers, and then select New Application Server.

   The Create Application Server Connection Wizard - Usage page is displayed, as shown in Figure 4-3.

   Figure 4-3 Create Application Server Connection Wizard - Usage Page

   
   Description of "Figure 4-3 Create Application Server Connection Wizard - Usage Page"
   
   

4. Accept the default selection (Standalone Server) and click Next.

   The Name and Type page is displayed, as shown in Figure 4-4.

   Figure 4-4 Name and Type Page

   
   Description of "Figure 4-4 Name and Type Page"
   
   

5. Specify a new name for the Application Server connection and click Next.

   The Authentication page is displayed, as shown in Figure 4-5.

   Figure 4-5 Authentication Page

   
   Description of "Figure 4-5 Authentication Page"
   
   

6. Specify a valid user name (for example, weblogic) and a password (for example, welcome1) for your new connection.

7. Click Next.

   The Configuration page is displayed, as shown in Figure 4-6.

   Figure 4-6 Configuration Page

   
   Description of "Figure 4-6 Configuration Page"
   
   

8. Specify the Oracle WebLogic host name (for example, localhost), which is the machine IP where the process needs to deploy and Oracle WebLogic domain (for example, base_domain).

9. Click Next.

   The Test page is displayed, as shown in Figure 4-7.

   Figure 4-7 Test Page

   
   Description of "Figure 4-7 Test Page"
   
   

10. Click Test Connection.

11. Ensure that the test status is successful.

12. Click Next.

    The Finish page is displayed, as shown in Figure 4-8.

    Figure 4-8 Finish Page

    
    Description of "Figure 4-8 Finish Page"
    
    

13. Click Finish.

    As shown in Figure 4-9, the new Application Server connection is listed in the left pane (Application Server tab).

    Figure 4-9 The New Application Server Connection

    
    Description of "Figure 4-9 The New Application Server Connection"
    
    

Designing an Outbound BPEL Process for Service Integration

The following tools are required to complete your adapter design-time configuration:

• Oracle Adapter Application Explorer (Application Explorer)

• Oracle JDeveloper BPEL Designer (JDeveloper) or Eclipse

Note:

The examples in this chapter demonstrate the use of Oracle JDeveloper.

Samples have been provided for this usecase scenario in the etc/sample folder in Application Adapters installation.

Before you design a BPEL process, you must create a schema and generate the respective WSDL file using Application Explorer. For more information, see "Generating WSDL (J2CA Configurations Only)".

Generating WSDL for Request/Response Service

To generate WSDL in Application Explorer:

1. Start Application Explorer and connect to a defined Siebel target or create a new target.

   For more information, see Connecting to a Defined Target.

2. Expand the Siebel target to which you are connected.

3. As shown in Figure 4-10, expand Business Object, Account, and then Account.

   Figure 4-10 Create Outbound JCA Service (Request/Response) Option

   
   Description of "Figure 4-10 Create Outbound JCA Service (Request/Response) Option"
   
   

4. Right-click queryWithView, and then select Create Outbound JCA Service (Request/Response).

   The Export WSDL dialog is displayed, as shown in Figure 4-11.

   Figure 4-11 Export WSDL Dialog

   
   Description of "Figure 4-11 Export WSDL Dialog"
   
   

5. Specify an export location on your file system or accept the default path.

   The .wsdl file extension is added automatically. By default, the names of WSDL files generated for request-response services end with _invoke.

6. Click OK.

You can now create an empty composite for SOA, which is the first step that is required to define a BPEL outbound process in Oracle JDeveloper.

Creating a New SOA Application for the Outbound BPEL Process

Perform the following steps to create a new SOA application for the outbound BPEL process:

1. Open Oracle JDeveloper on your system.

2. Click Application in the menu bar and select New from the menu, as shown in Figure 4-12.

   Figure 4-12 New Option in Application Menu

   
   Description of "Figure 4-12 New Option in Application Menu"
   
   

   The Create SOA Application wizard is displayed, as shown in Figure 4-13.

   Figure 4-13 Create SOA Application Wizard

   
   Description of "Figure 4-13 Create SOA Application Wizard"
   
   

3. From the Application Template list, click SOA Application.

4. Enter a name for the new SOA application (for example, Siebel_Outbound_BPEL) and click Next.

   The Name your project page is displayed, as shown in Figure 4-14.

   Figure 4-14 Name Your Project Page

   
   Description of "Figure 4-14 Name Your Project Page"
   
   

5. Enter a project name (for example, QueryWithView_Invoke) and click Next.

   The Configure SOA settings page is displayed, as shown in Figure 4-15.

   Figure 4-15 Configure SOA Settings Page

   
   Description of "Figure 4-15 Configure SOA Settings Page"
   
   

6. From the Composite Template list, select Empty Composite and click Finish.

   As shown in Figure 4-16, the new SOA application (Siebel_Outbound_BPEL) and associated project (QueryWithView_Invoke) are added to the Application Navigator tab in the left pane.

   Figure 4-16 SOA application (Siebel_Outbound_BPEL) In Application Navigator Tab

   
   Description of "Figure 4-16 SOA application (Siebel_Outbound_BPEL) In Application Navigator Tab"
   
   

Defining a BPEL Outbound Process

This section describes how to define a BPEL outbound process, which consists of the following stages:

1. Configuring a Third Party Adapter Service Component

2. Configuring an Outbound BPEL Process Component

Configuring a Third Party Adapter Service Component

Perform the following steps to create a third party adapter service component:

1. Drag and drop the Third Party Adapter component from the Component Palette tab (Service Adapters section) to the External References design pane, as shown in Figure 4-17.

   Figure 4-17 Third Party Adapter Component

   
   Description of "Figure 4-17 Third Party Adapter Component"
   
   

   The Create Third Party Adapter Service dialog is displayed, as shown in Figure 4-18.

   Figure 4-18 Create Third Party Adapter Service Dialog

   
   Description of "Figure 4-18 Create Third Party Adapter Service Dialog"
   
   

2. Enter a name for the new third party adapter service.

3. Ensure that Reference is selected from the Type list (default).

4. Click the Find existing WSDLs icon, which is located to the right of the WSDL URL field.

   The SOA Resource Browser dialog is displayed, as shown in Figure 4-19.

   Figure 4-19 SOA Resource Browser Dialog

   
   Description of "Figure 4-19 SOA Resource Browser Dialog"
   
   

5. Browse and select an outbound WSDL file from the following directory:

   <ADAPTER_HOME>\soa\thirdparty\ApplicationAdapters\wsdls
   

6. Click OK.

   The Localize Files dialog is displayed, as shown in Figure 4-20.

   Figure 4-20 Localize Files Dialog

   
   Description of "Figure 4-20 Localize Files Dialog"
   
   

7. Click OK.

   The outbound WSDL file and associated request and response XML schema files (.xsd) are imported to the project folder that has been created.

   You are returned to the Create Third Party Adapter Service dialog, as shown in Figure 4-21.

   Figure 4-21 Create Third Party Adapter Service Dialog

   
   Description of "Figure 4-21 Create Third Party Adapter Service Dialog"
   
   

8. Click the Find JCA Files icon, which is located to the right of the JCA File field.

   The SOA Resource Browser dialog is displayed, as shown in Figure 4-22.

   Figure 4-22 SOA Resource Browser Dialog

   
   Description of "Figure 4-22 SOA Resource Browser Dialog"
   
   

9. Browse and select the JCA properties file from the following directory:

   <ADAPTER_HOME>\soa\thirdparty\ApplicationAdapters\wsdls
   

10. Click OK.

    As shown in Figure 4-23, the following message is displayed.

    Figure 4-23 Copy File Confirmation Message

    
    Description of "Figure 4-23 Copy File Confirmation Message"
    
    

11. Click Yes.

    A copy of the JCA properties file is made in the project folder.

    You are returned to the Create Third Party Adapter Service dialog, as shown in Figure 4-24.

    Figure 4-24 Create Third Party Adapter Service Dialog

    
    Description of "Figure 4-24 Create Third Party Adapter Service Dialog"
    
    

12. Click OK.

    The third party adapter service component (QueryWithView) is created and displayed in the External References pane, as shown in Figure 4-25.

    Figure 4-25 Third Party Adapter Service Component (QueryWithView) Created in the External References Pane

    
    Description of "Figure 4-25 Third Party Adapter Service Component (QueryWithView) Created in the External References Pane"
    
    

    You are now ready to configure an outbound BPEL process component.

Configuring an Outbound BPEL Process Component

Perform the following steps to configure an outbound BPEL process component:

1. Drag and drop the BPEL Process component from the Component Palette tab (Service Components section) to the Components design pane, as shown in Figure 4-26.

   Figure 4-26 BPEL Process Component Dragged to the Components Design Pane

   
   Description of "Figure 4-26 BPEL Process Component Dragged to the Components Design Pane"
   
   

   The Create BPEL Process dialog is displayed, as shown in Figure 4-27.

   Figure 4-27 Create BPEL Process Dialog

   
   Description of "Figure 4-27 Create BPEL Process Dialog"
   
   

2. In the Name field, enter a name to identify the new outbound BPEL process component (for example, querywithview_out).

   By default, the BPEL specification is set to BPEL 1.1 Specification. The BPEL process also supports BPEL 2.0 Specification.

3. From the Template list, select Synchronous BPEL Process.

4. Click the Browse Input Elements icon, which is located to the right of the Input field to select the associated XML request schema file.

   The Type Chooser dialog is displayed, as shown in Figure 4-28.

   Figure 4-28 Type Chooser Dialog

   
   Description of "Figure 4-28 Type Chooser Dialog"
   
   

5. Expand Project Schema Files, queryWithView_invoke_request.xsd, and then select Siebel.

6. Click OK.

   You are returned to the Create BPEL Process dialog, as shown in Figure 4-29.

   Figure 4-29 Create BPEL Process Dialog

   
   Description of "Figure 4-29 Create BPEL Process Dialog"
   
   

7. Click the Browse Output Elements icon, which is located to the right of the Output field to select the associated XML response schema file.

   The Type Chooser dialog is displayed, as shown in Figure 4-30.

   Figure 4-30 Type Chooser Dialog

   
   Description of "Figure 4-30 Type Chooser Dialog"
   
   

8. Expand Project Schema Files, queryWithView_invoke_response.xsd, and then select SiebelResponse.

9. Click OK.

   You are returned to the Create BPEL Process dialog, as shown in Figure 4-31.

   Figure 4-31 Create BPEL Process Dialog

   
   Description of "Figure 4-31 Create BPEL Process Dialog"
   
   

10. Click OK.

11. As shown in Figure 4-32, create a connection between the outbound BPEL process component (querywithview_out) and the third party adapter service component (QueryWithView).

    Figure 4-32 Connection Between the Outbound BPEL Process Component (querywithview_out) and the Third Party Adapter Service Component (QueryWithView)

    
    Description of "Figure 4-32 Connection Between the Outbound BPEL Process Component (querywithview_out) and the Third Party Adapter Service Component (QueryWithView)"
    
    

12. Double-click the outbound BPEL process component (querywithview_out) in the Components pane.

    The following is displayed, as shown in Figure 4-33.

    Figure 4-33 Outbound BPEL Process Component (querywithview_out) in the Components Pane

    
    Description of "Figure 4-33 Outbound BPEL Process Component (querywithview_out) in the Components Pane"
    
    

13. Drag and drop the Invoke activity component to the Components pane and place it between the receiveInput activity component and the replyOutput activity component, as shown in Figure 4-34.

    Figure 4-34 Invoke Activity Component in the Components Pane

    
    Description of "Figure 4-34 Invoke Activity Component in the Components Pane"
    
    

14. Create a connection between the new Invoke activity component (Invoke1) and the third party adapter service component (QueryWithView), as shown in Figure 4-35.

    Figure 4-35 Connection Being Created Between the New Invoke Activity Component (Invoke1) and the Third Party Adapter Service Component (QueryWithView)

    
    Description of "Figure 4-35 Connection Being Created Between the New Invoke Activity Component (Invoke1) and the Third Party Adapter Service Component (QueryWithView)"
    
    

    The Edit Invoke dialog is displayed, as shown in Figure 4-36.

    Figure 4-36 Edit Invoke Dialog

    
    Description of "Figure 4-36 Edit Invoke Dialog"
    
    

15. Click the Automatically Create Input Variable icon, which is located to the right of the Input field to configure a new input variable.

    The Create Variable dialog is displayed, as shown in Figure 4-37.

    Figure 4-37 Create Variable Dialog

    
    Description of "Figure 4-37 Create Variable Dialog"
    
    

16. Accept the default values that are provided for the new input variable and click OK.

    You are returned to the Edit Invoke dialog, as shown in Figure 4-38.

    Figure 4-38 Edit Invoke Dialog

    
    Description of "Figure 4-38 Edit Invoke Dialog"
    
    

17. Click the Automatically Create Output Variable icon, which is located to the right of the Output field to configure a new output variable.

    The Create Variable dialog is displayed, as shown in Figure 4-39.

    Figure 4-39 Create Variable Dialog

    
    Description of "Figure 4-39 Create Variable Dialog"
    
    

18. Accept the default values that are provided for the new output variable and click OK.

    You are returned to the Edit Invoke dialog, as shown in Figure 4-40.

    Figure 4-40 Edit Invoke Dialog

    
    Description of "Figure 4-40 Edit Invoke Dialog"
    
    

19. Click Apply and then OK.

    As shown in Figure 4-41, the Invoke activity component (Invoke1) is updated accordingly.

    Figure 4-41 Updated Invoke Activity Component (Invoke1)

    
    Description of "Figure 4-41 Updated Invoke Activity Component (Invoke1)"
    
    

20. Drag and drop the Assign activity component to the Components pane and place it between the Receive activity component (receiveInput) and the Invoke activity component (Invoke1), as shown in Figure 4-42.

    Figure 4-42 Assign Activity Component Dragged to the Components Pane

    
    Description of "Figure 4-42 Assign Activity Component Dragged to the Components Pane"
    
    

21. Double-click the new Assign activity component (Assign1).

    Figure 4-43 Assign Dialog

    
    Description of "Figure 4-43 Assign Dialog"
    
    

22. Click the Plus sign icon and select Copy Operation from the list of available operations.

    The Edit Assign dialog is displayed, as shown in Figure 4-44.

    Figure 4-44 Edit Assign Dialog

    
    Description of "Figure 4-44 Edit Assign Dialog"
    
    

23. In the left pane, under Variables, expand InputVariable, and then select payload.

24. In the right pane, under Variables, expand Invoke1_queryWithView_InputVariable, and then select input_queryWithView.

25. Drag and map the payload variable to the input_queryWithView variable as shown in Figure 4-45.

    The mapped variables are populated in the highlighted area.

    Figure 4-45 Edit Assign Dialog

    
    Description of "Figure 4-45 Edit Assign Dialog"
    
    

26. Click Apply and then OK.

27. As shown in Figure 4-46, drag and drop the Assign activity component to the Components pane and place it between the Invoke activity (Invoke1) and the Reply activity (replyOutput).

    Figure 4-46 Assign Activity Component Dragged to the Components Pane and Placed Between the Invoke Activity (Invoke1) and the Reply Activity (replyOutput)

    
    Description of "Figure 4-46 Assign Activity Component Dragged to the Components Pane and Placed Between the Invoke Activity (Invoke1) and the Reply Activity (replyOutput)"
    
    

28. Double-click the new Assign activity component (Assign2), as shown in Figure 4-47

    Figure 4-47 Assign2 Dialog

    
    Description of "Figure 4-47 Assign2 Dialog"
    
    

29. Click the Plus sign icon and select Copy Operation from the list of available operations.

    The Edit Assign dialog is displayed, as shown in Figure 4-48.

    Figure 4-48 Edit Assign Dialog

    
    Description of "Figure 4-48 Edit Assign Dialog"
    
    

30. In the left pane, under Variables, expand Invoke1_queryWithView_OutputVariable, and then select output_queryWithView.

31. In the right pane, under Variables, expand outputVariable, and then select payload.

32. Drag and map the output_queryWithView variable to the payload variable.

    The mapped variables are populated in the highlighted area, as shown in Figure 4-49.

    Figure 4-49 Edit Assign Dialog

    
    Description of "Figure 4-49 Edit Assign Dialog"
    
    

33. Click Apply and then OK.

    The completed activity flow is now displayed, as shown in Figure 4-50.

    Figure 4-50 Completed Activity Flow

    
    Description of "Figure 4-50 Completed Activity Flow"
    
    

34. As shown in Figure 4-50, double-click composite.xml in the left pane.

35. As shown in Figure 4-51, click the Save All icon in the menu bar to save the new outbound BPEL process component that was configured.

    Figure 4-51 Save All Icon

    
    Description of "Figure 4-51 Save All Icon"
    
    

    You are now ready to deploy the BPEL outbound process.

Deploying the BPEL Outbound Process

Perform the following steps to deploy the BPEL outbound process.

1. Right-click the project name in the left pane (for example, QueryWithView_Invoke), select Deploy, and then click QueryWithView_Invoke, as shown in Figure 4-52.

   Figure 4-52 Deploy Option

   
   Description of "Figure 4-52 Deploy Option"
   
   

   The Deployment Action dialog is displayed, as shown in Figure 4-53.

   Figure 4-53 Deployment Action Dialog

   
   Description of "Figure 4-53 Deployment Action Dialog"
   
   

2. Ensure that Deploy to Application Server is selected.

3. Click Next.

   The Deploy Configuration dialog is displayed, as shown in Figure 4-54.

   Figure 4-54 Deploy Configuration Dialog

   
   Description of "Figure 4-54 Deploy Configuration Dialog"
   
   

4. Leave the default values selected and click Next.

   The Select Server dialog is displayed, as shown in Figure 4-55.

   Figure 4-55 Select Server Dialog

   
   Description of "Figure 4-55 Select Server Dialog"
   
   

5. Select an available application server that was configured and click Next.

   The SOA Servers dialog is displayed, as shown in Figure 4-56.

   Figure 4-56 SOA Servers Dialog

   
   Description of "Figure 4-56 SOA Servers Dialog"
   
   

6. Select a target SOA server and click Next.

   The Summary dialog is displayed, as shown in Figure 4-57.

   Figure 4-57 Summary Dialog

   
   Description of "Figure 4-57 Summary Dialog"
   
   

7. Review and verify all the available deployment information for your project and click Finish.

   The process is deployed successfully, as shown in Figure 4-58.

   Figure 4-58 Successful Deployment Message

   
   Description of "Figure 4-58 Successful Deployment Message"
   
   

Invoking the Input XML Document in the Oracle Enterprise Manager Console

Perform the following steps to invoke the input XML document in the Oracle Enterprise Manager console.

1. Log in to the Oracle Enterprise Manager console by using the following URL:

   http://localhost:7001/em
   

2. Expand your domain in the left pane followed by the SOA folder, as shown in Figure 4-59.

   Figure 4-59 Oracle Enterprise Manager Console

   
   Description of "Figure 4-59 Oracle Enterprise Manager Console"
   
   

3. As shown in Figure 4-60, select an available project (for example, Siebel_Outbound_queryWithView_BPEL).

   Figure 4-60 The Siebel_Outbound_queryWithView_BPEL Project Being Selected

   
   Description of "Figure 4-60 The Siebel_Outbound_queryWithView_BPEL Project Being Selected "
   
   

4. Click Test in the right pane.

   The Test Web Service page is displayed, as shown in Figure 4-61.

   Figure 4-61 Test Web Service Page

   
   Description of "Figure 4-61 Test Web Service Page"
   
   

5. Click the Request tab.

6. As shown in Figure 4-62, scroll down to the Input Arguments section.

   Figure 4-62 Input Arguments Section

   
   Description of "Figure 4-62 Input Arguments Section"
   
   

7. Select XML View from the list in the upper-left corner.

8. Provide an appropriate input XML document in the Input Arguments area.

9. Click Test Web Service.

   The output response is received in the Response tab of the Oracle Enterprise Manager console, as shown in Figure 4-63.

   Figure 4-63 Output Response That is Received in the Response Tab of the Oracle Enterprise Manager Console

   
   Description of "Figure 4-63 Output Response That is Received in the Response Tab of the Oracle Enterprise Manager Console"
   
   

Testing Outbound BPEL and Mediator Processes

When testing an outbound BPEL process from the Oracle Enterprise Manager console or an outbound Mediator process from the Enterprise Manager console, do not use the XML envelopes that are generated by these consoles. Instead, remove them and use the XML payloads that are generated from the schemas, which conform to the WSDLs for namespace qualifications.

The Mediator data flows can be tested using the Enterprise Manager console. When creating a Mediator data flow and interactions, the Web services are created and registered with the Oracle Application Server. For more information on creating a Mediator outbound process, see Chapter 5, "Integration With Mediator Service Components in the Oracle SOA Suite".

Designing an Inbound BPEL Process for Event Integration

This topic illustrates Siebel event integration. It describes design-time and run-time configuration. The following tools are required to complete your adapter design-time configuration:

• Oracle Adapter Application Explorer (Application Explorer)

• Oracle JDeveloper BPEL Designer (JDeveloper) or Eclipse

Note:

The examples in this chapter demonstrate the use of Oracle JDeveloper.

Samples have been provided for this usecase scenario in the etc/sample folder in the Application Adapters installation.

Before you design a BPEL process, you must generate the respective WSDL file using Application Explorer. For more information, see "Generating WSDL for Event Integration".

Generating WSDL for Event Integration

You must create a separate channel for every inbound J2CA service and select that channel when you generate WSDL for inbound interaction using Application Explorer.

Note:

If two or more events share the same channel, then event messages may not be delivered to the right BPEL process.

Creating a Channel

You must create a separate channel for every inbound J2CA service and select that channel when you generate WSDL for inbound interaction using Application Explorer.

Note:

If two or more events share the same channel, then event messages may not be delivered to the right BPEL process.

To create a channel:

1. In the left pane, click Events.

2. Expand the Siebel node.

   The ports and channels nodes appear in the left pane, as shown in Figure 4-64.

   Figure 4-64 Ports and Channels Nodes Under Siebel Node

   
   Description of "Figure 4-64 Ports and Channels Nodes Under Siebel Node"
   
   

3. Right-click Channels and select Add Channel.

   The Add Channel dialog is displayed, as shown in Figure 4-65.

   Figure 4-65 Add Channel Dialog

   
   Description of "Figure 4-65 Add Channel Dialog"
   
   

   Perform the following steps:

   1. Enter a name for the channel, for example, SiebelEvent.

   2. Enter a brief description.

   3. From the Protocol list, select HTTP Listener, MQ Series Listener, or File Listener.

   For demonstration purposes, this procedure uses the HTTP Listener as an example.

4. Click Next.

   The Basic dialog is displayed, as shown in Figure 4-66.

   Figure 4-66 Basic Dialog

   
   Description of "Figure 4-66 Basic Dialog"
   
   

5. Enter the system information as specified in the following table:

   Parameter	Description
   Listener port	Port on which to listen for Siebel event data.
   Https	For a secure HTTP connection, select the Https check box. This option is currently not supported.
   Synchronization Type	Select REQUEST_RESPONSE from the list, which is the recommended option.
   Encoding Type	Choose an encoding type to be used from the list. By default, ASCII is selected.

   
   

6. Click the PreParser tab, as shown in Figure 4-67.

   Figure 4-67 PreParser Tab

   
   Description of "Figure 4-67 PreParser Tab"
   
   

7. Specify the location of the schema file that was generated for the Integration Object node using the Export Schema(s) option in Application Explorer.

   Note:

   During run time, the Oracle Application Adapter for Siebel adds the namespace to the Siebel published document using the schema that is specified in the PreParser tab. If the Schema location field in the PreParser tab is empty, then BPEL and Mediator processes do not work properly as the Siebel published documents do not contain any namespaces.

8. Click OK.

   As shown in Figure 4-68, the channel appears under the channels node in the left pane. An X over the icon indicates that the channel is currently disconnected.

   Figure 4-68 New Channel Node

   
   Description of "Figure 4-68 New Channel Node"
   
   

   Note:

   Do not start the channel, as it is managed by BPEL PM Server. If you start the channel for testing and debugging purposes, then stop it before run-time.

   You must now create an Integration Object node.

Creating an Integration Object Node

1. Start Application Explorer.

2. Expand the Adapters node, as shown in Figure 4-69.

   Figure 4-69 Disconnected Siebel Target Node, Siebel, Under the Siebel Node

   
   Description of "Figure 4-69 Disconnected Siebel Target Node, Siebel, Under the Siebel Node"
   
   

   Perform the following steps:

   1. Expand the Siebel node.

      The defined Siebel targets are displayed under the adapter node.

   2. Click the target name, for example, siebel, under the Siebel node.

   The Connection dialog displays the values you entered.

3. Verify your connection parameters.

4. Right-click the target name and select Connect.

   The x icon disappears, indicating that the node is connected, as shown in Figure 4-70.

   Figure 4-70 Connected Nodes

   
   Description of "Figure 4-70 Connected Nodes"
   
   

5. Expand the Integration Object node and select Sample Account.

6. Right-click the Sample Account node and select Add IO Node.

   The Add IO Node dialog is displayed, as shown in Figure 4-71.

   Figure 4-71 Add IO Node Dialog

   
   Description of "Figure 4-71 Add IO Node Dialog"
   
   

7. Enter a node name (for example, Sample_Account) in the Node name field and a path to the Sample Account XSD file in the Schema location field.

   Please note:

   • For Siebel 7.5 or later: Generate XSD schemas directly from Siebel tools. You use the XSD schemas when you create Web services in Application Explorer. After you generate an XSD schema through Siebel tools, use it to create an IO node and a Web service.

   • For Siebel 7.0: You cannot generate XSD schemas directly from Siebel tools; only XDR schemas can be created. Before you create a Web service, you must first generate an XSD schema from the XDR schema using Application Explorer.

8. If the XSD schema has already been generated, then select XSD Schema. If you are using Siebel-generated XDR schemas, then do not select the XSD schema option.

9. Select a protocol (HTTP, FILE, or MQ Series) from the Protocol list.

10. Click Continue.

    The new Integration Object node is added, as shown inFigure 4-72.

    Figure 4-72 Integration Object Node

    
    Description of "Figure 4-72 Integration Object Node"
    
    

Note:

You must restart the Oracle WebLogic Server after the Integration Object node and channel are created.

Generating WSDL for Event Notification

After you create a channel and an associated Integration Object node, you must generate WSDL for the event using Application Explorer.

You must be connected to a Siebel target under the Adapters node in Application Explorer. For detailed information on how to define and connect to a target, see "Establishing a Connection (Target) for Siebel".

After you connect to a Siebel target, generate WSDL for the event as follows:

1. Right-click the Integration Object node (for example, Sample_Account), and then select Create Inbound JCA Service (Event), as shown in Figure 4-73.

   Figure 4-73 Create Inbound JCA Service (Event) Option Selected in Application Explorer

   
   Description of "Figure 4-73 Create Inbound JCA Service (Event) Option Selected in Application Explorer"
   
   

   The Export WSDL dialog is displayed, as shown in Figure 4-74.

   Figure 4-74 Export WSDL Dialog

   
   Description of "Figure 4-74 Export WSDL Dialog"
   
   

   Note:

   The schema validation options (Root, Namespace, Schema) are not applicable for the Oracle Application Adapter for Siebel.

   Perform the following steps:

   1. In the Name field, specify a name for the WSDL file.

      The .wsdl file extension is added automatically. By default, the names of WSDL files generated for events end with _receive.

   2. From the Channel list, select the channel you created for this inbound service (for example, SiebelEvent).

      Important: You must create a separate channel for every inbound service. Verify that the channel is stopped before run-time.

2. Click OK.

Creating a New SOA Application for the Inbound BPEL Process

Perform the following steps to create a new SOA application for the inbound BPEL process:

1. Open Oracle JDeveloper on your system.

2. Click Application in the menu bar and select New from the menu, as shown in Figure 4-75.

   Figure 4-75 New Option Being Selected in the Application Menu

   
   Description of "Figure 4-75 New Option Being Selected in the Application Menu"
   
   

   The Create SOA Application wizard - Name your application page is displayed, as shown in Figure 4-76.

   Figure 4-76 Create SOA Application Wizard - Name Your application Page

   
   Description of "Figure 4-76 Create SOA Application Wizard - Name Your application Page"
   
   

3. From the Application Template list, click SOA Application.

4. Enter a name for the new SOA application (for example, Siebel_Inbound_BPEL) and click Next.

   The Name your project page is displayed, as shown in Figure 4-77.

   Figure 4-77 Name Your Project Page

   
   Description of "Figure 4-77 Name Your Project Page"
   
   

5. Enter a project name (for example, SampleAccount_Receive) and click Next.

   The Configure SOA settings page is displayed, as shown in Figure 4-78.

   Figure 4-78 Configure SOA Settings Page

   
   Description of "Figure 4-78 Configure SOA Settings Page"
   
   

6. From the Composite Template list, select Empty Composite and click Finish.

   As shown in Figure 4-79, the new SOA application (Siebel_Inbound_BPEL) and associated project (SampleAccount_Receive) are added to the Application Navigator tab in the left pane.

   Figure 4-79 New SOA Application (Siebel_Inbound_BPEL) and Associated Project (SampleAccount_Receive)

   
   Description of "Figure 4-79 New SOA Application (Siebel_Inbound_BPEL) and Associated Project (SampleAccount_Receive)"
   
   

Defining a BPEL Inbound Process

This section describes how to define a BPEL inbound process, which consists of the following stages:

1. Configuring a Third Party Adapter Service Component

2. Configuring an Inbound BPEL Process Component

Creating a Third Party Adapter Service Component

Perform the following steps to create a third party adapter service component:

1. Drag and drop the Third Party Adapter component from the Component Palette tab (Service Adapters section) to the Exposed Services pane, as shown in Figure 4-80.

   Figure 4-80 Third Party Adapter Component

   
   Description of "Figure 4-80 Third Party Adapter Component"
   
   

   The Create Third Party Adapter Service dialog is displayed, as shown in Example 4-0.

   Figure 4-81 Create Third Party Adapter Service Dialog

   
   Description of "Figure 4-81 Create Third Party Adapter Service Dialog"
   
   

2. Enter a name for the third party adapter service.

3. Ensure that Service is selected from the Type list (default).

4. Click the Find existing WSDLs icon, which is located to the right of the WSDL URL field.

   The SOA Resource Browser dialog is displayed, as shown in Example 4-0.

   Figure 4-82 SOA Resource Browser Dialog

   
   Description of "Figure 4-82 SOA Resource Browser Dialog"
   
   

5. Browse and select an inbound WSDL file from the following directory:

   <ADAPTER_HOME>\soa\thirdparty\ApplicationAdapters\wsdls
   

6. Click OK.

   The Localize Files dialog is displayed, as shown in Example 4-0.

   Figure 4-83 Localize Files Dialog

   
   Description of "Figure 4-83 Localize Files Dialog"
   
   

7. Click OK.

   The inbound WSDL file and associated receive/request XML schema file (.xsd) are imported to the project folder that has been created.

   As shown in Example 4-0, you are returned to the Create Third Party Adapter Service dialog.

   Figure 4-84 Create Third Party Adapter Service Dialog

   
   Description of "Figure 4-84 Create Third Party Adapter Service Dialog"
   
   

8. Click the Find JCA Files icon, which is located to the right of the JCA File field.

   The SOA Resource Browser dialog is displayed, as shown in Example 4-0.

   Figure 4-85 SOA Resource Browser Dialog

   
   Description of "Figure 4-85 SOA Resource Browser Dialog"
   
   

9. Browse and select the JCA properties file from the following directory:

   <ADAPTER_HOME>\soa\thirdparty\ApplicationAdapters\wsdls
   

10. Click OK.

    As shown in Example 4-0, the following message is displayed.

    Figure 4-86 Copy File Confirmation Message

    
    Description of "Figure 4-86 Copy File Confirmation Message"
    
    

11. Click Yes.

    A copy of the JCA properties file is made in the project folder.

    You are returned to the Create Third Party Adapter Service dialog, as shown in Example 4-0.

    Figure 4-87 Create Third Party Adapter Service Dialog

    
    Description of "Figure 4-87 Create Third Party Adapter Service Dialog"
    
    

12. Click OK.

    The third party adapter service component (SampleAccount) is created and displayed in the Exposed Services pane, as shown in Example 4-0.

    Figure 4-88 Third Party Adapter Service Component (SampleAccount) Created in the Exposed Services Pane

    
    Description of "Figure 4-88 Third Party Adapter Service Component (SampleAccount) Created in the Exposed Services Pane"
    
    

    You are now ready to configure an inbound BPEL process component.

Creating an Inbound BPEL Process Component

Perform the following steps to create an inbound BPEL process component:

1. Drag and drop the BPEL Process component from the Component Palette tab (Service Components section) to the Components pane, as shown inExample 4-0.

   Figure 4-89 BPEL Process Component in the Components Pane

   
   Description of "Figure 4-89 BPEL Process Component in the Components Pane"
   
   

   The Create BPEL Process dialog is displayed, as shown in Example 4-0.

   Figure 4-90 Create BPEL Process Dialog

   
   Description of "Figure 4-90 Create BPEL Process Dialog"
   
   

2. In the Name field, enter a name to identify the new inbound BPEL process component (for example, SampleAccount_Inbound).

   By default, the BPEL specification is set to BPEL 1.1 Specification. The BPEL Process also supports BPEL 2.0 Specification.

3. From the Template list, select Base on a WSDL.

4. Uncheck the Expose as a SOAP service check box.

5. Click the Find existing WSDLs icon, which is located to the right of the WSDL URL field.

   The SOA Resource Browser dialog is displayed, as shown in Example 4-0.

   Figure 4-91 SOA Resource Browser Dialog

   
   Description of "Figure 4-91 SOA Resource Browser Dialog"
   
   

6. Browse and select an inbound WSDL file from the wsdls folder (for example, Sample_Account_receive.wsdl).

7. Click OK.

   The Localize Files dialog is displayed, as shown in Example 4-0.

   Figure 4-92 Localize Files Dialog

   
   Description of "Figure 4-92 Localize Files Dialog"
   
   

8. Click OK.

   Uncheck the box for Rename duplicate files field under Copy Options area.

   You are returned to the Create BPEL Process dialog, as shown in Example 4-0.

   Figure 4-93 Create BPEL Process Dialog

   
   

9. Click OK to create the connection, as shown in Example 4-0.

   Figure 4-94 Connection Created Between the Third Party Adapter Service Component (SampleAccount) and the Inbound BPEL Process Component (SampleAccount_Inbound)

   
   Description of "Figure 4-94 Connection Created Between the Third Party Adapter Service Component (SampleAccount) and the Inbound BPEL Process Component (SampleAccount_Inbound)"
   
   

10. Create a connection between the third party adapter service component (SampleAccount) and the inbound BPEL process component (SampleAccount_Inbound).

11. Double-click composite.xml in the left pane, as shown in Example 4-0.

    Figure 4-95 The Composite.xml File Being Selected in the Left Pane

    
    Description of "Figure 4-95 The Composite.xml File Being Selected in the Left Pane"
    
    

12. Click the Save All icon in the menu bar to save the new inbound BPEL process component that was configured, as shown in Example 4-0.

    Figure 4-96 Save All Icon

    
    Description of "Figure 4-96 Save All Icon"
    
    

    You are now ready to deploy the BPEL inbound process.

Deploying the BPEL Inbound Process

Perform the following steps to deploy the BPEL inbound process.

1. Right-click the project name in the left pane (for example, SampleAccount_Receive), select Deploy and then click SampleAccount_Receive, as shown in Example 4-0.

   Figure 4-97 SampleAccount_Receive Option

   
   Description of "Figure 4-97 SampleAccount_Receive Option "
   
   

   The Deployment Action dialog is displayed, as shown in Example 4-0.

   Figure 4-98 Deployment Action Dialog

   
   Description of "Figure 4-98 Deployment Action Dialog"
   
   

2. Ensure that Deploy to Application Server is selected.

3. Click Next.

   The Deploy Configuration dialog is displayed, as shown in Example 4-0.

   Figure 4-99 Deploy Configuration Dialog

   
   Description of "Figure 4-99 Deploy Configuration Dialog"
   
   

4. Leave the default values selected and click Next.

   The Select Server dialog is displayed, as shown in Example 4-0.

   Figure 4-100 Select Server Dialog

   
   Description of "Figure 4-100 Select Server Dialog"
   
   

5. Select an available application server that was configured and click Next.

   The SOA Servers dialog is displayed, as shown in Example 4-0.

   Figure 4-101 SOA Servers Dialog

   
   Description of "Figure 4-101 SOA Servers Dialog"
   
   

6. Select a target SOA server and click Next.

   The Summary dialog is displayed, as shown in Example 4-0.

   Figure 4-102 Summary Dialog

   
   Description of "Figure 4-102 Summary Dialog"
   
   

7. Review and verify all the available deployment information for your project and click Finish.

   The process is deployed successfully, as shown in Example 4-0.

   Figure 4-103 Deployment Successful Message

   
   Description of "Figure 4-103 Deployment Successful Message"
   
   

   Once event messages are triggered through Siebel, successful instances are received in the Oracle Enterprise Manager console.

Triggering an Event in Siebel

The following topic describes how to trigger an event in Siebel and verify event integration using Oracle Application Adapter for Siebel.

Triggering a Siebel Event to Test Event Runtime Integration

To trigger an event in Siebel:

1. As shown in Example 4-0, start the Siebel Call Center by entering the following URL in a browser:

   http://host name/callcenter/start.swe
   

   Figure 4-104 Site Map Option Selected Under the View Menu in the Siebel Call Center

   
   Description of "Figure 4-104 Site Map Option Selected Under the View Menu in the Siebel Call Center"
   
   

2. Click View and select Site Map from the list.

   The Site Map view is displayed, as shown in Example 4-0.

   Figure 4-105 Site Map View

   
   Description of "Figure 4-105 Site Map View"
   
   

3. Click Siebel Workflow Administration.

   The Siebel Workflow Administration page is displayed, as shown in Example 4-0.

   Figure 4-106 Siebel Workflow Administration Page

   
   Description of "Figure 4-106 Siebel Workflow Administration Page"
   
   

4. Click Workflow Processes.

   The Workflow Processes page is displayed, as shown in Example 4-0.

   Figure 4-107 Workflow Processes Page

   
   Description of "Figure 4-107 Workflow Processes Page"
   
   

5. Click Query to search for the Workflow needed to trigger a Siebel event, as shown in Example 4-0.

   Figure 4-108 Search Button in Workflow Processes Page

   
   Description of "Figure 4-108 Search Button in Workflow Processes Page"
   
   

6. As shown in Example 4-0, enter a Siebel workflow name and click Search.

   Figure 4-109 Workflow Processes Page

   
   Description of "Figure 4-109 Workflow Processes Page"
   
   

7. As shown in Example 4-0, select the workflow.

   Figure 4-110 Process Designer Tab

   
   Description of "Figure 4-110 Process Designer Tab"
   
   

8. Click the Process Designer tab and double-click the Send Siebel Quote Data HTTP workflow element.

   The Input Arguments tab is displayed, as shown in Example 4-0.

   Figure 4-111 Input Arguments Tab

   
   Description of "Figure 4-111 Input Arguments Tab"
   
   

9. Enter the IP address and port for the HTTPRequestURLTemplate input argument.

10. Click Return To Designer, as shown in Example 4-0.

    Figure 4-112 Return To Designer Button in Business Service Tab

    
    Description of "Figure 4-112 Return To Designer Button in Business Service Tab"
    
    

11. Click the Process Simulator tab, as shown in Example 4-0.

    Figure 4-113 Process Simulator Tab

    
    Description of "Figure 4-113 Process Simulator Tab"
    
    

    The Simulator tab is displayed, as shown in Example 4-0.

    Figure 4-114 Simulator Tab

    
    Description of "Figure 4-114 Simulator Tab"
    
    

12. Click Start then Continue to complete the Siebel event triggering process.

Verifying the Results

To verify your results:

1. Log in to the Oracle Enterprise Manager console by using the following URL:

   http://localhost:7001/em
   

2. As shown in Example 4-0, expand your domain in the left pane followed by the SOA folder.

   Figure 4-115 Oracle Enterprise Manager Console

   
   Description of "Figure 4-115 Oracle Enterprise Manager Console"
   
   

3. As shown in Example 4-0, select an available project (for example, Siebel_Inbound_sampacc_ionode_BPEL).

   Figure 4-116 Instances Tab

   
   Description of "Figure 4-116 Instances Tab"
   
   

4. Click the Instances tab in the right pane.

   Recently received run-time events are displayed in the Instances tab, as shown in Example 4-0.

   Figure 4-117 Recently Received Run-time Events Displayed in the Instances Tab

   
   Description of "Figure 4-117 Recently Received Run-time Events Displayed in the Instances Tab"
   
   

5. Select a Siebel instance ID.

   The Flow Trace page is displayed, as shown in Example 4-0.

   Figure 4-118 Flow Trace Page

   
   Description of "Figure 4-118 Flow Trace Page"
   
   

6. Select a component instance to view its detailed audit trail.

   The Instance page for the selected component is displayed, as shown in Example 4-0.

   Figure 4-119 Instance Page for the Selected Component

   
   Description of "Figure 4-119 Instance Page for the Selected Component"
   
   

7. Click the Audit Trail tab to view the event message.

   The message received from the Siebel system is displayed in the Audit Trail tab.