InfoCenter Home >
6: Administer applications >
6.6: Tools and resources quick reference >
6.6.35: Administering generation of deployment code >
6.6.35.0: Assembly properties for generating deployment code

6.6.35.0: Assembly properties for generating deployment code

Deployed module location (Required, String)
Specifies the name and location where the deployed archive will be saved. By default, this is the directory where you saved the archive file or the directory from which you launched the Application Assembly Tool. The deployed archive file is given the same name as the undeployed archive, prefixed with deployed_.

Working directory (Required, String)
Specifies the full path name of the working directory. This directory is used to save temporary files while creating the deployed archive. On UNIX systems, if there is insufficient space in the working directory, a segmentation violation error can occur. Make sure that there is sufficient space in the working directory. Required space varies depending on the application. By default, the working directory is /tmp on UNIX systems. You can specify a different working directory by using this field.

Dependent classpath
Specifies the class path where dependent class files can be found, if needed by the module being deployed. List only additional JAR files referred to by the JAR file being deployed. On Windows NT systems, separate each path by a semicolon (;). On UNIX systems, separate each path by a colon (:). Use one entry for each directory or JAR file to be searched. Files without the extension .jar or .zip are ignored.

Code generation only
Specifies that only stub and skeleton files are to be generated. The RMIC command and javac compiler are not to be run. The default is false (that is, all steps are executed).

Verify archive
Specifies whether verification is to take place during deployment. The default is false. Verification checks the completeness of the archive and ensures that the classes in the EJB JAR files are in compliance with the EJB 1.1 specification. Note that verifying archive files is important for successful generation of deployment code for the application. If an archive file is not valid, code generation can fail.

RMIC options
Specifies additional options to be passed to the RMIC command. These additional options are appended to the following options, which are always passed to the RMIC command and cannot be overridden: -keep (keeps intermediate generated files), -iiop (generates stubs for IIOP), -d directory_name (writes the files to the specified directory), -sourcepath directory_name (locates the source files in the specified directory), and -nowrite (compiled classes are not written to the file system).

Database type
Specifies the database type, operating system, and version number. This information is used when generating the SQL code for creating database tables for entity beans with container-managed persistence (CMP).

Database name
Specifies the name of the database. This information is used when generating the SQL code for creating database tables for entity beans with container-managed persistence (CMP). The database name is used in the generated DDL file.

Schema name
Specifies the name of the database schema. This information is used when generating the SQL code for creating database tables for entity beans with container-managed persistence (CMP). The schema name is used in the generated DDL file and in the generated persistence code.
Go to previous article: Administering generation of deployment code Go to next article: Administering Java Virtual Machine settings (overview)

 

 
Go to previous article: Administering generation of deployment code Go to next article: Administering Java Virtual Machine settings (overview)