The attributes of a business object are built from the list of columns in the database object. The enterprise service discovery wizard sets the attribute name to the name of the column. Globalized characters are supported in the attribute names. The adapter adds the attribute name, type, and application-specific information.
The types returned by the JDBC metadata are mapped to the business object attribute types as listed in the table "JDBC metadata column and business object attribute types." Only the JDBC types listed are supported by the adapter. Any columns with types not listed are not added to the business object. An informational message is produced stating, for example, The column named xxxx in the table named yyyy is not of a supported type and will not be added to the business object.
JDBC metadata column and business object attribute types
JDBC metadata column type | Business object attribute type |
---|---|
BIT | BOOLEAN |
CHAR |
STRING |
INTEGER |
INTEGER |
TIME |
DATE |
DECIMAL | STRING |
DOUBLE FLOAT | DOUBLE |
REAL | FLOAT |
The table titled "Attribute information" lists the attribute information set by the enterprise service discovery wizard and describes how it is set.
Attribute information
Attribute information | Set by enterprise service discovery | Additional information |
---|---|---|
Cardinality | No | |
Name | Yes | Name of the attribute. This is enabled for bidirectional languages. |
MinOccurs/MaxOccurs | Yes | If the column is not a primary key and is not nullable, the attribute is required, and the values for the attribute will be set to at least 1. |
Type | Yes | Set as shown in the table titled "JDBC metadata column and business object attribute types." |
The enterprise service discovery wizard sets the attribute application-specific information (ASI) in the business object as shown in the table titled "Attribute application-specific information." For more information on the attribute application-specific information see "Application-specific information for simple attributes."
Attribute application-specific information
Attribute ASI | Set by enterprise service discovery | Additional information |
---|---|---|
ColumnName | Yes | Set to the actual name of the column. This is enabled for bidirectional languages. |
FixedChar | No | Needs to be updated manually in the business object .xsd file. Use either text mode or the business object editor in WebSphere Integration Developer to edit the file. After updating the file, ensure there are no validation errors. See an example of FixedChar in an .xsd file in the section "Application-specific information for simple attributes." |
ForeignKey | No | |
OrderBy | No | |
PrimaryKey | Yes | If the column is a primary key, PrimaryKey will be set to true. |
UID | No |
If you choose to add stored procedures to the business objects, the verb application-specific information (ASI) is set as specified in the table titled "Verb application-specific information." For information on valid stored procedure types, see the section "Verb application-specific information."
Verb application-specific information
Verb ASI or Stored procedure parameters element | Set by enterprise service discovery wizard | Additional information |
---|---|---|
Parameters | Yes | Lists the stored procedure parameters. This is enabled for bidirectional languages. |
PropertyName | Yes | Set to the name of the business object attribute that you select. This is enabled for bidirectional languages. |
ResultSet | No | If the stored procedure returns a ResultSet, you need to set this parameter to true in the business object definition. |
StoredProcedure | Yes | Set to the stored procedure name. This is enabled for bidirectional languages. |
StoredProcedure Type | Yes | You choose from a list of types. |
Type | Yes | Set to the type of the stored procedure parameter (IP/OP/IO) . |
To build hierarchical business objects
The enterprise service discovery wizard generates flat business objects. It does not use the foreign key constraints that are defined in the database between different tables to build relationships automatically. These need to be linked manually. You can update the business object definitions either in text mode or by using the business object editor.
An example of the .xsd definition file for single- and multiple-cardinality child business objects is provided here. The element custInfoObj is a single-cardinality child business object, and addressObj is a multiple-cardinality child business object.
<element name="addressObj" minOccurs="1" type="Address:Address" maxOccurs="unbounded"> <annotation> <appinfo source="WBI"> <pasi:JDBCAttributeTypeMetadata xmlns:pasi= "urn:app:jdbc:asi"> <pasi:Ownership>true</pasi:Ownership> </pasi:JDBCAttributeTypeMetadata> </appinfo> </annotation> </element> <element name="custInfoObj" minOccurs="0" type= "CustInfo:CustInfo" maxOccurs="1"> <annotation> <appinfo source="WBI"> <pasi:JDBCAttributeTypeMetadata xmlns:pasi= "urn:app:jdbc:asi"> <pasi:Ownership>false</pasi:Ownership> </pasi:JDBCAttributeTypeMetadata> </appinfo> </annotation> </element>
Last updated: Thu Mar 23 13:24:30 2006
(c) Copyright IBM Corporation 2005.
This information center is powered by Eclipse technology (http://www.eclipse.org)