Provide options to perform the EJB Deploy settings (deprecated)

Specifies the class path of one or more zipped or Java™ archive (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 that 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.

Specifies 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.

Specifies the 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 you 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.

Database type is the same as the ejbdeploy command parameter -dbvendor name.

Specifies the name of the schema that you want to create.

The EJB deployment tool saves database information in the schema document in the JAR or EAR file, which means that 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.

Specifies the 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, you must select a DB2 backend database that supports SQLJ from the Database type drop-down list.

Available database access types include JDBC and SQLJ.

Specifies the class path of the DB2 SQLJ tool sqlj.zip file. The product uses this class path to run the DB2 SQLJ tool during application installation and generate SQLJ profiles (.ser files).

To view this setting, you must 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 you do not specify a class path, the product displays a warning about the missing class path. After you specify a valid class path, you can continue using the wizard for the application installation.

You can customize or add bindings to the generated SQLJ profile after the product installs the application. Use the administrative 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.

Specifies the Java developer kit compiler compliance level as 1.4, 5.0, 6.0, or 7.0 when you include application source files for compilation.

The default is to use whatever developer kit version the ejbdeploy command is using. For example, if your application is using new functionality defined in Version 7.0 or you are including source files (which is not recommended), then you must specify the Version 7.0 level.

The Java SE Development Kit compliance level that you specify must be the same level as the default Java SDK for the application server to which you are deploying your application. For example, if you select 8.0 for the Java SE Development Kit compliance level on this page, you must ensure that Java SE Development Kit 8.0 is installed and that the default Java SDK for the application server is set to 8.0. The Java SDKs page of the administrative 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.