While the HttpTargetConnector is by far the most commonly used target connector for REST and SOAP web services, Integration Broker delivers several other target connectors. These handle PeopleSoft-to-PeopleSoft communications, file transfers, outbound email, and messaging queues, as well as legacy protocols that Oracle has since deprecated.
| Connector ID | Java Class | Status | Primary Purpose |
|---|---|---|---|
PSFTTARGET |
PeopleSoftTargetConnector |
Active | PeopleSoft-to-PeopleSoft communication via Jolt and MIME multipart HTTP. |
SFTPTARGET |
SFTPTargetConnector |
Active | Outbound and inbound file transfer via SSH File Transfer Protocol (SFTP). |
SMTPTARGET |
SMTPTargetConnector |
Active | Outbound email delivery to SMTP mail servers. |
JMSTARGET |
JMSTargetConnector |
Active | Publish outbound messages to JMS queues and topics on message brokers. |
GETMAILTARGET |
GetMailTargetConnector |
Active | Multichannel Framework (MCF) email retrieval from mailboxes. |
FTPTARGET |
FTPTargetConnector |
Deprecated (PT 8.61) | Legacy unencrypted FTP and FTPS file transfers. |
AS2TARGET |
AS2TargetConnector |
Deprecated (PT 8.61) | EDI message transport using Applicability Statement 2. |
RIDCTARGET |
RIDCTargetConnector |
Deprecated (PT 8.59) | Oracle WebCenter Content (UCM) integration using RIDC API. |
PSFT81TARGET |
ApplicationMessagingTargetConnector |
Deprecated | Legacy PeopleSoft 8.1x Application Messaging bridge. |
FILEOUTPUT |
SimpleFileTargetConnector |
Deprecated (SDK Sample) | Writes outbound XML messages directly to gateway server disk files. |
The PSFTTARGET connector (PeopleSoftTargetConnector) is the outbound engine for native PeopleSoft-to-PeopleSoft integrations (e.g., syncing HR data from HCM to Financials or Campus Solutions).
It acts as the outbound counterpart to the PeopleSoftListeningConnector. When a PeopleSoft system routes an asynchronous or synchronous message to a remote PeopleSoft node:
multipart/related MIME envelope containing two parts:
IBInfo XML header containing routing and security metadata (From, To, ExternalOperationName, and encrypted passwords).PeopleSoftListeningConnector endpoint (https://<remote-gateway>:<port>/PSIGW/PeopleSoftListeningConnector).Guaranteed delivery, meaning the integration gateway will automatically retry transmission until the remote system acknowledges receipt.On the remote node definition (PeopleTools > Integration Broker > Integration Setup > Nodes):
Node Type: Set to PIA.
Connectors Tab: Select Gateway ID LOCAL and Connector ID PSFTTARGET.
Properties: Configure PRIMARYURL pointing to the remote system’s gateway endpoint:
http://remotehost:port/PSIGW/PeopleSoftListeningConnector
While normally routed automatically via Service Operation routings, PSFTTARGET can also be called dynamically via %IntBroker.ConnectorRequest:
Local Message &request, &response;
&request = CreateMessage(Operation.PERSON_BASIC_SYNC);
&request.IBInfo.IBConnectorInfo.ConnectorName = "PSFTTARGET";
&request.IBInfo.IBConnectorInfo.ConnectorClassName = "PeopleSoftTargetConnector";
/* Point directly to remote PeopleSoft listening connector */
&request.IBInfo.IBConnectorInfo.AddConnectorProperties("PRIMARYURL",
"https://fscm.example.com/PSIGW/PeopleSoftListeningConnector", %Property);
/* Optional: Override delivery mode (default is %IB_DM_Guaranteed) */
&request.IBInfo.IBConnectorInfo.DeliveryMode = %IB_DM_Guaranteed;
&response = %IntBroker.ConnectorRequest(&request);The SFTPTARGET connector (SFTPTargetConnector) transfers files to and from remote SFTP (SSH File Transfer Protocol) servers.
Architecture & Performance Note: Under the hood, SFTPTargetConnector does not establish an SSH connection directly from the Integration Gateway servlet. Instead, the gateway invokes the delivered PeopleCode handler PT_INTEGRATION:InvokeSFTP, which loops back into the PeopleSoft Application Server to call the PeopleCode PutAttachment or GetAttachment built-in functions.
Because of this loopback, two application server processes are consumed for each SFTP transaction (one handling the IB transaction and one executing the attachment transfer). For high-volume file batch operations, calling PutAttachment/GetAttachment directly from an Application Engine program—bypassing Integration Broker entirely—is often significantly faster and uses fewer resources.
| Property ID | Property Name | Description |
|---|---|---|
SFTPTARGET |
METHOD |
PUT (upload), GET (download), or PING (tests server connectivity and authentication). |
SFTPTARGET |
URL |
Must reference a PeopleTools URL Object name (e.g. MY_SFTP_SERVER created under PeopleTools > Utilities > Administration > URLs), not a raw URL string. |
SFTPTARGET |
REMOTEFILENAME |
Target file name on the remote SFTP server. |
SFTPTARGET |
BASE64ENCODE |
Y (default: base64-encodes payload for PUT, decodes for GET) or N (raw plain-text/binary). |
SFTPTARGET |
CHARSET |
Character encoding (defaults to UTF-8). |
SFTPTARGET |
TEMPDIR |
Working directory on the application server (defaults to PS_SERVDIR). |
SFTPTARGET |
ABSOLUTEPATH |
Y to treat TEMPDIR as an absolute filesystem path; N (default) resolves relative to PS_SERVDIR. |
Local Message &msg, &response;
&msg = CreateMessage(Operation.FILE_TRANSFER_OP);
&msg.IBInfo.IBConnectorInfo.ConnectorName = "SFTPTARGET";
&msg.IBInfo.IBConnectorInfo.ConnectorClassName = "SFTPTargetConnector";
/* URL property must match a PeopleTools URL definition ID: URL.MY_SFTP_DEST */
&msg.IBInfo.IBConnectorInfo.AddConnectorProperties("URL", "MY_SFTP_DEST", %Property);
&msg.IBInfo.IBConnectorInfo.AddConnectorProperties("METHOD", "PUT", %Property);
&msg.IBInfo.IBConnectorInfo.AddConnectorProperties("REMOTEFILENAME", "payroll_extract.csv", %Property);
&msg.IBInfo.IBConnectorInfo.AddConnectorProperties("BASE64ENCODE", "N", %Property);
/* Populate file content in message body */
&msg.SetContentString(&csvPayload);
&response = %IntBroker.ConnectorRequest(&msg);
/* On successful PUT, response XML returns: <FileTransferred>timestamp</FileTransferred> */
Local XmlDoc &respXml = &response.GetXmlDoc();The SMTPTARGET connector (SMTPTargetConnector) sends outbound messages as emails using an SMTP mail server.
integrationGateway.properties)ig.connector.smtptargetconnector.smtpservername=smtp.example.com
ig.connector.smtptargetconnector.smtpserverport=25
| Property ID | Property Name | Description |
|---|---|---|
SMTPTARGET |
EMAIL / DestEmailAddress |
Recipient email address (or comma-separated list). |
SMTPTARGET |
EMAILFROM / SourceEmailAddress |
Sender From email address. |
SMTPTARGET |
SUBJECT / Subject |
Email subject line. |
SMTPTARGET |
CONTENTTYPE / ContentType |
MIME content type (default is text/plain; use text/html for HTML email). |
Local Message &emailMsg, &emailResp;
&emailMsg = CreateMessage(Operation.EMAIL_DISPATCH_OP);
&emailMsg.IBInfo.IBConnectorInfo.ConnectorName = "SMTPTARGET";
&emailMsg.IBInfo.IBConnectorInfo.ConnectorClassName = "SMTPTargetConnector";
&emailMsg.IBInfo.IBConnectorInfo.AddConnectorProperties("DestEmailAddress",
"integrations@example.com", %Property);
&emailMsg.IBInfo.IBConnectorInfo.AddConnectorProperties("SourceEmailAddress",
"peoplesoft-noreply@example.com", %Property);
&emailMsg.IBInfo.IBConnectorInfo.AddConnectorProperties("Subject",
"Batch Integration Notification", %Property);
&emailMsg.IBInfo.IBConnectorInfo.AddConnectorProperties("ContentType",
"text/html; charset=UTF-8", %Property);
&emailMsg.SetContentString("<html><body><h3>Batch Complete</h3><p>Records processed: 1500</p></body></html>");
&emailResp = %IntBroker.ConnectorRequest(&emailMsg);The JMSTARGET connector (JMSTargetConnector) publishes outbound messages to Java Message Service (JMS) queues and topics hosted on enterprise message brokers such as Oracle WebLogic JMS, IBM MQ, or Oracle AQ.
The gateway connects to the JMS provider via JNDI lookup. Properties can be set in integrationGateway.properties or dynamically configured on node definitions (such as delivered node PT_CDB_UPDATE):
JMSUrl: Provider connection URL (e.g., t3://weblogic-host:7001 for WebLogic, or tcp://mq-host:1414 for IBM MQ).JMSTopic or JMSQueue: The target topic or queue destination name on the message broker.JMSFactory: JNDI name of the Connection Factory (e.g., weblogic.jms.ConnectionFactory).PROVIDER: Provider type (WebLogic, MQSeries, Oracle, iPlanet).JMSJNDIFactoryOverride: Initial Context Factory class (e.g., weblogic.jndi.WLInitialContextFactory).Local Message &jmsMsg = CreateMessage(Message.PT_CDB_UPDATE);
/* Load base connection settings from configured JMS Node */
&jmsMsg.IBInfo.LoadConnectorPropFromNode("PT_CDB_UPDATE");
/* Override destination topic and payload dynamically */
&jmsMsg.IBInfo.IBConnectorInfo.AddConnectorProperties("JMSTopic", "dashboard.alerts.topic", %Property);
&jmsMsg.SetContentString(&jsonOrXmlPayload);
/* Publish to JMS topic via Integration Gateway */
Local Message &resp = %IntBroker.ConnectorRequest(&jmsMsg);The GETMAILTARGET connector (GetMailTargetConnector) is an internal target connector used by the PeopleSoft MultiChannel Framework (MCF) and Email Collaboration Framework (EMC). It connects to POP3 or IMAP mail servers to poll mailboxes and retrieve inbound email communications for ingestion into PeopleSoft CRM or Approval Workflow Engine (AWE) email approvals.
PeopleTools delivers pre-configured nodes using GETMAILTARGET:
PT_EMC_GETMAIL: Dedicated node for Approval Workflow Engine (AWE) email approval responses.MCF_GETMAIL: General MultiChannel Framework email ingestion node.PSNODECONPROP / PSNODEPROP)MCF_Server: Inbound mail server hostname (POP3 or IMAP).MCF_User: Mailbox account username.MCF_Password: Mailbox password (encrypted using PSCipher).EMC_REPOSITORY_EMAILADDRESS: Target email inbox address.EMC_POLLING_FREQUENCY: Interval in minutes for the polling daemon.Batch programs such as EMC_PULL execute periodically, using GETMAILTARGET to download pending emails and parse approval action codes (e.g., Approve, Deny) back into the workflow engine.
Deprecated: PeopleTools 8.61 is the last supported release for
FTPTARGET.
The FTPTARGET connector was used to upload (PUT) and download (GET) files over standard unencrypted FTP or FTPS. Oracle has deprecated this connector in favor of modern, secure file transfer using SFTPTARGET.
Deprecated: PeopleTools 8.61 is the last supported release for
AS2TARGET.
The AS2TARGET connector was used for business-to-business (B2B) Electronic Data Interchange (EDI) messaging over HTTP/HTTPS adhering to the Applicability Statement 2 (AS2) standard with S/MIME encryption and Message Disposition Notifications (MDN).
Deprecated: Deprecated starting in PeopleTools 8.59.
The RIDCTARGET connector wrapped Oracle’s Remote Intradoc Client (RIDC) Java API to upload, check in, and download content to and from Oracle WebCenter Content (formerly Universal Content Management / UCM) synchronously over HTTP. Oracle recommends using REST APIs or custom PeopleCode integrations for modern WebCenter Content integrations.
Deprecated: Obsolete legacy connector.
The PSFT81TARGET connector (ApplicationMessagingTargetConnector) provided backward compatibility for PeopleTools 8.4x+ systems to transmit messages to legacy PeopleSoft 8.1x systems that ran the pre-Integration Broker Application Messaging architecture.
Deprecated / SDK Reference Sample: Relegated from core production connectors to the Integration Broker Connector SDK.
The FILEOUTPUT connector (SimpleFileTargetConnector) wrote outbound message payloads directly as XML files to a specified directory on the gateway server (fileconnector.FilePath). It was primarily used for development and offline testing to verify message structure without connecting to a network endpoint.
Look up any record, field, page, or component, audit security, and monitor Integration Broker across every database — in seconds.
A web console built for the PeopleSoft community — operational monitoring, security auditing, and metadata browsing in one tool.
On-demand security and operational reports for your PeopleSoft environment — no client install required.
Research any PeopleSoft object and monitor system health from a single browser tab — no App Designer, no SQL.
Chris Malek is a PeopleTools® Technical Consultant with over two decades of experience. He is available for consulting engagements.
Work with ChrisSWS turns SQL into production REST APIs — ready for AI, modern apps, and partner integrations. One install, unlimited potential.
A powerful PeopleSoft bolt-on that makes REST web services easy. You bring the SQL, SWS handles the rest.
Traditional PeopleSoft web services cost $3,600–$13,000 each to develop. SWS deploys production REST APIs in under 5 minutes through configuration alone.
Turn PeopleSoft data into clean REST APIs for AI integrations, modern applications, and vendor data feeds. Configuration-driven — no PeopleCode required.