This method installs Operations Center without opening the Installation Wizard. It takes all of the default values and run silently in the background. A response file can be used to supply predefined values including:
Options from the installation wizard
Licensing information from the license file
Configuration Manager settings
A configuration stored in the Configuration Storage data source
This method is intended for when you need to rerun the installation often, such as in a test environment.
You can run a silent installation on a Unix machine without having an X Window system set to display graphical (X client) applications on the local X server display. However, you will still need the local X server display to open the Configuration Manager on that machine.
For more information about the Configuration Manager and configurations and the Configuration Storage data source, see the Operations Center Server Configuration Guide.
Use the following sections to run an unattended installation:
To run an unattended installation:
To install Operations Center, do one of the following:
Windows: Insert the Operations Center Dashboard Installation CD and from the directory where the installation executable file resides, type install.bat -i silent at a command prompt.
Unix: Create a home directory for the installation, mount the Operations Center Dashboard Installation CD, then from the directory where the installation executable file resides, type install.sh -i silent at a command prompt.
Default install options are used to complete the installation.
After the unattended installation has completed, continue with Section 2.2.3, Configuring the Dashboard Database.
To run an unattended installation:
To install Operations Center, do one of the following:
Windows: Insert the Operations Center Installation CD and from the directory where the installation executable file resides, type install.bat -i silent at a command prompt.
Unix: Create a home directory for the installation, mount the Operations Center Installation CD, then from the directory where the installation executable file resides, type install.sh -i silent at a command prompt.
Default install options are used to complete the installation.
After the unattended installation has completed, continue with Section 2.2.3, Configuring the Dashboard Database.
To run an unattended installation with a response file:
Because there are multiple ways to create a response file, depending on the content you want to include, do one of the following:
To create a response file that includes the options from the installation wizard, licensing information, configuration manager settings, and a configuration stored in the Configuration storage data source, at a command prompt on the machine that has the existing Dashboard installation that you want to use, enter the following:
java -classpath Dashboard_Installation_Directory/lib/Customizer.jar com.mosol.install.myMOInstallerResponseFile responsefile.rsp Installation_Directory
replacing responsefile with the name of the response file to be created and Installation_Directory with the installation directory for the existing Dashboard installation.
For example, type:
java -classpath C:/Dashboard_Installation_Directory/lib/Customizer.jar com.mosol.install.myMOInstallerResponseFile C:/moresponse.rsp C:/ OperationsCenter_Dashboard_Install_Path/
to create a response file called moreresponse.rsp that uses the Dashboard installation located in the C:/ directory.
To create a response file that includes installation wizard options only, run a wizard-based or console installation by typing the following at a command prompt:
install.bat –i install method –r filename for Windows where install method is the installation method (either GUI or console) and filename is the name of the response file, such as myinstall.rsp.
install.sh –i install method –r filename for Unix where install method is the installation method (either GUI or console) and filename is the name of the response file, such as myinstall.rsp.
When a response file is created, it is saved in the Dashboard installation directory.
Copy the response file to the server where want to install the Dashboard.
If necessary, edit the file using a text editor. Some changes that you can make include:
Adding licensing information
Changing configuration settings
Modifying the configuration from the Configuration Storage data source
To use the response file to install the Dashboard, do one of the following:
Windows: Insert the Dashboard Installation CD and from the directory where the installation executable file resides, type install.bat -i silent -f filename.rsp at a command prompt replacing filename with the name of the response file.
Unix: Create a home directory for the installation, mount the Dashboard Installation CD, then from the directory where the installation executable file resides, type install.sh -i silent -f filename.rsp at a command prompt replacing filename with the name of the response file.
The options in the response file are used to automatically complete the installation.
After the unattended installation has completed, continue with Section 2.2.3, Configuring the Dashboard Database.
Use the response file during the process of performing a silent installation of the Dashboard on a different machine. The installation uses the options in the response file to automatically complete the installation wizard.
To install the Dashboard using the response file:
Copy the response file to the machine where you want to install the Dashboard.
If necessary, edit the response file using a text editor.
Perform a silent installation, enter the following at a command prompt:
Windows: install.bat –i silent –f filename.rsp
where filename is the name of the response file (such as myinstall.rsp).
UNIX: install.sh –i silent –f filename.rsp
where filename is the name of the response file (such as myinstall.rsp).
This section contains a sample response file for a the Dashboard installation, which is a standard ASCII text file. Response files are created from an actual installation of the product, giving you default values that are determined by that installation.
Because a response file’s content contains very few carriage returns, the following sample’s content is word-wrapped automatically where the documentation program can break a long string, such as at spaces, forward slashes, or certain characters. For example, in a text editor with word-wrap turned off, this sample response file contains 5 lines, one of which contains most of the content.
#Thu Feb 07 10:46:06 EST 2008 LICENSE_CONTENTS= CONFIGURATIONS_CONTENTS= USER_INSTALL_DIR=C\:\\myMOFeb7_Clone0 CUSTOMIZE_PROPERTIES_CONTENTS=<config>\n <properties>\n <entry>\n <string>MOCommunicationsMode</string>\n <string>https</string>\n </entry>\n <entry>\n <string>MyMORMICache</string>\n <string>false</string>\n </entry>\n <entry>\n <string>MOServerHost</string>\n <string>dhendricks</string>\n </entry>\n <entry>\n <string>JavaHome</string>\n <string>C\:\\Documents and Settings\\sshetty\\Local Settings\\Temp\\I1202399004\\Windows\\resource\\jre</string>\n </entry>\n <entry>\n <string>MymoLogLevel</string>\n <string>WARN</string>\n </entry>\n <entry>\n <string>MOSqlServerPort</string>\n <string>7560</string>\n </entry>\n <entry>\n <string>MymoLogInfo</string>\n <string>FILE "C\:\\myMOFeb7\\logs\\dashboard.trc" SIZE 5000000 RENAME "C\:\\myMOFeb7\\logs\\mymo.%36datetime.trc"</string>\n </entry>\n <entry>\n <string>MOImageServerPort</string>\n <string>7002</string>\n </entry>\n <entry>\n <string>LocalDomain</string>\n <string>localdomain</string>\n </entry>\n <entry>\n <string>MyMOWebServerPort</string>\n <string>7081</string>\n </entry>\n <entry>\n <string>HttpsCommentEnd</string>\n <string></string>\n </entry>\n <entry>\n <string>MyMOWebServerShutdownPort</string>\n <string>7006</string>\n </entry>\n <entry>\n <string>jvm.home</string>\n <string>C\:\\Program Files\\Java\\jre1.5.0_13</string>\n </entry>\n <entry>\n <string>MyMOCommunicationsMode</string>\n <string>bidirSSL</string>\n </entry>\n <entry>\n <string>UserName</string>\n <string>sjones</string>\n </entry>\n <entry>\n <string>MOWebServerPort</string>\n <string>7080</string>\n </entry>\n <entry>\n <string>MyMOServerPushEnabled</string>\n <string>false</string>\n </entry>\n <entry>\n <string>MORMIServerPort</string>\n <string>7099</string>\n </entry>\n <entry>\n <string>MyMOServerAlarmOperationsEnabled</string>\n <string>false</string>\n </entry>\n <entry>\n <string>InstallDir</string>\n <string>C\:\\myMOFeb7</string>\n </entry>\n <entry>\n <string>HostName</string>\n <string>djones</string>\n </entry>\n <entry>\n <string>HttpCommentEnd</string>\n <string>--></string>\n </entry>\n <entry>\n <string>HttpCommentHead</string>\n <string><\!--</string>\n </entry>\n <entry>\n <string>IpAddress</string>\n <string>192.168.10.228</string>\n </entry>\n <entry>\n <string>MyMOWebServerSSLPort</string>\n <string>7443</string>\n </entry>\n <entry>\n <string>MyMORMICacheTimeout</string>\n <string>75</string>\n </entry>\n <entry>\n <string>HttpsCommentHead</string>\n <string></string>\n </entry>\n </properties>\n</config>