Ozibug is a standard java 2.2 servlet which can be
run under different contexts (a context is the
first part of the path which identifies the servlet.)
This howto demonstrates how to run multiple instances
of the Ozibug application.
Note: there are not many cases where
you would need (or want) to do this, because you can
control data separation from within a single Ozibug
instance using the access control features.
However this document also demonstrates the configurability
of the Ozibug and is useful for this purpose alone.
Jakarta Tomcat will be used as the Web Container
in the examples.
It is assumed that this will be installed in a
directory referred to by the
TOMCAT_HOME variable.
It is also assumed that a suitable JDK is installed
in the directory referred to by the
JAVA_HOME variable.
We will install two Ozibug instances for imaginary
products called efish and echips.
Note: you will require a multi-instance
license to run more than one instance of the Ozibug servlet
within a Web Container.
Contact
info@tortuga.com.au
for further information on licensing.
Now we must configure Tomcat for the location
of the two servlet instances.
Add the following section of XML to the
TOMCAT_HOME/conf/server.xml file.
These sections should be contained within the already
existing <ContextManager></ContextManager>
section.
So far we have configured two instances of Ozibug
but apart from having different contexts (efish
& echips) they are still identical.
This might cause some confusion to any users or
administrators that have to use both systems.
There are two simple customizations that will help
to differentiate between the instances. The
system name as well as the header & body images can
be changed to reflect the ownership and/or purpose of
the Ozibug instance.
Refer to
User Interface Configuration Howto: System Name
and
User Interface Configuration Howto: Images
for details on how to change these attributes.
