In a typical distributed installation scenario, you install the FileNet® P8 Platform components on a system of networked servers. You can install some components as stand-alone applications, or install multiple instances of a single component.
When you deploy Content Platform Engine as a stand-alone
application, you configure a single application server. You must configure your Content Platform Engine instances and deploy those Content Platform Engine instances on a single server, by using a single directory for
the component files.
When you deploy Content Platform Engine in a WebSphere® Application Server managed environment, you can install and configure Content Platform Engine on any managed node. Then, use the application server administration console to deploy the bootstrapped Content Platform Engine EAR file to the servers on each managed node or to a cluster.
When you deploy Content Platform Engine in an Oracle WebLogic Server managed environment, you can install and configure Content Platform Engine on any managed server. Then, use the application server administration console to deploy the bootstrapped Content Platform Engine EAR file to any of the managed servers. The managed servers can be in a cluster.
JBoss Application Server has no managed deployment capability.
When you deploy Content Platform Engine in a WebSphere Application
Server or WebLogic Server non-managed
environment, you install and configure Content Platform Engine on any
Content Platform Engine server in the environment. After you configure the
bootstrapped Content Platform Engine EAR file on this first server, you are
directed to copy the bootstrapped EAR file to each of the other servers. Then, deploy the
bootstrapped EAR file on all of the servers.
When you deploy Content Platform Engine in a JBoss Application Server environment, install and configure Content Platform Engine on an initial server in the environment. Then, copy the Content Platform Engine EAR file from the initial server to the other servers in the environment.