Oracle - Web Services and PeopleTools

8/13/2019 Oracle - Web Services and PeopleTools

1/55

Stephen Wills

Applied Technology Sales Consultant

Web Services And PeopleToolsSouthern New England User Group Meeting, October 17th, 2008


2/55

The following is intended to outline our generalproduct direction. It is intended for informationpurposes only, and may not be incorporated into anycontract. It is not a commitment to deliver anymaterial, code, or functionality, and should not berelied upon in making purchasing decisions.The development, release, and timing of anyfeatures or functionality described for Oraclesproducts remains at the sole discretion of Oracle.


3/55

Agenda

Introduction To PeopleSoft Application Integration

Consuming A Web Service The Web Service Wizard

Demo: calling a Web Service and processing the results

Exposing A Web Service

Components

Component Interfaces

Demo

Preparing Services Publishing WSDL

Adding fields and re-publishing


4/55

Agenda





Components


Demo

Preparing Services Publishing WSDL

Adding fields and re-publishing


5/55

PeopleSoft Application IntegrationWhats The Goal?

Our goal with PeopleSoft Application Integration is to:

Enable application developers and customers to natively createand consume standard web services so that PeopleSoft

applications can integrate into SOA environments

Improve interoperability and automation by leveraging Web Service

standards and a common interface

Provide the option of interoperating with robust, optimized business

integration services through Oracle Business Integration

Technology (BPEL/ESB)


6/55

PeopleSoft IntegrationHow Do We Achieve This Goal?

Integration technology built into the PeopleSoft Internet

Architecture the PeopleSoft Integration Broker Embedded in tool set and delivered with all PeopleSoft

Enterprise applications

Providing support for:

Web Services

Inbound/outbound synchronous/asynchronous XML messaging,

including SOAP support

COM, C, C++, Java, XML access to PeopleSoft application logic

via API

Flat File processing, inbound and outbound


7/55

Messaging Transformation

Routing

Connectors

Development

Monitoring

What is an Integration Broker?


8/55

ServicesFocus on Added Web Services Support in PeopleTools 8.48


9/55

Service Operations

Focus on Added Web Services Support in PeopleTools 8.48


10/55

Wizards



11/55

Utilities



12/55

Monitor



13/55

Agenda





Components


Demo

Preparing Services

Publishing WSDL

Calling Service


14/55

DemonstrationConsume and Call a Web Service

Illustrate Web Service call using public Web Service:

Demonstrate calling a web service Review Contact Component

Review code used to invoke the Web Service

Review code used to process the results


15/55

Web Services Home Page

Web Services options accessed from Web Services Home Page


16/55

Consume Web Service Wizard

Wizard imports Web Service definitions from a variety of sources


17/55


Wizard inspects the WSDL and determines the service operations

that it finds only one in this case


18/55


NJM WSDL loaded from a file


19/55


Additional parameters automatically derived and set


20/55


21/55


Message names can be over-ridden if required for ease-of-use


22/55


Service name and default node automatically added


23/55


Confirmation of created Web Services objects

Complete view of objects available via View Consumed Service


24/55

View Consumed Service

View of complete Service including all associated objects


25/55

Consume Web ServiceDemonstration


26/55

Calling A Web Service

Web Service invoked programmatically by PeopleCode

For a synchronous message this would typically be codeon a FieldChange or PageSave event


27/55


Contact Record has FieldChange PeopleCode for FieldChange


28/55


1. Construct Request string

2. Make Synchronous Request Message call and receive results inthe Response Message

3. Unravel Response Message and display appropriate fields


29/55

Call Web ServiceDemonstration


30/55

Call Web Service

Example

User updates the

value of the data in

the Zip Code field Field Change

PeopleCode triggers

to call the Web

Service to return theWeather information

for that Zip code


31/55

Call Web Service

Example

Web Service returns

Weather including:

A graphic showingthe weather

High and low

forecast

temperatures

PeopleCode:

Extracts info from

the Web Service

response message

Formats anddisplays it on the

page


32/55

Agenda





Components


Demo

Preparing Services

Publishing WSDL

Calling Service


33/55

Demonstration

Publish And Process a Web Service

Review the PeopleTools object hierarchy

Review the Vendor Component Expose the Vendor Component as a Web Service

Call the Web Service using the SoapUI utility


34/55

PeopleTools Building Blocks

Record

Field FieldField

Record

Field FieldField

Record

Field FieldField

Page (Defines UI)Page (Defines UI)

Menu (Controls Navigation)

Security (Controls Access)

Component (Business Transaction Object)

Create fields

Create records from fields

Create pages from records

Create components from pages

Define Menu navigation to component

Set Security for component

Deploy via browser


35/55

PeopleTools Building Blocks

Record

Field FieldField

Record

Field FieldField

Record

Field FieldField

Page (Defines UI)Page (Defines UI)

Menu (Controls Navigation)

Component Interface

SOAP/

Web Services

Component Interface API

Java C/C++ COMPeopleSoft

Batch App

File

Layout

Security (Controls Access)

Component (Business Transaction Object)


36/55

Demonstration

Publish and process a Web Service

Review the PeopleTools object hierarchy

Review the Vendor Component Expose the Vendor Component as a Web Service

Call the Web Service using the SoapUI utility


37/55

Review the Vendor Component

Vendor Component in browser


38/55


Vendor Component in browser


39/55


Vendor Component Definition


40/55


Vendor Component Structure


41/55

Vendor Component Interface

This is the basis for the published Web Service

Fields become Properties

Default Methods are provided; others can be added with PeopleCode


42/55

Enable Required Service Operations

Select the Component Interface to be exposed as a Web Service


43/55


Review the CI Status to determine available CI Methods

Selected CI Methods will become Service Operations


44/55


Defaults are created

Aliases and message versions may be specified if required


45/55


Web Service and Service Operations now created

The Web Service can now be published and WSDL generated

S


46/55

Provide Web Service Wizard

Provide Web Service Wizard steps through process

Step 1: Select Service to be provided (defined in previous step)

P id W b S i Wi d


47/55



Step 2: Select required Service Operations

P id W b S i Wi d


48/55



Step 3: View Generated WSDL for Service

P id W b S i Wi d


49/55



Step 4: Publish WSDL to UDDI Server if required

Pro ide Web Ser ice Wi ard


50/55



Finish: Review WSDL Generation Log: note the WSDL URL

Test The Web Service


51/55


Test the Web Service with standard test tools e.g. SOAPUI

Add Web Service definition to testing tool using .WSDL



52/55



Web Service Operation definitions retrieved and created



53/55



Example of FindService Operation (Vendors starting with C)



54/55



Example of GetService Operation (for a Vendor returned by Find)

Q/A


55/55

Q/A

Documents

Oracle - Web Services and PeopleTools