+

Search Tips   |   Advanced Search

Portal, V6.1

 

Prepare to run the migration tasks

Preparing to run the migration tasks includes tasks such as updating user roles, changing the HTTP server timeout, collecting required files, performance tuning for export and import operations, and stopping and restarting servers.

Perform the following steps before running the migration tasks:

  1. Ensure that the new version of WebSphere Portal is installed and properly configured.

  2. Check your earlier version environment for any anonymous users with the roles listed below and change them to User:

    • Privileged User

    • Editor

    • Manager

    • Delegator

    • Security Administrator

    • Administrator

  3. Check that you have access to an administrative user ID and password for both the earlier version and the new version.

  4. Migration can take awhile, and interruptions to your HTTP connection during the export process or import process can cause migration to fail. To avoid this problem, change your HTTP server timeout to an unlimited length while performing the migration task. Refer to your HTTP server documentation for information on how to change the timeout value.

  5. Stop the earlier version of your Portal server if either of the following statements is true for your environment:

    • There is a port conflict or resource conflict when you start the current portal server.

    • You modified the number of groups and use WebSphere Portal to manage the groups.

  6. Do performance tuning for exporting and importing large groups and resources as follows. Check your LDAP server to determine the number of groups. If this number is greater than 200, complete the steps below.

    1. Modify the wmm.xml file for the earlier portal as follows:

      1. Change to the wp_old_root/wmm.

        If using i5/OS, the directory is wp_user_old_root.

      2. Open the wmm.xml file, locate the maximumSearchResults attribute, and change its value to a number greater than the actual number of groups on the LDAP server. For example...

        if the LDAP server has 300 groups, enter 301

      3. Save changes.

      4. If this is a clustered environment, change to the was_old_rowmm directory of the earlier version.

        If using i5/OS the directory is was_user_old_root.

      5. Open the wmm.xml file, locate the maximumSearchResults attribute, and change its value to a number greater than the actual number of groups on the LDAP server. For example...

        if the LDAP server has 300 groups, then enter 301.

      6. Save changes.

    2. If this is a clustered environment, modify the wmm.xml file for the earlier portal's deployment manager system as follows

      1. Change to the was_old_rowmm.

      2. Open the wmm.xml file, locate the maximumSearchResults attribute, and change its value to a number greater than the actual number of groups on the LDAP server. For example...

        if the LDAP server has 300 groups, enter 301

      3. Save changes.

    3. Complete any required tasks to enable security. Migration is not supported from a non-secure server.

    4. Change the LDAP server search parameters based on your server's documentation to either an unlimited value or a value large enough to handle the exporting and importing of large groups and resources. For example:

      • Search size limit: Unlimited

      • Search time limit: Unlimited

      • Idle timeout for paged searches: 172800

        This value should be 48 hours or more; no unlimited option is documented. The value is in seconds.

  7. To stop and restart the server1 and WebSphere_Portal servers:

    1. Open a command prompt and change to the /bin directory of the WAS profile in use. For example:

      • Windows: C:\IBM\WebSphere\profiles\profile\bin

      • UNIX: /opt/IBM/WebSphere/AppServer/profiles/profile/bin

      • i5/OS if using WAS V6 for Base and Express: /QIBM/UserData/WebSphere/AppServer/V6/Base/profiles/profile_root/bin

      • i5/OS if using WAS V6 for Network Deployment: /QIBM/UserData/WebSphere/AppServer/V6/ND/profiles/profile_root/bin

    2. Stop the WAS:

      • Windows: stopServer.bat server1 -username adminid -password passwd

      • UNIX: ./stopServer.sh server1 -username adminid -password passwd

      • i5/OS: stopServer server1 -username adminid -password passwd

    3. Stop the WebSphere_Portal server:

      • Windows: stopServer.bat WebSphere_Portal -username adminid -password passwd

      • UNIX: ./stopServer.sh WebSphere_Portal -username adminid -password passwd

      • i5/OS: stopServer WebSphere_Portal -username adminid -password passwd

    4. Start the WAS:

    5. Start the WebSphere_Portal server:

      • Windows: startServer.bat WebSphere_Portal

      • UNIX: ./startServer.sh WebSphere_Portal

      • i5/OS: startServer WebSphere_Portal

  8. Optional

    Set the Computer Associates eTrust SiteMinder property to ensure successful migration.

    If you are using eTrust SiteMinder to perform authorization, verify that the SiteMinderLoginModule custom property is defined because any XML Configuration Interface execution can be affected. For instructions on modifying the SiteMinderLoginModule custom property, see the topic on Configuring eTrust SiteMinder to perform authorization for WebSphere Portal.

 

Parent topic

Preparing for migration

 

Related tasks


Configure eTrust SiteMinder to perform authorization
Configure security