Highlighted
Absent Member.. Absent Member..
Absent Member..
109 views

UCMDB Support Tip: Customize ucmdb id pushback for a CI type

Out-of-the-box, UCMDB pushes the ucmdb id of each CI type back to Service Manager during population, by calling a Service Manager web service (ucmdbIDPushBack based on the ucmdbid.pushback.request and ucmdbid.pushback.xslt settings in the sm.properties file in UCMDB. To better suit your business needs, you can make the following tailorings to the ucmdb id pushback feature, using the <idPushbackConfigurations> element in the ServiceDeskConfiguration.xml file:

 

• To disable the ucmdb id pushback feature for a specific UCMDB CI type - for example:

UCMDB classes that are mapped to a sub-item type (IP Address, CPU, etc.) in Service Manager. Doing so can avoid unnecessary system overload. To disable the pushback feature for a UCMDB CI type (class), use this format:

<idPushbackConfiguration ucmdbClassName="<ucmdbClassName>"

idPushbackEnable="false"/>

Where, <ucmdbClassName> is the name of the UCMDB CI type.

Here are the out-of-the-box settings in the ServiceDeskConfiguration.xml file:

<idPushbackConfigurations>

<idPushbackConfiguration ucmdbClassName="interface"

idPushbackEnable="false"/>

<idPushbackConfiguration ucmdbClassName="cpu" idPushbackEnable="false"/>

<idPushbackConfiguration ucmdbClassName="disk_device"

idPushbackEnable="false"/>

<idPushbackConfiguration ucmdbClassName="file_system"

idPushbackEnable="false"/>

<idPushbackConfiguration ucmdbClassName="ip_address"

idPushbackEnable="false"/>

</idPushbackConfigurations>

 

To enable the pushback feature for a CI type, set idPushbackEnable="true" for it.

 

• To define a custom pushback web service and xslt file for a specific CI type -there are occasions when you need to define a custom pushback web service and XSLT for a specific CI type (class), for example, when a CI type you want to populate is not stored in the device table in Service Manager. This is because the out-of-the-box ucmdbIDPushBack web service is based on the device table. For example, you have tailored the integration in order to populate the Functional Group from Service Manager to UCMDB. If the Functional Group in Service Manager is not stored in the device table, you can define a custom web service and XSLT like the following:

<idPushbackConfigurations>

<idPushbackConfiguration ucmdbClassName="functional_group"

idPushbackEnable="true"

idPushbackRequest="UpdateucmdbIDPushBackForFunctionalGroupRequest"

idPushbackXSLT="ucmdbid_pushback_functionalgroup.xslt"/>

......

</idPushbackConfigurations>

 

Please note to support your pushback customizations, you need to create the specified custom web service record in Service Manager and XSLT file in UCMDB.

"HP Support
If you find this or any post resolves your issue, please be sure to mark it as an accepted solution."

Click the KUDOS star on the left to say 'Thanks'
Labels (1)
Tags (1)
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.