Skip Headers

# Configuring Development and Deployment Logins

Previous

Next

This section describes how to designate a defined login's role. For information on how to define a login, see "Configuring Login Information". TopLink recognizes the following login roles:

- Development Role

- CMP Deployment Role

- Non-CMP Session Role

Development Role

While using TopLink Workbench to develop a project (see "Development Role: Development Login"), you must define a login (see "Configuring Login Information") and designate it as the development login. The development login is stored in the TopLink project file. TopLink Workbench uses the information in the development login whenever you perform a data source operation from within TopLink Workbench. For example, when you read or write schema information from or to a data source during application development, the development login information is never written to a `sessions.xml` or `project.xml` file and is overridden by the deployment login (or the session login) at run time.

For more information on how to use a development login to connect to a database, see "Logging in to the Database".

CMP Deployment Role

If you are creating a CMP project (see "CMP Deployment Role: Deployment Login"), you may define a run-time login (see "Configuring Login Information") and designate it as the deployment login. This is the login that the application will use at run time, unless overridden in the `sessions.xml` file, CMP deployment file, or through Java code.

Non-CMP Session Role

If you are creating a non-CMP project (see "Non-CMP Session Role: Session Login"), Oracle recommends that you use the `sessions.xml` file to store the sessions your project uses at run time (see "Data Source Login Types").