|
|
|
|
 |
|
|
|
|
||||||||||||||||||||
|
|
|||||||||||||||||||||
|
||||||||||
BlueZone Web-to-Host is provided with several key web pages that make the product work.
The default.htm Page - The default.htm page contains a JavaScript that determines the exact browser type and level that is being used to access the web server. Since BlueZone Web-to-Host is designed to work with both Internet Explorer and Netscape Navigator, it is necessary for BlueZone Web-to-Host to know the browser type so that the correct ActiveX Control or Plug-in is served up to the end user. The default.htm page automatically launches frame.htm when the JavaScript is complete. It is not necessary, nor is it recommended to edit this JavaScript.
The frame.htm Page - The frame.htm page is an HTML page that contains a zero size frameset. The purpose of this frameset is to make the BlueZone Web-to-Host emulators appear to launch directly from the select.htm page as opposed to launching from the page that contains the Object Tag. This makes for a better user interface by cutting down on the number of keystrokes and web pages that are need to launch a BlueZone session. BlueZone Web-to-Host can be used without the frame.htm page without causing a problem.
The launch.htm Page - The launch.htm page is a default web page that contains icons and links to each BlueZone Web-to-Host client as mentioned in the Introduction. This page can be easily customized to suit your needs. The launch.htm page is a standard HTML page that was purposely designed not to contain any special hidden code or JavaScript so you can feel free to make changes to this page without any adverse affect on the product. If you prefer, you can delete the launch.htm entirely. However, this is not recommended until you have the product installed and working properly.
For instructions on how to delete the launch.htm page, click here.
Please look at the launch.htm page now by clicking here.
At the top of the page, there are four links, one for each of the BlueZone Web-to-Host emulators:
If you mouse over the links, you will see that each link goes to a web page called select_x.htm that is located in a separate folder, one for each emulator. The select_x.htm pages link to pages that contain Object Tags which enable BlueZone Web-to-Host to work. The Object Tag is discussed in more detail in ”The Object Tag - Advanced Configuration” section.
To see a BlueZone Web-to-Host Logic Flow Diagram, click here.
In the bottom half of the launch.htm page, there are three additional links:
eZClear is a very small (36KB) utility that is intended to be used as an administrative tool. Running eZClear will erase all the BlueZone Web-to-Host files, plug-in’s, ActiveX Controls, Registry entries and temp files from a specific users PC. eZClear is especially handy during the installation, testing and initial configuration of BlueZone.
The BlueZone Help Link will connect you to the BlueZone Help section of the SEAGULL web site.
The Administrator’s QuickStart Guide is intended primarily as a guide for new installations, not upgrades.
The technique used in this upgrade involves installing the new version of BlueZone Web-to-Host along side of your existing eZ3270/5250 installation. The BlueZone Web-to-Host setup program will create a new installation directory and copy the new BlueZone Web-to-Host files.
When the upgrade is complete, you will essentially have two working versions, your original eZ3270/5250 version and the new BlueZone Web-to-Host version. Using this method protects your current production installation of eZ3270/5250 and allows for testing and configuration of the new BlueZone Web-to-Host files before cutting over to production.
There are seven steps to the BlueZone Web-to-Host upgrade:
NOTE to Existing BlueZone Customers We are in the process of changing to a new software licensing scheme. This new Software Activation Feature, is currently not required to be used by existing BlueZone Customers. If you are an existing Customer, no changes are needed at this time. You can continue to use the current BlueZone licensing scheme.
However, if you would like to learn more about our new Software Activation Feature, click here.
The installation process is very simple. In fact, it is more of a copying process than an installation process. In other words, the BlueZone Web-to-Host files are simply copied to the appropriate folders or directories on your web server as static files. There is no associated BlueZone Web-to-Host application that runs on the web server.
For help in setting up a “virtual directory” on your web server, click here.
If you are installing BlueZone Web-to-Host on an HTTP Web Server, Domino Go, WebSphere or other EBCDIC web server, only the HTML files should be converted from ASCII to EBCDIC. All other files should be transferred as binary. All editing of the associated ASCII text files should be performed on an ASCII computer (not on the web server) with notepad, then copied back to the web server as a binary file.
 |
Also, be sure to copy the files as the correct file type as described above.
In order for BlueZone Web-to-Host to work properly with Netscape browsers, it is necessary to set the “path” which is located in the default.htm page. This “path” statement lets the JavaScript know the location of the Java Plug-in (.jar) and the Java “zippy” (.xpi) files.
You should now be able to connect to the newly created directory on your web server by accessing the web severs URL followed by /bluezone (or whatever name you gave to the newly created folder). This should bring up the default.htm page which will determine your browser type and version, then automatically launch the launch.htm page.
NOTE If you are using any optional features such as bzftp, BlueZone Scripting Host, HLLAPI, special fonts, etc., that are included in any of your Distribution Files, copy them over to the new bluezone directory now.
Here is an example of an old Distribution File vs. the new one.
|
NOTE It is no longer necessary to specifically call out the New Renex Terminal Font (nwrnxtrm.fo_,1) file because it is automatically included inside the .cab file, so you can delete it from your Distribution File. Any other fonts, should remain.
BlueZone Web-to-Host uses Object Tags instead of Embed Tags. Your Embed Tags will have to be converted to the new Object Tag format. This can be done manually or it can be done through a web based conversion utility provided by SEAGULL.
In eZ3270/5250 the pages that contained the Embed Tag was typically called display.htm or printer.htm. When an end user accessed one of these pages, the Embed Tag caused an eZ3270/5250 session or sessions to launch.
Here is an example of a simple mainframe Embed Tag:
<embed src=display.e3d s1=mfdisp1.zmd></embed>
In BlueZone Web-to-Host, it’s the pages that contain the Object Tags that will launch your BlueZone session or sessions. These pages are called obj_d_x.htm and obj_p_x.htm, and can be found in their respective folders. For example the obj_d_3.htm page for mainframe can be found in the bz3270 folder.
Here is an example of the Embed Tag shown above converted in an Object Tag:
<!-- Start IE Section -->
<OBJECT ID="Seagull Web-to-Host Control Module v3"
CLASSID="clsid:037790A6-1576-11D6-903D-00105AABADD3"
CODEBASE="../sglw2hcm.ocx#Version=3,1,0,201" HEIGHT=0 WIDTH=0>
<PARAM NAME="IniFile" VALUE="default.ini">
<PARAM NAME="Sessions" VALUE="MD_S1">
<PARAM NAME="MD_DistFile" VALUE="display.e3d">
<PARAM NAME="MD_S1" VALUE="mfdisp1.zmd">
<PARAM NAME="MD_S1_Save" VALUE="Yes">
</OBJECT>
<!-- End IE Section -->
<!-- Start Netscape Section -->
<OBJECT TYPE="application/x-bluezone" HEIGHT=0 WIDTH=0>
<PARAM NAME="IniFile" VALUE="default.ini">
<PARAM NAME="Sessions" VALUE="MD_S1">
<PARAM NAME="MD_DistFile" VALUE="display.e3d">
<PARAM NAME="MD_S1" VALUE="mfdisp1.zmd">
<PARAM NAME="MD_S1_Save" VALUE="Yes">
</OBJECT>
<!-- End Netscape Section -->
In the above example, note that there are two Object Tags, one for Internet Explorer (shown in blue) and one for Netscape (shown in red). When editing Object Tags you must make your changes to both Object Tags.
At first, Object Tags look very different from Embed Tags. However, if you look closely, you will see that they are very similar, they just have a different structure. Each Object Tag consists of a header and a body. The body is the part that contains all the PARAM NAME entries. The body is the part of the Object Tag that we are concerned with here.
If you break out the body of the Object Tag from the header and compare it to the Embed Tag, you will see that they are very similar.
<embed src=display.e3d s1=mfdisp1.zmd Save1=Yes></embed>
Go ahead and update the new Object Tags with the information contained in your existing Embed Tags.
NOTE When editing the Object Tags, it is very important to pay close attention to exact syntax. You must maintain quotes, exact character spacing and case of the characters that are used in the PARAM NAME strings. Very often when a problem occurs, it can be traced to a typo or incorrect case of a PARAM NAME value.
To learn more about Object Tags, click here.
Registration Key - Update the default.ini file by copying your current Registration Key from the old ez.ini file to the new default.ini file.
Configuration Lock - If you are using the Configuration Lock Feature update the values from your old ez.ini file located in the old ez directory.
If you are currently using multiple ez.ini files in eZ3270/5250 to support multiple lock configurations or desktop icons for multiple emulators, you will need to create multiple .ini files in the new BlueZone Web-to-Host system to support this. If you simply copy over the old .ini files, they will not have the correct structure. Instead, use the default.ini file as a master and copy it the number of times you need and then rename them with the same names you used in eZ3270/5250.
You have successfully upgraded eZ3270/5250 to BlueZone Web-to-Host. For more detailed information about operation of the BlueZone Emultor’s please consult the BlueZone Administrator’s Guide. For more detailed information about BlueZone Web-to-Host, please consult the BlueZone Web-to-Host Administrator’s QuickStart Guide.
 |
|
|
 |
