This section provides an example of creating a WebLogic Portal domain using an enterprise-quality database. For complete information about WebLogic Portal, see the WebLogic Portal documentation.
The following example explains the procedure to create a new ALINT domain. For more information about ALINT, see <<ALINT Landing Page>>
Please keep the following considerations in mind:
The MySQL JDBC driver is not fully XA compatible, therefore WebLogic Portal does not support using com.mysql.jdbc.jdbc2.optional.MysqlXADataSource. Data sources that require XA, and those that are XA capable, should use the com.myself.jdbc.Driver with the global-transactions-protocol LoggingLastResource instead.
Always define portalDataSourceAlwaysXA with an XA driver. For example, when configuring a domain for Oracle, use BEA’s Oracle Driver (Type 4 XA).
Always define p13nDataSource and cgDataSource-nonXA with a non-XA driver. For example, when configuring a domain for Oracle, use BEA’s Oracle Driver (Type 4) with these data sources.
For every other data source, a tab is displayed in the Configure JDBC Data Sources panel for Database Type and Driver configuration. The remaining data sources can be defined with either an XA or non-XA Driver, as required. When each data source is configured, click Test Connections to display the Test Data Source Connections window. Test each database source to verify database connectivity. Go back to the Configure JDBC Data Sources window to check and correct any database connectivity issue before proceeding.
Note: | If you selected the WebLogic Portal GroupSpace Framework check box in step 3, and you want to use a database other than PointBase for the GroupSpace Database, appsGroupSpaceDataSource will require data source configuration. For example, to use an Oracle database with the WebLogic Portal GroupSpace Framework configure appsGroupSpaceDataSource, to use BEA’s Oracle Driver (Type 4) and specify a user name and password that is unique for WebLogic Groupspace. For more information, see the
WebLogic Portal Database Administration Guide. Ensure that the database to which you want to test the connection is running. |
Also, if you selected WebLogic Portal GroupSpace Framework in Step 3, select the appsGroupSpaceDataSource in Available JDBC Data Sources, and then click Run Scripts to load the database objects for the WebLogic Portal GroupSpace Framework.
Note: | In the Results pane, verify that Database Load Successful is returned for each Run Script execution. Otherwise, correct the problem before proceeding. |
The following example explains the procedure to create a new WebLogic Portal domain that uses a database other than the default PointBase database. For additional information about configuring an Enterprise-Quality Database, see the WebLogic Portal Database Administration Guide.
Note: | The WebLogic Server check box is selected by default since it is a prerequisite for all WebLogic domains. |
Note: | The WebLogic Portal checkbox is selected by default since it is a prerequisite for WebLogic Portal GroupSpace. |
Please keep the following considerations in mind:
WL_HOME/portal/db/jdbc/README.txt
. This Readme file includes additional important information about database specific data source settings and XA JDBC Driver usage. It also describes a process for switching a default PointBase domain to a domain using an Enterprise Quality Database, without using the Configuration Wizard guide to modify each data source.
The MySQL JDBC driver is not fully XA compatible, therefore WebLogic Portal does not support using com.mysql.jdbc.jdbc2.optional.MysqlXADataSource
. Data sources that require XA, and those that are XA capable, should use the com.myself.jdbc.Driver
with the global-transactions-protocol LoggingLastResource
instead.
Always define portalDataSourceAlwaysXA
with an XA driver. For example, when configuring a domain for Oracle, use BEA’s Oracle Driver (Type 4 XA).
Always define p13nDataSource
and cgDataSource-nonXA
with a non-XA driver. For example, when configuring a domain for Oracle, use BEA’s Oracle Driver (Type 4) with these data sources.
For every other data source, a tab is displayed in the Configure JDBC Data Sources panel for Database Type and Driver configuration. The remaining data sources can be defined with either an XA or non-XA Driver, as required. When each data source is configured, click Test Connections to display the Test Data Source Connections window. Test each database source to verify database connectivity. Go back to the Configure JDBC Data Sources window to check and correct any database connectivity issue before proceeding.
Note: | If you selected the WebLogic Portal GroupSpace Framework check box in step 3, and you want to use a database other than PointBase for the GroupSpace Database, appsGroupSpaceDataSource will require data source configuration. For example, to use an Oracle database with the WebLogic Portal GroupSpace Framework configure appsGroupSpaceDataSource , to use BEA’s Oracle Driver (Type 4) and specify a user name and password that is unique for WebLogic Groupspace. For more information, see the
WebLogic Portal Database Administration Guide. Ensure that the database to which you want to test the connection is running. |
Also, if you selected WebLogic Portal GroupSpace Framework in Step 3, select the appsGroupSpaceDataSource
in Available JDBC Data Sources, and then click Run Scripts to load the database objects for the WebLogic Portal GroupSpace Framework.
Note: | In the Results pane, verify that Database Load Successful is returned for each Run Script execution. Otherwise, correct the problem before proceeding. |