Portal, Express Beta Version 6.1 Operating systems: i5/OS, Linux,Windows

Preparing 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.

1. Ensure that the current version of WebSphere Portal Express 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 current 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 Express to manage the groups.
6. Optional: If you had virtual portals defined in your earlier version of WebSphere Portal Express, use the Virtual Portal Manager to create the virtual portals from the earlier version in the current version.
7. 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. If you are migrating from either V5.0.2.2 or 5.0.2.3, perform these steps on that version:

      1. Change to the wp_old_root/shared/app/wmm directory.
      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, then enter 301.
      3. Save your changes.
   2. Complete any required tasks to enable security.
   3. 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: 172800Note: This value should be 48 hours or more; no unlimited option is documented. The value is in seconds.
8. Perform the following steps to stop and restart the server1 and WebSphere_Portal servers:

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

      • Windows: C:\IBM\WebSphere\profiles\profile_name\bin
      • Linux: /opt/IBM/WebSphere/AppServer/profiles/profile_name/bin
      • i5/OS if using WebSphere Application Server V6 for Base and Express: /QIBM/UserData/WebSphere/AppServer/V6/Base/profiles/profile_root/bin
      • i5/OS if using WebSphere Application Server V6 for Network Deployment: /QIBM/UserData/WebSphere/AppServer/V6/ND/profiles/profile_root/bin
   2. Enter the following command to stop the WebSphere Application Server:

      • Windows: stopServer.bat server1 -user admin_userid -password admin_password
      • Linux: ./stopServer.sh server1 -user admin_userid -password admin_password
      • i5/OS: stopServer server1 -profileName profile_root -user admin_userid -password admin_password where profile_root is the name of the WebSphere Application Server profile where WebSphere Portal Express is installed; for example, wp_profile.
   3. Enter the following command to stop the WebSphere_Portal server:

      • Windows: stopServer.bat WebSphere_Portal -user admin_userid -password admin_password
      • Linux: ./stopServer.sh WebSphere_Portal -user admin_userid -password admin_password
      • i5/OS: stopServer WebSphere_Portal -profileName profile_root -user admin_userid -password admin_password
   4. Enter the following command to start the WebSphere Application Server:

      • Windows: startServer.bat server1
      • Linux: ./startServer.sh server1
      • i5/OS: startServer server1 -profileName profile_root
   5. Enter the following command to start the WebSphere_Portal server:

      • Windows: startServer.bat WebSphere_Portal
      • Linux: ./startServer.sh WebSphere_Portal
      • i5/OS: startServer WebSphere_Portal -profileName profile_root
9. 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 Express.