About this task
If you are using Rational Integration Tester 8.5.0
or later and you must simulate an IBM DB2®,
Oracle, Microsoft SQL Server,
or MySQL database, you can use the integrated simulation database
or a vendor-specific database.
The integrated simulation database is an Apache Derby database that is included with
Rational Integration Tester. Although the
Apache Derby database is based on the Java™, JDBC,
and SQL standards, it cannot simulate the characteristics of all other databases.
Therefore, SQL statements for unsupported databases will fail on an Apache Derby database.
Hence, in the following situations, you must use a database of the same type as the
original simulation database:
- An application may be using SQL syntax that is not understood by the integrated
simulation database. This will be evident if the console of the application displays
messages about unexpected JDBC exceptions during the recording (learning) phase. If you
are using the Rational Integration Tester
JDBC proxy, these SQL errors are also logged in the activity log of IBM Rational Test Control Panel, which is viewable if you have Rational Test Control Panel
administrator privileges.
- A database might support a data type that the integrated simulation database does not
support. This will be evident if you try to edit a database table of a database stub that
includes a data type not supported by the Apache Derby database. Rational Integration Tester
will display SQL syntax error messages when saving the database table.
Note: If you elect to use the integrated simulation database,
the instances of the databases that Apache Derby uses are stored in
the workspace of Rational Integration Tester or IBM Rational Integration Tester Agent,
whichever is applicable. The specific location in the workspace is
unimportant because the locations where the instances are stored are
transient.
Depending on the option you select, the database
schema or the integrated simulation database will be used while Rational Integration Tester is
"learning" the stubs, and also used when a stub is started, that is,
the database schema or the integrated database will be used to store
the contents of a database stub.
Note: To run
more than one database stub simultaneously and you want to use a database
schema, you need a database stub schema for each database stub. For
example, to run five database stubs simultaneously, you need five
database stub schemas. However, each schema must match the corresponding
database. For example, to stub an Oracle database, you need an Oracle
schema. Alternatively, to stub a Microsoft SQL
Server database, you need a Microsoft SQL
Server schema, and so on.
The following table lists the
live and simulation database combinations that are supported by different
versions of Rational Integration Tester.
Live and simulation database combination support |
Rational Integration Tester version |
DB2/DB2 |
All |
DB2/Integrated
simulation database (excluding support for JDBC virtualization on IBM WebSphere® Application Server) |
8.5.0 or later |
DB2/Integrated
simulation database (including support for JDBC virtualization on WebSphere Application Server) |
8.5.1 or later |
Microsoft SQL
Server/Microsoft SQL Server |
All |
Microsoft SQL
Server/Integrated simulation database (excluding support for JDBC
virtualization on WebSphere Application Server) |
8.5.0 or later |
Microsoft SQL
Server/Integrated simulation database (including support for JDBC
virtualization on WebSphere Application Server) |
8.5.1 or later |
MySQL/MySQL |
All |
MySQL/Integrated simulation database (excluding
support for JDBC virtualization on WebSphere Application Server) |
8.5.0 or later |
MySQL/Integrated simulation database (including
support for JDBC virtualization on WebSphere Application Server) |
8.5.1 or later |
Oracle/Oracle |
All |
Oracle/Integrated simulation database (excluding
support for JDBC virtualization on WebSphere Application Server) |
8.5.0 or later |
Oracle/Integrated simulation database (including
support for JDBC virtualization on WebSphere Application Server) |
8.5.1 or later |