Business object names should reflect the structure they represent, such as Customer or Address. Names will most likely be derived during the metadata import process of enterprise metadata discovery, based on the name given by the enterprise information system (EIS).
Business object names should be converted to camel case, in which separators like spaces and underscores are removed, and the first letter of each word is capitalized; for example, ORDER_LINE_ITEM would be converted to OrderLineItem.
The parent business object graph should be named for the contained business object, followed by BG; for example, CustomerBG for a Customer business object.
Business object names have no semantic value to the adapter or the database.
Business objects carry database-specific metadata. They can have a string like JDBC or %AppName% as a prefix to help distinguish between the two types of business objects: application-specific and generic. The remainder of the name can describe the table or stored procedure that the business object represents. For example, if the business object definition is generated for the Employee Table in a database application, such as Human Resources (HR), the respective business object name will be HREmployee.
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)