Using unattended (silent) mode for upgrading the SAN Volume Controller Console

The unattended (silent) mode upgrade option enables you to upgrade or reinstall the SAN Volume Controller Console installations without having to interact with the installation wizard. The unattended mode can be helpful when you have to upgrade (or reinstall) multiple SAN Volume Controller Console installations.

Before you can upgrade or reinstall the SAN Volume Controller Console and PuTTY in graphical mode, you must ensure that you have performed the following tasks:

Ensure that your system meets the hardware and software requirements that are provided in the IBM System Storage Productivity Center Introduction and Planning Guide.
Download the SAN Volume Controller Console zip file from the following Web site:
www.ibm.com/storage/support/2145

After you have downloaded the zip file, you can extract the contents and write it to a CD or you can extract the contents to a directory on your system and perform the installation tasks from that directory.
If the secure shell (SSH) client software called PuTTY is not installed on your system, you must install PuTTY so that you can use the PuTTY key generator (PuTTYgen) to generate the SSH keys needed by the installation program. You can use the putty-<version>-installer.exe file that is located in the SSHClient/PuTTY folder that is included as part of the SAN Volume Controller Console zip file to install PuTTY on your system.

During the installation process, use the unattended method of installation to customize a response file. The response file is a template that is included in the zip file.

You can also create a standard response file to ensure that the product is installed consistently on multiple systems.

The installation wizard determines if this is a reinstallation or an upgrade of the SAN Volume Controller Console. If the installation wizard determines that the SAN Volume Controller Console was previously installed on the system, it does a comparison of the current version, release, modification, and fix code level with that of the code that is currently installed on the system.

If the level is the same, this is a reinstallation.
If the new code has a higher level, it is an upgrade.
If the new code level is lower than the level on the system, the installation is invalid.

Perform the following steps to install the SAN Volume Controller Console:

Log on to the system as a local system administrator.
Perform one of the following steps:
- If you wrote the contents of the zip file to a CD, insert the CD into the drive. If you have autorun mode set on your system, the SAN Volume Controller Console program starts within 30 seconds. When the IBM® System Storage® SAN Volume Controller Console Launchpad application begins, click Exit.
- If you did not write the contents of the zip file to a CD, go the directory where you extracted the zip file.
Locate the response file (named responsefile), which is in the W2K directory. If you wrote the contents of the zip file to a CD, you must copy and paste the response file to a location on your system.
Supply a file that contains the SSH2 RSA private key for the SSH client connection. The SAN Volume Controller Console connects to the SAN Volume Controller using the Secure Shell (SSH) protocol.
The installation program copies the SSH2 RSA private key to the following location:

inst_dir\cimom\icat.ppk

Where inst_dir is the location that you will install the SAN Volume Controller Console.

For example, if you use the default location, the file is copied in the following directory:

C:\ProgramFiles\IBM\svcconsole\cimom\icat.ppk
- If you have not generated the private key file before, you can generate one now using the PuTTYgen utility. Perform the following steps to generate the private key using the PuTTYgen utility:
1. Click Start > Programs > PuTTY > PuTTYgen.
2. Select SSH2 (RSA) as the type of key to generate.
3. Click Generate.
4. Move the cursor around the blank area of the Key section to generate a random number.
5. Click Save public key. You must provide this key to the SAN Volume Controller Console in a later step.
6. Click Save private key. You must provide this key to the installation wizard using the option that is in the response file.
7. Click Yes on the PuTTYgen warning window. You have the option to set a passphrase for your key. You can enter a passphrase in the Key passphrase and Confirm passphrase fields. The passphrase is used to encrypt the key on the disk. If you choose to use a passphrase, you must enter the passphrase before you are allowed to use the key.
  Attention: Do not enter anything in the Key passphrase and Confirm passphrase fields when you generate the key pair for the IBM System Storage Productivity Center or master console.
8. Use a text editor to set the value of the <-W puttyConfiguration.puttyPrivateKeyFile> option in the response file to the name of the file that contains the PuTTY private key.
Use a text editor to modify the default options in the response file with the values that you want to supply to the installation program:
1. Remove the # character from the beginning of a line if you do not want to use the default value. Change the default value to the value that you want for that option. You must enclose all values in double quotation marks ("").
2. Use the following guidelines to activate the appropriate lines in the response file:
Note: If a response file line is active but inappropriate to the mode (new, reinstall or upgrade), it is ignored.
New Installation:
- The <-P product.installLocation> option defines the default directory where the product is to be installed. To specify a destination directory other than the default, remove the # character from the corresponding line and replace the default directory with the desired directory.
- The <-G checkPrerequisite> option checks the prerequisites. If you want to disable this option, remove the # character from the corresponding line and change the value of the option to no.
- Change the default ports values for the embedded IBM WebSphere® Application Server V6 - SVC service using the update ports variables options. If you want to change a specific port that is used for a particular WebSphere service, remove the # character from the beginning of the line that contains the value of the option and set it to the desired value. The following options are available for the embedded WebSphere ports:
  - <-W ports.portSOAP="8884">
  - <-W ports.portRMI="2809">
  - <-W ports.portHTTP="9080">
  - <-W ports.portHTTPS="9443">
- Change the default port values and default server communication type for the IBM System Storage SAN Volume Controller Pegasus Server using the following variables options:
  Note: If you want to change a specific port or the default server communication type, remove the # character from the beginning of the line containing the option's value and set it to the desired value.
  - <-W serverCommunicationConfig.httpPort="5988">
  - <-W serverCommunicationConfig.httpsPort="5989">
  - <-W serverCommunicationConfig.communicationProtocol="both">
- The <-W puttyConfiguration.puttyPrivateKeyFile> options specifies the name and location of the PuTTY private key file that the SAN Volume Controller Console software should use to connect to the SAN Volume Controller clusters. Remove the # character from the corresponding line and add the fully qualified location of the PuTTY private key file. Do not save the response file with a .txt extension.
Reinstallation or Upgrade:
- The <-G startUpgrade> option must be enabled to permit the new SAN Volume Controller Console to be reinstalled (having the same version) or upgraded (installed at a higher version). To enable this option, remove the # character from the corresponding line and change the value of the option to yes.
- The <-G stopProcessesResponse> option tells the install program if it must automatically stop SLP, IBM System Storage SAN Volume Controller Pegasus Server, and IBM WebSphere Application Server V6 - SVC services when reinstalling or upgrading the product. By default, this option is set to no. If you do not change this default value, the reinstallation or upgrade stops when these services are running. If you want to automatically stop the SLP and IBM System Storage SAN Volume Controller Pegasus Server, remove the # character from the corresponding line and change its value to yes.
- The <-G saveConfiguration> option specifies if the configuration files must be saved when reinstalling or upgrading the product. If you do not want to save the configuration files when reinstalling or upgrading, remove the # character from the corresponding line and change the value of the option to no. If you do not choose to save the configuration, you must make the following lines active or accept the default values:
  - Change the default ports values for the embedded IBM WebSphere Application Server V6 - SVC using the update ports variables options. If you want to change a specific port used for a particular WebSphere service, remove the # character from the beginning of the line that contains the value of the option and set it to the desired value. The following options are available for the embedded WebSphere ports:
    - <-W ports.portSOAP="8884">
    - <-W ports.portRMI="2809">
    - <-W ports.portHTTP="9080">
    - <-W ports.portHTTPS="9443">
  - Change the default ports values and the default server communication type for the IBM System Storage SAN Volume Controller Pegasus Server using the following variable options:
    Note: If you want to change a specific port or the default server communication type, remove the # character from the beginning of the line that contains the option's value and set it to the desired value.
    - <-W serverCommunicationConfig.httpPort="5988">
    - <-W serverCommunicationConfig.httpsPort="5989">
    - <-W serverCommunicationConfig.communicationProtocol="both">
  - The <-W puttyConfiguration.puttyPrivateKeyFile> options specifies the name and location of the PuTTY private key file that the SAN Volume Controller Console software should use to connect to the SAN Volume Controller clusters. Remove the # character from the corresponding line and add the fully qualified location of the PuTTY private key file. Do not save the response file with a .txt extension.
Issue the following command in a command prompt window to start the installation:
```
Directory\W2K\install -options response file path\responsefile
```
Where Directory is the directory of your CD drive or the directory where you extracted the zip file and response file path is the directory of the response file that you copied or extracted in step 3 and customized in step 5.

Note: The directory name, including the drive letter, can be a maximum of 44 characters.

Example 1:
You extracted the zip file to a folder called SVCCExtract on the C: drive of your system and left the response file in the W2K directory. Issue the following command to start the installation:
```
C:\SVCCExtract\W2K>install -options responsefile
```
Example 2:
You are using a CD to install the SAN Volume Controller Console. Your CD drive is E: and you copied the response file to your C: drive. Issue the following command to start the installation:
```
E:\W2K\>install -options C:\responsefile
```
The following output is displayed during the installation:
```
C:\SVCCExtract\W2K>install -options responsefile

Initializing InstallShield Wizard...
Preparing Java(tm) Virtual Machine...
............................................
............................................
............................................
............................................
```
When the install is complete, the command prompt returns.

Check the install.log file for errors. This file is initially created in the system temporary file under the subdirectory named, cimagent. After all the prerequisites checks are performed, the log file is copied to the <dest-path>\logs directory.

The following is an example of an install.log file:

(May 15, 2007 9:36:06 AM), This summary log is an overview of the
 sequence of the installation of the IBM System Storage
 SAN Volume Controller Console 4.2.0.546
(May 15, 2007 9:38:22 AM), IBM System Storage 
SAN Volume Controller Console installation
process started with the following install parameters:
Target Directory: C:\Program Files\IBM\svcconsole
SOAP port: 8884
RMI port: 2809
(May 15, 2007 9:38:28 AM), Copying Service Location Protocol Files ... 
(May 15, 2007 9:38:29 AM), Service Location Protocol successfully installed
(May 15, 2007 9:38:29 AM), Copying IBM System Storage SAN Volume
Controller Pegasus Server Files ...
(May 15, 2007 9:39:26 AM), The PuTTY private key successfully copied
 into file C:\Program Files\IBM\svcconsole\cimom\icat.ppk
(May 15, 2007 9:39:51 AM), The file setupCmdLine.bat successfully updated.
(May 15, 2007 9:39:51 AM), Compile MOF files started ...
(May 15, 2007 9:40:06 AM), MOF files successfully compiled.
(May 15, 2007 9:40:06 AM), Generate a certificate store started ...
(May 15, 2007 9:40:19 AM), Certificate store called truststore 
successfully generated.
(May 15, 2007 9:40:20 AM), IBM System Storage SAN Volume
Controller Pegasus Server successfully installed
(May 15, 2007 9:40:20 AM), Installing embedded version of IBM WebSphere
 Application Server ...
(May 15, 2007 9:41:42 AM), IBM WebSphere Application Server V6 - SVC 
successfully installed.
(May 15, 2007 9:43:20 AM), Copying SAN Volume Controller Console Ear Files...
(May 15, 2007 9:46:11 AM), The ICAConsole application successfully installed.
(May 15, 2007 9:47:24 AM), The SVCConsole application successfully installed.
(May 15, 2007 9:48:06 AM), The help application successfully installed.
(May 15, 2007 9:48:27 AM), The ""C:\Program Files\IBM\svcconsole\console\
embeddedWAS\bin\expressPorts\UpdateExpressMultiPorts.bat"  -soap  8884 
 -boot  2809  -remove" command updated successfully embedded WAS ports 
in configuration files.
(May 15, 2007 9:48:27 AM), Command to be executed : net start cimomsrv
(May 15, 2007 9:48:49 AM), Command to be executed : net start 
"IBMWAS5Service - SVC"
(May 15, 2007 9:50:15 AM), The following services started successfully:
Service Location Protocol
IBM System Storage SAN Volume
Controller Pegasus Server
IBM WebSphere Application Server V6 - SVC
(May 15, 2007 9:50:15 AM), INSTSUCC: IBM
 System Storage SAN Volume Controller Console
has been successfully installed.

Issue the exit command to close the command prompt window. After the completion of the successful installation of the SAN Volume Controller Console, the installer attempts to start the following services:
- Service Location Protocol
- IBM System Storage SAN Volume Controller Pegasus Server
- IBM WebSphere Application Server V6 - SVC
Perform the following steps to view the post installation tasks:
1. Open a command prompt window.
2. Go to the W2K directory on your CD drive or the W2K directory that was created during the extract.
3. Issue the following command to open LaunchPad:
```
LaunchPad
```
4. Click Post installation tasks in the LaunchPad window.
5. Follow the instructions in this file to complete the post installation tasks for the SAN Volume Controller Console.
Use the Services component of the Windows® Computer Management utility to verify that the following services Status is set to Started and Startup Type is set to Automatic:
- Service Location Protocol
- IBM System Storage SAN Volume Controller Pegasus Server
- IBM WebSphere Application Server V6 - SVC