Message Types

Five types of messages are available:

Term	Definition
Rowset-based messages	For hierarchical data that is based on PeopleSoft records, you create a message definition by assembling records, organizing them into a hierarchy, and selecting fields from those records to include in the message. The result is a rowset that doesn't need to match an existing rowset structure in the application. Use the PeopleCode Rowset and operation classes to generate, send, receive, and process these messages.
Nonrowset-based messages	These messages can have virtually any structure and content. You create a message definition, but you do not insert any records. The message definition serves as a placeholder for the actual message. Use the PeopleCode XmlDoc and operation classes to generate, send, receive, and process these messages. If you're handling Simple Object Access Protocol (SOAP) compliant data, you can also use the SoapDoc class to generate and process these messages. The message schema can be XML or JSON. For a SOAP message the schema must be XML
Container messages	A container message is a nonrowset-based message that holds one or more part messages. A container message must contain all rowset-based messages or all nonrowset-based message parts.
Message parts	Message parts are rowset-based messages or nonrowset-based messages that you designate as a part message, to be used in a container message.
Document messages	A document messages are messages based on the PeopleSoft XML document technology. You create and manage these messages in the PeopleSoft Document Builder, either by creating the XML documents from the ground up, importing them from schema definitions, or from PeopleSoft records.

The following table describes when to use a given message type:

Message Type	When to Use
Rowset-based message.	All PeopleSoft-to-PeopleSoft integrations.
Nonrowset-based message.	Integrations with third-party systems.
Container message with rowset-based message parts.	Exposing PeopleSoft services to third-party systems.
Container message with nonrowset-based message parts.	Exposing PeopleSoft services to third-party systems and need to provide nested parts.
Document message.	Integrations with third-party systems.