# PeopleSoft Integration Broker Tables and Message Status Reference > Source: https://netray.co/tools/peoplesoft-integration-broker-tables-status-reference > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Free Tools ## Short answer Find the Integration Broker tables behind the asynchronous and synchronous monitors, what each message status means, and what to do about errors, retries and growth. ## Category oracle ## Erp Oracle PeopleSoft ## Audience - PeopleSoft integration developer - PeopleSoft administrator ## Tool **Kind:** worksheet **Mode:** reference **Columns:** #### Row type **Key:** kind **Type:** text #### Table / status **Key:** item **Type:** text #### Contents / meaning **Key:** contents **Type:** text #### Key or status column **Key:** keys **Type:** text #### Action or purge note **Key:** note **Type:** text **Rows:** **Kind:** Table **Item:** PSAPMSGPUBHDR **Contents:** Asynchronous publication header: one row per published message (transaction) **Keys:** IBTRANSACTIONID; status in PUBSTATUS **Note:** Shown on the Asynchronous Services monitor; archive or purge with APPMSGARCH **Kind:** Table **Item:** PSAPMSGPUBCON **Contents:** Publication contracts: delivery of a published message to each target node **Keys:** IBTRANSACTIONID; status in PUBCONSTATUS **Note:** Errors here are usually connection or target node problems **Kind:** Table **Item:** PSAPMSGSUBCON **Contents:** Subscription contracts: processing of an inbound message by a handler **Keys:** IBTRANSACTIONID; status in SUBCONSTATUS **Note:** Errors here are usually handler PeopleCode or data problems **Kind:** Table **Item:** PSIBLOGHDR **Contents:** Synchronous service operation log header **Keys:** GUID **Note:** Populated when synchronous logging is enabled; grows quickly at high log levels **Kind:** Table **Item:** PSIBLOGDATA **Contents:** Synchronous message request and response data **Keys:** GUID **Note:** May contain payload data; restrict access and purge on a schedule **Kind:** Table **Item:** PSIBLOGERR **Contents:** Synchronous error messages **Keys:** GUID **Note:** First place to look for failed synchronous calls **Kind:** Table **Item:** PSOPERATION **Contents:** Service operation definitions **Keys:** IB_OPERATIONNAME **Note:** Whether the operation is synchronous or asynchronous and its versions **Kind:** Table **Item:** PSSERVICE **Contents:** Service definitions **Keys:** IB_SERVICENAME **Note:** Groups service operations **Kind:** Table **Item:** PSMSGNODEDEFN **Contents:** Node definitions **Keys:** MSGNODENAME **Note:** Default local node, authentication option and node status **Kind:** Table **Item:** PSQUEUEDEFN **Contents:** Queue definitions for asynchronous operations **Keys:** QUEUENAME **Note:** Paused queues stop delivery; check queue status first **Kind:** Table **Item:** PSIBRTNGDEFN **Contents:** Routing definitions **Keys:** ROUTINGDEFNNAME **Note:** Inactive or missing routing is a common cause of messages not going out **Kind:** Status **Item:** New **Contents:** Message or contract created, waiting to be processed **Keys:** Status column of the header or contract **Note:** Many in New: check that the pub/sub domain and dispatchers are running **Kind:** Status **Item:** Started **Contents:** Picked up by a dispatcher **Keys:** Status column **Note:** Long time in Started can mean a stuck handler **Kind:** Status **Item:** Working **Contents:** Being processed by a handler **Keys:** Status column **Note:** Check application server handler processes if it does not progress **Kind:** Status **Item:** Done **Contents:** Processed successfully **Keys:** Status column **Note:** Eligible for archive and purge **Kind:** Status **Item:** Error **Contents:** Processing failed **Keys:** Status column **Note:** Read the error, fix the cause, then resubmit from the monitor **Kind:** Status **Item:** Retry **Contents:** Failed delivery that will be tried again **Keys:** Status column **Note:** Usually a target node that is down or unreachable **Kind:** Status **Item:** Timeout **Contents:** Processing exceeded the allowed time **Keys:** Status column **Note:** Check target response time and handler performance **Kind:** Status **Item:** Edited **Contents:** Message data was edited in the monitor **Keys:** Status column **Note:** Resubmit after editing; record who changed it **Kind:** Status **Item:** Cancelled **Contents:** Cancelled by an administrator **Keys:** Status column **Note:** Not processed; confirm the business impact **Kind:** Status **Item:** Hold **Contents:** Held and not processed until released **Keys:** Status column **Note:** Release or cancel from the monitor once the reason for the hold is resolved **Kind:** Tip **Item:** Dispatchers and handlers **Contents:** PSBRKDSP and PSBRKHND (broker), PSPUBDSP and PSPUBHND (publication), PSSUBDSP and PSSUBHND (subscription) run in the application server pub/sub domain **Keys:** Application server domain **Note:** If statuses stay New or Started, check these processes first **Kind:** Tip **Item:** Resubmit or cancel **Contents:** Use the Asynchronous Services monitor to resubmit or cancel operation instances, publication contracts and subscription contracts **Keys:** PeopleTools, Integration Broker, Service Operations Monitor **Note:** Avoid updating status columns with SQL **Kind:** Tip **Item:** Archive and purge **Contents:** The APPMSGARCH Application Engine program archives and deletes processed asynchronous messages **Keys:** Run on a schedule **Note:** Without it, PSAPMSG tables grow and monitor queries slow down **Notes:** Status columns are numeric codes decoded by translate values. On your database run: SELECT FIELDNAME, FIELDVALUE, XLATLONGNAME FROM PSXLATITEM WHERE FIELDNAME IN ('PUBSTATUS', 'PUBCONSTATUS', 'SUBCONSTATUS') ORDER BY FIELDNAME, FIELDVALUE to get the numeric code for each status name. Table and column names apply to PeopleTools 8.48 and later Integration Broker; confirm for your release in the Integration Broker PeopleBooks. ## Content **Intro:** This reference lists the PeopleSoft Integration Broker tables behind the Service Operations Monitor, the message statuses you see there, and what to do about each. It covers PeopleTools 8.5x and 8.6x. **Sections:** #### How to use it **Body:** Filter on row type. Table rows show where asynchronous publications, publication contracts, subscription contracts and synchronous logs are stored, and the key columns for joins. Status rows explain each monitor status and the usual action. Tip rows cover the processes and programs you will touch when things go wrong. Run the PSXLATITEM query in the notes once to get your numeric status codes, then write monitoring queries against PSAPMSGPUBCON and PSAPMSGSUBCON for error and retry counts by service operation. **Bullets:** - Publication contract errors point outward, to the target - Subscription contract errors point inward, to handler code or data - Synchronous failures are in PSIBLOGERR when logging is on #### How asynchronous messaging is stored **Body:** When PeopleSoft publishes an asynchronous service operation, a header row is written to PSAPMSGPUBHDR with an IBTRANSACTIONID. The publication dispatcher and handlers create a publication contract in PSAPMSGPUBCON for each routing to a target node, and deliver it. On the receiving side, each inbound message creates a subscription contract in PSAPMSGSUBCON processed by the handler PeopleCode. Queues group related messages; ordered queues process in sequence, so one error can hold the messages behind it. Synchronous calls skip these tables and are logged in PSIBLOGHDR, PSIBLOGDATA and PSIBLOGERR. #### Worked example: messages stuck in New **Body:** After a weekend patch, HR job data stopped reaching a downstream system. The monitor showed hundreds of publication contracts in New for the operation. Queue status in PSQUEUEDEFN was Run, and routings were active, so the cause was not configuration. The application server pub/sub domain had been restarted without pub/sub servers enabled, so PSPUBDSP and PSPUBHND were not running. After enabling them and rebooting the domain, contracts moved through Started and Working to Done within minutes, with no resubmission needed. #### Gotchas **Body:** Do not change status columns with SQL; resubmit and cancel through the monitor so headers and contracts stay consistent. Ordered queues hold later messages behind an error, so fix the oldest error first. Synchronous logging at a detailed level writes full payloads into PSIBLOGDATA, which may include personal data, so keep it off in production unless debugging and purge afterwards. Schedule APPMSGARCH so processed messages do not accumulate for years. **Bullets:** - Fix the oldest error in an ordered queue first - Treat logged payloads as sensitive data - Schedule archive and purge from day one **Cta:** If you want an assistant that watches your Integration Broker queues and explains failures in plain English, running on your own PeopleSoft servers, we can build that with you. **Faq:** #### What are the main PeopleSoft Integration Broker tables? **Answer:** Asynchronous messages are in PSAPMSGPUBHDR (publication headers), PSAPMSGPUBCON (publication contracts) and PSAPMSGSUBCON (subscription contracts), keyed by IBTRANSACTIONID. Synchronous logging uses PSIBLOGHDR, PSIBLOGDATA and PSIBLOGERR. Definitions live in PSOPERATION, PSSERVICE, PSMSGNODEDEFN, PSQUEUEDEFN and PSIBRTNGDEFN. #### How do PeopleSoft Integration Broker queues work? **Answer:** Asynchronous service operations are assigned to queues defined in PSQUEUEDEFN. A queue can be ordered, so messages process in sequence, or unordered for parallel processing. A paused queue stops delivery. In an ordered queue, an error blocks the later messages in the same queue until the earlier one is fixed and resubmitted or cancelled. #### Where do I see Integration Broker errors? **Answer:** Use the Service Operations Monitor: Asynchronous Services shows operation instances, publication contracts and subscription contracts with their status and error messages. Synchronous errors appear in the synchronous monitor when logging is on, stored in PSIBLOGERR. Application server logs for the pub/sub domain help when handlers fail to start. #### How do I purge Integration Broker messages? **Answer:** Run the delivered APPMSGARCH Application Engine program on a schedule to archive and delete processed asynchronous messages. Decide retention with audit before purging. For synchronous logs, keep logging levels low in production and clear old log data through the delivered options so PSIBLOGDATA does not grow without limit. ## Search terms peopletools integration broker tables, peoplesoft integration broker tables, peoplesoft integration broker queue, peoplesoft integration broker service, psapmsgpubhdr, psapmsgsubcon status, peoplesoft integration broker error status, peoplesoft service operation table --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json