Posts tagged GDS

Understanding the LiveCycle GDS – and freeing up disk space

LiveCycle, as an piece of Enterprise software, tends to assume that you may want to keep a quantity of data around for posterity. Long-lived processes can cause a lot of disk space bloat, and whilst this is fine for those who wish to archive lots, this may not be ideal when running a lower-spec server.
In this article, I will point out the main areas where data and disk space use can happen, and how to clean up.

Read the complete post here.

Change the GDS (Global Document Storage) location of a Production LiveCycle ES System

Important Remark:
Within the LiveCycle Documentation you will find the following on the GDS:
“The global document storage (GDS) is a directory used to store long-lived files such as PDF files used within a process or DSC deployment archives. Long-lived files are a critical part of the overall state of the LiveCycle ES environment. If some or all long-lived documents are lost or corrupted, the LiveCycle ES server may become unstable. Input documents for asynchronous job invocation are also stored in the GDS and must be available in order to process requests. Therefore, it is important that the GDS is stored on the redundant array of independent disks (RAID) and backed up regularly.”
So the GDS is the cornerstone of a LiveCycle system. Changing this location should be carefully executed by product experts. Take a back-up before you start and don’t try this at home …
Disease:
For whatever reason you want to change the location of the GDS. As explained above this is possible but should be very carefully executed.
Prescription:
Disclaimer: This section will describe the different steps to execute in order to move the location of the GDS. These steps should be considered as a Guideline and not as a by Adobe Supported set of actions. You are encouraged to execute this first in a Test environment before doing this in a Production environment. The different Steps are:
  1. Alert and Ask the End-Users to get out of the LiveCycle Application/Server
  2. Put the LiveCycle Application/Server in ‘Operate in safe backup mode’. In Adminui go to Settings > Core System > Backup Settings – select the ‘Operate in safe backup mode’ and hit the OK button.
  3. Backup the GDS folder
  4. Zip or Tar the GDS folder
  5. Change the location of the GDS folder. In Adminui go to Settings > Core System > Core Configurations and change the location of the GDS Directory. Hit the OK button; you will get a second page and hit the OK button again
  6. Shutdown the LiveCycle Application/Server
  7. Check whether the LiveCycle Application/Server system user has access to the new GDS folder
  8. UnZip or UnTar the files in the new GDS folder
  9. StartUp the LiveCycle Application/Server
  10. Do some basic validations. In Adminui go to Services > Applications and Services and choose Archive Management and Endpoint Management and check visually whether you get the expected information
  11. Deactivate the ‘Operate in safe backup mode’. In Adminui go to Settings > Core System > Backup Settings – unselect the ‘Operate in safe backup mode’ and hit the OK button

Tip to stay healthy:
Make sure that you have the final location of the GDS available, before you install LiveCycle in a Production environment.

—-
Original article at http://www.drflex.eu/2009/06/change-the-gds-global-document-storage-location-of-a-production-livecycle-es-system/?utm_source=rss&utm_medium=rss&utm_campaign=change-the-gds-global-document-storage-location-of-a-production-livecycle-es-system.

Change the GDS (Global Document Storage) location of a Production LiveCycle ES System

Important Remark:
Within the LiveCycle Documentation you will find the following on the GDS:
“The global document storage (GDS) is a directory used to store long-lived files such as PDF files used within a process or DSC deployment archives. Long-lived files are a critical part of the overall state of the LiveCycle ES environment. If some or all long-lived documents are lost or corrupted, the LiveCycle ES server may become unstable. Input documents for asynchronous job invocation are also stored in the GDS and must be available in order to process requests. Therefore, it is important that the GDS is stored on the redundant array of independent disks (RAID) and backed up regularly.”
So the GDS is the cornerstone of a LiveCycle system. Changing this location should be carefully executed by product experts. Take a back-up before you start and don’t try this at home …
Disease:
For whatever reason you want to change the location of the GDS. As explained above this is possible but should be very carefully executed.
Prescription:
Disclaimer: This section will describe the different steps to execute in order to move the location of the GDS. These steps should be considered as a Guideline and not as a by Adobe Supported set of actions. You are encouraged to execute this first in a Test environment before doing this in a Production environment. The different Steps are:
  1. Alert and Ask the End-Users to get out of the LiveCycle Application/Server
  2. Put the LiveCycle Application/Server in ‘Operate in safe backup mode’. In Adminui go to Settings > Core System > Backup Settings – select the ‘Operate in safe backup mode’ and hit the OK button.
  3. Backup the GDS folder
  4. Zip or Tar the GDS folder
  5. Change the location of the GDS folder. In Adminui go to Settings > Core System > Core Configurations and change the location of the GDS Directory. Hit the OK button; you will get a second page and hit the OK button again
  6. Shutdown the LiveCycle Application/Server
  7. Check whether the LiveCycle Application/Server system user has access to the new GDS folder
  8. UnZip or UnTar the files in the new GDS folder
  9. StartUp the LiveCycle Application/Server
  10. Do some basic validations. In Adminui go to Services > Applications and Services and choose Archive Management and Endpoint Management and check visually whether you get the expected information
  11. Deactivate the ‘Operate in safe backup mode’. In Adminui go to Settings > Core System > Backup Settings – unselect the ‘Operate in safe backup mode’ and hit the OK button

Tip to stay healthy:
Make sure that you have the final location of the GDS available, before you install LiveCycle in a Production environment.

—-
Original article at http://www.drflex.eu/2009/06/change-the-gds-global-document-storage-location-of-a-production-livecycle-es-system/.

How to Globally Turn Off LiveCycle Process Recording

Jayan Kandathil

There are situations where a LiveCycle system administrator has to (globally) turn off all process recordings that process developers may have enabled.

One of those cases is where the load testing team prepares the system for a high-volume load test. If recording is turned on for any of the processes involved in the load test, the filesystem-based GDS folder will experience high disk write I/O which will skew performance data (even if the GDS is configured to target the database). There is also the risk that the filesystem will run out of disk space.

To prevent this from happening, you can set a property of the AuditWorkflowService called ‘maxNumberOfRecordingInstances‘ using the AdminUI. Setting this to 0 (the default is 50) and saving the change will in effect turn off all process recording globally. There is no need to re-start LiveCycle. See screenshot below:

——-
Original article at http://blogs.adobe.com/livecycle/2011/03/how-to-globally-turn-off-livecycle-process-recording.html.

Go to Top