How do I customize export data to BMC Atrium CMDB?

To customize the default integration

To customize the default integration through a site specific file

To disable a port definition in the override file

It is recommended that you consult with your Entuity Professional Services representative before amending the Entuity integration module for BMC Atrium CMDB.

To customize the default integration:

To amend the information Entuity exports to BMC Atrium CMDB, you must configure both Entuity data export and the BMC Atrium CMDB application context.

1. Add new attributes to the Data Export Data Sets configuration file:

   sw_data_export_def_atrium_override.cfg

   You must edit the override file, because the tables provided with the integration are marked as read-only when accessed through the web UI.
2. Include the amended data export configuration to the Entuity server set-up. In:

   sw_data_export_def_site_specific.cfg

   include:

   sw_data_export_def_atrium_override.cfg

   You do not have to run configure, wait for Entuity to discover the new configuration.

3. Specify the override attributes in a site specific XML file, for example:
   

   entuity_home/etc/atrium_applicationContext1_site_specific.xml

   The name and location of the override file is defined in:
   entuity_home/integ/Atrium/classes\applicationContext.xml through an import command:

   <import resource="file:${entuity.home}/etc/atrium_applicationContext*_site_specific.xml" />

   The filename includes a wildcard character, an asterisk(*), which you can replace with 1 or more characters. In this way you could include multiple files through this 1 import command.
4. You will then need to log in to the database and drop the AtriumExport database:
   Log in, e.g.:
   

   entuity\database\bin\mysql -u root

   then drop the AtriumExport database:
   

   drop database AtriumExport

5. Rebuild AtriumExport database:

   <entuity_home>/integ/Atrium\bin>atriumExporter.exe -c

6. You can manually run or schedule data export to populate the AtriumExport database.
7. When atriumExporter runs (configure through provost_site_specific.conf and provost_atrium_exporter.conf), it forwards data to BMC Atrium CMDB.

To customize the default integration through a site specific file:

You can override the attributes in the default integration through a site specific file.The name and location of the override file is defined in the applicationContext.xml file and must conform to the template name (see Customized Integration Process Overview).

entuity_home/etc/atrium_applicationContext1_site_specific.xml

The following example file includes examples of how to remove, amend and add attributes.

The initial part of the XML file is its definition and this must remain unchanged.

<?xml version="1.0" encoding="UTF-8"?>
<beans xmlns="http://www.springframework.org/schema/beans"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:util="http://www.springframework.org/schema/util"
xsi:schemaLocation="http://www.springframework.org/schema/beans
http://www.springframework.org/schema/beans/spring-beans-2.0.xsd
http://www.springframework.org/schema/util/
http://www.springframework.org/schema/util/spring-util-2.0.xsd">

This section removes a specific attribute that is already defined, the Speed attribute from the portCIDefinition table.

<bean factory-bean="portCIDefinition" factory-method="removeAttr-Byname">
<constructor-arg value="Speed" />
</bean>

This section adds a new attribute, Alias, to the portCIDefinition table. The data export job
must also be amended to export the new value. Changing a supplied data export definition
can only be achieved through the configuration file.

<bean factory-bean="portCIDefinition" factory-method="addAttribute">
<constructor-arg>
<bean   class="com.entuity.bmc.CIAttributeValue">
<property name="name"  value="Alias"/>
<property name="dataExportColumnName" value="swc_alias"/>
</bean>
</constructor-arg>
</bean>

This section changes the value of a specific attribute to value defined in the configuration. The example includes different data types.

<bean factory-bean="portCIDefinition" factory-method="getAttrByName">
<constructor-arg value="Item" />
<property name="stringValue" value="SOME_STING_VALUE" />
<property name="intValue" value="33" />    <!-- OR -->
<property name="longValue" value="5000" />    <!-- OR -->
<property name="doubleValue" value="66.77" />    <!-- OR -->
</bean>

This section changes a set of mapped attribute for an already attribute.

<bean factory-bean="portCIDefinition" factory-method="getAttrByName">
<constructor-arg value-"PortType" />
property name="mapValues">
- <props>
<prop key="6">Ethernet</prop>
<prop key="7">Ethernet</prop>
<prop key="26">Ethernet</prop>
<prop key="62">Ethernet</prop>
<prop key="69">Ethernet</prop>
<prop key="117">Ethernet</prop>
<prop key="15">FDDI</prop>
<prop key="9">Token Ring</prop>
<prop key="115">Token Ring</prop>
<prop key="56">Fibre Channel</prop>
<prop key="default">Unknown</prop>
</props>
</property>
</bean>

This section changes the value of a specific BMC class to value defined in the configuration, from BMC_ComputerNetwork to BMC_ComputerSystem.

<bean factory-bean="deviceCIDefinition" factory-method="getInstance">
<property name="name" value="BMC_ComputerSystem"/>
</bean>
</beans>

To disable a port definition in the override file:

To disable a port definition in the override file, you must specify the following:

<bean id="portCIDefinition"  class="java.lang.String"/>
<bean id="deviceAddressCIDefinition"  class="java.lang.String"/>