How to Build Manifests for Managed Hosts (Command Line)

1. Determine which managed hosts you want to audit.

   For example, audit the /web-server/host1 and /web-server/host2 managed hosts.

2. Build manifests for the managed hosts.

   $ changemgr manifest [ -u username ] [ -p file ] [ -d domain ] \ -o relfilepathprefix [ -r relfilepath.brul ] topopath ...

   -o relfilepathprefix

   Specify the prefix to be used when creating the output inventories. The name of the managed host and the .bmft suffix are appended to the prefix specified to form the name of the resulting manifest.

   -r relfilepath.brul

   Specify the audit rules file to use to create the manifest.

   topopath

   Specifies the path to a managed host or host group that is relative to the top of the selected administrative domain.

   For descriptions of the other options, see How to Add Managed Hosts (Command Line).

Example-Building Manifests for Managed Hosts

Suzi builds manifests for the /web-server/host1 and /web-server/host2 managed hosts. She stores the files in the /web-server folder with a manifest file prefix of usr-only. The resulting file names are /web-server/host1.bmft and /web-server/host2.bmft.

$ changemgr manifest -o /web-server/ -r usr-only.brul \
/web-server/host1 /web-server/host2

If the argument to -o is a folder, terminate the argument with a slash. For example, if the argument to -o is /web-server/baseline, then baseline is prefixed to manifests created in the /web-server folder. Using this prefix, a resulting manifest name might be /web-server/baselinehost1.bmft.