PeopleSoft Integration Broker

Version 1.0

INTEGRATION BROKER GUIDE: Table of Contents

1. Introduction..............................................................................................................................................1 2. Integration Overview................................................................................................................................2 3. Integration Models...................................................................................................................................3 4. Definition..................................................................................................................................................4 5. Prerequisites required before implementing PeopleSoft Integration Broker.............................................6 6. Understanding PeopleSoft Integration Broker..........................................................................................7 7. Architecture..............................................................................................................................................9 5.2 Integration Engine Architecture:..............................................................................................13 8. Steps to Configure IB ............................................................................................................................14 6.1 Configuring the gateway ........................................................................................................14 6.2 Configuring Node ...................................................................................................................17 a. Local Node Setup.........................................................................................................17 I. Local Node: Node Info page..........................................................................................17 II. Local Node: Node Connectors page............................................................................19 b. Remote Node Setup.....................................................................................................20 I. Remote Node: Node Info Page.....................................................................................20 6.3 Configuring Messages............................................................................................................21 6.4 Configuring Queues................................................................................................................23 6.5 Configuring Services...............................................................................................................25 6.6 Configuring Services Operations ...........................................................................................25 A. Adding Handlers..........................................................................................................27 B. Adding Routing Definitions..........................................................................................28 6.7 Configuring Routings...............................................................................................................28 6. Writing Publishing and Subscription People Code.................................................................................30 7. Enhanced Features of Integration Broker in People Tools 8.48 & onwards...........................................35 8. Troubleshooting.....................................................................................................................................54 Publication Process Problems ....................................................................................................54 Publication Contract Is Not Created ............................................................................................54 Publication Contract Is in NEW Status ........................................................................................54 Publication Contract Stays in RETRY Status ..............................................................................54

Publication Contract Is in WORKING Status ...............................................................................54 Publication Contract Is in TIMEOUT Status ................................................................................55 Publication Contract Is in ERROR Status ...................................................................................55 Subscription Process Problems ..................................................................................................55 Subscription Contract Is not Created ..........................................................................................55 Subscription Contract Is in NEW Status ......................................................................................55 Subscription Contract Is in STARTED Status .............................................................................56 Subscription Contract Is in WORKING Status .............................................................................56 Subscription Contract Is in ERROR Status .................................................................................56 Other Possible Problems ............................................................................................................56 9. PS delivered EIP points.........................................................................................................................58 10. Summary and Benefits ........................................................................................................................67

1. Introduction
The Purpose of this document is to walk you through a complicated cycle of Integration Technology using PeopleSoft IB 8.48 and onwards. All the concepts and related definitions and details of individual terminology & concepts are not covered; such details are already available in the People Books online library. Idea in preparing this document is, just by following this document one should at least be able to: Know where to start, How to start and what is required, in order to work on App Messaging. Demonstrate a very simple practical example on how application messaging works. Have a basic understanding of Synchronous and Asynchronous Messages. Tips and tricks needs to be taken care while creating the initial skeleton of the Integration design Trouble shooting techniques. Easy and straightforward testing approaches for inbound and outbound messages. Comparative analysis of Integration technology between PeopleTools 8.48 and PrePeopleTools 8.48

Page 1 of 67

2. Integration Overview
IT management has always been forced to deal with the issue of multiple systems and a lack of communication standards, leading to islands of automation, operating unaware of each other. It is this initial problem that created the world of integration technologies. At the highest level, there are three primary areas in which integration technologies (commonly referred to as middleware), function: people, process and data.

The people layer or user-interface is primarily concerned with the aggregation and presentation of information. This information may take the form of application transactions, analytical reports, or web content; each of these elements being presented in a user-friendly format based on their specific role based privileges. This level of integration is the domain of the PeopleSoft Enterprise Portal. The Portal aggregates business critical transactions and provides relevant context for more accurate, timely, and effective business decisions. The process layer handles the system-to-system communications critical to the operation of any enterprise. This layer is squarely focused on optimizing existing business processes, and enabling new value-added operations through the powerful use of web technology. Although, we rarely see the system-to-system communications, they are far more frequent and complex than the simple web based interfaces we are used to as users. This challenging venue is the domain of the PeopleSoft Integration Broker. The data layer is primarily concerned with the extraction of key information from application databases and disparate data sources. This data is then warehoused for later analysis, typically using an off the shelf business intelligence tool. Our Enterprise Warehouse product suite enables data level archiving, retrieval, and analysis for the precise purpose of gaining insight into the inner workings and performance of your business.

Page 2 of 67

3. Integration Models
Consider for a moment all of the systems which need to communicate and share information: ERP, CRM, SCM, Legacy Applications, and the list goes on and on. In the past, links between these applications were created by hardwiring direct connections between systems. We call this approach, point-to-point integration. The downside to this paradigm is realized when a previously integrated system is updated, or when a new application is added to the environment. The point-to-point model requires each and every connection to be individually and programmatically created. This means that a single addition to the network causes a corresponding, and exponential, development effort.

Conversely, the hub-and-spoke model allows for a new application to integrate once to a hub, and leverage the existing connections to the other systems rather than create new ones. This new paradigm is possible, because each and every system communicates directly to the hub, letting it do the work of translating and routing messages between systems using pre-defined rules and definitions. Another value that the hub-and-spoke paradigm brings is in terms of adaptability. If there is one thing for certain, it is change. Using the Integration Broker, should an application change the way it stores and transmits information, using the hub-and-spoke model, only the logic within the hub is altered. None of the other systems are even aware of the modification, and most importantly, these other systems do not need to be altered in any way due to the change

Page 3 of 67

4. Definition
PeopleSoft Integration Broker facilitates exposing PeopleSoft business logic as services and consuming external web services for PeopleSoft applications to invoke. PeopleSoft Integration Broker also supports synchronous and asynchronous messaging with other PeopleSoft applications and with third-party systems. PeopleSoft Integration Broker uses a variety of communication protocols, while managing message structure, message content, and transport disparities. Scope of IB:
3rd party 1 3rd party 2

3rd party 3

PEOPLESOFT

Middleware 3rd party 4

3rd party 5

Page 4 of 67

Diagram depicting the usage of Integration Broker in real world.

Page 5 of 67

5. Prerequisites required before implementing PeopleSoft Integration Broker

PeopleSoft Integration Broker is installed as a part of PeopleSoft installation. The 2 major components of PeopleSoft IB are: 1. Integration Gateway - The integration gateway is a platform that manages the receipt and delivery of messages passed among systems through PeopleSoft Integration Broker. 2. Integration Engine - The integration engine is an application server process that routes messages to and from PeopleSoft applications as well as transform the structure of messages and translates data according to specifications that you define. Planning the Integration Broker: While planning the integrations to develop and execute, the following factors needs to be considered:
Real-time integrations or scheduled integrations.

-Determine if you business needs are best served with real-time integration or scheduled integrations. Inventory the integrations to develop.

-Determine which systems and applications will participate in each integration. -Consider dependencies on other systems owned by other groups having concurrent releases, and data dependencies within the context of synchronizing data between systems. Generic integrations.

-Is there is any chance of developing an generic integration. Perhaps in the current environment we have 2 systems to integrate but later as we go down the line we may need to integrate one more system to integrate with the current system. So we need to plan accordingly.

Determine which integrations will require synchronous messaging and which ones will require asynchronous messaging.
Prioritize integration development.

-Plan to develop mission critical integrations first, standard integrations next and nice-tohave integrations last. Determine if data will need transformation or translation. Plan on using integration simulation tools.

-Plan on using simulation tools such as PeopleSoft Send Master to simulate integration with external systems that are not under our control. Even when we do control all systems that are being integrated, if we cant get the integration to work using Send

Page 6 of 67

Master, we definitely wont be able to get it working from the external system. Test integrations using Send Master before spending hours debugging a system.

6. Understanding PeopleSoft Integration Broker

Followings are the main driving components of Integration Broker: Integration gateway architecture. Integration engine architecture. Transaction types. Incoming and outgoing message flows.

PeopleSoft Integration Broker is a middleware technology that: Performs asynchronous and synchronous messaging among internal systems and third-party systems. Exposes PeopleSoft business logic as web services to PeopleSoft and third-party systems. Consumes and invokes web services from third-party and PeopleSoft systems.

PeopleSoft Integration Broker enables you to perform these integrations among internal systems and thirdparty integration partners, while managing data structure, data format and transport disparities. Because of its modular design, you can reuse many elements that you develop for integrations. PeopleSoft Integration Broker consists of two subsystems: 1. Integration gateway - The integration gateway resides on a PeopleSoft web server. It is a platform that manages the receipt and delivery of messages passed among systems through PeopleSoft Integration Broker. It supports the leading TCP/IP protocols used in the marketplace today and provides extensible interfaces to develop new connectors for communication with legacy, enterprise resource planning, and internet-based systems. 2. Integration engine - The integration engine is installed on an application server as part of the PeopleSoft application. It runs on the PeopleSoft application server. Its tied closely to the PeopleSoft application, and it sends or receives messages for the application. Rather than communicating directly with other applications, the integration engine sends and receives messages through one or more separately installed integration gateways. The integration engine: Uses a modular architecture, so it can treat gateways as black boxes and communicate with them using standard connectors. Adapts elements of an existing integration to produce a new integration with only minor adjustments. Handles messages containing data in a variety of formats. Formats include PeopleSoft rowset-based message format, and non rowset-based message structures including , XML document object model messages, Simple Object Access Protocol (SOAP) messages, and non-XML files.
Page 7 of 67

Sends and receives messages asynchronously (like email) or synchronously (suspending activity to wait for a response). Applies message transmission type and routing based on specifications that you define in a PeopleSoft Pure Internet Architecture component. By applying application engine transform programs, transforms message structure and translates data content according to specifications that you define in PeopleSoft Pure Internet Architecture components and apply with Extensible Style sheet Language Transformation (XSLT) code or People Code. These specifications can be reused for other integrations.

Handles security features such as authentication, non repudiation, and cookies.

Page 8 of 67

7. Architecture
5.1 The Integration gateway architecture: The Integration Broker is comprised of four key elements: Packaged Connectors, Intelligent Routing, Transformation, and a Development and Monitoring Environment. Packaged Connectors All messages entering or leaving the Integration Broker pass through a single mechanism known as the Gateway. The Gateway is delivered with pre-built connectors to receive and transmit traffic using various standard protocols such as HTTP or JMS. More importantly, PeopleSoft provides an environment for the development of new connectors to legacy systems, ERP applications, and other web based systems. In addition, all PeopleSoft applications are built with integration in mind from the start. Whether you have CRM, HRMS, or another product line, we have pre-built interfaces that enable seamless communication between our applications and also between 3rd party systems. Routing Central to any messaging architecture is routing. Routing ensures that the incoming message is delivered to the right receiving system(s), and that the requesting system has the appropriate security privileges. Integration Broker also understands if the message needs to be sent in real-time (synchronous), or if it is deferrable (asynchronous), and manages the queuing of deferrable messages. The queue can even be set-up to handle message delivery based on pre-defined rules that assign differing priorities to message or system types (e.g. always customer order data messages first) Transformation Transformation is required to translate a message between different systems. This is much like translating a sentence from one language to another. The meaning of a sentence is the same in French or English, but unless some conversion is performed, neither person will understand the message. Similarly, the Integration Broker takes a system message and converts the data from one systems format into anothers. This becomes extremely valuable when you consider the hub-and-spoke model described earlier. With the PeopleSoft integration Broker, once an application has been mapped once, the Broker enables communication to any other system automatically. In the future, as the mapped system changes, there is only one place to modify the mapping, saving time and money. Development and Monitoring Environment Integral to the Integration Broker architecture is a development and monitoring environment. The development environment is used by programmers to map the complex relationships between systems. The developers determine how the broker

Page 9 of 67

should transform and route the messages, taking care to understand the various data schemas, and business process rules that must be managed. In addition, the monitoring environment is a dashboard for the entire messaging process, giving the user a picture of all messages moving in and out of the Broker. From this dashboard, administrators can view original messages, transformed messages, delivery status, or perform higher-level operations such as canceling delivery or resubmitting a message

Page 10 of 67

Below is the graphical representation of the Integration gateway:

Integration gateway is generally used to receive and send messages among integration participant systems. Listening connectors receive incoming messages and deliver the incoming requests to the gateway manager, which is a dispatcher for messages that flow through an integration gateway. The gateway manager determines which target connector to use to properly deliver the messages to their intended recipients. The target connector then delivers the messages to the intended recipients using the recipients preferred protocols.

Page 11 of 67

Frequently used term to be used with Integration Gateway: A. Listening Connectors Listening connectors receive incoming data streams and perform services based on the content of the stream. They are invoked externally by other PeopleSoft systems and third-party systems. B. Target Connectors Target connectors initiate communication with other PeopleSoft systems or third-party systems. A target connector might not receive a response from the target system during each operation, but every transmission requires a low-level acknowledgment. C. Gateway Manager The gateway manager processes every message that flows through an integration gateway and maintains links to the other major integration gateway components, including target connectors, listening connectors, and each of the gateway services. Listening connectors invoke the gateway manager when they receive a request. The gateway manager uses the messaging objects IBRequest and IBResponse to determine how to route each request. The gateway manager uses a number of the gateway services during this stage to perform operations such as message validation. The gateway manager then invokes the appropriate target connector based on the content of the message object and waits for a reply from the target connector. When the reply is received, the gateway manager forwards the reply to the calling listening connector. If an error occurs, the gateway manager uses the error handling service and works with the service to prepare an error reply for the listening connector.

Page 12 of 67

5.2 Integration Engine Architecture:

Below is the graphical representation of the Integration gateway:

Integration engine architecture

Page 13 of 67

The integration engine uses a variety of People Tools elements to create, implement, manage, and enhance integrations. Its modular architecture separates integration development activities from administrative activities. The integration engine is a combination of PeopleSoft Application Designer definitions, PeopleSoft Pure Internet Architecture definitions, PeopleCode, and XSLT code, along with the underlying mechanisms that tie all these elements together. The underlying mechanisms include the request handlers that process both inbound and outbound messages according to the specifications in the development and administrative elements.

8. Steps to Configure IB

6.1 Configuring the gateway

Navigation: Peopletools->Integration Broker-> Configuration->Gateways To define and configure a gateway:

1. Select People Tools, Integration Broker, Configuration, Gateways.

The Gateways search page appears. Do one of the following: Click Search, and select an existing gateway definition. The Gateways page appears, displaying the gateway definition. Add a new value, enter an integration gateway ID, and click Add. The Gateways page appears. 2. Enter the gateway URL for the selected gateways PeopleSoft listening connector. Specify the URL with the format: http://machinename:port/PSIGW/PeopleSoftListeningConnector In this case, machinename:port is the machine name and port, host name, or IP address of the web server hosting the gateway. The integration gateway URL is case sensitive. The gateway uses the PeopleSoft listening connector to receive service operations from an integration engine node or a remote gateway. 3. To load the delivered target connectors, click the Load Gateway Connectors button. You can load the delivered target connectors at this point, or at a later time. 4. Save the gateway definition.

Page 14 of 67

nnector

http://machinename:port/PSIGW/PeopleSoftListeningCo

5. Click the Gateway Setup Properties link to configure additional gateway settings and connector properties. The default user ID is administrator and the default password is password. Check the Change Password box to change the default password.

Page 15 of 67

Ping node
If the ping is successful a PeopleSoft page appears that displays the PeopleTools release and a status of Active.

Page 16 of 67

App Server Enter the machine name and BEA Jolt port number of the default application server URL(Application Server to use if no valid target node can be determined. URL) To determine the Jolt port of the application server, check the JOLTListener section in the psappsrv.cfg file. The file is located in <PS_HOME>\appserv\<DOMAIN_NAME>. Web Server URL Message Node Name Enter the machine name and BEA jolt port number of the default application server to use if no valid target node can be determined. Enter name of the PeopleSoft node with which the integration gateway is to communicate. Enter the user ID that you defined when you created the application server domain. Enter the UserPswd that you defined when you created the application server domain. PeopleSoft Integration Broker will automatically encrypt this password entry. Tools Release Enter PeopleTools version number installed on the application server.

User ID Password

6.2 Configuring Node You configure a node using the Node Definitions component, which consists of several pages. a. Local Node Setup When discussing nodes, it's important to consider the concepts of local and remote nodes. Whether a node is local or remote is determined by which database the node is defined in. If you're signed on to HCM which has node PSFT_HR defined, then node PSFT_HR is local. Later, if you're signed on to FIN, node PSFT_EP is remote. Therefore local and remote are relative terms. I.
Navigation Description

Local Node: Node Info page

PeopleTools > Integration Broker > Integration Setup > Nodes This section describes how to configure local nodes.

Here HRMS is the source system, in which PSFT_HR is the Default Local Node, which we are taking as Local Node for the integration. The local node in the source system will be the remote node in the target system and vice versa. Default Local node cant be changed at the user level, which is system defined one. Check the options in the Node Info tab for; Active Node Local node In the Connector tab page, give the Gateway ID as LOCAL and connector ID as PSFTTARGET. Save the Node

Page 17 of 67

Description Node Type

Authentication Option

Default Local Node

Enter a descriptive name for the node. Select from: PIA: Designates the node as a PeopleSoft database that uses PeopleSoft Integration Broker. This is the default for a new node. External: Designates the node as an entity that doesnt use PeopleSoft Integration Broker. ICType: A portal-specific setting that PeopleSoft Integration Broker doesnt use. Select from: Certificate: The current node uses a digital certificate to sign the messages it sends, and expects messages it receives to be signed by a complementary digital certificate. Password: Two new fields appear: Password and Confirm Password Indicates whether the current node represents the database to which you are assigned. PeopleSoft Integration Broker is delivered with one node predefined as the default local node. You can't change which node is the default local node, but you can use the Rename Node button to rename the default local node to more appropriately reflect your application or system. Indicates that the current node is either a portal node or the default local node.

Local Node Active Node

Select to make the current node definition active, so it can be used by PeopleSoft Integration Broker. Non-Repudiation Select to activate non repudiation for the current node. Segment Aware Check the box to configure the node to handle message segments. Password Confirm Password Displays when the Authentication Option is Password. Enter the node password. Reenter the node password you entered in the Password field.

Page 18 of 67

Default User ID Hub Node Master Node Company ID IB Throttle Threshold

On inbound integrations, this is the user ID that the sender must specify to invoke a service operation, unless you have set up an external user ID for this purpose. Select the name of a node that will serve as a gatekeeper for the current node. You can select any existing PeopleSoft Pure Internet Architecture node for this purpose. This field is for information only. If the current node is used as a hub, you can indicate the target node with which its associated. If the current node represents a subordinate database, you can indicate the primary database. Enter the name of the company or organization associated with the current node. Set this parameter on a remote node definition to limit the number of requests sent to the node per dispatch. The setting is in minutes. For slow-processing systems, this option can help to prevent saturating the targeting system with requests. This parameter is used only for asynchronous integrations. Select an image from the system database. Any application that uses images can use the selected image to represent the current node.

Image Name

II.
Navigation

Local Node: Node Connectors page

PeopleTools > Integration Broker > Integration Setup > Nodes Use this page to specify how the local default node should send messages to the current node, including which gateway, which target connector registered with that gateway, and which property settings for that connector should be used.

Description

Field Gateway ID:

Description When the default local node sends a message to any other node, the message first goes to the default local node's local gateway through its PeopleSoft listening connector, regardless of the gateway ID you select here. This field specifies the target connector appropriate to the communication method preferred by the current node. If the node is a PeopleSoft application with Integration Broker installed, select PSFTTARGET.

Value LOCAL

Connector ID:

PSFTTARGET

Page 19 of 67

b. Remote Node Setup I.

Navigation Description

Remote Node: Node Info Page

PeopleTools > Integration Broker > Integration Setup > Nodes This section describes how to configure remote nodes.

Here FIN is the Target system, in which PSFT_EP is the Remote Node. Check the options in the Node Info tab for; Active Node Uncheck the options in the Node Info tab for; Default local node Local node In the Connector tab page, Give the Gateway ID as LOCAL and connector ID as PSFTTARGET Save the Node

Page 20 of 67

6.3 Configuring Messages

Either a new message can be created or existing message can be modified from Message Builder page.
Navigation Description PeopleTools > Integration Broker > Integration Setup > Messages This section describes how to configure messages.

To add a message definition: 1. Select PeopleTools, Integration Broker, Integration Setup, Messages. 2. Select the Add New Value tab. 3. In the Message Name field, enter a name for the message. 4. In the Message. Version field, enter a version for the message. Accepted formats for the message version include: Version_1. V1. 5. Click the Add button. The Messages - Message Definition page appears. 6. In the Message Type group box, select the message type. Values are: Rowset-based Nonrowset-based (default) Container 7. (Optional) In the Alias field, enter the name that the external system is expecting, if different from the value in the Message Name field.
Page 21 of 67

This field appears only when you are defining nonrowset-based or container messages. 8. (Optional) Select the Message Parts check box if the message will be used as a message part in a container message definition. 9. (Optional) In the Description field, enter a description for the definition. 10. (Optional) From the Owner ID dropdown list box, select an owner for the definition. The owner ID helps to determine the application team that last made a change to the definition. 11. (Optional) In the Comment field, enter any pertinent comments about the definition. 12. The next step depends on the type of message definition that you are creating: Rowset-Based Message. You must add a root record to the definition before you can save it. Nonrowset-Based Message. The message definition is complete and you can click the Save button to save the changes. You can now add an XML message schema to the definition. Container Message. You must add at least one message part to the definition before you can save the changes.

Insert a root record into a rowset-based message definition using the Add a New Record page To insert a root record into a definition: 1. On the MessagesMessage Definitions page, click the Add Record to Root link. The Add New Record page appears. 2. In the New Record Name field, enter the name of the record to add, or click the Lookup button to search for and select one. 3. Click the OK button. The root record appears in the tree structure. Click the plus button to expand the tree and view fields that are associated with the record.

Page 22 of 67

6.4 Configuring Queues Service operations queues are used to queue service operations for processing

Navigation Description

PeopleTools > Integration Broker > Integration Setup > QUEUES This section describes how to configure queues

Either a new Queue can be created or existing Queue can be made Active. New Queue

Page 23 of 67

Location Queue

Queue Name Archive Unordered

Enter the name of the queue. Select to archive service operation instances that are assigned to the queue. By default, archiving is enabled. Select to enable field partioning and to process service operations unordered. By default, the check box is cleared and inbound service operations that are assigned to a queue are processed one at a time sequentially in the order that they are sent.

Description Queue Status

Enter a description for the queue. Values are: Run: (default) Service operations that are assigned to this queue are received and processed normally.
Page 24 of 67

Pause: Service operations are received but not processed until the status is reset to Run.. Object Owner ID Comments From the dropdown list box, select the object owner. Use this area to enter comments about the definition.

Operations Assigned This read-only section lists all service operations that are assigned to the queue. to Queue Include Add Field Select the Include check box next to a field name to include the field in queue partitioning. Click to view and select partitioning fields.

6.5 Configuring Services

Navigation Description

PeopleTools > Integration Broker > Integration Setup > Services This section describes how to configure Services

1. 2. 3. 4. 5. 6. 7. 8.

Open the Services page. In the Description field, enter a description for the service. (Optional.) In the Comments field, enter comments about the service or the service. (Optional.) In the Service Alias field, enter an alias name for the service. (Optional.) From the Object Owner ID dropdown list box, select the owner of the service. Enter a namespace URI for the service. Enter the service operation and operation type and press add to include the service operation You can also define service operation from service page by pressing the add button.

6.6 Configuring Services Operations

Page 25 of 67

Navigation Description

PeopleTools > Integration Broker > Integration Setup > Service operations This section describes how to configure Service operations

A service operation definition 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. There are four service operation types: Asynchronous Request/Response The sending system invokes a service operation asynchronously and processes the response from the receiving system asynchronously. Unlike a synchronous operation type, the response is not processed on the same thread as the response, and it is processed sometime in the future. The sending system's asynchronous process sends a synchronous request to a remote system. The sending asynchronous system expects the receiving system to send a synchronous response back. The sending asynchronous system transforms the response and puts it back in the queue for asynchronous consumption. Asynchronous One Way Synchronous The service operation is queued and sent in near real-time. Processing on the sending system continues without a response from the receiving system. The service operation is provided in real-time. Processing on the sending system does not continue until it receives a response from the receiving system.

Asynchronous to Synchronous

1. Click the Add Service Operation tab. 2. In the Service field, enter the service name to which the new operation will belong or click the Lookup button to search for a service name. 3. In the Service Operation field, enter a name for the service operation. 4. From the Operation Type drop-down list box, select an operation type. Values are: Asynchronous One Way Synchronous Asynch Request/Response Asynch to Synch 5. Click the Add button.

Page 26 of 67

The Service Operations component includes three pages: General Tab Handlers Tab Routings Tab Features general-service and default-service operation information. Provides summary information about handlers that have been added to an operation. Service operation handlers contain the programming logic for sending and receiving service operations and their contained messages, and for manipulating content. Provides summary information about service operations routings. Routing definition determine the directioninbound, outbound or hubof service operations

A. Adding Handlers To add handlers to a service operation: 1. On the Service Operations component, click the Handlers tab. The Handlers page appears. 2. In the Handlers section, enter a handler name in the Name field. Note that for OnRequest, and OnRoute handlers, you need not enter a name. The system adds a handler name after you provide the handler details. 3. From the Type dropdown list box, select the handler type. The service operation type determines the handler types that are available to choose. 4. From the Implementation dropdown list box, select the method to use to implement the handler. The service operation type determines the handler types that are available to choose. 5. From the Status dropdown list box, select a status for the handler. Values are: Active. Select to make the handler active. Inactive. Select to make the handler inactive.

Page 27 of 67

B.

Adding Routing Definitions 1. On the Service Operations component, click the Routings tab. The Routings page appears. 2. In the Routing Name field, enter a name for the routing. 3. Click the Add button.

6.7 Configuring Routings

Navigation Description

PeopleTools > Integration Broker > Integration Setup > Routings This section describes how to configure Routings

Page 28 of 67

Routing Name Indicates the name of the routing definition. This name is specified when you add a routing definition to the system. Service Operation Active System Generated Version Description Comments Sender Node Receiving Node Routing Type Enter the name of the service operation that will use the routing. If you access the Routings component from the Service Operations-Routing tab, PeopleSoft Integration Broker automatically populates this information. (Optional.) Check the box to activate the routing. By default, new routing definitions are active. If any of the referenced nodes are inactive, you cannot activate the routing. When selected, indicates that the PeopleSoft system generated the routing definition. Indicates the version of the service operation selected. Description of the routing definition. (Optional.) Enter comments about the routing definition. Enter the name of the sending node. Enter the name of the receiving node. Indicates the service operation type. PeopleSoft Integration Broker automatically populates this information when you select the service operation.

Page 29 of 67

6. Writing Publishing and Subscription People Code

a. Publishing Sync Message Write the following code for the SavePostChange of the Main Record Field as shown below.

Whenever the component is saved, the SavePostChange code is triggered:

&request.SyncRequest() - This code publishes the message with the data in the current rowset to
the app messaging services. &response is nothing but the acknowledgment returned by the Target application subscription code.

b. Publishing ASync Message

&MSG.Publish(); - This is the code to publish the Data in the form of a Rowset

Page 30 of 67

c. Sync Subscription Subscription for Sync message is written on the OnRequest Event of the Message as shown below.

d. Async Subscription:

Page 31 of 67

e. Message Monitor-To view the inbound and outbound messages:

Add a new row of data on the main Components and save the components. Check the message monitor for the first time. Message Monitor gives us the current state of all the messages that were published/subscribed.

We can select the Publishing Node to filter the results as shown above. The Overview page shows us the list of all the message channels along with the counts of instances for each status on the page. You can click on the link for a given status to find out the further details as shown below:

Depending on the status you can opt for canceling the message and can be resubmitted once the problem is corrected. This can be decided after looking into the Details to find the various Errors that occurred.

Page 32 of 67

Look for the Message Errors

Page 33 of 67

The XML viewer shows the XML Content that the server publishes. This is the actual way the data is published to the external Application using the XML tags.

On the Main page of the Monitor Once the message is published, the status changes to Done as shown below for a give message Channel.

Once you see the status of your message as Done, it means that the message has been successfully been posted and subscribed. Now you can go to the Duplicate pages on the PIA to check if the new rows are inserted here also. If the PeopleCode to insert the rows using the RowSet is correct, you will find the new rows existing here also.
Page 34 of 67

7. Enhanced Features of Integration Broker in People Tools 8.48 & onwards

Below is a description of the related message objects between 8.4X and 8.48. People Tools 8.4x Objects Node Channel Message Node transactions and relationships Service Message and Subscription People Code People Tools 8.48 / 8.49 Object Node Queue Message Service Operations, Service Operation Versions, and Routings Application classes and service operation handlers

Below is the comparative study of Intergration Broker usage between People Tools 8.48 onwards and pre 8.48.

a. Permission list:
Pre-8.48: Channels can be added to permission list which specifies who can monitor a particular channel, this should be a good default to pick up as most likely this permission list was setup explicitly for IB. In 8.48: These values can be changed using Service Configuration PIA page to assign the service to a different permission list, also can services belonging to multiple permission lists. b. Default Namespace: Pre-8.48: None In 8.48: This value can be changed using Service Configuration PIA and be able to assign each service to a different namespace.

c.

Transactions and Properties tabs are missing from the Portal Node Definitions.

Page 35 of 67

The navigation is: PeopleTools Integration Broker Node Definitions

Pre-8.48 version

The navigation in 8.48 PeopleTools is: PeopleTools Integration Broker Integration Setup Nodes

PeopleTools 8.48

d. Pre 8.48:
Properties hyperlink on the gateways page directs to the Gateway Properties file page.
Page 36 of 67

In 8.48: When clicked on the Gateway Setup Properties hyperlink on the Gateways page, a new page PeopleSoft Node Configuration appears. The Advanced Properties Link on PeopleSoft Node Configuration page directs to the Gateway Properties file page. The navigation is: PeopleTools Integration Broker Gateways

Gateways page in Pre 8.48 Version

The navigation is:

Page 37 of 67

PeopleTools Integration Broker Configuration Gateways

Gateways page in PeopleTools 8.48

PeopleSoft Node Configuration Page in PeopleTools 8.48

e. Message Creation: Pre 8.48: Message definitions can be created only in the Application Designer. There are two types of messages:

Rowset-based messages

For hierarchical data based on PeopleSoft records, create a message definition by assembling, organizing them into a hierarchy, and from those records to include in the message. The result is a rowset that doesnt match to and existing rowset structure in the application. Use the PeopleCode Rowset and Message classes to generate, send, receive, and process these messages.

Page 38 of 67

 Non- Rowset-based messages

These messages can have virtually any structure and content. You create a message definition, but you do not insert any records. The message definition serves as a placeholder for the actual message. Use the PeopleCode XmlDoc and Message classes to generate, send, receive and process these messages. If youre handling Simple Object Access Protocol (SOAP) compliant data, you can also use the SoapDoc class to generate and process these messages. For asynchronous integrations, define a single message. For synchronous integrations, define two messages: one for the request and one for the response

In 8.48: Message definitions can be created in the Pure Internet Architecture. Messages do not contain any processing logic. All processing logic is defined in service operations, using service operation handlers. Four types of messages are available: Rowset-based For hierarchical data that is based on PeopleSoft records, you create a message definition by assembling records, organizing them into a hierarchy, and selecting fields messages from those records to include in the message. The result is a rowset that doesnt need to match an existing rowset structure in the application. Use the PeopleCode Rowset and operation classes to generate, send, receive, and process these messages. Nonrowsetbased messages These messages can have virtually any structure and content. You create a message definition, but you do not insert any records. The message definition serves as a placeholder for the actual message. Use the PeopleCode XmlDoc and operation classes to generate, send, receive, and process these messages. If youre handling Simple Object Access Protocol (SOAP) compliant data, you can also use the SoapDoc class to generate and process these messages. A container message is a nonrowset-based message that holds one or more part messages.A container message must contain all rowset-based messages or all nonrowset-based message parts.

Container messages

Message parts Message parts are rowset-based messages or nonrowset-based messages that you designate as a part message, to be used in a container message. f. Services-Oriented Architecture Overview

PeopleTools 8.48: New feature It features a services-oriented architecture for integrations. Users create services and service operations that contain message, routing information and Processing logic. Processing logic is created using application classes and then the logic is associated to service operations using PeopleCode handlers. Users then use wizard-driven pages for generating, providing and consuming WSDL with integration partners. The transport mechanism for services and service operations is a message container. g. Running and Pausing Queues in the Service Operations Monitor Pre 8.48: If you create new message channels, you must grant users access to them to view or edit channel information, as well as the messages contained within them. Moreover, granting security access to new message channels is required to see transaction information in the Integration Broker Monitor. Users can view messages only in channels to which they have read access. All edit actions require write access. In 8.48: All Integration Broker security is now based at the service operation Level. Queue Security, formerly channel security, has been eliminated so the Queue Status Component will allow any user to run or pause queues.

Page 39 of 67

h. PSADMIN Settings The following PSADMIN settings have been removed: Handler Status Check Count. Tuxedo Queue Status Check Count. The system now performs the processing for these items internally. i. Enabling the Performance Statistics Feature

PeopleTools 8.48: New feature Use the Monitor Setup Options page in the Service Operations Monitor to enable the Performance Statistics feature. The Monitor Setup Options page features an IB Profile Status. On check box; select it to enable the feature.

The navigation is: PeopleTools Integration Broker Service Operations Monitor Administration Monitor Setup Options

Check box to enable Performance Statistics feature in PeopleTools 8.48

In previous releases you enabled this feature in PSADMIN. j. Segment-Aware Target Connectors

The following target connectors delivered by PeopleSoft are now segment-aware and can be used when sending message segments to integration partners: PeopleSoft target connector. HTTP target connector. FTP target connector. Simple File target connector. k. HTTP Target Connector

PeopleSoft has made the following enhancements to the HTTP target connector: The connector features a new property call SOAPUpContent that wraps outbound message content in SOAP format. This connector is also now segment-aware. To configure a node to handle segmented messages:

Page 40 of 67

1. 2. 3. 4. 5.

Select People Tools, Integration Broker, Integration Setup, Node Definitions. Select a node with which to work and click OK. The Node Definitions page appears. Select the Segment Aware box. Click the Save button.

The navigation is: PeopleTools Integration Broker Integration Setup Nodes Node Definitions.

Segment aware check box in Node definitions in PeopleTools 8.48

l.

Integration Gateway Enhancements: Jolt Session Pooling

PeopleTools 8.48: New feature The integration gateway maintains a pool of Jolt sessions to handle requests between itself and the integration engine. The integration gateway accesses a Jolt session from the pool, uses it for the connection, and then returns the session to the pool once it receives the response from the integration engine. The number of sessions to maintain in the session pool is defined in the integration gateway.properties file using the following property: ig.connection Set this property equal to the maximum number of sessions to maintain in the pool. The default value is 10. m. Integration Broker Handler Tester The Integration Broker Handler Tester replaces the Integration Broker Event Tester in PeopleTools 8.48. The handler Tester allows developers to test service operation handlers.Using this feature requires no setup of a receiving database and no publish and subscribe server processes configured and booted on the application server.Integration Broker Handler Tester executes all of the PeopleCode on your server with full debugging capabilities without affecting other developers.

Page 41 of 67

The navigation is: PeopleTools Integration Broker Service Utilities Handler Tester

Integration Broker Handler Tester in PeopleTools 8.48

n. Platforms Supported PeopleTools 8.48: New feature The following new platforms are supported for PeopleTools 8.48. Microsoft Windows 2003 Server HP-UX 11.23 Itanium 64-bit RHEL 3.0 (Red Hat Linux)

o. iWay SOAPSwitch Enhancements PeopleTools 8.48: New feature PeopleSoft provides you with the ability to create inbound and outbound integrations with enterprise resource planning (ERP) systems. These integrations are accomplished using a combination of PeopleSoft Integration Broker and adapters included in a third-party tool, iWay SOAPswitch. IWay SOAPswitch is an installation option during the PeopleTools installation. iWay SOAPswitch version 5.5.3.5 is an installation option provided with PeopleTools 8.48. p. JMS Provider Password The following parameter has been deprecated and removed from the integrationGateway.properties file: ig.jms.JMSTargetConnector.JMSProvider.Password q. Integration PeopleCode Pre 8.48: Messaging logic was attached to individual messages.

Page 42 of 67

In 8.48: With the new services-oriented architecture, users now extend a set of delivered application classes to create messaging logic. Instead of the logic getting attached to messages, it gets associated to handlers. Handlers are then defined on a service operation. In addition, there is a new object called IntBroker. Many of the methods and functions of the Message object from previous releases have been moved to the IntBroker object or deprecated. r. Provide/Consume Web Services

PeopleTools 8.48: New feature PeopleTools 8.48 features a Provide Services wizard and a Consume Services wizard. The Provide Services wizard enables you to generate WSDL documents from Integration Broker metadata to provide to integration partners. You can export WSDL to the Integration Broker WSDL repository, WSIL repositories and UDDI repositories. A WSDL preview feature enables you to copy and paste generated WSDL to file as well. The navigation is: PeopleTools Integration Broker Web Services Provide Web Service

Provide Web Service Wizard in PeopleTools 8.48

The Consume Services wizard enables you to import WSDL from PeopleSoft and external sources. External sources include WSIL repositories and UDDI repositories. The wizard also enables you to import WSDL from legacy PeopleTools 8.4x systems.

Page 43 of 67

The navigation is: PeopleTools Integration Broker Web Services Consume Web Service

Consume Web Service Wizard in PeopleTools 8.48

s.

Service Operations Monitor

The Integration Broker Monitor has been renamed the Services Operations Monitor and modified to monitor services and services operations. There are many field name changes and several new options for monitoring integrations, including the ability to cleanup segment data. The component has a different format and is now broken into Monitoring and Administration Sub components. The navigation is: PeopleTools Integration Broker Service Operations Monitor

Page 44 of 67

Service Operation Monitor Broken into Monitoring and Administration Components

t.

Service Operation Types:

Service operation types determine the type of message processing. There are four service operation types: Asynchronous Request/Response The sending system invokes a service operation asynchronously and processes the response from the receiving system asynchronously. Unlike a synchronous operation type, the response is not processed on the same thread as the response, and it is processed sometime in the future. The sending system's asynchronous process sends a synchronous request to a remote system. The sending asynchronous system expects the receiving system to send a synchronous response back. The sending asynchronous system transforms the response and puts it back in the queue for asynchronous consumption. Asynchronous One Way Synchronous The service operation is queued and sent in near real-time. Processing on the sending system continues without a response from the receiving system. The service operation is provided in real-time. Processing on the sending system does not continue until it receives a response from the receiving system.

Asynchronous to Synchronous

u. Transaction IDs Replace Publication IDs Pre 8.48: Message node, channel name and pub ID were used in combination to create a unique ID for the transaction. In 8.48: In this PeopleTools release, transaction IDs replaces publication IDs (pub IDs) from previous PeopleTools 8.4x releases. PeopleSoft has replaced that combination with a transaction ID that uniquely identifies a transaction. The application server assigns a unique transaction ID to each inbound and outbound transaction. v. Creating BPEL Process-Based Services

PeopleTools 8.48 supports integrations with BPEL process-based services. w. Creating Component Interface-Based Services PeopleTools 8.48 supports creating services from PeopleSoft component interface records and their corresponding methods. x. Introspection and Deployment Validation

PeopleTools 8.48: New feature The Introspection and Deployment Validation component enables you to introspect other PeopleTools 8.48 nodes and create point-to-point routings. Introspection can create point-to point routings on the local node when the service operation name and version name match exactly. The navigation is: PeopleTools Integration Broker Integration Setup Service Operations

Page 45 of 67

Introspection Hyperlink on Service Operations Page

Introspection and Deployment validation Page in 8.48

y.

Integration Metadata Backport Utility

PeopleTools 8.48: New feature The Integration Metadata Backport utility enables you to backport a limited amount of PeopleTools 8.48 integration for use with prior PeopleTools 8.4x systems. The Backport Metadata utility clones a PeopleTools 8.48 Application Designer project that you specify to a project that you can use on prior PeopleTools 8.4x systems The Metadata Backport utility backports PeopleTools 8.48 queues to channels used in previous PeopleTools 8.4x releases, and also backports PeopleTools 8.48 handlers to integration PeopleCode constructs used in previous PeopleTools 8.4x releases. The navigation is: PeopleTools Integration Broker Service Utilities Metadata Backport

Page 46 of 67

The Metadata Backport Component in 8.48

z.

External User ID and External Password

PeopleTools 8.48: New feature The Node Definitions page displays new External User ID and External Password fields when enabling WS-Security on external nodes. The navigation is: PeopleTools Integration Broker Integration Setup Nodes Node Definitions.

Node Definitions page in 8.48.

aa. Services Schema Validation PeopleTools 8.48: New feature The Services Schema Validation component allows you to enable schema validation for individual schemas within a service. It also enables you to build and/or update service operation schemas. The navigation is: PeopleTools Integration Broker Service Utilities Service Schema Validation

Page 47 of 67

Service Schema Validation component in 8.48

bb. Container Messages and Message Parts PeopleTools 8.48: New feature The concept of container messages and message parts has been introduced for this release. You can now create container messages and add one or more message parts to the container message. Container messages are always nonrowset-based messages. This enables you to eliminate sending PSCAMA data to integration partners. Message parts you include in a container message may be rowset-based or nonrowset based. The message parts you include in a container must either be all rowset-based message part or all nonrowset-based message parts; you cannot mix rowset-based message parts and nonrowset-based message parts in a container message. cc. IB Throttle Threshold PeopleTools 8.48: New feature The IB Throttle Threshold field enables you to enter a value to limit the number of requests sent to the node per dispatch. This is helpful if an integration partner has a slow-processing system that can process only X number of requests a minute, you can keep from saturating the target system.

Page 48 of 67

The navigation is PeopleTools Integration Broker Integration Setup Nodes

IB Throttle Threshold field on Node Definitions page.

dd. Page-Based Message and Message Queue Management PeopleTools 8.48: New feature Beginning with this PeopleTools release you now create and manage messages and queues (formerly message channels) in the PeopleSoft Pure Internet Architecture. Create messages using the Message Builder component. Create queues using the Queue Definitions page. The navigation is: PeopleTools Integration Broker Integration Setup Messages

Message Definition Page in 8.48

Page 49 of 67

The navigation is: PeopleTools Integration Broker Integration Setup Queues

Queue Definitions Page in 8.48

ee. WS-Addressing PeopleSoft Integration Broker adds a unique transaction ID in a web services addressing (WS-Addressing) SOAP header on outgoing messages. When a third-party processes the message it will send a response with the same WS-addressing header. WS-Addressing is handled on the integration gateway. ff. WS-Security PeopleTools 8.48: New feature PeopleTools 8.48 implements web service security (WS-Security) for inbound and outbound integrations. For outbound processing, PeopleSoft Integration Broker generates a WS-Security username token, which may or may not include a password. For inbound processing, PeopleSoft Integration Broker understands WS-Security username token, including user ID only, as well as user ID and password. gg. Default User ID PeopleTools 8.48: New feature The Node Definitions page features a new Default User ID field that is used web services security. If a web service request comes into the system without a user ID specified, the system checks the default user ID specified. If that user ID has clearance in the PeopleSoft system, then PeopleSoft honors the request. The navigation is: PeopleTools Integration Broker Integration Setup Nodes

Page 50 of 67

Default User ID field on Node Definitions Page

hh. WSIL URL The Node Definition page features a WSIL URL field used in conjunction with introspection and deployment validation on external nodes. ii. Exception Handling for Synchronous Message Processing

PeopleTools 8.48: New feature If an outbound synchronous request fails you can throw a framework exception leading to a message box error and subsequent component roll back of the transaction. This type of exception handling applies to outbound synchronous requests only, including outbound multi-threaded synchronous requests. For example, if 10 synchronous requests are performed in parallel (threaded sync request), you have the option to select the User Exception check box on the routing definition for the service operation. When the User Exception check box is select, if any of the synchronous requests error, the component is not rolled back. You can check each synchronous request to determine if there is an error and actually read the associated error message. You can then throw an exception or go on to process the next synchronous request in the array. jj. AS2 Listening and Target Connectors

PeopleTools 8.48: New feature The AS2 listening connector and target connector implement correlation IDs in Message Disposition Notifications (MDNs). This enhancement applies to asynchronous messages only. kk. PSADMIN Settings The following PSADMIN settings have been removed: Handler Status Check Count. Tuxedo Queue Status Check Count. The system now performs the processing for these items internally. ll. Generate SOAP Template

PeopleTools 8.48: New feature The Generate SOAP template utility enables you to create a SOAP template for any service for which WDSL has been generated. This SOAP template can then be used in the Handler Tester, Transformation Tester or Send Master to test SOAP messages.
Page 51 of 67

The navigation is: PeopleTools Integration Broker Service Utilities Generate SOAP Template

Generate SOAP Template page

mm.

Deleting Duplicate Routing Definitions

Application upgrades and the PeopleSoft Application Designer project copy process can cause duplicate routings in the PeopleSoft system. Effective with the PeopleTools 8.48.06 product patch, the Service Administration - Routings page now features a Delete Duplicate Routings section that enables you to search for duplicate routings in the system and delete them. The navigation is: PeopleTools Integration Broker Service Utilities Service Administration

Page 52 of 67

Routings Tab in Service Administration Page

nn. Service operations and routings replace transactions and relationships from previous PeopleSoft Integration broker 8.4x versions. oo. Starting from 8.48 an inbound service operation can be invoked as a particular user, previously it was just one user that is configured in integrationGateway.properties. As pre-8.48 requests do not have this authentication information set a default user for the service operation which will be used.

Page 53 of 67

8. Troubleshooting
Publication Process Problems Possible publication process problems include:

Publication contract is not created. Publication contract is in NEW status. Publication contract stays in RETRY status. Publication contract is in WORKING status. Publication contract is in TIMEOUT status. Publication contract is in ERROR status.

Publication Contract Is Not Created

Possible causes are:

No publication PeopleCode exists. Publication PeopleCode is incorrect. No outbound routings exists for the service operation.

Publication Contract Is in NEW Status

Possible causes are:

Sending queue is paused. Publication Dispatcher crashed or was brought down. Sending node is paused. Previous service operation had a status of Retry, Error, or Timeout. Sending domain is not active. After an unsuccessful ping, a row may be added to the table PSNODESDOWN; which will hold up the message queue; query the table PSNODESDOWN.

Publication Contract Stays in RETRY Status

Possible causes are:

The remote node cannot be pinged successfully; the publication contract will be processed when the remote node comes back up. No publication handler is available, either because it crashed or it was brought down. Receiving Node URL is incorrect in integrationGateway.properties file.

Publication Contract Is in WORKING Status

Possible causes are:

The publication handler processing the contract is on another machine and either the machine or the domain is down. Processing should continue when the pub/sub system on the other machine comes back up. Single threading on the application server is slowing processing.
Page 54 of 67

Publication Contract Is in TIMEOUT Status

Possible causes are:

An exception occurred on the target application server (look in APPSRV.LOG file for details); verify that: The reply is incorrectly routed; check Gateway for correct machine address of target node. Bad XML syntax.

Publication Contract Is in ERROR Status

Possible causes are:

Receiving node user profile not authorized to service operation. Inbound routing is not set up on the receiving system. Service operation is not active on the receiving system. Service operation has not been granted security access on the receiving system. The source node is not defined in the target database. Handler PeopleCode is bad. Remote application server is down. Receiving Node is not defined in the integrationGateway.properties file. Receiving PeopleSoft node has not been added to single signon. Service operation version on target is not active.

Subscription Process Problems

Possible subscription process problems include:

Subscription contract is not created. Subscription contract is in NEW status. Subscription contract is in STARTED status. Subscription contract is in WORKING status. Subscription contract is in ERROR status. Subscription contract is in EDIT status.

Subscription Contract Is not Created

Possible causes are:

No handler exists for the service operation. Service operation handler is missing method. Queue routing rules not set up properly.

Subscription Contract Is in NEW Status

Possible causes are:

Application Server down. Pub/Sub processes not configured on Application Server domain. The Subscription Dispatcher has crashed or has been brought down. Receiving queue is paused.

Page 55 of 67

Receiving node is paused. Previous service operation had errors or timed out. No row was inserted into PSAPMSGSUBPRCID, To insert a row enter the following SQL statement in your Query tool use the following statement: insert into PSAPMSGSUBPRCID values(0)

Subscription Contract Is in STARTED Status

Possible causes are:

Subscription Handler is down. Target component is not valid.

Subscription Contract Is in WORKING Status

Possible causes are: Subscription Handler crashed while processing message.

Subscription Contract Is in ERROR Status

Possible causes are:

Queue property if Ordered enables subscription contracts to go in random order, which causes FULLSYNC service operations to error out when the transaction is subscribed before the header. Service operation handler PeopleCode errors exist. Application data errors exist. Subscription Contract Is in EDIT Status Possible cause is that the XML was edited and is not yet resubmitted for processing.

Other Possible Problems

a.

Other possible problems include: Cannot find service operation in Service Operation Monitor. Service operations are being processed in an incorrect order. Service operation is not created. Service operation instance stays in NEW status. Service operation instance stays in STARTED status. Service operation instance stays in WORKING status. Unable to ping a node. Queue is PAUSED.

b. Cannot Find Service Operation in Service Operation Monitor Possible causes is that filtering is set in the Service Operation Monitor. c. Service Operations are Being Processed in an Incorrect Order Possible cause is that the queue was partitioned and the resulting subqueues do not match what was assumed for the ordering of the service operations.

Page 56 of 67

d. Service Operation Instance not Created Possible cause is that the service operation is inactive. e. Service Operation Instance Stays in NEW Status Possible causes are: The Application server is down. Pub/sub services are not configured on the Application Server domain. The Message Dispatcher crashed or was brought down. The item is not at the top of the queue; all service operations with the same queue or subqueue are in the same queue.

f.

Service Operation Instance Stays in STARTED Status

Possible causes are: All Message Handlers crashed or were brought down; processing will resume when Message Handlers come back up. The Message dispatcher processing the message is on another machine, and either the machine or the application server domain is down.

g. Service Operation Instance Stays in WORKING Status Possible causes are: Message Broker Handler crashed. The Message Handler processing the message is on another machine, and either the machine or the application server domain is down. The Message Handler working on the message is blocked. The service will time out, and the Message Dispatcher will retry the message. h. Unable to Ping a Node Possible causes are: The web server for the Gateway is down. The Gateway is not configured properly. The application server for the node is down. The Gateway URL is incorrect; verify that the URL is correct. Copy URL in browser address; you should see: PeopleSoft Integration Gateway PeopleSoft Listening Connector Status: ACTIVE i. Queue Is PAUSED rPossible cause is that some queues are delivered as paused. Change the status to Run for the service operations to process from New to Working.

Page 57 of 67

9. PS delivered EIP points

PeopleSoft have some delivered messages and Integration points. Below excel sheet have

PeopleSoft delivered Integration points Service Operati on Type

Asynchronus Asynchronus Asynchronus Asynchronus Asynchronus

Integration Point
ACCOUNT_CHARTFIELD_FULLSYNC.Versio n_1 ACCOUNT_CHARTFIELD_SYNC.Version_1 ALTACCT_CF_SYNC.Version_1 BUDGET_REF_CF_FULLSYNC.Version_1 BUDGET_REF_CF_SYNC.Version_1

Service Name
ACCOUNT_CHARTFIELD_FULLSYN C ACCOUNT_CHARTFIELD_SYNC ALTACCT_CF_SYNC BUDGET_REF_CF_FULLSYNC BUDGET_REF_CF_SYNC

Integration Set Name

GL ACCOUNT TABLE GL ACCOUNT TABLE ALTERNATE CHARTFIELD BUDGET CHARTFIELD BUDGET CHARTFIELD ACCOUNT

Description
Initial Load of GL Accounts Incremental Load of GL Accounts. Incremental update of Alternate Account ChartField.

REFERENCE Load budget reference ChartField. REFERENCE Incremental update to budget reference ChartField.

BUD_PERIOD_CALENDAR_FULLSYNC.Versi on_1

BUD_PERIOD_CALENDAR_FULLSY NC

Asynchronus

COMMIT ACCTG CALENDAR D

DETAIL

HRMS Integration with FSCM - Detail Calendar Data from Financials that defines Accounting Periods.

BUD_PERIOD_CALENDAR_SYNC.Version_1

BUD_PERIOD_CALENDAR_SYNC

Asynchronus

COMMIT ACCTG DETAIL CALENDAR D

HRMS Integration with FSCM - Detail Calendar Data from Financials that defines Accounting Periods

BUS_UNIT_FS_FULLSYNC.Version_1

BUS_UNIT_FS_FULLSYNC

Asynchronus

BUSINESS UNIT TABLE FS

Full table replication of Business Units between Financials and HRMS

BUS_UNIT_FS_SYNC.Version_1

BUS_UNIT_FS_SYNC

Asynchronus

BUSINESS UNIT TABLE FS

Incremental integration of Business Units between Financials and HRMS

BUS_UNIT_GL_FULLSYNC.Version_1

BUS_UNIT_GL_FULLSYNC

Asynchronus

BUSINESS UNIT TABLE GL

Bus Unit GL Full Sync

BUS_UNIT_PC_FULLSYNC.Version_1

BUS_UNIT_PC_FULLSYNC

Asynchronus

BUSINESS UNIT TABLE PC

Projects Business Unit Prompt

CHARTFIELD1_FULLSYNC.Version_1

CHARTFIELD1_FULLSYNC

Asynchronous

CHARTFIELD1

Load ChartField1.

CHARTFIELD1_SYNC.Version_1

CHARTFIELD1_SYNC

Asynchronous

CHARTFIELD1

Incremental update of ChartField1.

CHARTFIELD2_FULLSYNC.Version_1

CHARTFIELD2_FULLSYNC

Asynchronous

CHARTFIELD2

Load ChartField2

Page 58 of 67

CHARTFIELD2_SYNC.Version_1

CHARTFIELD2_SYNC

Asynchronous

CHARTFIELD2

Incremental update of ChartField2.

CHARTFIELD3_FULLSYNC.Version_1

CHARTFIELD3_FULLSYNC

Asynchronous

CHARTFIELD3

Load ChartField3

Integration Point
CHARTFIELD3_SYNC.Version_1

Service Name
CHARTFIELD3_SYNC

Service Operati on Type

Asynchronous

Integration Set Name

CHARTFIELD3

Description
Incremental update of ChartField3.

CLASS_CF_FULLSYNC.Version_1

CLASS_CF_FULLSYNC

Asynchronous

CLASS_CHARTFIELD

Load Class ChartField.

CLASS_CF_SYNC.Version_1

CLASS_CF_SYNC

Asynchronous

CLASS_CHARTFIELD

Incremental update to Class ChartField.

COUNTRY_FULLSYNC.Version_1

COUNTRY_FULLSYNC

Asynchronous

COUNTRY TABLE

Country Table

COUNTRY_SYNC.Version_1

COUNTRY_SYNC

Asynchronous

COUNTRY TABLE

Country Table Sync

DEPT_FULLSYNC.Version_1

DEPT_FULLSYNC

Asynchronous

DEPARTMENT TABLE

Full table replication of Departments between Financials and HRMS

DEPT_SYNC.Version_1

DEPT_SYNC

Asynchronous

DEPARTMENT TABLE

Incremental synchronization of Departments between Financials and HRMS HRMS Integration with FSCM - Detail Calendar Data from Financials that defines Accounting Periods. Inbound file publish after receiving flat file from E&G Financials 7.5.

DETAIL_CALENDAR_FULLSYNC.Version_1

DETAIL_CALENDAR_FULLSYNC

Asynchronous

DETAIL CALENDAR DATA

DETAIL_CALENDAR_SYNC.Version_1

DETAIL_CALENDAR_SYNC

Asynchronous

DETAIL CALENDAR DATA

Subscribe to detail calendar

ELAPSED_TIME_ADD.Version_1

ELAPSED_TIME_ADD

Asynchronous

T&L LABOR TIME REP ELPSD TIME

Moves elapsed time reporting data to PeopleSoft Time and Labor for billing purposes.

FUND_CF_SYNC.Version_1

FUND_CF_SYNC

Asynchronous

FUND TABLE

Load fund ChartField.

FUND_LOAD.Version_1

FUND_LOAD

Asynchronous

FUND TABLE

Publish and subscription of Fund Table.

HR_ACCT_CD_LOAD.Version_1

HR_ACCT_CD_LOAD

Asynchronous

ACCT CODE TABLE

AE:Publish and subscribe to ChartField Account Codes.

HR_CHARTFLD_COMBO_SYNC.Version_1

HR_CHARTFLD_COMBO_SYNC

Asynchronous

ACCT CODE TABLE

Incremental update of ChartField combinations.

JOBCODE_SYNC.Version_1

JOBCODE_SYNC

Asynchronous

Jobcode Setup Sync

JOURNAL_GENERATOR_APPL_ID_SYNC.V ersion_1

JOURNAL_GENERATOR_APPL_ID_ SYNC

Asynchronous

JOURNAL GENERATOR TEMPLATE

Publish and subscription of Journal Generator template.

JOURNAL_GEN_APPL_ID_FULLSYNC.Versio n_1

JOURNAL_GEN_APPL_ID_FULLSY NC

Asynchronous

JOURNAL GENERATOR TEMPLATE

Full Table publish and subscription of Journal Generator Template.

Page 59 of 67

LEDGER_DEFN_SYNC.Version_1

LEDGER_DEFN_SYNC

Asynchronous

STUDENT FINANCIALS GL INTERFAC

Incremental table synchronization of ledger definition.

Integration Point
LOCATION_FULLSYNC.Version_1

Service Name
LOCATION_FULLSYNC

Service Operati on Type

Asynchronous

Integration Set Name

LOCATION TABLE

Description
Location Sync Full Message

LOCATION_SYNC.Version_1

LOCATION_SYNC

Asynchronous

LOCATION TABLE

Location Table - Sync Message

OPER_UNIT_CF_FULLSYNC.Version_1

OPER_UNIT_CF_FULLSYNC

Asynchronous

OPERATING UNIT CHARTFIELD

Load Operating Unit ChartField.

OPER_UNIT_CF_SYNC.Version_1

OPER_UNIT_CF_SYNC

Asynchronous

OPERATING UNIT CHARTFIELD

Incremental update of Operating Unit ChartField.

PAYMENT_EXPENSES_REQUEST.Version_1

PAYMENT_EXPENSES_REQUEST

Asynchronous

PAYROLL PAYSHEET PAYMENT REQUE

Payment Expenses Request.

POSITION_FULLSYNC.Version_1

POSITION_FULLSYNC

Asynchronous

Position Data Setup Sync

POSITION_SYNC.Version_1

POSITION_SYNC

Asynchronous

Position Data Setup Sync

PRODUCT_CHARTFIELD_FULLSYNC.Versio n_1

PRODUCT_CHARTFIELD_FULLSYN C

Asynchronous

ACCT CODE TABLE

General Ledger sends ChartFIeld data to Payroll for North America.

PRODUCT_CHARTFIELD_SYNC.Version_1

PRODUCT_CHARTFIELD_SYNC

Asynchronous

ACCT CODE TABLE

General Ledger sends ChartFIeld incremental updates to Payroll for North America.

PROGRAM_CF_SYNC.Version_1

PROGRAM_CF_SYNC

Asynchronous

PROGRAM_CHARTFIELD

Incremental update of program ChartField.

PROJECT_ACTIVITY_FULLSYNC.Version_1

PROJECT_ACTIVITY_FULLSYNC

Asynchronous

PROJECT ACTIVITIES

Proj Activity Full sync

PROJECT_ACTIVITY_FULLSYNC.Version_2

PROJECT_ACTIVITY_FULLSYNC

Asynchronous

PROJECT ACTIVITIES

Syncing Project Activity

PROJECT_ACTIVITY_SYNC.Version_1

PROJECT_ACTIVITY_SYNC

Asynchronous

PROJECT ACTIVITIES

Proj Activity Sync

PROJECT_ACTIVITY_SYNC.Version_2

PROJECT_ACTIVITY_SYNC

Asynchronous

PROJECT ACTIVITIES

Syncing project activity

PROJECT_FULLSYNC.Version_1

PROJECT_FULLSYNC

Asynchronous

PROJECT TABLE

Full synchronization of the Projects table.

PROJECT_TEAM_FULLSYNC.Version_2

PROJECT_TEAM_FULLSYNC

Asynchronous

PROJECT TEAM

Project Team prompt

PROJECT_TEAM_SYNC.Version_2

PROJECT_TEAM_SYNC

Asynchronous

PROJECT TEAM

Project Team prompt

PROJECT_STATUS_DEFN_FULLSYNC.Versi on_1

PROJECT_STATUS_DEFN_FULLSY NC

Asynchronous

PROJECT STATUS DEFINITION

Project Status prompt

Page 60 of 67

Integration Point
PROJECT_STATUS_DEFN_SYNC.Version_1

Service Name
PROJECT_STATUS_DEFN_SYNC

Service Operati on Type

Asynchronous

Integration Set Name

PROJECT STATUS DEFINITION

Description
Project Status prompt

PROJECT_STATUS_FULLSYNC.Version_1

PROJECT_STATUS_FULLSYNC

Asynchronous

PROJECT STATUS

Project Status

PROJECT_STATUS_SYNC.Version_1

PROJECT_STATUS_SYNC

Asynchronous

PROJECT STATUS

Project Status

PROJECT_SYNC.Version_1

PROJECT_SYNC

Asynchronous

PROJECT TABLE

Incremental synchronization of the Projects table.

PROJ_ACTIVITY_STATUS_FULLSYNC.Versi on_1

PROJ_ACTIVITY_STATUS_FULLSY NC

Asynchronous

PROJECT ACTIVITY STATUS

Project Activity Status Message

PROJ_ACTIVITY_STATUS_SYNC.Version_1 RESOURCE_CAT_FULLSYNC.Version_1

PROJ_ACTIVITY_STATUS_SYNC

Asynchronous

PROJECT ACTIVITY STATUS

Project Activity Status Message

RESOURCE_CAT_FULLSYNC

Asynchronous

PROJECT RESOURCE CATEGORY

Resource Category Prompt

RESOURCE_CAT_SYNC.Version_1

RESOURCE_CAT_SYNC

Asynchronous

PROJECT RESOURCE CATEGORY

Resource Category Prompt

RESOURCE_SUB_CAT_FULLSYNC.Version_ 1

RESOURCE_SUB_CAT_FULLSYNC

Asynchronous

PROJECT RESOURCE SUBCATEGORY

Resource SubCategory Prompt

RESOURCE_SUB_CAT_SYNC.Version_1

RESOURCE_SUB_CAT_SYNC

Asynchronous

PROJECT RESOURCE SUBCATEGORY

Resource SubCategory Prompt

RESOURCE_TYPE_FULLSYNC.Version_1

RESOURCE_TYPE_FULLSYNC

Asynchronous

PROJECT RESOURCE TYPE

Resource Type Prompt

RESOURCE_TYPE_SYNC.Version_1

RESOURCE_TYPE_SYNC

Asynchronous

PROJECT RESOURCE TYPE

Resource Type Prompt

RES_CAT_SUB_CAT_LINK_FULLSYNC.Versi on_1

RES_CAT_SUB_CAT_LINK_FULLSY NC

Asynchronous

PROJECT CATEGORY-TOSUBCATEGOR

Relating Category and SubCat

RES_CAT_SUB_CAT_LINK_SYNC.Version_1

RES_CAT_SUB_CAT_LINK_SYNC

Asynchronous

PROJECT CATEGORY-TOSUBCATEGOR

Relating Category and SubCat

RES_TYPE_CAT_LINK_FULLSYNC.Version_ 1

RES_TYPE_CAT_LINK_FULLSYNC

Asynchronous

PROJECT TYPE-TO-CATEGORY LINK

Relate ResTypes and Categories

RES_TYPE_CAT_LINK_SYNC.Version_1

RES_TYPE_CAT_LINK_SYNC

Asynchronous

PROJECT TYPE-TO-CATEGORY LINK

Relate ResTypes and Categories

SETID_INITIALIZE.Version_1

SETID_INITIALIZE

Asynchronous

TABLE SET CONTROL

Setid

STATE_FULLSYNC.Version_1

STATE_FULLSYNC

Asynchronous

STATE TABLE

State Table Full Sync

Integration Point

Service Name

Service Operati on Type

Integration Set Name

Description
Page 61 of 67

STATE_SYNC.Version_1

STATE_SYNC

Asynchronous

STATE TABLE

State Table Message Incr Sync

UOM_FULLSYNC.Version_1

UOM_FULLSYNC

Asynchronous

UNIT OF MEASURE

Units of Measure Full Sync

UOM_SYNC.Version_1

UOM_SYNC

Asynchronous

UNIT OF MEASURE

Units of Measure Incr Sync Send the entire content of the Vendor table to NA Payroll from AP. NA Payroll subscribes only to HRMS vendors. Send the incremental update of vendors to Payroll for North America from AP. Payroll of North America subscribes only to update of HRMS vendors.

VENDOR_FULLSYNC.Version_1

VENDOR_FULLSYNC

Asynchronous

VENDOR

VENDOR_SYNC.Version_1

VENDOR_SYNC ACTION_REASON_SYNC

Asynchronous

VENDOR

ACTION_REASON_SYNC.Version_1

Asynchronous

Action Reason Setup Sync

ACTUAL_TIME_ADD.Version_1

ACTUAL_TIME_ADD

Asynchronous

T&L ACTUAL TIME

Provide cost information when a change to payable time impacts project costs

ACTUAL_TIME_BATCH_ADD.Version_1

ACTUAL_TIME_BATCH_ADD

Asynchronous

T&L ACTUAL TIME

Provide cost information when a change to payable time impacts project costs

BUS_UNIT_AV_SYNC.Version_1

BUS_UNIT_AV_SYNC

Asynchronous

AV BUSINESS UNIT

Contributor Rel Bus Unit Sync

BUS_UNIT_HR_FULLSYNC.Version_1

BUS_UNIT_HR_FULLSYNC

Asynchronous

BUS_UNIT_HR_SYNC.Version_1

BUS_UNIT_HR_SYNC

Asynchronous Full synchronization of accomplishments of a competency cluster table between HRMS 8.9 and Fin/SCM 8.8 SP1 Incremental synchronization of accomplishments of a competency cluster table between HRMS 8.9 and Fin/SCM 8.8 SP1

CLUSTER_ACCOMP_FULLSYNC.Version_1

CLUSTER_ACCOMP_FULLSYNC

Asynchronous

ACCOMPLISHMENT CLUSTER

CLUSTER_ACCOMP_SYNC.Version_1

CLUSTER_ACCOMP_SYNC

Asynchronous

ACCOMPLISHMENT CLUSTER

CLUSTER_COMP_FULLSYNC.Version_1

CLUSTER_COMP_FULLSYNC

Asynchronous

COMPETENCY CLUSTER

Full table pub CM_CLUSTER_COMP

CLUSTER_COMP_SYNC.Version_1

CLUSTER_COMP_SYNC

Asynchronous

COMPETENCY CLUSTER

Pub changes to CM_CLUSTER_COMP Full synchronization of a competency type between HRMS 8.9 and Financials Supply Chain 8.8 Service Pack 1 Incremental synchronization of a competency type between HRMS 8.9 and Financials Supply Chain 8.8 Service Pack 1

CM_TYPE_FULLSYNC.Version_1

CM_TYPE_FULLSYNC

Asynchronous

COMPETENCY TYPE

CM_TYPE_SYNC.Version_1

CM_TYPE_SYNC

Asynchronous

COMPETENCY TYPE

COMBO_CF_EDIT_REQUEST.Version_1

COMBO_CF_EDIT_REQUEST

Asynchronous

COMBINATION EDIT FOR CHARTFIELD

ChartField Combination validation request.

Integration Point
COMPETENCY_FULLSYNC1.Version_1

Service Name
COMPETENCY_FULLSYNC1

Service Operati on Type

Asynchronous

Integration Set Name

COMPETENCY TABLE

Description
Full synchronization of a competency table between HRMS 8.9 and Financials Supply Chain 8.8 Service Pack 1

Page 62 of 67

COMPETENCY_FULLSYNC2.Version_1

COMPETENCY_FULLSYNC2

Asynchronous

COMPETENCY TABLE

Full synchronization of a competency table between HRMS 8.9 and Financials Supply Chain 8.8 Service Pack 1 Full synchronization of a competency table between HRMS 8.9 and Financials Supply Chain 8.8 Service Pack 1 Incremental synchronization of a competency table between HRMS 8.9 and Financials Supply Chain 8.8 Service Pack 1 Incremental synchronization of a competency table between HRMS 8.9 and Financials Supply Chain 8.8 Service Pack 1 Incremental synchronization of a competency table between HRMS 8.9 and Financials Supply Chain 8.8 Service Pack 1

COMPETENCY_FULLSYNC3.Version_1

COMPETENCY_FULLSYNC3

Asynchronous

COMPETENCY TABLE

COMPETENCY_SYNC1.Version_1

COMPETENCY_SYNC1

Asynchronous

COMPETENCY TABLE

COMPETENCY_SYNC2.Version_1

COMPETENCY_SYNC2

Asynchronous

COMPETENCY TABLE

COMPETENCY_SYNC3.Version_1

COMPETENCY_SYNC3

Asynchronous

COMPETENCY TABLE

CORPORATE_CARD_FULLSYNC.Version_1

CORPORATE_CARD_FULLSYNC

Asynchronous

CREDIT CARD MERCHANT

Corporate Card Vendors

CORPORATE_CARD_SYNC.Version_1

CORPORATE_CARD_SYNC

Asynchronous

CREDIT CARD MERCHANT

Corporate Card Vendors

COUNTRY_FULLSYNC.Version_1

COUNTRY_FULLSYNC COUNTRY_SYNC

Asynchronous

COUNTRY TABLE

Country Table Full Sync.

COUNTRY_SYNC.Version_1

Asynchronous

COUNTRY TABLE

Country Table Sync.

CURRENCY_FULLSYNC.Version_1

CURRENCY_FULLSYNC

Asynchronous

CURRENCY CODE TABLE

Currency Table Full Sync

CURRENCY_SYNC.Version_1

CURRENCY_SYNC

Asynchronous

CURRENCY CODE TABLE

Currency Tbl Incremental Synch

DEPT_FULLSYNC.Version_1

DEPT_FULLSYNC

Asynchronous

DEPARTMENT TABLE

Dept Full Sync

DEPT_SYNC.Version_1

DEPT_SYNC

Asynchronous

DEPARTMENT TABLE

Dept Sync Incr. Message

DIRECT_DEPOSIT_FULLSYNC.Version_1

DIRECT_DEPOSIT_FULLSYNC

Asynchronous

DIRECT DEPOSIT

Load Direct Deposit data.

DIRECT_DEPOSIT_SYNC.Version_1

DIRECT_DEPOSIT_SYNC

Asynchronous

DIRECT DEPOSIT

Direct Deposit Increment update

EARNINGS_FULLSYNC.Version_1

EARNINGS_FULLSYNC

Asynchronous

EARNINGS TABLE

Load Earnings Table.

EARNINGS_SYNC.Version_1

EARNINGS_SYNC

Asynchronous

EARNINGS TABLE

Incremental update of Earnings Table

Integration Point
ESTIMATED_TIME_BATCH_ADD.Version_1

Service Name
ESTIMATED_TIME_BATCH_ADD

Service Operati on Type

Asynchronous

Integration Set Name

T&L ESTIMATED TIME

Description
Payable Time Message Full synchronization of a frequency table between HRMS 8.9 and Financials Supply Chain 8.8 Service Pack 1

FREQUENCY_FULLSYNC.Version_1

FREQUENCY_FULLSYNC

Asynchronous

FREQUENCY TABLE

Page 63 of 67

FREQUENCY_SYNC.Version_1

FREQUENCY_SYNC

Asynchronous

FREQUENCY TABLE

Incremental synchronization of a frequency table between HRMS 8.9and Financials Supply Chain 8.8 Service Pack 1

HOLIDAY_DATE_FULLSYNC.Version_1

HOLIDAY_DATE_FULLSYNC

Asynchronous

HOLIDAY DATES

Holiday Date Full Sync Full synchronization of the Job code information between HRMS 8.9 and Financials Supply Chain 8.8 Service Pack 1 Incremental synchronization of the Job code information between HRMS 8.9 and Financials Supply Chain 8.8 Service Pack 1 Full synchronization of the job family table between HRMS 8.9 and Financials Supply Chain 8.8 Service Pack 1 Incremental synchronization of the job family table between HRMS 8.9 and Financials Supply Chain 8.8 Service Pack 1

JOBCODE_FULLSYNC.Version_1

JOBCODE_FULLSYNC

Asynchronous

JOBCODE TABLE

JOBCODE_SYNC.Version_1

JOBCODE_SYNC

Asynchronous

JOBCODE TABLE

JOB_FAMILY_FULLSYNC.Version_1

JOB_FAMILY_FULLSYNC

Asynchronous

JOB FAMILY

JOB_FAMILY_SYNC.Version_1

JOB_FAMILY_SYNC

Asynchronous

JOB FAMILY

LOCATION_FULLSYNC.Version_1

LOCATION_FULLSYNC

Asynchronous

Location Sync Full Message

LOCATION_SYNC.Version_1

LOCATION_SYNC

Asynchronous

Location Table - Sync Message Incremental synchronization of all the name prefixes or titles between HRMS 8.9 and Financials Supply Chain 8.8 Service Pack 1

NAME_PREFIX_SUFFIX_SYNC.Version_1

NAME_PREFIX_SUFFIX_SYNC

Asynchronous

NAME PREFIX/SUFFIX TABLES

NID_TYPE_FULLSYNC.Version_1

NID_TYPE_FULLSYNC

Asynchronous

NID TYPE

Full synchronization of the national ID types between HRMS 8.9 and Fin/SCM 8.4sp1

NID_TYPE_SYNC.Version_1

NID_TYPE_SYNC

Asynchronous

NID TYPE

Incremental synchronization of the national ID types between HRMS 8.9 and Fin/SCM 8.4sp1

PAYMENT_EXPENSES_ACKNOWLEDGE.Ve rsion_1

PAYMENT_EXPENSES_ACKNOWL EDGE

Asynchronous

PAYROLL PAYMENT REQUEST ACKNOW

Provides Payroll's Acknowledgement of Expenses Request for Payment.

PAYMENT_EXPENSES_ISSUE.Version_1

PAYMENT_EXPENSES_ISSUE

Asynchronous

PAYROLL PAYSHEET PAYMENT ISS

Creates Payroll Paysheet for Payments Issued.

PERSON_ACCOMP_FULLSYNC.Version_1

PERSON_ACCOMP_FULLSYNC

Asynchronous

PERSON ACCOMPLISHMENTS

Full synchronization of accomplishments between HRMS 8.9 and Fin/SCM 8.8 SP1

PERSON_ACCOMP_SYNC.Version_1

PERSON_ACCOMP_SYNC

Asynchronous

PERSON ACCOMPLISHMENTS

Incremental synchronization of accomplishments between HRMS 8.9 and Fin/SCM 8.8 SP1 Full synchronization of the personal data between HRMS 8.9 and Financials Supply Chain 8.8 Service Pack 1

PERSON_BASIC_FULLSYNC.Version_1

PERSON_BASIC_FULLSYNC

Asynchronous

PERSON CONTRACT

Integration Point
PERSON_BASIC_SYNC.Version_1

Service Name
PERSON_BASIC_SYNC

Service Operati on Type

Asynchronous

Integration Set Name

PERSON CONTRACT

Description
Incremental synchronization of the personal data between HRMS 8.9 and Financials Supply Chain 8.8 Service Pack 1

PERSON_COMPETENCY_FULLSYNC.Versio n_1

PERSON_COMPETENCY_FULLSYN C

Asynchronous

PERSON COMPETENCY

PERSON_COMPETENCY_FULLSYNC

PERSON_COMPETENCY_SYNC.Version_1

PERSON_COMPETENCY_SYNC

Asynchronous

PERSON COMPETENCY

PERSON_COMPETENCY_SYNC

Page 64 of 67

PERSON_DIVERSITY_FULLSYNC.Version_1

PERSON_DIVERSITY_FULLSYNC

Asynchronous

PERSON DIVERSITY

Person Diversity Data

PERSON_DIVERSITY_SYNC.Version_1

PERSON_DIVERSITY_SYNC

Asynchronous

PERSON DIVERSITY

Person Diversity Data

PERSON_EDUCATION_SYNC.Version_1

PERSON_EDUCATION_SYNC

Asynchronous

Personal Education Sync

PERSON_PRIOR_WORK_SYNC.Version_1

PERSON_PRIOR_WORK_SYNC

Asynchronous

PERSON PRIOR WORK EXPERIENCE

Personal Prior Work Sync Full synchronization of the passport and citizenship information between HRMS 8.9 and Financials Supply Chain 8.8 Service Pack 1 Incremental synchronization of the passport and citizenship information between HRMS 8.9 and Financials Supply Chain 8.8 Service Pack 1

PERSON_VISA_CITIZEN_FULLSYNC1.Versio n_1

PERSON_VISA_CITIZEN_FULLSYN C1

Asynchronous

PERSON VISA/CITIZENSHIP

PERSON_VISA_CITIZEN_SYNC.Version_1

PERSON_VISA_CITIZEN_SYNC

Asynchronous

PERSON VISA/CITIZENSHIP

POSITION_FULLSYNC.Version_1

POSITION_FULLSYNC

Asynchronous

POSITION DATA

Position Data Setup Sync

POSITION_SYNC.Version_1

POSITION_SYNC

Asynchronous

POSITION DATA

Position Data Setup Sync Full synchronization of the Rating Models between HRMS 8.9 and Financials Supply Chain 8.8 Service Pack 1 Incremental synchronization of the Rating Models between HRMS 8.9 and Financials Supply Chain 8.8 Service Pack 1

RATING_MODEL_FULLSYNC.Version_1

RATING_MODEL_FULLSYNC

Asynchronous

RATING MODEL

RATING_MODEL_SYNC.Version_1

RATING_MODEL_SYNC

Asynchronous

RATING MODEL

RELEASE_REQUEST.Version_1

RELEASE_REQUEST

Asynchronous

Get Release Label

ROLE_ACCOMP_FULLSYNC.Version_1

ROLE_ACCOMP_FULLSYNC

Asynchronous

ROLE ACCOMPLISHMENTS

Role Accomplishments Full Sync

ROLE_ACCOMP_SYNC.Version_1

ROLE_ACCOMP_SYNC

Asynchronous

ROLE ACCOMPLISHMENTS

Role Accomplishments Sync

ROLE_CLUSTER_FULLSYNC.Version_1

ROLE_CLUSTER_FULLSYNC

Asynchronous

ROLE CLUSTER

Role Cluster Full Sync

ROLE_CLUSTER_SYNC.Version_1

ROLE_CLUSTER_SYNC

Asynchronous

ROLE CLUSTER

Role Cluster

Integration Point
ROLE_COMP_FULLSYNC.Version_1

Service Name
ROLE_COMP_FULLSYNC

Service Operati on Type

Asynchronous

Integration Set Name

ROLE COMPETENCIES

Description
Full table pub CM_ROLE_COMPS.

ROLE_COMP_SYNC.Version_1

ROLE_COMP_SYNC

Asynchronous

ROLE COMPETENCIES

Pub changes to CM_ROLE_COMPS

ROLE_FULLSYNC.Version_1

ROLE_FULLSYNC

Asynchronous

ROLE COMPETENCY / ACCOMPLISHMET

Role Competency / Accomplishmet

ROLE_SYNC.Version_1

ROLE_SYNC

Asynchronous

ROLE COMPETENCY / ACCOMPLISHMET

Role Competency / Accomplishmet

Page 65 of 67

SCHOOL_FULLSYNC.Version_1

SCHOOL_FULLSYNC

Asynchronous

SCHOOL TABLE

SCHOOL_FULLSYNC

SCHOOL_SYNC.Version_1

SCHOOL_SYNC

Asynchronous

SCHOOL TABLE

SCHOOL_SYNC

SETID_INITIALIZE.Version_1

SETID_INITIALIZE

Asynchronous

TABLE SET CONTROL

Setid

STATE_FULLSYNC.Version_1

STATE_FULLSYNC

Asynchronous

State Table Full Sync

STATE_SYNC.Version_1

STATE_SYNC

Asynchronous

State Table Message Incr Sync

TAX_LOCATION1_FULLSYNC.Version_1

TAX_LOCATION1_FULLSYNC

Asynchronous

HR TO FIN/FO FULLSYNC PUBLISH

TBLSET_CONTROL_INITIALIZE.Version_1

TBLSET_CONTROL_INITIALIZE

Asynchronous

TABLE SET CONTROL

Table set control

TIME_REPORTING_CODE_FULLSYNC.Versi on_1

TIME_REPORTING_CODE_FULLSY NC

Asynchronous

TIME REPORTING CODES

Time Reporting Code Full Table

TIME_REPORTING_CODE_SYNC.Version_1

TIME_REPORTING_CODE_SYNC

Asynchronous

TIME REPORTING CODES

Time Reporting Code Inc Update

TITLE_FULLSYNC.Version_1

TITLE_FULLSYNC

Asynchronous

TITLE

Full synchronization of the Title table between HRMS 8.9 and Fin/SCM 8.4sp1

TITLE_SYNC.Version_1

TITLE_SYNC

Asynchronous

TITLE

Incremental synchronization of the Title table between HRMS 8.9 and FIN/SCM 8 SP1

TL_TASKGRP_TBL_FULLSYNC.Version_1

TL_TASKGRP_TBL_FULLSYNC

Asynchronous

HR TO FIN/FO FULLSYNC PUBLISH

TL_WRKGRP_TBL_FULLSYNC.Version_1

TL_WRKGRP_TBL_FULLSYNC

Asynchronous

HR TO FIN/FO FULLSYNC PUBLISH

US_SOC_FULLSYNC.Version_1

US_SOC_FULLSYNC

Asynchronous

US SOC

US SOC Setup Fullsync

Integration Point
US_SOC_SYNC.Version_1

Service Name
US_SOC_SYNC

Service Operati on Type

Asynchronous

Integration Set Name

US SOC

Description
US SOC Setup Sync

VENDOR_SYNC.Version_1

VENDOR_SYNC

Asynchronous

VENDOR

Send the incremental update of HRMS vendors from Payroll for North America to AP. Payroll for North American sends tax, garnishment, and voluntary deduction withholding information to PeopleSoft Payables for payment. Full synchronization of the employees job history data between HRMS 8.9 and Financials Supply Chain 8.8 Service Pack 1 Incremental synchronization of the employees job history data between HRMS 8.9 and Financials Supply Chain 8.8 Service Pack 1

VOUCHER_BUILD.Version_1

VOUCHER_BUILD

Asynchronous

VOUCHERS

WORKFORCE_FULLSYNC.Version_1

WORKFORCE_FULLSYNC

Asynchronous

WORKFORCE DATA

WORKFORCE_SYNC.Version_1

WORKFORCE_SYNC

Asynchronous

WORKFORCE DATA

Page 66 of 67

10. Summary and Benefits

Real-time business is critical to the future of your enterprise. Employees need it, suppliers require it, and most importantly, customer demand it! The only question is, as critical components of your technology infrastructure increasingly lie outside of your four walls .how do you manage these changes and meet the demands of your key stakeholders? Using PeopleSofts Integration Broker technology, complex connections between legacy systems, packaged applications, and trading partners can all be created and managed securely over the Internet. This hub-and-spoke framework eliminates the need for expensive and timeconsuming point-to-point integrations between all of your applications, while providing an infrastructure focused on reusability and performance. The end result is an organization ready for the challenges of real-time business.
Page 67 of 67

From a technology perspective, Integration Broker is a core element of the PeopleTools Infrastructure. The same industry leading enterprise architecture that runs each and every one of our best-in-class applications includes the Integration Broker product. Whether you are already a PeopleSoft shop, or are considering one of our applications or a 3rd party integration tool, you can be confident that your integration requirements can be handled by the same infrastructure you trust today for your applications. No additional hardware investments, no new software to buy, no new programming languages to learn, no outside consultants to train. This is integration technology that is built-in and built-to last. Now thats return on investment!

Page 68 of 67