Xinify has built an integration between SMS 2003 and CMDB 2 /Asset 7 using Remedy Link for SQL 7. The integration is in closed beta at the moment but will soon be available FREE to the BMC community. We were commissioned by BMC to build this integration and it was done with the full support of Remedy Engineering.
A little background - The product Remedy Discovery Services for SMS is based on Enterprise Integration Engine (EIE) and an adapter was built to talk to SMS via WMI. This was revised/updated to work with EIE 7 but there are no out of box mappings and it is is really slow. An alternative was demanded by several customers. That's were we come in.
The Microsoft SMS Atrium Integration is using Remedy Link for SQL, also based on EIE, but going directly to the SQL tables and views. The reason we went this way is because is is exponentially faster. Additionally, our integration comes with the "mapping and exchange" work already done. Mapping is EIE term for basically doing push field from a source to a target. Echanges are the containers that run like an escalation to trigger the mappings to run. The mappings create/update/delete(if desired) CIs and Relationships in Atrium. Not only that but it includes workflow to cleanse and normalize some data and includes sample reconciliation rules and categorization workflow. It is as close to plug and play as you can get considering both SMS and Remedy applications could have been customized.
-------- Original Message --------
Subject: Remedy/SMS with xinify
From: "McKenzie, James J C-E LCMC HQISEC/L3"
<[EMAIL PROTECTED]>
Date: Thu, September 07, 2006 1:30 pm
To: [email protected]
**Again, another request for comments and best practices advise on this comibination?James McKenzieL-3 GSI__20060125_______________________This posting was submitted with HTML in it___
