Servertec   How To
Content
Introduction
Release Notes
Features
FAQs
Requirements
Installation
Add-ons
How To
Change Log
Future Plans
Knowledge Base
Documentation
Samples
Sales
Legal
Feedback

 

Select what you would like to do:
Run iServer
Test iServer
Administer iServer
Stop iServer
Test iServer Gateway
Setup iServer as a Windows NT Service
Automatically run iServer when Windows 9x starts
Setup iServer as a Linux/Unix init daemon
Setup iServer as a Secure Server
To start iServer:

Open a command shell and enter:

    iws { path | archive }
archive the JAR/ZIP archive containing the Web-site to use.
path is the directory where iServer was installed or deployed, normally c:\iws for WIN32 and /iws for Linux/Unix.
top of page
To test iServer:

Run iServer and from a Web Browser enter:

    protocol://host:port
host the name of the computer running iServer, normally localhost
port the port number iServer is listening on, normally 8080
protocol the Web protocol, normally http

Then click on Samples, click on the sample to run and click on run.

top of page


To administer iServer:

Assuming iServer is already running from a Web Browser enter:

    protocol://host:port/admin.html
host the name of the computer running iServer, normally localhost
port the port number iServer is listening on, normally 8080
protocol the Web protocol, normally http

Then login by entering admin for Username and admin for Password. Once login click on the name of the Server to administer and then in the Control Panel click on Manage.

top of page


To stop iServer:

Assuming iServer is already running from a command shell enter:

    stop_iws {protocol://}host:port username password
host the name of the computer running iServer, normally localhost
password the password used by the administrator, normally admin
port the port number iServer is listening on, normally 8080
protocol the Web protocol, normally http
username the user id of the administrator, normally admin

or from a Web Browser enter:

    protocol://host:port/admin.html
host the name of the computer running iServer, normally localhost
port the port number iServer is listening on, normally 8080
protocol the Web protocol, normally http

Then login by entering admin for Username and admin for Password. Once login click on the name of the Server to shutdown, normally localhost:8080 and then in the Control Panel click on the STOP button.

top of page


To test an iServer Gateway:

Install and configure iServer and the appropriate iServer Gateway, start iServer and then the Web/Application Server and finally from a Web Browser enter:

    protocol://host:port/servlet/HelloServlet
host the name of the computer running the Application/Web Server, normally localhost
port the port number the Application/Web Server is listening on, normally 80
protocol the Web protocol, normally http

To setup iServer as a Windows NT Service:
  1. Install and configure iServer.

  2. Open an MS-DOS Prompt and enter:

    instsrv iServer iws_dir\bin\win32\service.exe

    iws_dir the directory where iServer was installed, normally c:\iws

  3. Using the Control Panel double-click on System then click on Environment tab and add the following System Variables.

    Variable Value
    IWS_PATH the directory where iServer was installed or deployed, normally c:\iws
    IWS_HOSTNAME the name of the computer running iServer, normally localhost
    IWS_PORT the port number iServer is listening on, normally 8080
    IWS_PASSWORD the password used by the administrator, normally admin
    IWS_USERNAME the user id of the administrator, normally admin

  4. Restart the computer.

Notes:
iServer can not be used as a Windows NT Service when SSL Support is enabled.


To automatically run iServer when Windows 9x starts:
  1. Install and configure iServer.

  2. Open an MS-DOS Prompt and enter:

    cd iws_dir\install\win32.

    iws_dir is the directory where iServer was installed, normally c:\iws

  3. Change iServer.reg as needed.

  4. From the MS-DOS Prompt enter:

    regedit iServer.reg.

  5. Restart the computer.

Notes:
When iServer is started this way it will only start when a user is logged on and will need to be manually stopped using stop_iws or from the Administrator before the user logs off or the system is shut down or restarted. Ctrl+C or Ctrl+Break should not be used to stop iServer.


To setup iServer as a Linux/Unix init daemon:
  1. Login as root.

  2. Open a shell prompt and enter:

    cp iws_dir/install/linux/iws /etc/rc.d/init.d

    iws_dir is the directory where iServer was installed, normally /iws

  3. Change iws as needed.

  4. For every init level that iServer will be stopped enter:

    ln -s /etc/rc.d/init.d/iws /etc/rc.d/rclevel.d/K19iws

    level is 0-9, normally 0-2, 6

  5. For every init level that iServer will be started enter:

    ln -s /etc/rc.d/init.d/iws /etc/rc.d/rclevel.d/S89iws

    level is 0-9, normally 3-5

  6. Restart the computer.

To setup iServer as a Secure Server:
  1. Add the following entries to the CLASSPATH:

    Windows 9x/NT
    set CLASSPATH=iws_dir\classes\jsse.jar;%CLASSPATH%
    set CLASSPATH=iws_dir\classes\jcert.jar;%CLASSPATH%
    set CLASSPATH=iws_dir\classes\jnet.jar;%CLASSPATH%

    Linux/Unix
    export CLASSPATH="iws_dir/classes/jsse.jar:$CLASSPATH"
    export CLASSPATH="iws_dir/classes/jcert.jar:$CLASSPATH"
    export CLASSPATH="iws_dir/classes/jnet.jar:$CLASSPATH"

    iws_dir the directory where iServer was installed, normally c:\iws for Windows 9x/NT and /iws for Linux/Unix

  2. Restart the computer.

  3. From iServer Administrator - Certificates generate a new Self-Signed Certificate by clicking on the GENERATE button, entering the required information and submitting the form.

  4. Optionally, use the following steps to install a Certification Authority (CA) certificate.

    1. Generate a Certificate Signing Request (CSR) for the Self-Signed Certificate by clicking the REQUEST button on iServer Administrator - Certificates.

    2. Submit the CSR to a CA.

      Entrust, Thawte, and VeriSign are popular Certification Authorities.

    3. Import the Response Certificate overwriting the original Certificate by clicking IMPORT button on iServer Administrator - Certificates, using the same Alias as the Self-Signed Certificate and entering the File Name of the file containing the Response Certificate selecting the Check cacerts and Ignore Warnings and clicking on the OK button.

  5. From the iServer Administrator - Server form enable SSL Support.

  6. From the iServer Administrator - Server form change Port as needed, normally Secure Servers use port 443.

  7. Restart iServer and from a Web Browser enter:

    https://host:port

    host the name of the computer running iServer, normally localhost
    port the port number iServer is listening on, normally 8080

Notes:
iServer Certificate Administrator will only import Response Certificates that contain a complete Certificate Chain or Response Certificates whose Certificate Chain can be established using an existing Root CA Certificate.

iServer ships with JSSE 1.0.1 Export Edition. Optionally iServer supports JSSE 1.0.1 Domestic Edition which supports stronger encryption. See Add-ons for directions on how to install and configure JSSE Domestic Edition.

JSSE requires Java 1.2.0 or later.

Keystore and Certificate Administrators require Java 1.3.0 or later.

Web Browsers will accept Self-Signed Certificates after displaying a warning that they are self-signed.

Web Browsers will accept Test Certificates from Certification Authorities after displaying a warning that they can not be trusted.

The following restrictions apply only when iServer is running with SSL Support enabled:

  • Web Browsers must use https Web protocol

  • iws, start_iws, restart_iws, iwsSSLCommand and iServer Administrator - Monitor will not run unless one or more valid non test certificates exist in the keystore and the corresponding root CA certificates exist in Java's cacerts keystore

  • the server can not be started as a Windows NT Service

  • the server can not be specified as a server in any of the iServer Gateways

  • the server can not be specified as a server in ClusterProxy or ClusterRedirector
 top of page
 Built with iScript Copyright © 1997-2000 Servertec. All rights reserved.
Last Modified: Sat Aug 12 11:20:03 EDT 2000