Once you have created your model, schema, and data store map, and generated their supporting code, you can then create the application layer that will manage the business objects. If you plan to create a user interface, you can use the parts in theObjectExtender palette category on the Composition Editor. These parts are transaction-aware, that is, they understand transaction semantics such as #begin, and #commit.
Depending on your requirements, you can build nearly all of your application using VisualAge tools with very little scripting; you can build the persistence layer with the ObjectExtender tool set, and the user interface with the Composition Editor utilizing the ObjectExtender parts as well as the other parts available for building user interfaces.
If your application will not utilize a user interface, there are some details you will need to code in the code to manage your business objects, such as activating the data store, beginning transactions, creating business objects, and so on.
This section collects some of the details useful for programmers who are applying business rules and application logic to the model domain.