Prepare a source portal on a V6.1 application server

To ensure proper migration from WebSphere Portal v6.1.x, clean up that environment and apply the appropriate interim fixes.

  1. If the earlier portal server is configured to use DB2®, ensure that you are running the minimum required level – either V9.1 with Fix Pack 6 or later, or V9.5 with Fix Pack 5 or later.

      DB2 Fix packs are available for download from IBM DB2 Support.

  2. Back up the databases and the entire directory structure for the earlier portal server installation.

  3. Ensure that the existing portal environment is at the required service level for migration.

  4. To ensure that wkplc_comp.properties contains the correct information, run the following commands:

    • Windows™:

        ConfigEngine.bat validate-database-connection -DTransferDomainList=release,jcr

        ConfigEngine.bat connect-database -DTransferDomainList=release,jcr

    • UNIX™:

        ConfigEngine.sh validate-database-connection -DTransferDomainList=release,jcr

        ConfigEngine.sh connect-database -DTransferDomainList=release,jcr

    • i:

        ConfigEngine.sh validate-database-connection -DTransferDomainList=release,jcr

        ConfigEngine.sh connect-database -DTransferDomainList=release,jcr

      If you plan to migrate IBM Web Content Manager data, complete the remaining steps.

  5. On the source portal server, remove locks on all Web content items:

    1. Go to the Administration view.

    2. Go to Portal Content -> Web Content Libraries.

    3. Click View Locked Items.

    4. Select all items and then click Unlock.

  6. If you are migrating from v6.1.5, manually update the getNlsStrings.js file in Web Content Manager to work correctly with the v7.0 portal.

    1. On the 6.1.5 server, click Applications -> Content -> Web Content Management.

    2. In the authoring portlet, click Edit Shared Settings.

    3. Add the blog library to the authoring portlet.

      1. Click Library Selection.

      2. Select Blog Resources from the list of available libraries, and click Add.

      3. Click OK.

    4. Update the getNlsStrings.js file.

      1. Download the new version of the getNlsStrings.js file from the WebSphere Portal product documentation.

      2. Ensure that the Blog Resources library is selected in the Library drop-down menu.

      3. Select Components.

      4. Select the check box for FILE - Get NLS Strings JS, and click Edit.

      5. In the File Resource Element section, click Browse and navigate to the updated getNlsStrings.js file that you downloaded.

      6. Click Save and read to update the file and verify changes.

        If you do not update the getNlsStrings.js file before migration, the browser might display this error when displaying a blog or wiki page: ibmPortalConfig is not defined. If the error occurs after you update the getNlsStrings.js file, you might need to clear the browser's cache or delete any temporary internet files to ensure that the latest version of the file is loaded from the server.


Parent

Premigration tasks
Supported migration paths


Related tasks


Set service configuration properties

IBM Software Support, DB2 9

WebSphere Portal Update Installer

  Submitted by Richard Spinks on Sep 28, 2010 12:20:32 PM

Prepare a source portal on a V6.1 application server: wp7

The getNlsStrings.js file can now be downloaded from the link in step 6.d.i. Submitted by John R Chambers on Sep 22, 2010 1:04:24 PM

Prepare a source portal on a V6.1 application server: wp7

Step 6.d.i says to retrieve the "getNlsStrings.js file from the WebSphere Portal product documentation" but I am unable to locate it. Where exactly is this located? Thanks!


+

Search Tips   |   Advanced Search