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)`

Universal CMDB

Discovery > Discovery Modules > Middleware > Java EE Application Servers > WebSphere Discovery > How to Discover WebSphere Topology by Shell

How to Discover WebSphere Topology by Shell

This task describes how to discover a complete WebSphere topology using Shell protocols. The WebSphere discovery process discovers Web services that are deployed on an IBM WebSphere server. The discovered Web services are represented by the webservice CIT in the CMDB.

DFM first finds application servers based on the Shell protocol or endpoints (TCP Ports) and then discovers the WebSphere J2EE environment and components by Shell.

This task includes the following steps:

Prerequisite - Set up protocol credentials
This discovery uses the Shell protocol. You must define one of the following protocols:
- SSH Protocol
- Telnet Protocol
- NTCMD Protocol
For credential information, see Supported Protocols.
Prerequisite - Set up key stores
The following procedure is relevant if you are running a client machine that includes two key stores, each one needed for identification on a specific WebSphere server. If the client attempts to connect to one of the WebSphere servers with the wrong key store, the attempt fails. If the client then uses the second, correct key store to connect to the WebSphere server, that attempt also fails.
- Solution 1: Set up one key store on the client for all WebSphere servers.
- Solution 2: Set up one key store per IP address range for all WebSphere servers that use the same user name and password. For a server that uses a different user name and password, set up a key store in another IP range.
Run the discovery
Run the following jobs in the following order:

For details on running jobs, refer to "Module/Job-Based Discovery" in the HPE Universal CMDB Data Flow Management Guide.
1. Run the Range IPs by ICMP job to discover the target IPs.
2. Run the Host Connection by Shell job to discovers the target host and Shell connectivity to the host.
3. Run one of the following jobs:
  - Run the Host Applications by Shell job to discover applications of the target host, including running processes.
  - Run the JEE TCP Ports job to discover service endpoint information. For job details, see JEE TCP Ports Job.
4. Run the JEE WebSphere by Shell job. For job details, see JEE WebSphere by Shell Job.