Verify the Installation

It should now be possible to start the Content Engine and verify that the major components are working. To do so, carry out the following procedure on each engine-host, while logged in as escenic:

Start the Content Engine by entering:
```
$ ece start
```
Verify that the Content Engine is running by entering:
```
$ ece status
```
This should produce something like the following output:
```
[ece] Escenic Content Engine IS running (PID 1936) up 0d 1h 33m 51s
```
Open a browser, and try accessing the escenic-admin web application on each of the engine-hosts by entering:
```
http://engine-host-ip-address:8080/escenic-admin/
```
in the browser address field. There may be a delay while the Content Engine initializes, but eventually, you should see the following page:
Click on the Status link to display a set of status pages containing Content Engine test results.
Across the top of these pages is a menu containing links to each of the status pages. Click on each of these links in turn and verify that all the tests pass (indicated by a icon).
The icon indicates that something is not correctly configured. If you see one of these icons, then you need to check over all relevant settings. In most cases there is a help link next to the test result indicating the most likely causes of failure. Make any necessary corrections, then restart the Content Engine by entering:
```
$ ece restart
```
Wait a minute or so, then refresh the browser window to re-execute the tests that failed.

Verify that the Content Engine is correctly configured on all your engine-hosts before proceeding any further.

On some of the test pages you will see graphics/escenic-app-warning.png warning icons. In most cases these are simply an indication that no publications have yet been created, and they can be ignored.