BAM_ACTIVITY Table

The BAM_ACTIVITY table contains one record for each entry that is recorded by the BAM activity log driver.

Field

Datatype

Description

RecordKey

char(32)

Primary key for this table and foreign key for RecordKey in BAM_ACTIVITY_EXTENDED and BAM_ACTIVITY_CONTEXT tables. This value is a GUID, with no intrinsic meaning except to uniquely identify an activity record.

Tstamp

Datetime

The time at which this activity record was logged, with precision down to the millisecond if the system supports it.

RecordType

Int

Type of activity record, using the following codes:

100 (Enqueue). Receipt of message on an iWay internal queue.

101 (Start). Start of processing for a message

191 (End). End of processing for a message.

181 (Emit). Message is emitted from a channel. This may indicate a message leaving the iWay application or a message being transferred between iSM channels.

131 (Internal Event). Indicates the beginning or end of a certain event while processing the message. The RecordType for these entries is actually 131 plus an action code, the meaning of which can vary depending on the event type, but is typically 0, indicating the beginning of a certain processing stage. 1 indicates the successful completion of a stage. 2 indicates a failure of that state. For more information about other action codes, see the subtype field.

151 (Message). Indicates a BIZERROR message generated while processing the message.

TID

Char(48)

Transaction ID that identifies all activity for this message while being processed by the iWay application. The transaction ID remains constant when the message is transferred between iSM channels.

Note: An application can generate multiple messages from a single origin. All of these would share the same TID.

Recordkey101

Char(32)

The RecordKey of the start or enqueue entry that recorded the beginning of processing of this message on this channel. For example, it can be used to correlate start and end entries.

Correlid

Char(32)

Not used.

Version

Char(16)

iSM version.

Status

Int

The final status for processing of this message on this channel for end entry records (recordtype = 191). A value of 1 indicates success. Any value greater than 1 indicates failure.

Subtype

Int

The specific type of event for an event record. This can include, but is not limited to the following:

iSM life cycle events

Inbound decryption

Preparse

XML Parse

Inbound review

Inbound validation

Inbound Transform

Agent or Service

Outbound Transform

Outbound validation

Outbound review

Preemit

Outbound encryption

Emit

Subtype (continued)

Int (continued)

Emit Events

301. Records data that being emitted from iSM.

302. Records the response from the external system when data is emitted from iSM using a synchronous protocol.

Security Events

601. Events relating to a certain general security operation

602. Events relating to digital signatures. This type of event can use the following action codes: 3 (Sign), 6 (Verify), and 2 (Fail).

603. Events relating to encryption and decryption. This type of event can use the following action codes: 4 (Encrypt), 5 (Decrypt), and 2 (Fail).

Subtype (continued)

Int (continued)

User Events.

1000. Users can generate event entries in the activity log. User-created event codes must be greater than 1000.

Sequence

Int

In an iWay application in which a message is processed by multiple channels, the sequence indicates the order in which these channels received the message. This value is only stored with the start entry record (RecordType = 101).

Note: The sequence represents a logical, rather than chronological, ordering of channels. For example, if the channel with sequence 1 emits two messages to an internal queue for further processing, the start entry records on the internal channel for both of these messages will have a sequence of 2.

ResubmitCount

Int

The number of times this message has been resubmitted.

ResubmitSourceKey

Char(32)

The record key of the activity record that indicates the point in processing from which this message was extracted for resubmission.

Encoding

Varchar(16)

Character encoding of this message.

Signature

Varchar(64)

The name of the channel where this activity occurred.

MAC

Varchar(80)

Not used.

ConfigName

Varchar(128)

The iSM managed server or iIA on which this activity occurred.

HostName

Varchar(128)

The hostname of the system where this activity occurred.

Address

Varchar(128)

Not used.

Partner_to

Varchar(128)

Value of the partner_to special register if set to true, by certain EDI components.

Partner_from

Varchar(128)

Value of the partner_from special register if set to true, by certain EDI components.

Protocol

Varchar(150)

Protocol specific information. Simply, it is often the protocol name of the channel.

Field	Datatype	Description
RecordKey	char(32)	Primary key for this table and foreign key for RecordKey in BAM_ACTIVITY_EXTENDED and BAM_ACTIVITY_CONTEXT tables. This value is a GUID, with no intrinsic meaning except to uniquely identify an activity record.
Tstamp	Datetime	The time at which this activity record was logged, with precision down to the millisecond if the system supports it.
RecordType	Int	Type of activity record, using the following codes: 100 (Enqueue). Receipt of message on an iWay internal queue. 101 (Start). Start of processing for a message 191 (End). End of processing for a message. 181 (Emit). Message is emitted from a channel. This may indicate a message leaving the iWay application or a message being transferred between iSM channels. 131 (Internal Event). Indicates the beginning or end of a certain event while processing the message. The RecordType for these entries is actually 131 plus an action code, the meaning of which can vary depending on the event type, but is typically 0, indicating the beginning of a certain processing stage. 1 indicates the successful completion of a stage. 2 indicates a failure of that state. For more information about other action codes, see the subtype field. 151 (Message). Indicates a BIZERROR message generated while processing the message.
TID	Char(48)	Transaction ID that identifies all activity for this message while being processed by the iWay application. The transaction ID remains constant when the message is transferred between iSM channels. Note: An application can generate multiple messages from a single origin. All of these would share the same TID.
Recordkey101	Char(32)	The RecordKey of the start or enqueue entry that recorded the beginning of processing of this message on this channel. For example, it can be used to correlate start and end entries.
Correlid	Char(32)	Not used.
Version	Char(16)	iSM version.
Status	Int	The final status for processing of this message on this channel for end entry records (recordtype = 191). A value of 1 indicates success. Any value greater than 1 indicates failure.
Subtype	Int	The specific type of event for an event record. This can include, but is not limited to the following: iSM life cycle events Inbound decryption Preparse XML Parse Inbound review Inbound validation Inbound Transform Agent or Service Outbound Transform Outbound validation Outbound review Preemit Outbound encryption Emit
Subtype (continued)	Int (continued)	Emit Events 301. Records data that being emitted from iSM. 302. Records the response from the external system when data is emitted from iSM using a synchronous protocol. Security Events 601. Events relating to a certain general security operation 602. Events relating to digital signatures. This type of event can use the following action codes: 3 (Sign), 6 (Verify), and 2 (Fail). 603. Events relating to encryption and decryption. This type of event can use the following action codes: 4 (Encrypt), 5 (Decrypt), and 2 (Fail).
Subtype (continued)	Int (continued)	User Events. 1000. Users can generate event entries in the activity log. User-created event codes must be greater than 1000.
Sequence	Int	In an iWay application in which a message is processed by multiple channels, the sequence indicates the order in which these channels received the message. This value is only stored with the start entry record (RecordType = 101). Note: The sequence represents a logical, rather than chronological, ordering of channels. For example, if the channel with sequence 1 emits two messages to an internal queue for further processing, the start entry records on the internal channel for both of these messages will have a sequence of 2.
ResubmitCount	Int	The number of times this message has been resubmitted.
ResubmitSourceKey	Char(32)	The record key of the activity record that indicates the point in processing from which this message was extracted for resubmission.
Encoding	Varchar(16)	Character encoding of this message.
Signature	Varchar(64)	The name of the channel where this activity occurred.
MAC	Varchar(80)	Not used.
ConfigName	Varchar(128)	The iSM managed server or iIA on which this activity occurred.
HostName	Varchar(128)	The hostname of the system where this activity occurred.
Address	Varchar(128)	Not used.
Partner_to	Varchar(128)	Value of the partner_to special register if set to true, by certain EDI components.
Partner_from	Varchar(128)	Value of the partner_from special register if set to true, by certain EDI components.
Protocol	Varchar(150)	Protocol specific information. Simply, it is often the protocol name of the channel.

iWay Software