The business object definition that PortalODA generates contains:
When generating business objects by getting the information from Portal Infranet, 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 Understanding business objects.
This section describes:
PortalODA generates the following information at the business-object level:
Application-specific information at the business-object level contains the name of the corresponding Portal Infranet business component.
This section describes the properties that PortalODA generates for each attribute.
PortalODA obtains the value of the attribute's name from the corresponding attribute in the Portal Infranet business component.
When setting the type of an attribute, PortalODA converts the data type of the attribute in the Portal Infranet business component and converts it to the corresponding data type, as shown in Table 10. This is only in the case of business object generation, since business object conversion is for existing business objects.
Table 10. Correspondence of data types
Application | WebSphere business integration system | Length |
PIN_FLDT_INT | Integer | |
PIN_FLDT_ENUM | Integer | |
PIN_FLDT_STR | String | Length of corresponding attribute in Portal Infranet |
PIN_FLDT_BUF | String | Length of corresponding attribute in Portal Infranet |
PIN_FLDT_POID | String | Length of corresponding attribute in Portal Infranet |
PIN_FLDT_TSTAMP | Date | |
PIN_FLDT_ARRAY | Object | |
PIN_FLDT_SUBSTRUCT | Object | |
PIN_FLDT_BINSTR | String | Length of corresponding attribute in Portal Infranet |
PIN_FLDT_DECIMAL | Float |
PortalODA 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.
PortalODA obtains the length of the attribute from Portal Infranet.
PortalODA does not mark any attributes as key fields. You must manually mark the key fields after the business objects are generated.
If a field is designated not null in the table or view, PortalODA marks it as a required attribute. However, PortalODA does not mark the key field as required because the Portal Infranet 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.
PortalODA generates the verbs specified in the BO Properties window (as illustrated in Figure 23). It creates an AppSpecificInfo property for each verb but does not populate it.