This post is the result of packaging two installations from Oracle that setup Excel Addins.
Oracle Hyperion Smart View for Office, Fusion Edition.msi
Oracle(R) Essbase Spreadsheet Add-in, Fusion Edition.msi
Both of these are supplied inside Installshield installation executeables from which the MSIs can be extracted.
The solutions below involve configuring the installation directory to a location under program files, instead of the default of C:\Oracle.....
Oracle Hyperion Smart View for Office, Fusion Edition.msi was relatively straightforward. This MSI could be extracted from %TEMP% in the normal way and installed using standard msiexec command lines.
The essential parts of the transform are below. It seemed to be uneasy with spaces in the path but then Windows 95 only came out 17 years ago at the time of writing.
Directory Table
ProgramFilesFolder TARGETDIR .:PROGRA~1|progra~1
Property Table
INSTALLDIR C:\Progra~1\Oracle\SmartView\
APPLPATH C:\Progra~1\Oracle\SmartView\
The smartview Excel Addin is a COM type involving the key
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\Excel\Addins\Hyperion.CommonAddin
Oracle(R) Essbase Spreadsheet Add-in, Fusion Edition.msi was tricky. Going down the normal approaches with this item resulted in a broken install. Essentially, if an attempt is made to silently excute the extracted MSI, the installation reports success but the result is a broken install. (The connect menu item will not generate a dialog.)
The only way to silently or (basic) install a working installation was to use a command line for the installation executable
Spreadsheet Add-in.exe /S /v"/qb-! TRANSFORMS=TransformName.mst BINARY=en"
This transform for this included
Property Table
ALLUSERS 1
ARBORPATH C:\Progra~1\Oracle\Middleware\EPMSystem11r1\products\ExcelAddin
ESSBASEPATH C:\Progra~1\Oracle\Middleware\EPMSystem11r1\products\ExcelAddin
INSTALLDIR C:\Progra~1\Oracle\Middleware\EPMSystem11r1
The transform design also had vbs script custom actions and an Active Setup key to automatically setup the addins for subsequently logged on users. These were not strictly necessary however without them users would have to use the provided shortcuts to register and unregister the addins for themselves.
This solution was discovered on this message board.
http://www.appdeploy.com/messageboards/tm.asp?m=83133&mpage=1&key=𔒽
Note also that installing to a 64bit platform would require a transform to have relevent values set to C:\Progra~2 which equates to the C:\Program Files (x86) location on a 64bit machine.
