A comprehensive reference of the PeopleSoft database tables that underpin the Integration Broker messaging fabric. These tables store configuration metadata (nodes, services, routings, handlers, and queues) and runtime transaction state (asynchronous pub/sub contracts, error logs, and synchronous request traces).
Message nodes represent endpoints participating in integrations, including external third-party systems and local database instances.
| Table | Description & Notes | Key Columns |
|---|---|---|
PSMSGNODEDEFN |
Primary node definition (name, local node flag, authentication type, default user ID, and description). | MSGNODENAME, LOCALNODE, DEFAULT_USER_ID, AUTHOPTN, LOCALDEFAULTFLG, ACTIVE_NODE |
PSNODECONPROP |
Target connector properties assigned to a node (such as default URL, Method, Header configurations). |
MSGNODENAME, CONTYPE, PROPNAME |
PSNODEURITEXT |
Physical URI text for local PIA nodes (PL = Portal /psp/, CN = Content /psc/). Used by PIA to construct browser links. |
MSGNODENAME, URI_TYPE |
PSNODEPROP |
Custom key-value properties assigned to a node (Category, Identification, or Search tags). | MSGNODENAME, PROPTYPE, PROPNAME |
PSNODESDOWN |
Dynamic tracking table populated when an outbound external node fails to respond. pub/sub halts live delivery and falls back to periodic <OperationType>ping</OperationType> checks. |
MSGNODENAME, IB_OPERATIONNAME, ROUTINGDEFNNAME |
PSTRUSTNODES |
Trusted nodes configured for Single Sign-On (SSO) authentication tokens (PS_TOKEN). |
MSGNODENAME |
PSCONNECTSTRING |
Gateway connection URLs for remote gateways. | MSGNODENAME, CONTYPE |
A Service provides a high-level logical grouping of Service Operations. A Service Operation represents the actual messaging action (synchronous or asynchronous).
| Table | Description & Notes | Key Columns |
|---|---|---|
PSSERVICE |
Logical service definition header. | IB_SERVICENAME, ACTIVE_FLAG, SERVICETYPE |
PSSERVICEOPR |
Mapping table linking service operations to their parent service definition. | IB_SERVICENAME, IB_OPERATIONNAME |
PSOPERATION |
Primary service operation definition. Defines operation type (Synchronous, Asynchronous One-Way, Asynchronous Request-Response) and REST HTTP methods. | IB_OPERATIONNAME, OPERATIONTYPE, ROUTINGTYPE, DEFAULTVER |
PSOPERATIONURI |
REST URI templates configured for the operation. | IB_OPERATIONNAME, URI_INDEX |
PSOPRVERDFN |
Service operation version definition. Tracks effective status and default message schemas. | IB_OPERATIONNAME, VERSIONNAME, ACTIVE_FLAG |
PSOPRVERDFNPARM |
Request, response, and fault message parameters attached to a version. | IB_OPERATIONNAME, VERSIONNAME, MSGNAME, MSGTYPE |
PSOPRVERQUEPARM |
Queue assignment for asynchronous service operations. | IB_OPERATIONNAME, VERSIONNAME, QUEUENAME |
PSOPRGENRTGPARM |
Parameters used by Integration Broker to auto-generate routings. | IB_OPERATIONNAME, VERSIONNAME |
Routings define the transmission path between a sender node and a receiver node.
| Table | Description & Notes | Key Columns |
|---|---|---|
PSIBRTNGDEFN |
Primary routing definition. Specifies sender node, receiver node, effective status, and message detail logging flag (LOGMSGDTLFLG). |
ROUTINGDEFNNAME, IB_OPERATIONNAME, VERSIONNAME, SENDERNODENAME, RECEIVERNODENAME, EFF_STATUS, LOGMSGDTLFLG |
PSRTNGDFNCONPRP |
Connector property overrides specific to this routing (e.g. overriding URL, Method, or headers at the routing level). |
ROUTINGDEFNNAME, CONTYPE, PROPNAME |
PSRTNGDFNPROP |
Custom routing properties. | ROUTINGDEFNNAME, PROPNAME |
PSIBRTNGSUBDEFN |
Routing sub-definitions and transformation programs (XSLT or Application Class transforms). | ROUTINGDEFNNAME, TRANS_NAME |
PSRTNGDFNPARM |
Inbound and outbound message parameter mappings for the routing. | ROUTINGDEFNNAME, PARAM_SEQ |
Handlers define the execution engine that runs when an inbound or outbound message processes.
| Table | Description & Notes | Key Columns |
|---|---|---|
PSOPRHDLR |
Primary handler header. Specifies handler type (Application Class, Component Interface, etc.) and active status. | IB_OPERATIONNAME, HANDLERNAME, EFF_STATUS, HANDLERTYPE |
PSOPERATIONAC |
Application Class handler definitions: package root, sub-path, class name, and execution method (OnRequest, OnNotify, OnRouteSend, etc.). |
IB_OPERATIONNAME, HANDLERNAME, PACKAGEROOT, APPCLASSID |
PSOPERATIONCI |
Component Interface handler definitions (for CI-based web services). | IB_OPERATIONNAME, HANDLERNAME, BCNAME |
PSOPERATIONAE |
Application Engine handler definitions (legacy async processing). | IB_OPERATIONNAME, HANDLERNAME, AE_APPLID |
Queues govern asynchronous message delivery order, concurrency, and dispatch status.
| Table | Description & Notes | Key Columns |
|---|---|---|
PSQUEUEDEFN |
Queue header definition. Configures queue status (1 = Run, 2 = Pause), queue type (Ordered vs. Unordered), and dispatch limits. |
QUEUENAME, QUEUESTATUS, QUEUETYPE |
PSIBQUEUEINST |
Partition instances when queue partitioning is configured to parallelize processing. | QUEUENAME, QUEUEINST |
PSQUEUEOVRD |
Node-level queue status overrides. | QUEUENAME, MSGNODENAME |
PSQUEUEPART |
Queue partitioning keys. | QUEUENAME, PARTITION_KEY |
These tables track asynchronous publication and subscription contracts through their lifecycle:
| Table | Description & Operational Use |
|---|---|
PSAPMSGPUBHDR |
Publication Header: One row per published asynchronous transaction. Contains publication status, originating node, timestamp, and transaction GUID (IBTRANSACTIONID). |
PSAPMSGPUBDATA |
Publication Data: The raw XML or JSON payload of the published message. |
PSAPMSGPUBCON |
Publication Contracts: One row per receiving node. Tracks outbound delivery status (PUBCONSTATUS: 1 = New, 2 = Started, 3 = Done, 4 = Error, 5 = Retry). |
PSAPMSGSUBCON |
Subscription Contracts: One row per active inbound handler. Tracks local handler execution status (SUBCONSTATUS: 1 = New, 2 = Started, 3 = Done, 4 = Error). |
PSAPMSGPUBCERR |
Publication Contract Errors: Diagnostic error codes and messages when an outbound publication contract fails. |
PSAPMSGSUBCERR |
Subscription Contract Errors: Diagnostic error messages and PeopleCode stack traces when an inbound subscription handler fails. |
PSIBERR / PSIBERRP |
Integration Broker Errors & Parameters: Logged framework and connector exceptions (such as 158, 10721 contact errors and SSLHandshakeException details) with resolved parameter tokens. |
PSAPMSGDOMSTAT |
Pub/Sub Domain Status: Heartbeat and operational state of application server pub/sub domains (PSPUBDSP, PSSUBDSP, PSBRKDSP). |
Synchronous transactions (SyncRequest and inbound synchronous requests) do not use pub/sub queues. If logging is enabled (LOGMSGDTLFLG on PSIBRTNGDEFN), they write to these audit tables:
| Table | Description & Notes |
|---|---|
PSIBLOGHDR |
Header record for synchronous transactions. Records transaction GUID, operation name, response time, and completion status. |
PSIBLOGDATA |
Full request and response message payload bodies (only populated if LOGMSGDTLFLG = 1 Header & Detail). |
PSIBLOGERR / PSIBLOGERRP |
Logged errors and message catalog parameters for failed synchronous calls. |
PSIBLOGIBINFO |
Gateway connector attributes and metadata headers attached to the synchronous request. |
| Table | Description & Notes |
|---|---|
PSAUTHWS |
Web Service Permissions: Links Permission Lists (CLASSID) to Service Operations (IB_OPERATIONNAME). Required for a user or node default account to invoke a service operation. |
PSAUTHAS |
Application Service Permissions: Links Permission Lists (CLASSID) to Application Services Framework (ASF) URI templates and HTTP methods (PTIBAPPLNAME, IB_RESTMETHOD). |
When diagnosing why an integration is not delivering messages or responding to external calls, verify that the operation is fully active. In Integration Broker, an operation is functional only when all three legs are active:
PSOPRVERDFN with ACTIVE_FLAG = 'A'.PSIBRTNGDEFN with EFF_STATUS = 'A'.PSOPRHDLR with EFF_STATUS = 'A'.Missing any one of these three legs renders the service operation inactive.
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.