Absent Member.. Absent Member..
Absent Member..

OMi Custom attributes can't send to SM Incident

Hi all,

I'm doing a BSM(OMi) 9.21- SM 9.20 integration with groovy script and BDMapping.

Now I already done a event forwarding from OMi to Service Manager.

1.- OMi send an event to SM.
2.- SM open an IM and returns the id to Omi.

Well, the SM incident needs some fields that I only can send with a custom attribute in a OMi event. I'm configured the OMi event with some custom attributes but when I publish in a groovy and configure in a BDM mapping this CA fields don't write in a IM.

Do I need a special configuration in the groovy script for publish the custom attributes?. I need a special configuration in the BDM mapping too?

The BSM Extensibility Guide describes the Custom Attributes configuration:

In a MapOPR2SMCustomAttribute tag in a groovy script I have defined some like this:

private static final Map<String, String> MapOPR2SMCustomAttribute =["producttypeCA" : "SMCustomAttribute", "serviceCA" :  "SMCustomAttribute"]

on "serviceCA" and "producttypeCA" are a Custom Attributes in OMi event.

The guide talk about "Add a CA name to the map along with a Service Manager incident property name (XML tag
name)." I suppose that I have to write in a <<SM Incident XML tag names & constants>> part on the groovy script the serviceBS Custom attribute like this:

private static final String SERVICECA = "servicioBS"
private static final String PRODUCTTYPECA = "producttype"

in a Incident BDmapping 1.1 in SM I configured like this:

SM Object field |  Direction | BDM Object Field/Attribute
assignment               <->                   servicioBS
product.type             <->                  producttype

The data never arrives from OMi event to IM service Manager.

If I configure in the BDM the field "SM Callback" like this
and the BDM Object Field/Attribute  leaves blank the integration runs well.

Where can I look the information that OMi sends to SM?

Anybody runs the OMi integration to SM incident using the Custom attributes in OMi?

Best regards,

David Ferreiro
Service Delivery

Business Applications Engineer - ITILv3 Consultant

Hewlett-Packard CDS

Labels (1)
7 Replies
Established Member..
Established Member..

Hi David,


Did you get to send the custom attributes to SM incident?

I have the same problem to send this.


Thank you so much,


Ramirez Franco

Absent Member.. Absent Member..
Absent Member..



Did you find the solution for this problem? Im also having trouble with BDM mappings.




Contributor.. Contributor..

Hi, Any updates for the above question.


I am facig a similar issue, I am trying to send the field "application" from omi to SM but its not happening..



N V Rakesh

Super Contributor.
Super Contributor.




Did you people got the solution for the above.


Because I am also facing with the field Affected CI(logical.name).


I have integrated with SM and BSM for event forwarding ,I am able to create the IM ticket but the logical.name field is not mapping it,it is showing empty field.


Here in my environment we have not used the UCMDB integration ,instead there is direct integration with BSM and SM using BDM Mapping.



So please help me out how to populate the logical.name field in IN ticket.


Thanks and Regards,




Absent Member.. Absent Member..
Absent Member..

Dear All, 

 Did you got the solution. I am also facing the similar issue. 


Super Contributor.. Super Contributor..
Super Contributor..


Did you have the solution for that problem?

I have the similar issue. the version of HP SM is 9.3x and the HP BSM is 9.2x.

if exist an document, is posible to share us?

Thank You




Valued Contributor.. Valued Contributor..
Valued Contributor..

mail me at--> cases.hp@GMAIL.COM 





In the original post If you are mapping the assignment field turn off the field validation....


In case you are not getting the CI name make BSM as the global id generator..

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.