WAS v8.5 > Reference > Sets
Provide options to perform the EJB Deploy settings page
Use this page to specify options for the EJB deployment tool. The tool generates code needed to run enterprise bean files. We can specify extra class paths, Remote Method Invocation compiler (RMIC) options, database types, and database schema names to be used while running the EJB deployment tool.
This dmgr console page is a step in the application installation and update wizards. To view this page, select Deploy enterprise beans on the Select installation options page. Thus, to view this page, click Applications > New Application > New Enterprise Application > application_path > Next > Detailed - Show all installation options and parameters > Next > Deploy enterprise beans > Next > Step: Provide options to perform the EJB Deploy.
We can specify the EJB deployment tool options on this page when installing or updating an application containing EJB modules. The EJB deployment tool runs during installation of EJB 1.x or 2.x modules. The EJB deployment tool does not run during installation of EJB 3.x modules.
The options specified set parameter values for the ejbdeploy command. The tool, and thus the ejbdeploy command, is run on the EAR file during installation after you click Finish on the Summary page of the wizard.
Class path
Class path of one or more zipped or JAR files on which the JAR or EAR file being installed depends.
To specify the class paths of multiple entries, the file names must be fully qualified, separated by a path separator the target server uses, and enclosed in double quotation marks.
On Windows operating systems, the path separator is a semicolon (;). For example:
- path\myJar1.jar;path\myJar2.jar;path\myJar3.jar
On the other supported operating systems, the path separator is a colon (:). For example:
- path/myJar1.jar:path/myJar2.jar:path/myJar3.jar
Class path is the same as the ejbdeploy command parameter -cp class_path.
| Information | Value |
|---|---|
| Data type | String |
| Default | null |
RMIC
Whether the EJB deployment tool passes RMIC options to the Remote Method Invocation compiler. Refer to RMI Tools documentation for information on the options.
Separate options by a space and enclose them in double quotation marks. For example:
- "-nowarn -verbose"
The RMIC setting is the same as the ejbdeploy command parameter -rmic "options".
| Information | Value |
|---|---|
| Data type | String |
| Default | null |
Database type
Name of the database vendor, which is used to determine database column types, mapping information, Table.sql, and other information. Select a database type or the empty choice from the drop-down list. The list contains the names of valid database vendors. Selecting the empty choice sets the database type to "" (null).
If we specify a database type, previously defined backend IDs for all of the EJB modules are overwritten by the chosen database type. To enable backend IDs for individual EJB modules, select the empty choice to set the database type to null.
Deprecated feature: The backend IDs SQL92 (1992 SQL Standard) and SQL99 (1999 SQL Standard) are deprecated. Although the SQL92 and SQL99 backend IDs are available in the list on the Provide options to perform the EJB Deploy page, they are deprecated.
Database type is the same as the ejbdeploy command parameter -dbvendor name.
| Information | Value |
|---|---|
| Data type | String |
| Default | DB2UDB_V82 |
Database schema
Name of the schema to create.
The EJB deployment tool saves database information in the schema document in the JAR or EAR file, which means the options do not need to be specified again. It also means that when a JAR or EAR is generated, the correct database must be defined at that point because it cannot be changed later.
If the name of the schema contains any spaces, the entire name must be enclosed in double quotes. For example:
- "my schema"
Database schema is the same as the ejbdeploy command parameter -dbschema "name".
| Information | Value |
|---|---|
| Data type | String |
| Default | null |
Database access type
Database access type for a DB2 database that supports Structured Query Language for Java (SQLJ). Use SQLJ to develop data access applications that connect to DB2 databases. SQLJ is a set of programming extensions that support use of the Java programming language to embed statements that provide SQL (Structured Query Language) database requests.
To view this setting, select a DB2 backend database that supports SQLJ from the Database type drop-down list.
Available database access types include JDBC and SQLJ.
| Information | Value |
|---|---|
| Data type | String |
| Default | JDBC |
SQLJ class path
Class path of the DB2 SQLJ tool sqlj.zip file. WAS v8.5 uses this class path to run the DB2 SQLJ tool during application installation and generate SQLJ profiles (.ser files).
To view this setting, select a DB2 backend database that supports SQLJ from the Database type drop-down list.
Specify the drive and directory where the sqlj.zip file resides. For example:
On Windows operating systems, specify c:\SQLJ\sqlj.zip.
On all other operating systems, specify /SQLJ/sqlj.zip.
When you reinstall an application EAR file, the product deletes any existing SQLJ profiles and creates new profiles.
If we do not specify a class path, the product displays a warning about the missing class path. After we specify a valid class path, we can continue using the wizard for the application installation.
We can customize or add bindings to the generated SQLJ profile after the product installs the application. Use the dmgr console SQLJ profiles and pureQuery bind files page accessed by clicking Applications > Application Types > WebSphere enterprise applications > application_name > SQLJ profiles and pureQuery bind files.
| Information | Value |
|---|---|
| Data type | String |
| Default | null |
JDK compliance level
Java developer kit compiler compliance level as 1.4, 5.0, 6.0, or 7.0 when we include application source files for compilation.
The default is to use whatever developer kit version the ejbdeploy command is using. For example, if the application is using new functionality defined in v7.0 or you are including source files (which is not recommended), then specify the v7.0 level.
The JDK compliance level specified must be the same level as the default Java SDK for the application server to which we are deploying the application. For example, if you select 7.0 for the JDK compliance level on this page, ensure that JDK 7.0 is installed and the default Java SDK for the application server is set to 7.0. The Java SDKs page of the dmgr console lists the software development kits that are installed on the node and enables you to select a default SDK for the node or server. To view the Java SDKs page, click Servers > Server Types > WebSphere application servers > server_name > Java SDKs.
JDK compliance level is the same as the ejbdeploy command parameter -complianceLevel "1.4"| "5.0"| "6.0"| "7.0".
| Information | Value |
|---|---|
| Data type | String |
| Default | null (empty string) |
Related concepts:
Enterprise (Java EE) applications
Related
Install enterprise application files with the console
Reference:
Enterprise application settings