Use > Data Flow Management > Universal Discovery > Module/Job-based Discovery > How to Discover Running Software – Scenario

How to Discover Running Software – Scenario

This scenario explains how to set up the discovery of Oracle databases so that there is no need to enter a specific set of credentials to discover each database instance. Universal Discovery runs an extract command that retrieves the database name attribute.

In this scenario, we assume that the following syntax is used in the Oracle command lines:

c:\ora10\bin\oracle.exe UCMDB
  1. Prerequisites

    Display the Attribute Assignment Editor dialog box:

    1. Go to Data Flow Management > Universal Discovery.

    2. In the Discovery Modules/Jobs tab, in the Discovery Modules tree, select Host and Resources > Basic Applications.
    3. Select any one of the Host Application jobs, and in the Properties tab, select Global Configuration Files.

      Tip If you cannot see the Global Configuration Files pane, click the Up arrow [] below the Trigger Queries pane.

    4. Select applicationSignature.xml, and click Edit to open the Software Library dialog box. For details, see Software Library Dialog Box.

    5. Select the signature to be edited and click Edit .

    6. In the Software Identification Rule Editor dialog box that opens, next to Additional Attributes, click to open the Attributes Assignment Editor dialog box.

  2. Create a Command Line Rule

    The command line rule is text that identifies the process to be discovered, for example, oracle.exe c:\ora10\bin\oracle.exe UCMDB. You can substitute the text entry with a regular expression, so that discovery is more flexible. For example, you can set up a rule that discovers all Oracle databases, whatever their name.

    Subsequently, Universal Discovery uses the information in the command lines discovered by the regular expression to populate a CI's name attribute with the database name.

    1. To create a Command Line rule that includes a regular expression, in the Attributes Assignment Editor dialog box, click the Add button in the Parsing Rules pane. For details, see Attributes Assignment Editor Dialog Box.

    2. In the Parse Rule Editor dialog box, build the rule:

      • Enter a unique name in the Rule ID field: r1.

      • In the Process Attribute field, select Command Line.

      • In the Regular Expression field, enter the following regular expression:

        .+\s+(\w+)$

        This expression searches for any character (.), followed by a space or spaces (+\s+), followed by a word or words ((\w+)) that appear at the end of the line ($). You can use the following characters: a-z, A-Z, or 0-9. The following command line fulfills this expression:

        c:\ora10\bin\oracle.exe UCMDB

  3. Define the value of an attribute

    In this step, you define which attribute is used by Universal Discovery to discover the Oracle databases, and the value it should take.

    1. In the Attributes Assignment Editor dialog box, in the Attribute Assignments pane, click Add to select the attribute.

    2. In the Attribute Editor dialog box that opens:

      • Choose the attribute that holds the database name, from the list of Oracle CIT attributes—in this case The Database instance name.

      • Enter a value, using the following syntax: ${<rule ID name>(<group number>)}, in this case, ${r1(1)}.

        This dialog box is configured as follows: Universal Discovery enters the value of the first group ((\w+)$) in the command line regular expression (${r1(1)}) in the name attribute of the Oracle database CI.

        That is, during discovery, Universal Discovery searches through the process files for command lines with a word or words at the end of the line. For example, the following command line matches this regular expression:

        c:\ora10\bin\oracle.exe UCMDB

  4. Activate the Job

    For details, see How to Manually Activate Modules/Jobs/CIs and Discovery Modules/Jobs – Discovery Modules Pane.

Related Topics Link IconRelated Information