Port conflicts

During migration, it is possible that a port conflict might occur when starting up the target environment deployment manager, node agents, or IBM WebSphere Portal servers.

If we are completing a local migration, we might encounter a port conflict due to the source and target environments using the same ports. We can manually update the ports in the serverindex.xml located in the target_wp_profile/config/cells/cellnamenodes/nodename path to correct the port conflict issues.

We might also encounter a port conflict with the configuration wizard server. If this occurs, update the configuration wizard ports in the serverindex.xml located in cw_profile/config/cells/cellnamenodes/nodename.

Parent Migration considerations

Related tasks:

Use copies of source database domains to minimize downtime