Skip to main content

RDBMS(Add Custom Connections for Detection)

This section explains the steps to add a custom data source. The custom data source name and its details will appear in the Add New Connection screen. You can create a detection task for the same.

*Note: User must have an insight to the database and its logical structure (whose support needs to be added) i.e., 2-tier or 3-tier hierarchy.

Perform the below steps to add a support of new target database:

  1. To add the detection support for any database, download the CDATA JDBC driver or any other JDBC driver using the following url: https://www.CDATA.com/jdbc/download/ or check the vendor's website.

  2. Copy the JDBC jar files at the following location ‘…\Agents\DgDiscoverAgent\CustomFiles’. Add the details of the data source in the GenericDetection.xml file.

    These tags are mandatory in the xml file for any database whose support needs to be added for detection. The values can be changed as per the database. All the details must be added in the <data-source> tag and version number must be added in the <version> tag.

    For e.g., The details of the Custom_Postgres has been added in the GenericDetection.xml file as follows:

    CODE
    <data-sources>
    	<version>16</version>
           <data-source>
    		<data-source-name> Postgres </data-source-name>	
                 <jdbc-source-template> jdbc:postgresql:User=getUserName; 
                  Password=getPassword;Database=getDatabase;      
    	 	 Server=getHostNameOrIPAddress;Port=getPortNumber; 
                 </jdbc-source-template>
                 <jdbc-driver-classname> cdata.jdbc.postgresql.PostgreSQLDriver
    		</jdbc-driver-classname>
    <module>
    <value>DBMS</value>
    </module>
    <schema-hierarchy>
     <schema-level-object-hierarchy>true</schema-level-object-hierarchy>
    		 <append-schema-table-name>false</append-schema-table-name>
                 </schema-hierarchy>			
                <gui>
    		<fields>
                           <field-label>Hostname</field-label>
    			    <field-id>hostNameOrIPAddress</field-id>
    			    <field-default-value></field-default-value>
    			    <mandatory>true</mandatory>
                </fields>
    			<fields>
    			    <field-label>Port Number</field-label>
    			    <field-id>portNumber</field-id>
    			    <field-default-value></field-default-value>
    			    <mandatory>true</mandatory>
                </fields>
    			<fields>
    			    <field-label>Username</field-label>
    			    <field-id>userName</field-id>
    			    <field-default-value></field-default-value>		
    			    <mandatory>true</mandatory>
                </fields>
    			<fields>
    			    <field-label>Password</field-label>
    			    <field-id>password</field-id>
    			    <field-default-value></field-default-value>
    			    <mandatory>true</mandatory>
                </fields>
                        <fields>
    			    <field-label>Database Name</field-label>
    			    <field-id>database</field-id>
    			    <field-default-value></field-default-value>	
    			    <mandatory>true</mandatory>
                </fields>
    
    			<fields>
    			    <field-label>IP Address</field-label>
    			    <field-id>IPAddress</field-id>
    			    <field-default-value></field-default-value>	 
    			    <mandatory>false</mandatory>
                </fields>
             
             </gui>
    	</data-source>
    </data-sources >
    


    To know more about Tags, refer section Appendix J: Tags for Adding New Target Database.

  3. Restart the IDP. The newly added database should be visible on the Add New Connection screen.

    For e.g., in the below screenshot, the custom data source for Postgres and Oracle has been added in the Add New Connection screen.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.