<?xml version="1.0" encoding="UTF-8"?> | |
<!--Arbortext, Inc., 1988-2009, v.4002--> | |
<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN" | |
"task.dtd"> | |
<task id="twpub_wst" xml:lang="en-us"> | |
<title id="twpub_title">Publishing your application</title> | |
<shortdesc id="twpub_shortdesc"><i>Publishing</i> involves copying | |
files (projects, resource files, and server configurations) to the | |
correct location for the server to find and use them. In the test | |
environments, these files may already be in the correct location. | |
In some cases, temporary copies of the server configurations may be | |
created. You can either publish your application automatically or | |
manually.</shortdesc> | |
<prolog><metadata> | |
<keywords id="index"><indexterm>applications<indexterm>publishing | |
to servers</indexterm></indexterm><indexterm>servers<indexterm>publishing | |
applications</indexterm></indexterm></keywords> | |
</metadata></prolog> | |
<taskbody> | |
<context><b id="twpub_autotitle">Automatically publishing to a server</b><p | |
id="twpub_auto1">If the <uicontrol>Automatically publish when starting | |
servers</uicontrol> check box on the Server preferences page (<menucascade> | |
<uicontrol>Window</uicontrol><uicontrol>Preferences</uicontrol> | |
<uicontrol>Server</uicontrol><uicontrol>Launching</uicontrol> | |
</menucascade>) is selected, the workbench checks to see if your project | |
and files on the server are synchronized. If they are not, the project | |
and the files are automatically updated when the server is either | |
started or restarted.</p><p id="twpub_p2">To publish your application | |
manually you can complete one of the following in the Servers view:</p><p | |
id="twpub_auto2">In the workbench, you have several options to choose | |
for the <i>Publishing</i> settings. You can set these <i>Publishing</i> settings | |
by going into the Servers view, right-click the server and select <uicontrol>Open</uicontrol>. | |
The Server editor opens. In the <i>Overview</i> page of the server | |
editor, under the <uicontrol>Publishing</uicontrol> settings, you | |
are going to find the following settings:<ul> | |
<li><uicontrol>Never publish automatically</uicontrol>: Specifies | |
the workbench should never publish files to the server.</li> | |
<li><uicontrol>Automatically publish when resources change</uicontrol>: | |
Specifies the workbench to issue a publish after changes on a file | |
that is associated to the server are saved and a full time interval | |
has passed in the <uicontrol>Publishing interval</uicontrol> setting.</li> | |
<li><uicontrol>Automatically publish after a build event</uicontrol>: | |
Specifies the workbench to issue a publish after changes on a file | |
that requires a build and is associated to the server are saved, and | |
a full time interval has passed in the <uicontrol>Publishing interval</uicontrol> setting.</li> | |
<li><uicontrol>Publishing interval (in seconds)</uicontrol>: Specifies | |
the number of <i>seconds</i> that needs to pass before the workbench | |
calls a publish to happen on the server. However, if you make a subsequent | |
change to the files before this time interval has completed, the publish | |
is delayed as the timer is reset. The workbench makes a publish to | |
the server only after the full time interval has passed. If you set | |
the publishing interval to 0 seconds, an immediate publish should | |
happen after changes on a file are saved.</li> | |
</ul></p><p id="twpub_auto3">In the workbench, the default setting | |
is the <b>Automatically publish when resources change</b> option is | |
enabled with a value set in the publishing interval.</p><p>In addition, | |
under the <uicontrol>Select publishing actions</uicontrol> list, select | |
the tasks you want to run during publishing.</p><?Pub Caret -3?><b | |
id="twpub_manualtitle">Manually publishing to a server</b><p | |
id="twpub_manual1">If you do not want to wait for the automatic publishing | |
interval to pass, at anytime you can manually request the workbench | |
to issue a publish command to the server. Each manual publish command | |
causes a single publishing request to the server. To publish your | |
application manually you can complete one of the following in the | |
Servers view:</p><p><ul> | |
<li><ph id="twpub_steps_ph1">Select the server and then click the | |
<uicontrol>Publish to the server</uicontrol></ph> <image | |
alt="This is an image of the Publish toolbar icon." | |
href="../images/launch_publish.gif"><alt>This is an image of the Publish | |
toolbar icon.</alt></image> <ph id="twpub_steps_ph2">icon located | |
on the toolbar.</ph></li> | |
<li><ph id="twpub_steps_step2">Right-click the server and then select | |
<uicontrol>Publish</uicontrol>.</ph></li> | |
</ul></p></context> | |
<result><p id="twpub_p3">All the projects defined in the server configuration | |
that are associated with the selected server are published. The resources | |
in these projects are transferred to the location that is defined | |
by the server.</p></result> | |
</taskbody> | |
</task> | |
<?Pub *0000004819?> |