Contact Us 1-800-596-4880
  1. Homepage

  2. Oracle PeopleSoft REST Connector (1.0)

All Connectors

Oracle PeopleSoft REST Connector 1.0

Anypoint Connector for Oracle PeopleSoft REST (Oracle PeopleSoft REST Connector) enables Mule applications to call PeopleSoft Component Interface REST Transport (CIRT) endpoints over HTTPS. The connector sends JSON requests to the PeopleSoft Integration Broker REST listener (PSIGW/RESTListeningConnector).

Transport cryptography uses the JVM JSSE/TLS stack, so you can run the connector in a FIPS-mode Anypoint runtime after you install a FIPS-certified security provider on the runtime. The connector doesn’t enable FIPS mode.

For information about compatibility and fixed issues, refer to the Oracle PeopleSoft REST Connector Release Notes.

Before You Begin

To use this connector, you must be familiar with:

  • The Oracle PeopleSoft REST Connector’s API

  • Anypoint Connectors

  • Mule runtime engine (Mule)

  • Elements and global elements in a Mule flow

  • How to create a Mule app using Anypoint Code Builder or Anypoint Studio

Before creating an app, you must have:

  • Credentials to access the Oracle PeopleSoft REST target resource

  • Anypoint Platform

  • The latest versions of Anypoint Code Builder or Anypoint Studio

You must have access to a PeopleSoft Integration Broker REST listener and credentials for Basic authentication or OAuth 2.0 client credentials.

This connector requires CIRT services published for the Component Interfaces that your Mule app invokes. Publish those services in PeopleTools > Integration Broker > Web Services > CI-Based REST Services. This release supports standard CIRT V1 service routes and message contracts only. Custom service or operation aliases, non-V1 operation versions, customized message contracts, and custom PeopleCode Component Interface methods aren’t supported.

Supported Operations

Use Invoke CIRT Operation with a CIRT-published, REST-enabled Component Interface and one of these methods:

  • CREATE

  • GET

  • FIND

  • SAVE_SCALAR (scalar update that leaves child rowsets unchanged)

  • SAVE_NESTED (nested update of the full graph). Omitted child collections can delete rows on Update Data.

Each invocation makes a single CIRT request. For CREATE, SAVE_SCALAR, and SAVE_NESTED, provide an unwrapped Component Interface JSON body. The connector adds the required CIRT request envelope. GET and FIND don’t send a request body.

Successful responses retain the PeopleSoft response envelope. CREATE, SAVE_SCALAR, and SAVE_NESTED can return an acknowledgement instead of a complete record. If an application requires the created or updated record, invoke GET explicitly.

You can configure default headers and query parameters for both connection types. An operation-specific value overrides a default with the same name. On some PeopleTools gateways, query parameters on CIRT routes are treated as path keys, so prefer headers for CIRT traffic. The connector requests JSON responses by default. You can override the Accept header to request another format supported by the published service.

This release doesn’t include:

  • DataSense or metadata-driven payload schemas (operation bodies are untyped JSON)

  • The legacy Update User Profile ID Type and Cancel operations

    To replace the legacy Update User Profile ID Type operation, use Invoke CIRT Operation with the USER_PROFILE Component Interface and SAVE_NESTED. Supply the required path keys and unwrapped JSON, including the intended IDTypes collection. Any collection preparation and subsequent GET request are application responsibilities.

    Cancel isn’t available because CIRT is stateless and doesn’t provide a corresponding service operation. Remove or replace existing Cancel operations before migrating.

  • Other PeopleSoft surfaces such as Query API, Application Messaging, direct SQL, or file and EDI integrations

  • Automatic migration of Oracle PeopleSoft Connector psjoa host, port, and domain-password settings

Connection Types

Oracle PeopleSoft REST connections use these authentication types:

An OAuth 2.0 client credentials connection requests a new token and retries once after an HTTP 401. A Basic authentication HTTP 401 is returned as UNAUTHORIZED.

Next Step

After you complete the prerequisites, you’re ready to create an app and configure the connector using Anypoint Studio or Anypoint Code Builder.

See Also

Back to top