Set the run time for CMP sequence groups

By designating container managed persistence (CMP) sequence groups for entity beans, we can prevent certain types of database-related exceptions from occurring during the run time of the EJBs application. Within each group we need to specify 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:

• RI_INSERT, for setting a bean persistence sequence to prevent database referential integrity (RI) violations

• UPDATE_LOCK, for setting a bean persistence sequence to minimize exceptions resulting from optimistic concurrency control

Both types of sequence groups must be created after we have assembled the beans into an EJB module, prior to installing the application on the product. to edit sequence groups, uninstall the application, make the changes using the following steps as a guide, and then reinstall the application.

If we already selected or plan to use top-down mapping for mapping the enterprise beans to back end data, you do not need to create a sequence group with an RI_INSERT type. WAS ND v7.0 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 at http://publib.boulder.ibm.com/infocenter/radhelp/v7r5mbeta/topic/com.ibm.jee5.doc/topics/cejb3.html

 

Next steps

we are now ready to deploy the EJB module or combine it with other modules into a J2EE application.

Sequence grouping for container-managed persistence

 

Related tasks

Deploy enterprise apps