Pre-requisite
Discovery Source Prioritization over WSUS
Note: This functionality is available from JetPatch version 4.1.2.71+
In case different discovery sources reveal the same set of endpoints that are discovered by WSUS and you would like to keep the meta-data that comes from the discovery source (override the WSUS data when the merge between the different discovery sources happen) , please add the following property to the intigua.properties -
1. SSH to JetPatch application Server
2. Edit the intigua.properties file (vi /usr/share/tomcat/default/conf/intigua.properties) and add the priority you would like. This is an example of Activy Directory prioritizatized over WSUS
#1 Default value VSPHERE,AMAZON_EC2,ARM,ASM,WSUS,AD
#2 First elements has higher priority
#3 Not listed DS types has higher priorities then listed in the list
#4 To prefer ActiveDirectory DS over WSUS while others will have higher priority set-up the following:
discovery-source.priority-list=AD,WSUS
3. Save file and exit
4. Restart tomcat (service tomcat restart)
Change Discovery Source Timeouts
- SSH to the JetPatch application Server
- Edit /usr/share/tomcat/default/conf/intigua.properties
- Add and configure the relevant discovery sources to the properties file
// Amazon
discovery-source.AWS.success.sleep-time.min (default 10)
discovery-source.AWS.error.sleep-time.min (default 20)
// Active directory
discovery-source.AD.success.sleep-time.min (default 10)
discovery-source.AD.error.sleep-time.min (default 20)
// VCenter
discovery-source.VC.success.sleep-time.ms (default 500)
discovery-source.VC.error.sleep-time.min (default 5)
// Azure ASM
discovery-source.ASM.success.sleep-time.min (default 10)
discovery-source.ASM.error.sleep-time.min (default 20)
Comments
0 comments
Please sign in to leave a comment.