Creating a Data Source for a JDBC
Connector
The Change Tracker application connects to the database via a JDBC connection. In the Visual Administrator, you can set up JDBC connections to the MDM Change Tracking database which can reside on any one of the following database servers:
● MS SQL
● Oracle
● Max DB
Connection to the DB2 server is also supported.
Before creating a data source, you must first deploy the JDBC driver you want to use.
More information: refer to the following link: JDBC Connector Service → Deploying a JDBC Driver:
http://help.sap.com/saphelp_nw2004s/helpdata/en/b0/6e62f30cbe9e44977c78dbdc7a6b27/frameset.htm
or you can access this information through:
http://help.sap.com/saphelp_nw2004s/helpdata/en/, and in the search box enter, JDBC Connector Service.
Refer to the section: Deploying a JDBC Driver
This example is based on connection to MS SQL Server (2000).
There may be variations for other versions.
...
1. Open the Visual Administrator application where connection to the MS SQL Server is carried out.
2. Select JDBC Connector from the menu on the left under Services.
3. Select Data Sources.
4.
Select the Create New
Driver or DataSource icon. 
5. Choose the Main tab and populate the fields as per the table below:
Field Name |
Value |
Application Name |
Any value |
Name |
Any value |
Description |
Optional |
Aliases |
Free text – this is the name to be used when configuring the change tracker
When you click the Add Alias button, the deployer is automatically updated. |
Driver Name |
Select MSSQL from dropdown list |
JDBC Version |
Select value from dropdown list These examples are based on the Microsoft JDBC Connection For example, 2.0 with XA support |
Object Factory |
Actual strings for MS SQL Server For example, (JDBC Version 2.0), com.microsoft.jdbcx.sqlserver. |
DataSource Type |
Select value from dropdown list For example (JDBC Version 2.0), ConnectionPoolDataSource |
CPDS Classname |
com.microsoft.jdbcx.sqlserver. |
6. Select the Additional tab and populate the fields as per the table below:
Key |
Value |
databaseName |
Change Tracking Connection Parameter Connection Parameter is a database |
password |
Password to access database |
portNumber |
SQL Server port number Default for SQL: 1433 |
serverName |
DBMS Server |
user |
User name to access database |
SQL Engine |
Vendor SQL |
7. Save the data source.
8. Select the DB Initialization tab and enter the following statement:
Select count (*) as NumRecs from A2i_CM_History
9. Save your entries.
10. Select Execute.
If you receive a confirmation, your connection has been established.
...
...
1. Open the Visual Administrator application where connection to the Oracle Server is carried out.
2. Select JDBC Connector from the menu on the left under Services.
3. Select Data Sources.
4.
Select the Create New
Driver or DataSource icon. 
5. Choose the Main tab and populate the fields as per the table below:
Field Name |
Value |
Application Name |
Any value as long as it has not been used before |
Name |
Any value |
Description |
Optional |
Aliases |
Free text – this is the name to be used when configuring the change tracker Tip: Do not give the alias the name jdbc or copy the Name above
When you click the Add Alias button, the deployer is automatically updated. |
Driver Name |
From the dropdown list, select the Oracle JDBC driver that you deployed (see prerequisites above). |
JDBC Version |
Select value from dropdown list For example, 2.0 with XA support |
Object Factory |
Actual strings for Oracle Server For example, oracle.jdbc.pool.OracleDataSourceFactory |
DataSource Type |
Select value from dropdown list For example, XADataSource |
XADS Classname |
For
example, oracle.jdbc.xa.client.Oracle |
6. Select the Additional tab and populate the fields as per the table below:
Key |
Value |
password |
Password to access database |
url |
jdbc:oracle:thin:@<hostname>:<listener portnumber>:<DBMS Server> For example, jdbc:oracle:thin:@10.26.186.71:1521: |
user |
Change Tracking Connection Parameter For example, Vendor_z000 Connection Parameter is a User/Schema |
SQL Engine |
Vendor SQL |
7. Select the DB Initialization tab and enter the following statement:
Select count (*) as NumRecs from A2i_CM_History
8. Save your entries.
9. Select Execute.
If you receive a confirmation, your connection has been established.
If the NetWeaver instance is installed with MaxDB, then no additional driver installation is necessary. The data source uses the SYSTEM_DRIVER.
If this is not the case, then you must install the Max DB Client on the NetWeaver machine and create a new driver which uses the sapdbc.jar file.
...
1. Open the Visual Administrator application where connection to the Max DB Server is carried out.
2. Select JDBC Connector from the menu on the left under Services.
3. Select Data Sources.
4. Select the Create New Driver or DataSource icon.

5. Choose the Main tab and populate the fields as per the table below:
JDBC Version = 1.x
Driver Class = com.sap.dbtech.jdbc.DriverSapDB
Field Name |
Value |
Application Name |
Any value |
Name |
Any value |
Description |
Optional |
Aliases |
Free text – this is the name to be used when configuring the change tracker
When you click the Add Alias button, the deployer is automatically updated. |
Driver Name |
Select value from dropdown list For example, Max DB |
JDBC Version |
1.x ( no XA support) |
Driver Class |
com.sap.dbtech.jdbc.Driver |
Database URL |
jdbc:sapdb://<DBMS Server >/<Change Tracker Connection Parameter> Connection Parameter is a database |
User |
MDMADMIN |
6. Select the Additional tab and populate the following field as per the table below:
Key |
Value |
currentschema |
<Change Tracking Database
Name> |
Select Vendor SQL.
7.
Important!
Select the DB Initialization tab and enter the
following statement:
Select count (*) from A2i_CM_History
8. Save your entries.
9. Select Execute.
If you receive confirmation, your connection has been established.
