Servertec | iServer Deployment

Content Introduction Release Notes Features FAQs Requirements Installation Add-ons How To Change Log Future Plans Knowledge Base Documentation Conventions Users iServer Administration Deployment Reference Samples Sales Legal Feedback |
1. Select deployment method: Directory JAR/ZIP file Use the following instructions to deploy iServer to a directory. Run deploy_iws. deploy_iws path
   path | directory where to deploy iServer.
2. Place your files: servlet files in path/servlets CGI executable files in path/cgi-bin html files in path/wwwroot image files in path/wwwroot/images protected files in path/wwwroot/protected
   path | directory where iServer was deployed.
4. Update configuration files as needed. Update CLASSPATH. WIN32 set CLASSPATH=path/servlets;%CLASSPATH% LINUX/UNIX export CLASSPATH=path/servlets:$CLASSPATH
   path | directory where iServer was deployed.
5. Run iServer using: iws path
   path | directory where iServer was deployed.
2. top of page Use the following instructions to deploy iServer to a JAR/ZIP file. Use the instructions above to deploy iServer to a Directory. Extract classes in iws.jar and in servlet.jar. cd path jar -xvf iws_dir/classes/iws.jar jar -xvf iws_dir/classes/servlet.jar
   iws_dir | is the directory where iServer is installed.
   path | is where iServer was deployed.
3. Remove Administrator. cd path del stec/iws/AdminServlet.class del stec/iws/AdminConstants.class del stec/iws/AdminContext.class del stec/iws/AdminUtils.class del stec/iws/AdminGroups.class del stec/iws/AdminServlets.class del stec/iws/AdminACLs.class del stec/iws/AdminHosts.class del stec/iws/AdminPools.class del stec/iws/AdminAliases.class del stec/iws/AdminCPanel.class del stec/iws/AdminMonitor.class del stec/iws/AdminTemplates.class del stec/iws/AdminLogger.class del stec/iws/AdminSession.class del stec/iws/AdminWorkGroup.class del stec/iws/AdminUsers.class del stec/iws/AdminServer.class del stec/iws/AdminComputers.class del stec/iws/AdminResources.class del stec/iws/AdminMimeTypes.class del stec/iws/AdminRealms.class del stec/iws/AdminMessages.class del stec/iws/AdminLogin.class del stec/iws/AdminRights.class del stec/iws/StatusServlet.class del stec/iws/RealmAdministrator.class del stec/iws/DatabaseRealmAdministrator.class del stec/iws/FileRealmAdministrator.class
   path | is where iServer was deployed.
4. Using iServer Classes as a guideline, remove any unnecessary optional classes from iServer distribution. cd path del class_path
   class_path | is the path specified in iServer Classes.
   path | is where iServer was deployed.
5. Using the notes below, update configuration files in path/config, where path is the directory where iServer 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 is being used then change service definition for FileLogger in path/config/logger.ini as follows: 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 iServer was deployed.
6. 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 iServer was deployed.
7. Set the CLASSPATH as needed. WIN32 set CLASSPATH=jar_path/name;%CLASSPATH% LINUX/UNIX export CLASSPATH=jar_path/name:$CLASSPATH%
   jar_path | is the path to the JAR file.
   name | is the name of the JAR file.
8. Run iServer. WIN32 %JAVA_EXE% -classpath %CLASSPATH% stec.iws.iws jar_path/name LINUX/UNIX $JAVA_EXE -classpath $CLASSPATH stec.iws.iws jar_path/name
   jar_path | is the path to the JAR file.
   name | is the name of the JAR file.
#### Notes iServer Administrator can not be used to modify configuration files when running iServer from a JAR/ZIP archive.
top of page
| Copyright © 1997-2000 Servertec. All rights reserved. Last Modified: Sun Jan 09 19:34:12 EST 2000