NonStop Servlets for JavaServer Pages (NSJSP) 6.1 System Administrator's Guide

Configuring NSJSP
NonStop Servlets for JavaServer Pages (NSJSP) 6.1 System Administrator’s Guide—596210-006
3-34
The filemaps.config File
The filemaps.config file is only meant to contain Filemap definitions for specific
user applications. The default Filemap definitions for the overall NSJSP installation
are in the servlet.config and nsjspadmin.config files.
Example 3-41 illustrates the usage of the filemaps.config file for specific user
application Filemap definitions.
Example 3-41. Specific User Application Filemap Definitions
Consider an installation with a URI name of /dev running an application foo.war. By
default, the application can be accessed over the URL
http://<ipaddress:port>/dev/foo and the full application context path will be
/dev/foo. There might be situations where the application context and thus the URL
used to access the application along with the application cannot include the URI name
prefix. In that case, the URL to access the application would be
http://<ipaddress:port>/foo and the full application context path is /foo. The
filemaps.config file is used to achieve this objective and it can be achieved in one
the following ways:

By deploying the application through the NSJSP manager and indicating that the
context name should not have the default URI name prefix. In this case, the NSJSP
manager deploys the application without the default URI name prefix (in this case
/dev) and then makes an entry in the filemaps.config file for the
application context name /foo. The entry in the filemaps.config for the
application context name /foo, ensures that the configuration is retained
across server class restarts.

By manually making a Filemap entry in the filemaps.config file. If the
application is deployed manually by copying the war file to the webapps directory,
then a Filemap entry must be made in the filemaps.config file, manually. In
this example, the entry in the filemaps.config file should be Filemap /foo
$server_objectcode. The $server_objectcode variable can also be
replaced by the full path to the ssc file for this serverclass. For more information on
server_objectcode, see server_objectcode
on page 3-11.
The TANDEM_FILEMAPS_CONFIG environment variable must specify the fully qualified
location of filemaps.config file. The NSJSP servlet container reads the file identified
by this environment variable during startup and decides the correct context path for the
applications. For example, if there is an entry Filemap /foo $server_objectcode
in the filemaps.config and an application foo.war is being deployed, the NSJSP
servlet container will not prefix the URI name (/dev) to the context name (/foo) of the
application.