The
applet is for those people that provide
terminal based services and would like to
add web capabilities to it. The applet is the perfect way to make the transition from a terminal based system to a more sophisticated web based framework easier. To bring the terminal based application on the web one need to allow telnet or ssh access to it (which usually already exists) and then set up the Applet on a page on their web server. A second interesting usage is to set the applet up on your private home page and use it to be able to log in from remote locations without the need for any communication programs except a Java capable web browser.
QuickstartTo quickly have the applet up and running following the steps below:
- Save the
jta26.jar file into a directory on your web server.
- Create a html file: Make sure it looks like the following piece of HTML text:
<html>
<body>
<applet CODEBASE="."
ARCHIVE="jta26.jar"
CODE="de.mud.jta.Applet"
WIDTH=590 HEIGHT=360>
<param name="config" value="applet.conf">
</applet>
</body>
</html>
- Verify that all files (html and jar) are readable for all users, so that the web server can handle them.
- Load the web page from your web server. It should load the applet and prompt you with your web server login.
If you have a problem check the files again and have a look at the
Java console of your web browser to find out what the problem is. In case you still do not understand what is going wrong have a look at our FAQ and next write to us, but include a copy of your java console contents.
Configuring the AppletThe Applet loads default configuration options from a file called
default.conf which is contained in the
jta26.jar file. You can place your own configuration file
applet.conf in the same directory as the html page.
The following parameters apply for the applet:| Name | Value | Comment |
|---|
| config | configuration file | The parameter points to the configuration file for the applet. It may be either a path relative to the CODEBASE or a fully qualified URL. |
| Applet.detach | true or false | Detach the actual terminal display and its components from the browser window and run in a separate window. Use with care. The boolean value may either be true or false. See below! |
| Applet.detach.fullscreen | true or false | When detaching make the resulting window fill the whole screen. This might be useful for systems where people have to remote login and should get the biggest font that is possible on their screen. |
| Applet.detach.title | title string | Sets the window title of the detached applet. |
| Applet.disconnect | true or false | If set to true, the applet will disconnect from the remote host if you leave the web page. If false, the applet will stay connected and allows the user to continue the session. |
| Applet.disconnect.closeWindow | true or false | Closes the detached window if the connection is lost. If you want to disable this feature set it to false. |
| Applet.detach.immediately | true or false | This parameter is usually set to false and determines if the applet should detach immediately and run if set to true or simply display the button and wait until it is pressed if false. |
| Applet.detach.startText | text | Set this parameter if you want to use a start button to detach the applet. The default value is "Connect". |
| Applet.detach.stopText | text | The value set here will appear as the label of the button if the applet is in detached mode and running. The default value is "Disconnect". |
| Applet.detach.menuBar | true or false | Use this parameter if you want to disable the menubar in a detached applet. Usually that menubar is visible in a detached window but can be removed setting this parameter to false. |
Important: Any configuration options you can specify in the configuration file (
applet.conf or
default.conf) can also appear as an applet's tag:
<PARAM NAME="parameter" VALUE="value">
The only drawback is, before a PARAM is recognized a default value of that parameter
must have appeared in one of the configuration files!