Importing out-of-box content and enabling the dashboards and quick start page

This topic was edited by a BMC Contributor and has not been approved.  More information.

Various optional product objects are provided as out-of-box content to support common tasks and use cases. These objects are installed automatically by the unified product installer, but are not installed by the individual component installers. Similarly, the quick start page and Health and Value Dashboards, optional user interfaces, are not activated when you install or upgrade BMC Server Automation using the individual component installers.

After using the individual component installers to perform an installation or upgrade, you can choose to manually import the various types of out-of-box content and to manually activate the optional user interfaces.

For more information about the optional out-of-box content, see New items installed when you upgrade.


This task is not required if you use the unified product installer to install or upgrade BMC Server Automation. 

The following table provides additional details and instructions for importing the optional out-of-box content and activating the optional product interfaces:

Install blcontent, a collection of sample prepackaged content.From the directory where BMC Server Automation is installed on the Application Server, enter the appropriate command:
  • (Windows) NSH\bin\blcontent.exe
  • (Linux and UNIX) /NSH/bin/blcontent

For more information, see Loading prepackaged content.

Import zipkits, pre-defined content for specific tasks

 Click here to see a list of provided ZipKits.

ZipKit nameType of objects installed
Patch Ready (Windows)Component template
Extended object
Depot objects 
Windows 2012 R2 Standard ConfigurationComponent template
Depot objects 

Activation Status_Windows

(For Windows 2008 Servers and above only)

Extended object
IIS 8.5 (Windows 2012 R2)Depot object (package)
LAMP on CentOS 6Depot object (package)
Provisioning - Redhat Linux 6.0 (Internal zipkit, used by quick start page)Depot object (package)
Provisioning - Windows 2012 (Internal zipkit, used by quick start page)Depot object (package)

Perform the following steps:

  1. Navigate to the directories that you extracted from the main product package that you downloaded from the BMC Software Electronic Product Distribution (EPD) website. The main product package follows the naming convention BBSA<version>-<platform>.zip (for example, The top-level directory in the extracted directory structure typically has the same name, and is referred to here as <BASE_DIR>.
  2. Navigate to <BASE_DIR>/files/zipkits. Extract the zipkits that are stored there and store their contents in a temporary directory (referred to here as <UNZIPPED_ZIPKITS_DIR>).
  3. Execute the NSH scripts provided in the zipkits directory. Use the following commands, in which you are required to specify a valid product profile and role.
    • nsh '<BASE_DIR>/files/zipkits/ZipKitsImport.nsh' false '<PROFILE>' '<ROLE>' '<BASE_DIR>/files/zipkits' "<UNZIPPED_ZIPKITS_DIR>"
    • nsh '<BASE_DIR>/files/zipkits/CreateZipkitsJobs.nsh' false '<PROFILE>' '<ROLE>'

Import agent installers, agent bundles, and Agent Installer Jobs

 Click here to see a list of provided agent-related objects and their locations.

ObjectDepot PathCan be used for
Installers/Depot/BMC Maintenance/Agent Installers/Agent install and upgrade
Bundles/Depot/BMC Maintenance/Agent Bundles/Agent upgrade
Jobs/BMC Maintenance/Agent Installer Jobs/Agent upgrade

For more information about using these objects, see Installing one or more agents using the BMC Server Automation Console and Upgrading the RSCD Agent using an Agent Installer Job.

Execute an NSH script named CreateDepotSoftwareForAgents.nsh. Use the following command:

nsh '<BASE_DIR>/files/installers/rscd/CreateDepotSoftwareForAgents.nsh' false '<PROFILE>' '<ROLE>' '<APPSRVR_HOST>' '<BASE_DIR>/files/installers/rscd' '<VERSION (of BSA installation)>'

For example,

nsh "/C/Installers/BBSA89-WIN64/Disk1/files/installers/rscd/CreateDepotSoftwareForAgents.nsh" false "defaultProfile" "BLAdmins" "<appserver_host>" "/C/Installers/BBSA89-WIN64/Disk1/files/installers/rscd" ""

Activate the Health and Value Dashboards

Execute an NSH script named CreateDashboardReportJob.nsh.

Use the following series of commands to acquire credentials using the blcred utility and then to execute the NSH script:

blcred cred -acquire -profile '<PROFILE>'

nsh '<BASE_DIR>/files/dashboard/CreateDashboardReportJob.nsh' '<PROFILE>' '<ROLE>' '<BASE_DIR>/files/dashboard'

You can also use the BLCLI Utility generateDashboardReport  to generate the Dashboard report.

Import HTML reports and other artifacts for the SCAP compliance analysis of containers and images

Execute an NSH script named CreateContainerComplianceArtifacts.nsh. Use the following command:

nsh '<BASE_DIR>/files/container_compliance/CreateContainerComplianceArtifacts.nsh' '<PROFILE>' '<ROLE>' '<BASE_DIR>/files/container_compliance'

Activate the quick start page

Run the following blasadmin command:

set appserver DisableBSAConsoleQuickStartPage false

For more information, see Controlling the display of the quick start page.

Copy the Application Server installers to the file server for the Add Node functionality

Perform the following steps:

  1. On the file server, create a directory structure under the root for installer_bundle/<os>/files, where <os> is either linux or windows.
  2. Copy the contents of <upi dir>/Disk1/files/installers into the <file server>/installer_bundle/<os>/files directory that you created.
Was this page helpful? Yes No Submitting... Thank you