Essbase Migration

Essbase Migration

1 . Using LCM:

     Using LCM, we can export Essbase application artifacts from Source and import into Target.

• Export artifacts from Source 
• Find import_export folder in Source, copy and paste into same import_export folder in Target Environment
• Import artifacts from Target.

2. Without LCM:

• Stop Essbase application
• We can copy Essbase application from Source and paste into Target.
• Restart Essbase application
• In this way, we can copy application with data. No need to do restructure.

3. Using Migration wizard from EAS Console:

• After launching EAS console, Add Source and Target Essbase Servers and expand applications
• Launch Migration wizard and select Source and Target environments, click Next
• Select Source and Target applications and Click Next
• Verify migration artifacts which you want migrate and Click Finish 

Note: Check Replace option if you want to overwrite existing objects.

For first time migration, check out below link:
http://www.oracle.com/technetwork/middleware/performance-management/tutorials/essbaselcm-obe-101974.html

Thanks,

Mady

Hyperion Support Activities

Hyperion Support Activities

1. Essbase migration
2. Planning migration
3. HFM migration
4. FDM migration
5. FDMEE migration
6. Reports migration ( FR, Web Analysis, IR etc)
7. HSS Security migration
8. Application Security 
9. MSAD Configuration
10. Smart view netcount settings update
11. EAS console - java issue
12. planning not sync with security issue
13. FDM control tables not showing up target application
14. Big IP Urls
15. Smart view issues - User complaints
16. Startup document doesn't exist error while opening Workspace

Hyperion Log File Location

Hyperion Log File Location

D:\Oracle\Middleware\user_projects\domains\EPMSystem\servers\FoundationServices*\logs\SharedServices_Admin.log

D:\Oracle\Middleware\user_projects\domains\EPMSystem\servers\FinancialReporting*\logs\FRLogging.log

D:\Oracle\Middleware\user_projects\domains\EPMSystem\servers\FinancialReporting*\logs\FinancialReporting*.log

D:\Oracle\Middleware\user_projects\domains\EPMSystem\servers\CalcMgr*\logs\CalcMgr*.log

D:\Oracle\Middleware\user_projects\domains\EPMSystem\servers\FoundationServices*\logs\FoundationServices*.log

D:\Oracle\Middleware\user_projects\domains\EPMSystem\servers\FoundationServices*\logs\SharedServices_Admin.log

D:\Oracle\Middleware\user_projects\domains\EPMSystem\servers\FoundationServices*\logs\SharedServices_Audit.log

D:\Oracle\Middleware\user_projects\domains\EPMSystem\servers\FoundationServices*\logs\SharedServices_Bpmui.log

D:\Oracle\Middleware\user_projects\domains\EPMSystem\servers\FoundationServices*\logs\SharedServices_Bpmui_Config.log

D:\Oracle\Middleware\user_projects\domains\EPMSystem\servers\FoundationServices*\logs\SharedServices_Bpmui_Sec.log

D:\Oracle\Middleware\user_projects\domains\EPMSystem\servers\FoundationServices*\logs\SharedServices_CMSClient.log

D:\Oracle\Middleware\user_projects\domains\EPMSystem\servers\FoundationServices*\logs\SharedServices_Hub.log

D:\Oracle\Middleware\user_projects\domains\EPMSystem\servers\FoundationServices*\logs\SharedServices_LCM.log

D:\Oracle\Middleware\user_projects\domains\EPMSystem\servers\FoundationServices*\logs\SharedServices_Registry.log

D:\Oracle\Middleware\user_projects\domains\EPMSystem\servers\FoundationServices*\logs\SharedServices_Security.log

D:\Oracle\Middleware\user_projects\domains\EPMSystem\servers\FoundationServices*\logs\SharedServices_TaskFlow.log

D:\Oracle\Middleware\user_projects\domains\EPMSystem\servers\FoundationServices*\logs\Workspace.log

D:\Oracle\Middleware\user_projects\domains\EPMSystem\servers\FoundationServices*\logs\WorkspaceConfig.log

D:\Oracle\Middleware\user_projects\domains\EPMSystem\servers\RaFramework*\logs\RaFramework*.log

D:\Oracle\Middleware\user_projects\domains\EPMSystem\servers\ErpIntegrator*\logs\ErpIntegrator*.log

D:\Oracle\Middleware\user_projects\domains\EPMSystem\servers\EpmaDataSync*\logs\EpmaDataSync*.log

D:\Oracle\Middleware\user_projects\domains\EPMSystem\servers\EpmaWebReports*\logs\EpmaWebReports*.log

D:\Oracle\Middleware\user_projects\domains\EPMSystem\servers\AnalyticProviderServices*\logs\AnalyticProviderServices*.log

D:\Oracle\Middleware\user_projects\domains\EPMSystem\servers\EssbaseAdminServices*\logs\easserver.log

D:\Oracle\Middleware\user_projects\domains\EPMSystem\servers\EssbaseAdminServices*\logs\EssbaseAdminServices*.log

D:\Oracle\Middleware\user_projects\domains\EPMSystem\servers\Planning*\logs\Planning*.log

D:\Oracle\Middleware\user_projects\epmsystem1\diagnostics\logs\hfm\hfm.odl.log

D:\Oracle\Middleware\user_projects\epmsystem1\diagnostics\logs\hfm\HsvEventLog.log

D:\Oracle\Middleware\user_projects\epmsystem1\diagnostics\logs\hfm\InteropJava.log

D:\Oracle\Middleware\user_projects\epmsystem1\diagnostics\logs\registry\registry.log

D:\Oracle\Middleware\user_projects\epmsystem1\diagnostics\logs\ReportingAnalysis\stdout_console_servlets.log

D:\Oracle\Middleware\user_projects\epmsystem1\diagnostics\logs\services\HyS9CALC-syserr.log

D:\Oracle\Middleware\user_projects\epmsystem1\diagnostics\logs\services\HyS9CALC-sysout.log

D:\Oracle\Middleware\user_projects\epmsystem1\diagnostics\logs\services\HyS9FinancialManagementWebSvcs-syserr.log

D:\Oracle\Middleware\user_projects\epmsystem1\diagnostics\logs\services\HyS9FinancialManagementWebSvcs-sysout.log

D:\Oracle\Middleware\user_projects\epmsystem1\diagnostics\logs\services\HyS9FoundationServices-syserr.log

D:\Oracle\Middleware\user_projects\epmsystem1\diagnostics\logs\services\HyS9FoundationServices-sysout.log

D:\Oracle\Middleware\user_projects\epmsystem1\diagnostics\logs\services\HyS9FRReports-syserr.log

D:\Oracle\Middleware\user_projects\epmsystem1\diagnostics\logs\services\HyS9FRReports-sysout.log

D:\Oracle\Middleware\user_projects\epmsystem1\diagnostics\logs\services\HyS9RaFramework-syserr.log

D:\Oracle\Middleware\user_projects\epmsystem1\diagnostics\logs\services\HyS9RaFramework-sysout.log

D:\Oracle\Middleware\user_projects\epmsystem1\diagnostics\logs\services\HyS9aifWeb-syserr.log

D:\Oracle\Middleware\user_projects\epmsystem1\diagnostics\logs\services\HyS9aifWeb-sysout.log

D:\Oracle\Middleware\user_projects\epmsystem1\diagnostics\logs\services\HyS9FinancialManagementWebSvcs-syserr.log

D:\Oracle\Middleware\user_projects\epmsystem1\diagnostics\logs\services\HyS9FinancialManagementWebSvcs-sysout.log

D:\Oracle\Middleware\user_projects\epmsystem1\diagnostics\logs\ReportingAnalysis\stdout_console_default.log

D:\Oracle\Middleware\user_projects\epmsystem1\diagnostics\logs\ReportingAnalysis\agent.log

D:\Oracle\Middleware\user_projects\epmsystem1\diagnostics\logs\ReportingAnalysis\configuration_messages_default.log

D:\Oracle\Middleware\user_projects\epmsystem1\diagnostics\logs\ReportingAnalysis\eiengine.log

D:\Oracle\Middleware\user_projects\epmsystem1\diagnostics\logs\ReportingAnalysis\server_messages.log

D:\Oracle\Middleware\user_projects\epmsystem1\diagnostics\logs\ReportingAnalysis\server_messages_AdministrationServlet.log

D:\Oracle\Middleware\user_projects\epmsystem1\diagnostics\logs\ReportingAnalysis\server_messages_AnalyticBridgeService.log

D:\Oracle\Middleware\user_projects\epmsystem1\diagnostics\logs\ReportingAnalysis\server_messages_AuthenticationService.log

D:\Oracle\Middleware\user_projects\epmsystem1\diagnostics\logs\ReportingAnalysis\server_messages_AuthorizationService.log

D:\Oracle\Middleware\user_projects\epmsystem1\diagnostics\logs\ReportingAnalysis\server_messages_BrowseServlet.log

D:\Oracle\Middleware\user_projects\epmsystem1\diagnostics\logs\ReportingAnalysis\server_messages_CommonServices.log

D:\Oracle\Middleware\user_projects\epmsystem1\diagnostics\logs\ReportingAnalysis\server_messages_CSSSynchronizer.log

D:\Oracle\Middleware\user_projects\epmsystem1\diagnostics\logs\ReportingAnalysis\server_messages_DataAccessServlet.log

D:\Oracle\Middleware\user_projects\epmsystem1\diagnostics\logs\ReportingAnalysis\server_messages_EventService.log

D:\Oracle\Middleware\user_projects\epmsystem1\diagnostics\logs\ReportingAnalysis\server_messages_GSM.log

D:\Oracle\Middleware\user_projects\epmsystem1\diagnostics\logs\ReportingAnalysis\server_messages_HarvesterService.log

D:\Oracle\Middleware\user_projects\epmsystem1\diagnostics\logs\ReportingAnalysis\server_messages_iHTMLServlet.log

D:\Oracle\Middleware\user_projects\epmsystem1\diagnostics\logs\ReportingAnalysis\server_messages_JobManagerServlet.log

D:\Oracle\Middleware\user_projects\epmsystem1\diagnostics\logs\ReportingAnalysis\server_messages_JobService.log

D:\Oracle\Middleware\user_projects\epmsystem1\diagnostics\logs\ReportingAnalysis\server_messages_LoggingService.log

D:\Oracle\Middleware\user_projects\epmsystem1\diagnostics\logs\ReportingAnalysis\server_messages_LSM.log

D:\Oracle\Middleware\user_projects\epmsystem1\diagnostics\logs\ReportingAnalysis\server_messages_PersonalPagesServlet.log

D:\Oracle\Middleware\user_projects\epmsystem1\diagnostics\logs\ReportingAnalysis\server_messages_PublisherService.log

D:\Oracle\Middleware\user_projects\epmsystem1\diagnostics\logs\ReportingAnalysis\server_messages_RepositoryService.log

D:\Oracle\Middleware\user_projects\epmsystem1\diagnostics\logs\ReportingAnalysis\server_messages_SearchIndexing.log

D:\Oracle\Middleware\user_projects\epmsystem1\diagnostics\logs\ReportingAnalysis\server_messages_SearchKeywordProvide.log

D:\Oracle\Middleware\user_projects\epmsystem1\diagnostics\logs\ReportingAnalysis\server_messages_SearchMonitor.log

D:\Oracle\Middleware\user_projects\epmsystem1\diagnostics\logs\ReportingAnalysis\server_messages_ServiceBroker.log

D:\Oracle\Middleware\user_projects\epmsystem1\diagnostics\logs\ReportingAnalysis\server_messages_SessionManager.log

D:\Oracle\Middleware\user_projects\epmsystem1\diagnostics\logs\ReportingAnalysis\server_messages_TransformerService.log

D:\Oracle\Middleware\user_projects\epmsystem1\diagnostics\logs\ReportingAnalysis\server_messages_UsageService.log

D:\Oracle\Middleware\user_projects\epmsystem1\diagnostics\logs\ReportingAnalysis\stdout_console_agent.log

D:\Oracle\Middleware\user_projects\epmsystem1\diagnostics\logs\FinancialReporting\FRPrintLogging.log

D:\Oracle\Middleware\user_projects\epmsystem1\diagnostics\logs\epma\datasync.log

D:\Oracle\Middleware\user_projects\epmsystem1\diagnostics\logs\epma\dimensionServer.log

D:\Oracle\Middleware\user_projects\epmsystem1\diagnostics\logs\epma\NetJNIBridge.log

D:\Oracle\Middleware\user_projects\epmsystem1\diagnostics\logs\services\HyS9EPMADataSynchronizer-syserr.log

D:\Oracle\Middleware\user_projects\epmsystem1\diagnostics\logs\services\HyS9EPMADataSynchronizer-sysout.log

D:\Oracle\Middleware\user_projects\epmsystem1\diagnostics\logs\services\HyS9EPMAWebTier-syserr.log

D:\Oracle\Middleware\user_projects\epmsystem1\diagnostics\logs\services\HyS9EPMAWebTier-sysout.log

D:\Oracle\Middleware\user_projects\epmsystem1\diagnostics\logs\services\FRPrintService.Err.log

D:\Oracle\Middleware\user_projects\epmsystem1\diagnostics\logs\services\FRPrintService.Out.log

D:\Oracle\Middleware\user_projects\epmsystem1\diagnostics\logs\services\HyS9RaFrameworkAgentErr.log

D:\Oracle\Middleware\user_projects\epmsystem1\diagnostics\logs\services\HyS9RaFrameworkAgentOut.log

D:\Oracle\Middleware\user_projects\epmsystem1\diagnostics\logs\services\HyS9aps-syserr.log

D:\Oracle\Middleware\user_projects\epmsystem1\diagnostics\logs\services\HyS9aps-sysout.log

D:\Oracle\Middleware\user_projects\epmsystem1\diagnostics\logs\services\HyS9eas-syserr.log

D:\Oracle\Middleware\user_projects\epmsystem1\diagnostics\logs\services\HyS9eas-sysout.log

D:\Oracle\Middleware\user_projects\epmsystem1\diagnostics\logs\services\HyS9Planning-syserr.log

D:\Oracle\Middleware\user_projects\epmsystem1\diagnostics\logs\services\HyS9Planning-sysout.log

D:\Oracle\Middleware\user_projects\epmsystem1\diagnostics\logs\hfm\HsvEventLog.log

D:\Oracle\Middleware\user_projects\epmsystem1\diagnostics\logs\hfm\hfm.odl.log

D:\Oracle\Middleware\user_projects\epmsystem1\diagnostics\logs\hfm\InteropJava.log'

D:\Oracle\Middleware\user_projects\epmsystem1\httpConfig\ohs\diagnostics\logs\OHS\ohs_component\access_log

D:\Oracle\Middleware\user_projects\epmsystem1\httpConfig\ohs\diagnostics\logs\OHS\ohs_component\console~OHS~*.log

D:\Oracle\Middleware\user_projects\epmsystem1\httpConfig\ohs\diagnostics\logs\OHS\ohs_component\ohs_component.log

Let's focus on how to sift through the logs more quickly: 

Types of logs: 

1.    WebLogic Application Logs

These logs come from a web deployment and are located in the domains folder:

D:\Oracle\Middleware\user_projects\domains\EPMSystem\servers

2.    EPM Application Logs

once the service or application server is started properly, its internal logging takes over using the Oracle ODL logging framework. These log files are typically in the diagnostics folder, but may also reside in the domains folder or elsewhere based on the ODL configuration.

D:\Oracle\Middleware\user_projects\epmsystem1\diagnostics\logs

WebLogic Service Not Starting

For web application based services check out the specific WebLogic application log under the domains folder. If the web app is not able to start correctly, chances are it is not writing the EPM application logs because the logger was not initialized or the underlying service never came up. In the Application server log you will see the server go through different states like STATE_PREPARED, etc. During these phases the application does things like setup JDBC connections to the database and tries to initialize its services based on configuration details within the HSS registry. The server is available once you see a message like "server started in PRODUCTION mode".

Workspace Errors after Logging On

Workspace has two components required to log on, the Framework Services and the Framework/Foundation Web Services. For the Web components check the domain logs for Framework and Foundation.

However, the Agent services must start correctly, Check for the message "Giving control to the ORB" in the log:

D:\Oracle\Middleware\user_projects\epmsystem1\diagnostics\logs\ReportingAnalysis\stdout_console_default.log

Typically, if BI will not start - some type of exception is generated during the AGENT start up in stdout_contsole*.log

Errors in a Running Service

Usually once a web service has been started the domain logs become less important because the EPM application logging starts to take over. Assuming the service has started check for the EPM Applicaiton logs in the diagnostics folder for the particular product as the WebLogic Application log usually stops giving useful messages after "server started in PRODUCTION mode".

HFM Logs

HFM has historically been an outlier with respect to log setup. The best place to look for HFM specific errors is to use the HFMErrorLogViewer utility. This utility accumulates and formats the somewhat cryptic messages left in the Windows Registry and the HFM Database for human readable display. Remember, if you have the HFM Web service on a different node than the HFM Application node - the web server HFMErrorLogViewer might have different information.

In 11.1.2.2 HFM has a WebLogic component so look in the domain logs.

FDM Logs

FDM is an IIS deployed application. It logs generic errors to the Windows Registry. During run-time specific operations like loads may generate specific log messages. The log files are viewable by selecting the log file in the FDM web menu. Additionally this log file can be found by searching for *.log within the FDM Application's share directory, prefixed with the username of the user running the operation. Additional logging regarding adapter messages can be coaxed out by setting logging levels with the adapter settings for things like ERPI.

Additional information regarding troubleshooting using the logs can be found in my other posts:

Oracle-EPM-Troubleshooting-and-Debugging-Guide-(Part-1-of-2)

Oracle-EPM-Troubleshooting-and-Debugging-Guide-(Part-2-of-2)

Collected from https://epm-errors.blogspot.in/2013/01/epm-log-files-revisited.html

Thanks,

Mady

Commands which will useful in Troubleshooting

To get Linux 64-bit or 32-bit along with kernel info: uname -a

To check port number listening or not: netstat -an|grep <port>

To check Linux version if it is REDHAT: cat /etc/redhat-release

To check Linux version: cat /etc/system-release

To check process: ps -ux  

To check process ps -ef    

To check Hyperion services: ps -ef | grep oracle  

To check system up-time, CPU, RAM usage: top

To check time and date: date

To Check File size: du -sh Foldername

To check disk space all mount points: df –h 

To start weblogic as back end process: nohup ./startweblogic.sh &

To check log file: tail -f nohup.out

To check Port number status: netstat -an | grep 19000

To check Port Status using PowerShell : Test-NetConnection -ComputerName <Host Name> -Port <Number>

Thanks,
Mady

Planning application Migration with LCM export

Planning application Migration with LCM export

1.      Export planning application with all artifacts from Source server using LCM

2.      Copy that exported folder from source Import_Export location.

3.      Paste the same into target Import_Export location.

4.      Take backup of the same folder and then start doing the changes.

5.      Find the import.xml file and change application name if it is different name.

6.      Import.xml will be in 2 places in latest version (in my case 11.1.2.3)

7.      Find ApplicationDefination file, and do changes. We can find change:

a.      Data Source name

b.      Application name

c.      Start year

d.      No. of years. (Whatever we find in this file we can change which we can’t after application created.

8.      Select artifacts to import. If you okay security import, then select all artifacts otherwise uncheck security and import the application.

9.      In New versions, from 11.1.2.x no need to create application to import the application. If application is not there, LCM will create the application.
Note: Application will detect from changes which we made in import.xml files.

10.   Click on import and check Migration status.

11.   If it is successful, then check the application. If it is failed, check out the errors and try to resolve them and do migration again.

12.   Planning application import completed.

Thank you all…!!

How to Start and Stop Financial Management (HFM) Server Windows Processes

           Start and Stop HFM Server Windows Processes

How to Start and Stop Financial Management (HFM) Server Windows Processes
What are the main Windows processes of an HFM application server?
What happens when I start the HFM Windows Service?
What happens when I stop the HFM Windows Service?
Why should I use the HFM Windows Service?
When should I not use the HFM Windows Service?
Allowing HFM to start and stop as needed.
Why do I see multiple HsvDataSource.exe processes on an HFM application server?
When does the HsvDataSource.exe process stop itself?
Why might the HsvDataSource.exe not stop by itself?
What is the CASSecurity.exe process?
In what order should the HFM processes be stopped?

-------------------------------------------------------------------------------------------------------------------------------------------------------------------

How to Start and Stop Financial Management (HFM) Server Windows Processes
What are the main Windows processes of an HFM application server?
The main Windows processes of a HFM application server are HsxService.exe, HsxServer.exe, CASSecurity.exe and HsvDatasource.exe.


What happens when I start the HFM Windows Service?
Oracle's Hyperion Financial Management can be started by starting the Windows Service "Hyperion Financial Management - Management Service". When this service is started, a process called HsxService.exe will become visible in the Windows Task Manager, and will remain running until the Windows Service is stopped. The HsxServer.exe, CASSecurity.exe and HsvDataSource.exe processes are also started.


What happens when I stop the HFM Windows Service?
When the Hyperion Financial Management Windows service is stopped, the HsxService.exe process will be stopped along with the HsvDataSource.exe, CASSecurity.exe and HsxServer.exe processes.

Why should I use the HFM Windows Service?
Oracle typically recommends that customers use the Windows Service approach only when their individual applications within their HFM database are known to take several minutes to start up. By starting the Windows Service, the application server will pre-launch each application, which will then be "active" and already started when the first user attempts to connect to the application. In this way, the user will not experience any "delay" while logging in, due to application startup time.

Applications may take longer to start up when their metadata dimensions are very large, when an application server or database is under heavy load, or when the rules file of the application contains a slow performing "NoInput" rules section. This section may take longer to execute if it contains many loop statements through many different metadata Point of View (POV) members. Care should be taken when designing metadata and NoInput rules routines to reduce the start up time of an individual application.

When should I not use the HFM Windows Service?
A potential disadvantage of using the Windows Service approach is that all applications are started, regardless of the true requirement and usage of the end users. If there are many applications that exist in the HFM database, unnecessary memory and CPU cycles may be used launching applications which are not needed by the end users. For this reason, Oracle recommends that customers not keep unused HFM applications in production environment HFM databases, or to not use the HFM Windows Service approach if there are known unused HFM applications in the database.

Allowing HFM to start and stop as needed.
If the HFM Windows Service is not being used as above, Financial Management will start itself when end users attempt to log on to an HFM application. When any end user connects to HFM for the first time on a particular application server, the process HsxServer.exe will be started. This process builds connections to the HFM database repository, authenticates the user connecting, and returns a list of available HFM applications within the database. There will only be one HsxServer.exe process on each application server. If the end user who connected to the HFM application server then proceeds to select an HFM application name to open, the HsxServer.exe process will then launch the HsvDataSource.exe Windows process to start that application. The HsxServer.exe process will remain running until there are no users logged on to that application server and all HsvDataSource.exe processes have also stopped.

Why do I see multiple HsvDataSource.exe processes on an HFM application server?
Hyperion Financial Management opens one HsvDataSource.exe (HSVDAT~1.EXE) process on the HFM server per active application. Connections are application specific. If multiple applications are opened, multiple HsvDataSource.exe processes will be launched.

When an application is opened, a database connection pool is created between the application process and the relational database (SQL Server / Oracle / DB2 etc). However, connections are not released on an application basis - they are released on an application server basis. All connections are not released until the application server has no Financial Management users accessing any application.

When does the HsvDataSource.exe process stop itself?
When an application server determines that all users of a particular application on that application server have correctly logged off or timed out (e.g. web time out), then it sends a signal to the HsvDataSource.exe process running that application to stop itself.

When all HsvDataSource.exe processes on a particular application server have stopped themselves, then the HsxServer.exe and CASSecurity.exe processes will also be stopped. After a short delay, under normal circumstances, all HFM processes will stop themselves. Only when all HFM processes on all HFM application servers have been stopped is it safe to make changes to the relational database for example, copying applications, taking or restoring backups of the database or powering down the database. Changes to the database should NOT be made while any HsvDataSource.exe process is seen running in the Windows Task Manager.

Why might the HsvDataSource.exe not stop by itself?
If end users log off incorrectly, their sessions may not have stopped. Hyperion Reports, Financial Reporting, Web Analysis, Financial Data Quality Management, Shared Services task flows or other modules may be holding open connections to Financial Management applications. All other Hyperion processes and services which may be connecting to Financial Management should be stopped first. Financial Management administrators may like to use the "Users on System" module of Financial Management to stop end user connections. When Financial Management decides that all connections have stopped, it should proceed to shut itself down automatically.

What is the CASSecurity.exe process?
Another Windows process is CASSecurity.exe. This is a process that manages the interface between Financial Management and Hyperion Shared Services modules. It handles some of the authorization and authentication processes of HFM, as well as security related features while the application is running. Important Note: Any change in the Shared Services external provider configuration REQUIRES the CASSecurity.exe process to be recycled in order gain access to the provider changes. Follow the "In what order should the HFM processes be stopped" section.

In what order should the HFM processes be stopped?
If Financial Management appears to have frozen / crashed it may be necessary to stop the processes. Processes should be stopped in the following order:

The Hyperion Financial Management Windows Service (HsxService.exe) should be stopped via the Windows Services if it seen to be running.
The HsvDataSource.exe for each application should be shut down. Ideally it should be observed that the HsvDataSource.exe is using 00% CPU in the Windows Task Manager before it is stopped using "End Process". Care should be taken when stopping running processes.
Any CASSecurity.exe process which is still running in the Windows Task Manager should be stopped using "End Process"
If any HsxServer.exe process is still running, it should be stopped using "End Process"

CAUTION: In a multi-server environment where multiple application servers are connecting to the same relational database, the process of stopping HFM should be repeated on ALL HFM application servers before attempting to restart any HFM processes or "bring up" the applications once again. It is not recommended to stop and start any one server independently but instead to stop the whole environment and then bring it back up.

Source: How to Start and Stop Financial Management (HFM) Server Windows Processes [ID 989574.1] 

Thanks,

Mady