Quick Links

What is Integration Broker?

PeopleSoft Integration Broker—your integration control center—connects business processes across application and enterprise boundaries using a hub and spoke model. An open standards-based middleware technology, PeopleSoft Integration Broker automates the routing and transformation of data between disparate systems—replacing costly and time-consuming manual programming. Native support for web service standards such as XML, SOAP, and WSDL and a full suite of packaged connectors delivered out of the box ensure that we have an integration solution to fit every situation. By using Integration Broker, you can create real-time collaborative business processes that span entire enterprise systems, today.

Packaged Connectors

All messages entering or leaving the Integration Broker pass through a single mechanism known as the Gateway. The Gateway is delivered with prebuilt connectors to receive and transmit traffic using various standard protocols such as HTTP or JMS. More importantly, PeopleSoft provides an environment for the development of new connectors to legacy systems, ERP applications, and web-based systems. In addition, all PeopleSoft applications are built with integration in mind from the start. Whether you have CRM, HCM, or another product line, we have prebuilt interfaces that enable seamless communication between our applications and also between third-party systems.

Routing

Central to any messaging architecture is routing. Routing ensures that the incoming message is delivered to the right receiving system(s), and that the requesting system has the appropriate security privileges.

 The Integration Broker also understands if the message needs to be sent in real time (synchronous), or if it is deferrable (asynchronous), and manages the queuing of deferrable messages. The queue can even be set up to handle message delivery based on predefined rules that assign differing priorities to message or system types (for example, always customer-order data messages first).

Transformation

Transformation is required to translate a message between different systems. This is much like translating a sentence from one language to another. The meaning of a sentence is the same in French or English, but unless some conversion is performed, neither person will understand the message. Similarly, the Integration Broker takes a system message and converts the data from one system’s format into another’s. This becomes extremely valuable when you consider the hub and spoke model described earlier. With the Integration Broker, after an application has been mapped once, the Integration Broker enables communication to any other system automatically. In the future, as the mapped system changes, there is only one place to modify the mapping, saving time and money.

Development and Monitoring Environment

Integral to the Integration Broker architecture is a development and monitoring environment. The development environment is used by programmers to map the complex relationships between systems. The developers determine how the Integration Broker should transform and route the messages, taking care to understand the various data schemas and business process rules that must be managed.

 In addition, the monitoring environment is a dashboard for the entire messaging process, giving the user a picture of all messages moving in and out of the Integration Broker. From this dashboard, administrators can view original messages, transformed messages, or delivery status. Or, they can perform higher-level operations such as canceling delivery or resubmitting a message.