Copyright © Cloud Software Group, Inc. All Rights Reserved
Copyright © Cloud Software Group, Inc. All Rights Reserved


Chapter 3 TIBCO ActiveMatrix Adapter for PeopleSoft : Adapter Services

Adapter Services
TIBCO ActiveMatrix Adapter for PeopleSoft provides the following services:
The features described in Adapter Overview are available in these services.
Figure 13 Services of the Adapter
Communication parameters, database connectivity parameters, polling rate, and many other parameters can be configured for these adapter services using TIBCO Designer.
Adapter services require certain TIBCO specific objects to be embedded in the PeopleSoft system at design time. These objects enable the design-time adapter (DTA) to capture the PeopleSoft Component Interfaces and Application Messages as schemas. These schemas are used by the adapter at runtime.
The following sections describe how these adapter services interact with the PeopleSoft environment to provide message connectivity.
Publication Service
A Publication Service detects changes to data in the PeopleSoft application and exports these changes to the TIBCO environment.
You can configure a Publication Service to publish data from the PeopleSoft application to applications that are configured to work within the TIBCO environment. Multiple Publication Services can be configured. You can give each Publication Service a unique name to distinguish among them when they are serving different PeopleSoft components.
The adapter gives you an option to choose a Publication Service based on two technologies: Component Interfaces and Application Messaging, which allow for CI Publication Services and Message Publication Services.
CI Publication Service
If you apply a Component Interface to the adapter’s Publication Service, the Component Interface determines which records and fields are published from PeopleSoft. It establishes the format of the outgoing message.
The publishing capability of the adapter enables it to capture user-entered data through a PeopleSoft Windows client and through a web browser.
If a Publication Service is using Component Interfaces (CI Publication Service), data capture at runtime requires the TIB Work Page to be inserted in the required component. The TIB Work Page must be inserted at design time. TIB Work Page enables data capture from the component at runtime. This data is written to a staging table, which is polled by the runtime adapter. The runtime adapter picks up the data and publishes it to the TIBCO environment.
TIB Work Page is bundled with the TIB_PS8_ADAPTER project. It implements the logic for capturing fields for publication at runtime.
Message Publication Service
When running as a Message Publication Service, the adapter uses PeopleCode provided with the adapter to capture data from PeopleSoft in a PeopleSoft message and to send it over HTTP to the adapter. The runtime Message Publication Service receives the message, processes it and publishes it to the TIBCO environment. It then sends back an acknowledgement to the PeopleSoft system.
Figure 14 Typical Publication Service Flow
Subscription Service
A Subscription Service inserts inbound data from the TIBCO environment into the PeopleSoft database. You can configure multiple Subscription Services. You can give each Subscription Service a unique name to distinguish between them when they are serving different PeopleSoft components.
The adapter gives you an option to choose a Subscription Service based on two different technologies: Component Interfaces and Application Messaging, which allow for CI Subscription Services and Message Subscription Services.
PeopleSoft client library (PSJOA.JAR) required since the adapter makes native API calls.
CI Subscription Service
The CI Subscription Service uses Component Interface with the Subscription Service. The adapter subscribes to messages, maps them to PeopleSoft schemas and inserts data into the PeopleSoft database using a Component Interface. In this case, the service determines which records and fields must be inserted into PeopleSoft. Because Component Interfaces have an associated component, all necessary business logic and validations are triggered. Only when the Component Interface parses the business logic and validations is the data committed to the PeopleSoft database.
Message Subscription Service
A Message Subscription Service inserts inbound message data from the TIBCO environment into the PeopleSoft database. The adapter subscribes for a message from the TIBCO Environment and builds an IB message. It, then, sends the message over JMS/HTTP to the respective Listener Connector. The Message Subscription Service supports two types of Listener Connectors: JMS Listener Connector and HTTP Listener Connector.
The JMS Listener Connector subscribes for the configured Topic/Queue. On receiving a message, the connector calls the Subscriber PeopleCode for the configured message.
The HTTP Listener Connector waits for a message to be written on it. On receiving the message, the connector calls the Subscriber PeopleCode for the configured message.
The Subscriber PeopleCode has the logic to build the RecordSet from the Message received from the adapter.
Figure 15 Typical Subscription Service Flow
PeopleSoft client library (PSJOA.JAR) required since the adapter makes native API calls.
Request-Response Service
A Request-Response Service receives requests from the TIBCO environment and sends the requests to a PeopleSoft system. When a response is returned to the adapter from the PeopleSoft system, the adapter sends the response to the TIBCO environment.
Figure 16 Typical Request-Response Service Flow
The adapter supports request-response scenarios with the Request-Response Service. When the adapter receives a request, it takes the requested data, converts it into a formatted PeopleSoft schema, and sends it to PeopleSoft using a Component Interface. The adapter then returns the response. A Request-Response Services can also be used to insert data into the PeopleSoft database depending on the incoming request (whether it is a query, insert, or an update).
Request-Response Invocation Service
A Request-Response Invocation Service receives requests from and sends responses to PeopleSoft system. The adapter receives a request from the PeopleSoft system (acting as a Request-Response client). The request is sent to an external application (acting as an RPC server) via the TIBCO environment. When a response is returned to the adapter from the external application, the adapter sends the response back to the PeopleSoft system.
Request-Response Invocation Service Using Target Connectors (TIBCO JMS/HTTP)
The Target Connectors, TIBCO JMS Connector and TIBCO HTTP Connector, are used to communicate with the PeopleSoft Adapter. The adapter uses the Target Connectors to invoke a Request-Response Invocation Service.
Whenever there is an addition or a modification to a given component, PeopleSoft invokes the appropriate PeopleCode (savePreChange or savePostChange) to handle the change. The PeopleCode helps create a message and sets XML data from the Resultset. It also makes a synchronous call to the Target Connector (TIBCO JMS/HTTP). The Target Connector (TIBCO JMS/HTTP) reads the reply message and sends it to the calling PeopleCode.
JMS-Based Communication
The JMS-Based TIBCO Target Connector receives a request from the PeopleSoft System as XML message data. The connector constructs a TIBCO JMS message and sends it as a Topic/Queue request to the adapter. The adapter converts the message to the configured schema and sends a request to an external RPC server. On receiving a reply from the external RPC server, the adapter sends the reply to the TIBCO Target Connector, which then sends the reply back to PeopleSoft. In case the adapter instance is not running, it returns an operation timed out error and throws out an invalid message exception.
HTTP Based Communication
TIBCO ActiveMatrix Adapter for PeopleSoft acts as an HTTP server that listens on a configured port. The HTTP Target Connector sends a request to the adapter as an IB message. The adapter converts the message to the configured schema and sends a request to an external RPC Server. On receiving a reply from the external RPC server, the adapter writes the reply back to the HTTP Target Connector.
Figure 17 Typical Request-Response Invocation Service Flow
Example Scenario
The PeopleSoft system can be configured to retrieve the Currency data from an external system by passing a Country Code to the external system. The PeopleSoft system invokes the adapter, which sends out a request and receives a reply from the external system. The adapter then sends the reply to the PeopleSoft system.

Copyright © Cloud Software Group, Inc. All Rights Reserved
Copyright © Cloud Software Group, Inc. All Rights Reserved