HP OMi 10: opr-jobs command to manage deployment jobs

HP OMi 10, with Monitoring Automation feature, designed for Automatics policies assignment and Deployment.

But for some reason, sometime deployment jobs if fail due to agent connection problem for instance.

Even after agent connection establish , when deployment jobs fail, you have to restart the deployment jobs through GUI: 
Administration => Monitoring => Deployment Jobs
then select failed jobs, right click and restart deployment jobs.

there is alternative way to managed redeployment jobs using command line: 
<BSM_HOME>/opr/bin/opr-jobs.sh | bat <conection> -start

here the example:

If you want only redeploy failed jobs, use following:
<BSM_HOME>/opr/bin/opr-jobs.sh | bat <conection> -start failed


HP BSM

HP OMi 10: New version. What new and impact on the architecture?

Early this year, HP has released new HP Operation Manager i 10 which bring new architecture for Operation bridge families of HP Software.

http://www8.hp.com/us/en/software-solutions/operations-manager-i-operations-management/try-now.html

The main thing that shipped with this new version are:

• OMi now separated from BSM. BSM will mainly focused on the Application Performance Management (APM). A long with OMi 10 release, HP APM 9.25 also released.
• Monitoring Automation (MA) also will shipped together with OMi 10, no need separate installation to get MA feature on the OMi 10, like on the BSM 9.2x.

What the impact on your architecture?

Here I'll only discuss on the new deployment of the OMi. Later on, I plan to post the impact on the existing BSM/OMi/MA/OM deployment.

Why you need OMi?

That the first question that should come on your mind to decided for deploying of OMi.

OMi is designed as single event consolidation dashboard. You desired to have single pane of glass for events.

You have multiple events source which need to be consolidate and correlated. That is the perfect scenarios to bring OMi.

OMi naturally will consolidate Agent base event (from HP Operation Manager) and Agent-less event from SiteScope for Server and Application event.

OMi has integration with NNMi for Network base event which will give you much visibility on your entire infrastructure events.

Also, OMi shipped with various BSM Connector, to integrated third parties EMS:

IBM Tivoli

Zenoss

BMC Impact Manager

VCenterOps

Nagios

SCOM

What is Monitoring Automation?

Monitoring Automation which introduced on HP BSM 9.22, bring capability of BSM/OMi as Management Server, like HP Operations Manager. 
Yes, you can create monitoring policies, deploy policies,upload instrumentation and update installed Operation Agent.
And also for SiteScope (Agent-less)
Even more...AUTOMATION. I'll post another topic related to Monitoring Automation

What impact on your new deployment architecture?

By design, OMi 10 now is HP BSM with focused on Operation Bridge, and Monitoring Automation. Completely separate from HP BSM/APM.

You'll not found following feature when installing HP OMi:

• End User Management (HP BPM or HP RUM)
• Service Level Management
• Diagnostics
• System Availability Management (SiteScope UI), but you still have Event/Topology integration, and SiteScope monitoring configuration via Monitoring Automation.

On OMi 10 you will have:

• Operation Management complete feature (event browser, TBEC, SBEC etc)
• Service Health
• MyBSM (renamed as Workspace) and its component plus OOTB Pages
• RTSM as Foundation configuration management

How I can get complete feature of BSM 9.2x on OMi?
Integration. You can integrate HP BSM 9.2x/APM 9.2x to OMi 10 get complete feature.
End user monitoring event and HI can be sent to OMI.
Event from OMi can be sent to APM 9.2x to feed SLM.
I also plan to post on separate topic for OMi - APM integration.

Note: for future, I'll use APM instead of BSM.

HP OMi 10: opr-agt TARGET option

TARGET option

-query_name <query_name> | -view_name <view_name> | -filter_name <filter_name> | -node_list <node_list> [-dont_check_database] | -node_group <node_group> | -all



Option	Description
{‑query_name|‑qn} <query_name>	Performs the operation on monitored nodes selected by the specified TQL query.
{‑view_name|‑vn} <view_name>	Performs the operation on monitored nodes selected by the specified view.
{‑filter_name|‑fn} <filter_name>	Performs the operation on a list of monitored nodes with the HP Operations Agent installed that was obtained by applying the node filter.
{‑node_list|‑nl} <node_list> [-dont_check_database|-nodb]	Performs the operation on a list of one or more monitored nodes. The nodes must exist in the RTSM and must be associated with a CI of the type om_operations_agent. Separate multiple nodes with commas (for example, node1.example.com,node2.example.com). If used with the -dont_check_database option, the operation on the nodes is performed without checking if the nodes exist in the RTSM.
{‑node_group|‑ng} <node_group>	Performs the operation on a group of monitored nodes. A node groups is a CI collection containing hosts. Node groups can be maintained in the Monitoring Automation Node Editor or they can be imported through topology synchronization from HPOM to OMi. The nodes must exist in the RTSM and be associated with a CI of the type om_operations_agent. Specify node groups by their names or their paths (the latter applies to hierarchical node groups imported from HPOM for Windows).
-all	Performs the operation on all monitored nodes that have the HP Operations Agent installed (that is, nodes that are associated with a CI of the type om_operations_agent).

HP Omi 10: remote agent operation opr-agt command - General

The opr-agt Command-Line Interface

You can use the opr-agt command-line interface (CLI) to manage and configure the HP Operations Agent on one or more monitored nodes:

• Get the current status of the agent processes.
• Start or restart the agent processes.
• Shut down (stop) the agent processes.
• Return the version number of the installed HP Operations Agent software.
• Return the setting of configuration variables.
• Set configuration variables to a specified value.
• Switch the primary manager.
• Deploy configuration.
• Sets the primary manager for event reception (primary event receiver)

This command equivalent to opcragt on the HP Operation Manager.

The opr-agt command-line interface first contacts the RTSM to retrieve a list of monitored nodes. It then contacts up to 50 nodes in parallel to perform the requested operation. When you run an operation on more than one monitored node, opr-agt displays the status immediately after a remote operation finishes for each node. 

You can run opr-agt on a gateway or a data processing server. On the server, the server processes must be running, and the ovcd and ovbbccb processes must be running on the monitored node.

Location

<OMi_HOME>/opr/bin/opr-agt 

Synopsis

opr-agt <BSM_CONNECTION> <operation> <targets> <authentication> <toolInfo> 

Please follow the below link to see more detail explanation for each option:

<BSM_CONNECTION>

HP OMi 10: opr-agt BSM_CONNECTION option

BSM_CONNECTION Option

Please follow this link for general description of opr-agt


Syntax:

-username <login name> -password <password> ([-port <port>] [-server <GatewayServer> [-ssl] | -url <url>]) [-customer <customer ID>]




Note: If <BSM_CONNECTION> is omitted, the command is executed on the server to which you are logged on.

Option	Description
{-username|-user} <login name>	Sets the login name of the user required to execute CLI operations on the target gateway server.
{-password|-pw} <password>	Sets the password for the specified user. Default value: empty string
{-port|-p} <port>	Uses port <port> to connect to the target gateway server. Default value of <port>: 80 for HTTP connections 443 for HTTPS connections
-server <GatewayServer>	Sets the target gateway server, using <GatewayServer> as the hostname or IP address to locate it. Default value of <GatewayServer>: FQDN of the OMi gateway server
-ssl	When this option is specified, the HTTPS protocol is used to connect to the target gateway server. If omitted, the HTTP protocol is used. Cannot be used in conjunction with the -url option.
{-url|-u} <url>	Sets the target gateway server, using <url> as the URL to locate it. Default value of <url>: http://<OMi gateway FQDN>:80/opr‑config‑server/rest
{-customer|-cu} <customer ID>	Sets the identification number associated with a particular customer. Default value: 1 Only applicable if you have multi-tenancy on the RTSM.