Note: Tasks in this section
are required only if you are changing the location of your GDS directory
on the system you plan to upgrade to LiveCycle.
The global document storage (GDS) directory is used to store
long-lived files that are used within a process as well as critical
LiveCycle product components. The lifetime of long-lived files is
intended to span multiple restarts of a LiveCycle system, and can
span days and even years. These files may include PDF files, policies,
or form templates.
Long-lived
files are a critical part of the overall state of many LiveCycle
deployments. If some or all long-lived documents are lost or corrupted,
the existing LiveCycle server may become unstable and unusable for
an upgrade. Input documents for asynchronous job invocation are
also stored in the GDS directory and must be available in order
to process requests.
You
must create the GDS directory before you initialize the LiveCycle
database. See 3.5.1 Location of the global document storage directory for information.
You
can reuse the existing GDS directory or copy it’s contents to a
new location.
On
cluster configurations, create a shared file system for the GDS
directory on any computer that is accessible by each node in the
LiveCycle cluster, and ensure that all nodes of the cluster have
read and write permissions for the directory.
On
cluster configurations, you must specify the shared directory that
you create for GDS. You cannot use the default location in a cluster
environment.
Note: Create a shared file
system for the GDS directory on any computer that is accessible
by each node in the LiveCycle cluster, and ensure that all nodes
of the cluster have read and write permissions for the directory.
3.5.1 Location of the global document storage directory
You configure the location of your GDS directory with Configuration
Manager after you install LiveCycle. The GDS directory you specify
should be highly available and should have low access time to enhance
performance. If the GDS directory is on a shared network drive,
it is recommended that you specify the location as \\computer_name\GDS.
If
you changed the GDS location while installing LiveCycle, you can
determine the location of the directory as follows:
Log in to LiveCycle Administration Console and click Settings
> Core System Settings > Configurations.
Note the location that is specified in the Global Document
Storage Directory box.
If you must change the GDS directory location after completing
the installation (see LiveCycle Administration Help), you
should plan an appropriate location for the GDS directory.
Important: Module deployment will fail on Windows
if the GDS directory is at the drive root (for example, D:\). For
GDS, you must make sure that the directory is not located at the
root of the drive but is located in a subdirectory. For example,
the directory should be D:\GDS and not simply D:\.
3.5.2 Sizing factors for the global document storage directory
The size of the global document storage directory depends
on expected LiveCycle usage factors for the deployment. You should
allocate a minimum of 10 GB of disk space for the GDS directory.
While
upgrading to LiveCycle from a previous version of LiveCycle, you
must factor in the existing GDS data while allocating space for
the GDS directory. This actual size required for the GDS directory
may be in excess of 10 GB.
The following factors also affect the sizing:
The typical volume of documents that LiveCycle processes.
Processing high volumes of documents requires a larger GDS directory.
The typical size of documents that LiveCycle processes. Processing
large documents requires a larger shared GDS directory.
The complexity of documents that LiveCycle processes. Processing
complex documents, such as documents that are processed by multiple
services that are part of LiveCycle, require a larger GDS directory.
On
cluster configurations, in addition, documents that are processed
by different members of the cluster require a larger GDS directory.
3.5.3 Securing the global document storage directory
Access to the GDS directory must be secure. The long-lived
documents in this directory may contain sensitive user information,
such as information that requires special credentials when accessed
by using the LiveCycle SDK or user interfaces.
Use a security method that is appropriate to your operating system.
It is recommended that only the operating system account that is
used to run the application server has read and write access to
this directory.
Note: Deleting files or directories from the GDS directory
can render the LiveCycle server inoperative.