Skip Headers

# Non-CMP Session Role: Session Login

Previous

Next

You create a session login in the `sessions.xml` file for TopLink applications that do not use container-managed persistence (CMP).

Typically, the TopLink runtime instantiates a project when you load a session from the `sessions.xml` file (see Acquiring and Using Sessions at Run Time). The runtime also instantiates a login and its platform based on the information in the `sessions.xml` file.

The TopLink runtime uses the information in the session login whenever you perform a persistence operation using the session in your non-CMP TopLink application.

In this case, you do not configure a deployment login (see "CMP Deployment Role: Deployment Login").

If you are using TopLink Workbench and your login is based on a relational database platform, you must also configure a development login (see "Development Role: Development Login").

If a `sessions.xml` file contains a login, this login overrides any other login definition.

There is a session login type for each project type that persists to a data source. For a complete list of login types available, see "Data Source Login Types".

For information on configuring a session login, see "Configuring a Session Login".