Welcome to Scribd, the world's digital library. Read, publish, and share books and documents. See more
Standard view
Full view
of .
Look up keyword
Like this
0 of .
Results for:
No results containing your search query
P. 1
Integration Broker

Integration Broker

Ratings: (0)|Views: 22|Likes:
Published by Raghavender Raghu

More info:

Published by: Raghavender Raghu on Nov 04, 2012
Copyright:Attribution Non-commercial


Read on Scribd mobile: iPhone, iPad and Android.
download as DOC, PDF, TXT or read online from Scribd
See more
See less





PeopleSoft Integration Broker to perform asynchronous and synchronous messagingamong internal systems and third-party systems.Because of its modular design, Integration Broker can be reused in other integrations.The two major components of PeopleSoft Integration Broker are the integration gatewayand the integration engine. The integration gateway is a platform that manages the receiptand delivery of messages passed among systems through PeopleSoft Integration Broker.The integration engine is an application server process that routes messages to and fromPeopleSoft applications as well as tranforms the structure of messages and translates dataaccording to specifications that you define.The integration gateway resides on a PeopleSoft web server, and the integration engine isinstalled on an application server as part of the PeopleSoft application.
Integration Gateway Architecture
The integration gateway is a platform that manages the receipt and delivery of messages passed among systems through PeopleSoft Integration Broker. It supports the leadingTCP/IP protocols used in the marketplace today and provides extensible interfaces todevelop new connectors for communication with legacy, enterprise resource planning,and internet-based systems.Additional features include:
Backward compatibility for Extensible Markup Language (XML) links andPeopleSoft Application Messaging.
Listening connectors and target connectors that transport messages betweenintegration participants and the integration engine.
Basic logging information concerning message receipt, delivery, and errors.
Connection persistence with continuous open feeds to external systems throughconnectors, with full failover capabilities.
Transport protocol and message format management so that when messages reachthe integration engine, they have a PeopleSoft-compatible message format.
Architecture Elements
You use an integration gateway to receive and send messages among integration participant systems.
Listening connectors receive incoming messages and deliver the incoming requests to thegateway manager, which is a dispatcher for messages that flow through an integrationgateway. The gateway manager determines which target connector to use to properlydeliver the messages to their intended recipients. The target connector then delivers themessages to the intended recipients using the recipients’ preferred protocols.
Integration gateway architecture
Listening connectors and target connectors transport messages between integration participants and the integration gateway. These connectors support asynchronous andsynchronous message handling. Many connectors are configurable at the integrationgateway and system levels.
Listening Connectors
Listening connectors receive incoming data streams and perform services based on thecontent of the stream. They are invoked externally by other PeopleSoft systems and third- party systems.
Target Connectors
Target connectors initiate communication with other PeopleSoft systems or third-partysystems. A target connector might not receive a response from the target system duringeach operation, but every transmission requires a low-level acknowledgment.
PeopleSoft Integration Broker Connector SDK 
The integration gateway provides a fully extensible model for developing new connectors built to the interface specification of the PeopleSoft Integration Broker softwaredevelopment kit (SDK) by PeopleSoft customers, consultants, and applicationdevelopers.
Gateway Manager
The gateway manager processes every message that flows through an integration gatewayand maintains links to the other major integration gateway components, including targetconnectors, listening connectors, and each of the gateway services.Listening connectors invoke the gateway manager when they receive a message request.The gateway manager uses the messaging objects IBRequest and IBResponse todetermine how to route each message.The gateway manager uses a number of the gateway services during this stage to performoperations such as message validation. The gateway manager then invokes theappropriate target connector based on the content of the message object and waits for areply from the target connector. When the reply is received, the gateway manager forwards the reply to the calling listening connector.If an error occurs, the gateway manager uses the error handling service and works withthe service to prepare an error reply for the listening connector.
Integration Engine Architecture
The integration engine uses a variety of PeopleTools elements to create, implement,manage, and enhance integrations. Its modular architecture separates integrationdevelopment activities from administrative activities.The integration engine is a combination of PeopleSoft Application Designer definitions,PeopleSoft Pure Internet Architecture definitions, PeopleCode, and XSLT code, alongwith the underlying mechanisms that tie all these elements together. The underlyingmechanisms include the request handlers that process both inbound and outboundmessages according to the specifications in the development and administrative elements.
Transaction Types
PeopleSoft Integration Broker supports four types of messaging transactions. For anytransaction type, the application must invoke PeopleCode to generate and send amessage, or to receive and process a message.
Transaction TypeActions
Outboundasynchronous1.The application generates and sends a request message.2.One or more target system receives and processes the request

You're Reading a Free Preview

/*********** DO NOT ALTER ANYTHING BELOW THIS LINE ! ************/ var s_code=s.t();if(s_code)document.write(s_code)//-->