Show TOC

data-source-aliases.dtdLocate this document in the navigation structure

Definition

Use this document type definition (DTD) to produce XML files for setting aliases for a previously deployed DataSource.

You can deploy a DataSource alias definition by creating a data-source-aliases.xml file based on this DTD, and including it in:

  • The META-INF directory of the application archive (EAR)

  • The ./servers/descriptors directory of the library or service SDA

Structure

The data-source-aliases.dtd has the following structure:

Figure 1: data-source-aliases.dtd

The use of each element is explained below:

Schema Element / Attribute

Description

data-source-aliases

The root element for this deployment descriptor. Contains information about the application name to which the data source alias is associated, and the aliases for the specified DataSource.

application-name

Defines the name of the application to which the data source alias is associated. If the data-source-aliases.xml file is included in the archive file (EAR) of the application, this tag is ignored. If you deploy a standalone data source alias, the application name you specify is a formal name used for the configuration where the data source alias is stored. Therefore, you can specify a unique name.

Used in: data-source-aliases

aliases

Contains information about the name of the DataSource and the alias or aliases that you specify for the DataSource. You can include multiple <aliases> tags in a single data-source-aliases.xml file to add aliases for more than one DataSource objects.

Used in: data-source-aliases

data-source-name

Defines the DataSource for which you add aliases. The DataSource is defined by its name. On a system DataSource, you can use com.sap.dataSource.default

Used in: aliases

Example: <data-source-name> myDataSource </data-source-name>

alias

Defines the alias for the DataSource. The alias is used for binding the same DataSource with a different name in the naming, so that applications can use alternative names. Aliases must be unique.

Used in: aliases

Example: <alias> myDS </alias>

isolation-level

This is a DataSource-alias-specific setting which overrides the one specified for the DataSource.

Determines the transaction isolation level for the relevant DataSource. If you do not specify this setting, the system uses the isolation level of the relevant DataSource.

Possible values: TRANSACTION_READ_UNCOMMITTED , TRANSACTION_READ_COMMITTED , TRANSACTION_REPEATABLE_READ , TRANSACTION_SERIALIZABLE , TRANSACTION_NONE

Used in: aliases

max-connections

This is a DataSource-alias-specific setting which overrides the one specified for the DataSource.

Specifies the maximum number of connections the relevant DataSource can create.

The recommended value depends on the specifics of the application using the alias, and must not exceed the value specified for the relevant DataSource.

Used in: aliases