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 |
|
- Data Flow Probe Setup
- Data Flow Probes and Clusters
- UCMDB Integration Service
- Cluster Range Distribution Policy
- Limiting IP Movement in a Cluster
- Job Execution Policies
- Data Flow Probe Upgrade Overview
- Effects of Range Type on Discovery Workflows
- Install and Run Data Flow Probe and Probe Database on Linux with Non-Root User Account
- Using HTTPS Port 8453 as Default for Data Flow Probe
- How to Install a Second Data Flow Probe on a Windows Machine
- How to Deploy Hotfixes and Track Hotfixes Applied on Data Flow Probe
- How to Set Master Key for Password Encryption on Data Flow Probe
- How to Add Data Flow Probes to UCMDB
- How to Add Probe Clusters to UCMDB
- How to Start a Data Flow Probe
- How to Stop a Data Flow Probe
- How to Change the Data Flow Probe Default Domain
- How to Change the Data Flow Probe Port
- How to Move Resources From One Domain to Another Domain
- How to Change the UCMDB Integration Service Default Domain
- How to Check the UCMDB Integration Service Status
- How to Limit IP Movement in a Cluster
- How to Update the Data Flow Probe's IP Address
- How to Update the Data Flow Probe Memory Size
- How to Define Owner Tenants on Data Flow Probes
- How to Configure the Number of Connections to Other Machines
- How to Configure Periodic Data Flow Task Updates
- How to Prevent Probes from Sending Touch Information Simultaneously
- How to Encrypt/Decrypt IP Ranges Information on the Probes
- How to Configure the Data Flow Probe to Automatically Delete CIs
- How to Delete Unsent Probe Results
- How to Clear Data Flow Probe Data
- How to Clear UCMDB Integration Service Data
- How to Deploy a Data Flow Probe CUP
- How to Deploy a Data Flow Probe CUP Manually
- How to Align the Data Flow Probe CUP with the UCMDB Server CUP
- How to Uninstall Probe CUPs Manually
- How to Set Maximum Objects for Insert Results
- Data Flow Probe Process Ports
- DataFlowProbe.properties File
- DataFlowProbe.properties Parameters
- DataFlowProbeOverride.properties File
- Data Flow Probe Database Scripts
- Data Flow Probe Log Files
- Data Flow Probe Setup User Interface
- Troubleshooting and Limitations
Data Flow Probe Process Ports
The following ports are used by the Data Flow Probe process on the Data Flow Probe machine:
Port | Description |
---|---|
1977 | Data Flow Probe’s web application port. Used for JMX console and other web services. |
1978 | If the Data Flow Probe is installed in separate mode (Probe Manager and Probe Gateway are running in separate processes), this port is used by the Probe Manager process for the web application port (Manager’s JMX console). |
1979 | Web application port for the second Data Flow Probe (if installed). Used for JMX console and other web services. |
8453 |
Data Flow Probe’s secured web application port. Same as 1977, and is used for the JMX console and other web services if the Jetty HTTPS mode is enabled. Also used to redirect Credential Manager requests when the Data Flow Probe is installed in separate mode. |
8454 |
Data Flow Probe’s secured web application port. If the Data Flow Probe is installed in separate mode and Jetty HTTPS mode is enabled, this port is used by the Probe Manager process for the web application port (Manager’s JMX console). |
8455 |
Secured web application port for the second Data Flow Probe (if installed). It is used to share the Incoming and Original directories via HTTPs. |
1741 | Port opened by the Probe Gateway to enable RMI (Remote Method Invocation) between Gateway and Managers. |
1742 | Port opened by the Probe Manager to enable RMI (Remote Method Invocation) between Gateway and Managers. |
80 | Opened by a CallHome service for Universal Discovery Agents. |
81 | Opened by a CallHome service for Universal Discovery Agents. This port is used by the second Data Flow Probe (if installed). |
5432 | Port used by the PostgreSQL database. |
5433 | Port used by the PostgreSQL database for the second Data Flow Probe (if installed). |
1777 | Port used by the Tanuki wrapper. |
2055 | Port opened when the Collect Network Data by Netflow job has been activated. Used for connecting netflow data reported by nProbe software. |
34545 |
Port used by the XML Enricher. Note The port 34545 only listens on localhost if Data Flow Probe is newly installed. However, if Data Flow Probe is upgraded to the latest version, you need to add the following setting to the wrapperEnricher.conf file manually. # Make rmi listen on localhost only wrapper.java.additional.<the number>=-Djava.rmi.server.hostname=localhost |
34645 | Port used by the XML Enricher for the second Data Flow Probe (if installed). |
The following ports are used by the Data Flow Probe process on remote machines:
Port | Description |
---|---|
5672 | Used for AMQP-based discovery. |
5989 | Used for CIM-based discovery. |
8080 | Data Flow Probe uses this port to communicate with the UCMDB server (if the communication is configured to HTTP). |
8443 | Data Flow Probe uses this port to communicate with the UCMDB server (if the communication is configured to HTTPS). |
22 | Used for SSH-based discovery. |
23 | Used for Telnet-based discovery. |
80/81 | Used for HTTP, NetApp SANscreen/OnCommand, NNM, PowerShell, UDDI, VMware VIM discoveries. If the second Data Flow Probe is installed, port 81 will be used. |
135, 137, 138, 139, 445 + DCOM ports |
Used for WMI and NTCMD discoveries. Note Note: It is recommended that you use port 445. This is because, by default, Windows 2000 and later versions use SMB over TCP/IP via port 445 rather than over NetBIOS whenever possible. If port 445 is disabled, it will fall back to NetBIOS using port 137, 138, or 139. |
161 | Used for SNMP discovery. |
389 | Used for LDAP discoveries. |
1521, 1433, 6789, 3306, 2048, 5432 | Used for SQL (Database)-based discoveries. |
2738, 7738 | Used for Universal Discovery Agent-based discoveries. |
443 | Used for UCS, UDDI, VMWare VIM, NetApp, PowerShell discoveries. |
280 | Used for HPE SIM discovery. |
1099 | Used for Network Automation Java, JBoss discoveries. |
5985, 5986 |
Used for PowerCmd, PowerShell discoveries. Note Note: These ports depend on the Microsoft Windows operating system configuration. |
3200, 3300-3303, 33xx, where xx is the SAP server instance number | Used for SAP discovery. |
50004, 50104, 50204, 50304, 50404, 5xx04 where xx is the SAP J2EE server instance number | Used for SAP JMX discovery. |
2320 | Used for Siebel Gateway discovery. |
7001, 7002 | Used for WebLogic discovery. |
8880 | Used for WebSphere discovery. |
50001 | Used for HPE SIM discovery (secure communication). |
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 cms-doc@microfocus.com.
Help Topic ID:
Product:
Topic Title:
Feedback: