+

Search Tips   |   Advanced Search

JDBCProviderManagement command group for AdminTask object

We can use the Jython or Jacl scripting languages in interactive mode to configure data access and data sources . The commands and parameters in the JDBCProviderManagement group can be used to create or list data sources and Java database connectivity (JDBC) providers.

The JDBCProviderManagement (AdminTask) includes the following commands:


createDatasource

The createDatasource command creates a new data source to access the back end data store. Application components use the data source to access connection instances to the database.

Target object JDBC Provider Object ID - The configuration object of the JDBC provider to which the new data source will belong.

Required parameters

- name

The name of the data source. (String, required)

-jndiName

The Java Naming and Directory Interface (JNDI) name. (String, required)

-dataStoreHelperClassName

The name of the DataStoreHelper implementation class that extends the capabilities of the selected JDBC driver implementation class to perform data-specific functions. WebSphere Application Server provides a set of DataStoreHelper implementation classes for each of the JDBC provider drivers it supports. (String, required)

configureResourceProperties

This command step configures the resource properties that are required by the data source. (Required) We can specify the following parameters for this step:

name

The name of the resource property. (String, required)

type

The type of the resource property. (String, required)

value

The value of the resource property. (String, required)

Optional parameters

-description

The description of the data source. (String, optional)

-category

The category that we can use to classify a group of data sources. (String, optional)

-componentManagedAuthenticationAlias

The alias used for database authentication at run time. This alias is only used when the application resource reference is using res-auth=Application. (String, optional)

-containerManagedPersistence

Specifies if the data source is used for container managed persistence for enterprise beans. The default value is true. (Boolean, optional)

Examples

Batch mode example:

Interactive mode:

Avoid trouble: Be aware of the following issues with the createDatasource command:

gotcha


createJDBCProvider

The createJDBCProvider command creates a new Java database connectivity provider (JDBC) that we can use to connect to a relational database for data access.

Target object None

Required parameters

-scope

The scope for the new JDBC provider. Provide the scope in the form type=name. Type can be Cell, Node, Server, Application, or Cluster, and name is the name of the specific instance of the cell, node, server, application, or cluster that you are using. The default is none. (String, required)

-databaseType

The type of database that will be used by the JDBC provider. For example, DB2 , Derby, Informix , Oracle, and so on. (String, required)

-providerType

The JDBC provider type that will be used by the JDBC provider. (String, required)

-implementationType

The implementation type for this JDBC provider. Use Connection pool data source if the application runs in a single phase or a local transaction. Otherwise, use XA data source to run in a global transaction. (String, required)

Optional parameters

-classpath

List of paths or JAR file names that form the location for the resource provider classes. (String, optional)

-description

The description for the JDBC provider. (String, optional)

-implementationClassName

Specifies the Java class name for the JDBC driver implementation. (String, optional)

-name

The name of the JDBC provider. The default is the value from the provider template. (String, optional)

-nativePath

List of paths that form the location for the resource provider native libraries. (String, optional)

-isolated

Whether the JDBC provider loads within the class loader. The default value is false. We cannot specify a native path for an isolated JDBC provider. (Boolean, optional)

Examples

Batch mode example:

Interactive mode:


deleteDatasource

The deleteDatasource command deletes a data source for an existing JDBC Provider at a specific scope.

Target object DataSource Object ID - The configuration object of the DataSource to delete.

Required parameters None.

Optional parameters None.

Examples

Batch mode example:

Result:

The DataSource is deleted at the specific scope. Also, if DataSource is a DB2 data source configured as a Type 4 JDBC driver and enabled for Client Reroute, the JNDI name specified in either the Client reroute server list JNDI name field or the clientRerouteServerListJNDIName data source custom property is unbound.

To save the changes made by the command, invoke the save command of the AdminConfig object. If the changes are not saved, the Client reroute server list JNDI name must be rebound by issuing a test connection on DataSource or by restarting the server.


deleteJDBCProvider

The deleteJDBCProvider command deletes a JDBC provider and its data sources from a specific scope.

Target object JDBCProvider Object ID - The configuration object of the JDBCProvider to delete.

Required parameters None.

Optional parameters None.

Examples

Batch mode example:

Result:

The JDBCProvider is deleted at the specific scope. If JDBCProvider is a DB2 universal database provider, for each data source of JDBCProvider configured as a Type 4 JDBC driver and enabled for Client Reroute, the JNDI name specified in either the Client reroute server list JNDI name field or the clientRerouteServerListJNDIName data source custom property is unbound.

To save the changes made by the command, invoke the save command of the AdminConfig object. If the changes are not saved, the Client reroute server list JNDI names must be rebound by issuing test connections on the data sources of JDBCProvider or by restarting the server.


listDatasources

Use the listDatasources command to list data sources contained in the specified scope.

Target object None

Required parameters None.

Optional parameters

-scope

The scope for the data sources that will be listed. Provide the scope in the form type=name. Type can be Cell, Node, Server, Application, or Cluster, and name is the name of the specific instance of the cell, node, server, application, or cluster that you are using. The default is All. (String, optional)

Examples

Batch mode example:

Interactive mode:


listJDBCProviders

The listJDBCProviders command lists JDBC providers contained in the specified scope.

Target object None

Required parameters None.

Optional parameters

-scope

The scope for the JDBC providers that will be listed. Provide the scope in the form type=name. Type can be Cell, Node, Server, Application, or Cluster, and name is the name of the specific instance of the cell, node, server, application, or cluster that you are using. The default is All. (String, optional)

Examples

Batch mode example:

Interactive mode:


Related tasks

  • Use the wsadmin scripting AdminTask object for scripted administration

  • Commands (AdminTask)