|
|
This section provides an overview of the strategies and procedures for upgrading BEA WebLogic Portal to 10.0. You can upgrade from WebLogic Portal 9.2 and 9.2 Maintenance Packs (MP1 and MP2) applications to WebLogic Portal 10.0. You can also upgrade from WebLogic Portal 8.1 SP4, SP5, and SP6 applications directly to 10.0.
The following topics are covered in this chapter:
Much of the WebLogic Portal upgrade is 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 directly upgrade to WebLogic Portal 10.0 MP1 from the following versions:
The upgrade process involves upgrading portal applications and resources to WebLogic Portal 10.0 MP1.
| Note: | If you upgrade WebLogic Portal 10.0 installation to 10.0 MP1 using the upgrade installer, ensure that you run workshop4WP.exe with -clean and -initialize options after the upgrade. If you do not start Workshop with -clean and -initialize options after the upgrade, you will not be able to deploy web service applications. |
| Note: | Database upgrade from WebLogic Portal 10.0 to 10.0 MP1 is not required because the database structure is the same for 10.0 and 10.0 MP1. |
The high-level steps in the upgrade process include the following:
| Tip: | Ensure that you back up the customized domain start scripts before upgrading the domain to WebLogic Portal 10.0 MP1, because the changes will be overwritten when you run the WebLogic Portal 10.0 MP1 start scripts. You should manually copy any start script (and setDomainEnv.cmd/sh) modifications you made and want to preserve in the upgraded domain. |
You can easily upgrade your WebLogic Portal 9.2 and 9.2.x applications to 10.0. The WebLogic Portal APIs have been maintained in WebLogic Portal 10.0 (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 9.2 or 9.2.x portal applications and resources to WebLogic Portal 10.0.
The high-level steps in the upgrade process include the following:
| 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.0 start scripts. You should manually copy any start script (and setDomainEnv.cmd/sh) modifications you made and want to preserve in the upgraded domain. |
WebLogic Portal enables you to upgrade your 8.1 SP4, SP5, and SP6 applications directly to 10.0. Most WebLogic Portal APIs have been maintained in WebLogic Portal 10.0 (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 SP4, SP5, and SP6 portal applications and resources to WebLogic Portal 10.0. You are not required to upgrade from WebLogic Portal 8.1 to 9.2, and then to 10.0.
The high-level steps in the upgrade process include the following:
| 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.0 start scripts. |
If you are upgrading from WebLogic Portal 8.1 to 10.0, the new libraries listed in Table 1 -1 are added to your config.xml file. Removed libraries are deleted from the config.xml file. If you are upgrading from WebLogic Portal 9.2 or 9.2 MP1 to 10.0, the new libraries are added and the module version number changes to 10.0 in your config.xml file.
Table 1 -1 lists the library modules that are new or have changed in WebLogic 10.0.
WebLogic Portal 10.0 supports binary compatibility of Portal 9.2 applications deployed into a WebLogic Portal 10.0 domain (upgraded or new domain). Any references to pre-10.0 Workshop library modules will automatically be replaced by references to new Workshop libraries through the /<BEAHOME>/wlserver_10.0/common/deployable-libraries/wlp-compat/ directory.
This section outlines significant feature changes between the WebLogic Portal 8.1 or 9.2 and the WebLogic Portal 10.0 release.
| Note: | The following section applies only to an upgrade from WebLogic Portal 8.1 to 10.0. |
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. 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 8.1 and 9.2 PointBase Databases.
| Note: | If you upgrade a WebLogic Portal 8.1 application to 10.0 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.0 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. |
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 or 9.2 interaction features, including Content Selectors, Placeholders, Segments, and Campaigns.
When you run the BEA WebLogic Upgrade Wizard and it detects your Portal 8.1 or 9.2 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 10.0 RDBMS user store later.
| Note: | Events will fire for a content repository that was upgraded to 10.0 (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 will not fire for content in an 8.1 or 9.2 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 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 WebLogic Portal 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.0, see Upgrading Autonomy Search Services.
|