+

Search Tips   |   Advanced Search

Provide options to perform the EJB Deploy settings

Use this panel to specify options for the enterprise bean (EJB) deployment tool. The tool generates code needed to run enterprise bean files. You 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 console panel is a step in the application installation and update wizards. To view this panel, select Deploy enterprise beans on the Select installation options panel. Thus, to view this panel, click Applications > Install New Application > application_path > Show me all installation options and parameters > Next > Next > Deploy enterprise beans > Next > Step: Provide options to perform the EJB Deploy.

You can specify the EJB deployment tool options on this panel only when installing or updating an application that contains EJB modules.

The options specified set parameter values for the ejbdeploy command. The tool, and thus the ejbdeploy command, is run on the enterprise archive (EAR) file during installation after you click Finish on the Summary panel of the wizard.

Deploy EJB option - Class path

Specify the class path of one or more zipped or Java archive (JAR) files on which the Java archive (JAR) or EAR file being installed depends.

To specify the class paths of multiple zipped and JAR files, the zipped and JAR file names must be fully qualified, separated by semicolons, and enclosed in double quotation marks. For example:

path\myJar1.jar;path\myJar2.jar;path\myJar3.jar

Deploy EJB option - Class path is the same as the ejbdeploy command parameter -cp class_path.

Data type String
Default null

Deploy EJB option - RMIC

Specify 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"

Deploy EJB option - RMIC is the same as the ejbdeploy command parameter -rmic "options".

Data type String
Default null

Deploy EJB option - 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 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.

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, they are deprecated.

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

Data type String
Default DB2UDB_V82

Deploy EJB option - 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 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"

Deploy EJB option - Database schema is the same as the ejbdeploy command parameter -dbschema "name".

Data type String
Default null




 

Related concepts


Enterprise (J2EE) applications

 

Related tasks


Installing application files with the console

 

Related Reference

Enterprise application settings

 

Related information


The ejbdeploy command

 

Reference topic