The EJB deployment tool is invoked from the command line using the ejbdeploy command, which accepts an input EJB JAR or EAR file that contains one or more enterprise beans. It then generates an output, deployed JAR file or EAR file that contains deployment code in the form of .class files.
For a complete description of all of the options available to the ejbdeploy, see the related reference The ejbdeploy command.
The EJB deployment tool supports EJB single and multiple table inheritance. It supports the use of converters, which translate a database representation to a Java™ object type, and composers, which are used to map a single, complex bean field to multiple database columns. The EJB deployment tool supports the following levels of access intent (where AccessIntent is a WebSphere® extension):
For more information on these access intents, see the related topic Access intent and isolation level.
In addition to these values, an access intent can also contain an optional read ahead hint.
META-INF\backends\backend_id\databasename.dbm
META-INF\backends\backend_id\Table.ddl
If multiple backends exist and you did not set the current back-end ID in the EJB deployment descriptor, the EJB deployment tool will default to the first back-end ID that appears as a folder in the respective META-INF\backends directory as described earlier. If you map to a single backend database, then the generated DDL file will appear both in the directory as described above and also in the META-INF folder.
Also refer to Message format for EJB validation to understand the format used for messages generated by the EJB validator.