The information in this Blog is correct to the best of my knowledge – if you discover any errors, please post on the comments area.
Thanks to Pete Spencer of Adobe for his expertise.
- You need to specify various directories when you configure LiveCycle using the Configuration Manager. These include:
- Global Document Storage (GDS) Directory
- Temporary Directory
- Font Directories
- The values you enter into Configuration Manager are stored within the LiveCycle ear file. The values in this ear file are only used during initializing (bootstrapping) the LiveCycle database – after this, they are no longer used, and the values from the database are used instead.
- All of the directories must be specified from the perspective of the application server, NOT the perspective of the machine running Configuration Manager. In other words, these directories must exist on the application server. It’s therefore simplest if you actually run Configuration Manager on the target machine.
- You can modify the directory names in the database using Adminui at any time, including after installation. Home > Settings > Core System Settings > Configurations. You must restart the server before your changes take effect. You MUST move files from the old GDS to the new GDS while the server is stopped. You do not need to reconfigure or redeploy your ear files.
- There is only one directory location stored in the database, no matter how many instances you have in your cluster. In a clustered environment, you must set up your servers so that all of them have the same GDS, temp and font directory names. (There’s a way around this for the temp directory – see below.)
For example: if you’re running LiveCycle on different operating systems, you cannot set the System Font directory to c:\windows\fonts on one machine, and c:\winnt\fonts on a different machine. You will have to make the directory the same on all machines, even if this means copying files to matching directories.
Another example: You cannot set the Global Storage Directory to “C:\Adobe\Global” on one machine, and “\\machine1\c$\Adobe\Global” on another. You can use “\\machine1\c$\Adobe\Global” on both machines (although this would create a single point of failure).
- Make sure that the user under which you run the Application Server has read/write access to the temp/GDS directories, and read access to the Font directories.
- You can use the same LiveCycle ear files for installs onto multiple boxes (eg Dev, Test, Production), even if the actual directories on a second box don’t match those that you specified for the first box. You can deploy the LiveCycle ear files, run LiveCycle, and bootstrap the database. Then you can modify the directories using Adminui, and restart LiveCycle. Once you’ve done this, you can complete the configuration by installing components and samples, etc. (Note: We haven’t thoroughly tested this, and don’t know for sure that those directories in the LiveCycle ear file aren’t used for some other purpose – we recommend that you create separate LiveCycle ear files for each machine configuration.)
- These can be shared, or each application server in a cluster can have its own copy on a local drive.
- If you’re running Configuration Manager on one machine, and deploying to another, you must copy the LiveCycle fonts from the installation directory (usually C:\Adobe\LiveCycle8\fonts) to a location on the application server machine.
- Under Windows, the system fonts are generally either in C:\windows\fonts or c:\winnt\fonts.
Global Document Storage Directory (GDS)
- The GDS should be considered an extension to the database, and is part of the persistent state of the LiveCycle system. Don’t “clean up” the files in this directory.
- You should back up the files in this directory simultaneously with the database. See my previous post on this topic.
- The GDS must be a single directory that is shared between all instances of LiveCycle in a cluster. Usually this means setting up the GDS on a shared drive, or a Storage Area Network (SAN).
- It must also be referred to by exactly the same pathname for all instances of LiveCycle.
- If you change the location of the GDS, you must ALSO move all the files to the new location while the server is stopped.
- Each running instance of LiveCycle requires its own temporary directory. There are a number of ways of specifying the temporary directory:
- If you specific a non-blank directory in Configuration Manager (which also means a non-blank directory in adminui), then LiveCycle will use this value.
- If you specify a blank directory in Configuration Manager/Adminui, then LiveCycle will use the Java VM java.io.tmpdir system property.
- The java.io.tmpdir property can be set in several ways:
- You can specify it explicitly in the command line that you use to launch the Java VM that runs LiveCycle. For example, “java -Djava.io.tmpdir=C:\temp …”
- If you do not specify it explicitly, Java will set this value based on operating system defaults (eg value of “TEMP” system variable)
- If you are using vertical clustering, the members of the cluster will each need their own temp directory, but they are sharing the same physical drive. Therefore
- Leave the temporary directory blank in Configuration Manager/Adminui.
- Specify a different java.io.tmpdir Java system property for each instance of LiveCycle.