AniTa for the Web is a version of April System Design's AniTa terminal emulator that is written in 100% Java and primarily designed for use in an Internet / Intranet environment.
AniTa is the terminal emulator that gives new life to your text based applications on platforms such as UNIX, Linux and VAX. AniTa makes your text based application look as if they were written for a windowing environment with a graphical user interface (GUI). It gives you mouse, 3-D box attributes, color support and adds a graphical touch to your character based applications. All this helps extend the life of your text-based solutions.
AniTa supports a wide range of terminal emulations including DEC VT100, VT220, VT320, ANSI, Wyse60, and SCO Console emulations.
The easy to configure, 3-D box and color options, allow you to assign such attributes even when running an existing application written for text based monochrome screens. Alternatively the color can be controlled from the host with ANSI, ASCII or DEC VT525 color commands.
AniTa allows you to add buttons and icons to your text-based applications, and even to send information to the host by clicking the mouse on your application's screen.
AniTa gives you the choice of deploying as an Application, as an Applet or via Java Web Start. This means that you can choose to run AniTa for the Web either in its own window or in a web browser, and you choose whether to load the program from a disk or web server.
In addition to being able to be loaded from your local workstation, AniTa can be run from a network server - either a file server or a web server. The small size of the AniTa for the Web code, means that it can be deployed not just on a Local-Area-Network server, but also on a Internet or Intranet Wide-Area-Network server.
The ability to deploy AniTa for the Web on a centralized server greatly simplifies both installation and maintenance. A single centrally stored version of AniTa means that it can be easily upgraded and maintained. When new features are added to the product, the system administrator needs only to copy it onto the central server, then all users have access to the new version. In the same way, one or more centrally located configurations allow one configuration update to apply to all users.
AniTa for the Web is written in 100% JAVA. It conforms to the JAVA 2 specification and runs on a JAVA Virtual Machine version 1.2 or later.
This means that AniTa for the Web can run on any platform that supports this specification. Such platforms include Windows, Linux, Mac OS X, Solaris and UNIX well as a range of thin-clients.
By choosing AniTa for the Web as your terminal emulator, you gain independence of workstation platform. You can easily migrate from one platform to another and without problem combine different types of workstation platforms. You are no longer tied to one specific hardware or software supplier.
The pluggable look-and-feel capability implemented in AniTa for the Web means that you can have a "Microsoft Windows GUI" look-and-feel when running on Microsoft Windows and an "Linux windows GUI" look-and-feel when running on Linux or you can choose to have the same look-and-feel across all platforms.
In order to run the AniTa for the Web terminal emulator or its configuration program you must have a JAVA Virtual Machine (JVM). Although AniTa for the Web will run with a JVM version 1.2, we recommend using at least version 1.2.2 and if possible we strongly suggest that you use version 1.3 or for best performance 1.4. Installation of such a JVM is explained in Chapter 2 of this document; if you already have such a JVM installed, you can skip all of chapter 2.
When running the terminal emulator as an application and when running the configuration program the JVM is normally provided by installing a JAVA Runtime Environment (JRE).
The AniTa for the Web terminal emulator can run as an Applet in a Netscape Navigator or Microsoft Internet Explorer web browser. When running as an applet, the JVM is normally provided as a plug-in to the web browser. It is not necessary to install the plug-in initially on every computer, instead the plug-in will be loaded the first time it is required (e.g. if not already present, the first time you run AniTa for the Web in a web page).
For your convenience, a copy of this documentation is provided on the AniTa for the Web release CD. The JANITA directory on the CD contains a sub-directory called janitadoc containing this document in a file called index.html.
The latest version of the documentations is always available on the Internet at: http://www.april.se/janita.
The following information can be used to contact us for more information about our other products. It can also be used to obtain support help if your local distributor is unable to help you.
| Telephone: | +46 8 764 7040 |
| Fax: | +46 8 764 7044 |
| Tollfree Telephone: | 1-888-642-7745 |
| 1-888-64-APRIL |
The two e-mail addresses below can be used to contact April's marketing and support departments. The web server contains up-to-date information about all our products and how to contact us. The ftp server contains the latest upgrades and support releases for our products.
| Web server: | http://www.april.se |
| ...or: | http://www.aprilsystem.com | Ftp server: | ftp://ftp.april.se |
In order to run the AniTa for the Web terminal emulator or its configuration program you must have a JAVA Virtual Machine (JVM). If you already have such a JVM installed, you can skip to the next chapter.
When running the terminal emulator as an application and when running the configuration program the JVM is normally provided by installing a JAVA Runtime Environment (JRE). When running the terminal emulator as an applet, the JVM is normally provided as a plug-in to the web browser.
Although AniTa for the Web will run with a JVM version 1.2, we recommend using at least version 1.2.2 and if possible we strongly suggest that you use version 1.3 or for best performance 1.4.
The following information is provided only as a quick guide to installing the JVM. For the latest information see the relevant JVM documentation.
The JAVA Runtime Environment (JRE) for Windows 32-bit platforms is available from Sun. For convenience, we provide a copy on the same release CD as AniTa for the Web: in a catalog called "\JRE". The JRE can also be downloaded from Sun over the Internet at the address: http://java.sun.com/j2se/downloads.html.
The JRE is contained in a file called: j2re-1_4_1_02-windows-i586-i.exe. Note that the name of the file will change as the version of JRE changes.
To install the JRE on Windows:
The JRE is contained in a file called: j2re1_3_1-win.exe. Note that the name of the file will change as the version of JRE changes.
To install the JRE on Windows:
Some versions of Linux ship with a JRE already installed, so that it is quite likely that you will not need to install the JRE. However the following procedure can be used for those systems without a JRE or with an old version.
Please note, that unlike the Windows JRE, Sun have a different install procedure for the different versions of the Linux JREs.
The JAVA Runtime Environment (JRE) for Intel based Linux platforms is available from Sun. For convenience, we provide a copy on the same release CD as AniTa for the Web: in a catalog called "/JRE". The JRE can also be downloaded from Sun over the Internet at the address: http://java.sun.com/j2se/downloads.html.
The JRE is contained in a file called: j2re-1_4_1_02-linux-i386.bin or j2re-1_4_1_02-linux-i586-rpm.bin ..
To install the JRE in Linux:
To install the JRE in Linux as an RPM:
The JRE is contained in a file called: j2re-1_3_1-linux-i386.bin or j2re-1_3_1-linux-i386-rpm.bin.
To install the JRE in Linux:
To install the JRE in Linux as an RPM:
The JRE is contained in a file called: j2re-1_3_0-linux.sh or j2re-1_3_0-linux-rpm.sh.
To install the JRE in Linux:
To install the JRE in Linux as an RPM:
The JRE is contained in a file called: jre-1_2_2_006-linux-i386.tar.gz.
To install the JRE in Linux:
Some versions of Solaris ship with a JRE already installed, so that it is quite likely that you will not need to install the JRE. However the following procedure can be used for those systems without a JRE or with an old version.
The JAVA Runtime Environment (JRE) for Intel based Solaris platforms is available from Sun. For convenience, we provide a copy on the same release CD as AniTa for the Web: in a catalog called "/JRE". The JRE can also be downloaded from Sun over the Internet at the address: http://java.sun.com/j2se/downloads.html.
The JRE is contained in a self-extracting binary file called: j2re1_3_0_03-solx86.bin . Note that the name of the file will change as the version of JRE changes (e.g. version 1.2.2 was called Solaris_JDK_1.2.2_06_i386.bin).
To install the JRE in Solaris:
Some versions of Solaris ship with a JRE already installed, so that it is quite likely that you will not need to install the JRE. However the following procedure can be used for those systems without a JRE or with an old version.
The JAVA Runtime Environment (JRE) for Sparc based Solaris platforms is available from Sun. For convenience, we provide a copy on the same release CD as AniTa for the Web: in a catalog called "/JRE". The JRE can also be downloaded from Sun over the Internet at the address: http://java.sun.com/j2se/downloads.html.
The JRE is contained in a self-extracting binary file called: j2re1_3_0_03-solsparc.bin. Note that the name of the file will change as the version of JRE changes (e.g. version 1.2.2 was called Solaris_JDK_1.2.2_06_sparc.bin).
To install the JRE in Solaris:
Mac OS X ships with a highly-optimized, tightly integrated implementation of Java 2 Standard Edition, originally 1.3 and subsequently 1.4.1. It includes the client version of the HotSpot virtual machine. Further information can be found at: http://www.apple.com/java.
Information about obtaining and installing IBM AIX Java Technology Edition can be found at: http://www-106.ibm.com/developerworks/java/jdk/aix/index.html.
Currently only Netscape 6 supports a Java 2 Runtime Environment. No other browsers support JAVA 1.2 or later using their JAVA implementation, thus in order to run AniTa for the Web in these browser you need to have a JAVA plug-in.
JAVA Plug-Ins are available for the Netscape Navigator and Microsoft Internet Explorer web browsers from Sun at: http://java.sun.com/products/plugin/. The same site also contains very useful FAQs and Documentation.
It is not necessary to install the plug-in initially on every computer, instead the plug-in will be loaded the first time it is required (e.g. if not already present, the first time you run AniTa for the Web in a web page).
For other JAVA Virtual Machines, refer to the documentation provided with the JVM.
This chapter describes the installation of AniTa for the Web. Different sections of this chapter describe the installation methods on different operating systems.
AniTa for the Web can be installed on Windows 95, 98, NT, 2000, ME or XP Platforms.
To install the AniTa for the Web on Windows:
The above procedure can also be followed when performing an upgrade. This will cause the AniTa for the Web software to be upgraded, but the configuration files will remain unchanged.
Just click on one of the shortcut icons, to run the terminal emulator or its configuration program.
The installation procedure will automatically create an uninstall program. To run this, go to the "Control Panel" and click on "Add/Remove Programs". Select "AniTa for the Web" and click on the Add/Remove button.
This section described how to install AniTa for the Web on Linux platforms. It also explains how to add AniTa for the Web icons to the desktop - examples are given for the KDE 2.1 desktop. The procedures are similar for other desktops such as Gnome and CDE.
The above procedure can also be followed when performing an upgrade. This will cause the AniTa for the Web software to be upgraded, but the configuration files will remain unchanged.
It is possible to start AniTa from a desktop icon.
To start the configuration program from a desktop icon.
To add the AniTa for the Web documentation a desktop icon.
It is possible to start AniTa from the KDE Start Menu.
To add the configuration program to the start menu.
To add the AniTa for the Web documentation to the start menu.
To Run the AniTa for the Web terminal emulator from the command line: /usr/local/janita/janita
To Run the AniTa for the Web configuration from the command line: /usr/local/janita/janitaconfig
If you configured desktop icons, just click on one of the shortcuts, to run the terminal emulator or its configuration program.
To make AniTa for the Web available via the Web server on your Linux machine, you must do the following additional steps:
This section described how to install AniTa for the Web on UNIX platforms, including Solaris.
The above procedure can also be followed when performing an upgrade. This will cause the AniTa for the Web software to be upgraded, but the configuration files will remain unchanged.
To Run the AniTa for the Web terminal emulator from the command line: /usr/local/janita/janita
To Run the AniTa for the Web configuration from the command line: /usr/local/janita/janitaconfig
If you configured desktop icons, just click on one of the shortcuts, to run the terminal emulator or its configuration program.
To make AniTa for the Web available via the Web server on your UNIX machine, you must do the following additional steps:
Java Web Start combines the features and flexibility of a Java Application with the convenience and ease of use of a Web based program.
With Java Web Start, AniTa for the Web can be installed and configured once on a central web server, and then executed by users anywhere on the web without needing to install AniTa.
With Java Web Start, you launch AniTa for the Web simply by clicking on a Web page link. If AniTa for the Web is not present on your computer, Java Web Start automatically downloads all necessary files. It then caches the files on your computer so that AniTa for the Web is always ready to be relaunched anytime you want -- either from an icon on your desktop or from the browser link. And no matter which method you use to launch the application, the most current version of the application is always presented to you
Java Web Start runs independently of any browser, you can shut down your browser or surf to another Web page and continue using AniTa for the Web. When deployed with Java Web Start, AniTa for the Web does not require a browser interface to operate.
To save time later, the user can relaunch AniTa for the Web from the desktop icon, without powering up their browser again.
AniTa for the Web will only be loaded once across the web. Subsequently it will be executed from the client's local cache. However new versions of the AniTa for the Web program, or changes to its configuration with be automatically detected and updated.
AniTa for the Web is signed to provide security in an Internet environment.
On the workstation you need a web browser and a Java Runtime Environment.
Web start is included in the JRE starting with version 1.4. If you have version 1.3 then you will need to separately install web start.
Do not use a version 1.2 or earlier JRE. Although all of the normal functions of AniTa for the web are supported by the JRE 1.2, the JRE (as opposed to the plug-in) does not support code signing. Because AniTa can be loaded over the Internet, the code has been signed, so that the client knows that it is unchanged since it was released. This is to stop the possibility of code being send over the Internet being changed such as when infected by a virus.
To install a JRE go to: http://java.sun.com/j2se/
To install Web Start (only needed if you have a Java earlier than 1.4) go to: http://java.sun.com/products/javawebstart/
Once the Java Web Start software has been installed on the workstation, you can test it by running one of Sun's demo applications.
These are available at: http://java.sun.com/products/javawebstart/demos.html
Files
The directory on your web server that is chosen to for AniTa for the Web should contain the following files:
Because of janitaconfig's "export to jnlp" function, we suggest that you install the Java Runtime Environment 1.3 and the full AniTa for the Web onto the web server, even if you do not plan to use the application. There is however no requirement to install either Java or AniTa onto the Web server, it is quite possible to run the configuration program on a workstation, and just copy the exported JNLP and AWS file from the workstation to the server.
MIME
Configure the Web server to use the Java Web Start MIME type. All files with the .jnlp file extension should be set to the application/x-java-jnlp-file MIME type.
Most Web browsers uses the MIME type returned with the contents from the Web server to determine how to handle the particular content. The server must return application/x-java-jnlp-file MIME type for JNLP files in order for Java Web Start to be invoked. Each Web server has a specific way in which to add MIME types.
For a full explanation, check the documentation for the specifics of your Web server.
MIME on Apache
For the Apache Web server you must add a line to the MIME Types file. Look in the httpd.conf file for the parameter TypesConfig. This is followed by the name of the MIME Types file used by Apache. This file is usually called /etc/mime.types. Check this file for jnlp, and if it doesn't have an entry then add the following line:
application/x-java-jnlp-file jnlp
It is necessary to restart the Apache web server after adding a new MIME mapping !!!
MIME on Microsoft IIS
For Microsoft's Internet Information Server, this is done using the Internet Service Manager. Right click on the server and select properties. Select Computer MIME map and determine whether the .jnlp extension is mapped.
If the .jnlp extension is not mapped, then click "New Type" to map .jnlp to application/x-java-jnlp-file.
It is necessary to restart the IIS web server after adding a new MIME mapping !!!
AniTa for the Web can be run as an applet in a Web Browser. The AniTa applet is contained within the HTML code of a web page. The web page and the applet reside on the web server. The web page is normally in HTML format, but other formats such as ASP (Active Server Page) or JSP (Java Server Page) can be used to contain AniTa. ASP or JSP pages are especially useful if server side scripting is used in conjunction with AniTa.
AniTa is run in the Web Browser's Window and controlled by the Web Browser. AniTa is dependant on the type and version of Web Browser used. This is different from using Web Start, which only uses the Web Browser to start AniTa, then AniTa has control over its own window.
When running as an applet, AniTa for the Web can be installed and configured once on a central web server, and then executed by users anywhere on the web without needing to install AniTa.
AniTa for the Web is signed to provide security in an Internet environment.
On the workstation you need a Web Browser and a Java Plug-In Runtime Environment. AniTa for the Web requires version 1.2 or later of Java to run. We suggest version 1.3 or later. At the time of writing, the only browser to come with support for this is Netscape 6. Other browsers will need to download the Java 1.3 plug-in.
The first time the web browser encounters a web page that specifies the use of the plug-in, the browser must download and install the required files. System administrators can determine where users download Java Plug-in software; either from http://java.sun.com or from an internal server.
Sun provide information about the latest plug-in on their web site. Plug-ins can be downloaded free of charge from Sun: http://java.sun.com/products/plugin/
The directory on your web server that is chosen to for AniTa for the Web should contain the following files. They can be copied anywhere into the normal directory tree shared by the web server. the do not need to be placed in any special catalog such as cgi-bin.
You need to create a web page to contain the applet. This page is normally in HTML format. A default HTML page can be created automatically by the AniTa for the Web configuration program janitaconfig The web page will contain HTML tags to hold the applet and the configuration parameters.
Because of janitaconfig's "export to html" function, we suggest that you install the Java Runtime Environment 1.3 and the full AniTa for Java onto the web server, even if you do not plan to use the application. There is however no requirement to install either Java or AniTa onto the Web server, it is quite possible to run the configuration program on a workstation, and just copy the exported HTML file from the workstation to the server.
Once the configuration has been exported, the HTML file can be customized. It is also possible to use this HTML file as the basis for an ASP (Active Server Pages) or JSP (Java Server Pages) file. These allow the page including the AniTa for the WEB configuration to be changed dynamically using Visual Basic and JavaScript (ASP) or Java (JSP) programs.
The AniTa for the WEB applet is provided in two versions, the file janita.jar which is unsigned and the file janitas.jar which has been signed.
When an applet that has been signed is loaded into the web browser it is possible to verify who its creator was (in our case April System Design AB with a home site of www.april.se).
The applet is also checked to verify that it has not been changed since it was signed by the creator. A signed applet cannot be infected by a virus and still be successfully verified.
Web browsers contain a security mechanism called the sandbox. This sandbox greatly restricts the capabilities of applets. For example, the sandbox will only allow an applet to establish a terminal session (telnet) with the web server, it is not possible to telnet directly into any other machine.
However because of the built in verification security in a signed applet, it is possible for the user to "trust" a signed applet. The "trusted" applet still runs within the browser's sandbox, but with many of the restrictions removed.
The following functions can be performed by a signed and trusted, but not an unsigned, AniTa for the WEB applet.
We recommend using the signed version of the AniTa for the WEB applet.
The configuration information for AniTa for the Web is stored in an INI file, usually called janita.ini. The configuration program, janitaconfig, allows you to set most of the available configuration parameters. If you want to use a different configuration file name, this can be specified as the first parameter on the janitaconfig command line.
The configuration program is divided up into a number of different cards. Each of the cards is shown and explained later in this chapter.
AniTa for the Web supports a wide range of mnemonics. These are compatible with those in the Windows version of AniTa. Mnemonics always start with a < and end with a >, for example <ESC>.
These mnemonics allow different ways to specify the same code. For example all of the following would have the same effect: <cr> <ctrl-M> and <0D>
Letters used in mnemonics are not case dependant.
Valid mnemonics for ASCII characters:
<nul> <null> <soh> <stx> <etx> <eot> <enq> <ack> <bel> <bs> <ht> <tab> <lf> <vt> <form> <cr> <so> <si> <dle> <dc1> <dc2> <dc3> <dc4> <nak> <syn> <sync> <etb> <can> <em> <sub> <esc> <fs> <gs> <rs> <us> <del> <csi>
Control characters can also be specified using a mnemonic containing ctrl- followed a character. For example to send a control C (0x03) use the mnemonic <ctrl-C>.
Characters can be specified using a mnemonic containing their hexadecimal value as a two-digit value. To send the character 'A' which has a hexadecimal code of 0x41 use the mnemonic <41>.
AniTa for the Web supports a wide range of macros. With the exception of the keyboard macros, these are compatible with those in the Windows version of AniTa. Macro names always start with a % and end with a %, for example %hangup%. A macro name may optionally be followed by some additional data, for example %connectto%www.april.se
Letters used in macro names are not case dependant.
Keyboard macros cause the value of a terminal specific key to be sent to the host. The keyboard macros available depend on the terminal type.
Keyboard macros available for DEC terminals such as VT220:
%backspace% %enter% %np_enter% %np_period% %np_comma% %np_minus% %np_0% %np_1% %np_2% %np_3% %np_4% %np_5% %np_6% %np_7% %np_8% %np_9% %F6% %F7% %F8% %F9% %F10% %F11% %F12% %F13% %F14% %F15_HELP% %F16_DO% %F17% %F18% %F19% %F20% %FIND% %INSERT% %REMOVE% %SELECT% %PREV_SCREEN% %NEXT_SCREEN% %UP% %DOWN% %RIGHT% %LEFT% %PF1% %PF2% %PF3% %PF4% %PF5% %F6_S% %F7_S% %F8_S% %F9_S% %F10_S% %F11_S% %F12_S% %F13_S% %F14_S% %F15_HELP_S% %F16_DO_S% %F17_S% %F18_S% %F19_S% %F20_S%
Keyboard macros available for ANSI terminals such as SCO Console:
%UP% %DOWN% %RIGHT% %LEFT% %F1% %F1_S% %F1_C% %F1_SC% %F2% %F2_S% %F2_C% %F2_SC% %F3% %F3_S% %F3_C% %F3_SC% %F4% %F4_S% %F4_C% %F4_SC% %F5% %F5_S% %F5_C% %F5_SC% %F6% %F6_S% %F6_C% %F6_SC% %F7% %F7_S% %F7_C% %F7_SC% %F8% %F8_S% %F8_C% %F8_SC% %F9% %F9_S% %F9_C% %F9_SC% %F10% %F10_S% %F10_C% %F10_SC% %F11% %F11_S% %F11_C% %F11_SC% %F12% %F12_S% %F12_C% %PGUP% %PGDN% %INS% %DEL% %HOME% %END% %NP_5% %BTAB%
Keyboard macros available for Wyse terminals such as Wyse60:
%INSCHAR% %INSLINE% %INS% %REPL% %PGDN% %PGUP% %END% %END_S% %DELLINE% %DELCHAR% %PRINT% %DEL% %DEL_S% %END% %END_S% %PGDN_S% %PGUP_S% %F1% %F2% %F3% %F4% %F5% %F6% %F7% %F8% %F9% %F10% %F11% %F12% %F13% %F14% %F15% %F16% %F1_S% %F2_S% %F3_S% %F4_S% %F5_S% %F6_S% %F7_S% %F8_S% %F9_S% %F10_S% %F11_S% %F12_S% %F13_S% %F14_S% %F15_S% %F16_S% %F1_C% %F2_C% %F3_C% %F4_C% %F5_C% %F6_C% %F7_C% %F8_C% %F9_C% %F10_C% %F11_C% %F12_C% %F13_C% %F14_C% %F15_C% %F16_C% %F1_SC% %F2_SC% %F3_SC% %F4_SC% %F5_SC% %F6_SC% %F7_SC% %F8_SC% %F9_SC% %F10_SC% %F11_SC% %F12_SC% %F13_SC% %F14_SC% %F15_SC% %F16_SC% %ESC% %ESC_S% %BTAB% %TAB% %BSPACE% %BSP_S% %RETURN% %RETUR_S% %HOME% %HOME_S% %UP% %UP_S% %DOWN% %DOWN_S% %LEFT% %LEFT_S% %RIGHT% %RIGHT_S% %ENTER% %ENTER_S% %SEND%
Once a configuration has been completed, it is possible to export it into an HTML file. The file format exported will contain both an <OBJECT> and an <EMBED> tag so that it works with both Internet Explorer and Netscape Navigator browsers. If the "Auto export to HTML on save" box is checked on the Web Information card, then the configuration will automatically be exported to the specified HTML file every time a save is performed.
Once a configuration has been completed, it is possible to export it for Java Web Start. This will create a JNLP file for Web Start and an AWS file for AniTa. If the "Auto export to JNLP on save" box is checked on the Web Start Information card, then the configuration will automatically be exported to the specified JNLP and AWS files every time a save is performed.
Existing users of AniTa for Windows can import their existing configuration (WCF and MAP) files into the configuration program to create a AniTa for the Web configuration (INI) file.
To determine how a key is mapped, click in the "Mapped keys" scroll box. Move the select marker up or down to find a specific key. The "Mapped keys" box shows one line for each mapped key. The line contains three parameters, the keycode, the shift code and the string to which the key is mapped. The key and shift codes will be translated and shown in the "Key Code", "Symbolic name" and shift "Combination" fields.
Note: Java does not allow the numeric keypad's Enter key to be mapped differently from the main keyboard's Enter key. These both have the same key code in Java.
The parameters on this page are used to export the configuration information from the configuration file into a web page that can be used to start AniTa as a Web Start application. If you do not plan to run AniTa via Web Start then you can ignore these parameters.
To run AniTa via the Web, just point the Web Browser at the anita.jnlp page, or set-up link to it and click.
The parameters on this page are used to export the configuration information from the configuration file into a web page that contains AniTa as an Applet. If you do not plan to run AniTa as an Applet in a Web Browser then you can ignore these parameters.
To run AniTa via the Web, just point the Web Browser at the anita.html page, or set-up link to it and click.
The first screen font page contains parameters that apply regardless of whether the terminal is in 80 character wide or 132 character wide mode.
There are two different font selection pages, one for when the terminal is in 80 character wide mode and the other for 132 character wide mode. The contain the same parameters. It is often desired to change to a smaller and/or narrower font when the terminal switches from a screen that is 80 to one which is 132 characters in width.
These parameters are used to control how an AniTa application's window is initially positioned on the screen. They only apply when running as an application. They can be ignored when running as an Applet; positioning is then performed by the HTML code in the Web Browser.
This dialog box determines how AniTa maps the different terminal screen attributes to colors. Selecting "Use Host Color" will disable AniTa's mapping of attributes to colors, this being especially useful if the host sets its own colors.
This dialog box determines how AniTa maps different colors to boxes. By default there are three types of boxes, an in-box and out-box and an edit-box. It is possible to add new box definitions.
A string can be configured for the different mouse actions. When the user performs a mouse action, the corresponding string will be sent to the host. The string may contain mnemonics and macros. There are special macros that only apply to mouse actions. An empty field will cause the specific action to be disabled.
This screen determines what action is taken when a disconnect occurs. Different actions can be specified depending on if it were the host or the client that caused the disconnect.
This screen controls the action performed by a screen dump. A screen dump action can be caused by the user clicking the Print button, or by executing the %printscreen% macro or by an escape sequence being sent from the host.
This screen controls the way that the emulator performs terminal printing. Terminal printing is when the host sends data directly to the clients printer. It is sometimes also referred to as pass-through printing.
Each of the three supported printers can be configued as Raw or GUI.
When Raw printing is configured, the print output is sent directly to the specified Printer Name. This can be set to the name of a printer device or the name of a spool file. An optional Printer Command can be specified; this will be executed upon completion of the print spooling.
An example of using the lpr command on a Linux PC to print your job:
Printer Name: spooler0.txt
Printer Command: lpr -Phplaserjet spooler0.txt
An example of using a device on a Windows PC to print your job:
Printer Name: \\SERVER1\HPLASERJET
Printer Command: blank
A special program, anitaprint.exe, is provide to spool print jobs on Windows platforms. Other platforms can use their standard spoolers (such as lp or lpr on Linux and Solaris).
If the Printer Name is preceed by a @ then the first line of that file is used to specify the print output filename.
When GUI printing is configured, the print output is interpreted in order to create a Java GUI page and then this page is sent to the printer. The control codes are a limited subset of HPPCL. A default format for the GUI page can be configured.
This screen controls the way that the emulator performs terminal GUI printing. It allows the user to configure the default format of the Java GUI page used for printing.
This screen controls the button panels above and below the AniTa terminal emulation window. You can configure a top button panel above the AniTa terminal screen and a bottom button panel below it.
There are two screens that configure the contents of the top and bottom button panels.
Note that a button without any icon or text values will create an empty space in the button panel.
This chapter describes some of the special functions when running the AniTa for the Web emulator.
This button is used to connect or disconnect
the session to the host. When connected it shows a green telephone and the text
"disconnect"; pressing will disconnect the session. When disconnected it shows a
red telephone and the text "connect"; pressing will connect to the host. When in
the process of connecting, it shows a yellow telephone and the text
"connecting"; pressing will have no effect.
This button is used to send the contents of the
terminal screen to the printer.
These buttons are used to copy data to and from
the clipboard. The copy button will copy data from the terminal screen to the
clipboard; it is only enabled when an aera of the screen has been marked with
the mouse. The paste button will paste data from the clipboard into the emulator
as if it had been entered on the keyboard and thus send it to the host; it is
only enabled when a session is active.
This button is used to start the AniTa for the Web
configuration program in a seperate Window. It is only enabled when running as
an application, and cannot be used when running from the web (either using Web
Start or as an applet). If the configuration file is changed, the terminal
emulator must be restarted for it to take effect.
Sometimes when a problem occurs running an
application in AniTa, the resolution can best be determined by creating a trace
file. This trace file contains the all communications between the host computer
and AniTa.
To record the communications in a trace file, press the record button. Enter the name of the file into which the session will be recorded; the default is janita.trc. The button will change to stop recording.
Connect to the host system and login. Start the application and reproduce the problem so that it appears on the screen.
Press the stop recording button. This trace file will contain all the characters and escape sequences sent by the host to AniTa and all the keyboard input sent by AniTa to the host.
If you are using this file to report a problem to
support, please send the AniTa configuration file "janita.ini" as well as the
"janita.trc" file. This will enable support staff to play back your recording,
using you same configuration and see the problem as it appears on your screen.
The Play button is used to play back a trace file.
A programmer's guide for AniTa for the Web which includes programming tips and AniTa specific escape sequences is provided as a seperate document: janitaprog.html.