FileNet P8 component relationships

The IBM FileNet P8 Platform components are interdependent. While most components do not require other components be running in order to start successfully, the absence of other components can affect processing. As a general rule, start the components and related servers in the following order (reverse the order for shutdown):

The table below lists the relationships between components. Use this information to determine the optimum order for starting up and shutting down each component in your P8 system. In addition, use this information to determine the impact of shutting down a single component for maintenance or other purposes.

FileNet P8 Platform component Other components required prior to startup

This component depends on...

Other components depend on this component for...

Application Engine

 

Without Content Engine,
...Users can't log in to Workplace.
...Users can't access object stores.

Without Process Engine,
...Application Engine can't populate Workplace Task pages.
...Users can't use workflow-related Workplace applications.
...Users can't update user preferences.
...Users can't transfer or start workflows.

Records Manager
...Isn't available.

eForms
...Isn't available.

Business Activity Monitor

None

Without Process Analyzer,
...Business Activity Monitor can't get up-to-date information.

None
Content Engine

Directory service

Databases
-GCD
-Object store

Without Process Engine,
...Content Engine can't automatically launch workflows as a result of subscriptions.

Without CFS-IS, NTFS, 3rd party storage device, network or other file store,
...Content Engine can't retrieve associated content.

Without Rendition Engine,
...Content Engine publish requests get errors if the Rendition Engine connection has not been disabled.

Without Content Search Engine,
...Full-text searches fail with errors.
...Indexing jobs cannot complete.

Process Engine
...Can't process anything.
...Can't refresh user and group information.
NOTE  If the Process Engine server is already running, it will continue to run successfully until it needs to refresh its user cache. At that point, it displays errors until a Content Engine server becomes available.

Rendition Engine
...Can't publish completed requests.

Application Engine or Workplace XT
...Can't log in to Workplace or Workplace XT.
...Can't access object store.

Process Simulator
...Can't access object store to retrieve or store workflow and scenario definitions and simulation data.

eForms

Application Engine

Without Content Engine,
...Users can't log in to Workplace or Workplace XT.
...eForms can't access object stores.
...eForms can't determine connection point for access to Process Engine.

Without Process Engine,
...eForms can't launch workflows.

 

Portlets

 

Without Content Engine,
...Depends on application.

Without Process Engine,
...Depends on application.

 
Process Analyzer Database with analysis services manager

Without Content Engine,
...Process Analyzer can't determine connection point for access to Process Engine.

Without Process Engine,
...Process Analyzer can't update workflow activity or access workflow and configuration information.

Process Simulator
...Can't publish simulation data for analysis.
...Can't access production statistics for use in simulations.

Business Activity Monitor
...Can't display workflow activity, or, if already running, update workflow activity information.

Process Engine

Database

Content Engine
NOTE  The Process Engine server can start without a Content Engine server, but no processing can take place. The Process Engine server displays errors until the Content Engine is available.

Without Content Engine,
...Process Engine can't access object stores.

Without Application Engine or Workplace XT,
...Process Engine can't process Component queues.

Without a SMTP mail server,
...Process Engine can't notify users by e-mail when specified process-related events occur.

Without a Rules Listener on a rules server,
...Process Engine can't process rules-based workflows.

Application Engine or Workplace XT
...Can't process Component queues.
...Can't populate Workplace or Workplace XT Task pages.
...Can't use workflow-related Workplace or Workplace XT applications.
...Can't update user preferences.
...Can't transfer or launch workflows.
Process Simulator

None

Without Process Analyzer,
...Process Simulator can't publish simulation data for analysis.
...Process Simulator can't access production statistics for use in simulations.

Without Content Engine,
...Process Simulator can't save scenario and simulation definitions.

Without Application Engine or Workplace XT,
...Process Simulator can't access simulation-related applications via Workplace or Workplace XT.

None
Records Manager Application Engine

Without Content Engine,
...Records Manager can't store data models.

Without Process Engine,
...Records Manager can't launch workflows.

Without a Crystal Reports server,
...Records Manager can't generate reports.

None
Rendition Engine Database

Without Application Engine,
...Rendition Engine can't submit requests.

Without Content Engine,
...Rendition Engine can't queue requests.
...Rendition Engine can't publish completed requests.

Content Engine
...Can't publish in HTML or PDF formats.
Rules Listener on a rules server None None

Process Engine
...Can't process workflows using rules.

Workplace XT

 

Without Content Engine,
...Users can't log in to Workplace XT.
...Users can't access object stores.

Without Process Engine,
...Workplace XT can't populate Workplace XT Task pages.
...Users can't use workflow-related Workplace XT applications.
...Users can't update user preferences.
...Users can't transfer or launch workflows.

Records Manager
...Isn't available.

eForms
...Isn't available.