Hyperion Planning Start and Stop procedures

interestsauceInternet and Web Development

Oct 31, 2013 (3 years and 10 months ago)

179 views


C:
\
Program Files
\
neevia.com
\
docConverterPro
\
temp
\
NVDC
\
B88E448D
-
AE2F
-
4906
-
A922
-
BD0964A139F8
\
interestsauce_32eda28d
-
74b9
-
495d
-
bd4d
-
69cbe9ac713b.docx

Page
1


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 Develop
ment/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 co
mponents 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 ad
vised 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 w
orking)

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

fold
er
found on each of the servers as shown below:



C:
\
Program Files
\
neevia.com
\
docConverterPro
\
temp
\
NVDC
\
B88E448D
-
AE2F
-
4906
-
A922
-
BD0964A139F8
\
interestsauce_32eda28d
-
74b9
-
495d
-
bd4d
-
69cbe9ac713b.docx

Page
2


Hyperion
P
roduction 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 approac
h 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.





C:
\
Program Files
\
neevia.com
\
docConverterPro
\
temp
\
NVDC
\
B88E448D
-
AE2F
-
4906
-
A922
-
BD0964A139F8
\
interestsauce_32eda28d
-
74b9
-
495d
-
bd4d
-
69cbe9ac713b.docx

Page
3


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 highlighte
d below and then click OK.




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_S
tart_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 t
ake about 30
minutes to complete the task.
Use F5 to refresh the task list & status.
When finished you can
close the task scheduler.








C:
\
Program Files
\
neevia.com
\
docConverterPro
\
temp
\
NVDC
\
B88E448D
-
AE2F
-
4906
-
A922
-
BD0964A139F8
\
interestsauce_32eda28d
-
74b9
-
495d
-
bd4d
-
69cbe9ac713b.docx

Page
4




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 approx
imately 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 t
he services are already stop
ped

you can skip this step. Y
ou can perform the
remaining steps to verify that the services are indeed stopped. If you find that services are
still running then come bac
k 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 o
pen
ing

the ”Administrative tools
-
>Services” utility
window from the “Start” button on bottom left.

4.

Verify that all of the 14 “Hyper
ion 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 a
nd using the right mouse butt
on to select the “Stop” option.


C:
\
Program Files
\
neevia.com
\
docConverterPro
\
temp
\
NVDC
\
B88E448D
-
AE2F
-
4906
-
A922
-
BD0964A139F8
\
interestsauce_32eda28d
-
74b9
-
495d
-
bd4d
-
69cbe9ac713b.docx

Page
5




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
ow
n network id.


C:
\
Program Files
\
neevia.com
\
docConverterPro
\
temp
\
NVDC
\
B88E448D
-
AE2F
-
4906
-
A922
-
BD0964A139F8
\
interestsauce_32eda28d
-
74b9
-
495d
-
bd4d
-
69cbe9ac713b.docx

Page
6


6.

Verify that the services are stopped by opening the ”Administrative tools
-
>Services” utility
window from the “Start” button on bottom left.

7.

Verify that the
2

“Oraclexxxxxx” services are stopped (Status = Blank). See screen print
below sho
wing 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 Hy
pEss, the stop script resides and is
invoked from HypApp.






Explicitly
Start All Hyperion Planning components


After you have

execute
d

the steps
listed in the section above labeled “Stop all Hyperion
Planning components”

you

now

are rea
dy 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.


C:
\
Program Files
\
neevia.com
\
docConverterPro
\
temp
\
NVDC
\
B88E448D
-
AE2F
-
4906
-
A922
-
BD0964A139F8
\
interestsauce_32eda28d
-
74b9
-
495d
-
bd4d
-
69cbe9ac713b.docx

Page
7


4.

The Oracle services as shown
above

should have a “Started” status
. If the status is blank

then you will need to execute the ste
ps listed for stopping Planning and starting the services
again.




HypApp

5.

Log on to the HypApp server using an account that has Adm
inistrator 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 o
f “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.









C:
\
Program Files
\
neevia.com
\
docConverterPro
\
temp
\
NVDC
\
B88E448D
-
AE2F
-
4906
-
A922
-
BD0964A139F8
\
interestsauce_32eda28d
-
74b9
-
495d
-
bd4d
-
69cbe9ac713b.docx

Page
8





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 t
he 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” utilit
y
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 R
eporting Print…” will sometimes hang up. Before running the start
script, you need to make sure thi
s service gets stopped. If the status

is “started” or
“stopping” try manually stopping the service
by opening a DOS command window and
typing the foll
owing command:
taskkill

f

im hys9frprint.exe
If that doesn’t work then
you will need to
initiate a reboot of the server


5.

Af
t
er

the services are stopped (assuming we did not have to reboot the server) you can start
the reporting services by execu
ting

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 s
till did not start properly, you should try stopping and and starting all Hyperion
planning components.



C:
\
Program Files
\
neevia.com
\
docConverterPro
\
temp
\
NVDC
\
B88E448D
-
AE2F
-
4906
-
A922
-
BD0964A139F8
\
interestsauce_32eda28d
-
74b9
-
495d
-
bd4d
-
69cbe9ac713b.docx

Page
9