Secure JDBC Parameters in Resource Configuration Files
Secure JDBC Parameters in Resource Configuration Files
Resource configuration information for some database management resource types includes secure JDBC parameters. You can include or exclude secure JDBC parameters in the resource configuration file.
Resource configuration information for the following database management resource types can include secure JDBC parameters:
IBM DB2 for LUW
IBM Informix
Microsoft SQL Server
Netezza
Oracle
Sybase ASE
Teradata
For example, if secure communication is enabled for a Microsoft SQL Server metadata source, you might specify the truststore and keystore passwords as secure JDBC parameters.
When you export a resource configuration, you can include or exclude resource passwords and secure JDBC parameters in the resource configuration file. During export, Metadata Manager prompts you to include the resource password in the resource configuration file.
You have the following choices:
Include the password.
If you include the resource password and the resource uses secure JDBC parameters, Metadata Manager includes the secure JDBC parameters in the resource configuration file. In the resource configuration file, the advancedJDBCParameters parameter specifies the secure JDBC parameters. The parameters appear as an encrypted string.
Exclude the password.
If you exclude the resource password, Metadata Manager also excludes the secure JDBC parameters from the resource configuration file.
When you import a resource configuration, you can specify secure JDBC parameters. The Metadata Manager Service determines the values for secure JDBC parameters as follows:
If the resource configuration file includes secure JDBC parameters, the Metadata Manager Service creates the resource with the parameter values from the resource configuration file. If you specify secure JDBC parameters during import, the Metadata Manager Service ignores them.
If the resource configuration file does not include secure JDBC parameters and the resource requires them, you must specify the parameters during import. If you do not specify the secure JDBC parameters, the Metadata Manager Service might not be able to create the resource.
If the resource configuration file does not include secure JDBC parameters and the resource type can include them, you can specify secure JDBC parameters during import. The Metadata Manager Service creates the resource with the parameters that you specify.
If the resource type does not use JDBC parameters and you specify secure JDBC parameters during import, the Metadata Manager Service ignores the parameters that you specify.