This topic outlines the process for configuring access to a relational database, and provides links to more detailed instruction.
Steps for this task
From the administrative console, see Creating a JDBC provider using the administrative console.
OR
Using the wsadmin scripting client, see Example: Configuring a JDBC provider using wsadmin.
OR
Using the Java Management Extensions (JMX) API, see Creating a JDBC provider and data source using the Java Management Extensions API.
From the administrative console, see Creating a data source using the administrative console.
OR
Using the wsadmin scripting client, see Example: Configuring a new data source using wsadmin.
OR
Using the JMX API, see Creating a JDBC provider and data source using the Java Management Extensions API.
Tip: Different database vendors require different properties for implementations of their JDBC drivers. Set these properties on the WebSphere Application Server data source. Because Application Server contains templates for many vendor JDBC implementations, the administrative console surfaces the required properties and prompts you for them as you create a data source. However, if you script your data access configurations, you must consult the article Vendor-specific data sources minimum required settings for the required properties and settings options.
Note: When the data source configuration is saved, it will be saved in the resource.xml file. You should not need to modify the jdbc-resource-provider-templates.xml. However, special consideration should be taken if you need to update the jdbc-resource-provider-templates.xml file. See Creating and configuring a JDBC provider and data source using the Java Management Extensions API.