4 Integration With BPEL Service Components in the Oracle SOA Suite

Oracle Application Adapter for PeopleSoft integrates seamlessly with Oracle 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 SOA Suite, Oracle Application Adapter for PeopleSoft 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 Application Adapter Application Explorer (Application Explorer) for both request-response (outbound) and event notification (inbound) services of the adapter. For more information, see Chapter 2, "Configuring Oracle Application Adapter for PeopleSoft".

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 JDeveloper and deployed to a SOA server. Upon deployment to the SOA server, every newly built process is automatically deployed to the Oracle Enterprise Manager Console, where you run, monitor, and administer BPEL processes, and listen to adapter events.

Deployment of Adapter

During installation, Oracle Application Adapter for PeopleSoft 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

   
   Description of "Figure 4-1 Application Server Navigator"
   
   

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

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

    Figure 4-9 New Application Server Connection

    
    Description of "Figure 4-9 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 JDeveloper.

A sample outbound BPEL process is provided in the etc/sample folder of the application adapter 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 for Request/Response Service".

Generating WSDL for Request/Response Service

To generate WSDL for outbound interaction in Application Explorer:

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

   For more information, see "Defining a Target to PeopleSoft".

2. Expand Component Interfaces and select LOCATION.

3. Right-click LOCATION, and then select Create Outbound JCA Service (Request/Response), as shown in Figure 4-10.

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

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

   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"
   
   

4. 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.

5. Click OK.

You can now create a new SOA application, which is the first step that is required to define a BPEL outbound process in 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

   
   Description of "Figure 4-12 New Option"
   
   

   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, PSoft_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, LOCATION_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.

   The new SOA application (PSoft_Outbound_BPEL) and associated project (LOCATION_Invoke) are added to the Application Navigator tab in the left pane, as shown in Figure 4-16.

   Figure 4-16 New SOA Application and Associated Project

   
   Description of "Figure 4-16 New SOA Application and Associated Project"
   
   

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 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 (for example, LOCATION_invoke.wsdl) 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 (for example, LOCATION_invoke.jca) from the following directory:

   <ADAPTER_HOME>\soa\thirdparty\ApplicationAdapters\wsdls
   

10. Click OK.

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

    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 (Location) is created and displayed in the External References pane, as shown in Figure 4-25.

    Figure 4-25 Third Party Adapter Service Component

    
    Description of "Figure 4-25 Third Party Adapter Service Component"
    
    

    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 pane, as shown in Figure 4-26.

   Figure 4-26 BPEL Process Component

   
   Description of "Figure 4-26 BPEL Process Component"
   
   

   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, location_out).

   By default, the BPEL specification is set to BPEL 1.1 Specification. The BBPEL 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, LOCATION_invoke_request.xsd, and select PS8.

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, LOCATION_invoke_response.xsd, and select PS8.

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. Create a connection between the outbound BPEL process component (location_out) and the third party adapter service component (Location), as shown in Figure 4-32.

    Figure 4-32 Component Connection

    
    Description of "Figure 4-32 Component Connection"
    
    

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

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

    Figure 4-33 Outbound BPEL Process Component

    
    Description of "Figure 4-33 Outbound BPEL Process Component"
    
    

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

    
    Description of "Figure 4-34 Invoke Activity Component"
    
    

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

    Figure 4-35 Created Connection

    
    Description of "Figure 4-35 Created Connection"
    
    

    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.

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

    Figure 4-41 Invoke Activity Component

    
    Description of "Figure 4-41 Invoke Activity Component"
    
    

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

    
    Description of "Figure 4-42 Assign Activity Component"
    
    

21. Double-click the new Assign activity component (Assign1), as shown in Figure 4-43.

    Figure 4-43 Assign Activity Component

    
    Description of "Figure 4-43 Assign Activity Component"
    
    

    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"
    
    

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

23. In the right pane, under Variables, expand Invoke1_LOCATION_InputVariable and select input_ LOCATION.

24. Drag and map the payload variable to the input_ LOCATION variable as shown in Figure 4-45.

    Figure 4-45 Edit Assign Dialog

    
    Description of "Figure 4-45 Edit Assign Dialog"
    
    

    The mapped variables are populated in the highlighted area as shown in

    Figure 4-46

    
    

25. Click Apply and then OK.

26. Drag and drop the Assign activity component to the Components pane and place it between the Invoke activity (Invoke1) and the Reply activity (replyOutput), as shown in Figure 4-47.

    Figure 4-47 Assign Activity Component

    
    Description of "Figure 4-47 Assign Activity Component"
    
    

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

    Figure 4-48 Assign Dialog

    
    Description of "Figure 4-48 Assign Dialog"
    
    

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

    Figure 4-49 Edit Assign Dialog

    
    Description of "Figure 4-49 Edit Assign Dialog"
    
    

28. In the left pane, under Variables, expand Invoke_1_LOCATION_OutputVariable, and then select output_LOCATION.

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

30. Drag and map the output_LOCATION variable to the payload variable as shown in Figure 4-50.

    Figure 4-50 Edit Assign Dialog

    
    Description of "Figure 4-50 Edit Assign Dialog"
    
    

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

    Figure 4-51 Edit Assign Dialog

    
    Description of "Figure 4-51 Edit Assign Dialog"
    
    

31. Click Apply and then OK.

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

    Figure 4-52 Completed Activity Flow

    
    Description of "Figure 4-52 Completed Activity Flow"
    
    

32. Double-click composite.xml in the left pane, as shown in Figure 4-53.

    Figure 4-53 Composite.xml Tab

    
    Description of "Figure 4-53 Composite.xml Tab"
    
    

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

    Figure 4-54 Save All Icon

    
    Description of "Figure 4-54 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, LOCATION_Invoke), select Deploy, and then click LOCATION_Invoke, as shown in Figure 4-55.

   Figure 4-55 Deploy Option

   
   Description of "Figure 4-55 Deploy Option"
   
   

   The Deployment Action page is displayed, as shown in Figure 4-56.

   Figure 4-56 Deployment Action Page

   
   Description of "Figure 4-56 Deployment Action Page"
   
   

2. Ensure that Deploy to Application Server is selected.

3. Click Next.

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

   Figure 4-57 Deploy Configuration Page

   
   Description of "Figure 4-57 Deploy Configuration Page"
   
   

4. Leave the default values selected and click Next.

   The Select Server page is displayed, as shown in Figure 4-58.

   Figure 4-58 Select Server Page

   
   Description of "Figure 4-58 Select Server Page"
   
   

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

   The SOA Servers page is displayed, as shown in Figure 4-59.

   Figure 4-59 SOA Servers Page

   
   Description of "Figure 4-59 SOA Servers Page"
   
   

6. Select a target SOA server and click Next.

   The Summary page is displayed, as shown in Figure 4-60.

   Figure 4-60 Summary Page

   
   Description of "Figure 4-60 Summary Page"
   
   

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-61.

   Figure 4-61 Successful Deployment Message

   
   Description of "Figure 4-61 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-62.

   Figure 4-62 Oracle Enterprise Manager Console

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

3. Select an available project (for example, PSoft_Outbound_LOCATION_BPEL), as shown in Figure 4-63.

   Figure 4-63 PSoft_Outbound_LOCATION_BPEL Project

   
   Description of "Figure 4-63 PSoft_Outbound_LOCATION_BPEL Project"
   
   

4. Click Test in the right pane.

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

   Figure 4-64 Test Web Service Page

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

5. Click the Request tab.

6. Scroll down to the Input Arguments section, as shown in Figure 4-65.

   Figure 4-65 Input Arguments Section

   
   Description of "Figure 4-65 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.

   For example:

   <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"><soap:Body xmlns:ci="urn:iwaysoftware:adapter:peoplesoft:location:ci:request"><ci:PS8>  <ci:component perform="browse">LOCATION</ci:component>  <ci:key name="SETID">SHARE</ci:key>  <ci:key name="LOCATION">ALBERTA</ci:key></ci:PS8></soap:Body></soap:Envelope>
   

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-66.

   Figure 4-66 Output Response Tab

   
   Description of "Figure 4-66 Output Response Tab"
   
   

Testing Outbound BPEL and Mediator Processes

When testing an outbound BPEL process or an outbound Mediator process from the Oracle 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 Oracle Enterprise Manager console. When creating a Mediator data flow and interactions, the Web services are created and registered with the Oracle WebLogic Server. For more information on how to create 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 section demonstrates how Oracle Application Adapter for PeopleSoft integrates with PeopleSoft to receive event data. In this example, a PeopleSoft event occurs when a customer record is added to a PeopleSoft system.

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

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 JDeveloper.

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 event and select that channel when you generate WSDL for inbound interaction using Application Explorer.

Note:

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

Creating a Channel

To create a channel:

1. Click the Events node.

2. Expand the PeopleSoft node.

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

   Figure 4-67 Expanded PeopleSoft Events Node

   
   Description of "Figure 4-67 Expanded PeopleSoft Events Node"
   
   

3. Right-click Channels and select Add Channel.

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

   Figure 4-68 Add Channel Dialog

   
   Description of "Figure 4-68 Add Channel Dialog"
   
   

   Provide the following information:

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

   2. Enter a brief description (optional).

   3. From the Protocol list, select HTTP Listener.

4. Click Next.

5. When the HTTP listener dialog is displayed, enter the system information as specified in the following table:

   Parameter	Description
   Listener port	Port on which to listen for PeopleSoft event data.
   Https	For a secure HTTP connection, select the Https check box.
   Synchronization Type	Choose from the following synchronization options: REQUEST_RESPONSE REQUEST_ACK Important: The PeopleSoft channel does not work if the synchronization type is set to REQUEST.

   
   

6. Click OK.

   The channel appears under the channels node in the left pane. An X over the icon indicates that the channel is currently disconnected.

   Note:

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

Generating WSDL for Event Notification

After you create a channel and verify that it is not started, you must generate WSDL for the event using Application Explorer.

1. Start Application Explorer.

2. Expand the Adapters node.

   A list of all available adapters is displayed.

3. Expand PeopleSoft.

4. Click a target name under the PeopleSoft node, for example, PSFTtarget.

   The Logon pane on the right displays the saved parameters.

5. Verify your connection parameters.

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

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

   Figure 4-69 Connected PSFT Target

   
   Description of "Figure 4-69 Connected PSFT Target"
   
   

7. Expand Messages and select LOCATION_SYNC.VERSION_1.

8. Right-click LOCATION_SYNC.VERSION_1.

   Figure 4-70 Create Inbound JCA Service (Event) Option

   
   Description of "Figure 4-70 Create Inbound JCA Service (Event) Option"
   
   

9. Select Create Inbound JCA Service (Event), as shown in Figure 4-70.

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

   Figure 4-71 Export WSDL Dialog

   
   Description of "Figure 4-71 Export WSDL Dialog"
   
   

   Perform the following steps:

   1. In the Name field, specify the name of the WSDL file.

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

   2. From the Channel list, select the channel you created for this inbound service.

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

   3. Three check boxes for Root, Namespace, and Schema validation are also available. Selection of multiple validation options is allowed.

      - Root validation is used to validate the root element in the inbound XML document.

      - Namespace validation is used to validate the namespace in the inbound XML document.

      - Schema validation is used to validate the inbound XML document with the schema in the WSDL document.

      During run time, validation is processed based on the validation options that are selected. If more than one validation option is selected, during run time if the first validation option fails, the remaining validation options are not processed. Root and namespace validations are considered modest levels of validation. Schema validation is a stricter validation level. It is recommended to use root and namespace validation options together, unless the root element and namespace are different between the Messages in the PeopleSoft environment.

10. Click OK.

    You can now create a new SOA application, which is the first step that is required to define a BPEL inbound process in JDeveloper.

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-72.

   Figure 4-72 New Option

   
   Description of "Figure 4-72 New Option"
   
   

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

   Figure 4-73 Create SOA Application Wizard

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

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

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

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

   Figure 4-74 Name Your Project Page

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

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

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

   Figure 4-75 Configure SOA Settings Page

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

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

   Figure 4-76 Application Navigator Tab

   
   Description of "Figure 4-76 Application Navigator Tab"
   
   

   The new SOA application (PSoft_Inbound_BPEL) and associated project (LOCATION_SYNC_Receive) are added to the Application Navigator tab in the left pane, as shown in Figure 4-76.

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-77.

   Figure 4-77 Third Party Adapter Component

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

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

   Figure 4-78 Create Third Party Adapter Service Dialog

   
   Description of "Figure 4-78 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 Figure 4-79.

   Figure 4-79 SOA Resource Dialog

   
   Description of "Figure 4-79 SOA Resource Dialog"
   
   

5. Browse and select an inbound WSDL file (for example, LOCATION_SYNC.VERSION_1_receive.wsdl) from the following directory:

   <ADAPTER_HOME>\soa\thirdparty\ApplicationAdapters\wsdls
   

6. Click OK.

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

   Figure 4-80 Localize Files Dialog

   
   Description of "Figure 4-80 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 4-81.

   Figure 4-81 Create Third Party Adapter Service Dialog

   
   Description of "Figure 4-81 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-82.

   Figure 4-82 SOA Resource Browser Dialog

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

9. Browse and select the JCA properties file (for example, LOCATION_SYNC.VERSION_1_receive.jca)from the following directory:

   <ADAPTER_HOME>\soa\thirdparty\ApplicationAdapters\wsdls
   

10. Click OK.

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

    Figure 4-83 Copy File Confirmation Message

    
    Description of "Figure 4-83 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-84.

    Figure 4-84 Create Third Party Adapter Service Dialog

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

12. Click OK.

    The third party adapter service component (location_sync) is created and displayed in the Exposed Services pane, as shown in Figure 4-85.

    Figure 4-85 Third Party Adapter Service Component

    
    Description of "Figure 4-85 Third Party Adapter Service Component"
    
    

    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 in Figure 4-86.

   Figure 4-86 BPEL Process Component

   
   Description of "Figure 4-86 BPEL Process Component"
   
   

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

   Figure 4-87 Create BPEL Process Dialog

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

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

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

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

4. Uncheck the Expose as 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 Figure 4-88.

   Figure 4-88 SOA Resource Browser

   
   Description of "Figure 4-88 SOA Resource Browser"
   
   

6. Browse and select an inbound WSDL file (for example, LOCATION_SYNC.VERSION_1_receive.wsdl) from the default WSDL location.

7. Click OK.

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

   Figure 4-89 Localize Files Dialog

   
   Description of "Figure 4-89 Localize Files Dialog"
   
   

8. Uncheck the Rename duplicate files option in the Copy Options area, and then click OK.

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

   Figure 4-90 Create BPEL Process Dialog

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

9. Click OK.

   Figure 4-91 Created Connection

   
   Description of "Figure 4-91 Created Connection"
   
   

10. Create a connection between the third party adapter service component (location_sync) and the inbound BPEL process component (Location_Sync_Inbound), as shown in Figure 4-91.

11. Double-click composite.xml in the left pane, as shown in Figure 4-92.

    Figure 4-92 Composite.xml File

    
    Description of "Figure 4-92 Composite.xml File"
    
    

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

    Figure 4-93 Save All Icon

    
    Description of "Figure 4-93 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, LOCATION_SYNC_Receive), select Deploy, and then click LOCATION_SYNC_Receive, as shown in Figure 4-94.

   Figure 4-94 Deploy Option

   
   Description of "Figure 4-94 Deploy Option"
   
   

   The Deployment Action page is displayed, as shown in Figure 4-95.

   Figure 4-95 Deployment Action Page

   
   Description of "Figure 4-95 Deployment Action Page"
   
   

2. Ensure that Deploy to Application Server is selected.

3. Click Next.

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

   Figure 4-96 Deploy Configuration Page

   
   Description of "Figure 4-96 Deploy Configuration Page"
   
   

4. Leave the default values selected and click Next.

   The Select Server page is displayed, as shown in Figure 4-97.

   Figure 4-97 Select Server Page

   
   Description of "Figure 4-97 Select Server Page"
   
   

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

   The SOA Servers page is displayed, as shown in Figure 4-98.

   Figure 4-98 SOA Servers Page

   
   Description of "Figure 4-98 SOA Servers Page"
   
   

6. Select a target SOA server and click Next.

   The Summary page is displayed, as shown in Figure 4-99.

   Figure 4-99 Summary Page

   
   Description of "Figure 4-99 Summary Page"
   
   

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-100.

   Figure 4-100 Successful Deployment Message

   
   Description of "Figure 4-100 Successful Deployment Message"
   
   

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

Triggering an Event in PeopleSoft

Events are generated by activity in an application system. For example, PeopleSoft may generate an event as customer information is updated in the system. The following topics describe how to trigger an event in PeopleSoft and verify the event using Oracle Application Adapter for PeopleSoft.

To trigger an event in PeopleSoft:

1. Log in to PeopleSoft, select PeopleTools, Integration Broker, Integration Setup and then Nodes, as shown in Figure 4-101.

   Figure 4-101 PeopleTools Node Definitions

   
   Description of "Figure 4-101 PeopleTools Node Definitions"
   
   

2. Enter the node name you are using, for example, EXTERNAL, then click Search, as shown in Figure 4-102.

   Figure 4-102 External Node Name

   
   Description of "Figure 4-102 External Node Name"
   
   

3. Click the Connectors tab, as shown in Figure 4-103.

   Figure 4-103 Connectors Tab

   
   Description of "Figure 4-103 Connectors Tab"
   
   

4. Enter HTTPTARGET in the Connector ID field; then enter the listener URL and its port in the PRIMARYURL field.

5. To save the configuration, click Save.

   A successful dialog window is displayed.

   To check the listener status, click on the Ping Node button and continue the triggering if a window appears, as shown in Figure 4-104.

   Figure 4-104 Ping Node

   
   Description of "Figure 4-104 Ping Node"
   
   

6. Select Integration Broker, Integration Setup, and then Services from the main menu.

7. Enter LOCATION_SYNC in the Services field, and then click Search, as shown in Figure 4-105.

   Figure 4-105 Services

   
   Description of "Figure 4-105 Services"
   
   

8. Click LOCATION_SYNC.VERSION_1 in the Operation tab, as shown in Figure 4-106.

   Figure 4-106 Operation Tab

   
   Description of "Figure 4-106 Operation Tab"
   
   

9. Click the Routings tab, as shown in Figure 4-107.

   Figure 4-107 Routings Tab

   
   Description of "Figure 4-107 Routings Tab"
   
   

10. Click ADD_LOC in the Routing Definitions section, as shown in Figure 4-108.

    Figure 4-108 Routing Definitions Section

    
    Description of "Figure 4-108 Routing Definitions Section"
    
    

11. Click the Connector Properties tab, as shown in Figure 4-109.

    Figure 4-109 Connector Properties Tab

    
    Description of "Figure 4-109 Connector Properties Tab"
    
    

12. Enter the URL and the port number of the HTTP listener in the Connector Properties section and click Save, as shown in Figure 4-110.

    Figure 4-110 Connector Properties Section

    
    Description of "Figure 4-110 Connector Properties Section"
    
    

13. From the Main Menu in the left pane, select Set Up HRMS, Foundation Tables, Organization, and then Location, as shown in Figure 4-111.

    Figure 4-111 PeopleSoft Integration Broker Connectors Tab

    
    Description of "Figure 4-111 PeopleSoft Integration Broker Connectors Tab"
    
    

14. To find the location record you want to update, click Search; then make the changes and click Save, as shown in Figure 4-112.

    Figure 4-112 Location Definition Pane

    
    Description of "Figure 4-112 Location Definition Pane"
    
    

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. Expand your domain in the left pane followed by the SOA folder.

   Figure 4-113 Oracle Enterprise Manager Console

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

3. Select an available project (for example, PSoft_Inbound_LOCATION_SYNC.VERSION_1_BPEL), as shown in Figure 4-113.

   Figure 4-114 PSoft_Inbound_LOCATION_SYNC.VERSION_1_BPEL Project

   
   Description of "Figure 4-114 PSoft_Inbound_LOCATION_SYNC.VERSION_1_BPEL Project"
   
   

4. Click the Instances tab in the right pane, as shown in Figure 4-114.

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

   Figure 4-115 Recently Received Run-time Events

   
   Description of "Figure 4-115 Recently Received Run-time Events"
   
   

5. Select a PeopleSoft instance ID.

   The Flow Trace page is displayed, as shown in Figure 4-116.

   Figure 4-116 Flow Trace Page

   
   Description of "Figure 4-116 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 Figure 4-117.

   Figure 4-117 Instance Page

   
   Description of "Figure 4-117 Instance Page"
   
   

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

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