PeopleSoft Services Repository

User Guide

April 2012
PeopleSoft Services Repository
Copyright © 2012, Oracle and/or its affiliates. All rights reserved.

This software and related documentation are provided under a license agreement containing restrictions on
use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your
license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license,
transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse
engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is
prohibited.
The information contained herein is subject to change without notice and is not warranted to be error-free. If
you find any errors, please report them to us in writing.
If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on
behalf of the U.S. Government, the following notice is applicable:
U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software,
any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are
“commercial computer software” pursuant to the applicable Federal Acquisition Regulation and agency-
specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the
programs, including any operating system, integrated software, any programs installed on the hardware,
and/or documentation, shall be subject to license terms and license restrictions applicable to the programs.
No other rights are granted to the U.S. Government.
This software or hardware is developed for general use in a variety of information management applications.
It is not developed or intended for use in any inherently dangerous applications, including applications that
may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you
shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its
safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this
software or hardware in dangerous applications.
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of
their respective owners.
This software or hardware and documentation may provide access to or information on content, products, and
services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim
all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and
its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of
third-party content, products, or services.
PeopleSoft User Guide PeopleSoft Services Repository
April 2012

Contents
Introduction ......................................................................................................................................................4 
PeopleSoft Services Repository Tool ...........................................................................................................4 
User Input Menu .......................................................................................................................................4 
Running the Report ...................................................................................................................................5 
Integration Concepts in the PeopleSoft System ...........................................................................................7 
Integration Points ......................................................................................................................................7 
Integrations ...............................................................................................................................................7 
Integration Sets .........................................................................................................................................7 
Synchronous Processing ..........................................................................................................................8 
Asynchronous Processing ........................................................................................................................8 
Technologies Used by Integration Points .................................................................................................8 
Application Messaging ..............................................................................................................................8 
Business Interlinks ....................................................................................................................................8 
Component Interfaces...............................................................................................................................9 
File Layout ................................................................................................................................................9 
Flat File .....................................................................................................................................................9 
Generic .....................................................................................................................................................9 
Service Operation .....................................................................................................................................9 
Staging Table ............................................................................................................................................9 
XML Link .................................................................................................................................................10 
Important Sources of Integration Information .............................................................................................10 

Copyright © 2010, Oracle and/or its affiliates. All rights reserved. 3

PeopleBook Update PeopleSoft Services Repository
April 2012

Introduction
The PeopleSoft Services Repository is a compilation of information about the numerous service endpoints
exposed by Oracle's PeopleSoft applications. Integration Points, also known as EIPs, are the web service
connections that allow PeopleSoft applications to work smoothly with third-party systems and software, as
well as other Oracle applications.

The information within the Services Repository tool, in conjunction with PeopleBooks, help users and
implementation specialists fully explore the integration capabilities of our products.

Developers use the tool to find integrations points between publishing and subscribing product lines, for
example, between PeopleSoft Human Resources and PeopleSoft Financials.

PeopleSoft Services Repository Tool

User Input Menu
The PeopleSoft Services Repository tool is a MS Excel based file that allows the user to create a list of
integration points based on selecting available criteria within the User Input Menu.

User Input Menu criteria selection

4 Copyright © 2010, Oracle and/or its affiliates. All rights reserved.

PeopleSoft User Guide PeopleSoft Services Repository
April 2012

Available Criteria:
• Publishing Product Line. Select the product line that will publish the message between the two
product lines.
• Publishing Release. Select the release number of the publishing product line.
• Subscribing Product Line. Select the product line that will subscribe to the published message
between the two product lines.
• Subscribing Release. Select the release number of the subscribing product line.

Running the Report

Once you have selected the criteria for your report, or list of integration points, click the Run Report button. A
popup window will display which will give you the option to accept the default name of the report or create
your own.

Report name selection box

Once you select your report name, you will be taken directly to the report.

Copyright © 2010, Oracle and/or its affiliates. All rights reserved. 5

PeopleBook Update PeopleSoft Services Repository
April 2012

Services Repository report sample

The report that is created has nine columns of content:

• Product Line – Pub. Displays the selected publishing product line code, such as HCM or CRM.
• Release – Pub. Displays the selected publishing release number.
• Integration Point Name – Pub. Displays the name of the integration point that publishes the message
between the two product lines.
• Technology Type. Displays the name of the integration technology that is used to send the message.
• Product Line – Sub. Displays the selected subscribing product line code.
• Release – Sub. Displays the selected subscribing release number.
• Integration Point Name – Sub. Displays the name of the integration point that subscribes to the
message between the products.
• Technology Type – Sub. Displays the name of the integration technology that is used to receive the
message.
• Description/Comment. Additional information about the specific integration point.

You can create multiple reports, simply select the User Input tab and select new criteria. Each new report
displays in a new tab. The entire tool and reports can be saved to your local drive.
The Delete This Sheet button at the top of the report will delete that specific report only.

Note. Not all services listed per release are supported. For more Information on what services are supported
by Oracle PeopleSoft, please refer to the Oracle Support Policy.

6 Copyright © 2010, Oracle and/or its affiliates. All rights reserved.

PeopleSoft User Guide PeopleSoft Services Repository
April 2012

Integration Concepts in the PeopleSoft System

Integration Points
An integration point is an interface that a system uses to communicate with another PeopleSoft
application or an external application. The integration points that are delivered with the PeopleSoft system
provide generic functionality, so that they can be adapted for many uses. Integration points can be
implemented using different technologies available in the PeopleSoft system, such as Application Messaging,
Component Interfaces, Business Interlinks, XML links, XPI, and Supply Chain Business Modeler.

To communicate with each other, applications need to exchange information through compatible integration
points. Two integration points are compatible when their communication styles complement each other, and
the format of data sent by one application is acceptable to the other. In addition, the communication protocols
and data formats must also be compatible. For instance, data might be passed over HTTP/TCP or by secure
FTP or the data could be in CSV format or XML.

Here is an example. A PeopleSoft Human Resource Management 9.0 system sends data regarding a person
using an XML message. The integration point that sends the message is implemented using Application
Messaging in the PeopleSoft Integration Broker subsystem of the HRMS application. Only one message is
sent, and none is expected in return. The structure of the message is defined by the message object
PERSON_BASIC_SYNC.VERSION_1 in PeopleSoft Application Designer. All message names are followed
by a verb (for example, Notification or One Way) that provides information about the function of the message.
If another application can communicate with the PeopleSoft Human Resource Management 9.0 system
through multiple connectors supported by PeopleSoft Integration Broker and can accept the XML document
defined the message and understand it, then its integration point is compatible with the sending system.

Every integration point is “owned” by at least one application, but can be used by for integration in multiple
applications. Note, however, that sometimes two applications might use the same integration point but
implement it in different ways. Additionally, an integration point can be associated with one or more business
tasks.

Integrations
An integration is a pair of compatible integration points that are known to communicate with each other
without error to produce the desired business result. The PeopleSoft system provides numerous integrations
between both PeopleSoft and non-PeopleSoft applications.

Integration Sets
Integrations can be associated with or used by application groups as integration sets. An integration set is a
logical grouping of integrations that applications use for the same business purpose. For example, the
integration set ADVANCED_SHIPPING_ORDER contains all of the integrations that notify a customer that an
order has shipped. The publishing integration point sets up a service that accepts subscriptions requests and
sends messages. The subscribing integration point then requests subscription to the publisher and
subsequent messages.

Copyright © 2010, Oracle and/or its affiliates. All rights reserved. 7

PeopleBook Update PeopleSoft Services Repository
April 2012

Synchronous Processing
These design patterns are used when synchronous communication between your application and the other
application is required. Because this involves two different applications working together, in each pattern only
one application has the control of the events. It is either your application that controls all of the events or the
other application. The application that has the control of the events is usually the application that has the user
interface. In these patterns the data going across applications is usually low volume and quick response time
is desired. Request/Reply design patterns are characterized by applications that require real-time
synchronous communication between your application and the other application.

Asynchronous Processing
The asynchronous processing design patterns handle either full data replication or incremental updates. Full
data replication is the process used to seed, or initially populate or repopulate, a copy of an entire table onto
a remote database or legacy system. The entire contents of the table are published to all systems that require
a copy of the table. Generally, full data replication occurs with setup tables; that is, relatively static, low
volume tables keyed by setID. The ChartField tables (as in Account, Department, or Product) are examples of
setup tables.

Personal Data within HRMS (300,000 rows in some cases) and the Item Master within ERP (1 million rows in
some cases) are some of the highest volume and dynamic tables that are considered setup tables.
Integration partners may need to replicate many of the setup tables, and some organizations find it beneficial
to maintain these tables centrally and replicate changes to remote databases and legacy systems. Application
Messaging provides the technology for doing this. When you replicate setup data, application development
provides both the publication and subscription processes.

Technologies Used by Integration Points

Integration points use many different technologies to send and receive messages. Each integration
technology has specific characteristics that determine the behavior of the integration point.
The following integration technologies are currently used to implement integration points in the PeopleSoft
system.

Application Messaging

PeopleSoft Application Messaging provides applications within the PeopleSoft product family with the ability
to communicate synchronously or asynchronously with other PeopleSoft and third-party applications. An
application message defines the records and fields to be published or subscribed to. At runtime, XML is built
to represent the message structure and application data, though you can build, publish, and subscribe to
messages without knowledge of XML.

Business Interlinks
PeopleSoft Business Interlinks enable you to perform component-based, real-time integration from the
PeopleSoft system to external systems. PeopleSoft Business Interlinks do this by creating synchronous
transactions that enable PeopleSoft applications to pass exchange data with the external system in real time.
You can use PeopleSoft Business Interlinks to integrate the PeopleSoft system with third-party systems, with
another PeopleSoft application, or with systems on the internet.

8 Copyright © 2010, Oracle and/or its affiliates. All rights reserved.

PeopleSoft User Guide PeopleSoft Services Repository
April 2012

Component Interfaces
A component interface is a set of application programming interfaces (APIs) that you can use to access and
modify PeopleSoft database information using a program instead of the PeopleSoft client. PeopleSoft
Component Interfaces expose a PeopleSoft component (a set of pages grouped for a business purpose) for
synchronous access from another application—such as a PeopleCode, Java, C/C++,or Component Object
Model (COM) application. A PeopleCode program or an external program(Java, C/C++,or COM) can view,
enter, manipulate, and access PeopleSoft component data, business logic, and functionality without being
online.

File Layout
A file layout is a definition (or mapping) of a file to be processed. It identifies where fields are located in file
data. After you create a file layout, you can write PeopleCode programs that ultimately use file layout, either
to read data from or write data to a file. In addition to manipulating transaction data, flat files enable you to
use flat files to use file layouts to move data between your PeopleSoft database and external systems (data
interchange).

Flat File
Flat files are a generic technology capable of reading and writing to a file using a file layout object.

Generic
A generic integration uses an unspecified integration technology, although the subscriber or publisher is
known. A generic integration is a one-way integration that appears for informational purposes only.

Service Operation
Service operations provide applications within the PeopleSoft product family with the ability to communicate
synchronously or asynchronously with other PeopleSoft and third-party applications.
A service operation consists of general information about an operation, such as its name, description, and so
on. It also specifies an operation type, which determines how the operation is to be processed, synchronously
or asynchronously. In addition, it contains routings, which determine the direction, inbound or outbound, of the
service operation. A service operation has one or more handlers, which contain and run the programming
logic for sending or receiving the message, manipulating message content, and so on.

Note. Service operations house the processing logic found in messages, transactions and relationships in
previous PeopleSoft Integration Broker 8.4x versions.

Staging Table
Staging tables are a holding area for data and can function as an integration when one system places data
into a staging table for another system to access.

Copyright © 2010, Oracle and/or its affiliates. All rights reserved. 9

PeopleBook Update PeopleSoft Services Repository
April 2012

XML Link
The XML Linking language enables you to insert elements into XML documents to create a links between
resources.

Important Sources of Integration Information

For more detailed information on PeopleSoft integration technology, managing messaging, building message
schemas, and more, we highly recommend you review the PeopleTools 8.XX: PeopleSoft Integration Broker
PeopleBook.

Valuable PeopleSoft resources:

PeopleSoft Hosted PeopleBooks site

http://docs.oracle.com/cd/E17566_01/epm91pbr0/eng/psbooks/psft_homepage.htm

PeopleSoft Information Portal

http://www.oracle.com/us/products/applications/054275.html

PeopleSoft Business Process Maps

http://docs.oracle.com/cd/E17355_01/hf91bpm0/index.html

PeopleSoft Enterprise Integration Point Maps

http://docs.oracle.com/cd/E18171_01/EIPAPP91/index.html

10 Copyright © 2010, Oracle and/or its affiliates. All rights reserved.