The following is a guest post by Carol Park, R&D OpsBridge Specialist
Image courtesy of blog.exair.com
- Central configuration
- Organize the policies into groups and aspects, such as OneView, Microsoft SCOM, Nagios, etc.
- Assign and deploy to multiple Operations Connector systems (test/production, primary/backup)
- User permissions, for managing Operations Connector policies, are controlled centrally from OMi.
- Create a content pack for copying content to other OMi servers.
- Version control
- Maintain multiple versions of a policy, allowing you to revert to a previous version if needed.
- As with other OMi policies, you can define parameters in the policies such as the polling frequently of a structured log file or login credentials of a database policy.
- Instruction Text and Actions
- The OMi policy editors for policies that generate events (Events from DB, Events from Perl Scripts, Events from REST web services, Events from Structured Logfiles) enable you to configure Instruction Text and automatic and operator-initiated actions, just like any other type of OMi policy that generates events.
- The OMi policy editors allow you to select instrumentation to be deployed with the policies. For example, if you configure an Event from Perl Script policy to execute a local automatic action in one of the rules, then you can create instrumentation and associate it with the policy to ensure it is deployed with the policy.
Benefits of Operations Connector policy editor
Having said that, the Operations Connector policy editors provide two benefits:
- Policies that get events or metrics from a database data source have "Execute SQL statement" buttons. They let you test your database connection and SQL statement, and have access to the resulting sample data to assist in policy creation. These are significant benefits when working with database policies, so you may want to either continue to manage these policies in Operations Connector or use one Operations Connector to create and test the policies which you later upload to OMi for centralized assignment and deployment to multiple Operations Connectors.
- Policies that get events or metrics from a structured log file source allow you to load sample data from either the local file system or the Operations Connector server. The corresponding OMi policy editor allows you to load sample data from the local file system only. Thus, you may have an extra step to copy the file to the machine where you are running the browser if you want to work with the sample data when editing the policy from OMi.
While it is your choice to configure Operations Connector policies from either OMi or the Operations Connector UI, do not attempt to manage the same policy from both places. For example, policies deployed from OMi don’t appear in the Operations Connector policy management UI.
How to import existing policies from Operations Connector to OMi
If you choose to manage Operations Connector policies from OMi, you can import existing Operations Connector policies to OMi as follows:
- Copy the policies from Operations Connector to a temporary directory on the OMi You can find the Operations Connector policies in:
Note: If the policy contains a category, which you can see by editing the policy in the Operations Connector Policy Editor UI and looking at the Properties tab, then OMi assumes that there must be instrumentation of the same name. Since there is no instrumentation, you need to edit the policy and remove the category before copying the policies to OMi.
- Upload the policies to OMi:
Linux: /opt/HP/BSM/opr/bin/ConfigExchange.sh –user admin –uom –i
Windows: %TOPAZ_HOME%\opr\bin\ConfigExchange –user admin –uom –i
- Use the capabilities of OMi to organize the policies into aspects which you either assign directly to the Operations Connector node or create automatic assignment rules.
- Deploy the policies from OMi. This will overwrite the existing policies deployed to the agent on the Operations Connector.
- On the Operations Connector, delete the policies from the policy management store directory to avoid using them by mistake. If you are managing a subset of policies from OMi, then you need to know the policy IDs to delete selectively from the policy management store directory. You can get the policy IDs via the Operations Connector UI by clicking the Options button and selecting to display the Policy ID column.
Note: If you do change a policy in Operations Connector and want to upload the change to OMi, you will need to delete the existing version 1.0 from OMi before uploading so that it can upload a new 1.0 version.
There are many benefits to managing Operations Connector policies from OMi, particularly for environments where you have multiple Operations Connector servers. Please feel free to share your own experiences or raise questions.
You can join us to get sneak peeks at some of our new capabilities in Berlin and learn more about evolving to OpsBridge from your peers who have already begun, as well our experts.
The EMEA BSM Customer Forum in Berlin May 11-13th 2016 is now open to registrations Berlin
Customers KMD Denmark and Turkcell have sessions covering their OM2OpsBridge journey, and other session by our experts will also show you some of the benefits our customers have found by adopting the Operations Bridge.
Try OMi now! OMi 10.10 comes pre-loaded with a number of Management Packs that you can try out without the hassle of getting management pack software or evaluation license.