EJB Deployment
- EJB deployment tool
- Prerequisite tasks
- Generate EJB deployment code from the command line
- Generate EJB deployment code from the workbench
- Converters and composers
- DB2 SQLJ
- Mapping editor
- Approaches for mapping enterprise beans to database tables
- Specify optimistic concurrency control scheme for EJB 2.x CMP entity
- Requirements for deploying EJB applications using SQLJ
- Access intent and isolation levels
- The ejbdeploy command
- Message format for EJB validation
- Limitations of EJB deployment
- Limitations of EJB mapping tools
- Add the SQLJ run-time JAR file to the class path
- Add a column for collision detection
- Add a column for collision detection when the CMP bean exists
- Add a column for collision detection when generating a top-down
- Configure your application to use SQLJ instead of JDBC
- Delete deployment code
- Delete maps and schemas
- Installing the EAR file on the server
- Create EJB mappings
- Specify a discriminator column and value
- Create inheritance maps
- Create many-to-many (M:M) relationship maps
- Generate a meet-in-the-middle mapping
- Including an attribute in a predicate for optimistic access intents
- Avoiding overlapping maps
- Update maps with the Mapping editor
- Removing mappings via the Mapping editor
- Create secondary table maps
- Generate a top-down mapping
- Create and mapping unmapped elements
- Mapping database views
- Run the EJB deployment tool
- Specify a different location for the SQLJ translator and main class
- Configure EJB applications to use SQLJ instead of JDBC for enterprise
- Preliminary steps for running the DB2 SQLJ profile customizer using the Ant
- Deploying the EAR file
- Run the ejbdeploy command
- Run the Ant script
- Deploying EJB applications using SQLJ for data access
- Create a new EJB composer
- Create a new EJB converter