Read the requests or responses in the portal, stream, and status messages?

The portal can display message body details only when the message body is a standard production message body object. If the message body is “any other type,” the Body tab has no additional fields. [1]

The Contents tab can display formatted contents of the message body, for example XML for standard production messages or segment-based output for virtual documents. It also supports View Full Contents and View Raw Contents for those message types. [1]

For stream-based messages, the retrieved material does not describe a portal feature that directly renders arbitrary %Stream properties or %Status values in the Message Viewer. One returned example specifically describes a request/response message class containing only a %GlobalCharacterStream property where the Ensemble Message Viewer shows the stream content as blank. [2]

For %Status, the returned material only states that methods such as SendRequestSync(), SendRequestAsync(), and SendDeferredResponse() return a status value of type %Status, and that code can check or display that status programmatically. [3][4][5][6]

To read stream content programmatically, the documents show using stream methods such as Read(), ReadLine(), Rewind(), Write(), WriteLine(), MoveToEnd(), and Clear(). For HTTP responses, the response body is in %Net.HttpResponse.Data, which is a %GlobalBinaryStream. [7][8][9][10]

So based on the retrieved documents, there is no documented way here to read STREAM or STATUS messages directly in the portal in the same way as standard message contents. The available guidance is to access those values in code rather than through the portal viewer. [2][7][1]

Sources: