Push Windows CIs to Atrium

I want to push Windows CIs (v10.01) to Atrium (v8.1) using the Atrium Push adapter.  The data models for uCMDB and Atrium are fundamentally different in how they store this data.  uCMDB stores the OS info as attributes to the Computer (Windows) CI where Atrium stores the OS info as a separate CI from the Computer CI and creates a relationship between them.  I can push the Windows CI to the BMC_ComputerSystem CI, but how can I push the attributes to create the OS CI and, more importantly, create a relationship in Atrium where no such structure exists in uCMDB.  The HP documentation for the xml mapping seems to indicate that a source relationship must exist in uCMDB to create a target relationship in Atrium.  This seems like the most basic transfer of data (a computer and its os) from uCMDB to Atrium, yet the documentation doesn't seem to address it.

Parents
  • Hello toadstool,

    Yes, Atrium 8.1 integration is supported with HP uCMDB 10.01.
    You will need to use export data to Atrium package.
    To setup the integration various JAR and DLL files are required from the BMC Remedy/Atrium systems. These JAR/DLL files are listed in the integration deployment guide that accompanies this package.
        
    Best Regards,
    Nikola

  • Yes, I am aware it is supported and have it set up and verified functional in accordance with the integration guide.   My post was a question about how to push specific CIs and relationships when the data models do not match between HP and Atrium.

     

     I can push the Windows CI to the BMC_ComputerSystem CI, but how can I push the attributes to create the OS CI and, more importantly, create a relationship in Atrium where no such structure exists in uCMDB.  The HP documentation for the xml mapping seems to indicate that a source relationship must exist in uCMDB to create a target relationship in Atrium.  This seems like the most basic transfer of data (a computer and its os) from uCMDB to Atrium, yet the documentation doesn't seem to address it.

Reply
  • Yes, I am aware it is supported and have it set up and verified functional in accordance with the integration guide.   My post was a question about how to push specific CIs and relationships when the data models do not match between HP and Atrium.

     

     I can push the Windows CI to the BMC_ComputerSystem CI, but how can I push the attributes to create the OS CI and, more importantly, create a relationship in Atrium where no such structure exists in uCMDB.  The HP documentation for the xml mapping seems to indicate that a source relationship must exist in uCMDB to create a target relationship in Atrium.  This seems like the most basic transfer of data (a computer and its os) from uCMDB to Atrium, yet the documentation doesn't seem to address it.

Children