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 |
|
- VMware Infrastructure Discovery
- Supported Versions
- SSL Support
- Topology
- How to Discover VMware VIM Topology
- How to Run the Manual VMware VIM Connection Job
- How to Discover VMware ESX Server Topology over CIM
- Manual VMware VIM Connection Job
- VMware ESX Connection by CIM Job
- VMware ESX Connection by VIM Job
- VMware ESX Topology by CIM Job
- VMware ESX Topology by VIM Job
- VMware vCenter Connection by VIM Job
- VMware vCenter Topology by VIM Job
VMware vCenter Connection by VIM Job
This job discovers vCenter or VirtualCenter Servers.
This section includes:
-
Trigger CI: Node
-
Trigger query:
This job uses the VMware_VirtualCenter_Connection_by_VIM adapter.
-
Triggered CI Data
Name Description connection_url The connection URL of the vCenter server. credentialsId
The credentials ID of the WMI agent CI.
ip_addresses
List of all IPs connected to Host.
rs_id The CMDB ID of the vCenter server, reported as RunningSoftware. vc_id The CMDB ID of the vCenter server. -
Used Scripts
- memory.py
- shared_resources_util.py
- _vmware_vim_base.py
- _vmware_vim_20.py
- host_discoverer.py
- _vmware_vim_25.py
- _vmware_vim_40.py
- _vmware_vim_41.py
- vmware_vim.py
- vmware_virtualcenter_connection_by_vim.py
-
Adapter Parameters
Parameter Description remoteJVMArgs The JVM parameters that should be passed to the remote process. remoteJVMClasspath The class path used by the external Java process.
runInSeparateProcess When true, this enables the execution of the job in the external java virtual machine.
Default: true.
Note Do not change this parameter from the default.
-
Composition
-
Containment
-
IpAddress
-
Node
-
VMware VirtualCenter
-
Problem. The following error message is displayed when an operation cannot be performed due to lack of permissions:
User does not have required '<permission>' permission
Solution. Check that the user has permissions for all entities being discovered: In the VMware Infrastructure Client, access the Permissions tab of each entity (host, cluster, VM, and so on). Verify that the user has been assigned at least a Read-Only role.
Note You can view necessary permissions in the Discovery Job Details pane (Universal Discovery > Discovery Modules/Jobs tab > select <job> > Details tab).
-
Problem. The following error message is displayed when credentials are not correct:
Invalid user name or password
Problem. The VMware vCenter Connection by VIM job fails to connect to remote process and the job cannot run in FIPS mode or in non-FIPS mode.
Solution.
-
If you re-installed the probe, then no further manual modification is required.
-
If you upgraded the probe from an older version (for example, from 10.20 to 10.21), then you need to add the following values into the basic_discovery_minimal_classpath setting in the DataFlowProbe.properties file:
../lib/cryptojce.jar;../lib/cryptojcommon.jar;../lib/jcmFIPS.jar;