README for the IBM WebSphere Portal Version 4.1 Migration Pack

Last update: August 8, 2002

This document contains information about the Migration Pack for the IBM WebSphere Portal Multiplatforms Version 4.1.

• Prerequisites
• Hints and tips
• Space requirements
• Installing the Migration Pack
• Uninstalling the Migration Pack
• Finding additional information
• Trademarks

Prerequisites

To install the Migration Pack, the following level of WebSphere Portal Version 4.1 must already be installed:

• WebSphere Portal Enable Version 4.1.1

To determine whether this prerequisite level is installed, view the Welcome page for WebSphere Portal.

If your administrator has removed the Welcome page for WebSphere Portal, view the following file:

wps_root\wps.properties

where wps_root is the WebSphere Portal root directory. In the file locate the line that starts with buildnumber. This line shows which version of WebSphere Portal is installed.

Space requirements

The Migration Pack installation program requires approximately 10 MB of temporary space. After it is installed, the Migration Pack increases the IBM WebSphere Portal installation and runtime footprints by a small amount.

Hints and tips

• This Migration Pack upgrades WebSphere Portal Enable V4.1.1 to WebSphere Portal Enable V4.1.2. This Migration Pack does not upgrade WebSphere Portal Enable V4.1.1 to any other release of WebSphere Portal.
• If you plan to apply the Migration Pack to a cluster installation of WebSphere Portal Enable Version 4.1.1, contact the WebSphere Portal support team for help before you apply this Migration Pack.
• This Migration Pack can only be applied on WebSphere Application Server Advanced Edition, not on Single Server Edition.
• The Migration Pack does not define translated titles for existing places and pages. For example, the default place will still appear as Home, even if a non-English language is selected. After the Migration Pack has been installed, you can use the Manage Places and Manage Pages portlets to define translated titles for places and pages.
• No new portlets are deployed. If you want to use the new portlets which come with this Migration Pack, use the update function of the Manage Portlet Applications portlet to update the portlet code. New portlet war files for the standard administration portlets are located in:

  wps_root\fixpacks\1\DeployablePortlets

  The Migration Pack provides a script for the portal XML configuration utility that can be used to update all administrative portlets in one step after you have installed the Migration Pack.

Installing the Migration Pack

1. If WebSphere Application Server Security is enabled on your system, the Migration Pack installation prompts you several times for a user ID and password. To prevent this security prompt, you can temporarily set the login properties in the sas.client.props file:
   1. Open was_root\properties\sas.client.props for editing.
   2. Set the following properties:

      com.ibm.CORBA.loginSource=properties

      com.ibm.CORBA.loginUserid=your_admin_userid

      com.ibm.CORBA.loginPassword=your_admin_password

      where your_admin_userid and your_admin_password are the user ID and password of the bind user that you use to connect to the WebSphere Application Server admin console.

   3. Save your changes.
2. Obtain the file WPS412_MP.tar or WPS412_MP.zip from the product Web site:

   http://www.ibm.com/software/webservers/portal/

   Both archives have the same content. Download and unpack the file to a temporary directory on the system where WebSphere Portal is installed.
3. Make sure that no users are accessing the portal. Take the Portal Server offline, if necessary. Viewing portal pages and configuring the portal during the Migration Pack installation can cause unpredictable results and might leave your portal in an unusable state.
4. At a system command prompt, change to the directory where the Migration Pack was downloaded.
5. Make sure that your CLASSPATH contains the library (JAR or ZIP file) for your JDBC driver. For example, if you are using DB2 on AIX, Linux or Solaris, make sure that you use the db2java.zip for JDBC2 which is located in the sqllib/java12 subdirectory of your DB2 installation. You do this by executing the following commands:

   . /db2_home/sqllib/db2profile

   export CLASSPATH=db2_home/sqllib/java12/db2java.zip:$CLASSPATH

6. Make sure that WebSphere Application Server is running.
7. To install the Migration Pack, run the appropriate installation script:

   For AIX, Linux and Solaris systems:	sh fp1.sh
   For Windows systems:	fp1.bat

8. Follow the instructions provided by the installation program.

   Notes:

   • Canceling the Migration Pack installation after it has started to copy files can leave your portal in an unusable state. The canceled installation will not revert the portal to the state before the Migration Pack installation. To revert to the previous state, you must complete the Migration Pack installation and then uninstall the Migration Pack as described below. Click the Cancel button to end the installation only if the process hangs.
   • During the database initialization on AIX, Linux, or Solaris, a duplicateKeyError might occur. This error has no impact on WebSphere Portal and can be ignored.
9. To update all administrative portlets, perform the following steps:
   1. Change to the directory wps_root\fixpacks\1
   2. On Windows systems, execute the command

      ..\..\bin\xmlaccess UpdatePortlets.xml admin-id:password portal-host/wps/config

      On AIX, Linux and Solaris systems, execute the command

      sh ../../bin/xmlaccess.sh UpdatePortlets.xml admin-id:password portal-host/wps/config

      where admin-id:password are the User ID and password of the portal administrator and portal-host/wps are the host name and base URI that you have configured for you portal during installation.

10. If you set the login properties in step 1, you should remove these after installation. Do the following:
    1. Open was_root\properties\sas.client.props for editing.
    2. Set the following properties:

       com.ibm.CORBA.loginSource=prompt

       com.ibm.CORBA.loginUserid=

       com.ibm.CORBA.loginPassword=

    3. Save your changes.

Uninstalling the Migration Pack

If you deployed any new portlets after the Migration Pack was installed, you should remove those portlets before you uninstall the Migration Pack. The new portlets may require fixes and functions that were introduced with the Migration Pack and might not work with the previous level portal.

1. To restore all administrative portlets, perform the following steps:
   1. Change to the directory wps_root\fixpacks\1
   2. On Windows systems, execute the command

      ..\..\bin\xmlaccess RestorePortlets.xml admin-id:password portal-host/wps/config

      On AIX, Linux and Solaris systems, execute the command

      sh ../../bin/xmlaccess.sh RestorePortlets.xml admin-id:password portal-host/wps/config

      where admin-id:password are the user id and password of the portal administrator and portal-host/wps are the host name and base URI that you have configured for you portal during installation

2. After you restored the portlets to their old state, the portlets display content in English only. However, they still have translated titles. To avoid mixing English content with translated titles, delete all non-English titles for the portlets manually in the Manage Portlets portlet.
3. Make sure that WebSphere Application Server is running.
4. Make sure that your CLASSPATH contains the library (JAR or ZIP file) for your JDBC driver. For example, if you are using DB2 on AIX, Linux or Solaris, make sure that you use the db2java.zip for JDBC2 which is located in the sqllib/java12 subdirectory of your DB2 installation. You do this by executing the following commands:

   . /db2_home/sqllib/db2profile

   export CLASSPATH=db2_home/sqllib/java12/db2java.zip:$CLASSPATH

5. Change to the root directory for WebSphere Portal on your system.
6. To uninstall the Migration Pack, run the appropriate installation script:

   For AIX, Linux and Solaris systems:	sh remove-fp1.sh
   For Windows systems:	remove-fp1.bat

Finding additional information

For information about support and service, and for the latest fixes, visit the WebSphere Portal Web site:

http://www.ibm.com/software/webservers/portal/

For the WebSphere Portal Version 4.1 product documentation, see the copy of the InfoCenter that was installed with the Migration Pack or see the copy on the Web site library page.

Trademarks

IBM and WebSphere are trademarks or registered trademarks of IBM Corporation.

Microsoft, Windows, Windows NT, Windows 2000, Windows XP are registered trademarks of Microsoft Corporation.

Sun, Sun Microsystems, the Sun logo, Java and all Java-based trademarks and logos are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States and other countries.

Other company, product, and service names may be trademarks or service marks of others.

***************************************************************
(c) Copyright 2001, 2002 International Business Machines Corp.
    All rights reserved.
***************************************************************