XDSQLWriter Activity Driver

XDSQLWriter Activity Driver inserts records into the activity database formatted as described in this section. The records are designed for fast writing rather than for ease of later analysis. A set of inquiry service agents suitable for use in process flows is available to assist in analysis of the log. Users are cautioned that iWay does not absolutely guarantee the layout of the record from release to release, and this should be checked against the actual schema.

Fields in the Database	Description
recordkey	Unique record identifier.
recordtype	Type of this record - the event being recorded.
signature	Encoding of the listener name and protocol.
protocol	Name of the protocol.
address	Address to which an emit is to be issued. The format depends on the protocol.
tstamp	Time of record.
correlid	Correlation ID if present.
tid	Transaction ID assigned to this message.
msg	Message appropriate to this record type. For example, an input message contains the original message received, if possible. Streaming input does not contain a record.
context	Serialized special registers that were in the context at the time the record was written.
text	Message text for business errors (rules system violations).
status	Status code recorded. Success if 0; other status codes are based on the type of record being recorded.
subtype	Event code for event records, for example, parsing, agent calls, and returns.
partner_to	If the TPA has recognized a to party, the value is put here.
partner_from	If the TPA has recognized a from party, the value is put here.
encoding	Encoding of the listener that obtained the document.
mac	Hash encoded by a symmetric algorithm. Not used in this version.
version	Driver version (1.0 in 5.5.SM).

Note:

Partner fields contain the information extracted form the TPA via the TPN() function. For example, an EDI record has a field in the ISA that encodes partner information. This is passed into TPA to get the partner's name.
Mac is an encoded field of a hash value. It is intended to ensure that the record has not been modified by an unauthorized party. Once implemented, it cannot be null.
Time stamps are in compressed RFC 1138 form such as 20050509130705021Z.
The context is a string of token=value[;token=value]* elements. This consists of all simple value special registers in the context at the time the record was written, with the exception registers marked as secure or hidden.

Record Type Codes	Description
101	Message start.
131	Entry to event (see subtype codes).
132	Normal exit from event.
133	Failed exit from event.
151	Ancillary message (usually rules violation).
181	Emit.
191	Message end.

Record Subtype Codes	Description
1	Preparser
2	Parser
3	In reviewer
5	In validation
6	In transform
7	Agent or flow
8	Out transform
9	Out validation
11	Preemitter

iWay Software