Strategy ONE
OEM Silent Installations
You can use silent installation to easily embed Strategy One products with other applications. The steps below show you how to use a silent installation to deploy an OEM application on a Windows environment. For additional information on silent installations, see Automated Installation on Windows.
You can follow the steps below to perform a silent installation on a Windows environment. To perform a silent installation on a Linux environment, see Silent Installation.
Ensure that the Strategy installation files are accessible on the machine in which the installation is being performed. If a required installation file is not accessible, the installation can fail, often providing a warning about missing requirements.
To Perform an OEM Silent Installation
When Strategy One products are installed as software bundled with another product, the following procedure is strongly recommended:
-
Create an installation response file (
response.ini) for the Strategy One products to install. The table that follows shows which sections of the file are mandatory and which are optional.For detailed information regarding the contents of the
response.inifile, see Configuring a response.ini File to Install Strategy One.Response File Section
Selection
[Installer]Required
HideAllDialogs =Required
PreventReboot =Optional
StopAllServices =Optional
StopIIS =Optional
CheckRenameOperations =Optional
[UserRegistration]Required
[ComponentSelection]Required
EnterpriseManagerSelect =Required
[InitialPaths]Required
EnterpriseManager =Required Setting
HideAllDialogs = TRUEcauses the script for the response file to:Use default values as specified in the
response.inifile.Not require user input.
Keep the dialog flow consistent from one instance to the next. Consistency in the response file script from one instance to the next is necessary; if
setup.issdetects an inconsistency in the dialog flow, installation is terminated and a log file for the failure is created.The only dialog flow modifications pertinent to silent installation are specific to file location. Therefore, the only portion of the
response.inithat may need to be modified is the[InitialPaths]section.The rest of this procedure assumes you have saved the
response.inifile to the file pathC:\. If you save it to another file path, replaceC:\response.iniwith the file path of yourresponse.inifile.You must save the
response.inifile as ANSI encoding. -
Create the
setup.issfile to use in conjunction with theresponse.inifile for the silent installation. Use a text editor to create thesetup.issfile with the following information:Copy[InstallShield Silent]
Version=v7.00
File=ResponseFile
[File Transfer]
OverwrittenReadOnly=NoToAll
[Application]
Name=MicroStrategy
Version=x.y.z
#x.y.z represent the version of the MicroStrategy platform
Company=MicroStrategy
Lang=LanguageValue
[{8CCF3F6C-55B7-4A27-8C68-ADF21D0585A2}-DlgOrder]
Count=0You must save the
setup.issfile as ANSI encoding.The version in the
setup.issfile must match the Strategy version you are installing exactly. For example, if you are installing version 10.7.0 you must enterVersion=10.7.0. Entering a version asVersion=10orVersion=10.7.xcauses an error when trying to perform a silent installation of version 9.3.0.For an explanation of the
LanguageValueparameter within the lineLang=LanguageValue, see Language Settings for Silent Installations. -
From the Windows Start menu, select Programs, then select Accessories, and then right-click Command Prompt and select Run as Administrator. The User Account Control dialog box opens.
The steps to open a Windows command prompt with administrator privileges may be different depending on your version of Windows.
- Click Yes to open the command prompt with administrator privileges. The command prompt is displayed.
-
Run the silent install with the
response.inifile in conjunction with thesetup.issfile as follows:For an explanation of the
LanguageValueparameter, see Language Settings for Silent InstallationsINSTALL_PATH\setup.exe -LLanguageValue--ResponseFile="C:\response.ini" -s -f1"c:\setup.iss" -f2"c:\setup.log"In the syntax shown above, the
-sparameter indicates that the installation is to be completely silent. If the-sparameter is not included in the command, then an interface is displayed during the installation that shows the progress of the installation.If the setup program encounters an invalid value for an installation requirement, the setup terminates and the silent installation is ended. You can review any errors in the
setup.logfile. - If a restart is required after the installation is complete, a restart of the machine is automatically triggered. Power the machine back on to allow for the completion of any configurations that are required after the restart of the machine.
- After the installation is complete, you can check the result of the installation process. If the silent installation is successful, the resulting code value is zero (
ResultCode=0) in thesetup.logfile. This is the only indication of the installation being completed if the installation is completely silent and a restart of the machine is not required.
Language Settings for Silent Installations
In the final steps of the procedure to run an OEM silent installation:
- You can set MicroStrategy Developer language settings by setting the language value in the
setup.issfile. - You can bypass the language prompt by running
setup.exewith the command line option for the language.
The following table lists the values for the different languages that Strategy supports:
|
Language |
Value |
|
|
0006 |
|
|
0019 |
|
|
0009 |
|
|
0012 |
|
|
0007 |
|
|
0016 |
|
|
0017 |
|
|
0018 |
|
|
0022 |
|
|
2052 |
|
|
0010 |
|
|
0029 |
|
|
1028 |
For example, to select English as the language:
- For the setup.iss file, change
Lang=LanguageValueto:Lang=0009 - To run the silent install, use the command line option as follows:
Path\setup.exe -L0009
For the command line option, you must type -L in front of the language code to signify that you are entering a language.
