Administering your HATS LE Application

The HATS LE Administrative Console enables the system administrator to view sessions initiated for your HATS LE application. The application server must be running when you administer your HATS LE application.

To get to the HATS LE Administrative Console, enter the following URL in your Web browser:

http://<servername>/HATSLE/admin

where <servername> is the name of the server machine where your HATS LE application runs.

The Administrative Console home page shows the status of the application. You can enable or disable your application from this panel. You can also see the number of active connections. This is the default page when you enter the Administrative Console. Selecting any of the three menu items on the left-hand side of the Administrative Console window will open the appropriate page on the right-hand side:

Configure

The Configure section allows the administrator to specify settings for the application (using the Configuration wizard). The Configuration wizard is launched in the left-hand side of the Administrative Console window. It lists multiple configured connections in a table which can be sorted.

Manage Connections

This page displays a list of the active sessions connected to your HATS application and allows the administrator to manage all active connections to the application. You can sort the list by any column by clicking the column header. You can shut down a connection that has a problem.

Advanced

The Advanced section allows the administrator to configure more advanced settings of the application. This includes:

Editing the application (.hap) or a connection (.hco) file
Configuring the Connection List settings (see Connection List for more information)
Adding, editing, exporting, or deleting a selected template
Packaging your application into a zip file which can then be imported into the HATS Studio (see Migration for more information)

You can export your HATS LE application to a zip file that can be imported to HATS. Visit the HATS Web site at http://www.ibm.com/software/webservers/hats to find out what level of HATS is required for importing your HATS LE application.

Clicking Home at any time returns you to the Administrative Console page.

Viewing client host names in HATS LE Administrative Console

In the Manage Sessions section of the Administrative Console, you can see the IP address of each client that is connected to your HATS LE application (to view, click a session ID from the list of active sessions). In cases when clients connect through the IBM HTTP Server, as opposed to accessing your HATS LE application directly on your application server, the Session Details dialog might show only the IP address, not the fully resolved host name. To see the client host name, open the httpd.conf file in your IBM HTTP Server "conf" directory and add or edit the following: HostnameLookups on. You will need to stop and restart your HTTP server for this change to take affect. This will instruct the HTTP server to do a DNS lookup on the client IP address and determine its host name.

Note:

Making this change will cause a slight performance degradation, because the HTTP server will have to resolve the IP address before passing the client's request to the application server.

Message logs and traces

When a HATS LE application runs in the WebSphere Application Server, logging and tracing is performed for the application. Logging and tracing is controlled by the settings of the runtime.properties file, in the root directory of HATS5LE.ear. In the drive and directory where you installed WebSphere Application Server, there is a folder named installedApps, which contains a folder named HATS5LE.ear.ear.

You can find your message log and trace files in the drive and directory where you installed WebSphere Application Server, They will be stored in the \HATS5LE.ear.ear\logs directory.

You can use a text editor to modify the runtime.properties file.

Note:

The runtime.properties file must be edited with an ASCII editor. This can be done by transferring the file to a workstation (example: via FTP), editing the file and transferring it back.

The runtime.properties file contains the following basic properties:

maxTraceFiles

The maximum number of trace information files. The default is 5.

The base trace file name in runtime.properties is used as a template to generate unique sets of trace files for each application server. The default base name for a trace file is trace.txt, which can be changed.

An index (1, 2, 3, and so forth) is added to this name to distinguish multiple trace files. When trace1.txt reaches maxTraceFileSize, it is closed and renamed to trace2.txt. A new trace1.txt file is opened.

When the maxTraceFiles number is exceeded, the oldest file is deleted.

The trace*.txt files are created in the HATSLE directory.

maxTraceFileSize

Specifies the maximum size, in kilobytes, that a trace file reaches before an additional trace file is opened.

The value is a decimal integer. The default is 1024 KB.

traceFile

The name used as a template to generate file names for each set of application server files to which trace messages are written. The default base name for a trace file is trace.txt .

maxLogFiles

The maximum number of message files. The default is 2.

The base message log file name in runtime.properties is used as a template to generate unique sets of message log files for each application server. The default base name for a log file is messages.txt , which can be changed.

An index (1, 2, 3, and so forth) is added to this name to distinguish multiple message log files. When messages1.txt reaches maxLogFileSize, it is closed and renamed to messages2.txt . A new messages1.txt file is opened.

When the maxLogFiles number is exceeded, the oldest file is deleted.

The messages*.txt files are created in the HATSLE directory.

maxLogFileSize

Specifies the maximum size, in kilobytes, that a message log file reaches before an additional log file is opened.

The value is a decimal integer. The default is 512 KB.

logFile

The name used as a template to generate file names for each set of application server files to which log messages are written. The default base name for a trace file is messages.txt .

Note:

Names of the properties are case-sensitive. Do not change the property name.

The runtime.properties file contains the following HATS LE application tracing properties:

trace.RUNTIME

Specifies the level of tracing for the main runtime and for all settings under RUNTIME.* that do not specify a trace level.