Hyperion Planning Start and Stop Procedures

Hyperion Planning Start and Stop procedures Overview: Hyperion Planning has services that run in production on 2 separate Windows servers. 1. HypEss is used to run the Essbase database. 2. HypApp runs all of the application components need to support the Hyperion Workspace (user interface), report generation and printing, and the underlying components such as weblogic needed for security and network connectivity. Hyperion Planning in Development/test environment runs all services on 1 Windows server. 1. HypDev is used to run the Essbase database and all of the application components need to support the Hyperion Workspace (user interface), report generation and printing, and the underlying components such as weblogic needed for security and network connectivity. Windows command scripts have been created to start or stop the various Hyperion services. It is important to start and stop the services in a specific sequence. Therefore it is advised to use the scripts that have been developed to maintain the proper order. This document covers the 2 activities that we typically perform from a support perspective. 1. Stop and Start all Hyperion Planning services (used when user interface stops working) 2. Stop and Start only Hyperion Reporting services. (used when only reporting tool has problem) The Windows Hyperion start and stop command scripts can be found in the D:\commandScripts folder found on each of the servers as shown below:

Document1

Page 1

Hyperion Production Environment: NOTE: There are 2 different approaches you can take to stopping and restarting the Hyperion services on the production servers. The easiest and suggested way is to initiate a script using the task scheduler. The other approach is to log onto the individual servers and explicitly/manually run the stop or start scripts as described below. Instructions for both methods are shown below.

 Stop and restart all Hyperion Planning components using Task Scheduler You can open the batch task scheduler and run the “Stop_Start_All_Services” task on the Hyperion production server by doing the following steps: Open the task scheduler on your PC by doing the following:  

Click on the Windows Program Start button/icon. Then from the menu items select “All Programs” -> “Accessories” -> “System Tools” -> “Task Scheduler”

After the Task Scheduler window is open on your PC, click on the Action Menu item and then select the “Connect to another computer…” option. You may have to click on the option below the icons labeled “Task Scheduler (Local)” before clicking on the action menu.

That will open a new window as shown below. Simply enter the name of the Hyperion server you want to connect to. In this case, enter “HypEss” as highlighted below and then click OK. Document1

Page 2

To see the list of previously configured tasks on the server click on the “Task Scheduler Library” highlighted on the top left of the window. That will then display a list of tasks/jobs that can be run. Find the “Stop_Start_All_Services” name in the list then select it by clicking on it. Use the right mouse button to get a pop up menu with a list of options. Select “Run” to execute the script. The status of the task should change from Ready to Running. It will take about 30 minutes to complete the task. Use F5 to refresh the task list & status. When finished you can close the task scheduler.

Document1

Page 3

 Explicitly Stop All Hyperion Planning components HypApp 1. To stop Hyperion Planning you must log on to the HypApp server using an account that has Administrator privileges. All the System Analysts in the ERP group have the ability to log on to the servers using their own network id. 2. Execute the d:\commandScripts\StopServices.bat file. This will take approximately 13 minutes to complete. The script creates a log file when it runs. The log file can be found at \\hypapp\d$\coa\logs\StopServices.log NOTE: if the services are already stopped you can skip this step. You can perform the remaining steps to verify that the services are indeed stopped. If you find that services are still running then come back and run this stop script. It won’t matter if you run the stop script and everything is already stopped. 3. Verify that the services are stopped by opening the ”Administrative tools->Services” utility window from the “Start” button on bottom left. 4. Verify that all of the 14 “Hyperion xxxxxxxxxxxx” services and 2 “Oracle xxxxxx” services are stopped (Status = Blank). See screen print below showing the services that are normally started. If any of them are running then you may have to manually stop them by selecting the service and using the right mouse button to select the “Stop” option.

Document1

Page 4

HypEss 5. Now log on to the HypEss server using an account that has Administrator privileges. All the System Analysts in the ERP group have the ability to log on to the servers using their own network id. 6. Verify that the services are stopped by opening the ”Administrative tools->Services” utility window from the “Start” button on bottom left. Document1

Page 5

7. Verify that the 2 “Oraclexxxxxx” services are stopped (Status = Blank). See screen print below showing the services that are normally started. If any of them are running then you may have to manually stop them by selecting the service and using the right mouse button to select the “Stop” option. NOTE: Even though these services are running on HypEss, the stop script resides and is invoked from HypApp.

 Explicitly Start All Hyperion Planning components After you have executed the steps listed in the section above labeled “Stop all Hyperion Planning components” you now are ready to start all of the services as outlined below.

HypEss 1. To start Hyperion Planning you must log on to the HypEss server using an account that has Administrator privileges. All the System Analysts in the ERP group have the ability to log on to the servers using their own network id. 2. Execute the d:\commandScripts\StartServices.bat file. This will take approximately 18 minutes to complete. The script creates a log file when it runs. The log file can be found at \\hypess\d$\coa\logs\StopServices.log 3. Open the ”Administrative tools->Services” utility window from the “Start” button on bottom left. 4. The Oracle services as shown above should have a “Started” status. If the status is blank then you will need to execute the steps listed for stopping Planning and starting the services again. Document1

Page 6

HypApp 5. Log on to the HypApp server using an account that has Administrator privileges. All the System Analysts in the ERP group have the ability to log on to the servers using their own network id. 6. Open the ”Administrative tools->Services” utility window from the “Start” button on bottom left. 7. Verify that all of the 14 “Hyperion xxxxxxxxxxxx” services and 3 “Oracle xxxxxx” services have a Status of “Started”. Refer back to the screen print on page 3 showing the services that are normally started. If any of them are not started (status = blank) then you will need to execute the steps listed for stopping Planning and starting the services again.

Document1

Page 7

 Stop/Start Hyperion Reporting (only) Overview When problems arise with the Hyperion Reporting tool you can first attempt to stop and restart just the reporting services. It only takes about 8 minutes to restart just the reporting services, compared to about 30 minutes to stop and restart everything. There are 2 scripts used for this purpose and can be found on the HypApp server in the d:\commandScripts folder. 1. Stop_reporting_services.bat 2. Start_reporting_services.bat

HypApp 1. To stop Hyperion Reporting you must log on to the HypApp server using an account that has Administrator privileges. All the System Analysts in the ERP group have the ability to log on to the servers using their own network id. 2. Execute the d:\commandScripts\Stop_reporting_services.bat file. This will take approximately 4 minutes to complete. 3. Verify that the services are stopped by opening the ”Administrative tools->Services” utility window from the “Start” button on bottom left. 4. Verify that all 4 “Hyperion xxxxxxxxxxxx” reporting services are stopped (Status = Blank). See screen print below showing the 4 services that should be stopped. NOTE: The service “Hyperion Financial Reporting Print…” will sometimes hang up. Before running the start script, you need to make sure this service gets stopped. If the status is “started” or “stopping” try manually stopping the service by opening a DOS command window and typing the following command: taskkill –f –im hys9frprint.exe If that doesn’t work then you will need to initiate a reboot of the server 5. After the services are stopped (assuming we did not have to reboot the server) you can start the reporting services by executing the d:\commandScripts\Start_reporting_services.bat file. 6. After this start script finishes running, once again verify that the 4 reporting services are “Started”. 7. If they did not all start properly, you can try repeating these steps again. 8. If they still did not start properly, you should try stopping and and starting all Hyperion planning components.

Document1

Page 8

Document1

Page 9