How to identify the architecture (32-bit or 64-bit) of installed HFM in a machine?

INTERNAL ONLY

For corrections please mail to rajesh.x.theodore@oracle.com

METHOD 1: Reference: KB Article (1275540.1) Following method will help to identify if 64-bit HFM is installed in 64-bit server. 1. Check the file name of HFMErrorLogViewer_x64.exe and HFMErrorLookup_x64.exe under <HYPERION_HOME>\products\FinancialManagement\Consultant Utilities which will be having _x64 along with it. 2. Check the file name of HfmCopyApplication_x64.exe, HfmCopyAppCmd_x64.exe, HFMCopyAppLib_x64.dll, AccessLayer_X64.dll, DataLayer_X64.dll, HFMbdb-x64-43.dll, HsvDSMetadata2_x64.dll, under <HYPERION_HOME\products\FinancialManagement\Server which will be having _x64 along with it. 3. Check the file name vcredist_x64.exe, HatEx_x64.exe and HFM_xercesc_x64_2_4_0.dll under <HYPERION_HOME>\ products\FinancialManagement\Common which will be having _x64 along with it. 4. Check the file name HFM_xerces-c_x64_2_4_0.dll under <HYPERION_HOME>\products\FinancialManagement\Client which will be having _x64 along with it. 5. Working folder created for each application under <HYPERION_HOME>\products\FinancialManagement\Server Working Folder will have X64 in it. Example: HFM11113X64_WorkingData_<APP_NAME> NOTE: 1. If the above file names do not have x64 then the HFM installation is 32 bit in 64-bit server. 2. 64-bit HFM cannot be installed in 32-bit server. 3. .EXE files listed above will work even if it is renamed. But if the DLL files are renamed it will cause issue in HFM functioning. So the architecture can be identified through the above DLL file names.

Rajesh Theodore G

Method 2: NOTE: Third Party tool. Should be used at your own risk. Take backup of the DLL before testing. 1. Download Dependency Walker tool as per your operating system architecture from http://www.dependencywalker.com/ 2. Extract the tool in the machine and execute depends.exe file 3. Select FILE OPEN and select any DLL file from <HYPERION_HOME>\products\FinancialManagement\ 4. Check for the DLL file name in CPU column. This will list the architecture of the DLL. In this case its x64. If the installed HFM is a 32 bit software then the selected DLL file will be shown as an x86 (32 bit) under the CPU column.

Rajesh Theodore G

4. Following screen print is taken from 32-bit installation of GTALK in 64-bit server. 32-bit GTALK DLL is used for testing.

Rajesh Theodore G