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

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

The data layer is primarily concerned with the extraction of key information from application databases and disparate data sources. we rarely see the system-to-system communications. Page 2 of 67 . or web content. analytical reports. leading to islands of automation. each of these elements being presented in a user-friendly format based on their specific role based privileges. Although. Our Enterprise Warehouse product suite enables data level archiving. and effective business decisions. they are far more frequent and complex than the simple web based interfaces we are used to as users. operating unaware of each other. process and data. retrieval. This information may take the form of application transactions. typically using an off the shelf business intelligence tool. It is this initial problem that created the world of integration technologies. This level of integration is the domain of the PeopleSoft Enterprise Portal. and enabling new value-added operations through the powerful use of web technology. function: people.2. The people layer – or user-interface – is primarily concerned with the aggregation and presentation of information. Integration Overview IT management has always been forced to deal with the issue of multiple systems and a lack of communication standards. This layer is squarely focused on optimizing existing business processes. At the highest level. there are three primary areas in which integration technologies (commonly referred to as middleware). This data is then warehoused for later analysis. The Portal aggregates business critical transactions and provides relevant context for more accurate. This challenging venue is the domain of the PeopleSoft Integration Broker. The process layer handles the system-to-system communications critical to the operation of any enterprise. and analysis for the precise purpose of gaining insight into the inner workings and performance of your business. timely.

the hub-and-spoke model allows for a new application to integrate once to a hub. Another value that the hub-and-spoke paradigm brings is in terms of adaptability. If there is one thing for certain. and most importantly. and the list goes on and on. None of the other systems are even aware of the modification. should an application change the way it stores and transmits information. This new paradigm is possible. The point-to-point model requires each and every connection to be individually and programmatically created. it is change. CRM. Legacy Applications. using the hub-and-spoke model.3. SCM. In the past. Integration Models Consider for a moment all of the systems which need to communicate and share information: ERP. The downside to this paradigm is realized when a previously integrated system is updated. We call this approach. or when a new application is added to the environment. only the logic within the hub is altered. and leverage the existing connections to the other systems rather than create new ones. letting it do the work of translating and routing messages between systems using pre-defined rules and definitions. and exponential. development effort. Conversely. these other systems do not need to be altered in any way due to the change Page 3 of 67 . links between these applications were created by hardwiring direct connections between systems. This means that a single addition to the network causes a corresponding. Using the Integration Broker. because each and every system communicates directly to the hub. point-to-point integration.

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

Diagram depicting the usage of Integration Broker in real world. Page 5 of 67 .

• Prioritize integration development. Integration Gateway . -Plan on using simulation tools such as PeopleSoft Send Master to simulate integration with external systems that are not under our control.The integration gateway is a platform that manages the receipt and delivery of messages passed among systems through PeopleSoft Integration Broker. 2. • Inventory the integrations to develop. So we need to plan accordingly. Planning the Integration Broker: While planning the integrations to develop and execute. • Generic integrations. standard integrations next and nice-tohave integrations last.5. Even when we do control all systems that are being integrated.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. The 2 major components of PeopleSoft IB are: 1. • • Determine if data will need transformation or translation. -Determine if you business needs are best served with real-time integration or scheduled integrations. Integration Engine . the following factors needs to be considered: • Real-time integrations or scheduled integrations. Prerequisites required before implementing PeopleSoft Integration Broker PeopleSoft Integration Broker is installed as a part of PeopleSoft installation. 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. and data dependencies within the context of synchronizing data between systems. -Determine which systems and applications will participate in each integration. -Consider dependencies on other systems owned by other groups having concurrent releases. if we can’t get the integration to work using Send Page 6 of 67 . -Plan to develop mission critical integrations first. -Is there is any chance of developing an generic integration. • Determine which integrations will require synchronous messaging and which ones will require asynchronous messaging. Plan on using integration simulation tools.

and non-XML files.The integration gateway resides on a PeopleSoft web server. Test integrations using Send Master before spending hours debugging a system.Master. and non rowset-based message structures including . PeopleSoft Integration Broker enables you to perform these integrations among internal systems and thirdparty integration partners. It is a platform that manages the receipt and delivery of messages passed among systems through PeopleSoft Integration Broker. Exposes PeopleSoft business logic as web services to PeopleSoft and third-party systems. The integration engine: • Uses a modular architecture. It’s tied closely to the PeopleSoft application. PeopleSoft Integration Broker consists of two subsystems: 1. Incoming and outgoing message flows. 6. Transaction types. Adapts elements of an existing integration to produce a new integration with only minor adjustments. XML document object model messages. Understanding PeopleSoft Integration Broker Followings are the main driving components of Integration Broker: • • • • Integration gateway architecture. It supports the leading TCP/IP protocols used in the marketplace today and provides extensible interfaces to develop new connectors for communication with legacy. so it can treat gateways as black boxes and communicate with them using standard connectors. Integration engine . the integration engine sends and receives messages through one or more separately installed integration gateways. Integration gateway . Rather than communicating directly with other applications. Simple Object Access Protocol (SOAP) messages. Integration engine architecture. you can reuse many elements that you develop for integrations. and internet-based systems. enterprise resource planning. PeopleSoft Integration Broker is a middleware technology that: • • • Performs asynchronous and synchronous messaging among internal systems and third-party systems. Page 7 of 67 • • . while managing data structure. we definitely won’t be able to get it working from the external system. data format and transport disparities. and it sends or receives messages for the application. Formats include PeopleSoft rowset-based message format. Consumes and invokes web services from third-party and PeopleSoft systems. Because of its modular design. It runs on the PeopleSoft application server.The integration engine is installed on an application server as part of the PeopleSoft application. Handles messages containing data in a variety of formats. 2.

and cookies. • • • Handles security features such as authentication. By applying application engine transform programs.• Sends and receives messages asynchronously (like email) or synchronously (suspending activity to wait for a response). 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. non repudiation. Applies message transmission type and routing based on specifications that you define in a PeopleSoft Pure Internet Architecture component. These specifications can be reused for other integrations. Page 8 of 67 .

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

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

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

When the reply is received. B. Page 12 of 67 . They are invoked externally by other PeopleSoft systems and third-party systems. Target Connectors Target connectors initiate communication with other PeopleSoft systems or third-party systems. but every transmission requires a low-level acknowledgment. and each of the gateway services. the gateway manager forwards the reply to the calling listening connector. Gateway Manager The gateway manager processes every message that flows through an integration gateway and maintains links to the other major integration gateway components. 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. If an error occurs.Frequently used term to be used with Integration Gateway: A. A target connector might not receive a response from the target system during each operation. listening connectors. the gateway manager uses the error handling service and works with the service to prepare an error reply for the listening connector. 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. including target connectors. C. Listening connectors invoke the gateway manager when they receive a request. Listening Connectors Listening connectors receive incoming data streams and perform services based on the content of the stream.

2 Integration Engine Architecture: Below is the graphical representation of the Integration gateway: Integration engine architecture Page 13 of 67 .5.

Its modular architecture separates integration development activities from administrative activities. displaying the gateway definition. PeopleSoft Pure Internet Architecture definitions. The integration engine is a combination of PeopleSoft Application Designer definitions. click the Load Gateway Connectors button. enter an integration gateway ID. The Gateways search page appears. The gateway uses the PeopleSoft listening connector to receive service operations from an integration engine node or a remote gateway. host name. along with the underlying mechanisms that tie all these elements together. manage. The underlying mechanisms include the request handlers that process both inbound and outbound messages according to the specifications in the development and administrative elements. The integration gateway URL is case sensitive. and select an existing gateway definition. • Add a new value.The integration engine uses a variety of People Tools elements to create. machinename:port is the machine name and port. PeopleCode. implement. To load the delivered target connectors. or IP address of the web server hosting the gateway. and click Add. or at a later time. Select People Tools. Gateways. You can load the delivered target connectors at this point. Enter the gateway URL for the selected gateway’s PeopleSoft listening connector. and enhance integrations. The Gateways page appears. and XSLT code. 3. 2. Steps to Configure IB 6. The Gateways page appears. 8. Do one of the following: • Click Search.1 Configuring the gateway Navigation: Peopletools->Integration Broker-> Configuration->Gateways To define and configure a gateway: 1. Configuration. 4. Integration Broker. Specify the URL with the format: http://machinename:port/PSIGW/PeopleSoftListeningConnector In this case. Save the gateway definition. Page 14 of 67 .

Click the Gateway Setup Properties link to configure additional gateway settings and connector properties. Page 15 of 67 . The default user ID is administrator and the default password is password. Check the Change Password box to change the default password.nnector http://machinename:port/PSIGW/PeopleSoftListeningCo 5.

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 .

which consists of several pages.cfg file. Later.  Save the Node  Page 17 of 67 . URL) To determine the Jolt port of the application server. Local Node Setup When discussing nodes.  Check the options in the Node Info tab for. Whether a node is local or remote is determined by which database the node is defined in. Therefore local and remote are relative terms. then node PSFT_HR is local. check the JOLTListener section in the psappsrv.  The local node in the source system will be the remote node in the target system and vice versa. Enter the user ID that you defined when you created the application server domain. which is system defined one. PeopleSoft Integration Broker will automatically encrypt this password entry. it's important to consider the concepts of local and remote nodes. Tools Release Enter PeopleTools version number installed on the application server.  Default Local node can’t be changed at the user level. I. which we are taking as Local Node for the integration. a. The file is located in <PS_HOME>\appserv\<DOMAIN_NAME>. • Active Node • Local node  In the Connector tab page. 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 the UserPswd that you defined when you created the application server domain. User ID Password 6. give the Gateway ID as LOCAL and connector ID as PSFTTARGET. If you're signed on to HCM which has node PSFT_HR defined.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.2 Configuring Node You configure a node using the Node Definitions component. Enter name of the PeopleSoft node with which the integration gateway is to communicate. Here HRMS is the source system. node PSFT_EP is remote. if you're signed on to FIN. in which PSFT_HR is the Default Local Node. Navigation Description Local Node: Node Info page PeopleTools > Integration Broker > Integration Setup > Nodes This section describes how to configure local nodes.

Indicates that the current node is either a portal node or the default local node. You can't change which node is the default local node.Description Node Type Authentication Option Default Local Node Enter a descriptive name for the node. This is the default for a new node. Non-Repudiation Select to activate non repudiation for the current node. so it can be used by PeopleSoft Integration Broker. Password: Two new fields appear: Password and Confirm Password Indicates whether the current node represents the database to which you are assigned. Select from: PIA: Designates the node as a PeopleSoft database that uses PeopleSoft Integration Broker. Select from: Certificate: The current node uses a digital certificate to sign the messages it sends. Reenter the node password you entered in the Password field. Page 18 of 67 . External: Designates the node as an entity that doesn’t use PeopleSoft Integration Broker. but you can use the Rename Node button to rename the default local node to more appropriately reflect your application or system. Password Confirm Password Displays when the Authentication Option is Password. PeopleSoft Integration Broker is delivered with one node predefined as the default local node. Segment Aware Check the box to configure the node to handle message segments. and expects messages it receives to be signed by a complementary digital certificate. Local Node Active Node Select to make the current node definition active. ICType: A portal-specific setting that PeopleSoft Integration Broker doesn’t use. Enter the node password.

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. This field specifies the target connector appropriate to the communication method preferred by the current node. select PSFTTARGET. The setting is in minutes. Value LOCAL Connector ID: PSFTTARGET Page 19 of 67 . you can indicate the primary database.Default User ID Hub Node Master Node Company ID IB Throttle Threshold On inbound integrations. Any application that uses images can use the selected image to represent the current node. and which property settings for that connector should be used. If the node is a PeopleSoft application with Integration Broker installed. this option can help to prevent saturating the targeting system with requests. This parameter is used only for asynchronous integrations. you can indicate the target node with which it’s associated. which target connector registered with that gateway. Select the name of a node that will serve as a “gatekeeper” for the current node. Enter the name of the company or organization associated with the current node. Description Field Gateway ID: Description When the default local node sends a message to any other node. This field is for information only. unless you have set up an external user ID for this purpose. If the current node represents a subordinate database. Set this parameter on a remote node definition to limit the number of requests sent to the node per dispatch. Select an image from the system database. If the current node is used as a hub. You can select any existing PeopleSoft Pure Internet Architecture node for this purpose. regardless of the gateway ID you select here. the message first goes to the default local node's local gateway through its PeopleSoft listening connector. For slow-processing systems. this is the user ID that the sender must specify to invoke a service operation. Image Name II. including which gateway.

     Here FIN is the Target system. Navigation Description Remote Node: Node Info Page PeopleTools > Integration Broker > Integration Setup > Nodes This section describes how to configure remote nodes. • Default local node • Local node In the Connector tab page. Check the options in the Node Info tab for. Remote Node Setup I. in which PSFT_EP is the Remote Node. • Active Node Uncheck the options in the Node Info tab for. Give the Gateway ID as LOCAL and connector ID as PSFTTARGET Save the Node Page 20 of 67 .b.

The Messages . Click the Add button. if different from the value in the Message Name field. 4.Message Definition page appears. To add a message definition: 1. 2. enter a version for the message.6. (Optional) In the Alias field. Accepted formats for the message version include: • Version_1. Messages. Integration Setup. Page 21 of 67 . enter a name for the message. • V1. Integration Broker. Select PeopleTools. Select the Add New Value tab. Values are: • Rowset-based • Nonrowset-based (default) • Container 7. 5. In the Message. 3.3 Configuring Messages Either a new message can be created or existing message can be modified from Message Builder page. enter the name that the external system is expecting. select the message type. Navigation Description PeopleTools > Integration Broker > Integration Setup > Messages This section describes how to configure messages. In the Message Name field. 6. In the Message Type group box. Version field.

3. You must add at least one message part to the definition before you can save the changes. enter a description for the definition. The message definition is complete and you can click the Save button to save the changes. • Nonrowset-Based Message. Click the plus button to expand the tree and view fields that are associated with the record. 8. 12. Page 22 of 67 . The owner ID helps to determine the application team that last made a change to the definition. (Optional) In the Description field. On the Messages–Message Definitions page. • Container Message. 10. (Optional) From the Owner ID dropdown list box. 11. The next step depends on the type of message definition that you are creating: • Rowset-Based Message. or click the Lookup button to search for and select one. 9. select an owner for the definition. In the New Record Name field. The root record appears in the tree structure. You must add a root record to the definition before you can save it. 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. Click the OK button. The Add New Record page appears. (Optional) Select the Message Parts check box if the message will be used as a message part in a container message definition. enter any pertinent comments about the definition. (Optional) In the Comment field. 2. enter the name of the record to add.This field appears only when you are defining nonrowset-based or container messages. You can now add an XML message schema to the definition. click the Add Record to Root link.

6. New Queue Page 23 of 67 .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.

By default. Select to archive service operation instances that are assigned to the queue. Values are: Run: (default) Service operations that are assigned to this queue are received and processed normally. Page 24 of 67 . Description Queue Status Enter a description for the queue. 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.Location Queue Queue Name Archive Unordered Enter the name of the queue. archiving is enabled. Select to enable field partioning and to process service operations unordered. By default.

Open the Services page. 4.) From the Object Owner ID dropdown list box. 6. In the Description field. enter a description for the service.. Operations Assigned This read-only section lists all service operations that are assigned to the queue. 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. to Queue Include Add Field Select the Include check box next to a field name to include the field in queue partitioning. 2. Enter a namespace URI for the service. Click to view and select partitioning fields. 6. 3. (Optional. 5. 7.6 Configuring Services Operations Page 25 of 67 . (Optional. enter an alias name for the service. 6.Pause: Service operations are received but not processed until the status is reset to Run. Use this area to enter comments about the definition. select the owner of the service. (Optional. enter comments about the service or the service.) In the Service Alias field. 8. select the object owner.) In the Comments field. Object Owner ID Comments From the dropdown list box.5 Configuring Services Navigation Description PeopleTools > Integration Broker > Integration Setup > Services This section describes how to configure Services 1.

which determine the direction. Values are: • Asynchronous – One Way • Synchronous • Asynch Request/Response • Asynch to Synch 5. From the Operation Type drop-down list box. 2. and so on. enter the service name to which the new operation will belong or click the Lookup button to search for a service name. 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. of the service operation. 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. and so on. 3. It also specifies an operation type. The sending system's asynchronous process sends a synchronous request to a remote system. synchronously or asynchronously.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. In the Service field. such as its name. manipulating message content. The sending asynchronous system expects the receiving system to send a synchronous response back. Page 26 of 67 . the response is not processed on the same thread as the response. Asynchronous to Synchronous 1. and it is processed sometime in the future. A service operation has one or more handlers. it contains routings. Processing on the sending system does not continue until it receives a response from the receiving system. enter a name for the service operation. which determines how the operation is to be processed. description. select an operation type. Processing on the sending system continues without a response from the receiving system. In the Service Operation field. which contain and run the programming logic for sending or receiving the message. Click the Add button. In addition. 4. inbound or outbound. Unlike a synchronous operation type. The service operation is provided in real-time. Click the Add Service Operation tab.

select the handler type. The system adds a handler name after you provide the handler details. In the Handlers section. Service operation handlers contain the programming logic for sending and receiving service operations and their contained messages. The Handlers page appears. From the Type dropdown list box. outbound or hub—of service operations A. Select to make the handler active. Note that for OnRequest. and for manipulating content. Values are: • Active. Provides summary information about service operations routings. and OnRoute handlers. From the Status dropdown list box. 2. 4. The service operation type determines the handler types that are available to choose. enter a handler name in the Name field. Routing definition determine the direction—inbound. select the method to use to implement the handler.The Service Operations component includes three pages: General Tab Handlers Tab Routings Tab Features general-service and default-service operation information. 5. 3. • Inactive. The service operation type determines the handler types that are available to choose. select a status for the handler. On the Service Operations component. Select to make the handler inactive. click the Handlers tab. From the Implementation dropdown list box. Provides summary information about handlers that have been added to an operation. Page 27 of 67 . Adding Handlers To add handlers to a service operation: 1. you need not enter a name.

6. Click the Add button.7 Configuring Routings Navigation Description PeopleTools > Integration Broker > Integration Setup > Routings This section describes how to configure Routings Page 28 of 67 . 2.B. 3. In the Routing Name field. click the Routings tab. On the Service Operations component. Adding Routing Definitions 1. The Routings page appears. enter a name for the routing.

By default. Page 29 of 67 . PeopleSoft Integration Broker automatically populates this information when you select the service operation.) Check the box to activate the routing. 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.Routing Name Indicates the name of the routing definition. indicates that the PeopleSoft system generated the routing definition. If any of the referenced nodes are inactive. PeopleSoft Integration Broker automatically populates this information. (Optional. you cannot activate the routing. Indicates the version of the service operation selected. new routing definitions are active. Indicates the service operation type. Description of the routing definition. Enter the name of the sending node. (Optional. This name is specified when you add a routing definition to the system. Enter the name of the receiving node. When selected.) Enter comments about the routing definition. If you access the Routings component from the Service Operations-Routing tab.

Writing Publishing and Subscription People Code a.SyncRequest() .This is the code to publish the Data in the form of a Rowset Page 30 of 67 . Whenever the component is saved.  &response is nothing but the acknowledgment returned by the Target application subscription code.6.Publish(). . Publishing ASync Message &MSG. Publishing Sync Message Write the following code for the SavePostChange of the Main Record Field as shown below. b.This code publishes the message with the data in the current rowset to the app messaging services. the SavePostChange code is triggered:  &request.

c. d. Async Subscription: Page 31 of 67 . Sync Subscription Subscription for Sync message is written on the OnRequest Event of the Message as shown below.

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. The Overview page shows us the list of all the message channels along with the counts of instances for each status on the page. This can be decided after looking into the Details to find the various Errors that occurred. Message Monitor gives us the current state of all the messages that were published/subscribed. Check the message monitor for the first time. Message Monitor-To view the inbound and outbound messages: Add a new row of data on the main Components and save the components. We can select the Publishing Node to filter the results as shown above.e. Page 32 of 67 .

Look for the Message Errors Page 33 of 67 .

you will find the new rows existing here also. On the Main page of the Monitor Once the message is published. If the PeopleCode to insert the rows using the RowSet is correct. This is the actual way the data is published to the external Application using the XML tags.The XML viewer shows the XML Content that the server publishes. 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. the status changes to ‘Done” as shown below for a give message Channel. Page 34 of 67 . Once you see the status of your message as ‘Done’.

49 Object Node Queue Message Service Operations. a. b. Default Namespace: Pre-8.48. Transactions and Properties tabs are missing from the Portal Node Definitions.48. Page 35 of 67 . Permission list: Pre-8. this should be a good default to pick up as most likely this permission list was setup explicitly for IB.48 onwards and pre 8.48: This value can be changed using Service Configuration PIA and be able to assign each service to a different namespace. Enhanced Features of Integration Broker in People Tools 8.48: Channels can be added to permission list which specifies who can monitor a particular channel.4x Objects Node Channel Message Node transactions and relationships Service Message and Subscription People Code People Tools 8.48: These values can be changed using Service Configuration PIA page to assign the service to a different permission list.48: None In 8.7. and Routings Application classes and service operation handlers Below is the comparative study of Intergration Broker usage between People Tools 8.48 & onwards Below is a description of the related message objects between 8.48 / 8. also can services belonging to multiple permission lists. c. Service Operation Versions. People Tools 8. In 8.4X and 8.

48: “Properties” hyperlink on the gateways page directs to the Gateway Properties file page.48 d.The navigation is: PeopleTools  Integration Broker  Node Definitions Pre-8.48 PeopleTools is: PeopleTools  Integration Broker  Integration Setup  Nodes PeopleTools 8.48 version The navigation in 8. Pre 8. Page 36 of 67 .

48: When clicked on the “Gateway Setup Properties” hyperlink on the Gateways page. The “Advanced Properties Link” on PeopleSoft Node Configuration page directs to the Gateway Properties file page.48 Version The navigation is: Page 37 of 67 . a new page “PeopleSoft Node Configuration” appears.In 8. The navigation is: PeopleTools  Integration Broker  Gateways Gateways page in Pre 8.

48 e. create a message definition by assembling. The result is a rowset that doesn’t match to and existing rowset structure in the application. and process these messages. and from those records to include in the message.48 PeopleSoft Node Configuration Page in PeopleTools 8. organizing them into a hierarchy. Message Creation: Pre 8.48: Message definitions can be created only in the Application Designer. Use the PeopleCode Rowset and Message classes to generate. send. receive.PeopleTools  Integration Broker  Configuration  Gateways Gateways page in PeopleTools 8. Page 38 of 67 . There are two types of messages:  Rowset-based messages For hierarchical data based on PeopleSoft records.

but you do not insert any records.Rowset-based messages These messages can have virtually any structure and content. g. you can also use the SoapDoc class to generate and process these messages. granting security access to new message channels is required to see transaction information in the Integration Broker Monitor. using service operation handlers. A container message is a nonrowset-based message that holds one or more part messages. Users then use wizard-driven pages for generating. Services-Oriented Architecture Overview PeopleTools 8. Four types of messages are available:  Rowset-based For hierarchical data that is based on PeopleSoft records. to be used in a container message. The result is a rowset that doesn’t need to match an existing rowset structure in the application. Moreover. Users create services and service operations that contain message. receive. The transport mechanism for services and service operations is a message container.48: All Integration Broker security is now based at the service operation Level. The message definition serves as a placeholder for the actual message.  Nonrowsetbased messages These messages can have virtually any structure and content.48: New feature It features a services-oriented architecture for integrations. but you do not insert any records. receive and process these messages. For asynchronous integrations. Processing logic is created using application classes and then the logic is associated to service operations using PeopleCode handlers. and process these messages. All processing logic is defined in service operations. and process these messages. Running and Pausing Queues in the Service Operations Monitor Pre 8.A container message must contain all rowset-based messages or all nonrowset-based message parts.48: If you create new message channels. You create a message definition. you create a message definition by assembling records. define two messages: one for the request and one for the response In 8. Messages do not contain any processing logic. define a single message. Non. has been eliminated so the Queue Status Component will allow any user to run or pause queues. you must grant users access to them to view or edit channel information. as well as the messages contained within them. you can also use the SoapDoc class to generate and process these messages. send. In 8. Use the PeopleCode XmlDoc and operation classes to generate.48: Message definitions can be created in the Pure Internet Architecture. If you’re handling Simple Object Access Protocol (SOAP) compliant data. and selecting fields messages from those records to include in the message. f. Use the PeopleCode Rowset and operation classes to generate. If you’re handling Simple Object Access Protocol (SOAP) compliant data. Queue Security. formerly channel security. send. You create a message definition. For synchronous integrations. send. Use the PeopleCode XmlDoc and Message classes to generate. organizing them into a hierarchy. receive.  Container messages  Message parts Message parts are rowset-based messages or nonrowset-based messages that you designate as a part message. The message definition serves as a placeholder for the actual message. Page 39 of 67 . Users can view messages only in channels to which they have read access. providing and consuming WSDL with integration partners. routing information and Processing logic. All edit actions require write access.

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. 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. • This connector is also now segment-aware. The system now performs the processing for these items internally. • Simple File target connector. j. i. • HTTP target connector. On check box. Enabling the Performance Statistics Feature PeopleTools 8. PSADMIN Settings The following PSADMIN settings have been removed: • Handler Status Check Count. • FTP target connector. To configure a node to handle segmented messages: Page 40 of 67 . • Tuxedo Queue Status Check Count.48: New feature Use the Monitor Setup Options page in the Service Operations Monitor to enable the Performance Statistics feature. 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. k. The Monitor Setup Options page features an IB Profile Status.48 In previous releases you enabled this feature in PSADMIN.h.

48 l. Segment aware check box in Node definitions in PeopleTools 8. 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. Integration Setup. uses it for the connection.Using this feature requires no setup of a receiving database and no publish and subscribe server processes configured and booted on the application server. Select a node with which to work and click OK. The Node Definitions page appears. Page 41 of 67 . Integration Broker. 3. The handler Tester allows developers to test service operation handlers. Integration Gateway Enhancements: Jolt Session Pooling PeopleTools 8. The default value is 10. Select People Tools. 5. m. Select the Segment Aware box. The navigation is: PeopleTools  Integration Broker  Integration Setup  Nodes  Node Definitions. 2. 4. Click the Save button. Integration Broker Handler Tester The Integration Broker Handler Tester replaces the Integration Broker Event Tester in PeopleTools 8.48: New feature The integration gateway maintains a pool of Jolt sessions to handle requests between itself and the integration engine.1.48.connection Set this property equal to the maximum number of sessions to maintain in the pool. Node Definitions.Integration Broker Handler Tester executes all of the PeopleCode on your server with full debugging capabilities without affecting other developers.properties file using the following property: ig. The integration gateway accesses a Jolt session from the pool.

The navigation is: PeopleTools  Integration Broker  Service Utilities  Handler Tester Integration Broker Handler Tester in PeopleTools 8.Password q. Integration PeopleCode Pre 8. These integrations are accomplished using a combination of PeopleSoft Integration Broker and adapters included in a third-party tool.5.properties file: ig.48.48: New feature PeopleSoft provides you with the ability to create inbound and outbound integrations with enterprise resource planning (ERP) systems.48 n. iWay SOAPswitch. IWay SOAPswitch is an installation option during the PeopleTools installation. • • • Microsoft Windows 2003 Server HP-UX 11.5 is an installation option provided with PeopleTools 8. Page 42 of 67 .3. Platforms Supported PeopleTools 8.48: New feature The following new platforms are supported for PeopleTools 8.48: Messaging logic was attached to individual messages. p. iWay SOAPSwitch Enhancements PeopleTools 8. JMS Provider Password The following parameter has been deprecated and removed from the integrationGateway. iWay SOAPswitch version 5.23 Itanium 64-bit RHEL 3.0 (Red Hat Linux) o.JMSTargetConnector.48.JMSProvider.jms.

The navigation is: PeopleTools  Integration Broker  Web Services  Provide Web Service Provide Web Service Wizard in PeopleTools 8. In addition.48: With the new services-oriented architecture. Instead of the logic getting attached to messages. users now extend a set of delivered application classes to create messaging logic.4x systems.In 8. Many of the methods and functions of the Message object from previous releases have been moved to the IntBroker object or deprecated. External sources include WSIL repositories and UDDI repositories. A WSDL preview feature enables you to copy and paste generated WSDL to file as well. Page 43 of 67 . r. Provide/Consume Web Services PeopleTools 8.48 features a Provide Services wizard and a Consume Services wizard.48 The Consume Services wizard enables you to import WSDL from PeopleSoft and external sources. there is a new object called IntBroker. Handlers are then defined on a service operation. it gets associated to handlers. You can export WSDL to the Integration Broker WSDL repository.48: New feature PeopleTools 8. WSIL repositories and UDDI repositories. The wizard also enables you to import WSDL from legacy PeopleTools 8. The Provide Services wizard enables you to generate WSDL documents from Integration Broker metadata to provide to integration partners.

There are many field name changes and several new options for monitoring integrations.The navigation is: PeopleTools  Integration Broker  Web Services  Consume Web Service Consume Web Service Wizard in PeopleTools 8. Service Operations Monitor The Integration Broker Monitor has been renamed the Services Operations Monitor and modified to monitor services and services operations.48 s. including the ability to cleanup segment data. The navigation is: PeopleTools  Integration Broker  Service Operations Monitor Page 44 of 67 . The component has a different format and is now broken into Monitoring and Administration Sub components.

48: In this PeopleTools release. The service operation is provided in real-time. In 8. Introspection and Deployment Validation PeopleTools 8.Service Operation Monitor Broken into Monitoring and Administration Components t. channel name and pub ID were used in combination to create a unique ID for the transaction. transaction IDs replaces publication IDs (pub IDs) from previous PeopleTools 8. The sending asynchronous system expects the receiving system to send a synchronous response back. Creating BPEL Process-Based Services PeopleTools 8. The application server assigns a unique transaction ID to each inbound and outbound transaction. Transaction IDs Replace Publication IDs Pre 8.48: New feature The Introspection and Deployment Validation component enables you to introspect other PeopleTools 8. w. Service Operation Types: Service operation types determine the type of message processing. The navigation is: PeopleTools  Integration Broker  Integration Setup  Service Operations Page 45 of 67 .48 supports integrations with BPEL process-based services.48 nodes and create point-to-point routings. Asynchronous to Synchronous u. Processing on the sending system continues without a response from the receiving system. PeopleSoft has replaced that combination with a transaction ID that uniquely identifies a transaction.48 supports creating services from PeopleSoft component interface records and their corresponding methods. The sending asynchronous system transforms the response and puts it back in the queue for asynchronous consumption.4x releases. 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. Introspection can create point-to point routings on the local node when the service operation name and version name match exactly. and it is processed sometime in the future. the response is not processed on the same thread as the response. Unlike a synchronous operation type. v. Asynchronous – One Way Synchronous The service operation is queued and sent in near real-time. Processing on the sending system does not continue until it receives a response from the receiving system. The sending system's asynchronous process sends a synchronous request to a remote system. x.48: Message node. Creating Component Interface-Based Services PeopleTools 8.

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

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 queues using the Queue Definitions page.The navigation is PeopleTools  Integration Broker  Integration Setup  Nodes IB Throttle Threshold field on Node Definitions page. Create messages using the Message Builder component.48 Page 49 of 67 . The navigation is: PeopleTools  Integration Broker  Integration Setup  Messages Message Definition Page in 8. dd. Page-Based Message and Message Queue Management PeopleTools 8.

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

WSIL URL The Node Definition page features a WSIL URL field used in conjunction with introspection and deployment validation on external nodes. This SOAP template can then be used in the Handler Tester. Generate SOAP Template PeopleTools 8. This enhancement applies to asynchronous messages only.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. The system now performs the processing for these items internally. Transformation Tester or Send Master to test SOAP messages. Exception Handling for Synchronous Message Processing PeopleTools 8. For example. ii.48: New feature The AS2 listening connector and target connector implement correlation IDs in Message Disposition Notifications (MDNs). PSADMIN Settings The following PSADMIN settings have been removed: • Handler Status Check Count. 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.Default User ID field on Node Definitions Page hh.48: New feature The Generate SOAP template utility enables you to create a SOAP template for any service for which WDSL has been generated. ll. jj. if any of the synchronous requests error. the component is not rolled back. This type of exception handling applies to outbound synchronous requests only. you have the option to select the User Exception check box on the routing definition for the service operation. if 10 synchronous requests are performed in parallel (threaded sync request). AS2 Listening and Target Connectors PeopleTools 8. • Tuxedo Queue Status Check Count. including outbound multi-threaded synchronous requests. kk. Page 51 of 67 . When the User Exception check box is select.

06 product patch.48. the Service Administration .The navigation is: PeopleTools  Integration Broker  Service Utilities  Generate SOAP Template Generate SOAP Template page mm.Routings page now features a Delete Duplicate Routings section that enables you to search for duplicate routings in the system and delete them. 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. The navigation is: PeopleTools  Integration Broker  Service Utilities  Service Administration Page 52 of 67 .

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

• Publication Contract Is in NEW Status Possible causes are: • • • • • • Sending queue is paused. No outbound routings exists for the service operation. • 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. Publication contract is in WORKING status. Publication contract stays in RETRY status. • Publication Contract Stays in RETRY Status Possible causes are: • • • The remote node cannot be pinged successfully. Publication contract is in ERROR status. After an unsuccessful ping. Publication contract is in TIMEOUT status. either because it crashed or it was brought down. Sending domain is not active. or Timeout.8. Single threading on the application server is slowing processing. Sending node is paused. which will hold up the message queue. Error. query the table PSNODESDOWN.properties file. Publication PeopleCode is incorrect. the publication contract will be processed when the remote node comes back up. Troubleshooting • Publication Process Problems Possible publication process problems include: • • • • • • Publication contract is not created. • Publication Contract Is Not Created Possible causes are: • • • No publication PeopleCode exists. a row may be added to the table PSNODESDOWN. Processing should continue when the pub/sub system on the other machine comes back up. Publication contract is in NEW status. Receiving Node URL is incorrect in integrationGateway. Previous service operation had a status of Retry. Publication Dispatcher crashed or was brought down. No publication handler is available. Page 54 of 67 .

Receiving PeopleSoft node has not been added to single signon. Queue routing rules not set up properly. • Subscription Contract Is in NEW Status Possible causes are: • • • • Application Server down. Service operation version on target is not active. Subscription contract is in EDIT status. Subscription contract is in NEW status. The Subscription Dispatcher has crashed or has been brought down. Pub/Sub processes not configured on Application Server domain. Subscription contract is in WORKING status. Receiving Node is not defined in the integrationGateway. Page 55 of 67 . The source node is not defined in the target database. Subscription contract is in ERROR status. • Subscription Process Problems Possible subscription process problems include: • • • • • • Subscription contract is not created. • Subscription Contract Is not Created Possible causes are: • • • No handler exists for the service operation. Subscription contract is in STARTED status. Service operation has not been granted security access on the receiving system. verify that: The reply is incorrectly routed. • Publication Contract Is in ERROR Status Possible causes are: • • • • • • • • • • Receiving node user profile not authorized to service operation. Service operation handler is missing method. Handler PeopleCode is bad. Remote application server is down. Service operation is not active on the receiving system. check Gateway for correct machine address of target node.• Publication Contract Is in TIMEOUT Status Possible causes are: • • • An exception occurred on the target application server (look in APPSRV. Inbound routing is not set up on the receiving system. Receiving queue is paused. Bad XML syntax.LOG file for details).properties file.

Previous service operation had errors or timed out. • Other Possible Problems a. b. Service operations are being processed in an incorrect order. No row was inserted into PSAPMSGSUBPRCID. Service operation instance stays in NEW status. Queue is PAUSED. 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. Service operation is not created. Page 56 of 67 . 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. Service operation instance stays in STARTED status.• • Receiving node is paused. • • • • • • • • Other possible problems include: Cannot find service operation in Service Operation Monitor. which causes FULLSYNC service operations to error out when the transaction is subscribed before the header. c. Service operation handler PeopleCode errors exist. Target component is not valid. 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. • Subscription Contract Is in WORKING Status Possible causes are: • Subscription Handler crashed while processing message. Service operation instance stays in WORKING status. • Subscription Contract Is in ERROR Status Possible causes are: • • • • • Queue property if Ordered enables subscription contracts to go in random order. Unable to ping a node. Cannot Find Service Operation in Service Operation Monitor Possible causes is that filtering is set in the Service Operation Monitor.

and the Message Dispatcher will retry the message. • Copy URL in browser address. Queue Is PAUSED rPossible cause is that some queues are delivered as paused.d. • The Gateway is not configured properly. • The Message dispatcher processing the message is on another machine. • The Message Handler processing the message is on another machine. • The Message Handler working on the message is blocked. and either the machine or the application server domain is down. The Message Dispatcher crashed or was brought down. • The Gateway URL is incorrect. • g. and either the machine or the application server domain is down. • • • • f. • Page 57 of 67 . Service Operation Instance Stays in NEW Status Possible causes are: The Application server is down. h. Service Operation Instance Stays in WORKING Status Possible causes are: • Message Broker Handler crashed. verify that the URL is correct. all service operations with the same queue or subqueue are in the same queue. The item is not at the top of the queue. Service Operation Instance not Created Possible cause is that the service operation is inactive. processing will resume when Message Handlers come back up. • The application server for the node is down. you should see: • PeopleSoft Integration Gateway • PeopleSoft Listening Connector • Status: ACTIVE i. The service will time out. Unable to Ping a Node Possible causes are: • The web server for the Gateway is down. e. Pub/sub services are not configured on the Application Server domain. Service Operation Instance Stays in STARTED Status Possible causes are: All Message Handlers crashed or were brought down. Change the status to Run for the service operations to process from New to Working.

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. BUD_PERIOD_CALENDAR_SYNC.Versio n_1 ACCOUNT_CHARTFIELD_SYNC.Version_1 BUDGET_REF_CF_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.Detail Calendar Data from Financials that defines Accounting Periods BUS_UNIT_FS_FULLSYNC.Version_1 ALTACCT_CF_SYNC.Versi on_1 BUD_PERIOD_CALENDAR_FULLSY NC Asynchronus COMMIT ACCTG CALENDAR D DETAIL HRMS Integration with FSCM .Version_1 CHARTFIELD1_SYNC Asynchronous CHARTFIELD1 Incremental update of ChartField1. Below excel sheet have PeopleSoft delivered Integration points Service Operati on Type Asynchronus Asynchronus Asynchronus Asynchronus Asynchronus Integration Point ACCOUNT_CHARTFIELD_FULLSYNC. BUD_PERIOD_CALENDAR_FULLSYNC. CHARTFIELD2_FULLSYNC.Version_1 BUS_UNIT_GL_FULLSYNC Asynchronus BUSINESS UNIT TABLE GL Bus Unit GL Full Sync BUS_UNIT_PC_FULLSYNC. Incremental update of Alternate Account ChartField.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_PC_FULLSYNC Asynchronus BUSINESS UNIT TABLE PC Projects Business Unit Prompt CHARTFIELD1_FULLSYNC.Version_1 BUS_UNIT_FS_SYNC Asynchronus BUSINESS UNIT TABLE FS Incremental integration of Business Units between Financials and HRMS BUS_UNIT_GL_FULLSYNC. REFERENCE Incremental update to budget reference ChartField.Version_1 CHARTFIELD1_FULLSYNC Asynchronous CHARTFIELD1 Load ChartField1.Version_1 BUDGET_REF_CF_FULLSYNC.9.Version_1 CHARTFIELD2_FULLSYNC Asynchronous CHARTFIELD2 Load ChartField2 Page 58 of 67 . CHARTFIELD1_SYNC. REFERENCE Load budget reference ChartField. PS delivered EIP points PeopleSoft have some delivered messages and Integration points.

JOBCODE_SYNC.Version_1 DETAIL_CALENDAR_FULLSYNC Asynchronous DETAIL CALENDAR DATA DETAIL_CALENDAR_SYNC. FUND_CF_SYNC. HR_CHARTFLD_COMBO_SYNC. CLASS_CF_FULLSYNC. DETAIL_CALENDAR_FULLSYNC.Version_1 HR_CHARTFLD_COMBO_SYNC Asynchronous ACCT CODE TABLE Incremental update of ChartField combinations. CHARTFIELD3_FULLSYNC.Version_1 CLASS_CF_FULLSYNC Asynchronous CLASS_CHARTFIELD Load Class ChartField.Version_1 COUNTRY_FULLSYNC Asynchronous COUNTRY TABLE Country Table COUNTRY_SYNC. COUNTRY_FULLSYNC.5.Version_1 CLASS_CF_SYNC Asynchronous CLASS_CHARTFIELD Incremental update to Class ChartField.Version_1 HR_ACCT_CD_LOAD Asynchronous ACCT CODE TABLE AE:Publish and subscribe to ChartField Account Codes.Version_1 FUND_CF_SYNC Asynchronous FUND TABLE Load fund ChartField.Detail Calendar Data from Financials that defines Accounting Periods.Version_1 JOBCODE_SYNC Asynchronous Jobcode Setup Sync JOURNAL_GENERATOR_APPL_ID_SYNC.Version_1 CHARTFIELD3_FULLSYNC Asynchronous CHARTFIELD3 Load ChartField3 Integration Point CHARTFIELD3_SYNC.Version_1 DEPT_FULLSYNC Asynchronous DEPARTMENT TABLE Full table replication of Departments between Financials and HRMS DEPT_SYNC. JOURNAL_GEN_APPL_ID_FULLSYNC. FUND_LOAD. Page 59 of 67 .CHARTFIELD2_SYNC.V ersion_1 JOURNAL_GENERATOR_APPL_ID_ SYNC Asynchronous JOURNAL GENERATOR TEMPLATE Publish and subscription of Journal Generator template.Versio n_1 JOURNAL_GEN_APPL_ID_FULLSY NC Asynchronous JOURNAL GENERATOR TEMPLATE Full Table publish and subscription of Journal Generator Template.Version_1 DEPT_SYNC Asynchronous DEPARTMENT TABLE Incremental synchronization of Departments between Financials and HRMS HRMS Integration with FSCM . CLASS_CF_SYNC. HR_ACCT_CD_LOAD.Version_1 Service Name CHARTFIELD3_SYNC Service Operati on Type Asynchronous Integration Set Name CHARTFIELD3 Description Incremental update of ChartField3.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.Version_1 COUNTRY_SYNC Asynchronous COUNTRY TABLE Country Table Sync DEPT_FULLSYNC.Version_1 FUND_LOAD Asynchronous FUND TABLE Publish and subscription of Fund Table. Inbound file publish after receiving flat file from E&G Financials 7.Version_1 CHARTFIELD2_SYNC Asynchronous CHARTFIELD2 Incremental update of ChartField2.

Versi on_1 PROJECT_STATUS_DEFN_FULLSY NC Asynchronous PROJECT STATUS DEFINITION Project Status prompt Page 60 of 67 .Version_1 PAYMENT_EXPENSES_REQUEST Asynchronous PAYROLL PAYSHEET PAYMENT REQUE Payment Expenses Request.Version_2 PROJECT_TEAM_FULLSYNC Asynchronous PROJECT TEAM Project Team prompt PROJECT_TEAM_SYNC.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 PROJECT_ACTIVITY_FULLSYNC Asynchronous PROJECT ACTIVITIES Proj Activity Full sync PROJECT_ACTIVITY_FULLSYNC.Version_1 POSITION_FULLSYNC Asynchronous Position Data Setup Sync POSITION_SYNC.Version_2 PROJECT_ACTIVITY_FULLSYNC Asynchronous PROJECT ACTIVITIES Syncing Project Activity PROJECT_ACTIVITY_SYNC. PROJECT_ACTIVITY_FULLSYNC. PROJECT_TEAM_FULLSYNC. Integration Point LOCATION_FULLSYNC.Version_1 LOCATION_SYNC Asynchronous LOCATION TABLE Location Table . OPER_UNIT_CF_SYNC.Version_2 PROJECT_TEAM_SYNC Asynchronous PROJECT TEAM Project Team prompt PROJECT_STATUS_DEFN_FULLSYNC.Version_1 OPER_UNIT_CF_FULLSYNC Asynchronous OPERATING UNIT CHARTFIELD Load Operating Unit ChartField. PROGRAM_CF_SYNC. POSITION_FULLSYNC.Version_1 OPER_UNIT_CF_SYNC Asynchronous OPERATING UNIT CHARTFIELD Incremental update of Operating Unit ChartField.Sync Message OPER_UNIT_CF_FULLSYNC.Version_1 PRODUCT_CHARTFIELD_SYNC Asynchronous ACCT CODE TABLE General Ledger sends ChartFIeld incremental updates to Payroll for North America. PRODUCT_CHARTFIELD_SYNC.Version_1 PROJECT_ACTIVITY_SYNC Asynchronous PROJECT ACTIVITIES Proj Activity Sync PROJECT_ACTIVITY_SYNC. PAYMENT_EXPENSES_REQUEST.Version_2 PROJECT_ACTIVITY_SYNC Asynchronous PROJECT ACTIVITIES Syncing project activity PROJECT_FULLSYNC.Version_1 POSITION_SYNC Asynchronous Position Data Setup Sync PRODUCT_CHARTFIELD_FULLSYNC.Version_1 PROGRAM_CF_SYNC Asynchronous PROGRAM_CHARTFIELD Incremental update of program ChartField.LEDGER_DEFN_SYNC.Versio n_1 PRODUCT_CHARTFIELD_FULLSYN C Asynchronous ACCT CODE TABLE General Ledger sends ChartFIeld data to Payroll for North America.Version_1 PROJECT_FULLSYNC Asynchronous PROJECT TABLE Full synchronization of the Projects table.Version_1 LEDGER_DEFN_SYNC Asynchronous STUDENT FINANCIALS GL INTERFAC Incremental table synchronization of ledger definition.

Version_1 RES_TYPE_CAT_LINK_SYNC Asynchronous PROJECT TYPE-TO-CATEGORY LINK Relate ResTypes and Categories SETID_INITIALIZE.Integration Point PROJECT_STATUS_DEFN_SYNC.Version_1 RESOURCE_TYPE_FULLSYNC Asynchronous PROJECT RESOURCE TYPE Resource Type Prompt RESOURCE_TYPE_SYNC.Version_1 PROJECT_STATUS_SYNC Asynchronous PROJECT STATUS Project Status PROJECT_SYNC.Version_ 1 RESOURCE_SUB_CAT_FULLSYNC Asynchronous PROJECT RESOURCE SUBCATEGORY Resource SubCategory Prompt RESOURCE_SUB_CAT_SYNC.Version_1 PROJECT_SYNC Asynchronous PROJECT TABLE Incremental synchronization of the Projects table.Version_1 SETID_INITIALIZE Asynchronous TABLE SET CONTROL Setid STATE_FULLSYNC.Versi on_1 PROJ_ACTIVITY_STATUS_FULLSY NC Asynchronous PROJECT ACTIVITY STATUS Project Activity Status Message PROJ_ACTIVITY_STATUS_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 RESOURCE_CAT_FULLSYNC.Version_1 RESOURCE_TYPE_SYNC Asynchronous PROJECT RESOURCE TYPE Resource Type Prompt RES_CAT_SUB_CAT_LINK_FULLSYNC.Version_1 PROJECT_STATUS_FULLSYNC Asynchronous PROJECT STATUS Project Status PROJECT_STATUS_SYNC.Version_ 1 RES_TYPE_CAT_LINK_FULLSYNC Asynchronous PROJECT TYPE-TO-CATEGORY LINK Relate ResTypes and Categories RES_TYPE_CAT_LINK_SYNC.Version_1 RESOURCE_SUB_CAT_SYNC Asynchronous PROJECT RESOURCE SUBCATEGORY Resource SubCategory Prompt RESOURCE_TYPE_FULLSYNC.Version_1 RESOURCE_CAT_SYNC Asynchronous PROJECT RESOURCE CATEGORY Resource Category Prompt RESOURCE_SUB_CAT_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. PROJ_ACTIVITY_STATUS_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 RES_CAT_SUB_CAT_LINK_SYNC Asynchronous PROJECT CATEGORY-TOSUBCATEGOR Relating Category and SubCat RES_TYPE_CAT_LINK_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 .

Version_1 CM_TYPE_FULLSYNC Asynchronous COMPETENCY TYPE CM_TYPE_SYNC.Version_1 VENDOR_FULLSYNC Asynchronous VENDOR VENDOR_SYNC.Version_1 VENDOR_SYNC ACTION_REASON_SYNC Asynchronous VENDOR ACTION_REASON_SYNC.Version_1 CLUSTER_COMP_FULLSYNC Asynchronous COMPETENCY CLUSTER Full table pub CM_CLUSTER_COMP CLUSTER_COMP_SYNC.Version_1 BUS_UNIT_HR_SYNC Asynchronous Full synchronization of accomplishments of a competency cluster table between HRMS 8.Version_1 CLUSTER_COMP_SYNC Asynchronous COMPETENCY CLUSTER Pub changes to CM_CLUSTER_COMP Full synchronization of a competency type between HRMS 8.Version_1 CLUSTER_ACCOMP_SYNC Asynchronous ACCOMPLISHMENT CLUSTER CLUSTER_COMP_FULLSYNC.9 and Fin/SCM 8.Version_1 CLUSTER_ACCOMP_FULLSYNC Asynchronous ACCOMPLISHMENT CLUSTER CLUSTER_ACCOMP_SYNC.9 and Fin/SCM 8.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.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.8 Service Pack 1 CM_TYPE_FULLSYNC.STATE_SYNC. Integration Point COMPETENCY_FULLSYNC1.Version_1 BUS_UNIT_AV_SYNC Asynchronous AV BUSINESS UNIT Contributor Rel Bus Unit Sync BUS_UNIT_HR_FULLSYNC.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.8 Service Pack 1 Incremental synchronization of a competency type between HRMS 8.9 and Financials Supply Chain 8.9 and Financials Supply Chain 8.Version_1 BUS_UNIT_HR_FULLSYNC Asynchronous BUS_UNIT_HR_SYNC.8 SP1 CLUSTER_ACCOMP_FULLSYNC. Send the incremental update of vendors to Payroll for North America from AP.Version_1 STATE_SYNC Asynchronous STATE TABLE State Table Message Incr Sync UOM_FULLSYNC. VENDOR_FULLSYNC. NA Payroll subscribes only to HRMS vendors.Version_1 UOM_FULLSYNC Asynchronous UNIT OF MEASURE Units of Measure Full Sync UOM_SYNC. Payroll of North America subscribes only to update of HRMS vendors.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.Version_1 COMBO_CF_EDIT_REQUEST Asynchronous COMBINATION EDIT FOR CHARTFIELD ChartField Combination validation request.9 and Financials Supply Chain 8.8 SP1 Incremental synchronization of accomplishments of a competency cluster table between HRMS 8.8 Service Pack 1 Page 62 of 67 .Version_1 CM_TYPE_SYNC Asynchronous COMPETENCY TYPE COMBO_CF_EDIT_REQUEST.Version_1 Asynchronous Action Reason Setup Sync ACTUAL_TIME_ADD.

Version_1 COMPETENCY_SYNC3 Asynchronous COMPETENCY TABLE CORPORATE_CARD_FULLSYNC.Version_1 CORPORATE_CARD_SYNC Asynchronous CREDIT CARD MERCHANT Corporate Card Vendors COUNTRY_FULLSYNC.Version_1 DEPT_SYNC Asynchronous DEPARTMENT TABLE Dept Sync Incr.9 and Financials Supply Chain 8.8 Service Pack 1 Incremental synchronization of a competency table between HRMS 8.8 Service Pack 1 Incremental synchronization of a competency table between HRMS 8.Version_1 COMPETENCY_SYNC2 Asynchronous COMPETENCY TABLE COMPETENCY_SYNC3.9 and Financials Supply Chain 8.Version_1 CORPORATE_CARD_FULLSYNC Asynchronous CREDIT CARD MERCHANT Corporate Card Vendors CORPORATE_CARD_SYNC.Version_1 EARNINGS_SYNC Asynchronous EARNINGS TABLE Incremental update of Earnings Table Integration Point ESTIMATED_TIME_BATCH_ADD.9 and Financials Supply Chain 8.9 and Financials Supply Chain 8.8 Service Pack 1 Full synchronization of a competency table between HRMS 8.8 Service Pack 1 COMPETENCY_FULLSYNC3.Version_1 COUNTRY_FULLSYNC COUNTRY_SYNC Asynchronous COUNTRY TABLE Country Table Full Sync.Version_1 COMPETENCY_FULLSYNC2 Asynchronous COMPETENCY TABLE Full synchronization of a competency table between HRMS 8. EARNINGS_SYNC.COMPETENCY_FULLSYNC2.Version_1 FREQUENCY_FULLSYNC Asynchronous FREQUENCY TABLE Page 63 of 67 .Version_1 DIRECT_DEPOSIT_SYNC Asynchronous DIRECT DEPOSIT Direct Deposit Increment update EARNINGS_FULLSYNC.Version_1 EARNINGS_FULLSYNC Asynchronous EARNINGS TABLE Load Earnings Table.9 and Financials Supply Chain 8.9 and Financials Supply Chain 8.8 Service Pack 1 FREQUENCY_FULLSYNC.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. CURRENCY_FULLSYNC. Message DIRECT_DEPOSIT_FULLSYNC. DIRECT_DEPOSIT_SYNC.Version_1 Asynchronous COUNTRY TABLE Country Table Sync.8 Service Pack 1 Incremental synchronization of a competency table between HRMS 8.Version_1 CURRENCY_FULLSYNC Asynchronous CURRENCY CODE TABLE Currency Table Full Sync CURRENCY_SYNC. COUNTRY_SYNC.Version_1 COMPETENCY_SYNC1 Asynchronous COMPETENCY TABLE COMPETENCY_SYNC2.Version_1 COMPETENCY_FULLSYNC3 Asynchronous COMPETENCY TABLE COMPETENCY_SYNC1.Version_1 DIRECT_DEPOSIT_FULLSYNC Asynchronous DIRECT DEPOSIT Load Direct Deposit data.Version_1 DEPT_FULLSYNC Asynchronous DEPARTMENT TABLE Dept Full Sync DEPT_SYNC.Version_1 CURRENCY_SYNC Asynchronous CURRENCY CODE TABLE Currency Tbl Incremental Synch DEPT_FULLSYNC.

9 and Financials Supply Chain 8.Version_1 NAME_PREFIX_SUFFIX_SYNC Asynchronous NAME PREFIX/SUFFIX TABLES NID_TYPE_FULLSYNC. PAYMENT_EXPENSES_ISSUE.Version_1 HOLIDAY_DATE_FULLSYNC Asynchronous HOLIDAY DATES Holiday Date Full Sync Full synchronization of the Job code information between HRMS 8.Version_1 NID_TYPE_SYNC Asynchronous NID TYPE Incremental synchronization of the national ID types between HRMS 8.Version_1 FREQUENCY_SYNC Asynchronous FREQUENCY TABLE Incremental synchronization of a frequency table between HRMS 8.9 and Financials Supply Chain 8.Version_1 NID_TYPE_FULLSYNC Asynchronous NID TYPE Full synchronization of the national ID types between HRMS 8.9 and Fin/SCM 8.8 Service Pack 1 Incremental synchronization of the Job code information between HRMS 8.9 and Financials Supply Chain 8.Version_1 LOCATION_FULLSYNC Asynchronous Location Sync Full Message LOCATION_SYNC.Version_1 PAYMENT_EXPENSES_ISSUE Asynchronous PAYROLL PAYSHEET PAYMENT ISS Creates Payroll Paysheet for Payments Issued.9 and Fin/SCM 8.Versio n_1 PERSON_COMPETENCY_FULLSYN C Asynchronous PERSON COMPETENCY PERSON_COMPETENCY_FULLSYNC PERSON_COMPETENCY_SYNC.8 Service Pack 1 HOLIDAY_DATE_FULLSYNC.9 and Financials Supply Chain 8.FREQUENCY_SYNC.4sp1 NID_TYPE_SYNC.8 Service Pack 1 JOBCODE_FULLSYNC.Version_1 JOB_FAMILY_FULLSYNC Asynchronous JOB FAMILY JOB_FAMILY_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.Version_1 JOB_FAMILY_SYNC Asynchronous JOB FAMILY LOCATION_FULLSYNC.8 Service Pack 1 PERSON_COMPETENCY_FULLSYNC.9 and Fin/SCM 8.Sync Message Incremental synchronization of all the name prefixes or titles between HRMS 8.8 Service Pack 1 NAME_PREFIX_SUFFIX_SYNC.9 and Financials Supply Chain 8.8 SP1 Full synchronization of the personal data between HRMS 8.8 Service Pack 1 Full synchronization of the job family table between HRMS 8.Ve rsion_1 PAYMENT_EXPENSES_ACKNOWL EDGE Asynchronous PAYROLL PAYMENT REQUEST ACKNOW Provides Payroll's Acknowledgement of Expenses Request for Payment. PERSON_ACCOMP_FULLSYNC.4sp1 PAYMENT_EXPENSES_ACKNOWLEDGE.9 and Financials Supply Chain 8.9and Financials Supply Chain 8.8 SP1 PERSON_ACCOMP_SYNC.Version_1 JOBCODE_SYNC Asynchronous JOBCODE TABLE JOB_FAMILY_FULLSYNC.9 and Financials Supply Chain 8.Version_1 PERSON_ACCOMP_FULLSYNC Asynchronous PERSON ACCOMPLISHMENTS Full synchronization of accomplishments between HRMS 8.8 Service Pack 1 Incremental synchronization of the job family table between HRMS 8.9 and Fin/SCM 8.Version_1 JOBCODE_FULLSYNC Asynchronous JOBCODE TABLE JOBCODE_SYNC.Version_1 PERSON_BASIC_FULLSYNC Asynchronous PERSON CONTRACT Integration Point PERSON_BASIC_SYNC.Version_1 LOCATION_SYNC Asynchronous Location Table .8 Service Pack 1 PERSON_BASIC_FULLSYNC.Version_1 PERSON_ACCOMP_SYNC Asynchronous PERSON ACCOMPLISHMENTS Incremental synchronization of accomplishments between HRMS 8.Version_1 PERSON_COMPETENCY_SYNC Asynchronous PERSON COMPETENCY PERSON_COMPETENCY_SYNC Page 64 of 67 .

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.Version_1 RELEASE_REQUEST Asynchronous Get Release Label ROLE_ACCOMP_FULLSYNC.Version_1 ROLE_CLUSTER_SYNC Asynchronous ROLE CLUSTER Role Cluster Integration Point ROLE_COMP_FULLSYNC.Versio n_1 PERSON_VISA_CITIZEN_FULLSYN C1 Asynchronous PERSON VISA/CITIZENSHIP PERSON_VISA_CITIZEN_SYNC.Version_1 Service Name ROLE_COMP_FULLSYNC Service Operati on Type Asynchronous Integration Set Name ROLE COMPETENCIES Description Full table pub CM_ROLE_COMPS.8 Service Pack 1 Incremental synchronization of the passport and citizenship information between HRMS 8.Version_1 ROLE_ACCOMP_FULLSYNC Asynchronous ROLE ACCOMPLISHMENTS Role Accomplishments Full Sync ROLE_ACCOMP_SYNC.Version_1 PERSON_EDUCATION_SYNC Asynchronous Personal Education Sync PERSON_PRIOR_WORK_SYNC.Version_1 ROLE_ACCOMP_SYNC Asynchronous ROLE ACCOMPLISHMENTS Role Accomplishments Sync ROLE_CLUSTER_FULLSYNC.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.9 and Financials Supply Chain 8.PERSON_DIVERSITY_FULLSYNC.8 Service Pack 1 RATING_MODEL_FULLSYNC.Version_1 PERSON_DIVERSITY_FULLSYNC Asynchronous PERSON DIVERSITY Person Diversity Data PERSON_DIVERSITY_SYNC.9 and Financials Supply Chain 8.Version_1 ROLE_COMP_SYNC Asynchronous ROLE COMPETENCIES Pub changes to CM_ROLE_COMPS ROLE_FULLSYNC. ROLE_COMP_SYNC.Version_1 RATING_MODEL_SYNC Asynchronous RATING MODEL RELEASE_REQUEST.8 Service Pack 1 Incremental synchronization of the Rating Models between HRMS 8.Version_1 POSITION_FULLSYNC Asynchronous POSITION DATA Position Data Setup Sync POSITION_SYNC.Version_1 ROLE_FULLSYNC Asynchronous ROLE COMPETENCY / ACCOMPLISHMET Role Competency / Accomplishmet ROLE_SYNC.9 and Financials Supply Chain 8.Version_1 ROLE_CLUSTER_FULLSYNC Asynchronous ROLE CLUSTER Role Cluster Full Sync ROLE_CLUSTER_SYNC.Version_1 PERSON_VISA_CITIZEN_SYNC Asynchronous PERSON VISA/CITIZENSHIP POSITION_FULLSYNC.Version_1 RATING_MODEL_FULLSYNC Asynchronous RATING MODEL RATING_MODEL_SYNC.8 Service Pack 1 PERSON_VISA_CITIZEN_FULLSYNC1.Version_1 PERSON_DIVERSITY_SYNC Asynchronous PERSON DIVERSITY Person Diversity Data PERSON_EDUCATION_SYNC.Version_1 ROLE_SYNC Asynchronous ROLE COMPETENCY / ACCOMPLISHMET Role Competency / Accomplishmet Page 65 of 67 .

9 and Financials Supply Chain 8.Version_1 TL_WRKGRP_TBL_FULLSYNC Asynchronous HR TO FIN/FO FULLSYNC PUBLISH US_SOC_FULLSYNC.9 and FIN/SCM 8 SP1 TL_TASKGRP_TBL_FULLSYNC.Version_1 SETID_INITIALIZE Asynchronous TABLE SET CONTROL Setid STATE_FULLSYNC.8 Service Pack 1 Incremental synchronization of the employee’s job history data between HRMS 8.Version_1 SCHOOL_FULLSYNC Asynchronous SCHOOL TABLE SCHOOL_FULLSYNC SCHOOL_SYNC.Version_1 VENDOR_SYNC Asynchronous VENDOR Send the incremental update of HRMS vendors from Payroll for North America to AP.Version_1 US_SOC_FULLSYNC Asynchronous US SOC US SOC Setup Fullsync Integration Point US_SOC_SYNC.8 Service Pack 1 VOUCHER_BUILD.Version_1 TAX_LOCATION1_FULLSYNC Asynchronous HR TO FIN/FO FULLSYNC PUBLISH TBLSET_CONTROL_INITIALIZE.Version_1 SCHOOL_SYNC Asynchronous SCHOOL TABLE SCHOOL_SYNC SETID_INITIALIZE. and voluntary deduction withholding information to PeopleSoft Payables for payment.Version_1 VOUCHER_BUILD Asynchronous VOUCHERS WORKFORCE_FULLSYNC. Payroll for North American sends tax.Version_1 TITLE_FULLSYNC Asynchronous TITLE Full synchronization of the Title table between HRMS 8.Version_1 WORKFORCE_SYNC Asynchronous WORKFORCE DATA Page 66 of 67 .4sp1 TITLE_SYNC.Version_1 TIME_REPORTING_CODE_SYNC Asynchronous TIME REPORTING CODES Time Reporting Code Inc Update TITLE_FULLSYNC.Versi on_1 TIME_REPORTING_CODE_FULLSY NC Asynchronous TIME REPORTING CODES Time Reporting Code Full Table TIME_REPORTING_CODE_SYNC.Version_1 TITLE_SYNC Asynchronous TITLE Incremental synchronization of the Title table between HRMS 8.Version_1 STATE_SYNC Asynchronous State Table Message Incr Sync TAX_LOCATION1_FULLSYNC. Full synchronization of the employee’s job history data between HRMS 8.Version_1 TL_TASKGRP_TBL_FULLSYNC Asynchronous HR TO FIN/FO FULLSYNC PUBLISH TL_WRKGRP_TBL_FULLSYNC.SCHOOL_FULLSYNC.Version_1 TBLSET_CONTROL_INITIALIZE Asynchronous TABLE SET CONTROL Table set control TIME_REPORTING_CODE_FULLSYNC.Version_1 Service Name US_SOC_SYNC Service Operati on Type Asynchronous Integration Set Name US SOC Description US SOC Setup Sync VENDOR_SYNC.9 and Fin/SCM 8. garnishment.9 and Financials Supply Chain 8.Version_1 STATE_FULLSYNC Asynchronous State Table Full Sync STATE_SYNC.Version_1 WORKFORCE_FULLSYNC Asynchronous WORKFORCE DATA WORKFORCE_SYNC.

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

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

Sign up to vote on this title
UsefulNot useful