Limited supportBMC provides limited support for this version of the product. As a result, BMC no longer accepts comments in this space. If you encounter problems with the product version or the space, contact BMC Support.BMC recommends upgrading to the latest version of the product. To see documentation for that version, see BMC AMI Ops Infrastructure 7.1.

Target context definition


You can use a target context definition for targets that are critical to your site.

When you define a target context, you specify a unique combination of target and product. Defining a target context allows you to:

  • Specify products that you expect to be active for a target

    If a product is not active at a target, a signal can be made to MainView AutoOPERATOR to start that product.

  • Display the status of that target and product combination

    A CAS monitors active products automatically when it initializes. Specifying a target context definition causes the CAS to report the status of a product even if that product is not active.

  • Define a security profile for that target context

To define target contexts

  1. Use the information in Planning-a-target-context-definition to plan for the necessary target context definitions.
  2. Create target definitions by following the instructions in Defining-a-target-context.
  3. If necessary, enable target monitoring by following the instructions in Enabling-a-target-context-definition-member-in-the-local-CAS to define a target definition member to the local CAS definition.

This section contains the following topics:

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*