When migrating with On Demand Migration for Email (ODME) from GroupWise, you may see an informational message about a redirection, followed by errors/warnings about ODME being unable to connect to the GroupWise server:
Redirected from 'https://po1.example.com:7191/soap/' to the different post office address 'https://10.0.0.1:7191/soap/'
[1/2]Error detected, attempting retry 1 of 3 A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 10.0.0.1 :7191 (A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 10.0.0.1:7191)
When migrating from GroupWise in an environment where there are multiple GroupWise Post Offices, each GroupWise Post Office will need to have SOAP enabled and will need to be externally accessible. Also, when creating Migration Plans within the ODME portal, users will need to be grouped by GroupWise Post Office and the Source Connection settings will need to include the specific SOAP hostname or IP address for their GroupWise Post Office. Using this workaround, at least one ODME Migration Plan will need to be created for each GroupWise Post Office being migrated, with the appropriate SOAP hostname or IP address, and a list of users residing on that Post Office.
GroupWise will need to be configured to refer ODME to an externally accessible SOAP URL for each GroupWise Post Office. We would recommend contacting Novell directly for assistance with configuring your GroupWise Post Offices with external IP addresses and verifying redirection for external GroupWise clients, such as ODME.