Network Deployment (Distributed operating systems), v8.0 > Develop and deploying applications > Develop EJB applications > Assembling EJB 2.1 enterprise beans
Set the run time for CMP sequence groups
By designating container managed persistence (CMP) sequence groups for entity beans, you can prevent certain types of database-related exceptions during the run time of your EJB application. Specify in each group the order in which the beans update your relational database tables.
When you define a sequence group, you designate it as one of two types:
Both types of sequence groups must be created after we have assembled the beans into an EJB module, before installing the application on the product. If edit sequence groups, uninstall the application, make your changes with an assembly tool, and reinstall the application.
- RI_INSERT, for setting a bean persistence sequence to prevent database referential integrity (RI) violations. See the topic Sequence grouping for container-managed persistence in assembled EJB modules for more information.
- UPDATE_LOCK, for setting a bean persistence sequence to minimize exceptions resulting from optimistic concurrency control
If you already selected or plan to use top-down mapping for mapping your enterprise beans to back-end data, you do not need to create a sequence group with an RI_INSERT type. The product does not generate an RI policy for the database schema that it creates when you select top-down mapping.
To learn how to complete this task see the assembly tool information center.
What to do next
You are now ready to deploy your EJB module or combine it with other modules into a Java EE application. For more information about these two tasks, see the topics Installing enterprise application files and Assembling Java EE client applications.
Sequence grouping for container-managed persistence in assembled EJB modules
Deploy and administering enterprise applications
Install enterprise application files
Assembling applications