SEAGULL Web Manager

Administrator’s QuickStart Guide

Version 3.4

Introduction & Scope

Overview

Minimum Requirements

How SEAGULL Web Manager Works

Installing SEAGULL Web Manager

Manually Installing the SEAGULL Activation File

Configuring BlueZone Licensing

Testing the Connection

Administrator Login

Advanced Features

Enabling Optional Components

Launching BlueZone FTP From a Display Session

Advanced Login Features

Customize Your Host Access Login Screen

278-04

 

Introduction

The SEAGULL Web Manager (ASP Version) is an optional web based administrative and management tool for BlueZone Web-to-Host.

SEAGULL Web Manager minimum requirements:

  • Windows NT 4.0 SP4 or higher, Windows 2000 SP2 or higher
  • IIS (Internet Information Services) Version 4.0 or higher
  • Pentium 200 or higher
  • 64 Megabytes of Memory (128MB is required for Windows 2000)

Scope

The scope of this QuickStart Guide is to provide the steps necessary to perform an installation and basic configuration of the SEAGULL Web Manager.

 

Overview

The SEAGULL Web Manager (ASP Version) is a web based ASP (Active Server Page) program that requires a Microsoft NT 4.0 or Windows 2000 server running IIS version 4.0 or greater to operate. It’s purpose is to provide a web based interface for the administration, management and distribution of the SEAGULL BlueZone Web-to-Host family of emulation products.

The SEAGULL Web Manager must be installed on a Microsoft 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 is required to serve the BlueZone Web-to-Host application to the browser upon request.  No processing or emulation is performed on the web server, eliminating the need for additional processing power beyond that necessary to download less than one megabyte of files to the browser whenever the BlueZone Web-to-Host application is initially accessed or updated.

  • Any web server that supports HTML and JavaScript.
  • 10 megabytes of free disk space.

Web Client

Web Client requirements can be found at the following location:

 

How SEAGULL Web Manager Works

The SEAGULL Web Manager allows administrators to assign and manage host access sessions at the user level or at group levels, with control over almost every aspect of the user’s sessions, including dynamic LU/Device Name assignment.  Dynamic LU/Device assignment is the ability to assign an LU/Device to a user based on a user ID.

From the user's perspective, the user logs in to the application which then automatically downloads and deploys the host connectivity application, fully configured for that user including assignment of appropriate LU/Device Names. It then can automatically launch and connect the user to the host.

Application Structure

The Web Manager has two divisions, the User Interface and the Administration Interface.


User Interface

The User Interface consists of four screens: The login screen, the component initialization screen, the launch screen, the uninstall screen.

The User Interface requires either no action or that the user enter authentication information and click a OK button.

The login screen allows users to login to the application via Windows NT authentication (Internet Explorer Only), or via a loginID and password combination, or via a loginID only.  LoginID information can be automatically entered from a URL or an HTML form post or automatically detected, see Advanced Login section for details.

Once the user has been authenticated, they receive the component initialization screen, then are automatically taken to the launch screen, where host sessions are launched.  From the launch screen, users may then uninstall BlueZone.

Administration Interface

The Administration Interface is divided into six sections: Admin Home, User Manager, LU/Device Name Manager, Groups Manager, File Manager and Application Settings. These sections are designated by their icons.  Clicking on an icon (which appear to administrators at the top right hand corner of the screen) will take you to the main page for that section. Sections are designated with large versions of the icon in the background.

 Admin Home

The Admin Home is the starting point of the SEAGULL Web Manager application. It holds links to all of the other sections, to help, to default configurations, and the administrator's own configured sessions.

 User Manager

Through the User Manager, the administrator may add, modify and delete users and user sessions. This gives the administrator fine-grained control over user sessions. The administrator may also test user configurations from this section.

 LU/Device Name Manager

Via this interface, the administrator may add, modify and delete LUs (known as Device Names on the AS/400, called LUs here). The administrator designates the name, device type (e.g. AS/400 Printer, Mainframe Display), and the user to whom the LU is assigned.

 Groups Manager

The Groups Manager allows the administrator to add, modify and delete groups. A group is a collection of users, who share the same configuration files and settings. Group users may also receive dynamic LUs.

 File Manager

Through the File Manager, the administrator may create and modify distribution files (.bzw, .e3d, .e3p, .e5d, .e5p) and .ini files.

 Application Settings

Through the Application Settings, the administrator may view and modify global application settings.

 Log Out

The logout icon does not designate a section, it is provided as a convenient way to log out of the application from any screen.

 

Installing SEAGULL Web Manager

Pick your server from the following list, and follow that procedure. At the end of the procedure, the there will be a link that will return you to the next section.

At the end of the procedure, the there will be a link that will return you to the next section.

Windows NT 4.0 Server

Windows 2000 Server

Windows 2003 Server

 

Manually Installing the SEAGULL Activation File

NOTE This step is not necessary if you have already installed your Seagull Activation File during the installation process. If you have already installed it, proceed with Testing the Connection.

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 “BlueZone” subdirectory 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 - Testing the Connection

 

Testing the Connection

NOTE Performing the following “test” is absolutely necessary in order to properly set up the correct file paths in the SEAGULL Web Manager.

You should now be able to connect to the SWM directory on your web server by accessing the web server's URL followed by /swm. This should bring up the default Host Access Login page that end users will use to launch their sessions.

    Example: http://www.yourhost.com/swm

  1. Go to the default Host Access Login Page now.  It should look like this:

 

  1. Log in using the following Login ID without a password:

    Login ID = 5250demo
    Password =

    Click the Login button.
     
  2. You will be presented with the following screen:

  1. Click the Launch All Sessions button.
     
  2. This will launch a standard iSeries Display and Printer session to one of the Seagull iSeries hosts.
     
  3. Once the sessions are launched, close them down and proceed to the Administrator Login.

NOTE If you are installing a licensed version of BlueZone Web-to-Host, you will receive the following error:

To learn how to configure BlueZone to work with the SEAGULL License Manager, go to the Configuring BlueZone Licensing section.

 

Administrator Login

The SEAGULL Web Manager uses a slightly different URL for Administrator Login. This is done for security purposes. By making the physical path different, it is less likely that an end user will be able to “accidentally” login as an administrator.

To login as the administrator, add a forward slash followed by the word admin (/admin) to the end of the URL that you use to access the Web Manager login page and press enter.

    Example: http://www.yourhost.com/swm/admin

You will be presented with the Web Manager Administrative Login Screen as shown.

Use the following default "top level "account to login to Web Manager:

    LoginID = owner
    Password = owner

Upon logging in with the above LoginID and password, Web Manager will present you with the main Admin Home page as shown below:

You can now start the process of entering users and host information.  Please note the “Getting Started and “Help” links on this page.

NOTE If you want to “administer” Web Manager from this server, make sure that any files that you create have write permissions set to “Everyone”. Web Manager requires that the administrator as well as end users have the ability to write to certain Web Manager files on the web server.  Otherwise, you may encounter errors when setting up and configuring users from a remote PC and also, end users may encounter permission related errors.

If this is a brand new installation of Windows NT 4.0 or Windows 2000, the default file permissions will work just fine.