Common directories

All the Managed Servers in the cluster must be able to access the same directory locations in the file system: this is where configuration files, shared data files, and other related files such as pagination data is stored for the cluster. You must ensure that all members of the cluster access this location using the same directory paths.

The location of the shared directories is specified in the Visual Modeler web.xml file using context parameter elements of this form:


<context-param>
   <param-name>WritableDirectory.share.public.loadable</param-name>
   <param-value>/tmp</param-value>
</context-param>
<context-param>
   <param-name>WritableDirectory.share.public.noloadable
   </param-name>
   <param-value>/tmp</param-value>
</context-param>
<context-param>
   <param-name>WritableDirectory.share.private.loadable</param-name>
   <param-value>/tmp</param-value>
</context-param>
<context-param>
   <param-name>WritableDirectory.share.private.noloadable
   </param-name>
   <param-value>/tmp</param-value>
</context-param>

Note that by default, these elements are commented out: in this case, each instance of the Visual Modeler Web application acts independently of the other instances in the cluster. All file accesses are performed locally on the machine running the Web application.

The following table summarizes shared file locations:

Location Purpose
share.public.loadable Do not use.
share.public.noloadable Image files and other files that should be accessible to Web servers to serve up static content. Examples include GIF files associated with promotions and storefront partners.
share.private.loadable Class files to be shared across the cluster: this directory is used primarily for Sterling™ Omni-Configurator and Visual Modeler.
share.private.noloadable Configuration files, pagination files, and other files that must be shared across the cluster, but which should not be accessible from users' browsers.