Skip navigation.
Downloads | Product Documentation | Support

Managing WebLogic Platform Database Resources

# Default JDBC Configurations for WebLogic Platform

The following sections describe the default JDBC configurations for the prepackaged WebLogic Platform configuration templates used to create domains with the Configuration Wizard Topics include:

- Default JDBC Configuration for the Basic WebLogic Platform Domain
- Summary of Default JDBC Configurations for All Configuration Templates

Note: If you are using WebLogic Platform 8.1 SP2 or earlier, see "Default JDBC Configurations in SP2 or Earlier" in Important Usage Notes for Previous Releases of WebLogic Platform 8.1 at the following URL: `http://e-docs.bea.com/platform/docs81/sp_notes/sp_notes.html#sp2_defaultJDBC`

# Default JDBC Configuration for the Basic WebLogic Platform Domain

The following figure shows the default JDBC configuration for a domain created using the Basic WebLogic Platform Domain configuration template.

Figure 4-1 JDBC Configuration for the Basic WebLogic Platform Domain (Default)

As shown in the figure, the Basic WebLogic Platform Domain configuration template configures the following JDBC components, by default:

- One database, `workshop`: Provided by WebLogic Workshop and used by all components as default PointBase database.
- Four connection pools

- `bpmArchPool`: Provided and used by WebLogic Integration for business process management archiving.
- `cgJMSPool-nonXA`: Provided by WebLogic Workshop and used by WebLogic Workshop, WebLogic Portal, and WebLogic Integration for WebLogic JMS persistent file or database store.
- `cgPool`: Provided by WebLogic Workshop and used by WebLogic Workshop and WebLogic Integration for multiple functions.
- `portalPool`: Provided and used by WebLogic Portal for portal framework, services, and content management.

- Three data sources (Data Source)

- `cgJMSStore`: Provided and used by WebLogic Workshop for WebLogic JMS persistent file or database store.
- `p13n_trackingDataSource`: Provided and used by WebLogic Portal for behavior tracking.
- `p13nDataSource`: Provided and used by WebLogic Portal for personalization, sequence identifiers, and data synchronization.

- Four transactional data sources (Tx Data Source)

- `bpmArchDataSource:` Provided and used by WebLogic Integration for business process management archiving.
- `cgDataSource`: Provided and used by WebLogic Workshop for conversational persistence and WebLogic Integration document store.
- `cgDataSource-nonXA`: Provided and used by WebLogic Workshop for JMS control state management and third-party Compoze portlets. See a list of downloadable Compoze portlets at the following URL:

>     http://dev2dev.bea.com/products/wlportal/psc/Compoze.jsp

- `portalFrameworkPool`: Provided and used by WebLogic Portal for portal framework, services, and content management.

# Summary of Default JDBC Configurations for All Configuration Templates

The following table lists the default JDBC configuration settings for all of the WebLogic Platform prepackaged configuration templates.

Notes: The Basic WebLogic Server Domain template does not have preconfigured JDBC settings. The default domain configurations do not support XA.

Table 2 Default JDBC Configuration Template Settings (Non-XA)

Configuration Template | JDBC Resource Type | Resource Name | JDBC Configuration Setup
--- | --- | --- | ---
Basic WebLogic Workshop Domain | Database | workshop | PointBase
Connection Pool | cgJMSPool-nonXA | Connects to a PointBase database using a PointBase Type 4 Driver
Connection Pool | cgPool | Connects to a PointBase database using a PointBase Type 4 Driver
| Tx Data Source | cgDataSource | Bound to the cgPool connection pool
Tx Data Source | cgDataSource-nonXA | Bound to the cgJMSPool-nonXA connection pool
JMS Store | cgJMSStore | Bound to the cgJMSPool-nonXA connection pool
Basic WebLogic Integration Domain | Database | workshop | PointBase
Connection Pool | bpmArchPool | Connects to a PointBase database using a PointBase Type 4 Driver
Connection Pool | cgJMSPool-nonXA | Connects to a PointBase database using a PointBase Type 4 Driver
Connection Pool | cgPool | Connects to a PointBase database using a PointBase Type 4 Driver
Tx Data Source | bpmArchDataSource | Bound to the bpmArchPool connection pool
Tx Data Source | cgDataSource | Bound to the cgPool connection pool
Tx Data Source | cgDataSource-nonXA | Bound to the cgJMSPool-nonXA connection pool
JMS Store | cgJMSStore | Bound to the cgJMSPool-nonXA connection pool
Basic WebLogic Portal Domain | Database | workshop | PointBase
Connection Pool | cgJMSPool-nonXA | Connects to a PointBase database using a PointBase Type 4 Driver
Connection Pool | cgPool | Connects to a PointBase database using a PointBase Type 4 Driver
Connection Pool | portalPool | Connects to a PointBase database using a PointBase Type 4 Driver
| Data Source | p13n_trackingDataSource | Bound to the cgJMSPool-nonXA connection pool
Data Source | p13nDataSource | Bound to the cgJMSPool-nonXA connection pool
Tx Data Source | cgDataSource | Bound to the cgPool connection pool
Tx Data Source | cgDataSource-nonXA | Bound to the cgJMSPool-nonXA connection pool
Tx Data Source | portalFrameworkPool | Bound to the portalPool connection pool
JMS Store | cgJMSStore | Bound to the cgJMSPool-nonXA connection pool
Basic WebLogic Platform Domain | Database | workshop | PointBase
Connection Pool | bpmArchPool | Connects to a PointBase database using a PointBase Type 4 Driver
Connection Pool | cgJMSPool-nonXA | Connects to a PointBase database using a PointBase Type 4 Driver
Connection Pool | cgPool | Connects to a PointBase database using a PointBase Type 4 Driver
Connection Pool | portalPool | Connects to a PointBase database using a PointBase Type 4 Driver
Data Source | p13n_trackingDataSource | Bound to the cgJMSPool-nonXA connection pool
Data Source | p13nDataSource | Bound to the cgJMSPool-nonXA connection pool
Tx Data Source | bpmArchDataSource | Bound to the bpmArchPool connection pool
| Tx Data Source | cgDataSource | Bound to the cgPool connection pool
Tx Data Source | cgDataSource-nonXA | Bound to the cgJMSPool-nonXA connection pool
Tx Data Source | portalFrameworkPool | Bound to the portalPool connection pool
JMS Store | cgJMSStore | Bound to the cgJMSPool-nonXA connection pool
WebLogic Server Examples Domain | Database | demo | PointBase
Connection Pool | demoPool | Connects to a PointBase database using a PointBase Type 4 Driver
Connection Pool | demoXAPool | Connects to a PointBase database using a PointBase Type 4 Driver
Connection Pool | oraclePool | Connects to an Oracle database using an Oracle Thin DriverTx
Data Source | examples-dataSource-demoPool | Bound to the demoPool connection pool
Tx Data Source | examples-dataSource-demoXAPool | Bound to the demoXAPool connection pool
Tx Data Source | examples-dataSource-oracleXAPool | Bound to the oraclePool connection pool
JMS Store | exampleJDBCStore | Bound to the demoPool connection pool
Avitek Medical Records Sample Domain | Database | demo | PointBase
Connection Pool | MedRecPool-PointBase | Connects to a PointBase database using a PointBase Type 4 Driver
Connection Pool | MedRecXAPool-PointBase | Connects to a PointBase database using a PointBase Type 4 Driver
| Connection Pool | MedRecPool-Oracle | Connects to an Oracle database using an Oracle Thin Driver
Tx Data Source | MedRecTxDataSource | Bound to the MedRecXAPool-PointBase JDBC connection pool
JMS Store | MedRecJMSJDBCStore | Bound to the MedRecPool-PointBase JDBC connection pool