-
Notifications
You must be signed in to change notification settings - Fork 2
Discovery Management Console
This tip can be used to help troubleshoot problems with running the Discovery Management Console (Java JNLP) or can potentially be used as a workaround if the console is not working for you. For instance, if you are seeing com.sun.deploy.net.FailedDownloadException while attempting to run the console.
-
Download the signed jars dist/lib/sign/*.jar from the TADDM server to your workstation.
-
Click the Start Discovery Management Console button on the TADDM splash screen and download the confignia.jnlp file to the same directory where you downloaded the sign jars.
-
Edit confignia.jnlp and change the codebase at the top (line 3) to codebase="file:/C:/cmdb/dist/lib/sign" using your disk location where you have downloaded the jar and jnlp files.
-
Open the Configure Java dialog (javaws -viewer), click on the Security tab. Click "Edit Site List...". Add location "file:/" to the list. You might see a warning, ignore it.
-
Still in Configure Java, on the General tab, click View... button. Delete any cached TADDM applications. Close Configure Java.
-
Double click your edited confignia.jnlp to launch. You might see some warnings and prompts. Click through all of those to launch the console.
Best Practices
Sensors
- Supported Target Systems
- Generic Server Sensor (lsof)
- Enhanced CPU Discovery
- Discovering Batch Jobs
- Duplicate Reducer
- VMware Instance Extention
- RHEL Cluster Discovery
- Collecting certs with nmap
- MQ Discovery
- Windows Discovery
- Oracle Discovery
- IIS Discovery
- Ping Sensor
- Collect Config Files Recursively
- Shallow Server Discovery
- Host Storage Sensor