Configuring the VMware vCenter Lifecycle Manager adapter


You configure an adapter in TrueSight Orchestration Grid Manager. The configuration provides information about how the adapter interacts with the VMware vCenter Lifecycle Manager application. While each adapter must have a unique name, you can create multiple adapters with the same adapter type to allow for different configuration properties.

The form view provides an easy-to-use interface for configuring the actor adapter. You can also switch to the XML view to configure the adapter using XML only. However, after you switch to the XML view, and save the configuration in the XML, you cannot thereafter use the form view for modifying the adapter configuration.

Note

The default name of the actor adapter is LCMActor. The default name of the monitor adapter is LCMMonitor.

To configure the actor adapter, monitor adapter, or both

  1. Log on to the TrueSight Orchestration Grid Manager.
  2. Access the adapters page, by clicking the Manage tab; then click the Adapters tab.
  3. In the Adapters in Repository list:
    • Select the check box corresponding to bmc-adapter-vmware-lifecycle-manager-actor.
    • Select the check box corresponding to bmc-adapter-vmware-lifecycle-manager-monitor.
    • Select both check boxes to configure both adapters.
  4. Click Add to Grid to include the adapter in the Adapters on Grid list.
  5. Click Configure corresponding to the newly added adapter.
  6. On the Add an Adapter Configuration page, perform the following substeps to configure the adapter using the form view or jump to step 7 to configure the adapter using the XML view:
    1.  Enter a name for the adapter.

      Note

      The name does not support single-quote (') and the ampersand (&) characters.

    2. Enter a description for the adapter.
    3. Under Properties, enter the values for the configuration elements.

      Note

      Include all required elements indicated with an asterisk (*).

    4. Click OK.

      The newly configured adapter is now listed in the Adapters on Grid list.
  7. ( optional ) Configure the adapter in the XML view using the following substeps:
    1. Enter a name and a description for the adapter.
    2. Click Switch to XML View.
    3. On the Warning message that appears, click Switch View.
    4. In Properties, enter the adapter configuration properties in an XML format, including all required elements.

      Note

      If the default value for an optional element is acceptable, omit the element. Do not include empty elements.

    5. On the Warning message that appears, click Save.

This action saves the adapter configuration with settings in the XML view permanently. The newly configured adapter is now listed in the Adapters on Grid list.

The following table describes the node elements required for configuring the actor adapter.

 Node elements required for configuring the actor adapter

 

 XML sample for configuring the actor adapter

 <config>
  <soap-url>http://172.21.124.93:8080</soap-url>
  <user-name>requester</user-name>
  <password>requesterpassword</password>
</config>

 XML sample for configuring the actor adapter for secure communication

 <config>
  <soap-url>https://172.21.124.93:8081</soap-url>
  <user-name>requester</user-name>
  <password>requesterpassword</password>
</config>

Note

The current version of the adapter does not support role-based authorization for VMware Lifecycle Manager.

The following table shows the node elements for configuring the monitor adapter.

 Node elements for configuring the monitor adapter

 

 XML sample for configuring the monitor adapter

 <config>
    <soap-url>http://172.21.124.93:8080/</soap-url>
    <user-name>lcmadmin</user-name>
    <password>lcmadm1n</password>
    <events>
      <event>
        <type>REQs_FOR_VMs</type>
        <poll-interval>50</poll-interval>
        <start-date>20090201063118-0500</start-date>
        <end-date>20090528063118-0500</end-date>
      </event>
      <event>
        <type>VMs_SET_FOR_DECOMMISSION</type>
        <poll-interval>40</poll-interval>
        <start-date>20090201063118-0500</start-date>
        <end-date>20090428063118-0500</end-date>
        </event>
        <event>
        <type>REQs_WAITING_FOR_APPROVAL</type>
        <poll-interval>30</poll-interval>
        <start-date>20090201063118-0500</start-date>
        <end-date>20090528063118-0500</end-date>
      </event>
      <event>
        <type>REQs_WAITING_FOR_PLACEMENT</type>
        <poll-interval>25</poll-interval>
        <start-date>20090201063118-0500</start-date>
        <end-date>20090528063118-0500</end-date>
      </event>
    </events>
</config>

Enabling custom logging

To enable custom logging for the adapter, you must specify a log file name. You can also provide additional parameters for logging.

Note

You must be using TrueSight Orchestration version 8.1 or later to use the custom logging feature. These parameters will be ignored in earlier versions of TrueSight Orchestration Platform.

These parameters are available with supported adapter versions. See TrueSight Orchestration Content documentation for details.

  • Log File Name: Provide a name for the log file.
    This file will be stored in the AO_HOME/tomcat/logs directory. If Log File Max Backup Index value is greater than 0, the log file name is suffixed with the backup index. For example, if the parameter value is a.log, backup log files will have names, such as a.log.1, a.log.2.
  • Log File Size: Specify a size limit for the log file. 
    If the value specified for Log File Max Backup Index is greater than 0, when the specified size is reached, the current file is renamed with the suffix .1. Otherwise, the log file will be reset and over-written. The default value is 10MB. The available units are KiloBytes (KB), MegaBytes (MB) or GigaBytes (GB).
  • Log File Max Backup Index: Enter the maximum number of backup files allowed. The default value is 10.
  • Log File Append: Select this option to append new log information to the existing information in the file. If unselected, the file will be overwritten with new log information.
  • Log Level: Enter the logging level using one of the following choices:

    Logging level

    Description

    DEBUG

    The most detailed logging level; logs low-level messages, normal execution, recoverable erroneous conditions, and unrecoverable erroneous conditions

    INFO

    (default)

    Logs normal execution, recoverable erroneous conditions, and unrecoverable erroneous conditions

    WARN

    Logs recoverable erroneous conditions and unrecoverable erroneous conditions

    ERROR

    The least detailed logging level; logs only error conditions that are not usually recoverable

Encrypting an element's contents

You can add the attribute secure="true" to an XML adapter element XML view to ensure that the element's contents is encrypted when displayed.

Note

You must be using TrueSight Orchestration Platform version 8.1 or later to use this encryption attribute.

 

 

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