Unable to access Operations Connector(2019.05) user interface due to dependency of adobe flash (EOL)
Facing issue in accessing Operations Connector(2019.05) user interface due to dependency of adobe flash which is currently EOL.
Any solution for this.
Thanks for the response.
As per the below instructions provided in Operations connecter Install guide (Link), is it not possible to access the operations connector user interface.
To access the Operations Connector user interface from a supported web browser, enter the following URL:
You need to import the policies on the OBM server to manage them from there.
Here a high level description of the procedure that you could use:
- Run ovpolicy -list -level 3 on the connector node and note the <policy_ID> of the policies that you want to import on OBM
- Locate the files like <policy_ID>_data and <policy_ID>_header.xml under <DataDIr>/datafiles/policymanagement/store
- Copy these files to a <TempFolder> on your OBM gateway
- On the OBM gateway, import the policies with:
# ConfigExchange.sh -username admin -password ... -uom -i <TempFolder> -v
- You should now find your policies in the OBM console in "Administration > Monitoring > Policy Templates"
- Organize these policies into aspects, add your customizations, assign them to the connector node
This is a high level description and I have not tested it.
Thanks for sharing the details.
We have our Operations connector installed for our domain manger. Can you please let us know if we can use command line utility (bsmc-policy.bat) to manage the policy in Operations Connector node.
Options are limited and the way forward really is using the OBM server itself
This is how you would use bsmc-policy.[sh|bat]: https://docs.microfocus.com/itom/Operations_Connector:10.11/policy_management/Import_policies
You can also use ovdeploy to do some work.
What specifically did you want to do?
We ( @rajshekar_p and team) are using our own implemented "Operations Connector for Domain Manager"(Plugin) for Topology and Event Collection by defining policies that are imported and managed in Operations Connector.
We found out that from January onwards browser stopped supporting adobe flash and hence policies cannot be managed via a browser anymore. As an alternative can we continue to manage (import, activate, deactivate) the policies via command line using bsmc-policy tool without switching to the OBM policy management (new HTML 5 based UI).
From operations Connector the expectation is to Manage Policies and Edit policies defined.
We would like to know is it ok to continue using command tools as an alternative for the browser way of managing the policies.
Also, we would like to know what are the limitations if we continue using the command line tools for policy management in Operations Connector.
The command line allows you to perform most actions (e.g. enable/disable and add/modify/delete the policy). I guess you can script most of the steps so it doesn't get too tedious.
The downsides - policies are not stored in the OBM database meaning they are not backed up unless you backup the OpsCx node. You cannot deploy automatically to the managed node and you've got no versioning. Gven a choice, I'd deploy and manage policies from the OBM server.
https://www.microfocus.com/productlifecycle/lifecycleITOM.jsp?term=Operations%20Bridge%20Manager shows how long you will receive support for OpsCx. The issue here is that Adobe Flash player is no longer supported which is why I'd play for the long term and start deploying policies from OBM as was suggested earlier.
I know it's your choice but I would like to understand what don't you like about importing the policies into OBM and managing them from the console?