Tivoli Application Dependency Discovery Manager WebSphere Sensor seed file discovery detail
- WebSphereServer
- WebSphereCell
- WebSphereNode
- WebSphereNamedEndPoint
- ConfigFile
- LogicalContent
- AppDescriptor
<!-- TADDM WebSphere Sensor Seed File -->
<!-- Seed File Name : TVS5999_tvs5999.tivlab.raleigh.ibm.com_2809.xml -->
<!-- IDML File Name : ZOSDISC320WAS.BBOS001@tvs5999.tivlab.raleigh.ibm.com.2023-02-22T06.0
<!-- IDML Dataset : DLA320.V32BLD.FILL.TVS5999.IDML(BBOS001) -->
<!-- Seed Created : 2023-02-21 23:10:02 ROOT -->
<!-- IDML Created : 2023-02-22T06:02:25Z -->
<!-- WAS Server Type : Server -->
<!-- WAS Server Name : TVS5999:serverl -->
<!-- WAS Cell Name : TVS5999 -->
<!-- WAS Node Name : TVS5999 -->
<!-- Fqdn : tvs5999.tivlab.raleigh.ibm.com -->
<!-- z/OS : 5029-EVPMPLEX -->
<IDML_WAS_SEED>
<WAS_ROOT_DIR>/u/WebSphere/V9R0/AppServer</WAS_ROOT_DIR>
<WAS_VERSION>9.0.5.9</WAS_VERSION>
<SOAP_CONNECTOR_PORT>8880</SOAP_CONNECTOR_PORT>
<RMI_CONNECTOR_PORT>2809</RMI_CONNECTOR_PORT>
<JMX_LISTEN_IP_ADDRESS>9.42.62.29</JMX_LISTEN_IP_ADDRESS>
<HOST_MAPPINGS>
<HOST MAPPING>
<HOST_NAME>tvs5999.tivlab.raleigh.ibm.com</HOST_NAME>
<PRIMARY_IP_ADDRESS>9.42.62.29</PRIMARY_IP_ADDRESS>
<IP_ADDRESS>9.42.62.29</IP_ADDRESS>
</HOST_MAPPING>
</HOST MAPPINGS>
</IDML_WAS_SEED>
If you have WebSphere Deployment Managers on z/OS, you only need to run the WebSphere Application Server seed utility on those z/OS LPARs. The Tivoli Application Dependency Discovery Manager WebSphere Sensor discovers and populates Tivoli Application Dependency Discovery Manager with WebSphere lower-level resources for all WebSphere cells controlled by the WebSphere Deployment Managers on z/OS.
If you have not installed WebSphere Deployment Managers on z/OS, you must run the WebSphere Application Server seed utility on any z/OS LPARs where you want to discovery WebSphere. After this seed file is created and installed on the Tivoli Application Dependency Discovery Manager server, on the next discovery, the WebSphere IdmlSeedSensor looks for z/OS WebSphere seed files on the Tivoli Application Dependency Discovery Manager Server. If a seed file exists, it parses that seed file and creates a discovery seed file that is used to kick off the WebSphere sensor. The WebSphere sensor then does a deeper discovery of WebSphere on the z/OS system. It uses a TCP/IP SOAP Server connection from Tivoli Application Dependency Discovery Manager to the z/OS LPAR.
You can obtain the WebSphere Application Server seed utility for the z/OS DLA from the IBM® Service Management (previously called OPAL) website. However, if you have installed z/OS DLA, you already have a copy of WebSphere Application Server seed utility installed on z/OS. You should use that z/OS utility.
Downloading the WebSphere Application Server seed utility for the z/OS DLA from IBM Service Management OPAL website provides only the software you have already installed with z/OS DLA.
- If your needs are met by the seven higher-level WebSphere resource classes discovered by z/OS DLA, go no further.
- If you have all the information to create a WebSphere sensor XML seed file at your Tivoli Application Dependency Discovery Manager server, you don't need to run the WebSphere Application Server seed utility – it is only provided for your convenience.
- The z/OS DLA discovery is not changed by running the WebSphere Application Server seed utility.
Procedure
For more information about how to use the WebSphere seed sensor for z/OS to discover WebSphere resources on a z/OS system, see Using the WebSphere seed sensor for z/OS.