Content Engine startup and shutdown

This topic includes detailed instructions for starting up and shutting down the Content Engine software. Content Engine consists of the Content Engine software, the Global Configuration Database (GCD), one or more object store databases, and one or more file stores.

The IBM FileNet P8 Platform components are interdependent. See IBM FileNet P8 component relationships to determine the optimum order for starting up and shutting down your system components.

The tables below contain detailed startup and shutdown instructions. Each step is listed in the first column. The columns to the right contain the detailed instructions or commands necessary to accomplish the step. The first table describes startup and shutdown procedures using the graphical user interfaces (GUIs) available in the component or operating system software. The second table lists the equivalent command line instructions. You can execute the command-line instructions directly from a command prompt, or incorporate them into a script.

GUI procedures

GUI startup

You can configure a variety of options for automatic startup. In order to provide you with all of the steps required to start this component, the procedure below assumes that no automatic startup options have been configured. Where automatic startup is configured, the related step becomes unnecessary.

TIP Click Automatic startup tip for instructions on enabling automatic startup for a step.

Start the directory service server.

Use the startup procedures specified by your directory service software vendor.

Start the database server software. Where databases are remote or not collocated, be sure to start the Content Engine (GCD) database and the object store database(s).

Use the startup procedures specified by your database software vendor.

Start the application server software.

Use the startup procedures specified by your application server software vendor.
The following sections lists features that can be enabled or disabled using Enterprise Manager. If the feature was enabled prior to a previous shutdown, it remains enabled on startup, and no further action is necessary. If the feature was disabled prior to a previous shutdown, you must re-enable the feature on startup. Use the instructions below to verify the status of a feature and to enable it if necessary.

If a fixed content device is configured, enable the dispatcher.

Use Enterprise Manager to enable the dispatcher. See IBM FileNet P8 domain properties (Import Agent tab) for more information.

If a Rendition Engine is configured, enable the connection and dispatcher.

Use Enterprise Manager to enable the connection and dispatcher. See Enabling the Rendition Engine connection for detailed instructions.

If you have full-text indexing configured, enable the dispatcher.

Use Enterprise Manager to enable the dispatcher. See IBM FileNet P8 domain properties (Verity Server tab) for more information.

GUI shutdown

Stop the application server software.

Use the shutdown procedures specified by your application server software vendor.

NOTE  If your application server software provides these options, you can do the following:

  • Stop an individual application: you can stop the Content Engine application.
  • Finish work-in-progress: you can allow in-progress work to complete before stopping Content Engine.

Stop the database server software. Where databases are remote or not collocated, be sure to start the Content Engine (GCD) database and the object store database(s).

Use the shutdown procedures specified by your database software vendor.

Stop the directory service server.

Use the shutdown procedures specified by your directory service software vendor.

TIP For backup purposes, you can simply take the associated database(s) offline.

Command-line procedures

Command-line startup

Start the directory service server.

Use the startup procedures specified by your directory service software vendor.

Start the database server software. Where databases are remote or not collocated, be sure to start the Content Engine (GCD) database and the object store database(s).

Use the startup procedures specified by your database software vendor.

Start the application server software.

Use the startup procedures specified by your application server software vendor.
Command-line shutdown

Stop the application server software.

Use the shutdown procedures specified by your application server software vendor. By stopping the Content Engine application, you’re also stopping all the background processes (for example, Asynchronous Processing, Image Services Import Agent, Publishing, and Verity Server).

NOTE  If your application server software provides these options, you can do the following:

  • Stop an individual application: you can stop the Content Engine application.
  • Finish work-in-progress: you can allow in-progress work to complete before stopping Content Engine.

Stop the database server software. Where databases are remote or not collocated, be sure to start the Content Engine (GCD) database and the object store database(s).

Use the shutdown procedures specified by your database software vendor.

TIP For backup purposes, you can simply take the associated database(s) offline.