|
|
MicroNova YUZU: 20080616 (JSP 1.2/2.0) Released
06-17-2008
|
|
asadmin-deploydir(1AS) User Commands asadmin-deploydir(1AS) NAME
asadmin-deploydir, deploydir - deploys an exploded format of application archive SYNOPSIS
deploydir --user admin_user[--password admin_password][--host localhost] [--port 4848] [--secure|-s] [--passwordfile filename] [--terse=false] [--echo=false] [--interactive=true] [--virtualservers virtual_servers] [--contextroot context_root] [--force=true] [--ver- ify=false] [--precompilejsp=false][--name component_name] [--uniquetablenames=true | false] [--dbvendorname dbvendorname] [--createta- bles=false | --dropandcreatetables=false] dirpath Deploys the exploded format of the application archives present under the directory provided as the command operand. The deployed format, of EAR or WAR applications, reside on the application server and have a directory structure which can be used for deployment. 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. If the --uniquetablenames, --createtables, and --dropandcreatetables options are not specified, the entries in the deployment descriptors are used. This command is supported in remote mode only. OPTIONS
--user authorized domain application server administrative username. --password password to administer the domain application server. --host machine name where the domain application server is running. --port port number of the domain application server listening for administration requests. --secure if true, uses SSL/TLS to communicate with the domain application server. --passwordfile file containing the domain application server password. --terse indicates that any output data must be very concise, typically avoiding human-friendly sentences and favoring well- formatted data for consumption by a script. --echo setting to true will echo the command line statement on the standard output. --interactive prompts you for the required options that are not already specified. --virtualservers comma separated list of virtual server IDs. --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 if set to true, the syntax and semantics of the deployment descriptor is verified. --name name of the deployable component. --uniquetablenames guarantees unique table names for all the beans and results in a hashcode added to the table names. This is useful if you have an pplication with case-sensitive bean names. --dbvendorname name of the database vendor being used. Default is the corresponding entry in the cmp-resource () element of the sun-ejb-jar.xml file. If not specified, the default is SQL92. Thereby the DDL files to create and drop tables will be generated in SQL92 format. --createtables creates tables during deployment for applications using unmapped CMP beans. Default is the corresponding entry in the cmp-resource element of the sun-ejb-jar.xml file. If not specified, defaults to the entries in the deployment descriptors. --dropandcreatetables drops existing tables and creates tables during deployment for application using unmapped CMP beans. If not speci- fied, the tables will be dropped if the drop-tables-at-undeploy entry in the cmp-resource element of the sun-ejb- jar.xml file is set to true. The new tables are created if the create-tables-at-deploy entry in the cmp-resource element of the sun-ejb-jar.xml is set to true. On redeploy the tables created by the previous deploy are dropped before creating the new tables. OPERANDS
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 --precompilejsp=true /home/temp/sampleApp Command deploydir executed successfully Where: theexploded application to be deployed is in the /home/temp/sampleApp directory. EXIT STATUS
0 command executed successfully 1 error in executing the command asadmin-deploy(1AS), asadmin-undeploy(1AS), asadmin- enable(1AS), asadmin-disable(1AS), asadmin-list-components(1) J2EE 1.4 SDK March 2004 asadmin-deploydir(1AS)