|
|
This section provides an overview of the strategies and procedures for upgrading Oracle WebLogic Portal to 10.3. You can upgrade directly to Portal 10.3 from the following WebLogic Portal applications:
You are not required to upgrade from WebLogic Portal 8.1 to 9.2, from 9.2 to 10.0/10.2, and then from 10.0/10.2 to 10.3
The following topics are covered in this chapter:
Some of tasks associated with a WebLogic Portal upgrade are performed by running the WebLogic Upgrade Wizard. The WebLogic Upgrade Wizard is described in Upgrading WebLogic Application Environments.
To clarify the different activities described by this document, a brief list of terms is included:
You can upgrade your WebLogic Portal 9.2, 9.2 MP1, 10.0, 10.0 MP1, and 10.2 applications to 10.3. The upgrade process involves upgrading your WebLogic Portal domain and applications. Upgrade the portal domain using the WebLogic Upgrade Wizard before you upgrade your portal application. The upgrade procedure is explained in Upgrading to WebLogic Portal 10.3.
The WebLogic Portal APIs have been maintained in WebLogic Portal 10.3 (except for the Commerce API, which was deprecated in 10.0), and most core formats for the database and file based assets have not changed. Where changes have been made, tools are provided to upgrade you to the new format, or provide manual changes where needed.
The 9.2 and 10.0/10.2 upgrades are performed on a .project file. After you upgrade to Portal 10.3, you cannot go back to a previous portal version. If you are upgrading from WebLogic Portal 9.2 or 10.0/10.2 to 10.3, the PointBase database version has already been upgraded.
You can choose one of the following methods to upgrade your Portal 9.2 or 10.0/10.2 application to 10.3:
| Tip: | You cannot upgrade an existing EAR application; only a project can be upgraded. |
For instructions on upgrading, see Upgrading from Portal 9.2 and 10.0/10.2 to 10.3.
WebLogic Portal enables you to upgrade your 8.1 SP4, SP5, and SP6 applications directly to 10.3. Most WebLogic Portal APIs have been maintained in WebLogic Portal 10.3 (except for the Commerce API, which was deprecated in 10.0), and most core formats for the database and file based assets have not changed. Where changes have been made, tools are provided to upgrade you to the new format, or provide manual changes where needed.
The upgrade process involves upgrading WebLogic Portal 8.1 portal applications and resources to WebLogic Portal 10.3. The 8.1 to 10.3 upgrade is performed on a .work file. 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 start scripts.
| Note: | When you upgrade from WebLogic Portal 8.1 to 10.3, your PointBase database is upgraded. |
For instructions on upgrading, see Upgrading from Portal 8.1 to 10.3.
The Domain Upgrader tool is responsible for adding or removing library modules, as necessary. It also modifies existing library module path information to point to the new product installation.
Removed libraries are deleted from the config.xml file. If you upgrade from 8.1.x to 10.3, the libraries are added to your config.xml file. If you upgrade from 9.2 or 10.0 to 10.3, the module version number changes to 10.3 in your config.xml file. If you upgrade from 10.0 MP1 to 10.3, the domain upgrader removes the maintenance-lib references.
This section outlines significant feature changes between older version of WebLogic Portal and the Portal 10.3 release.
| Note: | The following section applies only to an upgrade from WebLogic Portal 8.1 to 10.3. |
WebLogic Portal 8.1 included a WebLogic Portal-specific RDBMSAuthenticator. This has been deprecated. WebLogic Server 9.2 contains a new default SQLAuthenticator authentication provider, which contains an RDBMS user store for users and groups. Oracle recommends upgrading to the new WebLogic Server SQLAuthenticator.
When you run the WebLogic Upgrade Wizard to upgrade your domain, it determines whether or not you are using the RDBMSAuthenticator in your 8.1 installation. If the RDBMSAuthenticator is detected, the WebLogic Upgrade Wizard prompts you to choose whether to upgrade to the WebLogic SQLAuthenticator as your default authentication provider or continue to use your existing RDBMS user store. Replacing the existing authentication provider with the new WebLogic Server SQLAuthenticator upgrades all content, including personalization features. You can also choose to manually upgrade your personalization features to the Portal 10.3 RDBMS user store later.
Choose one of the following options when upgrading your user store:
config.xml file is also updated.
If you do not upgrade your user store during the domain upgrade process, you can perform a manual upgrade later. The script to upgrade from the WebLogic Portal-specific RDBMS Authenticator to the WebLogic SQL Authenticator is <WLPORTAL_HOME>/p13n/db/<dbms>/upgrade_fromdbmsauth_ towlssqlauth.sql.
For additional information, see Upgrading 8.1, 9.2, or 10.0 PointBase Databases.
| Note: | If you upgrade a WebLogic Portal 8.1 application to 10.3 and you use the UserProviderControl.createUser() class in the upgraded domain, you might see a javax.security.auth.login.LoginException error when a new user attempts to log into WebLogic Portal. This occurs because by default new users in a WebLogic Portal 10.3 domain are created in the SQLAuthenticator and not in a migrated authentication provider (which normally is configured with a JAAS flag set to REQUIRED). Since the WebLogic Portal domain Upgrade Wizard does not adjust your JAAS settings or remove your existing authentication provider, you must adjust the JAAS setting or delete the authentication provider (as appropriate) to avoid this exception. |
Events can target content to a desired audience.
| Note: | Events will fire for a content repository that was upgraded to 10.3 (unless you turned event tracking turned off at the repository level). Events can include repository configuration changes, as well as content additions, updates, and deletions to the repository. Events do not fire for content in an 8.1 or 9.2 repository that was not upgraded. Events are fired for content that is added, updated, or removed from that repository. |
If you created a separate behavior tracking database in version 8.1 or 9.2, upgrade it as described in Upgrading Separate 8.1 Behavior Tracking Databases.
A new Autonomy engine is installed with WebLogic Portal 9.2 and higher. It is disabled by default after upgrade so it can be properly configured before launching. Autonomy services that have been enabled in WebLogic Portal 8.1 are also disabled after upgrade. For information about installing and configuring search services, see the Integrating Search Guide.
In addition, the Autonomy APIs and the all content management APIs, including search, were deprecated in WebLogic Portal 9.2. If you want to continue to use the deprecated APIs, you need to manually add the older Autonomy APIs to your application, as described in Using 8.1 Search within a 10.0 Portal Application.
For information about upgrading WebLogic Portal 8.1 to the new version of Autonomy that is included with WebLogic Portal 10.3, see Upgrading Autonomy Search Services.
|