Author Info
Chris Malek

Chris Malek is a PeopleTools® Technical Consultant with two decades of experience working on PeopleSoft enterprise software projects. He is available for consulting engagements.

About Chris Work with Chris
Do you need a quick way to create web services?
PeopleSoft Simple Web Services (SWS)

Introducing a small but powerful PeopleSoft bolt-on that makes web services very easy. If you have a SQL statement, you can turn that into a web service in PeopleSoft in a few minutes.

Read More & Purchase

Other Listening Connectors

Below are some other listening connectors that are not used very often or I don’t have any experience with.


The PeopleSoftListeningConnector is used to message between PeopleSoft instances. It uses MIME data encoding to transfer data.

From PeopleBooks:

…using MIME multipart message type (Content-Type: multipart/related;), with a very specific internal formatting: there are two MIME parts (section), one carries the IBInfo (the parameters of the sending) and the other carries the message payload XML.

The URL pattern is: https://host:port/PSIGW/PeopleSoftListeningConnector

In working with PeopleSoft integrations you normally do not use this listener. If you are developing an integration between two PeopleSoft database this is often used but is typically chosen behind the scenes based on the NODE type of “PIA” and the integration broker. We will not cover this in depth at this time.

The security for this node type typically uses these options:


  • JMS messages should be sent to JMS Listening Connector. The URL pattern is: https://host:port/PSIGW/JMSListeningConnector. I have never seen this used.


  • Applicability Statement 2 (AS2) EDI messages should be sent to AS2 Listening Connector. The URL pattern is https://host:port/PSIGW/AS2ListeningConnector. I have never seen this used.


The PS81ListeningConnector is used for older tools releases less than 8.2x. The URL pattern is http://host:port/PSIGW/PS81ListeningConnector