Modifying the configuration settings of the JDBC proxy

You can modify the registration.xml file of the JDBC proxy to change the server address, log level, and other settings.

Procedure

  1. The JDBCIntercept.zip package provided with Rational® Test Control Panel contains the registration.xml file. This file contains the configuration settings for the JDBC proxy. Download and extract the file that is provided with Rational Test Control Panel. For more information, see Rational Integration Tester tool packages
  2. Use a text editor to open the registration.xml file.
  3. Edit the configuration settings as shown in the following table:
    Table 1. JDBC proxy configuration settings
    Configurable setting Description
    server base-url="http://<Host name or IP address selected during installation of Rational Test Control Panel>:7819/RTCP"/

    By default, an IBM® Rational Test Control Panel installation listens for proxy registration on port 7819.

    If your Rational Test Control Panel installation uses a different port number, enter the number in this field.

    logger level
    Options are as follows:
    • debug
    • error
    • info
    • warning
    Choose and of these levels.

    identifier name

    This setting is for specifying a name for this proxy. A name makes it easier to identify a specific proxy when several proxies of the same type are registered with Rational Test Control Panel.
    Note: By default, this setting is commented out. Therefore, to use this setting, you must first uncomment it and then specify the identifier name.
    domains

    Generally, there is no need to edit the domain and environment tags.

    However, if you use Rational Test Control Panel to set up specific business domains and environments, do the following tasks:
    • Set the name attribute of the domain tag to the domain name in the Rational Integration Tester project that is used to record SQL events.
    • Set the name attribute of the environment tag to the name of the environment that is selected in the Rational Integration Tester project for recording SQL events.
    Note: If the domain and environment tags are not modified, the driver is available for recording and stubbing in all Rational Integration Tester projects that reference the Rational Test Control Panel installation with which the driver is registered.

    statistics initial-state

    Setting the initial state to on will set the observation level for this intercept in Rational Test Control Panel to Statistics when the intercept first registers with Rational Test Control Panel.

    Setting the initial state to off will set the observation level for this intercept in Rational Test Control Panel to None when the intercept first registers with Rational Test Control Panel.

    includes and excludes section

    By default, the JDBC driver is set to intercept all of the JDBC connections that the application makes.

    To enable or disable the driver for specific connections, use the include and exclude options.

    You can either specify the complete URL of the connection or control several similar connections with a prefix.

    While processing intercepts, the details in the include section is considered before applying the exclude section details.
    Warning: An empty <includes> section disables the driver.
    Here is an example to include a single connection and exclude all of the other connections:
    <includes>
    	<include>jdbc:oracle:thin:@devhost:9080:database2</include>
    </includes>
    Here is an example to exclude all the DB2® and local Oracle connections but include all the other connections:
    <excludes>
    	<exclude>jdbc:db2</exclude>
    	<exclude>jdbc:oracle:thin:@localhost</exclude>
    </excludes>
  4. Save and close the file.

What to do next

If you make any changes to the registration.xml file after deploying the JDBC proxy, restart each stand-alone application and hosted application that is communicating with the JDBC proxy; otherwise, the changes will not take effect.
Note: You might also need to make configuration changes to each stand-alone application and hosted application that is communicating with the JDBC proxy. For more information about this task, see the related links.

Feedback