Search for	Example	Results
A single word	`cat`	Topics that contain the word "cat". You will also find its grammatical variations, such as "cats".
A phrase. You can specify that the search results contain a specific phrase.	`"cat food"` (quotation marks)	Topics that contain the literal phrase "cat food" and all its grammatical variations. Without the quotation marks, the query is equivalent to specifying an OR operator, which finds topics with one of the individual words instead of the phrase.

Search for	Operator	Example
Two or more words in the same topic	`AND` `and` `+` (plus symbol) `&` (ampersand)	`cat AND dog` `"cat food"+milk` `"cat food"&"dog food"`
Either word in a topic	`OR` `or` `\|` (pipe)	`cat OR dog` `cat \| dog`
Topics that do not contain a specific word or phrase	`NOT` `not` `!` (exclamation point)	`NOT cat` `! dog`
Topics that contain one string and do not contain another	`^` (caret)	`cat ^ mouse`
A combination of search types	`( )` parentheses	`cat + (dog \| mouse)` `cat \| dog + (! mouse)`

Operations Manager i10.62

Administer > Setup and Maintenance > Monitored Nodes > Configure HTTPS communication > Configure two-way communication > Redirect HTTPS communication through proxies

Redirect HTTPS communication through proxies

You can redirect connections from OMi servers to HPE Operations Agents that are on different networks through a proxy.

The figure below shows connections between OMi servers and an agent through a load balancer and an HTTP proxy as follows:

The gateway server (1) opens connections to the proxy (2), for example to deploy policy templates and instrumentation or to launch actions. The proxy opens connections to the monitored node (3) on behalf of the gateway server, and forwards communication between them.

The gateway server (1) also opens connections to the data processing server (5) to forward certificate requests.
The monitored node (3) opens connections to the load balancer (4), for example to send events and action responses. The load balancer forwards communication to a gateway server (1) on behalf of the monitored node.
The data processing server (5) opens connections to the proxy (2), for example to send certificates. The proxy opens connections to the monitored node (3) on behalf of the data processing server, and forwards the certificate to the monitored node.

You can also redirect communication through proxies in more complex environments as follows:

The gateway server (1) opens connections to the proxy (2), for example to deploy policy templates and instrumentation or to launch actions. The proxy opens connections to the monitored node (3) on behalf of the gateway server, and forwards communication between them.

The gateway server (1) also opens connections to the data processing server (5) to forward certificate requests.
The monitored node (3) opens connections to the proxy (2), for example to send events and action responses. The proxy opens connections to the load balancer (4) on behalf of the monitored nodes, and the load balancer forwards communication to a gateway server (1).
The data processing server (5) opens connections to the proxy (2), for example to send certificates. The proxy opens connections to the monitored node (3) on behalf of the data processing server, and forwards the certificate to the monitored node.

Learn More

Example PROXY parameter values

To configure a node to use proxy1.example.com on port 8080 for all outbound connections, use the following value:

proxy1.example.com:8080
To configure a gateway server to use proxy2.example.com:8080 to connect to any host with a hostname that matches *.example.com or *example.org except hosts with an IP address in the range 192.168.0.0 to 192.168.255.255, use the following value:

proxy2.example.com:8080+(*.example.com,*.example.org)-(192.168.*.*)
To extend the above example to use proxy3.example.com to connect to backup.example.com only, use the following value:

proxy3.example.com:8080+(backup.example.com); proxy2.example.com:8080+(*.example.com,*.example.org)-(192.168.*.*)

In the above example, proxy3.example.com:8080+(backup.example.com) must be first, because the include list for proxy2.example.com contains *.example.com.

How to redirect HTTPS communication through proxies

Log in to the system that you want to configure as a user with administrative rights and open a command prompt or shell.
On systems that run a UNIX or Linux operating system, ensure that the PATH variable contains the path to the agent commands.
- On HP-UX, Solaris, or Linux, type export PATH=/opt/OV/bin:$PATH and then press Enter.
- On AIX, type export PATH=/usr/lpp/OV/bin:$PATH and then press Enter.
Specify the proxies to be used. You can specify different proxies to use depending on the host that the server wants to connect to. Type the following command on the gateway servers, data processing servers, or HPE Operations Agent systems:

ovconfchg -ns bbc.http -set PROXY <proxy>