|
You must configure the WebSphere Application Server instances
that you installed in the cluster by performing the following tasks:
6.2.1 Modifying the WebSphere time-out settingsYou must modify the WebSphere time-out settings on each
WebSphere Application Server in the cluster.
To modify WebSphere time-out settings:In the WebSphere Administrative Console navigation tree,
click Servers > Application servers and, in the
right pane, click the server name.
Under Container Settings, click Container services > Transaction Service.
In the Total transaction lifetime timeout box, type 300 and
then click OK.
Under Container Settings, click Container Services > ORB Service.
In the Request timeout box, type 360 and,
in the Locate Request Timeout box, type 300,
and then click OK.
Under Server Infrastructure, click Administration > Administration Services.
On the next screen, click JMX Connectors and, in the
table, click SOAPConnector.
On the next screen, click Custom properties and, in
the table, click requestTimeout.
In the Value box, type 1800.
Click OK and then click Save directly to the master configuration.
6.2.2 Modifying the JVM propertiesYou must modify the Java Virtual Machine (JVM) properties
of each WebSphere Application Server instance in the LiveCycle cluster
to add LiveCycle options.
Note: You must restart each node of the application
server after you modify the JVM parameters.
Before starting this procedure, you must know if your cluster
uses a 32-bit or 64-bit JVM. See Preparing to Install LiveCycle
(Server Cluster) to determine the JVM required for your cluster
configuration.
Before starting this procedure, you must determine how your LiveCycle
cluster implements cluster caching so that you can correctly configure
a JVM argument for cluster caching. You may implement cluster caching
by using UDP or TCP but not both. The following factors may affect
your choice:
UDP can be used only if your cluster is based on IPv4.
Use TCP if your cluster is either IPv4-based or IPv6-based.
On an IPv6-based cluster, you must use TCP to be IPv6-compliant.
If
you implement cluster caching by using TCP, you must also ensure
that you configure the TCP locators correctly (see “Configuring
the caching locators (caching using TCP only)” ).
 It is recommended to use TCP instead of UDP multicasting
for production systems because of the inherent reliability of the
TCP protocol. To modify JVM properties:Log
in to the WebSphere Administrative Console and, in the navigation
tree, click Servers > Application servers and then,
in the right pane, click the server name.
Under Server Infrastructure, click Java and Process Management > Process Definition.
Under Additional Properties, click Java Virtual Machine and
add or configure the following properties:
In the Initial Heap Size box,
type 512
In the Maximum Heap Size box, set one of the following
values:
In the Generic JVM arguments box, add the following
arguments:
-Xgcpolicy:gencon
-Dfile.encoding=utf8Note: Add
the -Xgcpolicy:gencon JVM argument only if WebSphere
is using the IBM JDK. However, do not add this argument in case
of WebSphere on Solaris operating system.
In the Generic JVM arguments box, set one of the following
values:
On the same screen, in the Generic JVM arguments box,
add the following caching arguments depending on the configured
cluster cache mechanism (UDP or TCP):
(Caching using
UDP discovery) Configure the multicast port argument in the following
format:
-Dadobe.cache.multicast-port=<port number>
Note: The value for <port number> can
be any available port between 1025 and 65535. The multicast port
must be unique to the LiveCycle cluster (that is, the port must
not be used by any other cluster on the same network, any attempt
to use the same port by any other cluster on the same network would
result in bootstrap failure). It is recommended that you configure
the same <port number> on all nodes in the LiveCycle cluster, as in this example:
-Dadobe.cache.multicast-port=33456
(Caching using UDP discovery) Setting multicast address argument
is optional. Default muticast addresses for IPv4 and IPv6 are as
following:
IPv6 - FF38::1234
IPv4 - 239.192.81.1
If you have restriction on multicast
addresses in your network, use following argument to set multicast
addresses:
-Dadobe.cache.multicast-address=<ip address>
Note: The value for <ip address> is
the IP address used for multicast networking. The IP address is
ignored if adobe.cache.multicast-port is zero.
Note: The multicast address must be unique to the LiveCycle
cluster and must not be used by any other cluster on the same network.
It is recommended that you configure the same <ip address> on all nodes in the LiveCycle cluster. For example:
-Dadobe.cache.multicast-address=239.192.81.1
(Caching using TCP only) For IPv4, configure the cluster
locators argument in the following format:
-Dadobe.cache.cluster-locators=<IPaddress>[<port number>],<IPaddress> [<port number>]
For
IPv6, configure the cluster locators argument in the following format:
-Dadobe.cache.cluster-locators=<hostname>@<IPv6 address>[<port number>], <hostname>@<IPv6 address>[<port number>]
Note: Configure, as a comma-separated list, the locators
for all nodes of the cluster. The value for <IPaddress> is
the IP address of the computer running the locator, and the value
for <port number> is any unused port between 1025
and 65535. It is recommended that you configure the same <port number> for all locators, as in this example:
-Dadobe.cache.cluster-locators=10.20.30.5[22345],10.20.30.6[22345]
For machines with multiple Network Interfaces
Some
machines may be connected to multiple networks via multiple Network
Interface Cards (NICs). For such machines, set the JVM property
-Dadobe.cache.bind-address to the IP address of
the network interface card that you are using for LiveCycle Server.
-Dadobe.cache.bind-address=<IP Address>
Note: It
is recommended to set JVM property -Dadobe.cache.bind-address for machines
with one Network Interface Card, also.
To prevent application server from Denial of Service attacks
configure the following JVM argument: -DentityExpansionLimit=10000
Click Apply and click Custom Properties.
(IPv4 only) On the next screen, click New,
add or configure the following properties, and then click OK:
In the Name box, type java.net.preferIPv4Stack.
In the Value box, type true.
(IPv6 only) On the next screen, click New,
add or configure the following properties, and then click OK:
In the Name box, type java.net.preferIPv6Stack.
In the Value box, type true.
In the Name box, type java.net.preferIPv6Addresses.
In the Value box, type true.
Click OK and then click Save directly to the master configuration.
Restart the server.
Repeat steps 11 to 19 for each server in the cluster.
6.2.3 Creating a J2C authentication alias for the databaseYou must create a J2C authentication alias for the database.
To create a J2C authentication configuration for the data source:(WebSphere 7.x) In the
WebSphere Administrative Console navigation tree, click Security > Global security.
In the right pane, under Authentication, click Java Authentication and Authorization Service > J2C authentication data,
and then click New.
Set the following properties:
In the Alias box,
type an alias name appropriate to the database user, such as IDP_DS/db2-db2user.
In the User ID box, type a name, such as db2user.
This ID is the login credential used to access the database that
will be used with the IDP_DS data source.
In the Password box, type a password for this user.
Note: In this guide, IDP_DS identifies the LiveCycle
data source.
Click OK and then click Save directly to master configuration.
Repeat steps 3 and 4 for RM_DS. Use EDC_DS/db2-db2user as
the alias name.
Note: EDC_DS is JNDI name of the
RM_DS datasource.
|
|
|
