|
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. 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 2.4.1 Location of the global document storage directory for information.
2.4.1 Location of the global document storage directoryYou 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 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:\.
2.4.2 Sizing factors for the global document storage directoryThe 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.
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.
2.4.3 Securing the global document storage directoryAccess 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.
2.4.4 Backing up the global document storage directoryThe global document storage directory should be backed
up to allow administrators to restore LiveCycle in case of failure.
If the global document storage directory becomes unavailable
or is lost due to failure, LiveCycle will not run until the GDS
directory and database are restored by a consistent back up or LiveCycle
is reinitialized with a new installation.
|
|
|
