In brief, use the Model Browser to define your object model. Your object model is a collection of business objects represented in terms of classes and associations. Once defined, the persistence support for your model is created by using code generation services.
To create a new object model, first determine the business objects in your model that will persist to the data store, then create the classes and associations that will represent your business objects.
Creating models. To create a model:
Creating classes. Continue defining the model by creating the classes and associations that represent the business objects for the model. To create a class:
Creating associations. To create an association between two classes:
Generating business objects. After you have completed the model description, generate the domain classes using the code generation services.
What the code generation services create. The generation of the model will produce the following:
Once the business object classes are generated, you can create transactional instances of the classes and manipulate them and their relationships in transactions. Refer to Managing business objects.
Saving models. Save your model definition to an application and storage class that you supply. Saving your model enables you to take advantage of the existing library management functions. These functions are the same ones you use when sharing code with other developers such as versioning, releasing, and loading different editions of an application.
Suggestion: A useful naming convention is to name your application as follows: XYZMetadataApp where the XYZ is some prefix you choose. Use this application to store a model, schema, and map for a given application.
Recommendation:Save the model definition to an application different from the generated model calsses. The model will generate into any previously generated schema that has the same name as the one it would have created. For existing columns, it does not modify information such as field type or length. If attributes or roles are deleted, the previously generated columns are not dropped and this is managed by the user.