+

Search Tips   |   Advanced Search

Hardware considerations

There might be cases where we are completing a remote migration to a new hardware configuration. This new server might have different requirements from the current environment we are migrating from. Generally, here are some key points to consider.

Source environment:

  • Revisit the hardware the software requirements for the platform we are migrating from. Ensure we are still in a fully supported environment.

  • Make sure we are current with, at least, the last two maintenance levels for that platform.

  • Be aware of the current overall performance and throughput. Know what the current activity is on the WebSphere Portal server.

  • Make sure that we have detailed information about the entire environment.

    • Identify all the systems the WebSphere Portal server connects to.

    • Keep a detailed list of all the credentials and connection information as well as the services provided by the other systems.

    • If firewalls are involved, make sure that you note ports, IP addresses, and host names used.

Target environment:

  • Review the system requirements for the new environment.

  • Review the supported migration paths.

  • Will this new system be dedicated as a WebSphere Portal server or it will be shared with other services?

    • If shared, be aware of potential resource conflicts such as ports as well as overall system performance.

  • Make sure we are at a supported maintenance level.

  • Be mindful of the projected WebSphere Portal server activity. Once migrated, or even during the testing phase of the migration, we should be able to compare performance data between the current and new WebSphere Portal servers.

Architecture:

  • Your target environment must be on the same system architecture than the source environment for migration. Migrating to a different architecture is not supported.


Parent Plan for migration