Bluestone Total-e-Server version 7.3

Bluestone Total-e-Server version 7.3 is a J2EE-compliant web application server.

Overview

The HP Bluestone "Total-e-Server" product provides a couple of ways of interfacing with Zeus Web Server, via CGI or NSAPI. These interface plugins are called 'Load Balance Brokers' (LBBs), and Zeus Web Server can use either:

• the Generic LBB, which is a CGI plugin
• the Netscape LBB, which is an NSAPI plugin

The HP Bluestone "Total-e-Server" 7.3 has been tested by Zeus Technology on Solaris 8/SPARC, HP-UX 11.11 and Linux 2.2/x86. The Generic LBB works on both operating systems. However, the Netscape LBB will not work under Linux. The NSAPI plugin provides significantly higher performance than the CGI plugin.

HP Bluestone's documentation for the LBBs is available at:

http://developer.bluestone.com/scripts/SaISAPI.dll/Gallery.class/docs/index.jsp

Choose the appropriate version of Total-e-Server and navigate to:

Total-e-Server

   -> Bluestone Universal Business Server

      -> Architecture

         -> Load Balance Broker.

In the rest of this document, it is assumed that Total-e-Server is installed in /opt/bluestone (pointed to by the environment variable $BSDIR) and Zeus Web Server in /usr/local/zeus (and set in the environment variable $ZEUSHOME).

Preparation

Install HP Bluestone Total-e-Server following the instructions provided in the HP documentation. Change directory into the $BSDIR/config/ subdirectory. Make sure that you have three files called SaLBB.ini, apserver.txt and sajava.ini. If any of these files are missing, suitable default files may be found in SaLBB.ini.example, apserver.txt.example and sajava.ini.trail.

Installing the Generic LBB

Create a Virtual Server using the Zeus Administration Server web-based user interface. Access the CGI configuration page by clicking the General link in the Virtual Server's configuration menu. Enable support for CGI scripts by clicking the appropriate radio button.

In the Configuring Additional CGI Environment Variables section, configure an environment variable called SAPPHIRE, set to $BSDIR (in our example, this will be /opt/bluestone).

The CGI LBB can be made accessible to the web server by adding an alias. Scroll down to the Configuring Aliases for CGI Script Directories section. Then add the following configuration:

Map requests for: /cgi-bin (or your choice)

Map requests to: $BSDIR/bin/Linux

Once this is done, click the Apply changes button to commit the new configuration. The CGI LBB executable may need to be made executable, by using the command chmod +x, if it is not already so. Any changes that have been made to the the virtual server should be applied, then the Bluestone server can be started (refer to $BSDIR/readme.txt). Access the 'Trail Map' with the following URL:

 http://your-host/cgi-bin/SaCGI.cgi/Demo.class/docs/index.htm

Step 8 of the trail map is a good test that things are working. In the sample URL, replace localhost/Scripts/SaCGI.cgi with the path to the CGI (for instance [your-host]/cgi-bin in the example immediately above).

Installing the Netscape LBB

First, enable NSAPI under Zeus Web Server by setting the radio button on the NSAPI configuration page. Copy the default NSAPI configuration files supplied with Zeus from the nsapi-skel directory, and copy these into the directory specified on the NSAPI configuration page.

Edit the mime.types file and add the following line:

 type=magnus-internal/sapphire exts=sph

Edit the obj.conf file, adding the following two lines after the first "load-types" line:

Init fn="load-modules" shlib="$BSDIR/bin/Linux/SaNSAPI30.so"
    funcs="sapphire-form,sapphire-init"
Init fn="sapphire-init" file="$BSDIR/config/apserver.txt"

    java="$BSDIR/config/sajava.ini"

Locations and names of the files will need to be changed as appropriate for your system.

In the <Object name="default"> section of the obj.conf file, add this line:

Service fn="sapphire-form" method="(GET|POST)"
    type="magnus-internal/sapphire"

In the document root, create an empty file called default.sph, and commit the changes for the Virtual Server. You may receive an INFO message regarding a license file; this does not appear to affect the actual operation of the LBB.

To check that the LBB has been successfully installed, ensure that the Bluestone server is running and access this URL:

http://[your-host]/default.sph/Demo.class/docs/index.htm

You should also try the JSP in step 8 of the trail map:

http://[your-host]/default.sph/Demo.class/docs/jspHelloWorld1/HelloWorld1.jsp

Content Manager [Administrator] 16 December 2005