IBM Control Desk, Version 7.6.0

Programmatically verifying that the installation was successful

After you have exited the Control Desk installation program without encountering any errors, you can verify that the installation completed successfully. The installation is programmatically verified through the use of post installation validation utilities.

Before you begin

The JAVA_HOME environment variable must be set on the system before you can use the verification utilities.

About this task

During installation, the Control Desk installation program performs a simple health check. This health check consists of logging in to the application to verify availability. This health check might not be sufficient to verify a successful installation in all deployment scenarios. For example, if, during installation, you select the option to deploy the application EAR file at a later date, this health check cannot verify the installation. This simple health check is also insufficient for verifying an upgrade.

A post installation validation utility is available after the product has been deployed.  The installValidation utility is used to validate the product and middleware installation. This command-line utility is used to verify the installation and configuration of the product in a more complete manner. These utilities can also be used to verify an existing deployment after changes in the environment, such as changes to host names, user IDs, and passwords.

Results of the installValidation utility are logged in GConfigurationError[yyyymmddHHmm], CTGConfigurationMessage[yyyymmddHHmm],CTGConfigurationSummary[yyyymmddHHmm], and CTGConfigurationTrace[yyyymmddHHmm]. These log files are found in the \IBM\SMP\ConfigTool\logs directory on the administrative workstation.

Procedure

  1. Log in to the server using the user ID that was used to run the installation program. If you intend to use the installValidation utility, log in to the server hosting the installed component.
  2. Ensure the JAVA_HOME environment variable is set properly to the location of a JRE 1.7 installation.
  3. To verify middleware installation, from the middleware image, update the middleware.properties file with the installation parameter values for middleware components to be verified, change directory to \HealthCheck and run the middlewareValidate.[sh|bat] command. To verify product installation, from the administrative workstation, change directory to \IBM\SMP\ConfigTool\scripts and run the installValidation.[sh|bat] command. For either command, use the parameters described below:
    Table 1. Verification utilities parameters
    Program Syntax parameters Input
    installValidation.[sh|bat] -action Use -action validate to start the validation of the product installation.

    Use -actionvalidateMiddleware to start the validation of the middleware installation.

    The -action parameter is the only mandatory parameter when using the installValidation utility.

      -trace Verification progress information is written to the screen during the verification process. You can modify the output using the -tracing parameter.
    • minimal

      Progress information is limited to error information.

    • normal

      Information includes individual test progress, individual test results, and overall progress of the entire verification process.

      This is the default mode of tracing.

    • verbose

      In addition to providing normal progress information, verbose tracing includes the test class name, test method name, and corrective action information.

      -confirm You are prompted before each test is started. You must confirm each test to be performed. There is no input for this parameter.
      -component You can provide a comma-delimited list of directories containing the test objects to limit testing to a specific set of tests.

    These test objects must be located in the \ibm\smp\HealthValidation\ directory. For the product installation program, only the CTGIN folder is provided.

      -dbuser Provide the user ID used to access the database.
      -dbpwd Provide the password of the user ID used to access the database.
      -wasuser Provide the WebSphere® Application Server Network Deployment user.
      -waspwd Provide the password for the WebSphere Application Server Network Deployment user.
      -maxuser Provide the Control Desk administrator user ID. For example, maxadmin.
      -maxpwd Provide the password for the Control Desk administrator user ID.
      -middlewareproperties Use
    -middlewareproperties file
    where file is the location of the middleware.properties file. By default, this file is found on the middleware installation media in the \HealthCheck directory.

    The middleware.properties contains the middleware installation properties, such as installation locations and ports. User names and passwords are not stored in this plain-text file. Some of the properties common to all platforms have been defined default values, but platform-specific properties like installation locations need to be updated in this file before starting the middlewareValidate utility.

    The -middlewareproperties parameter is the only mandatory parameter when using the middlewareValidate utility.

      -sourceDirectory Provide the installation directory for the software.
      -trace Verification progress information is written to the screen during the verification process. You can modify the output using the -trace parameter.
    • minimal

      Progress information is limited to error information.

    • normal

      Information includes individual test progress, individual test results, and overall progress of the entire verification process.

    • verbose

      In addition to providing normal progress information, verbose tracing includes the test class name, test method name, and corrective action information.

    If this option is not provided, by default, no output displayed.

      -bindDN

    Provide the bind Distinguished Name..

      -bindPwd

    Provide the password for the bind Distinguished Name.

    For example,
    installValidation.bat -action validate

Results

The installValidation.bat validation utility results are logged in ctginstallvalidationtrace00.log. This log is found in the \IBM\SMP\ConfigTool\logs directory on the administrative workstation.



Feedback