WebSphere Adapter for JDBC
Business object names should reflect the structure they represent, such as Customer or Address. Names are normally derived during the metadata import process of enterprise metadata discovery, based on the name given by the enterprise information system (EIS).
Enterprise metadata discovery replaces any special character in the business object name with U followed by its Unicode number, except for names that have the underscore (_) character. For example, the business object name would be Order_Item for the Order_Item table in the database application and ShippingU45Address for the Shipping-Address table.
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; that is, they derive no information nor meaning from the business object name. If one name is replaced by another, the adapter behavior remains the same.
Business objects carry database-specific metadata. A name can use 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.
An example of business object names not derived through the metadata import process are names for query business objects that you specify by using the enterprise service discovery wizard. Avoid specifying duplicate names for different query business objects, otherwise the names will be overwritten.
You can rename business objects by using the refactoring functionality in WebSphere® Integration Developer. For more details, refer to the WebSphere Integration Developer documentation.
Last updated: Tue 12 Dec 2006 03:32:38
(c) Copyright IBM Corporation 2005, 2006.
This information center is powered by Eclipse technology (http://www.eclipse.org)