Software AG Common Tomcat Kit 8.0 SP3 Readme May 2010 _________________________________________________________________ Contents


17 Νοε 2013 (πριν από 3 χρόνια και 6 μήνες)

958 εμφανίσεις

Software AG Common Tomcat Kit 8.0 SP3 Readme

May 2010


1.0 Overview
2.0 Installation
3.0 Uninstalling the Package
4.0 Start / Stop Commands
5.0 Installation Locations
5.1 Windows
5.2 UNIX
6.0 CTP Configuration Files
7.0 SSL Configuration
7.1 Defining a General HTTPs Connector
7.2 Client Side Modifications
8.0 Dependencies
9.0 Viewing the Documentation
10.0 Copyright Information
11.0 Support

1.0 Overview

The Common Tomcat Kit is based on Tomcat 5.5.28 technology.
Configuration files are installed in two locations:
- C:\Documents and Settings\All Users\Application Data\Software
AG\Tomcat and
- C:\Program Files\Software AG\Tomcat.
In contrast to the CTP, the Apache Tomcat distribution installs
the config files at one location: C:\apache-tomcat-<ver. no.>\bin
The Tomcat Kit includes the following functionality:
- AJAX infrastructure for creation and deployment of advanced
web applications, such as the Software AG Application Designer
- AJAX pluggable web application (framework) based
on CIS (CUP). New web applications are just plug-ins, well
integrated in the same UI, using "Eclipse like" concepts, such
as perspectives and plug-in aggregation.
- Includes ready to use Security Infrastructure.
- Uses JAAS LoginModules and SSX (Security eXtension).
- Ready configured for OS dependant usage.
- Interfaces for advanced customization CentraSite LDAP.
- Includes Tamino API for Java (used by Tamino/CentraSite apps).

2.0 Installation

There are two ways of delivering the Common Tomcat Kit:
- webMethods Installer distribution.
Refer to webMethods Installer for details on installation,
uninstallation, and software and hardware requirements.
- Digital media distribution.
Refer to the "Installation" chapter of the System Management
online documentation at for
details on installation, uninstallation, upgrade, and software
and hardware requirements.
All the information on installation and uninstallation in this
readme refers to the digital media distribution of the Common
Tomcat Kit.

3.0 Uninstalling the Package

To uninstall the Common Tomcat Kit properly, you must uninstall
the System Management Hub product. For details on the
uninstallation procedure, refer to the SMH documentation at

4.0 Start / Stop Commands

- On Windows systems: Use the services control panel to start and
stop the "Software AG Common Tomcat Service".
- On Unix systems: Use the script '' with arguments 'start'
or 'stop'.

5.0 Installation Locations

5.1 Windows
- Static program data:
%ProgramFiles%\Software AG\Tomcat\<VERSION>
- Dynamic program data including all web applications%Documents
and Settings%\All Users\Application Data\Software
- Logging:
%Documents and Settings%\All Users\Application Data\Software
AG\log\Tomcat \<VERSION>
- Configuration%Documents and Settings%\All Users\Application
Data\Software AG\Tomcat\<VERSION>\conf

5.2 UNIX
Files located at $CTPDIR/$CTPVERS:
opt/ static program data
var/ dynamic program data including all
web applications
var/opt/bin/ start/stop script (called by
runlevel boot scripts)
log/ logging
conf/ configuration

Files located at /etc/init.d (Solaris, Linux), /etc (AIX) or
/sbin/init.d (HP-UX):
sagNNctp80 runlevel boot script (N = any digit)

6.0 CTP Configuration Files

- The conf/server.xml file defines the Tomcat HTTP Port (default:
49981) and the Tomcat Shutdown Port(default:49993).
- The conf/urm_config.xml file is the SAG URM configuration file.
- The log4j.xml file is logging pluggable UI framework including
CIS and all plug-ins. It defines logging, install locations,
the start and stop commands. The directory path is

7.0 SSL Configuration

To protect passwords transmitted in clear text between a browser
and applications running on the application server, for example,
Tomcat, it is recommended to protect the communication with the
application server through the use of SSL. General instructions
on how to protect a Tomcat 5.x can be found at

Important: In a production environment, the use of self-signed
certificates is discouraged. Consider a PKI solution,
particularly in a multi-server setup.

7.1 Defining a General HTTPs Connector

With the installation of the Tomcat Kit, the server.xml file is
installed in the Tomcat conf directory.

The keystore is named "localhost_dont_use_in_production.jks" and
the password is "change_this_password". In the server.xml file,
an HTTPS connector is defined for port 49982.

Important: Do not use the supplied sample keystore for production
purposes! It is supplied only for instruction
purposes! You must acquire and provide your own server
certificate and define its location with the parameter
keystoreFile (replace the default value).

Note: The CN of the certificate needs to be identical to the
URL the server is addressed under, without the
"https://". For example, for a server reachable under
https://MyWebServer:8443/, the CN needs to

Tomcat supports both Java keystores (keystoreType="JKS" is the
default), and PKCS#12 keystores (keystoreType="PKCS12").

Set the keystore password accordingly (parameter keystorePass).

If you want to use client authentication, set clientAuth="true",
and supply a truststore that is a keystore containing the
certificate chain and trust root for those client certificates
you want to allow access for.

If the HTTPS connector is defined, then you should also have
a redirectPort="49982" as part of the non-HTTPS connector.

7.2 Client Side Modifications

On the client side, you are asked by the browser if you want to
trust the certificate. If you want to avoid this question, you
can import the server certificate, or in the case of a PKI,
preferably the CA certificate that has issued the server
certificate, into you browser truststore.

If you are accessing UDDI from a Java client using Sun JSSE, you
also have to set a truststore via<your_trust_store_here>

For details, see the JSSE documentation.

8.0 Dependencies

The Tomcat Kit depends on the Common Java Package (CJP). When CTP
is selected in the installation tree the CJP gets
selected automatically. If the target machine has CJP installed,
then Tomcat checks the version of CJP and updates it.

The Tomcat Kit can also be installed as part of a product's
installation. In this scenario the dependancies are handled
automatically as well.

Tomcat cannot be uninstalled if the target machine has installed
System Management Hub.

For more information about the installation of the Common Tomcat
Kit and System Management Hub, see the System Management Hub
documentation at

9.0 Viewing the Documentation

System Management Hub documentation is contained in the
distribution and installed in the doc folder in the installation
root directory.

You can browse the documentation by opening overview.htm with an
InternetBrowser. You can also view the documentation online at

10.0 Copyright Information

Copyright © 2010 Software AG, Darmstadt, Germany and/or Software
AG USA, Inc., Reston, VA, United States of America, and/or their

The name Software AG, webMethods, and all Software AG product
names are either trademarks or registered trademarks of Software
AG and/or Software AG USA, Inc. and/or their licensors. Other
company and product names mentioned herein may be trademarks of
their respective owners.

Use of this software is subject to adherence to Software AG’s
licensing conditions and terms. These terms are part of the
product documentation, located at and/or in the root
installation directory of the licensed product(s).

This software may include portions of third-party products. For
third-party copyright notices and license terms, please refer to
"License Texts, Copyright Notices, and Disclaimers of Third Party
Products." This document is part of the product documentation,
located at and/or in
the root installation directory of the licensed product(s).

11.0 Support

To obtain support for webMethods Product Suite components, refer
to the following resources:

Empower Product Support Web site
Visit the Empower Web site at to
learn about support policies and critical alerts, read technical
articles and papers, download products, fixes, and service packs,
submit feature/enhancement requests, and more.

Software AG Developer Community for webMethods
Visit the Software AG Developer Community at to
access additional articles, demos, and tutorials, technical
information, useful resources, online discussion forums, and