21
Demystify PeopleSoft Integration Broker Monitoring and Tools used by McMaster University Session #25826 Presented by Ernie Latif
Demystify PeopleSoft Integration Broker
Monitoring and Tools used by McMaster University
Session #25826
Presented by Ernie Latif
2016-08-02
Agenda
• About McMaster University
• Architecture overview
• Integration broker configuration objects
• Message life cycle
• Delivered monitoring tools
• Custom monitoring tool at McMaster
• Where to find more information
• Questions
2016-08-02
About McMaster University
• Founded in 1887 in Toronto and relocated to Hamilton in 1930.
• Over 30,000 total student population with over 6,800 staff
• Implemented the following Oracle/PeopleSoft applications:• Interaction Hub (Portal), FSCM 9.2, Data Warehouse 9.1 in 2013
• Campus Solutions 9.0 and HCM 9.2 in 2014/2015
• Currently a mix of PeopleTools 8.53 and 8.54
• Planning stages of application upgrades to Campus 9.2 and current PUM images (selective adoption) for all streams.
• Upgrade to PeopleTools 8.55 for all streams by end of 2017.
2016-08-02
Architecture overviewPeopleSoft to/from PeopleSoft
2016-08-02
Architecture overviewPeopleSoft to/from 3rd party application
2016-08-02
Integration broker configuration objects
Domains – refers to the application server(s) that have publication/subscription (pub/sub) services.
Nodes – Define application streams (instances) either PeopleSoft or Third Party. There is only one default local node in a system.
Messages – structure definition of data begin sent between nodes. Various types of messages: rowset, non-rowset (i.e. XML, SOAP).
Queues – used to manage and group messages. They can be either ordered or un-ordered.
2016-08-02
Integration broker configuration objects
Routing – defines the connection of a specific message to a node. Also holds details about any transformation to the node.
Handler – defines the code executed when a messages is received. Generally this is an application package.
Service Operations – brings together messages, queues, handlers and routings. Also holds security details. Basically defines how the message moves between systems.
Service – group of service operations.
2016-08-02
Message life cycle
Trigger a message withinthe application
Receive a message
2016-08-02
Message life cycle
Trigger a message within the application
Receive a message
Creates an operational instance
Opr Inst = New
2016-08-02
Message life cycle
Trigger a message within the application
Receive a message
Creates an operational instance
Opr Inst = New
Executes the service and
service operation
Opr Inst = Starting/Working
2016-08-02
Message life cycle
Trigger a message within the application
Receive a message
Creates an operational instance
Opr Inst = New
Executes the service and
service operation
Opr Inst = Starting/Working
Routing or Handler
transactions are created
Opr Inst = Done
PUB/SUB = New
2016-08-02
Message life cycle
Trigger a message within the application
Receive a message
Creates an operational instance
Opr Inst = New
Executes the service and
service operation
Opr Inst = Starting/Working
Routing or Handler
transactions are created
Opr Inst = Done
PUB/SUB = New
Transactions are processed
PUB/SUB =
Starting/Working
2016-08-02
Message life cycle
Trigger a message within the application
Receive a message
Creates an operational instance
Opr Inst = New
Executes the service and
service operation
Opr Inst = Starting/Working
Routing or Handler
transactions are created
Opr Inst = Done
PUB/SUB = New
Transactions are processed
PUB/SUB =
Starting/Working
Transactions completed
PUB/SUB = Done
2016-08-02
Delivered monitoring tools
Demo
2016-08-02
Delivered monitoring tools
2016-08-02
Delivered monitoring tools
2016-08-02
Custom monitoring tool used at McMaster
• PeopleSoft administrators were overwhelmed by errors and timeouts that were mostly due to network glitches and data.
• Found that most of the time we simply re-submit the message.
• Created a integration broker monitoring process that runs every 15 minutes in all streams that use IB.Logs any messages that are in Error or Timeout status.
If the message has less than 4 entries (log) for a specific transaction id then re-submit the message – setting the pub/sub status back to New.
If a message has been re-submitted 3 times without success then generate an error notification for a specific role and log it.
2016-08-02
Custom monitoring tool used at McMaster –Sample notificationThis notification was created by the IB monitor process. The following message has been re-submitted three times without success.
IB transaction : 235e4568-9473-11e5-8925-dd738c285afd
Status : ERROR
Pub Node : PSFT_HR
Sub Node : PSFT_EP
Queue : PERSON_DATA
Service Operation : PERSON_BASIC_SYNC
Error : Unable to find a Routing corresponding to the incoming request message.
You have received this message because you are in the notification group for this PeopleSoft stream.
2016-08-02
Custom monitoring tool used at McMaster –Impact assessment• Drastic reduction in the amount of time and resources required to monitor
integration broker.
• Engaged business analysts to triage the issue before assigning to the appropriate resource. As a result administrators are infrequently required to act.
• Issues are identified within an hour (business day) and dealt with.
• Demonstrates a more stable system to the end user.
• Process was deployed to our HR stream at the end of January 2016. As of June 1, 2016:622,432 messages were created or received.105 messages were found in error or timed out91 were automatically dealt with by the IB monitor process14 messages generated email notification and were resolved by the BSAs
2016-08-02
Where to find more information
docs.oracle.com
http://docs.oracle.com/cd/E66686_01/pt855pbr0/eng/pt/index.html
Products > Integration Tools
For general understanding > Integration Broker
For setting up and using > Integration Broker Administration
For monitoring > Integration Broker Service Operations Monitor
2016-08-02
Questions
Does integration broker change very much from PeopleTools 8.53 to PeopleTools 8.55?
More questions contact:
Ernie Latif
