Select what you would like to do:
Start Servertec Internet Server
Test Servertec Internet Server
Administer Servertec Internet Server
Stop Servertec Internet Server
Test Servertec Internet Server Gateway
Configure Servertec Internet Server for IPv6
Setup Servertec Internet Server as a Windows NT/2000/2003/XP Service when using Java 1.1.x
Setup Servertec Internet Server as a Windows NT/2000/2003/XP Service when using Java 2
Automatically run Servertec Internet Server when Windows 9x/Me starts
Setup Servertec Internet Server as a Linux/Unix init daemon
Setup Servertec Internet Server as a Solaris init daemon
Setup Servertec Internet Server as a Secure Server using Java Secure Socket Extension (JSSE)
Setup Servertec Internet Server as a Secure Server using Novell Netware Java Secure Socket Layer (JavaSSL)
To start Servertec Internet Server:
Open a command shell and enter:
archive
|
the JAR/ZIP archive containing the Web-site to use.
|
path
|
is the directory where Servertec Internet Server was installed or deployed,
normally c:\iws for Windows 9x/Me/NT/2000/2003/XP, /iws for
Linux/Solaris/Unix and SYS:\iws for Novell Netware.
|
top of page
To test Servertec Internet Server:
Run Servertec Internet Server and from a Web Browser enter:
hostname
|
the name of the computer running Servertec Internet Server,
normally localhost
|
port
|
the port number Servertec Internet Server 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 Servertec Internet Server:
Assuming Servertec Internet Server is already running from a Web Browser
enter:
protocol://hostname:port/admin.html
hostname
|
the name of the computer running Servertec Internet Server, normally
localhost
|
port
|
the port number Servertec Internet Server 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 Servertec Internet Server:
Assuming Servertec Internet Server is already running from a command shell
enter:
stop_iws {protocol://}hostname:port username password
hostname
|
the name of the computer running Servertec Internet Server,
normally localhost
|
password
|
the password used by the administrator, normally admin
|
port
|
the port number Servertec Internet Server 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://hostname:port/admin.html
hostname
|
the name of the computer running Servertec Internet Server,
normally localhost
|
port
|
the port number Servertec Internet Server 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 shut down, normally localhost:8080
and then in the Control Panel click on the STOP button.
top of page
To test an Servertec Internet Server Gateway:
Install and configure Servertec Internet Server and the appropriate Gateway,
start Servertec Internet Server and then the Web/Application Server and
finally from a Web Browser enter:
protocol://hostname:port/servlet/HelloServlet
hostname
|
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
|
top of page
To configure Servertec Internet Server for IPv6:
- Configure the underlying platform and network for IPv6.
- Install a Java implementation that supports IPv6.
- Start Servertec Internet Server and from the Administrator set IP Address
in the Socket Form to a valid IPv6 address in the form
H:H:H:H:H:H:H:H,
where H is a hexidecimal number from 0000 to FFFF.
- Restart Servertec Internet Server
top of page
To setup Servertec Internet Server as a Windows NT/2000/2003/XP Service when using
Java 1.1.x:
- Install and configure Servertec Internet Server.
- Using iws_dir\install\win32\iserver.ini as a template,
create iserver.ini in Windows directory, normally c:\WINNT in
Windows NT/2000/2003 and c:\Windows in Windows XP.
[j1service]
Debug=debug
JAVA_EXE=java_exe
CLASSPATH=classpath
IWS_PATH=iws_dir
hostname=hostname
port=port
username=username
password=password
classpath
|
the CLASSPATH to use,
normally set to the environment variable %CLASSPATH%
|
debug
|
whether to dump information useful in debugging j1service,
normally false
|
hostname
|
the name of the computer running Servertec Internet Server,
normally localhost
|
iws_dir
|
the base directory where Servertec Internet Server was
installed or deployed, normally c:\iws
|
java_exe
|
the Java VM to use, normally set to the environment
variable %JAVA_EXE%
|
password
|
the password used by the administrator, normally admin
|
port
|
the port number Servertec Internet Server is listening on,
normally 80
|
username
|
the user id of the administrator, normally admin
|
- Open an MS-DOS Prompt and enter:
j1service -i
- Restart the computer.
Notes:
When running Windows NT environment variables must be defined in
Start->Settings->Control Panel->System->Environment->System Variables.
When running Windows 2000 environment variables must be defined in
Start->Settings->Control Panel->System->Advanced->Environment Variables->
System Variables.
When running Windows XP environment variables must be defined in
Control Panel->System->Advanced->Environment Variables->System Variables.
When Debug is set to true, j1service.log is created in
c:\temp directory.
To remove Servertec Internet Server NT/2000/2003/XP Service, open an MS-DOS Prompt
and enter:
top of page
To setup Servertec Internet Server as a Windows NT/2000/2003/XP Service when
using Java 2:
- Install and configure Servertec Internet Server.
- Using iws_dir\install\win32\iserver.ini as a template,
create iserver.ini in Windows directory, normally c:\WINNT in
Windows NT/2000/2003 and c:\Windows in Windows XP.
[j2service]
Debug=debug
Option=-DSERVICE
Option=-Djava.class.path=classpath
Parameter=iws_dir
JavaVM=java_vm
classpath
|
the CLASSPATH to use,
normally set to the environment variable %CLASSPATH%
|
debug
|
whether to dump information useful in debugging j2service,
normally false
|
iws_dir
|
the base directory where Servertec Internet Server was
installed or deployed, normally c:\iws
|
java_dir
|
the base directory where Java was installed
|
java_vm
|
the java vm, normally java_dir\jre\bin\classic\jvm.dll
for Java 1.2.x and java_dir\jre\bin\hotspot\jvm.dll
for Java 1.3.x and java_dir\jre\bin\client\jvm.dll or
java_dir\jre\bin\server\jvm.dll for for Java 1.4.x or
later or when HotSpot is installed
|
- Open an MS-DOS Prompt and enter:
j2service -i
- Restart the computer.
Notes:
When running Windows NT environment variables must be defined in
Start->Settings->Control Panel->System->Environment->System Variables.
When running Windows 2000 environment variables must be defined in
Start->Settings->Control Panel->System->Advanced->Environment Variables->
System Variables.
When running Windows XP environment variables must be defined in
Control Panel->System->Advanced->Environment Variables->System Variables.
When Debug is set to true, j2service.log is created in
c:\temp directory.
To remove Servertec Internet Server NT/2000/2003/XP Service, open an MS-DOS Prompt
and enter:
top of page
To automatically run Servertec Internet Server when Windows 9x/Me starts:
- Install and configure Servertec Internet Server.
- Open an MS-DOS Prompt and enter:
cd iws_dir\install\win32.
iws_dir
|
is the directory where Servertec Internet Server was installed,
normally c:\iws
|
- Change iServer.reg as needed.
- From the MS-DOS Prompt enter:
regedit iServer.reg.
- Restart the computer.
Notes:
When Servertec Internet Server 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 Servertec
Internet Server.
top of page
To setup Servertec Internet Server as a Linux/Unix init daemon:
- Login as root.
- Open a shell prompt and enter:
cp iws_dir/install/linux/iws /etc/rc.d/init.d
chmod u+x,g+x /etc/rc.d/init.d
iws_dir
|
is the directory where Servertec Internet Server was installed,
normally /iws
|
- Change iws as needed.
- For every init level that Servertec Internet Server 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
|
- For every init level that Servertec Internet Server 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
|
- Restart the computer.
top of page
To setup Servertec Internet Server as a Solaris init daemon:
- Login as root.
- Open a shell prompt and enter:
cp iws_dir/install/linux/iws /etc/init.d
chmod u+x,g+x /etc/init.d
iws_dir
|
is the directory where Servertec Internet Server was installed,
normally /iws
|
- Change iws as needed.
- For every init level that Servertec Internet Server will be stopped
enter:
ln -s /etc/init.d/iws /etc/rclevel.d/K19iws
level
|
is 0-9, normally 0-1, 5-6, S
|
- For every init level that Servertec Internet Server will be started
enter:
ln -s /etc/init.d/iws /etc/rclevel.d/S89iws
level
|
is 0-9, normally 2-4
|
- Restart the computer.
top of page
To setup Servertec Internet Server as a Secure Server using Java Secure
Socket Extension (JSSE):
- If running Java 1.3.x or earlier then install Java Secure Socket Extension (JSSE) version 1.0.1 or later.
- If running Java 1.3.x or earlier then add the following entries to the CLASSPATH:
Windows 9x/Me/NT/2000/2003/XP
set CLASSPATH=jsse_dir\lib\jsse.jar;%CLASSPATH%
set CLASSPATH=jsse_dir\lib\jcert.jar;%CLASSPATH%
set CLASSPATH=jsse_dir\lib\jnet.jar;%CLASSPATH%
Linux/Solaris/Unix
export CLASSPATH="jsse_dir/lib/jsse.jar:$CLASSPATH"
export CLASSPATH="jsse_dir/lib/jcert.jar:$CLASSPATH"
export CLASSPATH="jsse_dir/lib/jnet.jar:$CLASSPATH"
Novell Netware
CLASSPATH=jsse_dir\lib\jsse.jar;$CLASSPATH
CLASSPATH=jsse_dir\lib\jcert.jar;$CLASSPATH
CLASSPATH=jsse_dir\lib\jnet.jar;$CLASSPATH
jsse_dir
|
the directory where JSSE was installed.
|
- Restart the computer.
- Start Servertec Internet Server and from the Administrator -
Certificates generate a new Self-Signed Certificate by clicking on the
GENERATE button, entering the required information and submitting the
form.
- Optionally, use the following steps to install a Certification Authority
(CA) certificate.
- Import any necessary root CA certicate into cacerts by opening an
MS-DOS Prompt or Linux/Solaris/Unix shell prompt and entering:
keytool -import -alias alias -keystore keystore -file filename -storepass password
alias
|
the alias name of the root CA certificate.
|
filename
|
the directory path and name of the file containing the root CA certificate.
|
java_dir
|
the directory where Java was installed
|
keystore
|
java_dir/jre/lib/security/cacerts for Windows 9x/Me/NT/2000/2003/XP
and Linux/Solaris/Unix and java_dir/lib/security/cacerts for
Novell Netware
|
password
|
the keystore password,
normally changeit
|
- Generate a Certificate Signing Request (CSR) for the Self-Signed
Certificate by clicking the REQUEST button in the Administrator -
Certificates.
- Submit the CSR to a CA.
Entrust,
Thawte,
and VeriSign
are popular Certification Authorities.
- Import the Response Certificate overwriting the original Certificate
by clicking IMPORT button in the 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.
Use the following steps to install a client certificate for the
server's certificate on each computer that stop_iws,
restart_iws, iwsSSLCommand and iws will be used on.
- Export the certificate by clicking the EXPORT button in the
Administrator - Certificates.
- Open an MS-DOS Prompt or Linux/Solaris/Unix shell prompt and enter:
keytool -import -alias alias -keystore keystore -file cert_dir/alias.cer -storepass password
alias
|
the alias name of the certificate,
normally mykey
|
cert_dir
|
the directory where the certificate was exported to
|
java_dir
|
the directory where Java was installed
|
keystore
|
java_dir/jre/lib/security/cacerts for Windows 9x/Me/NT/2000/2003/XP
and Linux/Solaris/Unix and java_dir/lib/security/cacerts for
Novell Netware
|
password
|
the keystore password,
normally changeit
|
From the Administrator - Server set the SecureSocketHandler to
stec.iws.JsseSecureSocketHandler.
From the Administrator - Server form enable SSL Support.
From the Administrator - Server form change Port as
needed, normally Secure Servers use port 443.
Restart Servertec Internet Server and from a Web Browser enter:
https://hostname:port
hostname
|
the name of the computer running Servertec Internet Server,
normally localhost
|
port
|
the port number Servertec Internet Server is listening on,
normally 443
|
Notes:
The Certificate Administrator only accepts tele-type printable characters
[ A-Z, a-z, 0-9, `~!@#$%^&*()-_=+\|[{]};:'", <.>/? [.
Some of the accepted characters, such as comma and slash, must be prefixed by
\. Finally, not all Certificate Authorities allow the complete list of
tele-type printable characters in request certificates.
The 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.
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 Servertec Internet Server is
running with SSL Support enabled:
- Requested URLs must use https Web protocol.
- iws will not run when SSL is enabled unless one or more valid
certificates exist in the server's keystore.
- When SSL is enabled and Java's cacerts keystore does not contain a valid
root CA certificate for the server's certificate, restart_iws,
stop_iws, iwsSSLCommand and Administrator - Monitor will
display untrusted server cert chain.
- The server can not be specified as a server in any of the Servertec
Internet Server Gateways.
- The server can not be specified as a server in ClusterProxy or
ClusterRedirector.
top of page
To setup Servertec Internet Server as a Secure Server using Novell Netware
Java Secure Socket Layer (JavaSSL):
- If Novell Netware Certificate Server has not already been installed,
install it and create a certificate for the server.
- Install Novell Netware Java Secure Socket Layer (JavaSSL) October 1999 release or later.
- Add the following entries to SYS:\etc\java.cfg:
CLASSPATH=SYS:\javassl\jdk_1.1_version\lib\ssl_sdk1.1.jar;
SYS:\javassl\jdk_1.1_version\lib\nssl1.1_exp.jar;$CLASSPATH
- Change iws_dir\config\server_properties.ini and
iws_dir\config\client_properties.ini as following:
nssl.keystore = SSL CertificateIP - hostname
hostname
|
the name of the computer running Novell Certificate Server
|
- Change iws_dir\config\iws.ini as following:
port=port
ssl=y
secure_socket_handler=stec.iws.NetwareSecureSocketHandler ?server_properties=./config/server_properties.ini &client_properties=./config/client_properties.ini
port
|
the port number Servertec Internet Server is listening on,
normally Secure Servers use port 443.
|
- Change iws_dir\config\logger.ini as following:
ignore_exceptions = java.net.SocketException, com.novell.service.security.net.nssl.SSLComponentException
- Restart the Netware computer.
- Use the following steps to install a root CA certificate for the
server's certificate on each computer that stop_iws,
restart_iws and iwsSSLCommand will be used on.
- Copy the certificate at SYS:\PUBLIC\RootCert.der to a local
drive.
- Open an MS-DOS Prompt or Linux/Solaris/Unix shell prompt and enter:
keytool -import -alias alias -keystore java_dir/jre/lib/security/cacerts -file cert_dir/RootCert.der -storepass password
alias
|
the alias name of the self-signed certificate,
normally mykey
|
cert_dir
|
the directory where the self-signed certificate was copied to
|
java_dir
|
the directory where Java was installed
|
password
|
the keystore password,
normally changeit
|
- Optionally, install a Certification Authority (CA) certificate.
- Start Servertec Internet Server and from a Web Browser enter:
https://hostname:port
hostname
|
the name of the computer running Servertec Internet Server,
normally localhost
|
port
|
the port number Servertec Internet Server is listening on,
normally 443
|
Notes:
Requires that iws_dir/classes/optional.jar be
present in the CLASSPATH.
The Keystore and Certificate Administrator can not be used, since Novell
Netware Certificate Server is used to manage certificates.
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 Servertec Internet Server is
running with SSL Support enabled:
- Requested URLs must use https Web protocol
- iws will not run when SSL is enabled unless one or more valid
certificates exist.
- When SSL is enabled and Java's cacerts keystore does not contain a valid
root CA certificate for the server's certificate, restart_iws,
stop_iws, iwsSSLCommand and Administrator - Monitor will
display untrusted server cert chain.
- The server can not be specified as a server in any of the Servertec
Internet Server Gateways.
- The server can not be specified as a server in ClusterProxy or
ClusterRedirector.
- iws_dir\config\client_properties.ini and
iws_dir\config\server_properties.ini can also be used to
specify additional optional Netware Java SSL engine parameters as defined in
the documentation for JavaSSL in
SYS:\JavaSSL\JDK_1.1_Version\doc\api\index.html.
|