Migrating From WebLogic Portal 7.0 to WebLogic Portal 7.0 Service Packs

e-docs > WebLogic Platform > WebLogic Portal > Migration Guide > Migrating From WebLogic Portal 7.0 to WebLogic Portal 7.0 Service Packs

Migration Guide

Migrating From WebLogic Portal 7.0 to WebLogic Portal 7.0 Service Packs

Migrating to Service Pack 7

BEA WebLogic Portal 7.0 Service Pack 7 (SP7) WebLogic Portal 7.0 compliant with JDK 1.4.2. No new functionality or major behavior changes were introduced.

It also incorporates service pack upgrades for all WebLogic Platform 7.0 components (WebLogic Server, WebLogic Workshop, WebLogic Integration, WebLogic Portal and WebLogic JRockit). WebLogic Platform 7.0 SP7 can be used to update all WebLogic Platform 7.0 components.

When migrating an application from 7.0, 7.0 SP1, 7.0 SP2 to 7.0 SP4, 7.0 SP4 to 7.0 SP5, 7.0 SP5 to 7.0 SP6, or 7.0 SP6 to 7.0 SP7, follow the instructions for migrating a WebLogic Portal domain at http://download.oracle.com/docs/cd/E13196_01/platform/docs70/relnotes/relnotes.html#migration.

Migrating to Service Pack 6

BEA WebLogic Platform 7.0 Service Pack 6 (SP6) incorporates service pack upgrades for all WebLogic Platform 7.0 components (WebLogic Server, WebLogic Workshop, WebLogic Integration, WebLogic Portal and WebLogic JRockit).

WebLogic Platform 7.0 SP6 can be used to update all WebLogic Platform 7.0 components.

When migrating an application from 7.0, 7.0 SP1, 7.0 SP2 to 7.0 SP4, 7.0 SP4 to 7.0 SP5, or 7.0 SP5 to 7.0 SP6, follow the instructions for migrating a WLP domain at http://download.oracle.com/docs/cd/E13196_01/platform/docs70/relnotes/relnotes.html#migration.

Migrating to Service Pack 4

BEA WebLogic Platform 7.0 Service Pack 4 (SP4) incorporates service pack upgrades for all WebLogic Platform 7.0 components (WebLogic Server, WebLogic Workshop, WebLogic Integration, WebLogic Portal and WebLogic JRockit). BEA WebLogic Platform 7.0 SP4 is the first full service pack release since WebLogic Platform 7.0 SP2.

Note: A separate 7.0 SP3 release of WebLogic Server/WebLogic Workshop is available to WebLogic Server and WebLogic Workshop support customers only. A separate WebLogic JRockit 7.0 SP3 release is also available to customers using WebLogic Server 7.0 SP3. The WebLogic Server 7.0 SP3 upgrade installers do not allow SP3 to be applied to an existing WebLogic Integration 7.0, WebLogic Portal 7.0 or full WebLogic Platform 7.0 installation.

WebLogic Platform 7.0 SP4 can be used to update all WebLogic Platform 7.0 components.

When migrating an application from 7.0, 7.0 SP1, or 7.0 SP2 to 7.0 SP4, follow the instructions for migrating a WLP domain at http://download.oracle.com/docs/cd/E13196_01/platform/docs70/relnotes/relnotes.html#migration.

Migrating to Service Pack 2

When migrating your 7.0 application to 7.0 SP1, or when migrating your 7.0 or 7.0 SP1 application to 7.0 SP2, follow the instructions for migrating a WLP Domain at http://download.oracle.com/docs/cd/E13196_01/platform/docs70/relnotes/relnotes.html#migration.

Migrating to Service Pack 1

The Configuration Wizard (introduced in WebLogic Platform 7.0) allows you to create new domains quickly and easily. If you created domains using the Configuration Wizard in WebLogic Platform 7.0, you need to migrate those domains for use with WebLogic Platform 7.0 Service Pack 1.

For most domains, migration from WebLogic Portal 7.0 to WebLogic Portal 7.0 Service Pack 1 is a three-step process:

Step 1: Upgrade Product JAR Files in the domain directory. A migration script is provided for this purpose.

Note: You can also revert a domain to its pre-migration state.
Step 2: Update the Domain to Support Service Pack 1 Changes. Depending on the domain template used to generate the domain, you may need to add or modify existing scripts or files.
Step 3: Update Startup Scripts and Configuration Files to Reference New BEA_HOME Directory Location (Non-Upgrades Only). Perform this step only if you installed WebLogic Platform 7.0 Service Pack 1 into a new directory.

Note: If you upgraded your existing WebLogic Platform 7.0 installation, you can skip this step.

These steps are explained in detail in the following sections. You will need to repeat this process for each domain that you want to migrate.

Note: This section decribes how to migrate domains specific to WebLogic Portal. For information about migrating other WebLogic Platform domains, see "Migrating Domains Created Using the Configuration Wizard" in the WebLogic Platform 7.0 Service Pack 1 Release Notes at the following URL:

http://download.oracle.com/docs/cd/E13196_01/platform/docs70/relnotes/relnotes.html#migration

Step 1: Upgrade Product JAR Files

To upgrade product JAR files for a domain that you generated using the Configuration Wizard to Service Pack 1, navigate to the BEA_HOME\weblogic700\server\bin directory and execute one of the following commands:

Windows: migrate.cmd domain mode
UNIX: migrate.sh domain mode

Note: You will be prompted to press any key to start processing.

The following table defines the command-line arguments.

Argument

Description

domain

Full pathname of the domain directory.

mode

Migration mode. The mode can be set to one of the following values:

upgrade: Upgrade the product JAR files in the domain directory, as required. The original product JAR files are saved as *.jar.orig. If the timestamp of an existing product JAR file is more recent than the timestamp on the corresponding SP1 installation product JAR file, the file is skipped. This is the default mode.

revert: Reverts a domain that was migrated earlier using the backup files (*.jar.orig) generated. If no *.jar.orig files exist, the command is ignored.

Argument	Description
domain	Full pathname of the domain directory.
mode	Migration mode. The mode can be set to one of the following values: upgrade: Upgrade the product JAR files in the domain directory, as required. The original product JAR files are saved as .jar.orig. If the timestamp of an existing product JAR file is more recent than the timestamp on the corresponding SP1 installation product JAR file, the file is skipped. This is the default mode. revert: Reverts a domain that was migrated earlier using the backup files (.jar.orig) generated. If no *.jar.orig files exist, the command is ignored.

For example, the following command upgrades a domain called mydomain located in the default user projects directory (BEA_HOME\user_projects):

Windows: migrate.cmd c:\bea\user_projects\mydomain upgrade
UNIX: migrate.sh c:/bea/user_projects/mydomain upgrade

The following command reverts the changes made to mydomain during the migration:

Windows: migrate.cmd c:\bea\user_projects\mydomain revert
UNIX: migrate.sh c:/bea/user_projects/mydomain revert

Step 2: Update the Domain to Support Service Pack 1 Changes

To update a domain that is based on the WLP Domain template to support WebLogic Platform 7.0 Service Pack 1, perform the following steps.

Note: Before adding or modifying any files, it is recommended that you backup the original files.

In the web.xml file for the tools Web application (located, by default, in the BEA_HOME\user_projects\domain\beaApps\portalApp\tools\WEB-INF directory), locate the Customer Profile and Order Pages security constraint and define the resources to which the security constraint applies using the <url-pattern> element.
The following sample excerpt from the web.xml file shows the required updates in bold:
<security-constraint>

<web-resource-collection>
<web-resource-name>
Customer Profile and Order Pages
</web-resource-name>
<description>
Customer Profile and Order Pages
</description>

<url-pattern>/tools/*</url-pattern>
<url-pattern>/repository/*</url-pattern>
<url-pattern>/security/*</url-pattern>
<http-method>GET</http-method>
<http-method>POST</http-method>
</web-resource-collection>
</security-constraint>
Note: WebLogic Server validates each web-resource-collection element within a security-constraint element to ensure that it contains at least one URL pattern. If you have other Web applications in your domain, verify that all web-resource-collection elements contain at least one URL pattern, appropriate for the security constraint.

Copy the following files from the BEA_HOME\weblogic700\common\templates\domains\shared\bea\portal\webapps\tools\tools directory to the tools directory of your tools Web applications. Be careful not to overwrite any files that you have customized.

catalog\category_add_remove_items.jsp
catalog\item_property_edit.jsp
catalog\item_property_edit_mr.jsp
catalog\item_property_edit_mu.jsp
catalog\item_property_edit_sr.jsp
catalog\item_property_edit_su.jsp
catalog\item_search.jsp
usermgmt\groupuser_property_edit_mr.jsp
usermgmt\groupuser_property_edit_mu.jsp
usermgmt\groupuser_property_edit_sr.jsp
usermgmt\groupuser_property_edit_su.jsp
usermgmt\group_add_remove_users.jsp
usermgmt\group_edit.jsp
usermgmt\group_scope_property.jsp
usermgmt\user_create.jsp
usermgmt\user_edit_info.jsp
usermgmt\user_scope_property.jsp

If you have created a portal Web application in your domain, you need to perform the following steps for each application:

Copy the following files from the BEA_HOME\weblogic700\common\templates\webapps\portal\baseportal\j2ee\framework directory to the framework directory of your portal Web application. Be careful not to overwrite any files that may have been created using one of these filenames.

edit_titlebar.properties
error\configurationerror.properties
error\footer.inc
error\header.inc
error\header.properties
error\missingformfield.properties
error\parameters.properties
error\pipeline.properties
error\request.properties
error\runtimeerror.properties
hnav_bar.properties
maximize_titlebar.properties
minimize_titlebar.properties
normal_titlebar.properties
security\help.properties
security\meta.inc
vnav_bar.properties

Update the following JSP files in the framework directory of your portal Web application using the corresponding files in the BEA_HOME\weblogic700\common\templates\webapps\portal\baseportal\j2ee\framework directory as a guide for comparison. Because you may have modified the JSP files to customize your portal, it is not recommended that you overwrite the existing files unless you are certain that they have not been customized.

edit_titlebar.inc
error\configurationerror.jsp
error\error.jsp
error\missingformfield.jsp
error\parameters.jsp
error\pipeline.jsp
error\request.jsp
error\runtimeerror.jsp
error\sessiontimeout.jsp
error\sessiontimeout.properties
floated_portlet.jsp
hnav_bar.jsp
maximize_titlebar.inc
minimize_titlebar.inc
normal_titlebar.inc
security\help.jsp
security\login_header.inc
security\need_group.jsp
security\new_user.jsp
security\set_password.jsp
tools\header.jsp
tools\header.properties
tools\portal_prefs.jsp
vnav_bar.jsp

Copy the following files from the BEA_HOME\weblogic700\common\templates\webapps\portal\baseportal\j2ee\WEB-INF\lib directory to the WEB-INF\lib directory of your portal Web applications. Be careful not to overwrite any files that you have customized.

ent_taglib.jar
es_taglib.jar
i18n_taglib.jar
lic_taglib.jar
p13n_servlet.jar
portal_servlet.jar
portal_taglib.jar
portlet_taglib.jar
ren_taglib.jar
res_taglib.jar
um_taglib.jar
util_taglib.jar
visitor_taglib.jar
webflow_servlet.jar
webflow_taglib.jar
weblogic-tags.jar

Step 3: Update Startup Scripts and Configuration Files to Reference New BEA_HOME Directory Location (Non-Upgrades Only)

Note: This step is only required if you installed WebLogic Platform 7.0 Service Pack 1 into a new directory that is separate from the WebLogic Platform 7.0 installation. If you upgraded your existing WebLogic Platform 7.0 installation, you can skip this step.

The domain startup scripts (such as, startWebLogic) and configuration files (such as config.xml) define the full pathnames to files within the BEA_HOME directory. You need to search for and update these full pathnames to reference the new BEA_HOME directory location. In addition, you must update any custom scripts, such as build scripts, that define full pathnames to the files within the BEA_HOME directory to reflect the new BEA_HOME location.

Note: Many startup scripts set environment variables in your current shell, including variables that reference your BEA_HOME directory. After updating the BEA_HOME references in script files, you should open a new shell to ensure that the latest environment settings are used.