Configuring the Accelerator Loader server for JDBC Gateway sources

Configure the Accelerator Loader server for use with the JDBC Gateway.

Before you begin

Configure access to the data source using the JDBC Gateway. See Creating a data source definition entry.

About this task

To use the JDBC Gateway to connect to your data source, the following changes must be made to the Accelerator Loader server:
  • The DEFINE DATABASE TYPE value must be set, as follows:

    "DEFINE DATABASE TYPE(JGATE)"
    JGATE
    DDF endpoint is the JDBC Gateway.
  • Optionally, the following utility and SEF procedure can be configured in support of TYPE(JGATE):
    HLVDRATH
    A utility that sets encrypted passwords in GLOBALU variables. You can also use this utility to list existing credential information.
    HLVEJGAG
    An ATH rule that switches credentials when connecting to a JGATE data source using DRDA. This rule uses AES encrypted passwords stored as GLOBALU system variables.

Procedure

  1. In the Accelerator Loader server configuration file, register the connection to the JDBC Gateway using a definition statement, such as the following example:
    "DEFINE DATABASE TYPE(JGATE)"         ,
                     "NAME(name)"                  ,
                     "LOCATION(location)"          ,
                     "DDFSTATUS(ENABLE)"           ,
                     "DOMAIN(your.domain.name)"    ,
                     "PORT(port)"                  ,
                     "IPADDR(1.1.1.1)"             ,
                     "CCSID(37)"                   
    
    The following table lists the parameters:
    Parameter Description Valid values
    AUTHTYPE Authentication type. This can be either DES for Diffie Hellman Encryption Standard or AES for Advanced Encryption Standard.

    When AUTHTYPE is not supplied, the default is DES. To force AES, the option must be added to the DEFINE DATABASE statement. Each server can be different in what is supported as to AES/DES.

    For this setting to have effect, you must specify a security mechanism (SECMEC) that requests encryption.

    DES
    Diffie Hellman Encryption Standard (default value)
    AES
    Advanced Encryption Standard.
    CCSID

    Specify the EBCDIC single-byte application CCSID (Coded Character Set Identifier) configured for this RDBMS subsystem on the RDBMS installation panel DSNTIPF, option 7. (Optional)

    Refer to the RDBMS vendor documentation for a list of valid CCSIDs.
    DDFSTATUS

    The DDF activation status can be altered online by using the ISPF 4-Db2 dialog panels. (Required)

    ENABLE
    Make this DDF definition active.
    DISABLE
    DDF endpoint is not used.
    DOMAIN The domain name or hostname on which the JDBC Gateway server is running. Either DOMAIN or IPADDR is required, but not both. No default value.
    IPADDR The dot-notation IPV4 address of the host on which the JDBC Gateway server is running. Either DOMAIN or IPADDR is required, but not both.

    If this parameter is not specified, the value 127.0.0.1 (local host) is the default. For group director definitions, use the DVIPA IP address of the group director.

    LOCATION

    For JGATE: The location name specified in the JDBC Gateway data source definition entry. See Creating a data source definition entry.

    (Required)

    A valid value is a string 1 - 16 characters.

    NAME

    The database name as known to the server. (Required)

    A valid value consists of 1 - 4 characters. Clients use this ID when they request access to a specific downstream database server.
    PORT

    The TCP/IP port on which the JDBC Gateway server is listening. (Required)

    A valid 1-5 numeric string.

    If this keyword is not entered, the default DRDA port number 443 is used.

    SECMEC The DRDA security mechanism in force.
    EUSRIDPWD
    Encrypt the user ID and password.
    USERIDPWD
    User ID and password are sent as is. No encryption is used.
    USRIDONL
    User ID is sent as is. No encryption is used for the user ID only (client security).
    USRENCPWD
    Encrypt password only.
    TYPE

    Defines the DDF endpoint type.

    JGATE
    DDF endpoint is the JDBC Gateway.

    When using the JDBC Gateway, JGATE is the valid value.

  2. Optional: To define alternate authentication information, use the sample job HLVDRATH to add a global default user definition or authentication information for specific mainframe users as follows:
    1. Locate the HLVDRATH member in the hlq.SHLVCNTL data set.
    2. Modify the JCL according to the instructions provided in the HLVDRATH member.

      When adding the SYSIN statements that define the alternate credentials for logging in to your JDBC Gateway source, as instructed in the JCL, make sure to specify the correct DBTYPE. For JDBC Gateway sources, specify DBTYPE=JGATE.

    3. Submit the job.
    4. Optional: To verify the information stored in the GLOBALU variables and list existing authentication, use the REPORT=SUMMARY statement in the HLVDRATH member and submit the job.
  3. Optional: If using alternate authentication information, auto-enable the SEF ATH rule SHLVXATH(HLVEJGAG) to provide the logon credentials to each JDBC Gateway data source instance. Global variables are used to define alternate authentication credential mapping for the SEF ATH rule.
    1. On the Administer Accelerator Loader Server menu, select option 3 for Manage Rules.
    2. Select option 2 for SEF Rule Management.
    3. Enter * to display all rules, or ATH to display only authentication rules.
    4. Enable the rule by specifying E and pressing Enter.
    5. Set the rule to Auto-Enable by specifying A and pressing Enter.
      Setting the rule to Auto-enable activates the rule automatically when the server is restarted.
  4. Restart the Accelerator Loader server.

Results

The connection between the JDBC Gateway and the Accelerator Loader server for the JDBC data source has been defined.

What to do next

Use the Accelerator Loader studio to create virtual tables and views from the JDBC data source.