Understanding Message Parts

Message parts are individual message definitions that get used in container messages.

While message parts can be rowset-based or nonrowset-based, the advantage of using message parts comes when working with rowset-based messages. By using nonrowset-based message parts, you cannot take advantage of PeopleSoft Integration Broker's framework for creating message definitions, use of PeopleCode, serialization, porting, and so on. The following table highlights some of the advantages of using rowset-based message parts:

Rowset-Based Message Parts	Nonrowset-Based Message Parts
You can use the PeopleSoft Pure Internet Architecture to build rowset-based message parts.	You cannot use the PeopleSoft Pure Internet Architecture to build nonrowset-based message parts.
Message schema is automatically generated for rowset-based messages.	You must generate message schema for nonrowset-based message parts.
The mapping from XML to rowset is managed by the framework.	You must use the XMLDoc class to manipulate nonrowset-based message content. In addition, you must manually map the XML into XMLDoc for the parts.

Container messages are always nonrowset-based. So, if you use a container message that contains rowset-based part messages, the container messages sends XML that contains none of the standard PeopleSoft message XML structures, such as PSCAMA, FieldTypes, and so on. However, you can use the rowset-based classes and methods to populate and read the structure of each part message.