The Sessions Editor

Developers use the OracleAS TopLink Sessions Editor to create and manage the sessions.xml file. The sessions.xml configures one or more sessions for a project, and associates the sessions with the project. This approach allows you to configure the following elements for each project: Database (JDBC) login information different from that used during development (for example, external data sources for the host application server's connection pools) JTA/JTS transaction usage Cache synchronization Session Broker (multiple databases appearing as a single OracleAS TopLink session)