Previous | OpenFusion Graphical Tools | Next |
It is possible to deploy the Java Tomcat Web server within an OpenFusion installation. The Tomcat server is used by the OpenFusion SOAP Bridge, as described in the Messaging Bridges Guide.
Tomcat is deployed as an embedded server and can be configured as a Java Object. As such, it can be deployed as a separate service or co-located with another OpenFusion service. See Adding Singletons and Java Objects for details of deploying Java Objects in an OpenFusion installation.
See http://jakarta.apache.org/ for further details of the Tomcat Web server.
Each configured Tomcat object has its own webapps directory created within the configuration directory hierarchy. In addition, a global webapps directory is maintained at the root level of the OpenFusion installation.
By default, the ROOT Web archive file (ROOT.war) is deployed into every configured Tomcat instance. Additional Web archive files can be deployed by one of the following methods:
The Tomcat Web server has a security manager enabled by default. This uses the following security policy file:
<INSTALL>/etc/tomcat.policy
where <INSTALL> is the OpenFusion installation directory.
If more fine-grain security control is required, the file can be copied into the Tomcat home directory and edited as appropriate. The Tomcat Security Policy File property is used to locate this file.
In order to deploy your own Java Server Pages (JSPs) in the Tomcat Web server, a .jar file containing a Java compiler must be included in the CLASSPATH.
JSPs supplied with the OpenFusion CORBA Services distribution are pre-compiled and deployed within a .war file and therefore do not need access to a Java compiler.
The following properties can be configured through the GUI manager for each embedded Tomcat object.
The home directory of the Tomcat server. This defaults to the configuration directory for the Tomcat Java Object:
<INSTALL>/domains/<domain>/<node>/<service>/TomcatObject/
where <INSTALL> is the OpenFusion CORBA Services installation directory. See The Object Hierarchy for details of the domains directory structure.
The Tomcat work directory. This defaults to the work directory under the default Tomcat home directory:
<INSTALL>/domains/<domain>/<node>/<service>/TomcatObject/work
where <INSTALL> is the OpenFusion CORBA Services installation directory. See The Object Hierarchy for details of the domains directory structure.
This property is independent of the Tomcat Home Directory property and does not change if Tomcat Home Directory is changed.
The directory into which Tomcat deploys Web archive files. This defaults to the webapps directory under the default Tomcat home directory:
<INSTALL>/domains/<domain>/<node>/<service>/TomcatObject/webapps
where <INSTALL> is the OpenFusion CORBA Services installation directory. See The Object Hierarchy for details of the domains directory structure.
This property is independent of the Tomcat Home Directory property and does not change if Tomcat Home Directory is changed.
A colon-separated list of Web archive files to be deployed from the global webapps directory into the Tomcat WAR directory.
The ROOT.war file is always deployed and does not have to be included in the list.
The full path and name of the file which defines the security policies used by the Tomcat security manager. This defaults to:
<INSTALL>/etc/tomcat.policy
where <INSTALL> is the OpenFusion CORBA Services installation directory.
The port on which the Tomcat server listens for http requests. The default is 8080, but if this port in use by any other Web server deployed on the same system, a different port must be selected.
This property should be checked (TRUE) if the Tomcat Object will be used to serve up the files used for remote system configuration. The default value for this property is TRUE. See Distributed Installation Configuration, for more details of remote system configuration.
The directory that will be served up by the Tomcat Object. To allow remote system configuration, this should be the OpenFusion installation directory (which is the default value for the property). The directory should be specified as a URL of type file://.
This directory will be served up when a Web browser is used to access the following URL:
http://<server>:<port>/<context>
server is the machine which is running the Tomcat Object.
port is the port that Tomcat listens on, specified in the Tomcat Port property.
context is the path specified in the Context Path property.
If the directory contains a file called index.html, that file is returned to the browser. If index.html does not exist, a directory listing is returned instead.
This property is only enabled if the Serve Root URL property is checked.
The virtual directory that will be served up by the Tomcat Object. This defaults to the name of the Service that the Tomcat Object is a part of. See the Root URL property for details of how this property can be used.
This property is only enabled if the Serve Root URL property is checked.
Once the service containing the Tomcat Java Object has been started, the Tomcat deployment can be tested by attempting to connect to the default Web page. To connect to the default page, type the following into the address bar of a Web browser:
http://<server>:<port>
where <server> is the name of the machine running the Tomcat server and <port> is the port number specified in the Tomcat Port property (8080 by default).
If the server is working correctly, the Web page illustrated will be displayed.
Previous | OpenFusion Graphical Tools | Next |