Use the deploytool utility to deploy and package your J2EE applications and components, create and edit J2EE deployment descriptors, and create and edit Sun Java System Application Server specific deployment descriptors. If the application is not J2EE compliant, an error message is displayed.
Only one session of the deploytool utility can run with a specific user directory. A lock file is created to ensure that only one utility session is running. A message is displayed if a lock file is detected.
displays the arguments for launching the deploytool.
identifies the user directory. The default user directory is .deploytool under your home directory. Only one deploytool session can be running per user directory. A lock file is created under the user directory to ensure that only one session of the deploytool is running. The deploytool utility uses this directory to store configuration information.
On Solaris, the default directory is at ~/.deploytool
identifies the configuration directory. The configuration directory is where the asenv.conf file is located.
Bundled installation: /etc/appserver
Unbundled installation: default is /etc/opt/SUNWappserver or user specified
Evaluation installation: cd /etc. Where AS_SERVER_INSTALL is the directory where you have installed the Sun Java System Application Server 8.
displays the deploytool log messages on the terminal window in Solaris and command window on windows.
example% deploytool --userdir /myapplication --config_dir /myconfigdir
Where --userdir specifies the destination directory, and -config_dir identifies the configuration directory.