Introduction

The SEAGULL Java Web Manager is an optional web based administrative and management tool for Seagull Software’s BlueZone family of host connectivity products.  The Java Web Manager is designed to be a multi-platform application.

SEAGULL Java Web Manager requirements:

• A web server that can support Java Servlet API 2.1 or later
• Pentium 200 or higher processor
• Enough memory to support your operating system and web server per the OS and web server software vendors recommendations

Scope

The scope of this QuickStart Guide is to provide an overview and the steps necessary to install the Java Web Manager. Once the installation is complete, you will be able to access the Java Web Manager user interface and launch BlueZone Web-to-Host demonstration sessions.  Also, you will be able to access the Java Web Manager Administrator Interface and launch the Java Web Manager Administrator’s Guide which will guide you through the process of configuring the Java Web Manager to meet your specific End User and host access requirements.

Overview

SEAGULL Java Web Manager is the "Web Enabled" management application for controlling the distribution and configuration of Seagull's BlueZone family of host connectivity products.

The Java Web Manager must be installed on a web server that is accessible by your end users.

Server Location Tips:

• If you want to distribute BlueZone emulation to remote users over the Internet, typically this web server would then be installed outside of your corporate firewall in a DMZ.
   
• If you want to distribute BlueZone emulation to local and remote users on an Intranet or private network, this web server would then be installed anywhere on your private network that is accessible by your local and remote users.
   
• If you want to distribute BlueZone emulation to internal users on a local LAN, this web server would then be installed anywhere on your internal network that is accessible by your local users.

Minimum Requirements

Web Server

• A web server that can support Java Servlet API 2.1 or later
• Intel Pentium 200 or higher processor
• Enough memory to support your operating system and web server per the OS and web server software vendor’s recommendations
• 25 megabytes of free disk space.

Java Web Manager will run in most modern Servlet containers implementing the Java Servlet API 2.1 or higher. It has been tested in IBM WebSphere 3.5 on OS/390, OS/400, Windows NT and Windows 2000; in Caucho Resin on Linux 7.2, in Apache Tomcat 3.x on Win98/NT/2000; and Apache Tomcat 4.x on Win98/NT/2000, HP-UX, and Linux 7.2.

Web Client

Web Client requirements can be found at the following location:

http://www.seagullsoftware.com/docs/html/bluezone_requirements.htm

Installing SEAGULL Java Web Manager

If you want to upgrade your current installation of Java Web manager, click here for the Upgrade Procedure

The Java Web Manager is distributed as an industry standard Web Application Archive, or WAR.  The structure of a WAR is such that it can be placed directly into a compliant Servlet container, the container will discover the WAR, unpack it from the archive format and place the resulting Web application into service.

Please consult your Servlet container's documentation for appropriate installation instructions for WARs and Web Applications.

If your Servlet container does not perform automatic WAR installation, then you may be able to install the Web application manually. The WAR file compression format is actually a ZIP format. Unzip (gunzip, jar) the WAR and install it into your Servlet container according to the manufacturer's instructions for installation and registration of Web applications.

Java Web Manager will run in most modern Servlet containers implementing the Java Servlet API 2.1 or higher. It has been tested in IBM WebSphere 3.5 on OS/390, OS/400, Windows NT and Windows 2000; in Caucho Resin on Linux 7.2, in Apache Tomcat 3.x on Win98/NT/2000; and Apache Tomcat 4.x on Win98/NT/2000, HP-UX, and Linux 7.2.

NOTE For instructions on how to install Java Web Manager on WebSphere 3.5 running on OS/390, click here

If you need to download and install the latest Java SDK and Tomcat versions, follow these steps:

NOTE If you already have an acceptable version of the Java SDK and Servlet container installed on your server, then skip down to the Installing Web Manager section.

Java 2 SDK

1. To download the Java 2 SDK, click the following link:

http://java.sun.com/j2se/1.4.2/download.html

2. Locate and click the “Download J2SE SDK” link.
    
3. Scroll down and accept the license agreement.
    
4. Locate your server platform from the list and download the appropriate file.

Tomcat Download

1. To download Tomcat, click the following link:

http://jakarta.apache.org/tomcat/index.html

2. In the left hand column, locate and click the “Binaries” link under the Download heading.
    
3. Scroll way down the page until you come to the Tomcat 4.1.30 heading.  The listing is alphabetical.
    
4. Download the appropriate Tomcat 4.1.30 file (.zip, .tar or .exe) for you server platform.

NOTE If you are installing Tom act on a Microsoft server, we recommend downloading and installing the .exe version of Tomcat.

Installation

1. Install the Java SDK.

CAUTION! The Java SDK must be installed before Tomcat.

2. Install Tomcat.

Installing Web Manager

1. Copy the SWM.WAR file (available after downloading and unzipping the CD Image) to C:\Program Files\Apache Group\Tomcat 4.1\webapps.
    
2. Start Tomcat (from the icon created at installation time) it will unpack the WAR file and create an SWM folder.

NOTE Be patient... this may take a while!

3. You can then start web manager by launching a browser session and entering: http://yourservername:8080/swm/admin

Congratulations! The installation portion of the Web Manager is complete.

Proceed to the next section: Installing the SEAGULL Activation File

Installing the SEAGULL Activation File - Very Important

Installing the SEAGULL Activation File is very simple. It’s simply a matter of copying the SAF file to the correct directory on the web server. By default, BlueZone comes with a "non-working" SAF file as a placeholder.

BlueZone emulators will not function properly unless you install a valid SEAGULL Activation File (SAF).

1. Locate your SEAGULL Activation File (it will be called seagull.saf) which was sent as an E-mail attachment to the person who ordered BlueZone.
    
2. On your web server, copy this SAF file to the “files” subdirectory (swm\files) of the Web Manager installation, overwriting the existing SAF file.

NOTE If you don’t have your SEAGULL Activation File at this time, you can proceed with the installation, it’s just that when you test the connection, you will receive the following error:

This error will go away once you have installed a valid SAF file.

Proceed to the next section: Accessing Web Manager

Accessing Web Manager

Once installed, the Java Web Manager application will be available at the URL of your Servlet container in the "/swm"  directory.  The Web Manager is available to browsers via two Servlets: "/swm/Admin" and "/swm/Hosts".

The "Hosts" Servlet is the interface for users to launch BlueZone connections to your mainframes, iSeries, and servers.

Example:

http://www.yourhost.com/swm/Hosts or   http://68.19.128.11/swm/Hosts

The "Admin" Servlet is the interface for administration of BlueZone session distribution and configuration.

Example:

http://www.yourhost.com/swm/Admin or http://68.19.128.11/swm/Admin

Launching Demonstration Sessions

Once you have successfully installed the Java Web Manager, you can test the installation by launching the demonstration sessions.  Open your Web browser and go to the "Hosts" interface.  Your URL should look something like this:

http://www.yourhost.com/swm/Hosts  or   http://68.19.128.11/swm/Hosts

You should see the "login" screen, where you enter a Login ID and Password to login to Java Web Manager as shown.

eZClear

You will also see a link labeled "Clear BlueZone". This link will access a utility we provide called eZClear.  It’s a good idea to run eZClear to clear your cache of old BlueZone files prior to testing and configuring BlueZone sessions. This allows you as the Administrator, to view the sessions the way a "first time" user would see them and also provides a convenient way for you to "reset" a user.  Running eZClear on an End User's workstation will delete any configuration changes that they have made to their BlueZone sessions, so do not run it if they have settings that they wish to keep.  To run eZClear, click the link and follow the instructions.

Launching the Demo

A default user has already been pre-configured with the Login ID of "demo" and password "demo". Login now using demo/demo.

If this is a "new" login, you should get a dialogue asking for permission to run the SEAGULL Web-to-Host Control Module.  This component handles the interaction between the PC and the Web Server.

If this is the first time BlueZone has ever been run on this workstation, you will receive a dialogue asking for permission to run the SEAGULL Web-to-Host Control Module.  This component handles the interaction between the End User workstation and the Web Server.

You should now see the Java Web Manage default Launch Page.  This screen consists of six session listings, one for each of the BlueZone applications available via the Java Web Manager as shown:

There are a number of ways to launch BlueZone sessions.  Underneath each icon, there is a "launch" link - click on a link to launch the corresponding session.  Below the "launch" link, there is a check box, check the sessions you wish to launch and click the "Launch Selected Sessions" button at the top of the page.  A third alternative is to click the "Launch All Sessions" button at the top of the page, which will launch every session listed on the page and is analogous to selecting every checkbox and clicking the "Launch Selected Sessions" button.

Once you launch a session, you should see a small window with a progress bar indicating that the SEAGULL Web-to-Host Control Module is caching BlueZone components.  If you receive error messages, consult the Troubleshooting Guide located in the BlueZone Web-to-Host Administrators Guide.  Once all components are cached, a BlueZone session window will open.

Congratulations! You should now have BlueZone applications up and running.

Once you have a session window open you can close the browser or browse away and your sessions will remain active.  You can also close the session windows and easily re-launch them from the "launch" window. At this point, launching a session that is already launched will bring the requested session window the front.

SEE BlueZone Display & Printer Help for help with individual BlueZone emulation clients.

Administrator Interface Login

Open your Web browser and go to the "Admin" interface. Your URL should look something like this:

http://www.yourhost.com/swm/Admin  or  http://68.19.128.11/swm/Admin

You should see the "login" screen, where you enter a Login ID and Password to login to the Java Web manager Administrator Interface as shown here:

Two administrator's are pre-configured: "owner" and "admin". For this exercise you may login as either the owner or the administrator of this Java Web Manager. The password is the same as the Login ID.  Login as owner/owner.

SEE The Java Web Manager Administrator’s Guide for more details.

Java Web Manager Administrator’s Guide

To access the Java Web Manager Administrator’s Guide, login to the Administrator Interface (as described above), locate the Help section (near to top of the page) and click the link labeled “Online Help - Detailed online help is available here”.

You will be brought to the Web Manager Help Pages.  Click the link labeled “Web Manager Administrator’s Guide”.