<!DOCTYPE REFENTRY PUBLIC "-//Sun Microsystems//DTD DocBook V3.0-Based SolBook Subset V2.0//EN" [
<!--ArborText, Inc., 1988-1999, v.4002-->
<!ENTITY metainfo SYSTEM "metainfo.sgm">
<!ENTITY options-common SYSTEM "options-common.sgm">
<!ENTITY synopsis-common SYSTEM "synopsis-common.sgm">
<!ENTITY % commonents SYSTEM "smancommon.ent">
%commonents;
<!ENTITY % booktitles SYSTEM "booktitles.ent">
%booktitles;
<!ENTITY Dash "&ndash;">
]>
<?Pub UDT _bookmark _target>
<?Pub Inc>
<refentry id="deploydir-1">
<refmeta><refentrytitle>deploydir</refentrytitle><manvolnum>1</manvolnum>&metainfo;
</refmeta>
<refnamediv><indexterm><primary sortas="deploydir">deploydir &mdash; deploys
an exploded format of application archive</primary></indexterm><indexterm>
<primary sortas="deploys an exploded format of application archive">deploys
an exploded format of application archive &mdash; deploydir</primary></indexterm>
<refname>deploydir</refname><refpurpose>deploys an exploded format of application
archive</refpurpose></refnamediv>
<refsynopsisdiv><title>&synp-tt;</title>
<cmdsynopsis><command>deploydir </command>&synopsis-common;
<arg>&Dash;&Dash;virtualservers <replaceable>virtual_servers</replaceable></arg>
<arg>&Dash;&Dash;contextroot <replaceable>context_root</replaceable></arg>
<arg><option role="nodash">&Dash;&Dash;force=true</option></arg><arg><option
role="nodash">&Dash;&Dash;verify=false</option></arg><arg><option role="nodash">&Dash;&Dash;precompilejsp=false
</option></arg><arg><option role="nodash">&Dash;&Dash;name <replaceable>component_name
</replaceable></option></arg><arg><option role="nodash">&Dash;&Dash;uniquetablenames=<replaceable>
true|false</replaceable></option></arg><arg><option role="nodash">&Dash;&Dash;dbvendorname <replaceable>
dbvendorname</replaceable></option></arg><arg><option role="nodash">&Dash;&Dash;createtables=false
</option> | <option role="nodash">&Dash;&Dash;dropandcreatetables=false</option></arg>
<arg><option role="nodash">&Dash;&Dash;generatermistubs=false</option></arg>
<arg><option role="nodash">&Dash;&Dash;availabilityenabled=false</option></arg>
<arg><option role="nodash">&Dash;&Dash;libraries <replaceable>jar_file</replaceable>[(<replaceable>
path_separator</replaceable>)<replaceable>jar_file</replaceable>*]</option></arg>
<arg><option role="nodash">&Dash;&Dash;target <replaceable>target</replaceable></option></arg>
<arg choice="plain"><replaceable>dirpath</replaceable></arg>
</cmdsynopsis></refsynopsisdiv>
<refsect1><title>&desc-tt;</title>
<para>Use this command to deploy an application directly from a development
directory. The appropriate directory hierarchy and deployment descriptors
conforming to the Java EE specification must exist in the deployment directory.
</para>
<para>Directory deployment is for advanced developers only. Do not use it
in production environments. In production environments, use the deploy command.
Directory deployment is only supported on localhost, that is, the client and
server must reside on the same machine. For this reason, the only values for
the <option role="nodash">&Dash;&Dash;host</option> option are: <itemizedlist>
<listitem><para><literal>localhost</literal></para></listitem>
<listitem><para>The value of the <literal>$HOSTNAME</literal> environment
variable</para></listitem>
<listitem><para>The IP address of the machine</para></listitem>
</itemizedlist></para>
<para>If the <option role="nodash">&Dash;&Dash;uniquetablenames</option>, <option
role="nodash">&Dash;&Dash;createtables</option>, and <option role="nodash">&Dash;&Dash;dropandcreatetables
</option> options are not specified, the entries in the deployment descriptors
are used.</para>
<para>The <option role="nodash">&Dash;&Dash;force</option> option makes sure
the component is forcefully (re)deployed even if the specified component has
already been deployed or already exists. Set <option role="nodash">&Dash;&Dash;force
</option> to false for a first deployment. If the application with that name
is running and force is set to false, the command fails.</para>
<para>This command is supported in remote mode only.</para>
</refsect1>
<refsect1><title>OPTIONS</title>
<variablelist termlength="wide">&options-common;
<varlistentry><term><option role="nodash">&Dash;&Dash;virtualservers</option></term>
<listitem><para>Comma-separated list of virtual server IDs. </para>
</listitem></varlistentry>
<varlistentry><term><option role="nodash">&Dash;&Dash;contextroot</option></term>
<listitem><para>Valid only if the archive is a web module. It is ignored for
other archive types; defaults to filename without extension.</para>
</listitem></varlistentry>
<varlistentry><term><option role="nodash">&Dash;&Dash;force</option></term>
<listitem><para>Makes sure the component is forcefully (re)deployed even if
the specified component has already been deployed or already exists.</para>
</listitem></varlistentry>
<varlistentry><term><option role="nodash">&Dash;&Dash;verify</option></term>
<listitem><para>If set to true, the syntax and semantics of the deployment
descriptor is verified.</para>
</listitem></varlistentry>
<varlistentry><term><option role="nodash">&Dash;&Dash;precompilejsp</option></term>
<listitem><para>By default, this option is set to false, which does not allow
the JSP to pre-compile during deployment. Instead, JSPs are compiled during
runtime.</para>
</listitem></varlistentry>
<varlistentry><term><option role="nodash">&Dash;&Dash;name</option></term>
<listitem><para>Name of the deployable component.</para>
</listitem></varlistentry>
<varlistentry><term><option role="nodash">&Dash;&Dash;uniquetablenames</option></term>
<listitem><para>Guarantees unique table names for all the beans and results
in a hashcode added to the table names. This is <?Pub Caret>useful if you
have an application with case-sensitive bean names.</para>
</listitem></varlistentry>
<varlistentry><term><option role="nodash">&Dash;&Dash;dbvendorname</option></term>
<listitem><para>Specifies the name of the database vendor for which tables
are created. Supported values include <literal>db2</literal>, <literal>mssql
</literal>, <literal>oracle</literal>, <literal>derby</literal>, <literal>
javadb</literal>, <literal>postgresql</literal>, <literal>pointbase</literal>
and <literal>sybase</literal>, case-insensitive. If not specified, the value
of the <literal>database-vendor-name</literal> attribute in <literal>sun-ejb-jar.xml
</literal> is used. If no value is specified, a connection is made to the
resource specifie by the <literal>jndi-name</literal> subelement of the <literal>
cmp-resource</literal> element in the <literal>sun-ejb-jar.xml</literal> file,
and the database vendor name is read. If the connection cannot be established,
or if the value is not recognized, SQL-92 compliance is presumed.</para>
</listitem></varlistentry>
<varlistentry><term><option role="nodash">&Dash;&Dash;createtables</option></term>
<listitem><para>Creates tables at deployment of an application with unmapped
CMP beans. Default is the <literal>create-tables-at-deploy</literal> entry
in the <command>cmp-resource</command> element of the <filename>sun-ejb-jar.xml
</filename> file. </para>
</listitem></varlistentry>
<varlistentry><term><option role="nodash">&Dash;&Dash;dropandcreatetables
</option></term><listitem><para>Drops existing tables and creates tables during
deployment for application using unmapped CMP beans. If not specified, the
tables are dropped if the <filename>drop-tables-at-undeploy</filename> entry
in the <filename>cmp-resource</filename> element of the <filename>sun-ejb-jar.xml
</filename> file is set to true. The new tables are created if the <filename>
create-tables-at-deploy</filename> entry in the <filename>cmp-resource</filename>
element of the <filename>sun-ejb-jar.xml</filename> is set to true. When the
component is redeployed, the tables created by the previous deployment are
dropped before creating the new tables.</para>
</listitem></varlistentry>
<varlistentry><term><option role="nodash">&Dash;&Dash;generatermistubs</option></term>
<listitem><para>if set to true, static RMI-IIOP stubs are generated and put
into the <filename>client.jar</filename>. If set to false (default) the stubs
are not generated.</para>
</listitem></varlistentry>
<varlistentry><term><option role="nodash">&Dash;&Dash;availabilityenabled
</option></term><listitem><para>&se-ee-only; This option controls whether
high-availability is enabled for SFSB checkpointing and potentially passivation.
If set to false (default) all SFSB checkpointing is disabled for the specified
application or EJB module. If set to true, the specified application or module
is enabled for high-availability. Set this option to true only if high availability
is configured and enabled at higher levels, such as the server and container
levels.</para>
</listitem></varlistentry>
<varlistentry><term><option role="nodash">&Dash;&Dash;libraries</option></term>
<listitem><para>Specify the library JAR files by their relative or absolute
paths. Specify relative paths relative to <replaceable>instance-root</replaceable><literal>
/lib/applibs</literal>. The JAR files are separated by a colon on Unix and
Linux systems and by a semicolon on Windows systems. The libraries are made
available to the application in the order specified. Place the dependent JAR
files in the <replaceable>domain-dir</replaceable><literal>/lib</literal>
directory.</para>
</listitem></varlistentry>
<varlistentry><term><option role="nodash">&Dash;&Dash;target</option></term>
<listitem><para>&se-ee-only;Specifies the target to which you are deploying.
Valid values are:<itemizedlist>
<listitem><para><literal>server</literal>, which deploys the component to
the default server instance <literal>server</literal> and is the default value.
</para>
</listitem>
<listitem><para><literal>domain</literal>, which deploys the component to
the domain.</para>
</listitem>
</itemizedlist></para>
</listitem></varlistentry>
</variablelist></refsect1>
<refsect1><title>OPERANDS</title>
<variablelist termlength="wide">
<varlistentry><term><replaceable>dirpath</replaceable></term><listitem><para>
path to the directory containing the exploded format of the deployable archive.
</para>
</listitem></varlistentry>
</variablelist></refsect1>
<refsect1><title>&exam-tt;</title>
<example>
<title>Using the deploydir command</title>
<para>The exploded application to be deployed is in the <filename>/home/temp/sampleApp
</filename> directory. Since the <literal>force</literal> option is set to
true, if an application of that name already exists, the application is redeployed.
</para>
<screen>asadmin> <userinput>deploydir --user admin --passwordfile passwords.txt 
--host localhost --port 4848 --force=true --precompilejsp=true /home/temp/sampleApp
</userinput>
Command deploydir executed successfully</screen>
</example>
</refsect1>
<refsect1><title>EXIT STATUS</title>
<variablelist termlength="medium">
<varlistentry><term>0</term><listitem><para>command executed successfully
</para>
</listitem></varlistentry>
<varlistentry><term>1</term><listitem><para>error in executing the command
</para>
</listitem></varlistentry>
</variablelist></refsect1>
<refsect1><title>&also-tt;</title>
<para><link linkend="deploy-1"><citerefentry><refentrytitle>deploy</refentrytitle>
<manvolnum>1</manvolnum></citerefentry></link>, <link linkend="undeploy-1"><citerefentry>
<refentrytitle>undeploy</refentrytitle><manvolnum>1</manvolnum></citerefentry></link>, <link
linkend="enable-1"><citerefentry><refentrytitle>enable</refentrytitle><manvolnum>
1</manvolnum></citerefentry></link>, <link linkend="disable-1"><citerefentry>
<refentrytitle>disable</refentrytitle><manvolnum>1</manvolnum></citerefentry></link>, <link
linkend="list-components.1"><citerefentry><refentrytitle>list-components</refentrytitle>
<manvolnum>1</manvolnum></citerefentry></link></para>
</refsect1>
</refentry>
<?Pub *0000011931>
