3.6 Installation considerations

3.6.1 Disabling Virus scans (Windows only)
3.6.2 Installing from network drives
3.6.3 Using LiveCycle with a Luna HSM cluster
- 3.6.3.1 Enable HAOnly mode on the Luna device
3.6.4 Manual use of Acrobat restricted
3.6.5 Temporary directory
- 3.6.5.1 Temporary directory on cluster configurations

3.6.1 Disabling Virus scans (Windows only)

To improve the speed of the installation, you may choose to disable any on-access virus scanning software for the duration of the installation.

3.6.2 Installing from network drives

It is recommended that you install LiveCycle only from the installation media or a local disk drive. Attempting to install the software over a network results in considerable delays in starting and installing. It is also likely that installing from a network drive will add to the length of the directory path, which will cause the LiveCycle installer to prevent the installation from proceeding.

3.6.3 Using LiveCycle with a Luna HSM cluster

When using a SafeNet Luna ethernet-attached Hardware Security Module (HSM) cluster, you must ensure HAOnly mode is enabled on the device.

3.6.3.1 Enable HAOnly mode on the Luna device

Use the vtl tool shipped with the Luna client to determine if HAOnly mode is enabled. Type:
```
vtl haAdmin –HAOnly -show
```
1) If HAOnly mode is not enabled, type:
```
vtl haAdmin –HAOnly -enable
```

3.6.4 Manual use of Acrobat restricted

If you installed the PDF Generator for native document conversion, use of the bundled Acrobat installation is restricted to the Generate PDF service and is not licensed for any other use.

3.6.5 Temporary directory

LiveCycle requires a temporary directory to store documents that are larger than the maximum inline size set for document objects. For detailed information on how you can improve the performance of your LiveCycle Server by specifying an appropriate value for this setting, see this blog on the Document Max Inline Size performance knob.

(AIX, Linux, and Solaris only) If a non-root user is running the application server, the user must have read, write, and execute permissions on the specified temporary directory.

Important: (For cluster deployments only) Future upgrades might fail if you specify a shared network directory as the temporary directory.

3.6.5.1 Temporary directory on cluster configurations

Horizontal cluster: The location of the temporary directory can be either unique or shared for a horizontal cluster. Create a unique temporary directory on each node of the cluster to eliminate network traffic to a shared drive or directory.

Vertical cluster: Create a shared temporary directory. Typically, the shared folder is on the same local system as the vertical cluster.

In addition to the shared temporary folder, each server creates its unique subdirectories to store temporary data. The subdirectory name is based on the corresponding server name.

(JBoss Only) To ensure each JBoss instance has a unique name, open the run.bat file, and manually modify the -Dadobeidp.serverName=<servername> JVM argument. The default value is server1.