Describes the purpose and syntax of the serviceDeploy command
including a description of all of the parameters and their values. An example
of the command is included.
Purpose
The
serviceDeploy command
builds an .ear file from a .jar file that contains service components.
Note: Parameters
are not case-sensitive.
Roles
This command can be issued by users with the
following roles:
Syntax
serviceDeploy inputarchive [<-workingDirectory temppath> <-outputAppliation outputpathname.ear> <-noJ2eeDeploy true|false> <-freeform true|false > <-cleanStagingModules true|false> <-keep true|false> <-ignoreErrors true|false> <-classpath jarpathname;rarpathname;warpathname;... -help]
Parameters
- inputarchive
- A required, positional parameter that specifies the .jar, .zip or .ear
file that contains the application to be deployed. If the command is not issued
from the path in which the file resides, this must be the full path for the
file. The .zip file can be either a nested archive or an Eclipse ProjectInterchange
format file.
- -classpath
- An optional parameter that specifies the locations of required resource
files (.ear .jar, .rar and .war) files. The path to each file should be a
fully-qualified path separated by semicolons (;) with no spaces. Omitting
this parameter results in serviceDeploy searching only
the path from which the command is entered.
- -freeform
- An optional parameter that specifies that the J2EE subdirectory in the service.jar
should be treated as a free-form project. The default value is false.
- -help
- An optional parameter used to display the parameters for this command.
- -ignoreErrors
- An optional parameter that specifies that serviceDeploy builds
an .ear file regardless of errors while building or validating the application.
The default for this parameter is false.
- -cleanStagingModules
- An optional parameter that specifies whether to delete staging modules
within an input .ear file before deployment. The default for this parameter
is false.
- -keep
- An optional parameter that specifies whether to save any temporary files
generated after deployment. The default for this parameter is false.
- -noJ2eeDeploy
- An optional parameter that specifies whether the application requires
EJB deployment after generating the .ear file. The default for this parameter
is false.
- -outputApplication
- An optional parameter that specifies the name of the .ear file serviceDeploy
creates. The default is inputjarfile.ear, where inputjarfile is
the filename minus the extension specified for the input .jar file.
- -workingDirectory
- An optional parameter that specifies a directory serviceDeploy uses
to write temporary files.
Output
When serviceDeploy completes
processing, it creates an .ear file in the directory from which the command
is run unless the -outputApplication parameter is specified.
Example of serviceDeploy command
The
following command example:
- Creates an application file called MyValueModule.ear from
the MyValueModule.jar file.
- Specifies that the resources reside in the directories c:\java\myvaluemoduleres.rar, c:\java\commonres.ear and c:\java\myvaluemodweb.war.
- Enables the J2EE subdirectory within the .jar file as free-form.
- Keeps the temporary files generated during deployment.
servicedeploy MyValueModule.jar
-classpath c:\java\myvaluemoduleres.rar;c:\java\commonres.ear;c:\java\myvaluemodweb.war
-noj2eedeploy true -freeform true -keep