Previous Next Contents Index


Deploying and Downloading Applications

This chapter describes deploying the finished product onto one or more Netscape Application Server(s).

The following topics are described in this chapter:


Deploying Applications
Deploying your application means creating a copy of it on one or more servers, usually in order to make it publicly available for use. You deploy an application from the Deployment Manager. The Deployment Manager is a tool that has been integrated into the Netscape Application Builder. For information about the Deployment Manager, see the Deployment Guide for the Netscape Application Server.

Servlets must be registered and enabled after deployment in order to make them available to the server; this can be done at deployment time, or later by a server administrator.

Enterprise JavaBeans should be prepared for deployment by rechecking their access control lists, timeouts, and other values that need different values in a production environment. For information about how to change these values, see "Examining and Changing EJB Properties" on page 381.

About Deploying Applications
Deploy your finished application to one or more Netscape Application Servers and optionally one or more web servers, depending on your server configuration. You must register a machine with Netscape Application Builder in order to deploy to it.

If you employ more than one server on its own machine, you can perform load balancing and process management in order to increase application responsiveness. These issues are normally managed by the server administrator.

You can further increase effective bandwidth if you also deploy to one or more web servers. Web servers can serve static pages, images, and JavaScript files that do not need access to application processes.

About File Locations
All compiled Java files, JavaServer Pages (JSPs), and database access files are deployed to the application server (or servers, if there is more than one in your server configuration). HTML pages are deployed to your web server.

Static files that do not require interaction with the application server, such as images, static HTML pages, and JavaScript files, are deployed directly to a web server if one exists in your server configuration. These files can be served by the application server if no web server exists.

How to Deploy an Application
To deploy an application:

  1. Choose Rebuild Project from the Build menu to verify that your project is up-to-date.
  2. Choose Deploy from the Project menu to invoke the Deployment Manager, which will package your project as a JAR file.
  3. Specify whether you want to include source files when you deploy the project.
  4. Register your server if it has not already been registered.
  5. Select the application to be deployed, the server on which to deploy, then click Deploy to deploy your application on the server.
  6. Choose the Deploy tab in the Messages window and review the deployment messages.

Saving JAR Files
You can use the Package as JAR item on the Project menu to save an application as a JAR file. Specify whether you want to include source files when you deploy the application.

You can then deploy this JAR file using NASDM, but not Netscape Application Builder. You can keep the JAR file for comparison with JAR files subsequently downloaded from NAS. You may explicitly delete this file when it is no longer needed.

Note. An existing JAR file for an application is overwritten when ever you deploy the application.


Downloading a Previously Deployed Application
You can download a project if its JAR file exists and if it was previously deployed from your machine. To download a project:

  1. Choose the Download menu item from the File menu.
  2. Specify the server from which to download and the project's JAR file.
  3. Choose Download to download the JAR file.
Note. Nab also

 

© Copyright 1999 Netscape Communications Corp.