Migrating from the WebSphere Connect JDBC driver

WebSphere® Application Server Version 8.5 does not include the WebSphere Connect JDBC driver for SQL Server. This driver was supported through Version 6.1. Use the WebSphereConnectJDBCDriverConversion command to convert data sources from the WebSphere Connect JDBC driver to the DataDirect Connect JDBC driver or the Microsoft SQL Server JDBC driver. The WebSphereConnectJDBCDriverConversion command processes resources.xml files, and there are many options that can be specified to indicate which resources.xml files to process.

Before you begin

Supported configurations:

This topic is about configuration migration, such as migrating deployment managers and federated nodes in a network deployment environment. The Application Migration Toolkit for WebSphere Application Server provides support for migrating applications from previous versions of WebSphere Application Server to the latest product version. For information about migrating applications, read more about the Migration Toolkit.

Read Overview of migration, coexistence, and interoperability and Premigration considerations.

About this task

Avoid trouble: If you are running in a mixed node environment, you must issue this command for each node, specifying a specific cell name for the cellName parameter, and a specific node name for the nodeName parameter. If you do not issue these commands, you will get the following exception for your back-level nodes:

IGR0480E: The node node-name specified for the -nodeName parameter
is not at the current release. Migrate this node to the current release and rerun the tool.

Syntax

./WebSphereConnectJDBCDriverConversion.sh
			[-profileName profile_name]
			[-driverType MS | DD]
			[-classPath class_path]
			[-nativePath native_path]
			[-pathSeparator separator]
			[[-cellName ALL | cell_name [-clusterName ALL | cluster_name] |
			  [-applicationName ALL | application_name] |
			  [-nodeName ALL | node_name] [-serverName ALL | server_name]]]
			[-backupConfig true | false] 
			[-username userID]
			[-password password]
			[[-traceString trace_spec [-traceFile file_name]]

WebSphereConnectJDBCDriverConversion.bat
			[-profileName profile_name]
			[-driverType MS | DD]
			[-classPath class_path]
			[-nativePath native_path]
			[-pathSeparator separator]
			[[-cellName ALL | cell_name [-clusterName ALL | cluster_name] |
			  [-applicationName ALL | application_name] |
			  [-nodeName ALL | node_name] [-serverName ALL | server_name]]]
			[-backupConfig true | false] 
			[-username userID]
			[-password password]
			[[-traceString trace_spec [-traceFile file_name]]

Parameters

-profileName profile_name

This optional parameter is used to specify a specific profile configuration in the Version 8.5 environment.

If this parameter is not specified, the default profile is used. If the default is not set or cannot be found, an error is returned.

If the command is run from within the profile_name/bin directory, it is implicit that the profile_name profile should be migrated and this parameter is not needed.

-driverType MS | DD

This required parameter is used to indicate the type of conversion that you want to perform.

Specifying MS converts to the Microsoft SQL Server JDBC Driver, and specifying DD converts to the DataDirect Connect JDBC driver.

-classPath class_path

This required parameter is used to specify the class path for the new JDBC driver.

-nativePath native_path

This optional parameter is used to specify the native path for the new JDBC driver.

-pathSeparator separator

This optional parameter is used to specify a path separator other than the default.

The default is operating-system dependant and is listed in the command-line help.

-cellName ALL | cell_name

This optional parameter is used to specify the specific name of the cell to process or to specify all cells.

The default is ALL. If ALL is specified, the values specified for the nodeName, serverName, applicationName, and clusterName parameters are ignored, and the settings for these parameters revert to their default values of ALL.

-clusterName ALL | cluster_name

This optional parameter is used to specify the specific name of the cluster to process or to specify all clusters.

The default is ALL

-application nameName ALL | application_name

This optional parameter is used to specify applications to process. (Some resource.xml files might exist in applications if enhanced EAR file support is used.)

The default is ALL

-nodeName ALL | node_name

This optional parameter is used to specify the specific name of the node to process or to specify all node names in the configuration. If you specify a specific nodeName, you must also specify a specific cell name on the cellName parameter. If a specific cell name is not specified, the default value of ALL is used for this parameter.

If ALL is specified for this parameter, the value specified for the serverName parameter is ignored, and the setting for the serverName parameter reverts to its default value of ALL.

-serverName ALL | server_name

This optional parameter is used to specify the specific name of a server or to specify all server names in a node.

The default is ALL.

-backupConfig true | false

This parameter is used to specify whether (true) or not (false) to back up the existing configuration before the command makes changes to the configuration.

The default is true.

-username userID

This optional parameter is used to specify the user name to be used by this command.

-password password

This optional parameter is used to specify the password to be used by this command.

-traceString trace_spec

This optional parameter is used with -traceFile to gather trace information for use by IBM® service personnel.

The value of traceString is "*=all=enabled" and must be specified with quotation marks to be processed correctly.

-traceFile file_name

This optional parameter is used with -traceString to gather trace information for use by IBM service personnel.