Integration Broker

Integration broker is one of those areas of PeopleSoft that introduces a lot of terminology. You really need to get your head around this terminology before you can understand what's going on. Unfortunately, the documentation in PeopleBooks can be a little terse. So here's my understanding of the major concepts.

Gateways

Are the pathways between systems. There is always a LOCAL gateway in PeopleSoft which refers to the source PeopleSoft system. Other gateways may exist - for example when there are differences between PeopleTools versions.

Domains

Refer to PeopleSoft application server (tuxedo) domains for publish/subscribe (pub/sub) services. These are turned on at the application server and required for Integration Broker to work.

Nodes

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

Messages

Define the structure of the XML sent between nodes. The key difference between asynchronous and synchronous messages is acknowledgement - synchronous messages need to be acknowledge by the receiver, asynchronous ones don't. Web services typically use synchronous messages.

The SQL below will return the structure of your message if it is rowset based (uses PeopleSoft record definitions to define the structure).

select RF.FIELDNAME
from PSRECFIELD RF
where
    RF.RECNAME = 'MESSAGE_RECNAME'
    and not exists (
        select  1
        from    PSMSGFLDOVR MFO
        where   MFO.MSGNAME = 'MSGNAME'
        and     MFO.APMSGVER = 'VERSION_N'
        and     MFO.RECNAME = RF.RECNAME
        and     MFO.FIELDNAME = RF.FIELDNAME
        and     MFO.DONOTPUBLISH = 1
    )
order by RF.FIELDNUM;

Queues

Are used to manage and group messages so that all messages are sent through the multiple pipes. Queues are used for administration of integration broker to avoid stopping everything when something is wrong. For example you can pause a one queue for messages to the report architecture without say stopping messages to the finance system.

Routings

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

Handlers

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

Service Operations

Bring together messages, queues, handlers and routings. They essentially define how the message moves between systems.

Services

Group service operations into the conceptual service provided. For example, you might have a service based on a component interface. The service operations would be the methods (create/find/get/update/update data) and the service would be the interface to that component interface.

Further Information

Comments

Unless otherwise stated, the content of this page is licensed under Creative Commons Attribution-ShareAlike 3.0 License