Servertec Deployment
Content
Introduction
Release Notes
Features
FAQs
Requirements
Installation
How To
Change Log
Future Plans
Knowledge Base
Documentation
Conventions
Command Line
Administrator
Localization
Programming
Security
Performance
Deployment
Server API
Servlet / JSP API
Xerces API
CGI
SSI
Servlets
Config Files
Log Files
Classes
Directory Tree
Examples
Legal
Contact Us

 

Select deployment method:
Directory
JAR/ZIP file


Use the following instructions to deploy Servertec Internet Server to a directory.
  1. Update deploy_iws as needed.

  2. Run deploy_iws.

    deploy_iws path

    path directory where to deploy Servertec Internet Server.

  3. Place your files:

    binary files in path/bin
    servlet files in path/classes
    CGI executable files in path/cgi-bin
    html files in path/wwwroot
    image files in path/wwwroot/images

    path directory where Servertec Internet Server was deployed.

  4. Update configuration files in path/config as needed, where path is the directory where Servertec Internet Server was deployed.

  5. Update PATH.

    set PATH=path/bin;%PATH%

    path directory where Servertec Internet Server was deployed.

  6. Run Servertec Internet Server using:

    iws path

    path directory where Servertec Internet Server was deployed.

top of page


Use the following instructions to deploy Servertec Internet Server to a JAR/ZIP file.
  1. Use the instructions above to deploy Servertec Internet Server to a Directory.

  2. Using the notes below, update configuration files in path/config, where path is the directory where Servertec Internet Server was deployed.

    • Remove /docs and /admin.html definitions from path/config/aliases.ini and remove AdminServlet from path/config/servlets.ini.
    • if administrator and clustering was removed then remove /status definition from path/config/aliases.ini and StatusServlet from path/config/servlets.ini.
    • if FileLogger and DatabaseLogger is not being used then change service definition in path/config/logger.ini to stec.iws.ConsoleLogger.
    • if logger is not being used then set log_access = n, log_errors = n, log_events = n in path/config/logger.ini.
    • if connection pools are not being used then set connection_pools = n in path/config/iws.ini.
    • if security is not being used then set security = n in path/config/iws.ini and clear path/config/acl.ini, path/config/groups.ini, /config/users.ini, path/config/realms.ini and path/config/resources.ini.
    • if <servlet> tag was removed then remove .ssi from path/config/aliases.ini and ServletTagServlet from path/config/servlets.ini.
    • if ssi was removed then remove .shtml from path/config/aliases.ini and SSIncludeServlet from path/config/servlets.ini.
    • if ssi and cgi was removed then remove /cgi-bin from path/config/aliases.ini and CgiServlet from path/config/servlets.ini.
    • if InvokerServlet was removed then remove /servlet from path/config/aliases.ini and InvokerServlet from path/config/servlets.ini.
    • if FileServlet was removed then remove / from path/config/aliases.ini and FileServlet from path/config/servlets.ini.

    service = stec.iws.FileLogger?basedir= logs_dir &access_log_template=default&log_rollover_interval=weekly

    logs_dir is an absolute path to a directory where the logger will write to.
    path directory where Servertec Internet Server was deployed.

  3. Create the JAR file.

    cd path
    jar -cvf jar_path/name *

    jar_path is the path to where to place the JAR file.
    name is the name of the JAR file to create.
    path is where Servertec Internet Server was deployed.

  4. Run Servertec Internet Server.

    iws jar_path/name

    jar_path is the path to the JAR file.
    name is the name of the JAR file.

Notes

The Administrator can not be used to modify configuration files when running the server from a JAR/ZIP archive.
 top of page
Copyright © 1998-2005 Servertec. All rights reserved.
Privacy Statement.
Last Modified: Sun Sep 04 14:57:18 EDT 2005