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

Use these steps to install the IBM® TotalStorage® DS Storage Manager in your Windows environment using the unattended (silent) mode.

Prerequisites

Before you install theIBM TotalStorage DS Storage Manager, verify that the prerequisite software and hardware are installed on your system. The DS Storage Manager is supported on the following Windows operating system versions: The installation program checks for prerequisites and stops if any prerequisites are missing.

Context

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 TotalStorage DS Storage Manager CD.

Perform the following steps to install the IBM TotalStorage DS Storage Manager in your Windows environment using the unattended mode:

Steps

  1. Log on to your Windows system as an administrator.
  2. Insert the IBM TotalStorage 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.
  3. 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 represents 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.
  4. 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>""
    • Replace the value in the management types section with one of the following:
      • "realtime" – Use this value if you only want Real-time Management (for connected configuration and Copy Services). Remember that this allows a product configuration to be created only when you are connected to the network.
      • "simulated" – Use this value only if you want to create product configurations in offline mode.
      • "both" – Use this value if you want to create product configurations when you are connected to the network or when you are working offline.
    • 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 passwords must contain at least 6 characters.
      • Use the following options within the responsefile.txt file to set these options:
        • For the keystore use: 
          -W wasSslConfiguration.keystorePassword="your_keystore_password"
        • For the truststore 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.
  5. Save the modifications to the response file.
  6. Type the following command at the command prompt and press the Enter key on your keyboard to start the installation process in silent mode: setup.exe -options <responsefile-path>\<responsefile> 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).
  7. Wait for the installation program to install the product. This can take 5 - 10 minutes.
  8. 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 TotalStorage DS Storage Manager is installed.
  9. Start the IBM TotalStorage DS Storage Manager, if no errors are evident.
  10. Perform the postinstallation tasks when the DS Storage Manager has been installed successfully. You can access the instructions for the postinstallation tasks from the postinstallation.txt file, in the doc directory on the product CD.

Example

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

################################################################################
#
# InstallShield Options File
#
# Wizard name: Setup
# Wizard source: setup.jar
# Created on: Tue Jul 27 09:02:47 EEST 2004
# Created by: InstallShield Options File Generator
#
# This file contains values that were specified during a recent execution of
# Setup. It can be used to configure Setup with the options specified below when
# the wizard is run with the "-options" command line option. Read each setting's
# documentation for information on how to change its value.
# 
# A common use of an options file is to run the wizard in silent mode. This lets
# the options file author specify wizard settings without having to run the
# wizard in graphical or console mode. To use this options file for silent mode
# execution, use the following command line arguments when running the wizard:
# 
#    -options "responsefile.txt" 
#
################################################################################

-silent

################################################################################
#
# IBM TotalStorage 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. 
#

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


################################################################################
#
# User Input Field - type
#
# The management types selection, that can be: "realtime" for connected
# configuration and Copy Services (a realtime management); "simulated" for
# disconnected configuration (a simulated management); "both" for both types of
# management.
#

-W appSelection.type="both"


################################################################################
#
# User Input Field - hostname
#
# The fully-qualified host name of the machine where 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.
# 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.
#


-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 for Eclipse  
# This value must not conflict with existing port assignments on the system.
#

-W wasExpressConfig.helpPort="8455"


################################################################################
#
# User Input Field - certificateOption
#
# 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
# certificates. For 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 - 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=""


################################################################################
#
# 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.
#

Contents Previous Next