Installation tests

Overview

After installation, you must always perform the following test. As a result, you will become familiar with the structure and operation of LogWeb/Ajax and will be able to better assess which settings are suitable for your specific implementation.

LogWeb/Ajax URLs

LogWeb/Ajax is always called up in the browser with a URL. The basic URL of the installed application depends on your system environment:

Example 1 - Stand-alone servlet container:

• Your servlet container (for example, Tomcat) is accessible directly over the port 8084 on the test computer in your network myname.com
• You have installed the war file under the name (or the context root) ajax.
• The default welcome page is then accessible under

  http://test.myname.com:8084/ajax
  

Example 2 - Servlet container with front-end Web server:

• You have installed an HTTP server, such as Apache, under www.myname.com, and configured a router to your servlet container under /tomcat.
• You have installed the war file under the name (or the context root) ajax.
• The default welcome page is then accessible at

  http://www.myname.com/tomcat/ajax
  

If you only enter this basic URL in the browser, the login page for starting a session is displayed.

Within LogWeb/Ajax, the following paths are defined:

• ajax: If you do not enter a path, you are automatically directed to the login page ajax/login.
• ajax/login: You directly access the login page.
• ajax/help: The help page is displayed.
• ajax/admin: A page providing administrative functions is displayed.
  During the configuration, you usually restrict access to all pages of this directory.

Offline tests

To check the installation, you first need to perform offline tests:

• During offline tests, there is no connection to a real host system.
• Instead, prepared session files (trace files) are used that were originally logged during an online host session.
• Every time you start a "transmission to the simulated host", the next host response which was originally logged is displayed instead.
• This display occurs independently of your actual inputs, which can occasionally be confusing.

The purpose of offline tests is primarily to test for proper installation and the interworking of all the required components. However, you can also use the offline tests to familiarize yourself with LogWeb/Ajax and the corresponding terminal types as well as test specific settings without risk.

How to proceed:

• In the browser, enter the URL of the home page: ..ajax
• When the login page is displayed, log in as admin and leave the password field empty; then click "login".
• In the lower area on the home page, the prepared offline connections are listed. Select the corresponding test, for example: "3270 Offline demo" or "Unix Offline demo".
• The terminal emulation is displayed in a new browser window.
• Using Help on the menu bar, you get general advice about operating the terminal emulation.
• Note:
  • With UNIX terminals, data is transferred each time you press a key.
  • With mainframe terminals, normal text input or cursor movements are performed locally in the browser and are immediately shown on the screen; data transfers are performed only when you press one of the F keys on the computer, for example.
• Every time you trigger a data transfer, the data is transferred to the server. With offline tests, however, only the host responses are displayed that were previously logged previously, regardless of your actual input.

You can always end the terminal emulation by selecting Session/Terminate Session, or simply by closing the browser window.

Online tests

Required information:

For online tests with your host systems, you must first enter the minimum information for access in "connection templates":

• IP address of the host system
• Port number of the host system

Depending on your host application, further information can be required such as:

• Terminal type
• Station name

The connection wizard supports you when creating and editing these templates.

For initial tests with your host applications, you require the usual access data, such as:

• Login ID
• Password

and basic knowledge of how to use your applications.

Frequently, access over the LogWeb/Ajax server must be specifically granted on the host.

You therefore need to coordinate your tests with your host system administrators.

Starting the connection wizard:

• In the browser, enter the URL of the administrator start page: ..ajax/admin.
  Note that all administrator pages are usually protected with a password after the configuration is completed.
• Select Connection Wizard to start the connection wizard.

Creating a connection template:

• Select "Create a new connection" and then click "Next >".
• Select your "Connection Type", for example, "xterm/VT Connection to Unix" or "5250 Connection to IBM AS/400" and then click "Next >".
• Select the users for which the new connection is intended; for your tests, enter "All Groups".
  You can add the file name and the description for the new connection; then click "Next >".
• Enter the IP address, the port number and the log, if necessary, under which your host system is accessible and then click "Next >".
• Depending on your application, you must make further settings, for example, for the "Terminal Type", "Character Set" or "Station Name". Then, click "Next >".
• For the test connection, you can skip the parameters that follow. Click "Next >", until you have finished editing the template.
• Now save the template and exit the connection wizard.

Starting a host connection:

• In the browser, enter the URL of the start page: ..ajax.
• When the login page is displayed, log in as admin and leave the password field empty; then click "login".
• In the lower area on the start page, the connection which you have just created is listed. Select it.
• The terminal emulation is displayed in a new browser window.
• Using Help on the menu bar, you get general advice about using the terminal emulation.

Further steps depend on your host application; usually, you must login first there (host login).

You can always end the terminal emulation by selecting Session/Terminate Session, or by simply closing the browser window.