1. To create the database connection, go to Architecture School > Logical View. 
   Click General > Database Server and provide the name. 
    
   
   

2. Navigate to Architecture School > Physical View, double-click on the recently created database connection to configure the connection to match that used by the Java application. Check the successful database connection message by clicking Test Connection. 
   
   

3. Also, configure the Simulation Database connection to your separate schema and click on Test Stub Connection.  
   
   
    

Deploying the Test Integrations and APIs JDBC proxy into Apache Tomcat 

The configuration changes described in the following topics must be made to each stand-alone application and hosted application that communicates with a Test Integrations and APIs JDBC proxy. 

A Test Integrations and APIs JDBC proxy must be deployed on each application server that is running Apache Tomcat. The JDBC proxy enables a server that hosts applications to use JDBC to access a live database that you want to record or virtualize.  
 
First, install the tool package by following the steps below: 

1. Log in to Test Virtualization Control Panel, open the Tools page, and download the JDBC driver package (.zip file).  
   Alternatively, copy the package from “C:\Program Files\IBM\DevOpsTestControlPanel\tools” folder. For more details, refer here. 

2. Extract the JDBCIntercept.zip file. Copy the below files into the <Tomcat installation directory>\common\lib or to whichever Tomcat library folder that contains JDBC drivers.
   
   com.ibm.rational.rit.jdbcdriver4.jar, 
   jsqlparser15.jar, 
   antlr-3.4.jar, and  
   registration.xml (JDBC proxy configuration file)    
   
      
   

3. Locate the Tomcat startup script; its location depends on the Operating System.  
   
   a. Windows: %CATALINA_HOME%\bin\catalina.bat 
   b. Unix-Linux: $CATALINA_HOME/bin/catalina.sh
   
   Open the catalina file for editing and add the following JAVA_OPTS variable, set the jdbc.drivers property as follows: 
   SET JAVA_OPTS=%JAVA_OPTS% -Djdbc.drivers=com.greenhat.jdbc.Driver
   
   
   Save and close the file. For more details, refer here.  

4. Restart Control Panel Service and restart Tomcat server to reflect the changes, refer here.
    

Now, log in to the Test Virtualization Control Panel, then navigate to the Infrastructure page. Verify that the JDBC Agent shows the status as "Connected". The configuration changes must be made to each stand-alone application and hosted application that communicates with a Test Integrations and APIs JDBC proxy. 
 

Creating database stubs using the Recording Studio 

1. Open the Test Integrations and APIs product and open the Recording Studio perspective. 

2. In the Monitor Configuration view, click on the symbol “+“ to select the operators or resources to monitor.  

3. Click OK after adding the resource, which will be displayed as an active connection ready for monitoring.  
    

4. Start Recording the JDBC Events by clicking on the Record button  in the Events View tab. On Events View popup, select Yes, record the SQL... and Create a database stub but don't start it. It is not possible to create a stub from previously recorded events; you must create the stub directly as part of the recording process. 
    
   
    
   The recording rule is shown on the DevOps Test Control Panel Network Dashboard. 
    
   
   Note that the Recipient column shows the destination for matching events. By default, Recording Studio listens on a different random port number each time it is started. In this case, the Library Manager has been used to fix the port number to “7777” to avoid problems with firewalls. 
   
    

5. Invoke your java program or AUT hosted on Tomcat server, to interact with database and capture the events. 
    

6. Execute some SQL queries, in this case, insert data into the UserDetails table. 
   
   
   

7. The event is being seen in the Recording Studio. Events will be posted directly from the Integration Tester JDBC Agent within the Java application to the Recording Studio.  Events are not sent via Test Integrations and APIs.   
    

8. The matching table is created in the stub simulation schema as well as an internal table to store the SQL command. (Check the SQL Dashboard Database as shown below)
    

9. Stop the recording and see the stub created in Test Factory.
    
   
   
   

10. The Tables tab shows a summary of tables captured and their data columns and rows. 
    
    

11. The Queries tab lists any SQL queries that were recorded. 
    
    

12. After events are recorded, you can create a test from the selected events in the Events View pane. Click the Create Test from selected events icon in the Events View toolbar, or right-click the messages and select Create Test or Create Parameterized Test from the menu. 
     

13. On the Resource Type dialog, select a type of test that you want to create, click Next. 
     

14. On the Data Storage page, choose one of the following storage options, click Next. 
    
    
    
    

15.  On the Summary page, enter a name for the test. To edit the new test immediately after it is created, select Open resource after finish and Click Finish. 
    
    
     
    

16. A test is created. The test contains Test Steps that relate to the selected events. Test steps vary on the type of event. 
     
     

Refer to the product documentation below for additional details. 

Creating tests from recorded events
Database stubs overview
Recording Studio