Configuring for asynchronous discovery

To run an asynchronous discovery, you must first configure the discovery.

1. To generate a discovery script package, enter one of the following commands from the $COLLATION_HOME/bin directory:
   • Regular method

     makeASDScriptPackage OUTPUT_DIR UNAME [IPADDRESS] [PACKING_METHOD]

     OUTPUT_DIR

     The directory path for the script package.

     UNAME

     The operating system of the target system, on which the script is to be run. The valid values are AIX, Linux, SunOS, FreeBSD, Windows, or NONSTOP_KERNEL.

     IPADDRESS (optional)

     The IP address of the target system on which the script is to be run.

     The scripts that are used for asynchronous discovery use information from TADDM server properties that are defined in the collation.properties file, and some of these properties might be scoped.

     scoped property

     A property to which you can append either an IP address or the name of a scope set. The IP address or the scope set name makes the property dependent on the host that is being discovered. You can use only scope set names that do not contain spaces, apostrophes ('), periods (.), and forward slashes (/).

     If you have customized any of the TADDM server properties so that they are scoped, you should include the IPADDRESS option in the makeASDScriptPackage command.

     PACKING_METHOD (optional)

     The method to use to package the files. The valid values are tar or zip.

     If no method is specified, the method is determined by the operating system. For example, for operating systems such as Linux®, the tar method is used.

     By default, the system path is searched for the archive utility. If necessary, add the com.ibm.cdb.tarpath property to the collation.properties file, and specify an alternative path for the archive utility.

     On Solaris operating systems, because of a limitation in the length of file names, you must use the gtar archive utility, and you must specify the path to the utility.

     The following example shows how to specify the path of the tar command on the TADDM server for the AIX® operating system:

     com.ibm.cdb.tarpath=tar

     The following examples show how to specify the path of the tar command on the target system, depending on the operating system:

     For AIX

     com.ibm.cdb.targettarpath.AIX=tar

     For Solaris

     com.ibm.cdb.targettarpath.SunOS=/usr/sfw/bin/gtar

     For example, to generate a discovery script package for the AIX operating system, enter the following command:

     ./makeASDScriptPackage /tmp AIX

     This command creates the following AIX script package in the tmp directory: /tmp/taddm_AIX.tar.
   • Extended method

     makeASDScriptPackage --outputDir OUTPUT_DIR --uname UNAME [--ipAddress IP_ADDRESS] [--packingMethod PACKING_METHOD] [--sensors SENSOR]

     --outputDir OUTPUT_DIR

     See the description of the OUTPUT_DIR parameter of the regular method.

     --uname UNAME

     See the description of the UNAME parameter of the regular method.

     [--ipAddress IP_ADDRESS] (optional)

     See the description of the IPADDRESS parameter of the regular method.

     [--packingMethod PACKING_METHOD] (optional)

     See the description of the PACKING_METHOD parameter of the regular method.

     [--sensors SENSOR] (optional)

     The name of the sensor that you want to include in your package. The following table contains the sensor names that must be used in this command.

     Table 1. Sensor names used in the makeASDScriptPackage command.

     Sensor	Name used in the command
     Apache sensor	apacheserver
     Citrix XenServer sensor	xenserver
     FreeBSD computer system sensor	computersystem
     Generic server sensor	genericserver
     HP NonStop computer system sensor	computersystem
     IBM AIX computer system sensor	computersystem
     IBM DB2 sensor	db2
     IBM Lotus Domino server sensor	dominoserverinitial
     IBM Tivoli Utilization sensor	utilization
     IBM WebSphere MQ Server sensor	mqserver
     IBM WebSphere sensor	webspherescript
     JBoss Application Server 7 sensor	jboss7
     Kernel-based virtual machine sensor	kvm
     Linux computer system sensor	computersystem
     Microsoft Exchange sensor	exchange
     Microsoft IIS Web server sensor	iisserver
     Oracle sensor	oracle
     Solaris computer system sensor	computersystem
     WebLogic SSH sensor	weblogiclaunchersensor
     Windows computer system sensor	computersystem

     The Asynchronous discovery sensor is added to every package by default. All operating system sensors have computersystem name. They are differentiated on the basis of the --uname parameter. For example, if you specify the following parameters:

     [...] --uname Linux --sensors computersystem

     Linux computer system sensor is added to the package.

     For example, to generate a discovery script package for the AIX operating system, enter the following command:

     ./makeASDScriptPackage --outputDir /tmp --uname AIX --sensors computersystem

     This command creates the following AIX script package in the tmp directory: /tmp/taddm_AIX.tar.
2. Copy the script package from the OUTPUT_DIR to the target system, and extract the script package.
3. As a root user on UNIX systems, or administrator on Windows system, grant execute privileges to all script files. If the discovery script is run as a non-root, or non-administrator user, some sensor scripts might not complete a successful discovery, or the data that the sensor discovers might be limited.
4. Run the scriptsRunner.sh script for the UNIX targets, or the scriptsRunner.bat for the Windows target.
5. Move the resulting archive file (for example, /tmp/taddm${version}/asd/taddmasd-${hostname}-${execution timestamp}.tar) to the TADDM server in the location that is defined by the com.ibm.cdb.discover.asd.AsyncDiscoveryResultsDirectory property in the collation.properties file.
6. In the collation.properties file, set the value of the com.ibm.cdb.discover.asd.ProcessUnreachableIPs property to true.
7. Ensure that the asynchronous discovery sensors (ASDPingSensor and ASDSensor) are enabled in your discovery profile.
   By default, only the ASDSensor is enabled in the Level 2 and Level 3 discovery profiles.
8. Create a scope with the IP address of the target system.