The runAssembler
command takes a number of command-line flags that you can use individually or in combination to alter the output of the command. These can be supplied as follows:
runAssembler [-liveconfig] [
cmd-options
]
earfilename
[-layerlayer-name
] [-standalone]
-mmodule-list
Ordering is significant with respect to the following command options:
–liveconfig
must follow therunAssembler
command-standalone
must precede–m
-layer
must precede–standalone
and–m
The following table describes runAssembler
options.
Option | Description |
---|---|
| Includes the contents from an existing EAR file in the assembled EAR file. See Including an Existing EAR File, below. |
| Instead of assembling a complete EAR file, creates a JAR file that collapses the JAR files and directories in the CLASSPATH into a single library. |
| Collapses all JAR files and directories in the CLASSPATH into a single JAR file in the assembled EAR file. By default, these JAR files and directories are copied separately to the EAR file’s |
| Specifies a Java properties file whose settings are used to override the default context root values for any web applications included in the assembled EAR file. To specify the context root for a web application in this properties file, add a line with the following format:
where |
| Specifies the value for setting the display name in the |
| JBoss requires that your If the |
| Collapses all |
| Required for applications running on JBoss. For JBoss, the following line is required in the
The |
| Enables one or more Named Configuration layers for the application. This switch can take multiple arguments, each representing a named configuration layer. This option must immediately precede the |
| Enables the |
| Instructs By default the
to
The
|
| Overwrites all resources in the existing EAR file. By default, resources in the assembled EAR are only overwritten if the source file is newer, to reduce assembly time. |
| Packs the assembled EAR file into the archived J2EE enterprise archive format. By default, the EAR is assembled in an exploded, open-directory format. |
| Includes the comma separated list of jar files on the
Note: Special characters appearing in jar file names might cause that file to be ignored. When naming files, use only alphanumeric characters and the underscore. |
| JBoss 6.1 only; this option should be used only in development environments. When assembling the EAR file with |
| Specifies the value for the |
| Configures the assembled EAR in standalone mode, so that it contains all application resources, including Nucleus configuration files, and does not refer to the Oracle Commerce Platform installation directory. By default, the EAR is assembled in development mode, where only classes, libraries, and J2EE modules are imported to the EAR file, and Nucleus configuration and other resources are used directly from the Oracle Commerce Platform install directory. |