If you implement caching for your LiveCycle cluster by
using TCP, configure the TCP locators to find other members of the
LiveCycle cluster.
Note: This section does not apply
if you implement caching for your LiveCycle cluster by using UDP
(See 3.4 Modifying the JBoss run.conf fileto configure caching for your LiveCycle
cluster using UDP.)
Do the following to enable LiveCycle cluster caching using TCP:
Ensure that the TCP locators are installed and configured.
TCP locators are installed in the [LiveCycle root]/lib/caching
directory, with a default configuration, when you install LiveCycle.
You can change the default configuration. (See Modifying
the TCP locators.)
Configure
each node in the LiveCycle cluster to use the locators. (See 3.4 Modifying the JBoss run.conf file)
Ensure that TCP locators are running.
4.4.1 Modifying TCP locatorsThe LiveCycle installer creates a default configuration
of the TCP locators that is ready to use without modification. You
can move the locators to any computer on your network and run them
on that computer. The locators do not have to reside on a computer
that is a member of the LiveCycle cluster. You can also create additional
failover locators to support high availability in your cluster.
(See To
install the TCP locators:.)
You can also modify the TCP locators to use a port other than
the default port (22345). (See To
modify the default locator port (Windows): or To
modify the default locator port (UNIX):.)
4.4.2 Install TCP locatorsLog on to the computer where you installed LiveCycle
and navigate to the [LiveCycle root]/lib/ caching directory.
Copy the caching directory and its contents to the computer
on which you want to run the locators.
You can start TCP locator
from default location. You should copy the caching directory to
another location, only if:
4.4.3 Modify the default locator port (Windows)Open the startlocator.bat file in a text editor.
The startlocator file for a default installation is on the
computer where you installed LiveCycle, in the [LiveCycle root]/lib/caching
directory.
Change the default port number (22345) to your preferred
port number in the following properties:
set port=22345
-Dlocators=localhost[22345]
The port number can be
any available port between 1025 and 65535. See 3.4 Modifying the JBoss run.conf file for steps to complete the configuration. Important: Ensure that the port number that is configured
here matches the port number that is configured in the JVM argument
of each node of the LiveCycle cluster.
(Computers with multiple network cards only) If the computer
hosting the locator has multiple network cards, set the following
properties in the script:
set bindaddr=<bind IP address>
Where <bind IP address> is
the IP address that the locator will listen on. You must specify
the <bind IP address> for the JVM argument adobe.cache.cluster-locators on
each node in your LiveCycle cluster.
Note: If
you do not specify the bind address and the bind port in the startlocator script,
you will be prompted to input these values when you execute the
script. However, for IPv6, you must specify the bind address and
the bind port in the startlocator script itself.
Save the edited file.
Repeat steps 1 to 4 on any additional locators for your LiveCycle
cluster.
4.4.4 Modify the default locator port (UNIX)Open the startlocator.sh file in a text editor.
The startlocator file for a default installation is located
on the computer where you installed LiveCycle, in the [LiveCycle root]/lib/caching
directory.
Change the default port number (22345) to your preferred
port number in the following properties:
GF_PORT=22345
The
port number can be any available port between 1025 and 65535.
Important: Ensure that the port number that is configured
here matches the port number that is configured in the JVM argument
of each node of the LiveCycle cluster.
(Computers with multiple network cards only) If the
computer hosting the locators has multiple network cards, modify
the following argument:
GF_BIND_ADDRESS="<bind IP address>"
Where <bind IP address> is
the IP address that the locator will listen on. You must specify
the <bind IP address> for the JVM argument adobe.cache.cluster-locators on
each node in your LiveCycle cluster.
Note: For
IPv6, it is recommended that you specify the bind address and the
bind port in the startlocator script itself.
Save the edited file.
Repeat steps on any additional locators for your LiveCycle
cluster.
4.4.5 Start the TCP locatorsYou must start the TCP locators before you start your cluster.
If the TCP locators are not running when you start the members of
the LiveCycle cluster, caching will not function.
On the computer where the TCP locators are installed,
navigate to the caching directory. For a default installation, the
TCP locators are installed on the computer where you installed LiveCycle,
in the [LiveCycle root]/lib/caching directory.
(IPv6 only) Modify startlocator.bat (Windows) or startlocator.sh (UNIX) and
add the following JVM arguments: -Djava.net.preferIPv6Stack=true
-Djava.net.preferIPv6Addresses=true
Run the appropriate file:
Repeat above steps on any additional locators for your LiveCycle
cluster.
Note: (Windows Only)On running startlocator script, you would be
prompted to change the default value. You can choose to keep the
default values provided in the script or you can provide new values.
4.4.6 Stop TCP locatorsOn the computer where the TCP locators are installed,
navigate to the caching directory. For a default installation, the
TCP locators are installed on the computer where you installed LiveCycle,
in the [LiveCycle root]/lib/caching directory.
Run the appropriate file:
Repeat steps 1to 2 on any additional locators for your LiveCycle
cluster.
Note: If you are not using the default values in the startlocator script
and mentioned specific IP address and port values, specify the same
values in the stoplocator script. Otherwise, the stoplocator script
may fail to stop the locators.
|
|
|