The configuration of the Content Engine connection in a highly available environment depends on the type of application you want to connect to the Content Engine. You can configure administrative applications or user applications to connect to the Content Engine.
Administrative applications, such as IBM® FileNet® Enterprise Manager and IBM FileNet Deployment Manager, modify metadata and GCD information such as property templates, class and property definitions, and domain level objects such as sites, object stores, and file storage areas.
Due to the built-in lag in metadata synchronization across the Content Engine nodes, changes made on one node are not synchronized immediately after a configuration change is made via an administrative application.
To ensure your administrative applications always get a consistent view of the system metadata, you must configure them all to point to a single Content Engine node (the same node), rather than a virtual server.
In the event the configured Content Engine fails you must reconfigure your administrative applications to point to a different Content Engine node. For information, go to the IBM FileNet P8 online help and navigate to .
User applications such as Workplace and Workplace XT are content and process centric applications used in everyday production to check documents in and out and access workflows, for example.
For user applications, the Content Engine connection in a highly available environment differs depending on your HA configuration, but in any case must be configured to connect to the virtual server, so that it will be redirected automatically to another Content Engine node in the event of a Content Engine node failure.