RE: Migrate IBM Notes Traveler from Windows Server to IBMi -- MIDRANGE-L

Jim,

You can't cluster across platforms. I haven't performed these steps but I would be wary. I would personally configure your Traveler on i as a Brand new Traveler server and plan and manually configuring it to match your old environment. I did this a few times many years ago and wrote an article on it. You can find the article here: http://www.ibmsystemsmag.com/ibmi/administrator/domino/traveler_ibmi/?page=2

I copied the relevant information here:

1. Register a new Domino server named Mobile using a temporary IP address you have configured on the IBM i system.

2. Set all appropriate security and server configurations for the server in the server document.

3. Install Domino version 9 and Traveler on IBM i.

4. Configure the Mobile Domino server and add Traveler to it as previously described. Note: You’ll want to use the same URL as your existing server (https://traveler.mycompany.com/traveler in this example).

5. Configure SSL by copying the keyring file from the existing Traveler server. Note: For HTTP to start properly, you must specify the IP address in the “host name(s)” field in the server document (Figure 3) or override the IP address returned for traveler.mycompany.com by modifying the host table on IBM i. The remaining steps assume the system host table was modified.

6. Test the new Mobile server. This can easily be most done via a browser and the Android Emulator available for download as part of the <http://developer.android.com/sdk/index.html> Android SDK. Again, you’ll need to modify the host table for the PC used during testing to access this new server.

7. Shut down both the Traveler and Mobile Domino servers.

8. Configure the TCP/IP Interface for the IP address previously used by the Traveler server and remove/update the host table entry for Traveler on IBM i.

9. Modify the notes.ini of the Mobile server and set the IP address listed in the following lines to the IP addresses previously used by the Traveler server:

a. TCPIP_TCPAddress= <traveler ip address>

b. NTS_HOST_IP_ADDR= <traveler ip address>

10. Start the Mobile server.

11. Attempt to access mail from the mobile device. You may notice that the first time the device synchronizes with the new server it takes longer as a “prime sync” must be performed. That’s it! You now have a migrated your Traveler users to IBM i. In a future article, I’ll show how to take this single server and configure it for high availability/disaster recovery.

Good Luck!

Amy Hoerle
System Administrator II
Think Mutual Bank
5200 Members Pkwy NW, Box 5949
Rochester, MN 55901

507-536-5815 or
800-288-3425 Ext 5815
ahoerle@xxxxxxxxxxxxx

From: JWGrant@xxxxxxxxxxxxxxx [mailto:JWGrant@xxxxxxxxxxxxxxx]
Sent: Wednesday, April 20, 2016 9:09 AM
To: 'Midrange Systems Technical Discussion' <midrange-l@xxxxxxxxxxxx>
Subject: Migrate IBM Notes Traveler from Windows Server to IBMi

Hi All:

We run a single instance of IBM Notes Traveler https://urldefense.proofpoint.com/v2/url?u=http-3A__9.0.1.8 <https://urldefense.proofpoint.com/v2/url?u=http-3A__9.0.1.8&d=CwIFAw&c=DaPkNJGYNNktHGSdNDiRSrrGMA_zFD3Py0EgkIqOa30&r=NtepIEOpBLtYVdxFYqeN6LAjPXHpgt-h60TSbp4rww0&m=k76_jvM2z2A87yvFrTVr82Hs-YsTLTdC4LpFypqvtcQ&s=Ga8sJ8PFnX6Nk3o-LxOXaENYlgocbd5ubxM8Ph2fqqM&e> &d=CwIFAw&c=DaPkNJGYNNktHGSdNDiRSrrGMA_zFD3Py0EgkIqOa30&r=NtepIEOpBLtYVdxFYqeN6LAjPXHpgt-h60TSbp4rww0&m=k76_jvM2z2A87yvFrTVr82Hs-YsTLTdC4LpFypqvtcQ&s=Ga8sJ8PFnX6Nk3o-LxOXaENYlgocbd5ubxM8Ph2fqqM&e= Build
201510070111_20 on a windows server.
We are interested in migrating this workload to the IBMi.

Its been some time since we have migrated the traveler from one server to
another and I seem to remember its pretty straight forward.

I saw these steps in the Knowledge center, any other considerations or
issues to be aware of when
performing the migration?

Jim

Moving a stand alone system to a new stand alone system
This method assumes you currently have a stand alone IBM Traveler server
and simply want to move it to a different stand alone server without
setting up an Enterprise DB. It also assumes you will have only minor, if
any, network configuration changes.
Note: There will be a degree of system outage using this method. As such,
it is recommended that a twenty four hour outage window be planned for and
announced to the user base.
1. Install the new operating system, Domino, and the IBM Traveler
application on the new IBM Traveler server with a similar configuration as
the existing IBM Traveler server, including SSL settings, SSL
certificates, Domain certificates and any security settings.
2. Verify the new IBM Traveler server is functional. In this case,
instruct one existing user to sync against the new server and verify it
works as expected.
3. Shut down both IBM Traveler servers.
4. Copy the following items from the old IBM Traveler server to the
new one:
a. The entire directory of <data>/traveler/ntsdb.
b. The file: <data>/LotusTraveler.nsf.
5. In the notes.ini on the new server, set the following parameters
parameters:
NTS_TEMPLATE_INSTALL=1
NTS_CLIENT_UPDATE=FULL
6. Start the new Domino server. The IBM Traveler server may perform
database migration depending on the version of the old server. Wait until
you see the message Traveler Started... before continuing.
7. Change the Proxy Server, Firewall, or other network appliance to
route traffic for the old server to the new server.
Or...
Change the physical hostname and IP address of the new server to be the
value of the old server. If you choose this option, you should also change
the hostname, IP Address and External URL parameters in the Domino server
document and any Internet Site documents to match the physical server
changes. A Domino server restart is recommended after making these
changes.
8. Verify any existing users continue to functional normally.
9. Power® off the old server if desired.

Jim W Grant
Senior VP, Chief Information Officer
Web: https://urldefense.proofpoint.com/v2/url?u=http-3A__www.pdpgroupinc.com <https://urldefense.proofpoint.com/v2/url?u=http-3A__www.pdpgroupinc.com&d=CwIFAw&c=DaPkNJGYNNktHGSdNDiRSrrGMA_zFD3Py0EgkIqOa30&r=NtepIEOpBLtYVdxFYqeN6LAjPXHpgt-h60TSbp4rww0&m=k76_jvM2z2A87yvFrTVr82Hs-YsTLTdC4LpFypqvtcQ&s=w8Vs9ifH1ewxbaqjy02qYZU3ZwfVF0TukvmiNg4bu7Y&e> &d=CwIFAw&c=DaPkNJGYNNktHGSdNDiRSrrGMA_zFD3Py0EgkIqOa30&r=NtepIEOpBLtYVdxFYqeN6LAjPXHpgt-h60TSbp4rww0&m=k76_jvM2z2A87yvFrTVr82Hs-YsTLTdC4LpFypqvtcQ&s=w8Vs9ifH1ewxbaqjy02qYZU3ZwfVF0TukvmiNg4bu7Y&e=
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx <mailto:MIDRANGE-L@xxxxxxxxxxxx>
To subscribe, unsubscribe, or change list options,
visit: https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.midrange.com_mailman_listinfo_midrange-2Dl <https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.midrange.com_mailman_listinfo_midrange-2Dl&d=CwIFAw&c=DaPkNJGYNNktHGSdNDiRSrrGMA_zFD3Py0EgkIqOa30&r=NtepIEOpBLtYVdxFYqeN6LAjPXHpgt-h60TSbp4rww0&m=k76_jvM2z2A87yvFrTVr82Hs-YsTLTdC4LpFypqvtcQ&s=XZOzrzh7jciIioRRt4ST2QPKa7SfsXco9B3Em7YBgQE&e> &d=CwIFAw&c=DaPkNJGYNNktHGSdNDiRSrrGMA_zFD3Py0EgkIqOa30&r=NtepIEOpBLtYVdxFYqeN6LAjPXHpgt-h60TSbp4rww0&m=k76_jvM2z2A87yvFrTVr82Hs-YsTLTdC4LpFypqvtcQ&s=XZOzrzh7jciIioRRt4ST2QPKa7SfsXco9B3Em7YBgQE&e=
or email: MIDRANGE-L-request@xxxxxxxxxxxx <mailto:MIDRANGE-L-request@xxxxxxxxxxxx>
Before posting, please take a moment to review the archives
at https://urldefense.proofpoint.com/v2/url?u=http-3A__archive.midrange.com_midrange-2Dl <https://urldefense.proofpoint.com/v2/url?u=http-3A__archive.midrange.com_midrange-2Dl&d=CwIFAw&c=DaPkNJGYNNktHGSdNDiRSrrGMA_zFD3Py0EgkIqOa30&r=NtepIEOpBLtYVdxFYqeN6LAjPXHpgt-h60TSbp4rww0&m=k76_jvM2z2A87yvFrTVr82Hs-YsTLTdC4LpFypqvtcQ&s=YzZzwnsjJzS5rOs7Es9L4kK3-5tEFuvLtqZslOxd_EU&e> &d=CwIFAw&c=DaPkNJGYNNktHGSdNDiRSrrGMA_zFD3Py0EgkIqOa30&r=NtepIEOpBLtYVdxFYqeN6LAjPXHpgt-h60TSbp4rww0&m=k76_jvM2z2A87yvFrTVr82Hs-YsTLTdC4LpFypqvtcQ&s=YzZzwnsjJzS5rOs7Es9L4kK3-5tEFuvLtqZslOxd_EU&e= .

Please contact support@xxxxxxxxxxxx <mailto:support@xxxxxxxxxxxx> for any subscription related questions.