The business object definition that SiebelODA generates contains:
When generating business objects by getting the information from the Siebel application server, the application-specific information generated is for simple attributes only. The exception to this rule is if the container attribute is a multi-value link. In all other cases, the user must enter the application-specific information as described in Supporting Siebel business services.
This section describes:
SiebelODA generates the following information at the business-object level:
Application-specific information at the business-object level contains the name of the corresponding Siebel business object or business component.
This section describes the properties that SiebelODA generates for each attribute.
SiebelODA obtains the value of the attribute's name from the corresponding attribute in the Siebel business component.
When setting the type of an attribute, SiebelODA converts the data type of the attribute in the Siebel business component and converts it to the corresponding data type, as shown in Table 12. This is only in the case of business object generation, since business object conversion is for existing business objects.
Table 12. Correspondence of data types
Application | WebSphere business integration system | Length |
DTYPE_BOOL |
BOOLEAN |
|
DTYPE_ID, DTYPE_PHONE |
STRING |
Length of corresponding attribute in the Siebel application server |
DTYPE_TEXT DTYPE_NOTE | ||
DTYPE_DATE DTYPE_TIME DTYPE_DATETIME DTYPE_UTCDATETIME |
DATE |
|
DTYPE_INTEGER DTYPE_NUMBER |
INTEGER |
|
DTYPE_CURRENCY |
DOUBLE |
SiebelODA sets the cardinality of all simple attributes to 1 and the container attributes to n. The user should change the cardinality of the container attributes wherever it is needed. For example, if the container attribute turns out to be a PickList, the user needs to set the cardinality to 1.
SiebelODA obtains the length of the attribute from the Siebel application server.
If the column is a primary key in the table or view, SiebelODA marks it as a key attribute. In the case of business object generation, the Id attribute is the only one marked as key by default.
If a field is designated not null in the table or view, SiebelODA marks it as a required attribute. However, SiebelODA does not mark the key field as required because the Siebel application generates its own Id values while creating a record.
The user should edit this property if container attributes have not been generated and ensure the correctness if container attributes have been generated.
Number of rows in the database table that the connector retrieves per polling interval. Allowable values are 1 to 500.
The default is 1.
SiebelODA generates the verbs specified in the BO Properties window. It creates an AppSpecificInfo property for each verb but does not populate it.