WAS v8.0 > Migration and coexistence > Distributed operating systems > Migrate product configurations
Migrate from the WebSphere Connect JDBC driver
WAS v8.0 does not include the WebSphere Connect JDBC driver for SQL Server. 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.
Supported configurations:
This topic is about configuration migration, such as migrating dmgrs and federated nodes in a network deployment environment. The Application Migration Toolkit for WAS provides support for migrating applications from previous versions of WAS to the latest product version. For information about migrating applications, read more about the Application Migration Toolkit.
Read Overview of migration, coexistence, and interoperability and Premigration considerations.
Avoid trouble: 
If you are running in a mixed node environment, 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.
jul2011
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
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.
Specify MS converts to the Microsoft SQL Server JDBC Driver, and specifying DD converts to the DataDirect Connect JDBC driver.
The default is operating-system dependant and is listed in the command-line help.
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.
jul2011
The default is ALL
The default is ALL
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, 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.
jul2011
The default is ALL.
The default is true.
The value of traceString is "*=all=enabled" and must be specified with quotation marks to be processed correctly.