| Oracle® Fusion Middleware Upgrade Guide for Oracle WebLogic Portal 10g Release 3 (10.3.7) E14253-06 |
|
|
View PDF |
| Oracle® Fusion Middleware Upgrade Guide for Oracle WebLogic Portal 10g Release 3 (10.3.7) E14253-06 |
|
|
View PDF |
This chapter describes upgrade tasks related to upgrading your WebLogic Portal product to 10.3.7.
This chapter contains the following sections:
Section 2.2, "Upgrading WebLogic Portal 10.2/10.3/10.3.2/10.3.4/10.3.5/10.3.6 to 10.3.7"
Section 2.3, "Upgrading from WebLogic Portal 10.3.6 to 10.3.7 Without Upgrading the Domain"
The WebLogic Upgrade Wizard executes database scripts to add and modify database tables for WebLogic Portal 10.3.7. Before you run the Upgrade Wizard to perform database upgrade tasks, you should perform full backups of all WebLogic Portal databases.
Note:
There have been no database schema changes after WebLogic Portal release 10.3.2.Oracle 8.1.7 (DBMS version and drivers) is no longer supported. Upgrade to either Oracle 11g or 12c by following your vendor's instructions before you upgrade to WebLogic Portal 10.3.7.
When you run the 10.3.7 Upgrade Wizard, the default is to automatically upgrade the main WebLogic Portal database. You can choose to defer database upgrades and do that manually. Certain database upgrade tasks, such as dropping deprecated database objects, upgrading separate behavior tracking databases, and upgrading separate content management databases require a manual database upgrade.
For additional information on how to perform database upgrade tasks manually, see Appendix A, "Performing Database Upgrade Tasks Manually".
Table 2-1 lists the .SQL files containing the Data Definition Language (DDL) for the database upgrade from WebLogic Portal 10.2/10.3/10.3.2/10.3.4/10.3.5/10.3.6 to 10.3.7. This information is for reference purpose only.
Table 2-1 Files Containing the DDL for Upgrading from 10.2/10.3/10.3.2/10.3.4/10.3.5
| Directory Name | File Name |
|---|---|
|
|
p13n102_create.tables.sql p13n102_drop.tables.sql |
|
|
pf102_create_tables.sql pf102_drop_tables.sql |
|
|
cmv102_create_tables.sql |
You can upgrade to WebLogic Portal 10.3.7 from the following WebLogic Portal versions: 10.2/10.3/10.3.2/10.3.4/10.3.5/10.3.6. The upgrade process requires you to upgrade your WebLogic Portal domain and portal applications. Before you upgrade, ensure that you back up your applications and data and remove any database objects that are not required.
Note:
if you are upgrading WebLogic Portal 10.3.6 to release 10.3.7, you can choose to upgrade only your portal applications and not the WebLogic Portal domain. For information, see Section 2.3, "Upgrading from WebLogic Portal 10.3.6 to 10.3.7 Without Upgrading the Domain."This section contains the following topics:
Before you upgrade your application environment, you should manually back up the domain and any external application and application database resources in a separate process. You should back up the relevant information on all machines in the domain. The wizard backs up only the domain directory and does not preserve file permissions.
You can clean up an existing database (any database prior to Portal 10.3.7) that contains unused and deprecated/removed WebLogic Commerce Services database objects.
Run the following scripts to remove the objects from the database:
<WLPORTAL_HOME>/portal/db/<DBMS>/wlcs_drop_fkeys.sql
<WLPORTAL_HOME>/portal/db/<DBMS>/wlcs_drop_tables.sql
This section provides upgrade instructions for WebLogic Portal database and metadata files.
As you prepare to upgrade your portal application, review the Oracle Enterprise Pack for Eclipse upgrade documentation available by choosing Help > Help Contents > Oracle Workshop for WebLogic User's Guide > Upgrading to Workshop for WebLogic 10.x. The Oracle Enterprise Pack for Eclipse documentation includes step-by-step instructions for using the Import Wizard, and detailed information about what happens during the upgrade process and any required manual pre- or post-upgrade tasks.
Perform the following steps to upgrade your portal domain:
Verify that the WebLogic domain is not running.
Upgrade the portal domain using the WebLogic Upgrade Wizard before you upgrade your portal application. To start the WebLogic Upgrade Wizard in graphical mode and upgrade a WebLogic domain on a Windows platform, run upgrade.cmd from the <WLPORTAL_HOME>\common\bin directory
Note:
Do not use the menu option Start > All Programs > Oracle Products > WebLogic Server 10.x > Tools > Domain Upgrade Wizard. This launches the WebLogic Server domain upgrade wizard.Note:
The WebLogic Upgrade Wizard is described in detail in Oracle Fusion Middleware Upgrade Guide for Oracle WebLogic Server.The wizard upgrades your portal, content management, and personalization database data.
In <WL_DOMAIN>/config/config.xml file, ensure that the entries correctly point to your upgraded WebLogic Portal domain path and that the release number is correct (10.3.7).
Note:
Weblogic Portal 10.3.7 uses WebLogic Server 10.3.6. All
config.xml entries must point to WebLogic Portal release 10.3.7. However the following two entries must point to WebLogic Server release 10.3.6:
"<domain-version>10.3.6.0</domain-version>"
"<configuration-version>10.3.6.0</configuration-version>"
For entries in config.xml, sample codes are shown below, which point to release 10.3.7.
content-management-cmis-base-web-lib
<library>
<name>content-management-cmis-base-web-lib#10.3.7@10.3.7</name>
<target>AdminServer</target>
<source-path><<WLPORTAL_HOME>>/../modules/com.bea.content.cmis.rest_10.3.7.0/content-management-cmis-base-web-lib.war</source-path>
<deployment-order>1</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
</library>
<library>
<name>content-management-cmis-base-web-lib#10.3.7@10.3.7.1</name>
<target>AdminServer</target>
<source-path>><<WLPORTAL_HOME>>/../modules/com.bea.content.cmis.rest_10.3.7.0/maintenance\1037\default\content-management-cmis-base-web-lib.war</source-path>
<deployment-order>1</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
</library>
content-management-cmis-rest-app-lib
<library>
<name>content-management-cmis-rest-app-lib#10.3.7@10.3.7</name>
<target>AdminServer</target>
<module-type>ear</module-type>
<source-path><<WLPORTAL_HOME>>/../modules/com.bea.content.cmis.rest_10.3.7.0/content-management-cmis-rest-app-lib.ear</source-path>
<security-dd-model>DDOnly</security-dd-model>
</library>
<library>
<name>content-management-cmis-rest-app-lib#10.3.7@10.3.7.1</name>
<target>AdminServer</target>
<source-path><<WLPORTAL_HOME>>/../modules/com.bea.content.cmis.rest_10.3.7.0/maintenance\1037\default\content-management-cmis-rest-app-lib.ear</source-path>
<deployment-order>1</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
</library>
content-management-cmis-rest-web-lib
<library>
<name>content-management-cmis-rest-web-lib#10.3.7@10.3.7</name>
<target>AdminServer</target>
<source-path><<WLPORTAL_HOME>>/../modules/com.bea.content.cmis.rest_10.3.7.0/content-management-cmis-rest-web-lib.war</source-path>
<deployment-order>1</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
</library>
<library>
<name>content-management-cmis-rest-web-lib#10.3.7@10.3.7.1</name>
<target>AdminServer</target>
<source-path><<WLPORTAL_HOME>>/../modules/com.bea.content.cmis.rest_10.3.7.0/maintenance\1037\default\content-management-cmis-rest-web-lib.war</source-path>
<deployment-order>1</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
</library>
content-management-faces-web-lib
<library>
<name>content-management-faces-web-lib#10.3.7@10.3.7</name>
<target>AdminServer</target>
<source-path><<WLPORTAL_HOME>>/../modules/com.bea.content.vcr_10.3.7.0/content-management-faces-web-lib.war</source-path>
<deployment-order>1</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
</library>
<library>
<name>content-management-faces-web-lib#10.3.7@10.3.7.1</name>
<target>AdminServer</target>
<source-path><<WLPORTAL_HOME>>/../modules/com.bea.content.vcr_10.3.7.0/maintenance\1037\default\content-management-faces-web-lib.war</source-path>
<deployment-order>1</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
</library>
content-management-web-lib
<library>
<name>content-management-web-lib#10.3.7@10.3.7</name>
<target>AdminServer</target>
<source-path><<WLPORTAL_HOME>>/../modules/com.bea.content.vcr_10.3.7.0/content-management-web-lib.war</source-path>
<deployment-order>1</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
</library>
<library>
<name>content-management-web-lib#10.3.7@10.3.7.1</name>
<target>AdminServer</target>
<source-path><<WLPORTAL_HOME>>/../modules/com.bea.content.vcr_10.3.7.0/maintenance\1037\default\content-management-web-lib.war</source-path>
<deployment-order>1</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
</library>
p13n-app-lib-base
<library>
<name>p13n-app-lib-base#10.3.7@10.3.7</name>
<target>AdminServer</target>
<source-path><<WLPORTAL_HOME>>/../modules/com.bea.p13n_10.3.7.0/p13n-app-lib-base.ear</source-path>
<deployment-order>1</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
</library>
<library>
<name>p13n-app-lib-base#10.3.7@10.3.7.1</name>
<target>AdminServer</target>
<source-path><<WLPORTAL_HOME>>/../modules/com.bea.p13n_10.3.7.0/maintenance\1037\default\p13n-app-lib-base.ear</source-path>
<deployment-order>1</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
</library>
p13n-core-web-lib
<library>
<name>p13n-core-web-lib#10.3.7@10.3.7</name>
<target>AdminServer</target>
<source-path><<WLPORTAL_HOME>>/../modules/com.bea.p13n_10.3.7.0/p13n-core-web-lib.war</source-path>
<deployment-order>1</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
</library>
<library>
<name>p13n-core-web-lib#10.3.7@10.3.7.1</name>
<target>AdminServer</target>
<source-path><<WLPORTAL_HOME>>/../modules/com.bea.p13n_10.3.7.0/maintenance\1037\default\p13n-core-web-lib.war</source-path>
<deployment-order>1</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
</library>
vcr-app-lib
<library>
<name>vcr-app-lib#10.3.7@10.3.7</name>
<target>AdminServer</target>
<source-path><<WLPORTAL_HOME>>/../modules/com.bea.content.vcr_10.3.7.0/vcr-app-lib.ear</source-path>
<deployment-order>1</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
</library>
<library>
<name>vcr-app-lib#10.3.7@10.3.7.1</name>
<target>AdminServer</target>
<source-path><<WLPORTAL_HOME>>/../modules/com.bea.content.vcr_10.3.7.0/maintenance\1037\default\vcr-app-lib.ear</source-path>
<deployment-order>1</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
</library>
Tip:
If you customized how you set the domain in your start scripts, your changes will be overwritten when you run the WebLogic Portal 10.3.7 start scripts. You should manually copy any start script (and setDomainEnv.cmd/sh) modifications you made and want to preserve in the upgraded domain.Note:
If you are using the RDBMS Security Store feature, as part of the upgrade process, the DDL automatically creates the RDBMS Security Store tables in the schema for which the p13nDatasource is configured. If a portal domain administrator wishes to use or configure a database schema other than the schema for which the p13nDatasource is configured, he or she must manually run the following script to create the RDBMS Security Store tables for that schema:<WLPORTAL_HOME>/p13n/db/<database_vendor>/rdbms_security_store_create_tables.sql
For more information on the RDBMS Security Store tables, see "RDBMS Security Store Tables" in the Oracle Fusion Middleware Database Administration Guide for Oracle WebLogic Portal.
The upgrade process involves upgrading WebLogic Portal applications and resources to WebLogic Portal 10.3.7. Upgrades are performed on the Eclipse project folder. After you upgrade to WebLogic Portal 10.3.7, you cannot go back to a previous portal version.
Choose one of the following ways to upgrade your portal application to 10.3.7:
Open an existing portal application as a workspace in Eclipse.
Import an existing exploded project into Eclipse.
Import an archived project file into Eclipse.
Tip:
You cannot upgrade an existing EAR application; only a project can be upgraded.You can choose to point your upgraded application to a new or upgraded 10.3.7 domain.
Perform the following steps to upgrade a WebLogic Portal application to release 10.3.7:
In Oracle Enterprise Pack for Eclipse, ensure that Project > Build Automatically is enabled to resolve any build errors. By default, it is enabled.
As needed, upgrade individual applications as described in Oracle Fusion Middleware Production Operations Guide for Oracle WebLogic Portal.
Weblogic Portal 10.3.7 uses WebLogic Server 10.3.6, and the core format of the database is same as Weblogic Portal 10.3.6. When upgrading from Weblogic Portal 10.3.6, you can optionally choose to create a new WebLogic domain and upgrade only WebLogic Portal applications without upgrading the Weblogic domain or database.
Perform the following steps to upgrade WebLogic Portal 10.3.6 to 10.3.7 without upgrading the domain:
Install WebLogic Portal 10.3.7. For more information, see Installing WebLogic Portal.
Back up the database associated with WebLogic Portal 10.3.6. For more information, see Section 2.2.1, "Backing Up Your Applications and Data."
Create a new WebLogic domain using WebLogic Portal 10.3.7. For more information, see WebLogic Domain Configuration Wizard.
Note:
While creating the WebLogic domain, do not execute database scripts, but you can specify the database details associated with Weblogic Portal 10.3.6 in the Configure JDBC Data Sources page.If you did not specify database details in the previous step, configure the newly created WebLogic domain for the database and schema associated with WebLogic Portal 10.3.6 using the WebLogic console. For information, see JDBC Data Source: Configuration: Connection Pool.
Import the project into a new workspace using WebLogic Portal 10.3.7. For more information, see Section 2.2.4, "Upgrading WebLogic Portal Applications."
Point your upgraded application to a new domain.
Log in to WebLogic Portal 10.3.7 and verify your applications.
|
 Copyright © 2010, 2016, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|