Creating the server lifecycle properties mapping file

To use the Import Lifecycle Properties option on the Virtual Infrastructure Discovery Job, you must create a properties mapping file for the lifecycle properties. The mapping file contains a list of mappings for the targets and VMware vCenter servers against which the Virtual Infrastructure Discovery Job is run.

Before you begin

Note the following considerations when creating the file:

• You must store the file in a depot folder so that it is accessible across Application Server instances.
• The Import Lifecycle Properties option on the Virtual Infrastructure Discovery Job imports only the three supported lifecycle properties (OWNER, EXPIRY_DATE, LOCATION) for all registered virtual machines.

• The Name parameter for the VirtualEntityManager element must match the name provided in the CONNECTION_URL of the Connection property set instance of the virtual entity manager. 

  Note

  If a server has been renamed, you must manually change the Connection property set instance value to the renamed server name for the Virtual Infrastructure Discovery Job remediation target and Import Lifecycle options to execute successfully.

To create a properties mapping file for the Import Lifecycle Properties option

1. Create an XML file with the format shown in the following figure: 

   
   <?xml version="1.0"?>
   <CustomPropertyMapping>
      <VirtualEntityManagerList>
          <VirtualEntityManager>
              <name>_hostname_1_</name>
              <type>VMware vCenter</type>
              <property name="location"       defaultValue="Boston"            isMap="false"  customProperty=""  />
              <property name="owner"          defaultValue="BMC"             isMap="false"  customProperty=""  />
              <property name="expiry date"  defaultValue="2009-08-21 14:07:20" isMap="false"  customProperty=""  />
          </VirtualEntityManager>
          <VirtualEntityManager>
              <name>_hostname_2_</name>
              <type>VMware vCenter</type>
              <property name="location"       defaultValue=""  isMap="true"  customProperty="VM location"    />
              <property name="owner"          defaultValue=""  isMap="true"  customProperty="VM owner"       />
              <property name="expiry date"  defaultValue=""  isMap="true"  customProperty="VM expiry date"/>
          </VirtualEntityManager>
      </VirtualEntityManagerList>
   </CustomPropertyMapping>
   

    Where <hostname> is the fully qualified VMware vCenter server name or IP address.

2. Do one of the following:
   • Specify that the lifecycle property values be imported from the default values specified in the mapping file. The example shown for hostname_1 in the above example shows how you would enter the default values in the mapping file.

   • Specify that the lifecycle property values be retrieved from the virtual entity manager (for example, the vCenter server) by mapping custom properties on the virtual entity manager to each of the supported properties. The example shown for hostname_2 in the aboce example shows how you would retrieve properties from the virtual entity manager using the isMap attribute.

     The macro unmigrated-inline-wiki-markup from Confluence is no longer available.

     The macro unmigrated-inline-wiki-markup from Confluence is no longer available.