The business object definition that the JDBC ODA generates contains:
This section describes:
The JDBC ODA generates the following information at the business-object level:
Application-specific information at the business-object level allows you to:
At the business-object level, application-specific information format consists of parameters separated by semicolon (;) delimiters. The name of the parameter and its value are separated by a colon (:) delimiter. The syntax is:
TN=TableName; SCN=StatusColumnName:StatusValue
where TableName identifies the database table, StatusColumnName is the name of the database column used to perform logical deletes, and StatusValue is the value that signifies that a business object is inactive or deleted.
The AppSpecificInfo that the JDBC ODA generates at this level contains a value only for the name of the database table, view, stored procedure, or synonym/nickname. For information on specifying a value for the status column, see Application-specific information at the business-object level.
This section describes the properties that the JDBC ODA generates for each attribute. For more information about the attributes, see Business object attribute properties.
The JDBC ODA obtains the value of the attribute's name from the column name in the database table, view, stored procedure, or synonym/nickname.
When setting the type of an attribute, the JDBC ODA converts the data type
of a column in the table or view to a corresponding IBM WebSphere Business
Integration Adapter Business Object type. This conversion is done in
two steps. First, the data type in the database is converted to a JDBC
type. Then, the JDBC type is converted to an IBM WebSphere Business
Integration Adapter Business Object type. The first conversion is done
by the JDBC driver that you are using. Please refer to the JDBC
specification (2.0 and later) for details on individual database type
mapping to a JDBC type. Table 9 shows the conversion from the JDBC Type to the corresponding
IBM WebSphere Business Integration Adapter Business Object type.
Table 9. Correspondence of data types
JDBC type | WebSphere Business Integration Adapter business object type |
---|---|
BIT |
BOOLEAN |
CHAR |
STRING |
VARCHAR |
STRING |
LONGVARCHAR |
STRING |
INTEGER |
INTEGER |
NUMERIC |
INTEGER |
SMALLINT |
INTEGER |
TINYINT |
INTEGER |
BIGINT |
INTEGER |
DATE |
DATE |
TIME |
DATE |
TIMESTAMP |
DATE |
DECIMAL |
STRING |
DOUBLE |
DOUBLE |
FLOAT |
DOUBLE |
REAL |
FLOAT |
BINARY |
STRING, add BYTEARRAY=TRUE to AppSpecificInfo |
VARBINARY |
STRING, add BYTEARRAY=TRUE to AppSpecificInfo |
The JDBC ODA sets the cardinality of all simple attributes to 1.
The JDBC ODA obtains the length of a string from the length specified for the varchar, char, or text data type.
If the column is a primary key in the table, the JDBC ODA marks it as a key attribute. However, if a view, stored procedure, or synonym/nickname, instead of a table, is selected as the source node to generate Business Objects, the JDBC ODA does not mark the column as a key attribute. In this case, the key attribute needs to be set manually.
The JDBC ODA does not set the IsForeignKey property. You can set it in Business Object Designer.
If a field is designated not null in the table, view, stored procedure, or synonym/nickname, the JDBC ODA marks it as a required attribute. However, the JDBC ODA does not mark the key field as required because there may be a sequence associated with it, or it may be an identity column.
The JDBC ODA includes two parameters for the AppSpecificInfo property at the attribute level. The syntax of the specified parameters are:
CN=ColumnName
where ColumnName is the name of the column in the database table, view, stored procedure or synonym/nickname associated with the specific attribute.
BYTEARRAY=true|false
The JDBC ODA recognizes columns with binary data and creates an attribute of type String with an AppSpecificInfo property of BYTEARRAY=true.
The JDBC ODA generates the verbs specified in the BO Properties window. It creates an AppSpecificInfo property for each verb but does not populate it. For more information, see Application-specific information format for verbs.