P. 1


|Views: 3,102|Likes:
Published by Prashant Prakash
PS Integration Broker
PS Integration Broker

More info:

Published by: Prashant Prakash on Apr 10, 2009
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





When the MIME request is received by the application server, the message is parsed and is used to build a
request object. The MIME structure is not propagated into the server.

Assuming the message parses without error, the application server must pre-process the message before the
request can actually be handled.

Pre-processing involves:

•authenticating the message, depending on the authentication scheme configured. If the request fails
authentication, an error is returned.

•determining if there is a transaction corresponding to the request in the Node Transaction table. Aside
from Ping messages, all incoming messages must resolve to a single, unique entry in this table. If a
suitable transaction cannot be found for a request, an error occurs.

•determining the message handler to invoke. Currently, there are three message types supported by
the integration broker: Ping, Synchronous, and Asynchronous. The message type determines the
handler code to invoke. Synchronous messages are passed to sync-specific code, and async
messages are passed to the publish/subscribe subsytem.

Once messages have been passed to their respective handlers, further processing is dictated by the data and
PeopleCode specific to a particular system. Async requests will be published, and subscription PeopleCode will be

2 This is not entirely true. One credential element that may be present is the one for “Cookies”. Obviously if this is
set, the app server would be right in assuming that the request came through the HTTP ListeningConnector.
Similarly, SOAP requests are passed into the app server in SOAP format. However, as a general rule the app
server is isolated from the details of the protocol and the general broker code on the server does not care what
listening connector was used for a given request.

© Copyright PeopleSoft Corporation 2001. All rights reserved.



executed. Synchronous messages may invoke PeopleCode, or in the case of Hub configurations the request may
immediately be routed to another external system.

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)//-->