Searching the Help
To search for information in the Help, type a word or phrase in the Search box. When you enter a group of words, OR is inferred. You can use Boolean operators to refine your search.
Results returned are case insensitive. However, results ranking takes case into account and assigns higher scores to case matches. Therefore, a search for "cats" followed by a search for "Cats" would return the same number of Help topics, but the order in which the topics are listed would be different.
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 |
|
|
Either word in a topic |
|
|
Topics that do not contain a specific word or phrase |
|
|
Topics that contain one string and do not contain another | ^ (caret) |
cat ^ mouse
|
A combination of search types | ( ) parentheses |
|
Port Usage
This section provides a list of the ports that are used by OMi. This list can be used as a tool for troubleshooting, monitoring and ensuring OMi servers are configured correctly. In addition, instructions are provided for configuring some of these ports.
Learn more
Some of the listed ports are only used for troubleshooting access to the application via the Java Management Extensions (JMX) consoles. It is important, however to have access to these ports so that data from OMi can be quickly accessed and issues can be identified.
Note An extensive range of ports are used between the OMi data processing server and gateway server for the use of Java’s Remote Method Invocation (RMI) protocol. HPE Software does not advise or support the use of operating system firewalls on either of these servers. HPE Software does not advise or support having firewall servers installed between these OMi servers.
Port | Description | Connection | Server Type1DPS = Data processing server, GW = gateway server |
---|---|---|---|
1099 | Naming service used by the application server (JNDI). | public |
DPS, GW |
2317 | HTTP Channel for Web Data Entry (WDE) process | local | GW |
4447 |
Application server remote interface |
local | DPS, GW |
5433 | Connection between the data processing server and the embedded PostgreSQL database server | public | DPS |
5445 | JMS client and JMS bus connections | public | DPS, GW |
8009 | AJP channel for the application server | local | DPS, GW |
8010 | AJP Channel for Web Data Entry (WDE) process | public | GW |
8080 | HTTP Channel for the application server process | local | DPS, GW |
8105 | Web Data Entry (WDE) Shutdown Port | local | GW |
8443 | Secure Connection to RTSM URL | public | DPS, GW |
8444 | Secure Connection to RTSM with Client-Certificate Authentication | public | DPS, GW |
9990 | Application server HTTP management interface | local | DPS, GW |
9999 | Application server native management interface | local | DPS, GW |
11020 | RMI management channel for the OMi service (Nanny Manager) | local | DPS, GW |
11021 | HTTP channel (JMX Console) for the OMi Service (Nanny Manager) | local | DPS, GW |
21212 | HTTP Interface for RTSM | public | DPS, GW |
21215 | AJP Channel for RTSM | public | DPS, GW |
21302 | RMI communication from console web-app to admin web-app | local | DPS, GW |
21303 | RMI communication from console web-app to custom action script server running on the same host | local | DPS, GW |
21304 | RMI communication between opr-web webapp and opr-config-server webapp for content upload | local | DPS, GW |
29000 | HTTP channel for JMX Console | local | DPS, GW |
29604 | RMI management channel for the Web Data Entry (WDE) process | public | GW |
29612 | RMI management channel for the RTSM process | public | DPS, GW |
29616 | RMI port for schedulergw process | public | GW |
29622 | RMI management channel for the OPR backend process | public | DPS |
29623 | RMI management channel for the JMS bus process | public | DPS, GW |
29628 | RMI for script execution for OPR backend process | public | DPS, GW |
29630 | RMI port for online BLE processes | public | DPS |
29700 | RMI port for Marble Supervisor process | public | DPS |
29800 | HTTP port (JMX Console) for Marble Supervisor process | local | DPS |
29904 | HTTP channel (JMX Console) for the Web Data Entry (WDE) process | local | GW |
29912 | HTTP port (JMX Console) for RTSM | local | DPS, GW |
29916 | HTTP port (JMX Console) for schedulergw process | local | GW |
29922 | HTTP channel (JMX Console) for the OPR backend process | local | DPS |
29923 | HTTP port (JMX Console) for JMS bus process | local | DPS,GW |
29928 | HTTP port (JMX Console) for script execution for pipeline processing in OMi | local | DPS,GW |
29930 | HTTP port (JMX Console) for Business Impact process | local | DPS |
30020 | HTTP port (JMX Console) for marble loader processes | local | DPS |
32000-32999 | OMi service (Nanny Manager) uses the first available port in each range (Tanuki Service Mgmt) | local | DPS, GW |
49152-65535 | Dynamic ports are used for inter-component channels using Java RMI | local | DPS, GW |
OMi connects to external servers such as database, SMTP, NTP, or LDAP servers. By default, the following ports are used:
Default Port | External Server | OMi Server Type |
---|---|---|
25 | SMTP channel from the OMi servers to the SMTP mail server | DPS, GW |
123 | NTP channel from the OMi servers to the NTP server | DPS, GW |
389 | Connection between the gateway server and LDAP server for authentication | GW |
636 | Secure connection between the gateway server and LDAP server for authentication | GW |
1433 | Connection between the data processing server and the remote Microsoft SQL Server | DPS |
1434 | Connection between the data processing server and the remote Microsoft SQL Server Browser Server. This port is only used when a named instance is used. | DPS |
1521 | Connection between the data processing server and the remote Oracle database server | DPS |
5432 | Connection between the data processing server and the remote PostgreSQL database server | DPS |
If there is a firewall between OMi and the external server, you must configure the firewall to allow connections between OMi and the external server.
If the database has been configured to use a different port, disable OMi, run the configuration wizard and modify the port in the Database Settings page, and then enable OMi again. For details about the configuration wizard, see the
OMi by default listens at the following ports for incoming data:
Default Port | Description |
---|---|
80 |
HTTP channel to the gateway server (Apache web server). See also How to Manually Change Port 80 or 443. |
383 |
Port used by the communication broker to receive events, topology, and other data from OM, HPE Operations Agents, HPE OpsCx, and others. See also Configure communication broker ports. |
443 | HTTPS channel to the gateway server (Apache web server). |
When you change the default ports, update any data collector that were configured before you modified the port (for example, SiteScope). Modify the gateway server address in each data collector to reflect the new port as follows: <OMi gateway>:<new port>
. Alternatively, if there is a load balancer in the deployment, update the load balancer to forward communication to the new ports.
Tasks
Note The ports listed in Used Ports are the ports OMi uses. If you must change a port assignment, it is strongly recommended that you first consult with HPE Software Support.
Port 80 is used by the OMi web server. To modify this port, you must reconfigure other components on the OMi server and restart OMi.
-
Modify the virtual gateway server settings.
-
Open Infrastructure Settings:
Administration > Setup and Maintenance > Infrastructure Settings
Alternatively, click Infrastructure Settings.
Select Platform Administration from the Foundations drop-down list.
Locate the Platform Administration - Host Configuration table. If this table is not visible, set the Select Context option to All.
-
Modify the Default Virtual Gateway Server for Application Users URL to
https://<server name>:<new port>. -
Modify the Default Virtual Gateway Server for Data Collectors URL to
https://<server name>:<new port>.
-
-
Modify the direct gateway server settings
-
In the same table, modify the Direct Gateway Server for Application Users Server URL to include the new port.
-
Modify the Direct Gateway Server for Data Collectors URL to include the new port.
-
-
Modify the local virtual gateway server settings
-
In the same table, modify the Local Virtual Gateway Server for Application Users URL to include the new port.
-
Modify the Local Virtual Gateway Server for Data Collectors URL to include the new port.
-
-
Modify the Open OMi URL
-
Remotely connect to the OMi gateway server and select Start > All Programs > HPE Operations Manager i.
-
Right-click Open HPE Operations Manager i and select Properties.
-
In the Web Document tab, modify the URL field as follows: https://<gateway server>:<new port>/omi.
-
-
Modify the web server settings
Modify the web server settings. This procedure varies depending on web server type. They should all be performed on the OMi gateway server. The following example is for an Apache web server:
-
Open the file
<OMi_HOME_GW>/WebServer/conf/httpd.conf
in a text editor. -
Go to the line that begins with
Listen
, and modify the port value as required. -
Go to the line that begins with
ServerName
and modify the port value as required.
-
-
Restart all OMi servers and update data collectors.
Restart all OMi servers and update any data collectors that were configured before you modified the port (for example, SiteScope). Modify the gateway server address in each data collector to reflect the new port as follows:
<OMi gateway>:<new port>
.
Port 5445 is the port used by the JMS client and JMS bus connections. To change the port, perform the following procedure on each OMi server:
-
Stop all OMi servers (gateway and data processing servers).
-
On the OMi primary date processing server, run the opr-support-utils tool to change the port:
Windows:
<OMi_HOME>\opr\support\opr-support-utils.bat ‑bus ‑setport <new_port>
Linux:
/opt/HP/BSM/opr/support/opr-support-utils.sh ‑bus ‑setport <new_port>
Tip Use the
‑bus ‑getport
option to query the current port. -
Start all OMi servers (gateway and data processing servers).
This port number is the port through which the Tomcat AJP13 connector enables communication between components on the OMi server. Perform the following on each OMi server whose Tomcat AJP13 connector port you want to redirect, and restart OMi.
-
Change the application server port definition:
-
In a text editor, open the following file:
<OMi_HOME>/application-server/standalone/configuration/standalone.xml
-
Search for the following line in the file:
<socket-binding name="ajp" interface="management" port="8009"/>
-
Change the port number.
-
-
Configure the web server to use the new port:
-
In a text editor, open the following file:
<OMi_HOME>/WebServer/conf/workers.properties
-
Search for the following line:
worker.localAjp.port=8009
-
Change the port number.
-
-
Windows only. Configure the reserved ports in the registry.
Under the key
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters]
, replace the existing port with the new port.Restart the operating system.
-
Restart all OMi servers.
We welcome your comments!
To open the configured email client on this computer, open an email window.
Otherwise, copy the information below to a web mail client, and send this email to ovdoc-asm@hpe.com.
Help Topic ID:
Product:
Topic Title:
Feedback: