Overview
This document contains information about how to integrate Zeus Web Server with SunOne ASP Server(formerly known as Chilisoft ASP Server). Two integration methods are available:
- Using the Zeus Web Server Gateway Module
- Using NSAPI
Support Considerations
We recommend use of the Gateway Module over NSAPI although both appear to be possible for uncomplicated deployments. General information about the strengths and weaknesses of each of these can be found on the Third Party Product Integration Methods Page
SunONE ASP Server's documentation states that Zeus Web Server is not supported but we have found that the instructions below do appear to allow the Sun product to be used with Zeus. We therefore provide these instructions on an as-is basis and may need to refer customers to our Consultancy Services if further investigation on this non-Zeus product in needed.
At the time of writing, Sun only provide support for the following platforms:
- Solaris 8 on SPARC
- Solaris 9 on SPARC
- Redhat Linux 7.3 on IA32
- Microsoft Windows 2000 & XP on IA32
If you use SunONE ASP on any platforms not listed above, we would not recommend using NSAPI at all. The Gateway method allows full responsibility for the request to be passed onto SunOne ASP without making use of NSAPI shared libraries on unsupported platforms.
Installation Instructions common to Gateway and NSAPI
- Download the SunONE ASP binaries from Sun Microsystems.
-
Extract the compressed file to a temporary directory:
-
mkdir /tmp/casp-install
tar -xzf sunone_asp4.0.1-linux-full.tar.gz -C /tmp/casp-install (the archive does not contain a parent directory)
From the installation directory (for example, /tmp/casp-install) run ./install.sh as root.
- Accept the license agreement and choose a location to install to. If this is not the first installation of SunONE ASP on your machine, you make like to see the notes in the Additional Information section.
A number of JAR files will now be extracted to this location and you will be prompted for a license key or asked if you would like to use the product in evaluation mode.
- Now complete the installation by choosing either the:
Gateway specific instructions
or
NSAPI based approach.
Details on the suitability of either method can be found on the Third Party Product Integration Methods page.
SunONE ASP configuration:
- Install the SunONE ASP Apache bundle when prompted. The Gateway Module will forward .asp requests to this web server.
-
When Apache has been installed, you will be given the option to customize your installation options. Because Zeus Web Server will be receiving the requests first and Gatewaying a selected portion onto Apache, set the listen-port to a value different that you have with Zeus Web Server, e.g. set the Apache listen-port to 8080.
-
After specifying the document root, the installation program will ask for a limit to be specified for the number of simultaneous connections. Such a bottleneck does not exist in Zeus Web Server so to find the most appropriate value for this figure it will be necessary to perform load testing of the system for your projected traffic levels.
-
The SunONE ASP installation program will ask for the user that Apache should run as along with choosing to start this web server on system boot.
-
Choose your preferred language
- When given a choice of web servers to install SunONE ASP with, use the Apache server that has just been configured.
Zeus Web Server configuration:
- Either specify a list of directories whose content should be mapped to SunONE's ASP Apache Web Server:
Requests to send Web Server Port
/asp_dir localhost 8080
or:
specify a file type extension that associates a particular content type with SunONE's ASP Apache Web Server:
Requests to send Web Server Port
~/.*\.asp localhost 8080
It may be necessary to change the port number to reflect the customized configuration options selected earlier for Apache Web Server
Ideally no static content should be forwarded to SunONE's web server to take advantage of Zeus Web Server's superior connection handling abilities.
- Enable 'Rewrite HTTP redirects' and 'Rewrite domain within a cookie' via the Radio buttons.
-
Commit the changes to the virtual server.
- From the Admin Server, in the NSAPI page of your virtual server enable NSAPI support and download the default template NSAPI configuration files:
obj.conf
magnus.conf
mime.types
- Copy the files to $ZEUSHOME/ns-config/https-<vserver>/config/ creating the directories if they do not already exist.
Edit the mime.types file so that it reads as follows:
# Supplementary mime.types for NSAPI
#
# $ZEUSHOME/ns-config/https-<vserver>/config/mime.types
type=chilisoft-internal/active-server-page exts=asp,asa
-
Return to the SunONE ASP installer, and choose not to install Apache.
Choose your preferred language
When asked which web server to install SunONE ASP to, choose to do a Fast search for web servers in common locations.
The SunONE ASP installer should now report that it has located a Zeus Web Server with a Settings file e.g. /usr/local/zeus/ns-config/https-<vserver>/config/magnus.conf - confirm the location choice to the installer.
- You may now choose to customize your SunONE ASP settings, one of these will be to restart the host Web Server (Zeus in this case) to activate the updated configuration. If you do not say yes to this question, perhaps because you chose not to customize your SunONE ASP settings, you will need to restart Zeus manually.
Similarly, you can also choose to customize the Administration Console configuration (whether to start on boot, the port number to listen on ["5100"], the default username ["admin"], and the default password ["root"]) or again go with the defaults.
-
SunONE ASP will now verify it's installation, and exit if successful - can can now proceed to access the samples (if installed) to verify functionality.
-
Test your SunONE ASP installation by looking at the examples at http://<vserver>/caspsamp/.
If you experience difficulties, please first test that the examples can be accessed directly from Apache Web Server.
SunONE ASP adds entries to the /etc/services file on the system it is installed upon. These entries look like:
# Local services
casp3000 3000/tcp # 3000 - Sun ONE ASP
casp3001 3001/tcp # 3000 - Sun ONE ASP
casp3002 3002/tcp # 3000 - Sun ONE ASP
casp3003 3003/tcp # 3000 - Sun ONE ASP
casp3004 3004/tcp # 3000 - Sun ONE ASP
casp3005 3005/tcp # 3000 - Sun ONE ASP
casp3006 3006/tcp # 3000 - Sun ONE ASP
casp3007 3007/tcp # 3000 - Sun ONE ASP
casp3008 3008/tcp # 3000 - Sun ONE ASP
casp3009 3009/tcp # 3000 - Sun ONE ASP
casp3010 3010/tcp # 3000 - Sun ONE ASP
casp3011 3011/tcp # 3000 - Sun ONE ASP
casp3012 3012/tcp # 3000 - Sun ONE ASP
casp3013 3013/tcp # 3000 - Sun ONE ASP
casp3014 3014/tcp # 3000 - Sun ONE ASP
casp3015 3015/tcp # 3000 - Sun ONE ASP
casp3016 3016/tcp # 3000 - Sun ONE ASP
casp3017 3017/tcp # 3000 - Sun ONE ASP
casp3018 3018/tcp # 3000 - Sun ONE ASP
casp3019 3019/tcp # 3000 - Sun ONE ASP
casp3020 3020/tcp # 3000 - Sun ONE ASP
casp3021 3021/tcp # 3000 - Sun ONE ASP
casp3022 3022/tcp # 3000 - Sun ONE ASP
casp3023 3023/tcp # 3000 - Sun ONE ASP
casp3024 3024/tcp # 3000 - Sun ONE ASP
casp3025 3025/tcp # 3000 - Sun ONE ASP
casp5100 5100/tcp # 5100 - Sun ONE ASP Administration Console
casp5101 5101/tcp # 5101 - Sun ONE ASP Administration Console Engines
casp5102 5102/tcp # 5101 - Sun ONE ASP Administration Console Engines
Before installing SunONE ASP to ensure that there are no left over entries from a previous installation. Uninstalling SunONE ASP does not appear to remove these entries. Careful auditing of the /etc/services file is therefore recommended before and after installing this product.
Other files added to the system include files in /etc/init.d named asp-admin-port, asp-server-port, and apache-bindle-port. These can similarly be left behind after uninstallation if interleaving copies of SunONE ASP are installed on the same server.
