PeopleSoft Integration Broker

Vijay ContinuServe

Integration Broker
Architecture

Integration Gateway, Integration Engine, Nodes & Messages

Services and Services Operations Handlers, Routings & Queues Application Messaging- Types Messaging flows Security

PeopleSoft Integration Broker provides service oriented architecture (SOA) technology that facilitates the transmission of synchronous and asynchronous service operations
PeopleSoft Integration Broker provides a mechanism for communicating with the outside world using XML files. Communication can take place between different PeopleSoft applications or between PeopleSoft and third-party systems. Enables disparate systems to share information in common manner.

PeopleSoft GFS (Customers)

Integration Process

PeopleSoft CIS (Accounts)

Events Customer created in PS GFS Message triggered from PS GFS to PS CIS Message subscribed in CIS Account created in CIS

Email System

Sender and a Recipient E-mail addresses made up of a user (part before @ sign) & a domain (part after @ sign) e-mail server that routes e-mail to Recipients domain Gateways Nodes Messages Services and Service Operations Queues Integration Engine

Building Blocks of Integration Broker

Gateways
Platform to manage the reciept and sending messages among the systems through IB. Resides on the PS Webserver. It knows nodes- i.e., for given node it knows server name, app server port, username & pass so that it can connect to nodes app server & push the message to IB running in that env. Kind of e-mail server

Integration Engine
App server process that routes the messages to and from the PS Applications and also transforms the messages with the given specifications.Installed on PS App server as part of the PS application.

Nodes
Define what application a message belongs to - any system that integration broker can talk to (including the local system) will have a node. Domain part of email address

Routings

Handlers Services

Used to link a service operation to a node, and can also specify transformation of a message.

Contain code and logic for sending/receiving/manipulating mesages.

Used to logically group a set of service operations.

Service Operations Domains

Bring together messages, queues, handlers and routings. They essentially define how the message moves between systems.
Refer to PeopleSoft application server (tuxedo) domains.

Queues
Used to manage and group messages so that all messages are sent through the multiple pipes Can be paused or running

Messages
Define the structure of the XML sent between nodes Asynchronous Synchronous Includes records and fields, & child records are nested under their parent records Only one Level 0 Record In terms of e-mail analogy, message name would be both User part of email address, & message itself would be Body of e-mail.

Configure Integration Gateway

Enable services by enabling pub/sub processes in App Server Give the PS Instance a unique name by changing Default local node Establish connection between App Server and Integration gateway by setting up PS listening connector Establish connection between Integration gateway and App Server by setting up PS target connector Make sure Domain Status is Active

Integration Broker Architecture

Synchronous Program waits for a successful response from remote system before it will continue
Asynchronous

More like email analogy Message is sent & program gets on with its life, assuming the message will be OK
Most PeopleSoft systems use Asynchronous messaging

Incoming request through PS IB

Outgoing request through PS IB

External System Sends a Request to PeopleSoft Integration Broker Request is Received by the Listening Connector Request is Processed by the PeopleSoft Target Connector Request is Received by the Application Server

Application Server Generates Request Request is Received by the PeopleSoft Listening Connector Request is Received by the Target Connector Response is Received by the Target Connector Response is Received by the PeopleSoft Listening Connector

This picture shows how PS IB communcates with 3rd party using sync and async App. Messages

When creating sales order, to make sure that sufficient order is in hand, for this a synchronous process is initiated to invoke a Web service in your inventory system for a real-time confirmation of sufficient quantity. The Integration Broker sends an XML message to the inventory Web service, and an XML message is sent back to the Integration Broker to acknowledge that the order can be fulfilled. The results of this process are displayed in the order entry page. The sales order is completed and saved. An XML Application Message is then delivered asynchronously to the two subscribing systems. The Application Messaging framework guarantees delivery of the order data to the two subscribing systems.

Thank You