HP_Openview网络管理数据抽取,表现和汇总.ppt

* Once you’ve build the template, now we need to let SR know it exists. This requires a few simple steps: * This user interface for adding a new report definition is straightforward… OK, so you can see how easy it is to add your own report. Here’s one way that we’re taking advantage of open data sources and the Service Reporter... * This integration is under development, but I wanted to share with you what you can look forward to in the future. This integration project primarily consists of: - adding templates that report data from the NNM 6.0 data warehouse - using NNM topology information to help MW agents be discovered - using SR’s “repload” utility to automatically schedule reports - documentation for making the NNM DW connection easy * Sample reports... * More sample reports… THIS CONCLUDES my SR-specific discussion. Questions? * Now, let’s wind things down a bit by talking some things you need to think about before implement reporting at this level in your organization. Here are three topics that come to mind: * Which one do you use? It depends! If your environment is C/S, NNM availability may be very important, as network connectivity is crucial. NNM’s ECS circuits may further help describe what is going on ITO is ideal place, as the agent may provide additional (correlative) information regarding why there is an availability issue * Once again, there is more than one way to achieve an objective But, you need to determine how you will approach this * Here is an example that touches on a number of products in our portfolio. * Before you go back, I suggest you consider these four issues. Basically, this is a ready-aim-fire approach. * Finally, here are some gotchas to avoid: * So, if I had to summarize what we talked about in just one picture... * In this case, this is an unformatted result of a query... * ITO version 5 offers many new features, including: * integration with Service Navigator * integration with OpenView Service Reporter * Ext