Setting up a database transport

Before you can record and virtualize Db2® activities in COBOL and PL/I applications on z/OS® systems, you must set up a database transport.

Before you begin

You must have installed and configured both components of the agent. For more information, see Installing and configuring the agent for z/OS.

Procedure

Select Database Server from the General menu in the Logical View.
Provide a name for the server, and then click OK.
Switch to the Physical View and perform the following steps:

You can see an unconnected resource corresponding to the database server.
1. Open the database server.
2. Select IBM Db2 (Universal) as the Driver on the Connection tab.
3. Specify a database URL in the following format on the Connection tab:
  
  jdbc:db2://hostname:port/LocationName
Replace the values in the hostname and port fields with the values for your instance of Db2®.
Replace LocationName with the location name of your Db2® instance.

Your Db2® administrator can provide you with this information.
Specify the ID and password for the user to connect to Db2®.

This user ID must have authority to access the tables that you want to record.
Specify the schema name for the tables that you want record.
If you want to encrypt the connection to Db2®, follow these steps:
1. Select Use SSL on the SSL tab.
2. Select a keystore that contains the Server certificates to trust.
3. Select New, if you did not define a keystore (also known as an identity store).
  
  The New Identity Store window is displayed.
4. Create a new keystore and provide a password for the keystore.
  
  Note: Be sure to remember the password that you assign to your new keystore.
5. Select Import Key/Certificate(s), to import the CA certificate with which the Db2® certificate was signed.
Select Test Connection to verify that you can successfully connect to Db2®.
On the z/OS tab, select Enable z/OS, and then add a mapping that specifies the hostname or IP address where the Db2® instance resides, and the four-character subsystem ID used by Db2®.
Some z/OS systems have multiple IP addresses and host names. Use the IP address or hostname to use for the communications with the computer where the agent runs. If you know of multiple host names for your z/OS system, you can specify multiple entries, mapping each of the host names to the Db2® subsystem ID.
Note: If you are unsure of the Db2® subsystem ID, you can find it specified on the DSN SYSTEM parameter within the batch jobs. You can find the Db2® subsystem to which a CICS is connected by using the CICS CEMT I DB2CONN command.
Provide the Profile Service connection URL, User ID, Password, and SSL information on the z/OS tab.
The parameters for the Profile Service are required in the following conditions:
- You want to intercept Db2 calls from CICS.
- You do not want to specify all the parameters within batch job JCL that are required for connecting to the Agent for z/OS.
The connection URL is in the following format:
```
http:// (or https:// when you use SSL)
hostname:port – hostname and port number where the Profile Service is running
context_path – context_path parameter in your sites Profile Service eqaprof.env file. The default is /api/v1
/profile
        
```
Select the database to use as the simulation database on the Stub tab.
You can either use the database integrated with Rational® Integration Tester (Derby), Db2® on Linux, UNIX, or Windows, or Db2® on z/OS.
Notes:
- If you use Db2® on z/OS, you can either use the same instance of Db2® where the real data resides, or you can use a different instance of Db2®.
- If you use the same instance of Db2®, then you must use a different database schema.
- Regardless of whether it is the same instance of Db2® or not, if your connection to the real Db2® is encrypted, your connection to a simulation database on Db2® must also be encrypted.
For more information about the permissions that must be granted to the user ID that is used to connect to a simulation database on Db2®, see Authorization.