This task is best suited for use in a development environment.
An expanded directory, also known as an exploded directory, contains an unassembled (unpackaged) application or module. To deploy a directory format instead of an archive, use the asadmin deploy subcommand in remote mode and specify a path to a directory instead of to an archive file. The contents of the directory must be the same as the contents of a corresponding archive file. The directories that hold modules must be named with suffixes that identify the type of archive that the structure is based on, such as _jar or _war.
You can change deployment descriptor files directly in the expanded directory.
If your environment is configured to use dynamic reloading, you can also dynamically reload applications or modules that are deployed from the directory. For instructions, see To Reload Changes to Applications or Modules Dynamically.
The directory must be accessible to the machine on which Enterprise Server runs.
On Windows, if you are deploying a directory on a mapped drive, you must be running Enterprise Server as the same user to which the mapped drive is assigned. This enables Enterprise Server to access the directory.
Ensure that the server is running.
Remote commands require a running server.
Verify that the expanded directory contents match the archive file.
Deploy the directory by using the deploy(1) subcommand and specifying the path to the expanded directory.
Deployment directories might change between Enterprise Server releases.
This example deploys the expanded directory for the hello application. The path name is stored in the domain configuration file (domain.xml).
asadmin> deploy --name hello Application deployed successfully with name hello. Command deploy executed successfully.
You can also view the full syntax and options of the subcommand by typing asadmin help deploy at the command line.