Configuring the physical database resource

After a physical database is created, you can configure the details of the physical database.


  1. Open the Physical View of HCL OneTest™ API’s Architecture School perspective.
  2. Double-click the database to configure. The Database dialog is displayed.
  3. Configure the Connection details, as follows:
    Table 1. Fields for database connection details
    Field Description
    Maximum Number of Connections Enter the maximum number of database connections from HCL OneTest API that are to be available in the pool. If you leave this field blank, it defaults to 1. You might increase the value if you run multiple tests that use the same database resource concurrently.
    Driver Enter the driver details for the specified database type, or select one of the included drivers from the drop-down list if listed.
    Note: The list displays only some of the common drivers and is not listed based on the drivers that you add to the database libraries in the Library Manager.
    Database URL Enter the connection URL for the database, or modify the default URL after you select one of the included drivers. For more information on the specification of database URLs when using IP literal addresses, see IP literal address.
    The following table lists the connection URL patterns that are supported by HCL OneTest API:
    Table 1. Supported URL patterns
    Database driver URL pattern
    IBM® DB2® Universal jdbc:db2://hostName:port/databaseName
    IBM Db2 Alias jdbc:db2:db_alias
    IBM Db2 iSeries jdbc:as400://hostName/defaultSchema
    Derby jdbc:derby://hostName:port/databaseName
    Composite Software JDBC jdbc:compositesw:dbapi@hostName:port?domain=composite&dataSource=system&registerOutputCursors=true
    Microsoft SQL Server jdbc:sqlserver://hostName:port;databasename=databaseName
    Microsoft SQL Server jdbc:jtds:sqlserver://hostName:port/databaseName
    MySQL Connector/J jdbc:mysql://hostName:port/databaseName
    Oracle jdbc:oracle:thin:@hostName:port:sid
    Oracle jdbc:oracle:thin:@//hostName:port/sid
    Oracle jdbc:oracle:thin:@ldap(s)://hostName:port/[dn][attributes][scope][filter][extensions]
    Oracle jdbc:oracle:thin:@connectionDescriptor
    Example connection descriptor:
        (ADDRESS=(PROTOCOL=TCP)(HOST=host1) (PORT=1521))           
    PostgreSQL jdbc:postgresql://hostName:port/databaseName
    SQL Lite jdbc:sqlite:databaseName
    Sybase jTDS jdbc:jtds:sybase://hostName:port/databaseName
    Sybase jConnect jdbc:sybase:Tds:hostName:port/databaseName
    Username/Password Enter a valid user name and password combination to send when you are connecting to the database. Both fields support tags, but the menu is not supported in the Password field.
    Database Schema Enter the name of the database schema to switch to when a connection is established. This field is optional and you can use it to access database tables outside of your default database schema.
    Note: To access the database schema, you might need to grant user access to that schema. For example, GRANT access value ON SCHEMA schema name to USER user name.
    Note: Click Test Connection to verify the connection details.
  4. If required, configure z/OS details, as follows:
    Note: The zOS tab and the SSL tab are enabled only if the Database driver chosen is IBM Db2 Universal. For more information on the recording and virtualization of COBOL Db2 programs on z/OS®, see Testing with IBM Db2 on z/OS systems.
    Table 3. Fields for z/OS configuration
    Field Environments Description
    Subsystem - Host Alias Mappings CICS and MVS batch The entries added provide additional information that is needed to map compiled language Db2 events from a z/OS source to the appropriate JDBC connection.
    Each entry corresponds to a mapping between a Host Name Alias and a Subsystem ID.
    • The Host Name Alias is the fully qualified hostname of the z/OS machine where the database resides. Generally speaking, the Alias corresponds to the hostname in the Database URL for the JDBC connection.
    • The Subsystem ID is the unique identifier of the Db2 subsystem on the z/OS machine. This identifier does not correspond with the JDBC 'database' name in the Database URL. The Db2 subsystem roughly corresponds to an installed Db2 instance.
    DBRM locations CICS only The entries specify the locations of the DBRM files. For example, USER1.COBOL.DBRM.
    CADP Web URLs CICS only The entries added provide RIT with information to connect to the CADP Web application, for automatic configuration of CADP profiles needed for recording and virtualization of COBOL Db2 programs on z/OS. Select the Test Connection(s)button to validate the URLs.
    Recording/Stubbing Filters CICS only Specify the transaction ID, program name, compile unit, user ID, and application ID to be matched when you are recording the CICS region.
    • Rule matching is manged by using CADP profiles on the CICS region.
    • A CADP profile for each rule will be generated for each CICS regions listed in the CADP WebURLs tab.
    • Each rule must be specified on a new line.
    • The wildcard character * can be used at the end of any field value.
    • If a value for one of the fields is unspecified, it defaults to the * character.
    • The values of the Transaction ID and Compile Unit are case-sensitive.
    • Rules define the name of the generated CADP profile using ProfileName. If not specified a profile name will be automatically generated.
    • Each CADP Profile on the CICS region must have a unique name. Existing profiles of the same name on the region will be overwritten.
      Examples of rules are:
    You can do the following actions in each field described in the table, except for Recording/Stubbing Filters:
    • To add a new entry, click Add.
    • To update an entry, select it, make changes to the values, and then click Update.
    • To delete an entry, select it and click Remove.
    Table 4. Fields for SSL configuration (only applies to z/OS)
    Field Description
    Use SSL

    Select this check box to enable security for the transport.

    Selecting the check box makes the other controls on the SSL tab available.

    Server certificates to trust

    All available identity stores are displayed in the drop-down menu. Select one of the following menu items:

    To define a new identity store. See Identity stores and SSL.
    Identity store
    To specify an identity store that contains certificates that the client is to trust.
  5. For more information about the settings available under the Stub tab, see Setting up the schema used for stubbing a physical database.
  6. Configure the schemas and stored procedure filters, under Advanced tab, as follows:
    Table 5. Fields for Advanced details - Enable Stored Procedure Retrieval
    Field Description
    Schema Enter the name of a schema to limit retrieval to that schema (available only if the next option is disabled).
    Use Connection Username Enable this option to retrieve procedures only from the user’s schema (based on the user name/password supplied under the Settings tab).
    Catalog/Package Enter a catalog/package name to limit retrieval to only the procedures that are contained by the catalog/package.
    Procedure Enter a procedure name to retrieve only that specific procedure.
  7. Configure timestamp formatting, under Advanced tab, as follows:
    Table 6. Fields for Advanced details - Enable Timestamp formatting
    Field Description
    Precision Override the default value of Timestamp values. Nine defaults for the fractional second precision.
    Format zero Enable this option to add trailing zeros to match the selected precision when there are no fractional seconds.