Configuring LogWeb/Ajax

Overview

As is shown by the installation, LogWeb/Ajax is a fully Internet-capable client/server system. The system is based on the latest Internet technology and is independent of server-side and client-side operating systems:

• The server side is a pure-Java Web application.
• The client side is a pure browser application.
• The communication between client and server is standard http or https.

For the configuration, this means the following:

• You perform all tasks on the server side only.
• If required for your implementation, you centrally customize the basic configuration for the client on the server.
  Your customizations are then saved in the custom directory of the server.
• Users can configure clients individually (for example, "Edit Color Scheme") without your assistance by using the corresponding menus if you do not prohibit this in your customizations.
• User settings are saved in cookies on the client system.
  During the initial system start (or if cookies are blocked), your custom settings are used.

You also use the basic system that you typically use and configure; this particularly applies to the servlet containers that you implement. You can find descriptions of these with the corresponding company, for example, Tomcat.
For configuring Apache and Tomcat, we have listed special tips that you can also apply to other products accordingly.

We wish you much success in installing, configuring, and operating LogWeb/Ajax, and we will support you as much as possible in your efforts.

User administration

Through user administration, you group together users with the same profile of requirements, such as "administrators", "internal users" or "external users", and you assign them rights, such as "may save files on the server".

An "empty user administration service" comes standard and is already preconfigured; you can use this without any modification for initial tests:

• Users do not need to enter a user name when logging in. These users are automatically logged in as "default" users in the "default" group.
• All users can save data on the server. The (global) user directoryuserdb/data/userdata/default is used for this purpose.
• In addition, an "admin" user in the "admin" group is set up with special rights.
• The group directory userdb/data/groupdata/admin already contains prepared demo connectivity files.

For productive use, you have the following options:

• If you have no special requirements, you can continue to use the empty user administration service provided.
• If required, you can simply customize this accordingly by entering the needed users and groups.
• If you already use LOG-WEB user administration, you can select this and continue to use it unmodified.
• If you are already use another user administration service, for example, through portal integration or services such as LDAP and ActiveDirectory, you can integrate the service here.

File system

The client/server file system provides users with user-specific and group-specific areas on the server and manages their configurations according to priority:

• The basic configuration provided: config (lowest priority)
• Your global customization in the custom directory: //CustomData
  Contains only the files that you used from the basic configuration and are customized according to your company-specific implementation.
• Group-specific customizations: //GroupData/GROUP
  Each group directory contains only the files that you have specifically customized for each user group.
• User-specific customizations: //UserData/USER (highest priority)
  Users typically save their own settings and templates in their individual user directories.

The integrated cache-system enables fast access to the configurations.

Although all configuration directories are created to correspond with the basic configuration provided, these directories only contain data customized by individual users. Except for the basic configuration, all directories can be either missing or empty; these directories are then automatically created.

The standard package contains a preconfigured "empty file system" that you can use without modification for initial tests.

For productive use, you only need to specify the paths for your own data area.

Connection templates

To ensure that users can access the shared host applications, you define the required parameters (for example, IP addresses) in connection templates:

• Each connection template describes a mainframe or UNIX connection.
  The templates usually contain all parameters required for these connections but can be extended to contain user-specific values, such as user name or LU name.
• You can create connection templates either for all users or for a single user group.
  The templates are found in the directories
  • //CustomData/_login (for all users) or
  • //GroupData/GROUP/_login (for the corresponding user group)
• A "wizard" supports you in creating and editing connection templates. In the process, an INI file is generated using your parameters.

The standard distribution contains only "offline templates" for the "short test" that you can perform as an admin user. These templates are found in the directory

userdb/data/groupdata/admin/_login

of the preconfigured file system.

After the installation, you must create the connection templates to your own host systems.

Custom configuration

• Users can typically specify the behavior of the emulation window themselves. However, you can also specify or restrict the behavior in basic settings.
• You can customize startup behavior of the terminal emulation using auto-start macros.
• You can customize terminal-specific settings such as menu system, toolbar, keyboard configuration, and mouse actions and define them in templates.
• You can make special login customizations so that, for example, the local environment of the client computer is evaluated upon startup, or so that the global layout of the terminal emulation is customized and and integrated in your own portal site.
• For special tasks, you can modify both documents and print data before sending them to the client.

Configuration file WEB-INF/ajax.ini

The configuration file ajax.ini comes standard and is already preconfigured; you can use this without modification for initial tests.

For productive use, you need to modify the parameters for user administration and the file system to meet your requirements more precisely.

If you also want to allow the "Park Session" function in a UNIX connection template, the cache parameters specified here may not be sufficient; in this case, you can increase these parameters:

• VTCacheStartup = 10000 (startup cache)
• VTCache = 10000 (running cache size)

Restricting access: WEB-INF/web.xml

After completing your work, you need to either delete all functions that are critical for your implementation or protect these functions with a password by making entries in the configuration file web.xml:

<!-- ================================================= -->
<!-- protect administrative JSPs                       -->
<!-- uncomment the security-constraint below           -->
<!-- to protect critical pages:                        -->
<!-- admin session hook, all admin/, log evaluation... -->
<!-- ================================================= -->
<!--
<security-constraint>
	<display-name>Administrator JSP</display-name>
	<web-resource-collection>
		<web-resource-name>AdminPage</web-resource-name>
		<description>The administrative JSPs</description>
		<url-pattern>/admin/*</url-pattern>
		<url-pattern>/login/showSession.jsp</url-pattern>
		...
		<http-method>GET</http-method>
		<http-method>POST</http-method>
	</web-resource-collection>
	<auth-constraint>
		<role-name>manager</role-name>
	</auth-constraint>
</security-constraint>
-->

Note

• Before system operation, we recommend that you save all path parameters on directories that are outside of the Web application; this enables easier updates and backups in the future.
• Changes made directly to the files and directories are only applied after the Web application is restarted.