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 |
|
Mappings Used in the Topology Integration
Ops Connector for OEM comes preconfigured with the basic set of topology mappings that you can extend and tailor to your needs. The preconfigured mappings include only basic subsets of topology entity types defined in OEM. These subsets can therefore be used with all OEM versions that Ops Connector for OEM supports.
The topology mappings are defined in the following XML files:
-
package.xml
: You may not edit this file. -
contextmapping.xml
: Edit this file to adjust the set of the OEM target types that are mapped. -
typemapping.xml
: Edit this file to reconfigure the mapping of target types to CI types. -
attributemapping.xml
: Edit this file to reconfigure the target attribute mapping. -
relationmapping.xml
: Edit this file to reconfigure the mapping of relations between targets.
The files are located on the OMi Data Processing Server host in the following directory:
Windows: %topaz_home%\conf\opr\topology-sync\sync-packages\HPBsmIntOEM
Linux: /opt/HP/BSM/conf/topology/xml/sync-packages/HPBsmIntOEM
Default Target Type Mapping
The following table lists the preconfigured OEM target type mapping.
The values outside parentheses represent display names in the user interface of a systems management application. The values inside parentheses represent internal keywords in the corresponding database.
OEM Type | OMi Type |
---|---|
OEM All Targets (group ) |
CiCollection (ci_collection ) |
IP Address (IPAdress ) |
IpAddress (ip_address ) |
Host (Linux) (host ) * |
Unix (unix ) |
Host (Windows) (host )* |
Windows (nt ) |
Host (host ) |
Computer (host_node ) |
Listener (oracle_listener ) |
Oracle TNS Listener (oracle_listener ) |
Database Instance (oracle_database )
|
Oracle (oracle ) |
Pluggable Database (oracle_pdb ) |
Oracle (oracle ) |
Oracle HTTP Server (oracle_apache ) |
Apache (apache ) |
Oracle WebLogic Server ( weblogic_j2eeserver ) |
Weblogic AS (weblogicas ) |
Microsoft IIS (microsoft_iis ) |
IIS Web Server (iis ) |
Microsoft SQL Server ( microsoft_sqlserver_database ) |
SQL Server (sqlserver ) |
Application Deployment (j2ee_application ) |
J2EE Application (j2eeapplication ) |
* Linux
and Windows
are attributes of the same target type (host
)
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: