Real Time Information Director User Documentation

RTID Message Format and Programmatic Interfaces

Hewlett-Packard Company 5 529618 - 002

characters like kanji—you must specify the encoding in the <?xml> tag. The Director

converts double-byte characters to single byte before storing them in the database.

Outbound encoding is ISO 8859 by default, but you can specify a different encoding in

the properties file, using the "OutboundEncoding" property, for example:

OutboundEncoding=UTF-8

The RTID outbound encoding must match the encoding of the SPQ/MXMX database.

For example, if the MX database is configured to support Spanish encoding, then the

RTID outbound encoding must also be.

The Native Document Header

A native document can, but need not, contain a header. The header is used to provide

information for security, auditing, and end-to-end transaction logging, as described in the

document entitled RTID Security and Auditing.

Below is an excerpt of a native document containing a header. The first several fields are

related to security:

• CONSUMER is the person the data describes

• AGENT is the person who submits or requests the data about the consumer

• ROLE describes how the agent is related to the consumer.

Other header fields support end-to-end transaction logging:

• SOURCE_NM identifies the source system, in any way meaningful to the

application

• TRANSACTION_DOCUMENT_TY identifies the message type, in any way

meaningful to the application

• TRANSACTION_DOCUMENT_NO identifies the document number, in any

way meaningful to the application

• SOURCE_REFERENCE_DOC_NO identifies the key field of the top-level

record of the document.

<ROLE>PersonalPhysician</ROLE>

<SOURCE_NM></SOURCE_NM>

<TRANSACTION_DOCUMENT_TY>PersonalData</TRANSACTION_DOCUMENT_TY>

<TRANSACTION_DOCUMENT_NO>00001</TRANSACTION_DOCUMENT_NO>