Deploying SDOs on non-WAS servers

When using Service Data Objects (SDOs) and targeting WebSphere Application Server (WAS) based servers (such as WAS 5.1, 6.0, 6.1 and Portal 5.1, 6.0), the Rational application development product automatically sets up deployment information at runtime. However, if you want to target a non-WAS server, you need to manually ensure that your server has access to the necessary SDO libraries and other resources. To do this, complete the following steps:

Make sure the JDBC Mediator Library jars are available to your server by adding the jars to the server classpath.
To see the jars that are needed, look at your project in the Project Explorer or Package Explorer. You will see a classpath library entitled JDBC Mediator Library, which is used to enable you to work with your applications at development time. If you expand the classpath library node, you can see the jars that are required for that library, as well as their path on the disk. Make sure that copies of these jars available to your target server.
Make sure you can access the database on the target server. To do this using the Driver Manager connection on your target server, you must make sure that your driver jars are available to the server.
To determine which jars are used at development time, select Properties from your project's context menu and then select JDBC Connections from the property page. Select your desired connection, and in the Runtime connection details section, click the Edit button. This displays your connection details, including the jars needed for the Class Location. Alternatively, you can choose to use a data source connection, in which case you will need to ensure that the required data source has been set up on your target server.