Installing the IBM System Storage DS Storage Manager on the Windows operating system in unattended (silent) mode

Complete this task to install the IBM^® System Storage™ DS Storage Manager in your Windows environment using the unattended (silent) mode.

Before you install the IBM System Storage DS Storage Manager, verify that the prerequisite software and hardware are installed on your system. The installation program checks for prerequisites and stops if any prerequisites are missing. If you have the correct level of Java code, but Java errors appear during installation, request a new installation CD from your IBM representative.

Notes:

The name of the user who logs on and performs the installation must not contain any non-ASCII or special characters. It could cause the installation to fail.
The DS Storage Manager is not supported on any Windows 64-bit operating system.

The unattended (silent) mode installation option allows you to run the installation program unattended. Use this method of installation to customize a response file and to issue a command from a command prompt window. The response file is a template on the IBM System Storage DS Storage Manager CD.

Perform the following steps to install the IBM System Storage DS Storage Manager in your Windows environment using the unattended (silent) mode:

Log on to your Windows system as an administrator.
Insert the IBM System Storage DS Storage Manager installation CD into the CD-ROM drive. If the interactive mode starts, click the Exit selection on the LaunchPad window to exit.
Locate the response file (responsefile.txt) in the root directory of your CD and copy it to a directory of your choosing on your system, or open a command prompt window and generate the template response file.
To generate the template response file, perform the following steps:
1. Ensure that your command prompt is located at the root directory of the CD-ROM drive.
2. Type setup.exe -options-template <responsefile-path>\<responsefile>, where responsefile-path is the path where you want the response file to be created, and responsefile is the name of the response file that you want to create.
3. Press the Enter key and wait for the program to create the response file.
Open the response file using a text editor and modify the default options with the values that you want.
Follow these guidelines when you modify the default options:
- Remove the three # characters from the beginning of each line that contains a parameter (if you generated the response file as shown before). Change the parameter default value to the value that you want for that option. You must enclose all values in double quotation marks ("<value>").
- Verify that all paths generated or modified in the response file are correct. There are some cases when the generated file displays an incorrect string representing the path of the installation location. For example, the parameter "-P installLocation = "C:Program FilesMy Product"" is wrong and must be "-P product.installLocation = "<directory where you want the DS Storage Manager installed>""
- Ensure that the entered values for the ports values are available and not used by other applications on your system. Use the command "netstat -a" to verify the ports in use on your system.
- Specify two passwords for the SSL keys files. These passwords must observe the following criteria:
  - The password must be a minimum of six characters and it cannot contain any blanks.
  - Allowable characters are letters A - Z and a - z, digits 1 - 9, and special characters - and _ (hyphen and underscore).
  - Use the following options within the responsefile.txt file to set these options:
    - For the keystore file use:
      -W wasSslConfiguration.keystorePassword="your_keystore_password"
    - For the truststore file use:
      -W wasSslConfiguration.truststorePassword="<your_truststore_password>"
      
      Note: These options do not have default values. If you do not set these values, the installation process fails.
Save the modifications to the response file.
Type the following command at the command prompt and press the Enter key on your keyboard to start the installation process in unattended (silent) mode: setup.exe -options <responsefile-path>\<responsefile> -silent where
- responsefile-path — represents the path where the response file resides.
- responsefile — represents the relative name of the response file that you used or created (for example, responsefile.rsp or responsefile.txt).
Wait for the installation program to install the product. This can take 5 - 10 minutes.
Note: During this processing, the installation process checks to see if the DS Storage Manager server and DS Network Interface Server are already installed and if they are the current version or have to be upgraded. If they are already installed and need to be upgraded, the installation process performs this function using the already set values from the previous server installation, found on the system in the server configuration files, for all the associated values. The specified values in the response file are ignored.
If required, perform a system restart to complete the installation. After the system has restarted, the two servers (DS Storage Manager server and DS Network Interface Server) are automatically started by the system.
Verify that the DS Storage Manager server and IBM System Storage DS Network server are operating. From the Windows Control Panel, select Administrative Tools, and then Services. Both servers must show a "Started" status. You cannot start the DS Storage Manager until both of the servers are started.
Check the install log file for any possible error messages. This file is located in the xxx\logs\install.log directory, where xxx is the destination directory where the IBM System Storage DS Storage Manager is installed.
Start the IBM System Storage DS Storage Manager, if no errors are evident.
Perform the post installation tasks when the DS Storage Manager has been installed successfully.

The following is an example of the template response file that is created when you process the previous steps.

################################################################################
#
# InstallShield Options File Template
#
# Wizard name: Setup
# Wizard source: setup.jar
# Created on: Tue Jan 25 18:01:00 EET 2005
# Created by: InstallShield Options File Generator
#
# This file can be used to create an options file (i.e., response file) for the
# wizard "Setup". Options files are used with "-options" on the command line to
# modify wizard settings.
# 
# The settings that can be specified for the wizard are listed below. To use
# this template, follow these steps:
# 
#    1. Enable a setting below by removing leading '###' characters from the
#    line (search for '###' to find settings you can change).
# 
#    2. Specify a value for a setting by replacing the characters <value>.
#    Read each setting's documentation for information on how to specify its
#    value.
# 
#    3. Save the changes to the file.
# 
#    4. To use the options file with the wizard, specify -options <file-name>
#    as a command line argument to the wizard, where <file-name> is the name
#    of this options file.
#
################################################################################

-silent

################################################################################
#
# IBM System Storage DS6000 Storage Manager Install Location
#
# The install location of the product. Specify a valid directory into which the
# product should be installed. If the directory contains spaces, enclose it in
# double-quotes. For example, to install the product to C:\Program Files\My
# Product, use
# 
#    -P installLocation="C:\Program Files\My Product"
#


 -P installLocation="C:\Program Files\IBM\DS6000StorageManager"


################################################################################
#
# User Input Field - type
#
# The management types selection, can be: "full", which installs the Full
# Management Console, and "offline", which installs the Offline Management
# Console.
#


 -W managementType.type="full"


################################################################################
#
# User Input Field - hostname
#
# The fully-qualified host name of the machine where the DS Storage Manager
# Server will be installed.
#


 -W wasExpressConfig.hostname="localhost"


################################################################################
#
# User Input Field - httpPort
#
# The port number that the HTTP transport in the application server will use.
# The HTTP transport is a request queue between the application server and the
# HTTP server (Web server). This value must not conflict with existing port
# assignments on the system.
#


 -W wasExpressConfig.httpPort="8451"


################################################################################
#
# User Input Field - httpsPort
#
# The port number that the HTTPS transport in the application server will use
# for secure HTTP transport. This value must not conflict with existing port
# assignments on the system. To enable HTTPS, the user must also perform the
# procedure described in Console Developer InfoCenter (Setting up SSL) after DS
# Storage Manager Server is installed.
#


 -W wasExpressConfig.httpsPort="8452"


################################################################################
#
# User Input Field - bootstrapPort
#
# The address for the bootstrap function and the port number for the Java Remote
# Method Invocation (RMI) connector in the application server. This value must
# not conflict with existing port assignments on the system.
#


 -W wasExpressConfig.bootstrapPort="8453"


################################################################################
#
# User Input Field - soapPort
#
# The address for the Simple Object Access Protocol (SOAP) connector in the
# application server. This value must not conflict with existing port
# assignments on the system.
#


 -W wasExpressConfig.soapPort="8454"


################################################################################
#
# User Input Field - helpPort
#
# The port that the help system (based on Eclipse technology) will use to
# receive requests for help files. This value must not conflict with existing
# port assignments on the system.
#


 -W wasExpressConfig.helpPort="8455"


################################################################################
#
# User Input Field - certificateOption
#
# SSL Certificates Files Select one of the following options concerning the SSL
# certificates. Legal values are: "generate" (the default value) - Generate the
# self-signed certificates during installation. "use" - Use existing
# certificatesFor example, to specify that the "generate" option is selected,
# use -W wasSslConfiguration.certificateOption="generate"
#


 -W wasSslConfiguration.certificateOption="generate"


################################################################################
#
# User Input Field - keystoreFileName
#
# The absolute path of the keystore file.
#


 -W wasSslConfiguration.keystoreFileName=
"C:\Program Files\IBM\SMServer\keys\SMServerKeyFile.jks"


################################################################################
#
# User Input Field - keystorePassword
#
# The password for the keystore file.
#


 -W wasSslConfiguration.keystorePassword=""


################################################################################
#
# User Input Field - confirmedKeystorePassword
#
# The password confirmation of the keystore file. On silent mode the password
# confirmation is NOT necessary.
#


 -W wasSslConfiguration.confirmedKeystorePassword=""


################################################################################
#
# User Input Field - truststoreFileName
#
# The absolute path of the truststore file.
#


 -W wasSslConfiguration.truststoreFileName=
"C:\Program Files\IBM\SMServer\keys\SMServerTrustFile.jks"


################################################################################
#
# User Input Field - truststorePassword
#
# The password for the truststore file.
#


 -W wasSslConfiguration.truststorePassword=""


################################################################################
#
# User Input Field - confirmedTruststorePassword
#
# The password confirmation of the truststore file. On silent mode the password
# confirmation is NOT necessary.
#


 -W wasSslConfiguration.confirmedTruststorePassword=""


################################################################################
#
# Delete server certificates option
#
# Option to delete certificates files if they exist.Legal values are: "yes" - in
# order to delete application server certificates if they exist on the location,
# and to generate others, or "no" (the default value) - in order to keep the
# existing application server certificates.
#


 -G deleteCertificates=yes


################################################################################
#
# User Input Field - keystoreAlias
#
# The alias for the self-signed digital certificate, which is used to uniquely
# identify the certificate within the keystore file. If you have only one
# certificate in each keystore file, you can assign any value to the label.
# However, it is good practice to use a unique label related to the server name.
#


 -W CertificateParams.keystoreAlias="DSKey"


################################################################################
#
# User Input Field - keySize
#
# The key size. That must be between 512 and 1024 and must be multiple of
# 64b.The only two allowed values are 512 or 1024. If you enter other values it
# takes the default value 1024.
#


 -W CertificateParams.keySize="1024"


################################################################################
#
# User Input Field - commonName
#
# The common name is the primary, universal identity for the certificate; it
# should uniquely identify the principal that it represents. In a WebSphere
# environment, certificates frequently represent server principals, and the
# common convention is to use common names of the form "host_name" and
# "server_name". The common name must be valid in the configured user registry
# for the secured WebSphere environment.
#


 -W CertificateParams.commonName=""


################################################################################
#
# User Input Field - organizationName
#
# The name of your organization.
#


 -W CertificateParams.organizationName="IBM"


################################################################################
#
# User Input Field - organizationUnit
#
# The organization unit (a department or division). For a self-signed
# certificate, these fields are optional. However, commercial CAs might require
# them.
#


 -W CertificateParams.organizationUnit=""


################################################################################
#
# User Input Field - localityName
#
# The location (city). For a self-signed certificate, these fields are optional.
# However, commercial CAs might require them.
#


 -W CertificateParams.localityName=""


################################################################################
#
# User Input Field - state
#
# The state or province (if applicable). For a self-signed certificate, these
# fields are optional. However, commercial CAs might require them.
#


 -W CertificateParams.state=""


################################################################################
#
# User Input Field - country
#
# The two-letter identifier of the country/region in which the server belongs.
# For a self-signed certificate, these fields are optional. However, commercial
# CAs might require them.
#


 -W CertificateParams.country="US"


################################################################################
#
# User Input Field - validity
#
# The lifetime of the certificate in days.
#


 -W CertificateParams.validity="3650"