Integrating with Third-Party Systems

This section provides an overview of this scenario and discusses how to configure the system for this scenario.

For communications with third-party systems, messages can go through local or remote gateways.

Sending a message to a third-party system is the same as sending a message to a PeopleSoft Integration Broker node, except that the target connector that you select depends on the third-party system with which you are communicating.

Messages from third-party systems can enter the gateway through any of the listening connectors that are delivered with PeopleSoft Integration Broker or through a listening connector that you build. You cannot use the PeopleSoft listening connector for integrations with third-party systems, because it can accept messages only in the PeopleSoft internal format.

Image: Integrations with Third-Party Systems

This diagram shows the connectors that a PeopleSoft system can use to communicate with a third-party system and how the PeopleSoft system can communicate with third-party systems.

Integrations with third-party systems

This section discusses how to configure:

  • The PeopleSoft Human Resources system.

  • The PeopleSoft Human Resources integration gateway.

Configuring the PeopleSoft Human Resources System

On the PeopleSoft Human Resources system:

  1. Define a local integration gateway.

    Use the Gateways component to set up a local integration gateway for sending messages.

  2. Create a service operation.

    Use the Service Operations component to create a service operation that contains an inbound point-to-point routing definition where the sending node is the hub system and the receiving node is the PeopleSoft CRM system.

  3. Set up a remote node.

    Set up a remote node that represents the third-party system. When you define this node, you select the appropriate connector (for example, JMS target connector, SMTP target connector, and so forth) for communicating with the third-party system.

  4. Create a service operation with an inbound routing definition where the sending node is the third-party system and the receiving node is the PeopleSoft HR system.

  5. In the service operation definition you created in the previous step, create an outbound routing definition where the sending node is the PeopleSoft HR system and the receiving node is the third-party system.

Configuring the PeopleSoft Human Resources Integration Gateway

The only required integration gateway properties for the local integration gateway are the default Oracle Jolt connect string properties that enable communication with integration engines on the PeopleSoft Human Resources system. Set these properties in the file.