Preparing a patch job with modified settings
The following procedure describes the steps in running patch analysis using the Network Shell Script job provided by TrueSight Server Automation Vendor Patch Content, after customizing various settings within this job. This procedure differs, depending on whether you are preparing a job for HP-UX for CentOS.
- Before you begin
- To prepare a patch job for execution by configuring settings that are common to HP-UX and CentOS
- To modify settings for an HP-UX patch job
- To modify settings for a CentOS patch job
- Related topics
Before you begin
To store HP-UX patch binaries and metadata, ensure that the designated patch repository has approximately 5 GB of free space available.
To prepare a patch job for execution by configuring settings that are common to HP-UX and CentOS
- In the Jobs folder of TrueSight Server Automation Console, locate the HP-UX or LinuxPatch Analysis job.
This job is a Network Shell Script job used for patch analysis, and it is stored within the Jobs folder, Jobs/Patch Analysis Jobs/[HPUX|Linux] Patch Analysis/Patch Analysis Jobs. Right-click the Network Shell Script job and select Open.
- Select the Targets tab and click Add.
- From the list on the left side, select the target server or servers and click the right arrow to move your selections to the right side. Servers are displayed either by group or by name:
- By Group: The left panel displays servers in a hierarchical list arranged by server group. Choose servers either by as a group or by selecting individual servers within the groups.
- By Name: The left panel displays servers in table view which can be sorted by clicking a column heading. To select multiple servers, use CTRL+click or SHIFT+click.
- Click OK.
- Select the Parameters tab.
For the following parameters on the Parameters tab, which are common to all Network Shell Script Jobs (that is, not unique to HP-UX or CentOS patch analysis), click Value and enter information according to the following table:
Parameter
Description
Auto Execute Deploy Batch Jobs
Flag: -X
Determines auto-execution of deployed batch jobs when analysis is performed in packaging-enabled mode (-p).- 0: (Default) The Deploy Batch job is not executed after packaging.
- 1: The Deploy Batch job is executed after packaging.
Debug Mode
Flag: -d
Produces output, used for debugging purposes, in all phases of analysis. Choose either:- 1: Analysis runs in debug mode. Results are available in a log file (once run, right-click the job in the right pane and select Log File).
- 0: (Default) Analysis does not run in debug mode.
Deploy Job Folder Name
Flag: -J
In the Console hierarchy, identify the location of the repository (Depot) where Deploy Jobs are stored after the job is created from scripts. Entry in this box is mandatory and the folder must exist. The default value is /Patch Analysis Jobs/Linux Patch Analysis/Patch Deploy Jobs.Depot Patch Folder Name
Flag: -D
In the Console hierarchy, identify the location of the patch repository (Depot) where BLPackages and software items are created. Entry in this box is mandatory and the folder must exist.hosts
Flag: -f
Non-editable box containing target servers defined for the job in the previous step.local directory
Flag: -w
Read-only box that identifies the location where Product Name is installed.- Continue modifying settings that are specific to the operating system, as described in one of the following sections below:
To modify settings for an HP-UX patch job
After performing the first few steps of modifying the patch job, on the Parameters tab, enter values for the Script Mode parameter (-m).
The script mode parameter (-m) determines which of three actions (analysis, download, packaging) occur when the job runs.Enter any combination (such as a, ad, or adp) of the following three options, without spaces or punctuation:
Value
Description
Analyze (a)
The Analyze option runs patch analysis and stores results for all missing binaries in a Results file.
Download (d)
The Download option downloads missing binaries. Patch binaries are not visible in the patch repository but have been downloaded from the vendor site. Patches become visible when you run the script a second time using the Package (-p) option.
Analysis Results file generated by the Analysis option. If the Analysis Results file is not present when you run the Download option, the job will fail.
Package (p)
Package missing binaries into BLPackages. The use of this option is possible only after the Analyze (-a) and Download (-d) options have already been run.
On the Parameters tab, enter values for the following parameters related to the connection with the vendor’s site through an SWA Server:
Parameter
Description
SWA Installation Path
Flag: -i
(Mandatory) Enter the local path to the directory where SWA is installed.SWA Location
Flag: -t
(Mandatory) Enter the local path to the SWA working directory which will be used as the patch repository.SWA Server
Flag: -u
(Mandatory) Enter the host name of an SWA Server managed by BMC BladeLogic.- Through the Catalog Download mandatory parameter (Flag: -x), specify whether or not to download a new swa_catalog.xml. Click Valueand select the relevant option:
- 0 - do not download a new swa_catalog.xml; use the old one
- 1 - download a new swa_catalog.xml
To indicate the type of patches included in analysis, for the Filter Options parameter, click Value and enter one of the following options:
Paramter
Description
CHAIN=patchID[,patchID]*
Analyze a specific patch(es) or its recommended successor(s). This is the preferred option for analysis.
CRIT
Analyze only those patches that fix critical problems
PATCH=patchID[,patchID]*
Analyze a specific patch(es). Note that the CHAIN= option is recommended for analysis.
PCW
Analyze only those patches with critical warnings
PW
Analyze only those patches with warnings (patches with critical warnings, defined by the PCW option, are included in this set).
QPK
Analyze only the latest Quality Pack Bundle.
SEC
Analyze only those patches contained in the latest Quality Pack.
list_PATCH=patchList
Analyze only those patches identified on the specified patch list.
list_CHAIN=patchList
Chain analyze those patches, or their recommended successors, identified on the specified list.
- Click OK.
To modify settings for a CentOS patch job
After performing the first few steps of modifying the patch job, on the Parameters tab, enter values for the Script Mode parameter (-m).
The script mode parameter (-m) determines which of three actions (analysis, download, packaging) occur when the job runs.Enter any combination (such as a, p, or ap) of the following options, without spaces or punctuation:
Value
Description
Analyze (a)
The Analyze option runs patch analysis and stores results for all missing binaries in a Results file.
Package (p)
Package missing binaries into BLPackages. The use of this option is possible only after the Analyze (-a) option has already been run.
For the Analysis Type Parameter, click the Value box and enter one of the following analysis types:
Analysis Type
Format Description
list:<list file path>
Define the nsh path to a file which lists RPMs, Packages, and Errata IDs for analysis. The file is formatted as one RPM, Package, or Errata ID per line.
When a name in this file contains an asterisk (*), Vendor Patch Content installs or updates all RPMs, Packages, or Errata IDs beginning with the included text. For example, if you specify the string sysstat*, all patches containing sysstat in the RPM, Package, or Errata name are either installed or updated.
repo:updates
Define one or more patch repositories where patch analysis will be performed on the entire repository. This parameter requires a definition for the Linux Patch Repository (-l) parameter.
rpm:<rpmname,[rpmname]*>
List specific RPMs to analyze
- Click OK.
Related topics
Executing-the-patch-analysis-job
Preparing-a-patch-job-for-HP-UX-or-CentOS-with-predefined-settings