PatchingJob - createOtherLinuxPatchingJobWithTargetServer
This command creates a Patching Job that is run against an individual server, using an existing "other" Linux catalog, such as SuSE/OEL.
This command returns a handle to the newly created Patching Job. The handle can be used in other commands that need to reference the Patching Job.
The jobGroupName argument provides the fully qualified path to the parent group. The targetGroupName argument provides the target group name for the new Patching job. The catalog name provides the fully qualified path for the catalog already defined. The include/exclude list text file could have entries for smart groups and/or depot objects one on each line. The depot objects and the smart group should be existing in the catalog before running this command. To include the depot object add NAME#(name of the depot object)" in the include file. To include a smart group add "GROUP#(complete path to the smart group)" in the include file. for instance an example of the contents in the include/exclude list file could be NAME#APSB-0611 GROUP#/Catalog/TestCatalog1/smartGroup1.
Note: As of BMC Server Automation 8.8, when using this command to create a Patching Job on a SuSE Linux server, zypper is used as the patching tool for analysis. If you want to use yum instead, use the new PatchingJob - createSusePatchingJobWithTargetServer command.
Return type : DBKey
Command Input :
Name of the job.
Parent group for this job.
Name of the target server.
OtherLinux Catalog group for this job.
Include file path.
Exclude file path.
True to set install mode, false otherwise.
True to set exact architecture, false otherwise.
The following example creates a Patching Job with a single target OtherLinux server, using an existing catalog.
JOB_GROUP=/noc/patching TARGET_SERVER=testServer CATALOG_NAME=/noc/otherLinuxCatalog JOB_KEY=`blcli PatchingJob createOtherLinuxPatchingJobWithTargetServer nocPAJob $JOB_GROUP $TARGET_SERVER $CATALOG_NAME //localhost/c/include.lst //localhost/c/exclude.lst true false