It is important to configure your attachments for high
availability, as they can be a critical feature of the product for
many organizations. You must configure a shared disk that can be accessed
by all of the application server and the HTTP server nodes in the
topology. The shared disk must also be highly available, so that
it does not become a point of failure.
About this task
You can use various methods to configure a highly available
file system that can be accessed by the HTTP server and application
server nodes. For example, you can use IP-based replication, local
mirroring, clustered network-attached storage (NAS), or clustered
storage area network (SAN). The file system solution must use a service
IP and common storage directories with replication, so that you can
mask the file system failover from the HTTP server and the application
server.
Procedure
- Mount the shared file system on all HTTP and application
server nodes. For Linux, an
automount utility such as AutoFS can assist with the mounting process. Windows systems can access the
shared directory through a Universal Naming Convention path.
- Allow read access to the shared directory for the user
who starts the HTTP server services. This user must be able to view
and retrieve files from the system.
- Allow read and write access to the shared directory for
the user who starts the WebSphere® Application
Server services.
- Configure the attachments in the application,
by using the shared file system path.