This documentation applies to the 8.1 version of Service Level Management, which is in "End of Version Support." You will not be able to leave comments.

To view the latest version, select the version from the Product version menu.

Configuring the BMC SIM plug-in

The following steps describe how to configure the BMC Service Impact Manager (BMC SIM) plug-in.

To configure the BMC SIM plug-in

  1. In BMC Remedy User, open the Application Administration Console.
  2. Choose Service Level Management > Configure Collector Module > Collection Nodes, and then click Open.
    The Collection Node form appears.
  3. Select the Collection Point that manages the collection of data from this node.
  4. Select BMC Service Impact Manager as the node type from the list.
    Selecting the node type changes the UI to display the necessary fields you must configure for SIM.
  5. Enter the Name.
    The name should describe the Collection Node.
  6. Define the Frequency.
    The frequency defines how often the Collection Point calls for data from the Collection Nodes. One minute is the shortest interval for this setting, but consider performance when setting this frequency. However, the higher the frequency, the more resource intensive it becomes. Because of demands on the server inherent in collecting data, a lower Collection Node frequency yields a more efficient collection process, but you must balance this against the need to trigger milestones promptly. The objective is to collect data frequently enough to ensure that the times chosen for milestones are not compromised, but not so often that the server is overloaded. The default is 300 seconds or 5 minutes. For more information on defining frequency, see Collection Node frequency.
  7. Define the MissingDataLimit.
    Missing data limit is a time limit that determines when BMC Service Level Management (BMC SLM) considers the data as missing. After this period of time, the missing data rule is applied and the values cannot be used even if they subsequently become available. If this missing data limit is too long, it might result in a delay in triggering milestones. The default is 600 seconds or 10 minutes. For more information on missing data limits, see Missing data limits for Collection Nodes.
  8. Enter the location of the IIWS server.

    Tip

    You can configure the BMC Impact Integration Web Services Server in the mcell.dir file to include the cell that was installed with the BMC Performance Manager Portal. See the installation documentation for the BMC Impact Integration Web Services Server for information about editing the mcell.dir file.

  9. Enter the IIWS Port number.
  10. Enter the IIWS Protocol.
  11. Enter the Cell Name.
    Create a Collection Node for each cell that contains service model components used in service target definitions. This needs to be done before any BMC SIM service targets are defined.
  12. Specify the location of the Cell Server.
  13. Enter the Cell Port number.
  14. Enter the password to the Cell Encryption Key.

    Note

    The Cell Encryption Key is set during BMC SIM cell installation.



    The Discover Metrics button allows you to discover a set of available metrics from a Collection Node and it is initiated by users from the Collection Node configuration. The Discover Metrics button is enabled when you select the configured Collection Nodes.

This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Comments