(F5 using 3DNS for load balancing
by DNS routing) Configure the IOR cache time-to-live for applications
accessing a farmed Process Engine.
In a farmed
Process Engine environment where you use
F5 for load balancing by using DNS routing and the 3DNS method, you
must configure the client machine IOR (Interoperable Object Reference)
cache time-to-live to a value smaller than the default 3600 seconds,
matching the DNS TTL set for the 3DNS. Having a cache time-to-live
that is longer than the 3DNS TTL will cause the calls to be routed
to only one
Process Engine server
instead of the preferred
Process Engine server
as intended by the 3DNS routing. The cache time-to-live is set by
using the system property
filenet.pe.ior.cache.ttl.in.seconds.
The
configuration is required for the following components:
- Content Engine
- Application Engine
- Component Manager on Application Engine (configuration
done post-installation)
- Workplace XT
- Component Manager on Workplace XT (configuration
done post-installation)
- Custom client applications that use the Process Engine API.