NonRowset Message Objects

NonRowset Messages can be used for various purposes inside the integration broker. The are used in the following situations.

  • If you want complete control over the output in your handler to produce your own XML, JSON or CSV.
  • If you need to take data from a 3rd part and parse it out manually.
  • If you need to consume or produce dynamic output based on certain data conditions.
  • If you want to accept non-standard data formats.

The Service Operation Setup always requires some response message object defined on the service operation. So if you are handling the data encoding and decoding in your handler you just need something there as a “shell”. You will not use any of the actual functionality of the message object.

I generally keep a “GENERIC” message that I use on all service operations where I am handing the input and output data encoding in the handler. This is a trigger for me that I am not use the functionality of the message object and the handler is doing all the logic. You could create a new message for each of your service operation but it provide no value at all.

Generic Message

XML Output

For example usage of XML output you can see the XML Encoding Section. In that example, the PeopleCode creates the XML and then calls SetXmlDoc method on the response message object of the service operation. This is where we are using the NonRowset Message as a shell and then just having our PeopleCode set the XML on the message and we don’t let the PeopleTools framework do any magic.

XML Parsing

For example of XML parsing you can see the XML Encoding section.


Author Info
Chris Malek

Chris Malek is a PeopleTools® Technical Consultant with two decades of experience working on PeopleSoft enterprise software projects. He is available for consulting engagements.

About Chris Work with Chris