OMi - What is it really?!
There's been a lot of confusion (on my part as well, I must confess) about what exactly OMi is, and how it works. On the plus side, I've just had a great chat with one of the developers & two of the solution architects to help me finally understand what it is, how it works, and why you might want it.
First things first - OMi is a name only appreciated by the marketing team because it has caused mass confusion - OMi is NOT the next version of OMW in the way that NNMi is for NNM. OMi is a "layer-on-top" tool that enhances your troubleshooting & root cause analysis capabilities for OMW/OMU (and OML?) and comes as part of the BAC suite. By purchasing & installing OMi you get BAC, and must install & operate the BAC server. So this loops back to those still running OVIS and wondering about what they'll need to do about moving off of it (topic for upcoming post - OVIS migration to BAC).
If you want to make use of OMi you need to do a couple of things...
1. Have OMW or OMU running with all requisite SPIs
2. Get your NNM up to NNMi (unless you don't have it, then skip this step)
3. Install BAC & OMi (kind of one step...)
4. In installing BAC & OMi you by default install uCMDB, which must now be configured
5. Run the automated configuration tool to pull the data from your OMW/U tool to populate the uCMDB
6. Start to configure your dashboards and views
Of course, I've grossly over-simplified, but it's a roadmap to get you started. As always - if you have specific questions you'd like me to answer or thoughts you'd like to share on any of this please reply to the postings!
Taking the "blah" out of blogging on IT Project, Service, and Operations management topics.
No comments:
Post a Comment