You can install or deploy multiple instances of Content Engine on a single web application server. You can
also define multiple virtual servers for Process Engine.
You can also use virtual Process Engine server
definition to separate a development environment from a production environment.
When you deploy multiple Content Engine instances on a
single server, you configure a single application server.
If you deploy multiple instances of Content
Engine on multiple servers, the application server type and level must
be identical on all servers. OS must be
the same but can be at different levels
When multiple Process Engine
virtual servers are configured on a single server, all configuration and
administration programs are executed by indicating which Process
Engine virtual server to act on. It is a best practice, then, to always
specifically name your Process Engine virtual
servers. Otherwise, default will be applied as the name Process
Engine virtual server. In such cases, any time you start a configuration
or administration program and you don't explicitly identify the Process Engine virtual server to act on, the Process Engine virtual server named default will be
Verifying Process Engine installation. You can verify your Process Engine installation by using Application
Engine (Workplace). You must install Application Engine or Workplace before
starting this task.
A server farm is a group of identical servers accessed through hardware or
software load balancing technology. All the servers are active, provide the
same set of services, and are effectively interchangeable. A load balancer
distributes incoming client requests over the servers in the group.
Because the data processed by various FileNet P8
components are interdependent, you must back up all data within a single
FileNet P8 domain at the same time, regardless of the physical location of the
data. To maintain the integrity of the data within your FileNet P8 site, you
must therefore restore the entire FileNet P8 domain as well, since restoring a
single component of the system introduces inconsistencies and errors.
FileNet P8 Platform
does not support hot backups (that is, backups performed while the database is
online and available for reading and writing). You must shut down each FileNet
P8 component before you back it up. This requirement ensures proper
synchronization (for example, between stored content and associated metadata).