How to load Compliance Content
These videos show how to load compliance content and how to run a quick audit.
Compliance Content Install
For more detailed installation instructions (including silent installation), see Installing content libraries.
Compliance Quick Audit
What to do
At a high level, you must obtain the compliance content installer (the file name is usually something like Content-Install-Windows.exe or Content-Install-Linux.bin). You can get this file from the "Product Downloads" section of the support site (AKA "EPD"). Make sure you get the Content Installer from the same major version as your installed product (for example, 8.2). Get the latest service pack version of the Content Installer, as the Content Installer service pack versions do not necessarily align with the product installer service pack versions. For example, at one time BMC BladeLogic Server Automation 8.1 SP5 was current, while the content installer may have been 8.1 SP7.
Once you have the installer, it is easiest to run it from an Application Server as a local Administrator or root. You must have access to a role and user with permissions to create extended objects, files on the file server, a top-level component template group, and component templates. If you are using UNIX, you may need access to an X Window display. This can be remotely displayed through a variety of methods.
- Run the Content Installer executable
- Provide a temporary directory for the Content Installer executable to write to
- Provide credentials (user, role, and password)
- Specify whether you are using a multi-Application Server (MAS) environment. The content installer runs for quite some time, but you can either monitor a log file whose location will be provided by the installer or watch the component templates node to see the templates being created.
Content Installation FAQs:
Prior to version 8.0, you will see a folder name under compliance workspace that includes the build version in the folder name. In 8.1 or later versions, you must check the content.version file, which gets created under the ../fileserver/Content folder.
The content of the content.version file looks like this:
Please comment below to ask questions about this document.