Data Source

Use the Data Source configuration page to edit the business integration data source properties.

To view this administrative console page, click Resources > JDBC > Business Integration Data Sources > Data Source link.

Required security role for this task: When security and role-based authorization are enabled, you must be logged in as an administrator or a configurator to perform this task.
Use the Data Source configuration page to review and edit existing business integration data sources. This page has the following configuration sections:
Data Source Provider
Shows the selected provider name and the implementation type. The implementation type can be XA or Connection Pool.
Scope
Shows the scope at which the data source is configured. The scope can be cell, cluster or server.
Data Source Properties
The data source properties are specific to each selected database provider.
Component Specific Properties
These fields are determined by the component being configured. Typically, the component needs to set the JNDI name and usually the data source name in order to find the data source. It holds a component specific description for the use of this data source and the component name that is using the data source.
Create Tables
If checked the tables are created on first touch or when the data source is configured. If unchecked, then the component that uses the data source assumes that the tables are present. The user can find the database scripts in the instruction box to give the database administrator to create the needed tables.
Create Schema
If the component and data base provider supports schema creation, then the flag shows below the Create Tables flag.

New data sources cannot be created on this page. Data sources can only be created on a component specific configuration page. The component specific configuration page sets all the required fields.

The fields shown in the Data Source configuration page depend on the type of database provider used. This page shows what a typical DB2 configuration page would look like. If you choose a different database provider, some of the fields may be different or missing particularly in the Component Specific Properties section.


Links marked (online) require access to the Internet.

Check for updates to this topic (online)

Provider

Identifies the database provider or file store. The provider or file store cannot be changed after it has been configured.

Table 1. Provider
Property Value
Data type String
Default None

Implementation Type

Specifies the implementation type of XA or Connection Pool (CP). For most database providers, use XA as the implementation type needed for two-phase commits.

Table 2. Implementation Type
Property Value
Data type String
Default None

Scope

Shows the scope at which the data source is configured. The scope can be cell, cluster, node or server. For example, NodeA/TestServer is a fully qualified server scope. You cannot edit the scope once it is configured.

Table 3. Scope
Property Value
Data type String

User Name

Identifies a user name that can authenticate with the database. Ensure that the user has been granted all access rights for the intended operations. If you need the user to create schemas and tables, ensure that the user has all the rights needed to create schemas and tables.

Table 4. User name
Property Value
Data type String

Password

Identifies the user's password used to authenticate with the database.

Table 5. Password
Property Value
Data type String

Database Name

Identifies the name of the database.

Table 6. Database name
Property Value
Data type String

Schema Name

Identifies the schema name used to access this configured data source.

Table 7. Schema name
Property Value
Data type String

Server Name

Identifies the database's server.

Table 8. Server name
Property Value
Data type String

Server Port Number

Specifies the database listener port used for all communications involving this data source.

Table 9. Service port number
Property Value
Data type Integer

Driver Type

Specifies the driver type for the database provider. See "JDBC specifications" for more information on driver types.

Table 10. Driver type
Property Value
Data type Integer

Component

Displays the name of the component that requires the data source.

Table 11. Component
Property Value
Data type String

Data Source Name

Specifies the data source name used to uniquely identify a data source configuration. This name corresponds to WebSphere® Application Server JDBC data source name.

Table 12. Data source name
Property Value
Data type String
Default None

JNDI Name

Specifies the JNDI name used by the component to locate the data source. This field is configured by the component to ensure that the data source can be found. It is not editable.

Table 13. JNDI name
Property Value
Data type String
Default None

Description

Provides a description of the Business Integration data source.

Table 14. Description
Property Value
Data type String

Create Tables

Select this check box to allow the component to create the tables the first time it accesses the data source. If your site policy restricts table creation to a database administrator, clear the check box, locate the scripts in the message box and give these scripts to your database administrator to run.

Table 15. Create tables
Property Value
Data type Boolean
Default See "Table and schema creation matrices".

Under Additional Properties are links to additional information.

Custom Properties
Links you to the WebSphere Application Server Network Deployment JDBC data source custom properties page. Use this page to fine tune your data source settings.
JDBC Data Source
Links you to the WebSphere Application Server Network Deployment JDBC data source configuration page. Use this page to fine tune data source configuration settings.
J2C Authentication Alias
Links you to the page for configuring the authentication settings used by this data source. If the link does not show, then no authentication is used.
Messaging Engine Data Store
Links you to the Messaging Engine data store that uses the data source. If the data source does not use a messaging engine, this link will not be available.