Installing LogWeb/Ajax

Overview: LogWeb/Ajax

LogWeb/Ajax is a client/server application. The application is based on the latest Internet technology and independent from the operating system on the server side and client side:

The advantages of the client/server architecture are fully used, for example:

Most importantly, our 30 years of experience in this critical environment guarantees:

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

Standard system environments

We use the following standard system environments for testing:

In further descriptions, we assume that you have already installed the required standard software on the server side and configured the software for your specific requirements.
For configuring Apache and Tomcat, we have listed only special tips that you can also apply to other products accordingly.

Installation

LogWeb/Ajax is delivered as a complete Web Archive (WAR). The Web archive consists of a single file ajax.war and contains:

During installation, you only need to publish the war file in your servlet container. The process is the same as for typical deployments; for more details, see the documentation for your servlet container.

License file WEB-INF/license.ini

If you have received the license file license.ini, copy the file in the directory WEB-INF. Without a license file, the availability of the application is restricted (scope of functions and expiry date).

Installation tests

We strongly recommend that you perform installation tests after the installation:

You usually work together with your host administrators during the online tests. The connection templates that you generate during these tests can be used later.

Further steps

For initial tests with your host applications, use the connection templates, that you used for the first online test. LogWeb/Ajax comes preconfigured; you therefore do not need to make further adjustments.

Further steps in the process mainly depend on other factors of your system environment and host applications (as well as the ease of use that you want to provide your users). For example, you frequently need to make specific entries for the host printer ("printer LU name"), which you can usually specify in the connection templates or in user administration.

As soon as you have an overview of what LogWeb/Ajax provides by default, you can make further customizations for your specific implementation:

You must perform the following steps before productive use:

We will be pleased to assist and support you with the configuration and any required customizations.

Important for updates

If you have customized the LogWeb/Ajax configuration files during the installation, you need to note the following:

From experience, we recommend the following procedure:

In general, we recommend that you also compare the previous configuration files that you applied with the corresponding files delivered in the update version, otherwise you may be unable to use new functions. This especially applies to the custom configuration that you reference using 

CustomData = XXXX

in the central configuration file WEB-INF/ajax.ini.

Notes on the update to Ajax 3 with WebSpool

New parameters are included in the configuration file WEB-INF/ajax.ini. If you want to keep your latest configuration you must apply these parameters to your latest ajax.ini and modify the values to meet your needs if required.

Starting from Ajax version 3.1.5, the printer connection does not need to be configured separately in the Apache Web server or Tomcat and can be removed from the corresponding configurations.

With Tomcat, you can delete the printer connection by deleting the following entries (if available):

In conf/server.xml:

<!-- Support of static contents of LogWeb; similar to a real web server.
 The base directory is appBase (see above)
 -->
 < Context path="/logwebhtml" docBase="../../../logweb/html" />

In conf/web.xml:

<servlet>
	<servlet-name>logweb-CGI</servlet-name>
	<servlet-class>org.apache.catalina.servlets.CGIServlet</servlet-class>
	...
</servlet>

<servlet-mapping>
	<servlet-name>logweb-CGI</servlet-name>
	<url-pattern>/logwebcgi/*</url-pattern>
></servlet-mapping>

Before doing this, you need to stop and restart the application server.

In the Apache Web server configuration, delete the settings for the printer connection only if you are not using LogWeb and Ajax simultaneously.
If you want to remove the settings, search in the Apache configuration files (usually httpd.conf) for logwebhtml and logwebcgi. The entries are either

Alias /logwebhtml "<directory>"

or

ScriptAlias /logwebcgi "<directory>"

or

ProxyPass /logwebcgi "<directory>"
ProxyPassReverse /logwebcgi "<directory>"

In this case, <directory> is the LogWeb installation directory with the subdirectory logwebcgi or logwebhtml.

In the first two cases, the Apache Web server is used as a normal Web server; in the last case, Apache is used as an HTTP proxy server.

For each Alias and ScriptAlias entry, there is a <Directory> section. 

<Directory "<directory>"
	...
</Directory>

Delete the Directory section and the Alias or ScriptAlias lines.

In the case of a HTTP proxy server, delete all entries with ProxyPass and ProxyPassReverse that contain the text logwebcgi.

Notes on updating from version 2

Note the following points in particular when updating from version 2:

© Logics Software 2006 - 2009