Stop and Start sequence of FileNet 5.1 system components (Same sequence for FileNet 5.0 also)

Start sequence

1. Directory service (Ex: AD, TDS... )
2. RDBMS (Ex: DB2, SQL,Oracle....)
3. Machine for the Web application server hosting the Content Engine (Windows, UNIX, or Linux)
4. Java EE application server hosting the Content Engine (IBM WebSphere, )
5. Content Engine (FileNetEngine application, which can be set to start automatically)
6. Machine for the Process Engine
7. Process Engine server in Process Task Manager on Windows or UNIX, or if the Process Engine runs on a Windows machine, IMS ControlService and Process Engine Services Manager
8. Machine for the Java EE application server hosting the Application Engine (Windows, UNIX, or Linux)
9. Java EE application server hosting Workplace, Workplace XT
10. Workplace (FileNetWorkplace) or Workplace XT (WorkplaceXT) application or both (can be set to start automatically)
11. Process AE Services Manager, Process WP XT Services Manager, or both started on a Windows host machine for the user interface
12. Component Managers on the host machine for the Application Engine or Workplace XT if a supported business solution uses a component.
13. FileNet add-on products, such as Records Manager, Email Manager, or eForms Manager.

Stop Sequence

1. Stop any FileNet add-on products first, such as Records Manager.
2. Stop the Component Manager on the host server.
3. Use WAS to stop the application WorkplaceXT.
4. Stop the Process Engine with Process Task Manager.
5. Use WAS to stop the application FileNetEngine(Content Engine).
6. The directory service and RDBMS are stopped by their respective administrators if necessary.