CON9126 - Bain-CON9126 Roadmap-IntegrationBroker PDF

1 Copyright 2012, Oracle and/or its affiliates. All rights reserved.
ed. Insert Information Protection Policy Classification from Slide 13

Integration Broker Roadmap
Dave Bain
PeopleSoft Product Management
2 Copyright 2012, Oracle and/or its affiliates. All rights reserved. Insert Information Protection Policy Classification from Slide 13
The following is intended to outline our general product
direction. It is intended for information purposes only,
and may not be incorporated into any contract.
It is not a commitment to deliver any material, code, or
functionality, and should not be relied upon in making
purchasing decisions. The development, release, and
timing of any features or functionality described for
Oracles products remains at the sole discretion of
Oracle.
Program Agenda
Integration Broker Value Proposition

Documents
RESTful Services
Integration Network
Integration Workcenter
Mobile Application Platform
Q&A
Integration Broker
Integration Gateway External Systems
G
PeopleSoft HTTP Custom
App ESB
a
http t Web
Service JMS
PeopleSoft e
App Server Listening Mobile
Connector w PSFT
8.1 REST UI
a
y Listening Connectors
jolt M
PeopleSoft a HTTP FTP Custom
FTP
Target EMail
Connector n
Message Queues a SMTP JMS SFTP
g XML
PSFT
e 8.1 File
r
Target Connectors
Integration Broker
PeopleSoft to
PeopleSoft
Integrations
Integration Broker is
technology to integrate with
PeopleSoft Applications
Fusion
Apps/ Integration 3rd Party Service Definitions
Fusion Broker Integrations
Middleware Pub/Sub Services
Integration Gateway
Web
Services
Integration Broker
The next progression

for Integration Broker is
Integration providing fluid user
Broker interfaces for front end
integration
Integration Broker
Connecting PeopleSoft Applications
Continue to Invest in Integration Technology to Provide the Best
Standards Based Integration for PeopleSoft Applications
Increase Developer/Administrator Productivity

Improve Performance and Stability
Add More Integration Options
Ongoing Compliance with Standards
Documents
Integration Broker
Documents are the

primary Data Structure
used across Integration
Broker. They are
required for new
features such as
RESTful Services and
Mobile Application
Platform
Integration Broker
Documents
Structure Data Definition

Primitives, compounds
(document), and collections (of
primitive or compounds).
Rich PeopleCode API
Translate between XML or
PeopleSoft Record Definitions
Integration Broker
Create a Document from

XML Schema or a
PeopleSoft Record
Definition
Integration Broker
In the Document Tester,

add values and generate
XML, JSON or
PeopleCode
RESTful Web Services
Integration Broker
RESTful Services
Representative State Transfer is an architectural style that follows four
principles
HTTP methods for operations (get, post, put, delete)
Stateless thus a representation
Can be located via a uniform resource identifier
Body contents is XML or Java Script Object Notation (JSON)
Adopted by Yahoo, Facebook, Amazon, Google
Generally considered easier to use than WSDL
Integration Broker
RESTful Services
RESTful services are

Defined as a Service type in Integration Broker
Support for
HTTP Based operations (post, get, put, delete, head)
Supported type JSON, XML, HTTP, Text
Gives developers more options one that is being heavily adopted
Easier to build/use expect gains in developer productivity
Integration Broker
Building a RESTful Service

RESTful or Non-RESTful
Defined at the Service, not
Service Operation
Cannot be changed once
created
Integration Broker
Distinguish between provider

and consumer
Use Web Access Descriptive
Language (WADL) not Web
Service Descriptive Language
(WSDL)
Rest Method is an HTTP
method, not Service Operation
Integration Broker
Service Operation defines

REST HTTP Method
Security Authentication
Type
PSToken w/o SSL
Basic Auth w/o SSL
None
Integration Broker
RESTful Service
Rest Base URL + URI:

http://rtdc79492vmc:813/PSIGW/PSIGW/RESTListeningConnector/Employees.v1/employees
Integration Broker
In this example, the URL to call the service is one of these:

http://10.242.11.95/:813/PSIGW/RESTListeningConnector/AKTT/WeatherStation.v1/weather/CA/Oakland?forecast=10/06/2011
http://10.242.11.95/:813/PSIGW/RESTListeningConnector/AKTT/WeatherStation.v1/weather/CA/Oakland
http://10.242.11.95/:813/PSIGW/RESTListeningConnector/AKTT/WeatherStation.v1/weather/CA
Integration Broker
URI Template Builder
Simplifies the process of

creating one or more URIs
Expression builder
Follows standards
Validate to see results
New in PeopleTools 8.53
Integration Broker
REST Content Type
Supports all standard

content types
JSON
XML
HTML
Plain text
Integration Broker
RESTful Service
From this:
<?xml version="1.0"?>
<soapenv:Envelope xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:wsa="http://schemas.xmlsoap.org/ws/2003/03/addressing/" xmlns:xsd="http://www.w3.org/2001/XMLSchema/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance/">
<soapenv:Header xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
<wsse:Security soap:mustUnderstand="1" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-
200401-wss-wssecurity-secext-1.0.xsd">
<wsse:UsernameToken wsu:Id="UsernameToken-1" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">
<wsse:Username>USER</wsse:Username>
<wsse:Password Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText">PASSWORD</wsse:Password>
</wsse:UsernameToken>
</wsse:Security>
</soapenv:Header>
<soapenv:Body xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"/>
</soapenv:Envelope>
To this:
http://PSPC:813/PSIGW/RESTListeningConnector/Employee_Details.v1/details/KF0016
Integration Broker
PeopleTools 8.52
RESTful Services introduced
Support for XML and plain text
Simple URI support
PeopleTools 8.53
Support for JSON directly from a document
Generate PeopleCode from document
Complex URI definition
Integration Network HCM FMS
CRM Portal
Integration Broker
Local Gateway
Two or more PeopleSoft

HCM CS
applications share a common
Integration Gateway
Gateway PeopleTools version Integration
Gateway
must be equal to or greater than
the most recent PeopleTools
version of all the Applications
FSCM CRM
Integration Broker
Remote Gateway
Integration Gateway to
HCM CS
Gateway communication is
referred to as Remote Gateway
IG IG
FSCM CRM
Integration Broker
Problems
Maintaining integration
points at endpoints is HCM CS
difficult.
Makes tasks such as Integration

Gateway
brining a new system online
or updating a system
difficult.
Hard to track a message

through the entire lifecycle FSCM CRM
of the message
Integration Broker
Integration Network
Requires two or more
PeopleSoft applications
Allows administration of
many tasks to be done
from a single system,
with insight into all
systems
Provides useful reports
and utilities
Integration Broker
Integration Network
At least one application must be
running PeopleTools 8.52 or above
All applications that share a local
Integration Gateway are considered
part of the same Integration
Network
PeopleSoft applications accessed
via remote gateways are supported
Integration Broker
Node Registration
List of all nodes on the gateway

that are not part of the
Integration Network
Automatically add node
definitions to both sides
Simplifies setting up test
environments and bringing up
new systems
Integration Broker
Integration Network
Network Setup
Identify the applications that are part
of the Integration Network
Each application must have local
keystore setup
Network Node Registration (8.53)
automatically registers nodes from a
shared gateway
Integration Broker
Integration Network
Network Status
Check the status of each application
in the Integration Network from one
place
Drill into error details to see more
information about status errors
Integration Broker
Integration Network
Network Monitor
Check the monitor information from
any application in the Integration
Network
Drill into the details and look at
transaction information
Integration Broker
Integration Network
Transactional Tracker
Track the details of a message on
both the local sending and the
remote receiving applications
Eliminates the need to disconnect
and log on to another system for
transaction details
Immediate insight, useful for
debugging
Integration Broker
Integration Network
Bulk Change
One time change to a set of nodes
in the integration network
Search based on node-type and
other criteria
Limited to select fields
Integration Broker
Integration Network
Node Lockdown
Preserve partial values on Node
definitions when projects are applied
Useful for migrating between
development, testing and production
environments
Integration Broker
Integration Network
Introspection
Looks at the group of integration
points selected across the
integration network
Determines if the integrations are
valid and operational
Reports on any errors
Will activate and build routing
definitions on request
Integration Broker
Integration Network
Active Integrations
Given a node and an integration
group this will list all the active
integration points
Integration Broker
Workcenter
Single landing page

Assigned to users by role
Simplifies navigation
Provides most common links,
components, reports
Integration Broker
Configuration
Administration
Monitoring
Utilities
Integration Broker
Configuration Activity Guide
Simplifies configuration process

Keeps track of current step
Completion of the activity guide
completes setup
Integration Broker HCM FMS
Release 8.53
CRM CS
Integration Broker
PeopleTools 8.53
Document Enhancements
JSON support for documents
Auto generate json structures
RESTful Service URI Builder
Integration Network
Automatic registration
Workcenter
Configuration Activity Guide
Integration Broker
PeopleTools 8.53
Connector Request is a PeopleCode API that issues a

direct call to the HTTP Target Connector
Better error handling with the Connector Request
&Output = %IntBroker.ConnectorRequestURL
("http://finance.yahoo.com/d/quotes.txt/ ?symbols=PSFT&format=l1c1d1t1");
Integration Broker
PeopleTools 8.53
JMS Listening Admin
New Administration page that

helps administer JMS
integrations
Integration Broker
PeopleTools 8.53
Maximum Segments
Global setting for the maximum

number of segments for a
message
Prevents very large messages
from processing
Used in the Data Migration
Workbench
Integration Broker
PeopleTools 8.53
XSLT Builder
New XSLT Transformation Page
Integration Broker HCM FMS
Release 8.54
CRM CS
Putting Integration Broker
to Use:
Integration Broker
Next Gen UI and MAP
Next Gen UI
And Mobile
Application
Platform are two
different
complementary
technologies
Integration Broker
Next Generation UI
Natural progression of
PeopleSoft user interface to
support smartphone, tablet and
desktop devices
Complete support for entire PIA
stack
Reuse of significant portions of
business logic and PeopleTools
Integration Broker
MAP Technology
Natural progression of RESTful
service feature
Runs through Integration
Gateway so it bypasses entire
PIA stack
RESTful services are generated
for default behavior and
supplemented with PeopleCode
and Java Script
Demo:
Mobile Approvals
Integration Broker
Layouts describe the

contents of pages that
are made from document
elements and static
controls. Layouts are
created in the Layout
Designer
Integration Broker
The Template contains all

of the styles for the page
layout. They are
responsive and can
provide different look
based on media type.
Templates can be reused
across layouts to keep a
common look and feel.
Integration Broker
The Mobile Application

Platform WorkCenter
provides a productive
user interface for building
responsive mobile
applications
Integration Broker
MAP Technology
Flexible UI use for entire app or for plugins
Open Integration Model multi-app, multi-pillar
access
Performance server side caching, simple
lightweight ajax
Security supports classic web model
Reusable patterns
Responsive development based on media types
Pluggable User Interface following RESTful
service architecture
Integration Broker
Connecting PeopleSoft Applications
Continue to Invest in Integration Technology to Provide the Best
Standards Based Integration for PeopleSoft Applications
Increase Developer/Administrator Productivity

Improve Performance and Stability
Add More Integration Options
Ongoing Compliance with Standards
ORACLE
PRODUCT
LOGO
QUESTIONS
AND
ANSWERS
Graphic Section Divider

CON9126 - Bain-CON9126 Roadmap-IntegrationBroker PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

CON9126 - Bain-CON9126 Roadmap-IntegrationBroker PDF

Uploaded by

Copyright:

Available Formats

1 Copyright 2012, Oracle and/or its affiliates. All rights reserved.

ed. Insert Information Protection Policy Classification from Slide 13

Integration Broker Value Proposition

The next progression

Increase Developer/Administrator Productivity

Documents are the

Structure Data Definition

Create a Document from

In the Document Tester,

RESTful services are

Building a RESTful Service

Building a RESTful Service

Distinguish between provider

Building a RESTful Service

Service Operation defines

Rest Base URL + URI:

In this example, the URL to call the service is one of these:

URI Template Builder

Simplifies the process of

REST Content Type

Supports all standard

Two or more PeopleSoft

Makes tasks such as Integration

Hard to track a message

List of all nodes on the gateway

Single landing page

Configuration Activity Guide

Simplifies configuration process

Connector Request is a PeopleCode API that issues a

JMS Listening Admin

New Administration page that

Global setting for the maximum

New XSLT Transformation Page

Layouts describe the

The Template contains all

The Mobile Application

Increase Developer/Administrator Productivity

You might also like