5 Integration With Mediator Service Components in the Oracle SOA Suite

This chapter describes integration with Mediator service components in the Oracle SOA Suite. It contains the following topics:

The scenarios shown in this chapter require the following prerequisites.

Prerequisites

The following are installation and configuration requirements:

The examples in this chapter present the configuration steps necessary for demonstrating service and event integration with Siebel. Prior to using this material, you must be familiar with the following:

Overview of Mediator Integration

Mediator provides a comprehensive application integration framework. Oracle Application Adapter for Siebel used with Mediator enables you to seamlessly integrate enterprise software, eliminating the need to write custom code. Functional modeling, as opposed to custom coding solutions, allows for software reuse and reduces the complexity and management challenges that arise over the software lifecycle. This integration model consists of two components--high-level integration logic and low-level platform services.

Adapter integration with Oracle WebLogic Server, Mediator is a two-step process:

  1. Design Time: Oracle Application Adapter for Siebel is configured in Application Explorer for services and events, as described in Chapter 2, "Configuring Oracle Application Server Adapter for Siebel". Integration logic is modeled in iStudio. Metadata are stored in repositories.

  2. Runtime: The underlying platform treats this metadata as run-time instructions to enable the communication between participating applications.

Configuring a New Application Server Connection

For more information on how to configure a new Application Server connection in Oracle JDeveloper, see Configuring a New Application Server Connection.

Configuring a Mediator Outbound Process

The following example describes how to configure a Mediator outbound process to your Siebel system, using a Mediator project in Oracle JDeveloper.

Prerequisites

Before you design a Mediator outbound process, you must generate the respective WSDL file using Application Explorer. For more information, see "Siebel Service Integration".

Creating a New SOA Application for the Outbound Mediator Process

Perform the following steps to create a new SOA application for the outbound Mediator 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 5-1.

    Figure 5-1 New Option in the Application Menu

    Application menu
    Description of "Figure 5-1 New Option in the Application Menu"

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

    Figure 5-2 Create SOA Application Wizard - Name Your Application Page

    Create SOA Application wizard
    Description of "Figure 5-2 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_Outbound_Mediator) and click Next.

    The Name your project page is displayed, as shown in Figure 5-3.

    Figure 5-3 Name Your Project Page

    Name your project pane
    Description of "Figure 5-3 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 5-4.

    Figure 5-4 Configure SOA Settings Page

    Configure SOA settings pane
    Description of "Figure 5-4 Configure SOA Settings Page"

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

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

    Figure 5-5 A New SOA Application (Siebel_Outbound_Mediator) and Associated Project (QueryWithView_Invoke) Added to the Application Navigator Tab

    Application Navigator tab
    Description of "Figure 5-5 A New SOA Application (Siebel_Outbound_Mediator) and Associated Project (QueryWithView_Invoke) Added to the Application Navigator Tab"

Defining a Mediator Outbound Process

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

  1. Configuring a Third Party Adapter Service Component

  2. Configuring an Outbound Mediator Process Component

  3. Configuring the Routing Rules

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 pane, as shown in Figure 5-6.

    Figure 5-6 Third Party Adapter Component Being Dragged to the External References Pane

    External References pane
    Description of "Figure 5-6 Third Party Adapter Component Being Dragged to the External References Pane"

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

    Figure 5-7 Create Third Party Adapter Service Dialog

    Create Third Party Adapter Service dialog box
    Description of "Figure 5-7 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 5-8.

    Figure 5-8 SOA Resource Browser Dialog

    SOA Resource Browser dialog box
    Description of "Figure 5-8 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 5-9.

    Figure 5-9 Localize Files Dialog

    Localize Files dialog box
    Description of "Figure 5-9 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 5-10.

    Figure 5-10 Create Third Party Adapter Service Dialog

    Create Third Party Adapter Service dialog box
    Description of "Figure 5-10 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 5-11.

    Figure 5-11 SOA Resource Browser Dialog

    SOA Resource Browser dialog box
    Description of "Figure 5-11 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.

    The following message is displayed, as shown in Figure 5-12.

    Figure 5-12 Copy File Message

    Copy File message
    Description of "Figure 5-12 Copy File 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 5-13.

    Figure 5-13 Create Third Party Adapter Service Dialog

    Create Third Party Adapter Service dialog box
    Description of "Figure 5-13 Create Third Party Adapter Service Dialog"

  12. Click OK.

    The third party adapter service component (GetDetail) is created and displayed in the External References pane, as shown in Figure 5-14.

    Figure 5-14 Third Party Adapter Service Component (GetDetail) in the External References Pane

    External References pane
    Description of "Figure 5-14 Third Party Adapter Service Component (GetDetail) in the External References Pane"

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

Configuring an Outbound Mediator Process Component

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

  1. Drag and drop the Mediator component from the Component Palette tab (Service Components section) to the Components pane, as shown in Figure 5-15.

    Figure 5-15 Mediator Component Being Dragged to the Components Pane

    Components pane
    Description of "Figure 5-15 Mediator Component Being Dragged to the Components Pane"

    The Create Mediator dialog is displayed, as shown in Figure 5-16.

    Figure 5-16 Create Mediator Dialog

    Create Mediator dialog box
    Description of "Figure 5-16 Create Mediator Dialog"

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

  3. From the Template list, select Synchronous Interface.

  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 5-17.

    Figure 5-17 Type Chooser Dialog

    Type Chooser dialog box
    Description of "Figure 5-17 Type Chooser Dialog"

  5. Expand Project WSDL Files, queryWithView_invoke.wsdl, Inline Schemas, schema, and select Siebel.

  6. Click OK.

    You are returned to the Create Mediator dialog, as shown in Figure 5-18.

    Figure 5-18 Create Mediator Dialog

    Create Mediator dialog box
    Description of "Figure 5-18 Create Mediator 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 5-19.

    Figure 5-19 Type Chooser Dialog

    Type Chooser dialog box
    Description of "Figure 5-19 Type Chooser Dialog"

  8. Expand Project WSDL Files, queryWithView_invoke.wsdl, Inline Schemas, schema, and select SiebelResponse.

  9. Click OK.

    You are returned to the Create Mediator dialog, as shown in .Figure 5-20

    Figure 5-20 Create Mediator Dialog

    Create Mediator dialog box
    Description of "Figure 5-20 Create Mediator Dialog"

  10. Click OK.

  11. As shown in Figure 5-21, create a connection between the outbound Mediator process component (QueryWithView_ Mediator) and the third party adapter service component (QueryWithView).

    Figure 5-21 Connection Between the Outbound Mediator Process Component (QueryWithView_ Mediator) and the Third Party Adapter Service Component (QueryWithView)

    Oracle JDeveloper workspace area
    Description of "Figure 5-21 Connection Between the Outbound Mediator Process Component (QueryWithView_ Mediator) and the Third Party Adapter Service Component (QueryWithView)"

    You are now ready to configure the routing rules.

Configuring the Routing Rules

Perform the following steps to configure routing rules for the Mediator outbound process component:

  1. Double-click the outbound Mediator process component (QueryWithView_ Mediator) in the Components pane, as shown in Figure 5-22.

    Figure 5-22 The Outbound Mediator Process Component (QueryWithView_ Mediator) in the Components Pane

    Oracle JDeveloper workspace area
    Description of "Figure 5-22 The Outbound Mediator Process Component (QueryWithView_ Mediator) in the Components Pane"

    The Routing Rules dialog is displayed, as shown in Figure 5-23.

    Figure 5-23 Routing Rules Dialog

    Routing Rules dialog box
    Description of "Figure 5-23 Routing Rules Dialog"

  2. In the <<Filter Expression>> area, click the Select an existing mapper file or create a new one icon to the right of the Transform Using field.

    The Request Transformation Map dialog is displayed, as shown in Figure 5-24.

    Figure 5-24 Request Transformation Map Dialog

    Request Transformation Map dialog box
    Description of "Figure 5-24 Request Transformation Map Dialog"

  3. Select the Create New Mapper File option and click OK.

    The Siebel_To_Siebel.xsl tab is displayed, as shown in Figure 5-25.

    Figure 5-25 Siebel_To_Siebel.xsl Tab

    Siebel_To_Siebel.xsl tab
    Description of "Figure 5-25 Siebel_To_Siebel.xsl Tab"

  4. Map the iWayRequest:Siebel source element to the iWayRequest:Siebel target element.

    The Auto Map Preferences dialog is displayed, as shown in Figure 5-26.

    Figure 5-26 Auto Map Preferences Dialog

    Auto Map Preferences dialog box
    Description of "Figure 5-26 Auto Map Preferences Dialog"

  5. Retain the default values and click OK.

  6. As shown in Figure 5-27, click the QueryWithView_Mediator.mplan tab.

    Figure 5-27 QueryWithView_Mediator.mplan Tab

    QueryWithView_Mediator.mplan tab
    Description of "Figure 5-27 QueryWithView_Mediator.mplan Tab"

    You are returned to the Routing Rules dialog, as shown in Figure 5-28.

    Figure 5-28 Routing Rules Dialog

    Routing Rules dialog box
    Description of "Figure 5-28 Routing Rules Dialog"

  7. In the Synchronous Reply area, click the Select an existing mapper file or create a new one icon to the right of the Transform Using field.

    The Reply Transformation Map dialog is displayed, as shown in Figure 5-29.

    Figure 5-29 Reply Transformation Map Dialog

    Reply Transformation Map dialog box
    Description of "Figure 5-29 Reply Transformation Map Dialog"

  8. Select the Create New Mapper File option and click OK.

    The SiebelResponse_To_SiebelResponse.xsl tab is displayed, as shown in Figure 5-30.

    Figure 5-30 SiebelResponse_To_SiebelResponse.xsl Tab

    SiebelResponse_To_SiebelResponse.xsl tab
    Description of "Figure 5-30 SiebelResponse_To_SiebelResponse.xsl Tab"

  9. Map the iWayResponse:SiebelResponse source element to the iWayResponse:SiebelResponse target element.

    The Auto Map Preferences dialog is displayed, as shown in Figure 5-31.

    Figure 5-31 Auto Map Preferences Dialog

    Auto Map Preferences dialog box
    Description of "Figure 5-31 Auto Map Preferences Dialog"

  10. Retain the default values and click OK.

    As shown in Figure 5-32, the mapping is completed.

    Figure 5-32 Completed Mapping

    completed mapping
    Description of "Figure 5-32 Completed Mapping"

  11. Click the Save All icon in the menu bar to save the new outbound Mediator process component that was configured, as shown in Figure 5-33.

    Figure 5-33 Save All Icon

    Save All icon
    Description of "Figure 5-33 Save All Icon"

    You are now ready to deploy the Mediator outbound process.

Deploying the Mediator Outbound Process

Perform the following steps to deploy the Mediator outbound process.

  1. As shown in Figure 5-34, right-click the project name in the left pane (for example, QueryWithView_Invoke), select Deploy, and then click QueryWithView_Invoke.

    Figure 5-34 Deploy Option

    Deploy context menu
    Description of "Figure 5-34 Deploy Option"

    The Deployment Action dialog is displayed, as shown in Figure 5-35.

    Figure 5-35 Deployment Action Dialog

    Deployment Action dialog box
    Description of "Figure 5-35 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 5-36.

    Figure 5-36 Deploy Configuration Dialog

    Deploy Configuration dialog box
    Description of "Figure 5-36 Deploy Configuration Dialog"

  4. Leave the default values selected and click Next.

    The Select Server dialog is displayed, as shown in Figure 5-37.

    Figure 5-37 Select Server Dialog

    Select Server dialog box
    Description of "Figure 5-37 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 5-38.

    Figure 5-38 SOA Servers Dialog

    SOA Servers dialog
    Description of "Figure 5-38 SOA Servers Dialog"

  6. Select a target SOA server and click Next.

    The Summary dialog is displayed, as shown in Figure 5-39.

    Figure 5-39 Summary Dialog

    Summary dialog box
    Description of "Figure 5-39 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 5-40.

    Figure 5-40 Deployment Successful Message

    SOA Log tab
    Description of "Figure 5-40 Deployment Successful 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 5-41.

    Figure 5-41 Oracle Enterprise Manager Console

    Oracle Enterprise Manager console
    Description of "Figure 5-41 Oracle Enterprise Manager Console"

  3. As shown in Figure 5-42, select an available project (for example, Siebel_Outbound_queryWithView_Mediator).

    Figure 5-42 An Available Project (for example, Siebel_Outbound_queryWithView_Mediator) Being Selected

    Test button
    Description of "Figure 5-42 An Available Project (for example, Siebel_Outbound_queryWithView_Mediator) Being Selected "

  4. Click Test in the right pane.

    The Test Web Service page is displayed, as shown in Figure 5-43.

    Figure 5-43 Test Web Service Page

    Test Web Service pane
    Description of "Figure 5-43 Test Web Service Page"

  5. Click the Request tab.

  6. Scroll down to the Input Arguments section, as shown in Figure 5-44.

    Figure 5-44 Input Arguments Section

    Input Arguments section
    Description of "Figure 5-44 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 5-45.

    Figure 5-45 Output Response Received in the Response Tab of the Oracle Enterprise Manager Console

    Response tab
    Description of "Figure 5-45 Output Response Received in the Response Tab of the Oracle Enterprise Manager Console"

Configuring a Mediator Inbound Process

The following example describes how to configure a Mediator inbound process to your Siebel system, using a Mediator project in Oracle JDeveloper.

Prerequisites

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

Creating a New SOA Application for the Inbound Mediator Process

Perform the following steps to create a new SOA application for the inbound Mediator 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 5-46.

    Figure 5-46 New Option

    Application menu
    Description of "Figure 5-46 New Option"

    The Create SOA Application wizard is displayed, as shown in Figure 5-47.

    Figure 5-47 Create SOA Application Wizard

    Create SOA Application wizard
    Description of "Figure 5-47 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_Inbound_Mediator) and click Next.

    The Name your project page is displayed, as shown in Figure 5-48.

    Figure 5-48 Name Your Project Page

    Name your project pane
    Description of "Figure 5-48 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 5-49.

    Figure 5-49 Configure SOA Settings Page

    Configure SOA settings pane
    Description of "Figure 5-49 Configure SOA Settings Page"

  6. From the Composite Template list, select Empty Composite and click Finish to show the Application Navigator, as shown in Figure 5-50.

    Figure 5-50 SOA Application (Siebel_Inbound_Mediator) and Associated Project (SampleAccount_Receive) Added to the Application Navigator Tab

    Application Navigator tab
    Description of "Figure 5-50 SOA Application (Siebel_Inbound_Mediator) and Associated Project (SampleAccount_Receive) Added to the Application Navigator Tab"

    The new SOA application (Siebel_Inbound_Mediator) and associated project (SampleAccount_Receive) are added to the Application Navigator tab in the left pane.

Defining a Mediator Inbound Process

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

  1. Configuring a Third Party Adapter Service Component

  2. Configuring an Inbound Mediator Process Component With a File Adapter

  3. Configuring the Routing Rules

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 Exposed Services pane, as shown in Figure 5-51.

    Figure 5-51 Third Party Adapter Component Being Dragged to the Exposed Services Pane

    Exposed Services pane
    Description of "Figure 5-51 Third Party Adapter Component Being Dragged to the Exposed Services Pane"

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

    Figure 5-52 Create Third Party Adapter Service

    Create Third Party Adapter Service dialog box
    Description of "Figure 5-52 Create Third Party Adapter Service"

  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 Figure 5-53.

    Figure 5-53 SOA Resource Browser Dialog

    SOA Resource Browser dialog box
    Description of "Figure 5-53 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 Figure 5-54.

    Figure 5-54 Localize Files Dialog

    Localize Files dialog box
    Description of "Figure 5-54 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.

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

    Figure 5-55 Create Third Party Adapter Service Dialog

    Create Third Party Adapter Service dialog box
    Description of "Figure 5-55 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 5-56.

    Figure 5-56 SOA Resource Browser Dialog

    SOA Resource Browser dialog box
    Description of "Figure 5-56 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 5-57, the following message is displayed.

    Figure 5-57 Copy File Confirmation Message Dialog

    Copy File message
    Description of "Figure 5-57 Copy File Confirmation Message Dialog"

  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 5-58.

    Figure 5-58 Create Third Party Adapter Service Dialog

    Create Third Party Adapter Service dialog box
    Description of "Figure 5-58 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 Figure 5-59.

    Figure 5-59 Third Party Adapter Service Component (SampleAccount) Created in the Exposed Services Pane.

    Exposed Services pane
    Description of "Figure 5-59 Third Party Adapter Service Component (SampleAccount) Created in the Exposed Services Pane."

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

Configuring an Inbound Mediator Process Component With a File Adapter

Perform the following steps to configure an inbound Mediator process component with a File adapter.

  1. Drag and drop the Mediator component from the Component Palette tab (Service Components section) to the Components pane, as shown in Figure 5-60.

    Figure 5-60 Mediator Component Being Dragged to the Components Pane

    Components pane
    Description of "Figure 5-60 Mediator Component Being Dragged to the Components Pane"

    The Create Mediator dialog is displayed, as shown in Figure 5-61.

    Figure 5-61 Create Mediator Dialog

    Create Mediator dialog box
    Description of "Figure 5-61 Create Mediator Dialog"

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

  3. From the Template list, select Define Interface Later.

  4. Click the OK.

    The new Mediator process component is added to the Components pane, as shown in Figure 5-62.

    Figure 5-62 Mediator Process Component Being Added to the Components Pane

    Components pane
    Description of "Figure 5-62 Mediator Process Component Being Added to the Components Pane"

  5. Drag and drop the File Adapter component from the Service Adapters pane to the External References pane.

    The Adapter Configuration Wizard - Welcome page is displayed, showing the Welcome page, as shown in Figure 5-63.

    Figure 5-63 The Adapter Configuration Wizard - Welcome Page

    Adapter Configuration Wizard
    Description of "Figure 5-63 The Adapter Configuration Wizard - Welcome Page"

  6. Click Next.

    The Service Name page is displayed, as shown in Figure 5-64.

    Figure 5-64 Service Name Page

    Service Name pane
    Description of "Figure 5-64 Service Name Page"

  7. Type a name for the new File adapter in the Service Name field and click Next.

    The Adapter Interface page is displayed, as shown in Figure 5-65.

    Figure 5-65 Adapter Interface Page

    Adapter Interface pane
    Description of "Figure 5-65 Adapter Interface Page"

  8. Ensure that the Define from operation and schema (specified later) option is selected.

  9. Click Next.

    The Operation page is displayed, as shown in Figure 5-66.

    Figure 5-66 Operation Page

    Operation pane
    Description of "Figure 5-66 Operation Page"

  10. Select Write File from the list of Operation Type options and specify an Operation Name (for example, Write).

  11. Click Next.

    The File Configuration page is displayed, as shown in Figure 5-67.

    Figure 5-67 File Configuration Page

    File Configuration pane
    Description of "Figure 5-67 File Configuration Page"

  12. Specify a location on your file system for the output file.

  13. In the File Naming Convention field, specify a name for the output file.

  14. Click Next.

    The Messages page is displayed, as shown in Figure 5-68.

    Figure 5-68 Messages Page

    Messages pane
    Description of "Figure 5-68 Messages Page"

  15. Click browse for schema file, which is located to the right of the URL field.

    The Type Chooser dialog is displayed, as shown in Figure 5-69.

    Figure 5-69 Type Chooser Dialog

    Type Chooser dialog box
    Description of "Figure 5-69 Type Chooser Dialog"

  16. Expand Project WSDL Files, Sample_Account_receive.wsdl, Inline Schemas, and schema.

  17. Select the available schema (for example, SiebelMessage)

  18. Click OK.

    You are returned to the Messages page, as shown in Figure 5-70.

    Figure 5-70 Messages Page

    Messages pane
    Description of "Figure 5-70 Messages Page"

  19. Click Next.

    The Finish page is displayed, as shown in Figure 5-71.

    Figure 5-71 Finish Page

    Finish pane
    Description of "Figure 5-71 Finish Page"

  20. Click Finish.

  21. Create a connection between the inbound Mediator process component and the third party adapter service component, as shown in Figure 5-72.

    Figure 5-72 Connection Between the Inbound Mediator Process Component and the Third Party Adapter Service Component

    Oracle JDeveloper workspace area
    Description of "Figure 5-72 Connection Between the Inbound Mediator Process Component and the Third Party Adapter Service Component"

  22. Create a connection between the inbound Mediator process component and the File adapter component, as shown in Figure 5-73.

    Figure 5-73 Connection Between the Inbound Mediator Process Component and the File Adapter Component

    Oracle JDeveloper workspace area
    Description of "Figure 5-73 Connection Between the Inbound Mediator Process Component and the File Adapter Component"

    You are now ready to configure the routing rules.

Configuring the Routing Rules

Perform the following steps to configure routing rules for the Mediator inbound process component:

  1. Double-click the inbound Mediator process component in the Components pane, as shown in Figure 5-74.

    Figure 5-74 Inbound Mediator Process Component in the Components Pane

    Inbound Mediator process component
    Description of "Figure 5-74 Inbound Mediator Process Component in the Components Pane"

    The Routing Rules dialog is displayed, as shown inFigure 5-75 .

    Figure 5-75 Routing Rules Dialog

    Routing Rules dialog box
    Description of "Figure 5-75 Routing Rules Dialog"

  2. In the <<Filter Expression>> area, click the Select an existing mapper file or create a new one icon to the right of the Transform Using field.

    The Request Transformation Map dialog is displayed, as shown in Figure 5-76.

    Figure 5-76 Request Transformation Map Dialog

    Request Transformation Map dialog box
    Description of "Figure 5-76 Request Transformation Map Dialog"

  3. Select the Create New Mapper File option and click OK.

    The SiebelMessage_To_SiebelMessage.xsl tab is displayed, as shown in Figure 5-77.

    Figure 5-77 SiebelMessage_To_SiebelMessage.xsl Tab

    SiebelMessage_To_SiebelMessage.xsl tab
    Description of "Figure 5-77 SiebelMessage_To_SiebelMessage.xsl Tab"

  4. Map the iWayEvent:SiebelMessage source element to the iWayEvent:SiebelMessage target element.

    The Auto Map Preferences dialog is displayed, as shown in Figure 5-78.

    Figure 5-78 Auto Map Preferences Dialog

    Auto Map Preferences dialog box
    Description of "Figure 5-78 Auto Map Preferences Dialog"

  5. Retain the default values and click OK.

    As shown in Figure 5-79, the mapping is now complete.

    Figure 5-79 Completed Mapping

    completed mapping
    Description of "Figure 5-79 Completed Mapping"

  6. As shown in Figure 5-80, click the Save All icon in the menu bar to save the new inbound Mediator process component that was configured.

    Figure 5-80 Save All Icon

    Save All icon
    Description of "Figure 5-80 Save All Icon"

    You are now ready to deploy the Mediator inbound process. You can follow the same procedure that is described in "Defining a BPEL Inbound Process".

    Once event messages are triggered through Siebel, output XML is received in the location that was specified for the File adapter component. For more information on triggering events in Siebel, see "Triggering an Event in Siebel".