PeopleSoft Outbound Sales Order to ESB

Purpose

In this tutorial, you learn how to configure PeopleSoft Integration Broker to publish an Application Message as an outbound SOAP message to an external Oracle Enterprise Service Bus (ESB) process. You create an XSD from a WSDL file that is generated by Peopelsoft and provide that XSD file as input to the ESB service. You also learn how to create, deploy, and test an ESB service to receive the published Application Message (a Sales Order from PeopleSoft.)

Time to Complete

Approximately 3 hours

Topics

This tutorial covers the following topics:

	Overview
	Prerequisites
	PeopleSoft Setup
	PeopleSoft Integration Setup
	Create an ESB Service
	Submit a Sales Order from PeopleSoft
	Summary
	Related information

Viewing Screenshots

Place the cursor over this icon to load and view all the screenshots for this tutorial. (Caution: This action loads all screenshots simultaneously, so response time may be slow depending on your Internet connection.)

Note: Alternatively, you can place the cursor over an individual icon in the following steps to load and view only the screenshot associated with that step. You can hide an individual screenshot by clicking it.

Overview

This integration example highlights PeopleSoft as a Web Service provider for services that are consumed by Oracle SOA Suite Enterprise Service Bus (ESB). A common business scenario is where an event is generated in Peoplesoft and a number of external applications need to be made aware of the availability of this event. For example, generation of a new Sales Order, new employee record, or new journal entry are events that require order data, employee data or journal data to be published to external system. In this tutorial, when a new Sales Order is created in PeopleSoft CRM, an AppMessage is created, wrapped in a SOAP envelope, and published using Integration Broker to Oracle ESB. As part of this task, message schemas are extracted and provided to the ESB for service consumption. ESB then consumes the message and routes it to any external application. This tutorial uses a file system as an external application to which messages are routed.

Back to Topic List

Prerequisites

Before starting this tutorial, you should:

Back to Topic List

PeopleSoft Setup

To perform steps described in this tutorial, first make sure that PeopleSoft Configuration is ready. Verify that the PeopleSoft Gateway is accessible and that the Peoplesoft Integration Broker service is ready to create an outbound event message route as described below. Then define the message type to be consumed by a Web Service consumer such as an Enterprise Service Bus process.

Back to Topic List

PeopleSoft Integration Setup

Back to Topic List

1.	Creating a Node: Nodes represent any organization, application or system that play a part in integration. For example, nodes can represent customers, business units, suppliers, other trading partners, external or third-party software systems, and so on. Node definitions define the locations to or from which messages can be routed. Because an application can send messages to itself, a default local node definition that represents the application is delivered as part of the integration engine. Create a Node for your SOA Suite system. a. Open an Internet Explorer window and browse to PeopleSoft URL. Login with a valid Userid and Password. b. From the menu on the left, navigate to PeopleTools -> Integration Broker -> Integration Setup -> Nodes. To create a new Node, click the Add a New Value tab. c. Enter a unique name for the node.This tutorial uses node name VICKY. Click Add. A node by name VICKY is now added. Click the node name link in the search result to set the node definition. d. On the Node Definitions Tab, perform the following: Enter a Description Select External as the Node Type Select None as the Authentication Option Enter VP1 as the Default UserID (this is not used for Outbound integration) Click Save. e. Click the Connectors tab to set the communication protocol. The Gateway ID should already be set to LOCAL. If not, enter LOCAL. Click the Lookup Connector ID magnifying glass next to Connector ID field and select HTTPTARGET from the popup list. You will see three HTTP properties. In value field of property with ID PRIMARYURL, enter your ESB Console URL http://<your IP Address>:<port>/esb/esb/EsbConsole.html Click the Ping Node button to test connectivity to the ESB Console. You should receive a Success message as shown in the following screenshot. If it is not successful, check your URLIP Address and return to the Connector page to try again. Click Save. We could click the routing tab and add the routing but we will navigate a different way so you get familiar with the other pages.
2.	Creating a Routing A routing definition defines the sending and receiving nodes for a transaction, and specifies any inbound and outbound transformations to invoke. A routing definition must exist on each system that is participating in a particular transaction. For example, let's say that System A (local node) is going to send a service operation to System B (ESB), a point-to-point routing needs to be created between the two systems. a. In the PeopleSoft instance, from the menu on the left, navigate to PeopleTools -> Integration Broker -> Integration Setup -> Services. b. Enter CRM_SALES_ORDER in the search field and click Search . c. In the Services page > Existing Operations section, click the CRM_SALES_ORDER.VERSION_1 service operation. d. Create a routing to distribute the message upon firing. On the Service Operation screen, select the ROUTINGS tab. e. Create a routing to your specific node by typing a unique name in the Routing Name field (ex. ROUTE_<nodename>) and click the ADD button. This tutorial adds a routing called ORDER2VICKYESB. f. Enter the following info on the Routing Definitions tab Description: Enter a description Sender Node: Enter PSFT_CR (this is your local node name) Receiver Node: This should be the node you created g. Click the Connector Properties tab. h. The Gateway ID should be LOCAL and the Connector ID should be HTTPTARGET. Setup the Connector Properties to match the following: HEADER CONTENT-TYPE text/xml; charset=utf-8 HEADER SOAPACTION "execute" HEADER SENDUNCOMPRESSED Y HTTPPROPERTY METHOD POST HTTPPROPERTY SOAPUpContent Y PRIMARYURL URL http://<your_ip_address>:port/event/PeopleSoft/Inbound/ReceivePSFTOrder_RS By default only 3 properties are shown. To add more properties so you can set the above values, click the + sign corresponding to a property row below which you want to create the new property row. To choose property ID, name, and value from a list of available values, use the search icon relative to each field. Otherwise you can directly type the value in the field. Property ID Property Name Value HEADER CONTENT-TYPE text/xml; charset=utf-8 HEADER SOAPACTION "execute" HEADER SENDUNCOMPRESSED Y HTTPPROPERTY METHOD POST HTTPPROPERTY SOAPUpContent Y PRIMARYURL URL http://<your_ip_address>:port/event/PeopleSoft/Inbound/ReceivePSFTOrder_RS Note: the SoapAction and Primary URL must match the service that we will create in ESB. i. Now we need to add a transformation to add proper Namespace to the outbound message. Click the Parameters Tab. j. For the Message.Ver into Transform 1 field, select CRM_SALES_ORDER.VERSION_1 k. For the Transform Program 1 field, select the transformation that was created in a previous step (ie ADD_MSG_NS) l. For the Message.Ver out of Transforms field, select CRM_SALES_ORDER.VERSION_1   m. Click Save.
3.	Creating XSD file from Generated WSDL You need to import the XSD schema of the CRM_SALES_ORDER message into the ESB project that you will create in the next section. The Provide Web Service function generates a WSDL with inline XSD schema for any Service/Service Operation with an "Any to Local" Inbound Routing. Even though this tutorial is an Outbound integration and not an Inbound integration, we will add an inbound routing so the WSDL can be generated and we can pull the inline XSD. Perform the following are the steps to generate a WSDL and to copy/paste the schema from it to create a XSD file. a. Generate an Inbound Routing for our Service. From the menu the menu on the left, navigate to PeopleTools -> Integration Broker -> Services Operation. Enter CRM_SALES_ORDER in the search field and click Search. b. In the Services Operation section, click the CRM_SALES_ORDER link to view details about this service. c. In the Default Service Operations Version > Routing Actions Upon Save section, select the Generate Any-to-Local check box. Had the routing action been generated previously, you will see the Regenerate Any-to-Local check box instead. d. Click Save. This generates an Inbound Routing and you receive a confimation message window. Acknowledge and dismiss the window. You can see the Inbound Routing by click on the Routings tab. e. Now generate the WSDL. Navigate to PeopleTools -> Integration Broker -> Web Services -> Provide Web Service. f. In Step 1, enter CRM_SALES_ORDER as the Service Name and click Search. Make sure the CRM_SALES_ORDER Service check box is selected and click the Next button. In Step 2, select the Service Operation CRM_SALES_ORDER.VERSION_1 check box and click the Next button. In Step 3, click the View WSDL link to view the WSDL. g. Within the WSDL Viewer window, right click and click Select All. Copy the content to a clip board. Open a Notepad file on your system and paste the copied content into it. The in-line schema that we want are all lines beginning with tags <xsd:> or </xsd:>. Remove all lines starting with <wsdl: or </wsdl: at the start and end of the file so what is left is all lines between tags <xsd:schema .> and </xsd: schema>. In Notepad, select File > SaveAs to save this file on your machine as CRM_SALES_ORDER.xsd.

Back to Topic List

Create an ESB Service

Back to Topic List

Submit a Sales Order from PeopleSoft

Finally, we are ready to test by creating a new Sales Order. The customer name and product ID used in our example here are based on our local configuration. For your CRM instance, use a customer and a product that exists in your system.

1.	Open an Internet Explorer window to the PeopleSoft URL and login to PeopleSoft instance with appropriate Userid and Password. From the menu on the left, navigate to Orders and Quotes -> Add Order to open a New Order Form.
2.	In the Customer Field box, enter Adventure 54 and click the Search button to bring up the customer record.
3.	In the Line Summary section > Add Product(s) field, enter 10009 and click the Add button to retrieve the product data.
4.	Click Submit.
5.	A message that the order has successfully been submitted is displayed along with an Order ID at the top of the page.
6.	Return to the ESB Control Center browser window or start it if not already open. Click the Instance icon to see any new instance can be noticed.
7.	Click the Go arrow button that appears next to the Search field to search for all the Instances. If you don't see any new instance, review the Troubleshooting section.
8.	Highlight the retrieved Instance to see the Instance Diagram.
9	For final confirmation of a successful run, use Windows Explorer to verify that the order file (Order_#.xml) was indeed created in the c:\temp folder which is you identified in FileAdapater creation.

Back to Topic List

Summary

In this tutorial you learned how to generate WSDL from Peoplesoft and how to create an ESB service that can consume the generated WSDL.

Back to Topic List

Place the cursor over this icon to hide all screenshots.