Skip Headers

# Data Source Login Types

Previous

Next

The login (if any) associated with a session determines how the TopLink runtime connects to the project's data source.

A login includes details of data source access, such as authentication, use of connection pools, and use of external transaction controllers. A `Login` owns a data source platform.

A data source platform includes options specific to a particular data source including such as binding, use of native SQL, use of batch writing, and sequencing. For more information about platforms, see "Data Source Platform Types".

For projects that do not persist to a data source, a login is not required. For projects that do persist to a data source, a login is always required.

In TopLink Workbench, the project type determines the type of login that the project uses, if applicable.

You can use a login in a variety of roles. A login's role determines where and how you create it. The login role you choose depends on the type of project you are creating and how you intend to use the login:

- "Non-CMP Session Role: Session Login"

- "CMP Deployment Role: Deployment Login"

- "Development Role: Development Login"

There is a session login type for each project type that persists to a data source:

- DatabaseLogin

- EISLogin

Note that there is no XML login. TopLink XML projects are used for nonpersistent, in-memory object to XML data transformation and consequently there is no data source to log in to. For more information about persistent and nonpersistent projects, see "Persistent and Nonpersistent Projects".

For additional information, see the following:

- "Projects and Login"

- "Configuring Common Data Source Login Options"