You could do that but that also requires careful planning. This is because when the server comes back up, the synchronization anchors are no longer accurate between the server and device, so the data must be refreshed on the device with the server version.”Īnd what about timing and testing this change – do all devices at one go – seems uncertain to me.Ĭonvinced that changing host name on Traveler is too much hassle and still not want to have to touch the devices – maybe do the other way around, vice versa, change host name and IP address for the Domino mail server.
The one downside to this situation is that if a user had made changes on the device that were pending synchronization, then these changes will be lost when the server is restored. The mobile device will not receive duplicate entries on the server or device. Again from the Traveler wiki “There is no problem for the clients if the server must be replaced (e.g.
I have not tested this but if it’s even possible (note: I assume it is not recommended you should re-configure devices from scratch) – again for sake of discussion I suppose it’s like a server replacement from the device perspective – you should (must) stick to the same version so if upgrade was in the plan you have to do that later.
Say you have a management solution for mobile devices so you could update profiles on devices centrally, how would that work. This goes down error paths on the device and tends to cause odd device behavior noticed by the device user.” And “ The devices will be making extra requests with all the redirections and that will affect battery life.”Īlright – so these are some of the reasons you read in a lot of places that don’t change host name and IP address on Traveler installations. Most of the requests are POST, and the device will respond to a 302 redirect by repeating it as a GET which means the body of the POST is missing. “ The Apple iOS devices will not tolerate the HTTP 302 redirect that is proposed. I checked with Traveler development team and they also responded:
Even if it works – do you really want the dependency for Traveler users to the old server plus the extra load on HTTP crunching all the Traveler requests? I would not recommend it. It does add another component into the system for Traveler and iNotes so maybe this is not possible (due to the extra expense and administration etc.) – but it also is very useful, and a requirement if you want to have high availability for Traveler.īut is there another solution using redirects, modified IWAREDIR.NSF and/or “External URL” Traveler setting?įor the sake of argument, let’s say creating a redirection rule as if the resource requested by the URL had moved to another location (which it has – right). This would avoid having to change the host name on the devices. The proxy would use the existing host name and then pass (not redirect back to the device via 302) the request to the right server. Okay – so changing host name of Traveler server is it possible to do this without touching all existing devices – yes, if you have a reverse proxy it is.
So basically you have a lot of dependencies to your host (might even have the same host name as Windows computer name) – some examples: Ok – so if you can keep your host name and IP address for Traveler you are good to go ahead to do a machine swap, refer to “ Moving Traveler to a new server” on the Notes/Domino wiki for more information.īut what if you can’t keep IP address/hostname – reason being host name that ended up in Traveler profile is the same name as your iNotes server, it is home server for Notes users and you did not use another virtual web server host name for Traveler. *) Heads up: Banned documents and Repeated Crash Protection for Lotus Notes Traveler: “ By default the repeated crash protection is enabled and set to detect and ban a document after the second crash“. The need is to minimize user intervention on mobile devices moving to new dedicated Traveler server. Now you want to move it out to another server, as the Traveler workload is heavy, better performance is the goal and/or to eliminate the risk of Traveler issues* affecting your other service(s) on the machine, example it’s your iNotes server as well.
Scenario: you wanted to test Lotus Traveler so Traveler was set up to an existing Domino server at the time, or even the only server you had.