Structure of a Configuration Signature File

The configuration signature file defines rules to find provider’s connection string in consumer’s configurations. You can find the configuration signature file at UCMDB UI > Data Flow Management > Adapter Management > Packages > ASM_Enhanced > Configuration Files > ConfigurationFileSignature.xml.

The following example shows the content and structure of the configuration signature file:

<ConfigurationFileSignature>
    <Application name="application1">
        <PropertyFile name="properties file name">
            …
        </PropertyFile>
        <Output>
            <SCP type="ucmdb" host="${hostname}" port="${port}"/>
		…
        </Output>
    </Application>
    <Application cit="application2">
        <CommandLine>
		…
        </CommandLine>
        <Output>
            <SCP type="${db.type}" host="${db.host}" context="${db.name}"/>
		…
        </Output>
    </Application>
    …
</ConfigurationFileSignature>

Rules can be grouped by running software name, product name, or CI Type. Each kind of running software is defined as an <Application> element, and each <Application> element may contain one or more configuration search methods and one <Output> element. The <Output> element defines how to generate service end points from connection strings.

The ConfigurationFileSignature.xsd file can help you understand the syntax of the configuration signature file. This file locates in the same folder as the ConfigurationFileSignature.xml file.

The dependency job can search connection strings from command line or from the configuration documents in the file system. For more information, see the following sections:

• Search connection strings from command line
• Search connection strings from configuration documents