Red Hat NETSCAPE ENTERPRISE SERVER 6.0 - NSAPI PROGRAMMER GUIDE Manuel d'utilisateur télécharger pdf (Page 28)

Deploying a Web Application using wdeploy

28 iPlanet Web Server, Enterprise Edition Programmer’s Guide to Servlets • May 2001

• The .WAR file gets extracted at the target directory.

For example:

wdeploy deploy -u /hello -i server.iplanet.com -v acme.com

-d /iws60/https-server.iplanet.com/acme.com/web-apps/hello

/iws60/plugins/servlets/examples/web-apps/HelloWorld/HelloWorld.war

This utility results in the following web-apps.xml entry:

<vs>

<web-app uri="/hello"

dir="/iws60/https-server.iplanet.com/acme.com/webapps/hello"/>

</vs>

The /iws60/https-server.iplanet.com/acme.com/web-apps/hello directory

has the following contents:

colors

index.jsp

META-INF

WEB-INF/

web.xml

/classes/

HelloWorldServlet.class

HelloWorldServlet.java

SnoopServlet.class

SnoopServlet.java

Before you can run a web application that has been deployed, you must make sure

that the

server.xml file for the server instance points to the web-apps.xml file for

your virtual server.

After you have deployed an application, you can access it from a browser as

follows:

http://vs_urlhost[:vs_port]/uri_path/[index_page]

The parts of the URL have the following meanings:

vs_urlhost One of the urlhosts values for the virtual server.

vs_port (optional) Only needed if the virtual server uses a non-default port.

uri_path The same one you used to deploy the application. This is also the context

path.

index_page (optional) The page in the application that end users are meant to access

first.

1 2 ... 23 24 25 26 27 28 29 30 31 32 33 ... 123 124

Pas de commentaire

Red Hat NETSCAPE ENTERPRISE SERVER 6.0 - NSAPI PROGRAMMER GUIDE Manuel d'utilisateur Page 28