NOTE: All steps are done from the Administration Console.
Create a new environment variable:
1. Go to Environment
2. Manage WebSphere Variables
3. Click on New
4. Create a new env variable for the driver's installation directory, for instance: CONNECTJDBC_JDBC_DRIVER_PATH
5. For Value, put the path in which the drivers are installed: \WebSphere\Appserver\lib - (the driver must be in the location to work correctly with WebSphere)
Create the Resource:
1. Go to Resources
2. go to JDBC Providers
3. Create a New Provider
4. Give it a name: DataDirect ConnectJDBC type 4 driver for MS SQL Server
5. Set the classpath variable using the environment variables that you set:
${CONNECTJDBC_JDBC_DRIVER_PATH}/sqlserver.jar
${CONNECTJDBC_JDBC_DRIVER_PATH}/base.jar
${CONNECTJDBC_JDBC_DRIVER_PATH}/util.jar
6. Put in the implementation class name:
com.ddtek.jdbcx.sqlserver.SQLServerDataSource
NOTE: if you are connecting using SequeLink and need distributed transactions, be sure to use com.ddtek.jdbcx.sequelink.SequeLinkDataSource as your implementation class name.
Create Datasources from the Provider:
1. Click on DataSources from the Provider Screen (on the bottom under Additional Properties)
2. Click New on the Data Sources screen
3. Give it a Name: MyDataSourceName
4. Give it a JNDI name: jdbc/MyDataSourceName
5. IBM Websphere support has indicated that there is currently no data source helper class specifically designed to be used with the Connect for JDBC drivers, so the safest choice would be to use the GenericDataStoreHelper class. The main drawback to using this class is that it has no error mapping to the Websphere Stale Connection Exception architecture. It is recommended that customers who wish the best possible mapping set up their own custom DataStoreHelper class for the Connect for JDBC driver they intend to use:
http://publib.boulder.ibm.com/infocenter/ws51help/index.jsp?topic=/com.ibm.websphere.base.doc/info/aes/ae/rdat_levport.html
http://publib.boulder.ibm.com/infocenter/ws51help/index.jsp?topic=/com.ibm.websphere.base.doc/info/aes/ae/rdat_datstorexmp.html
6. Click on Custom Properties
7. Add a new connection property for each of the connection properties required to connect. Required connection properties may include ServerName, PortNumber, User, and Password. Check the Connect for JDBC Reference Guide for details on required connection properties for the driver you are trying to use.
Once you save, the new datasource will be available for use.
