Configuring the JDBC data source by using an nzjdbc.ini file (Windows)

A data source contains the sets of data that the JDBC driver accesses, along with all the environments that are associated with the data.

You can configure a JDBC data source by specifying data source properties when creating a connection string in a JDBC application. For information about how to specify properties when creating a connection string, see JDBC connection strings. Alternatively, you can save data source configuration information, including a data source name (DSN), on the local server by using the nzjdbc.ini file. You can then specify that DSN for the dsn property as part of the connection string, which enables the connection string to access all the associated data source configuration properties that are in the nzjdbc.ini file.

Before you begin

Install the JDBC driver. See Installing the JDBC driver (Windows).

Procedure

  1. Start the GUI by issuing the following command: 
    java -jar <driver_jarfile>
  2. When the list of data sources is displayed, add a data source by clicking Add.
  3. In the Data Source Configuration window, click the Connection Options tab and provide information as appropriate:
    Data source1
    Specifies the name of the data source.
    Host1
    Specifies the name of the host to connect to.
    Port1
    Specifies the port number.
    Database1
    Specifies the database name.
    Description
    Specifies the description for the data source.
    User
    Specifies the user name to connect to the database.
    Password
    Specifies the password for authentication.
    Schema
    Specifies the name of the schema within the specified database on the Netezza Performance Server system. This field is used for Netezza Performance Server systems that support multiple schemas within a database. If you do not specify a schema, you connect to the default schema of the database.
    Important: Calling the setSchema method to specify a new schema causes all future queries, including those using previously created or prepared Statement objects, to use the new schema. This behavior is different from that documented in the Oracle JDBC specification.
    Test Connection
    Tests the connection with the set parameters.

    1 This field is required.

  4. Click the Advanced Options tab and provide information as appropriate:
    Batch size
    Specifies the number of rows to be fetched in a cycle. The default is 256.
    Login timeout
    Specifies the maximum wait time to make a connection. The default is infinite.
    Read only
    Specifies whether the connection is read only. The default is false.
    Autocommit
    Specifies whether autocommit applies to the connection. The default is true.
    Ignore update count
    Allows the JDBC driver to export more than two billion rows (the maximum int value). The default is off.
    Log level
    Specifies the log level for the connection. The default is OFF.
    Logger type
    Specifies the type to be used for logging. The default is TEXT.
    Logger directory
    Specifies the log directory into which the log files are written.
    Database metadata
    When selected, specifies that you can get metadata information that is not restricted to the current catalog and schema. If you do not select this check box, your information is restricted to the current catalog and schema.
    Defaults
    Selects the defaults for the items in the Advanced Options tab.
  5. Click the SSL Options tab and provide information as appropriate:
    Preferred Unsecured
    Specifies that connections that do not use SSL are preferred but that a connection is not refused solely because it uses SSL encryption.
    Only Unsecured
    Specifies that only connections that do not use SSL to encrypt data are accepted. This security level can help increase performance but carries the risks that come with an unencrypted connection.
    Preferred Secured
    Specifies that connections that use SSL are preferred but that a connection is not refused solely because it does not use SSL encryption.
    Only Secured
    Specifies that only connections that use SSL to encrypt data are accepted. This security level increases security but reduces performance somewhat, because of the necessity of encrypting the data stream.
    Certificate file
    Specifies the name of the certificate authority (CA) file that is used to authenticate connections. If you use a CA for authentication, the name of the CA file must match the name that the security administrator defined for the database to which you are attempting to connect. For more information about security and authentication, see the IBM® Netezza® System Administrator’s Guide.
    Login module
    Specifies the entry module name of the set of Kerberos properties from the login.conf file. The JDBC driver uses the login module class to create authentication tickets.
    Kerberos SSO delegation
    Specifies that if you configure an IBM Cognos Business Intelligence application in Kerberos SSO mode, the JDBC driver uses the authentication ticket that the Cognos product provides. The value of the krbSSODelegation connection parameter overrides the setting of the Kerberos SSO Delegation check box.
  6. Click the Client Information Options tab and provide client information as appropriate:
    Application name
    Specifies the application name.
    Client host name
    Specifies the client host name.
    Client user
    Specifies the client user.
  7. After entering data source configuration options, test the connection by clicking Test Connection on the Connection Options tab.
  8. When the connection is established, click OK on the confirmation screen.
  9. On the Data Source Configuration window, click OK.