|
|
This section provides an overview of the strategies and procedures for upgrading BEA WebLogic Portal® 8.1 SP4, SP5, and SP6 applications to WebLogic Portal 9.2. The following topics are discussed:
Much of the WebLogic Portal upgrade is performed by running the WebLogic Upgrade Wizard. The WebLogic Upgrade Wizard described in Upgrading WebLogic Application Environments.
To clarify the different activities described by this document, a brief list of terms is included:
WebLogic Portal enables you to easily upgrade your 8.1 SP4, SP5, and SP6 applications to 9.2. With the exceptions noted in this guide, WebLogic Portal APIs have been maintained in WebLogic Portal 9.2, and most core formats for the database and file based assets have not changed. Where changes have been made, tools are provide to upgrade you to the new format, or make you aware of manual changes where those are needed.
The upgrade process involves upgrading WebLogic Portal 8.1 SP4, SP5, and SP6 portal applications and resources to WebLogic Portal 9.2. The high level steps in the upgrade process are:
This section outlines significant feature changes between the WebLogic Portal 8.1 and the WebLogic 9.2 release.
Webflows and pipelines were deprecated in Version 8.1 and are no longer supported; you can use page flows in place of these deprecated features.
Previous releases of WebLogic Portal 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. BEA 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:
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 WEBLOGIC_HOME/common/p13n/db/dbms/upgrade_fromdbmsauth_towlssqlauth.sql
For additional information, see Upgrading PointBase Databases.
| Note: | If you upgrade a WebLogic Portal 8.1 application to 9.2 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 9.2 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 change the JAAS setting or delete the authentication provider (as appropriate) to avoid this exception. |
Interaction Management enables you to develop, manage, and measure personalized portal applications. Personalization and Campaign management combine to form the foundation of Interaction Management. These functions help you target content to a desired audience.
When you run the BEA WebLogic Upgrade Wizard, the wizard upgrades your WebLogic Portal 8.1 interaction features, including Content Selectors, Placeholders, Segments, and Campaigns.
When you run the BEA WebLogic Upgrade Wizard and it detects your Portal 8.1 installation, you can select the Upgrade RDBMSAuthenticator option, as described in Security. Selecting this option replaces the existing authentication provider with the new WebLogic Server SQLAuthenticator and upgrades all content, including personalization features. You can also choose to manually upgrade your personalization features to the Portal 9.2 RDBMS user store later.
| Note: | Events will fire for a content repository that was upgraded to 9.2 (unless you turned event tracking off at the repository level). Events can include repository configuration changes, as well as content additions, updates, and deletions to the repository. Events will not fire for content in an 8.1 repository that was not upgraded. Events will be fired for content that is added, updated, or removed from that repository. |
If you created a separate behavior tracking database in version 8.1, upgrade it as described in Upgrading Separate Behavior Tracking Databases.
The WebLogic Portal 8.1 content management API has been deprecated and a new content API is introduced for WebLogic Portal 9.2. Although the 8.1 API still functions within 9.2, all new portal development should use the 9.2 API. For more information about the new content API, see the WebLogic Portal JavaDoc.
The 7.0 ContentManager and DocumentProvider APIs were deprecated in WebLogic Portal 8.1. For WebLogic Portal 9.2, they have been completely removed and are no longer supported. It is recommended that you use the 9.2 API.
In addition, the Service Provider Interface (SPI) that is used to connect third-party repositories to the Virtual Content Repository has been extended to allow SPI users to take advantage of new features and the new content API. For more information about the new SPI, see WebLogic Portal JavaDoc.
For a complete list of all the deprecated classes in the API, see WebLogic Portal JavaDoc.
A new Autonomy engine is installed with WebLogic Portal 9.2. 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 WebLogic Portal Search Guide.
In addition, the Autonomy APIs and the all content management APIs, including search, have been 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 9.2 Portal Application.
For information about upgrading to the new version of Autonomy that is included with WebLogic Portal 9.2, see Upgrading Autonomy Search Services.
|