SerialMessage is an application specific business object (ASBO) that holds the representation of the triggering business object that is stored in the database.
SerialMessage is created in a collaboration object based on the MessageStore collaboration template and is stored in the database by the JDBCConnector. (The JDBCConnector is the runtime portion of an IBM® WebSphere® Business Integration Adapter for JDBC.) The business-object-level application specific information field contains the name of the table in the database where the object is stored. The format is: TN=SerialMessages (assuming that the table name is SerialMessages).
Name | Type | Description | Key | App Spec Info |
---|---|---|---|---|
ObjectKey | If the GENERATE_KEY property of the Message Store collaboration object is false, ObjectKey is type String. If GENERATE_KEY is true, ObjectKey is type Integer. | Holds the unique key used to store the object in the database. The unique key is comprised of one or more attributes in the triggering business object concatenated together. Each of these object attributes must be of type String. The attributes of the triggering business object that make up the key are specified by the OBJECT_KEY property of the MessageStore collaboration object. | x | If GENERATE_KEY is false, CN= ObjectKey::::. If GENERATE_KEY is true, CN= ObjectKey:: UID=xxx::: (where xxx determines how the key is generated — see the Adapter for JDBC user guide). |
ObjectData | String | Holds the triggering business object after it has been converted to a serial data string by the IBM® WebSphere® Business Integration Data Handler for XML. | CN= ObjectData::::: |
To examine a listing of the attributes of the SerialMessage business object, use the System Manager or Business Object Designer.
For more information on related business objects, collaboration templates, and other components, see the following:
Parent topic: PIMR business objects