 |
|
|
NAME
| | deploydir - deploys the J2EE component that is in the directory located on
the server machine |
SYNOPSIS
| | deploydir --user admin_user[ --password admin_password ] [ --host localhost ]
[ --port 4848 ][ --passwordfile filename ][ --secure |-s ]
[ --virtualservers virtual_servers ] [ --type application|ejb|web|connector ]
[ --contextroot context_root ] [ --force=true ] [ --precompilejsp=false ]
[ --verify=false ][ --name component_name ] [ --availabilityenabled ]
[ --instance instancename ] dirpath |
| |
Use the deploydir command to deploy the J2EE component
that is in the directory located on the server machine. If you use the asadmin deploydir command to deploy a directory instead of an EAR
file, your directory structure holding the individual modules must be named
with _jar, _war and _rar suffixes.
The --force option makes sure the component is forcefully
(re)deployed even if the specified component has already been deployed or
already exists. Set --force to false for a first deployment.
If the application with that name is running, and force is set to false, the
command fails.
|
| |
- --user
- administrative
user associated for the instance.
- --password
- administrative
password corresponding to the administrative user.
- --host
- host name
of the machine hosting the administrative instance.
- --port
- administrative
port number associated with the administrative host.
- --passwordfile
- file containing passwords appropriate for the command (e.g., administrative
instance).
- --secure
- if true,
uses SSL/TLS to communicate with the administrative instance.
- --virtualservers
- comma separated list of virtual server IDs.
- --type
- type of component
to be deployed.
- --contextroot
- valid
only if the archive is a web module. It is ignored for other archive types;
defaults to filename without extension.
- --force
- makes sure
the component is forcefully (re)deployed even if the specified component has
already been deployed or already exists.
- --precompilejsp
- by default is set to false which does not allow the JSP to pre-compile during
deployment. Instead JSPs are compiled during runtime.
- --verify
- the syntax
and semantics of the deployment descriptor is verified if set to true.
- --name
- name of the
deployable component.
- --availabilityenabled
- Valid only for deployment of application, EJB module, and Web module.
Valid values are null, true, and false. If this option is not specified, it
will be considered null and not false. When set to true, availability is enabled
for that application or module. For applications, both HTTPSessions and stateful
session beans (SFSB) are enabled for availability. The parent web and EJB
container values take precedence. The EJB module or Web module is enabled
for availability. The parent EJB or Web container value take precedence.
This option is available only in the Enterprise Edition of Sun Java
System Application Server.
- --instance
- name
of the instance.
|
| |
-
dirpath
- path to the directory containing the exploded format of the deployable archive.
|
| | Example 1. Using deploydir
| |
| |
asadmin> deploydir --user admin --passwordfile passwords.txt --host localhost
--port 4848 --force=true --verify=false --name fortune --type application
--instance server1 /export/samples/fortune
Deployed the application:fortune
|
Where: the fortune application is deployed to the
directory specified.
|
|
| |
- 0
- command executed successfully
- 1
- error in executing the command
|
Company Info
|
Contact
|
Copyright 2003 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
|
