What Order Should Hyperion Services be Started, so that Hyperion Planning will Work Properly

What Order Should Hyperion Services be Started, so that Hyperion Planning will Work Properly [ID 738471.1]
Modified 10-JAN-2011 Type HOWTO Status PUBLISHED
In this Document
Goal
Solution

Applies to:

Hyperion Planning - Version: 9.3.1.0.00 to 9.3.1.0.00 - Release: 9.3 to 9.3
Information in this document applies to any platform.
Goal

To provide the order in which the application services should be started so that Planning will work properly.

Solution

The following Hyperion product services and processes are listed in their recommended startup order. The names of the Services are given as they appear in the Windows 'Services' list after a standard installation:

1. Hyperion S9 OpenLDAP
2. Hyperion S9 Shared Services
3. Hyperion S9 BI+ 9.3 Core Services 1
4. Hyperion S9 EPM Architect Process Manager
which also starts the following:
5. Hyperion S9 EPM Architect Engine Manager
6. Hyperion S9 EPM Architect Job Manager
7. Hyperion S9 EPM Architect Event Manager
8. Hyperion S9 BI+ Analytic Services 9.3.1 — hypservice
9. Hyperion S9 Administration Services ATS5
10.Essbase Integration Server (this service might not exist)
11.Hyperion S9 Provider Services ATS5
12.Hyperion S9 BI+ 9.3 Interactive Reporting Service 1 (this service might not exist)
13.Hyperion S9 BI+ 9.3 Workspace
14. IIS: IIS Admin Service
15. HTTP SSL
16. World Wide Web Publishing Service
17. Hyperion S9 Apache 2.0
18. Hyperion S9 BI+ 9.3 Web Analysis (this service might not exist)
19. Hyperion S9 EPM Architect Web ATS5
20. Hyperion S9 EPM Architect Data Synchronization ATS5
21. Hyperion S9 Planning
22. HyperionRMIRegistry