Listening Connector?A listening connector is a servlet running on the integration gateway that handles requests from clients. They are used for services that PeopleSoft is providing to an external system. It surfaces itself to the client as a path in the URL. For example, the HttpListeningConnector is reached by posted to https://host:port/PSngConnector and the REST connector is reach by posting to https://host:port/PSIGW/RESTListeningConnector
They are responsible for accepting the request pulling out any header information or security information and passing it to the back end PeopleSoft layers. There are several delivered listening connectors and each one is used for a different purpose and has different ways to pass the request and parameters.
Here is a simplified schematic.
The 2 you should really focus on are the HttpListeningConnector and the RESTListeningConnector. If you have to use SOAP then look at PeopleSoftServiceListeningConnector.
We will go over each one in detail in the sections below.
If you have custom requirements to create your own listening connector you can see these links:
Chris Malek is a PeopleTools® Technical Consultant with over two decades of experience working on PeopleSoft enterprise software projects. 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.