Performing the installation of Vendor Patch Content

To install Vendor Patch Content, you can choose between a regular (interactive) installation and a silent (unattended) installation.

Before you begin

If your environment requires a proxy server, define proxy server settings for the Application Server using the blasadmin utility. For more information, see To set up HTTP proxy server support.

The Vendor Patch Content installer runs a Perl script. Therefore, ensure that the blasadmin configuration for the _template deployment on the Application Server where you are running the VPC installer has the correct settings for the location of the Perl installation on the Application Server.  To check this, run the following command:
blasadmin -s _template show perlconfig location
This command should return /usr/bin/perl if your Perl binary is in /usr/bin/perl, or /C/perl/bin/perl.exe if Perl is installed in c:\perl\bin\.
If you need to modify the location, use the following command: set perlconfig location <pathToPerl>
For more information about configuring Perl, see Configuring-Perl.

To install Vendor Patch Content

1. Locate and extract the contents of the compressed installation file, TrueSight-serverautomation-patch-content-v<version_number>.zip, to any directory under the Application Server Installation directory on the server running TrueSight Server Automation. For more information about downloading the zip file, see Downloading-the-installation-files.
   
   

   Note

   • If you want use TrueSight Smart Reporting - Platform 20.02 for generating VPC reports, download the compressed script file from the TrueSight Server Automation 20.02 download location. TrueSight Smart Reporting - Platform 20.02 does not support the VPC content that is installed from the script files packaged with the earlier TrueSight Server Automation versions.
   • If you want to install VPC using the nsh here option from the TrueSight Server Automation Console installed on the Application Server, perform the following steps before running the installation:
     
     1. Upon command prompt, navigate to the Application Server Installation directory by entering the following command: cd //@
        This command ensures that the directory path does not have the //localhost/ appended to it.
     2. Enter another cd command to switch to the ke directory within the Application Server Installation directory.

2. Instruct Network Shell Script to run the script, nsh load-patch-content.nsh, as follows:

   • To run the installation with menu options, run the network shell script using the following format:
     nsh load-patch-content.nsh-r roleName-v profileName

     Option	Description
     -r roleName	Defines the user's role. This option is necessary only if the user performing the installation was assigned multiple roles.
     -v profileName	Defines a specific profile to use during installation, if you want to override the use of defaultProfile.

   • To run a silent installation, include the -c option, which defines HP-UX as the platform for patch content. Use the following format for a silent run of the Network Shell Script:
     nsh load-patch-content.nsh -r roleName -v profileName -c hpux-patch-content
     or
     nsh load-patch-content.nsh -r roleName -v profileName -c linux-patch-content
     

   Note

   (Linux only) If you receive an error message, indicating that the BLCLI credentials validation test failed, exit the installation and obtain session credentials. For more information, see Session credentials for VPC.

   If you receive an error message regarding a problem finding the deployment directory based on the $DEPLOYMENT_NAME variable, perform the following workaround: open the load-patch-content.nsh file for editing and replace the $DEPLOYMENT_NAME variable with the name of the deployment where you are performing the installation.

3. At the prompt, enter the path to where the BMC BladeLogic Application Server is installed.
4. At the Prompt, enter the path to where you want to install Vendor Patch Content (typically within the TrueSight Server Automation installation directories).
   As part of the installation, a patch subdirectory is created in the location where you want to install Vendor Patch Content.

5. Press Enter.

   Note

   If you are running a silent installation, that is, if you passed the -c option to the Network Shell Script in step 2, the installation continues automatically from this point forward. Installation logs display on screen.

   The installation menu appears, with the following options:

   Menu option	Description
   1 Load HP-UX Patch Content	Load patch content for patch analysis on an HP-UX platform. Installation is automatic and does not require further input. At the end you are returned to the Vendor Patch Content Installation Menu.
   2 Load Linux (CentOS) Patch Content	Load patch content for patch analysis on a Linux (CentOS) platform. Installation is automatic and does not require further input. At the end you are returned to the Vendor Patch Content Installation Menu.
   3 Set HP-UX Credentials	Provide the HP-UX credentials (user and password) for permission to download the catalog and patches to the repository.
   4 Configure Reports	Configure the reporting functionality.
   5 Configure Proxy	Optionally provide the credentials (user and password) of a proxy server that you want to use during HP-UX patch analysis.
   6 Exit	Exit the installation routine.

6. Depending on the platform, type 1 or 2 as your selected menu option and press Enter.
   The installation is completed. At the end of the installation, you are returned to the installation menu.
7. Type 3 and then enter the HP-UX credentials (user and password) that allow you to download the catalog and patches to the repository.
8. To configure the reporting functionality, type 4 as your selected menu option and press Enter. 
9. If you want to use a proxy during HP-UX patch analysis, type 5 and then enter the credentials (user and password) of the proxy server.
10. To exit the installation, type 6.