Configure the Component Manager and start it on an Application Engine.
- Start Process
Task Manager on the Application Engine server
by running one of the following command files from the AE_install_path/FileNet/AE/Router directory,
depending on your operating system:.
Option |
Description |
UNIX® |
routercmd.sh |
Windows® |
routercmd.bat |
If the Registry Port assigned to Component Manager conflicts
with the port number required by another application or service running
on the Application Engine server,
Process Task Manager will not start up as expected and the necessary vwtaskman.xml will
not be automatically created. If this happens, make a copy of the
sample vwtaskman.xml.sample file located on the Application Engine. - On Application Engine, the file
is located in:
- Drive:\Program Files\FileNet\AE\Router on Windows
- /opt/FileNet/AE/Router on UNIX
Open vwtaskman.xml.sample with a text editor,
change the port element value to an available port number, and save
the file to vwtaskman.xml in the same directory.
- In Process Task Manager, select the server name in the
left pane.
- Find the Registry Port for the server in the right pane
and verify that it is correct.
- Select Component Managers in the
left pane .
- Enter the Content URI , service username, and service password
Content URI to authenticate to the Content Engine server. The Content
URI defaults and you can use the default or change the value.
- Right-click and select New to select
a connection point from the drop down list.
- Enter or modify the component properties as appropriate. For details, see the . In an environment configured for single sign-on (SSO),
do not use the SSO server name in the URL, even if Process Task Manager
displays it by default.
(F5 using 3DNS for load balancing
by DNS routing in a high availability environment) 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.- Create the p8bpmsystems.properties configuration
file in the JRE/LIB directory of the application server, or in the
JRE/LIB directory of the Component Manager. For example,
on Windows, create:
C:\Program Files\IBM\AE\Router\
java\jre\lib\p8bpmsystems.properties
- Add this line to the file:
filenet.pe.ior.cache.ttl.in.seconds=TTL
Where TTL is
the IOR cache time-to-live in seconds.
For example,
to set the IOR cache time-to-live to 30 seconds: filenet.pe.ior.cache.ttl.in.seconds=30
- Click Start on the toolbar.
In a farmed or cluster configuration,
make the same changes on every node and restart the Component Integrator.