Re: mirror to production
>I could simply change DNS name and voila each client would connect seamlessly. >This code is for a large hospital and changing DNS names like this does not >seem to be in the cards. That what we did at the last place I worked. Alternatively, if your users are on Windows, you can push new .4DLink files to them in Windows login scripts. That worked effectively too and may be easier to implement in your environment. HTH, Tom Benedict > On Oct 4, 2019, at 09:40, Chuck Miller via 4D_Tech <4d_tech@lists.4d.com> > wrote: > > Hi all, > > We are ready to implement our new mirror code and are writing documentation > on this process. The one thing I have not figured out is how to turn the > mirror into production. > > The server itself is pretty easy as I have a record that has IP address of > production machine in a record. > > What I do not understand is how to update the clients. Production and Mirror > are on different subnets so the built client on the machine will not be able > to connect to without a change to 4Dlink file. > > What I was hoping was to use a DNS name and simply change the IP address it > points to so if I had > > Server_prod which pointed at 192.168.5.5 > Server_Mirros which pointed at 192.162.5.17 > > The IP’s are of course not the real ones in use > > I could simply change DNS name and voila each client would connect > seamlessly. This code is for a large hospital and changing DNS names like > this does not seem to be in the cards. > > Can anyone tell me how they are doing this > > Thanks and regards > > ** 4D Internet Users Group (4D iNUG) Archive: http://lists.4d.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub: mailto:4d_tech-unsubscr...@lists.4d.com **
Re: mirror to production
On Oct 4, 2019, at 5:24 PM, Chuck Miller wrote: > Good thought but when you have a but client a new 4dlink file gets created on > connection and that is the one that is used If you are using a “built” 4D Client, then the 4Dlink file is not an option because the build client uses it’s own internal .4Dlink file. But if you are using standard 4D Server and 4D, then you can do what I specified. Since you are deploying in a very controlled hospital environment, I would suggest you put this back on the IT department. They make all the rules and make it difficult. So make it their problem to solve. If they want to make it easy, they can do the DNS change work. If they want to make it hard, they can deal with how to make it work. You know what needs to be done to get 4D Client to connect to 4D Server. Tell them how it works and then ask them “how do you propose we solve this problem”. You would be surprised how quickly they decide what is “completely impossible” become easily done when they have to make it work. Remember that it is their sandbox that you are playing in. You are just a third party vendor. If they want to make it difficult, that’s not your problem, that’s their problem. And the users need to know that. Tim * Tim Nevels Innovative Solutions 785-749-3444 timnev...@mac.com * ** 4D Internet Users Group (4D iNUG) Archive: http://lists.4d.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub: mailto:4d_tech-unsubscr...@lists.4d.com **
Re: mirror to production
Good thought but when you have a but client a new 4dlink file gets created on connection and that is the one that is used Regards Chuck Sent from my iPhone > On Oct 4, 2019, at 3:13 PM, Tim Nevels via 4D_Tech <4d_tech@lists.4d.com> > wrote: > >> On Oct 4, 2019, at 2:00 PM, Chuck Miller wrote: >> >> We are ready to implement our new mirror code and are writing documentation >> on this process. The one thing I have not figured out is how to turn the >> mirror into production. >> >> The server itself is pretty easy as I have a record that has IP address of >> production machine in a record. >> >> What I do not understand is how to update the clients. Production and >> Mirror are on different subnets so the built client on the machine will not >> be able to connect to without a change to 4Dlink file. >> >> What I was hoping was to use a DNS name and simply change the IP address it >> points to so if I had >> >> Server_prod which pointed at 192.168.5.5 >> Server_Mirros which pointed at 192.162.5.17 >> >> The IP’s are of course not the real ones in use >> >> I could simply change DNS name and voila each client would connect >> seamlessly. This code is for a large hospital and changing DNS names like >> this does not seem to be in the cards. >> >> Can anyone tell me how they are doing this > > DNS name change is definitely the way to go, but if you can’t do that, then > you could do something like this. > > First, all of your 4D Client users need to have a network file server share > that they all have mounted. > > On that share create a folder and put in that folder a .4Dlink file that > everyone will use to connect to 4D Server. > > Next make a shortcut to this 4Dlink file and send this to all your users. > Tell them this is the file they should double-click to connect to 4D Server. > No user will have the real 4Dlink file on their hard drive. They only get to > have a shortcut to the 4Dlink on the network share. > > When you want to switch from production to mirror server you just change the > IP address inside 4Dlink file on the file server share. > > Tim > > * > Tim Nevels > Innovative Solutions > 785-749-3444 > timnev...@mac.com > * > > ** > 4D Internet Users Group (4D iNUG) > Archive: http://lists.4d.com/archives.html > Options: https://lists.4d.com/mailman/options/4d_tech > Unsub: mailto:4d_tech-unsubscr...@lists.4d.com > ** ** 4D Internet Users Group (4D iNUG) Archive: http://lists.4d.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub: mailto:4d_tech-unsubscr...@lists.4d.com **
Re: mirror to production
On Oct 4, 2019, at 2:00 PM, Chuck Miller wrote: > We are ready to implement our new mirror code and are writing documentation > on this process. The one thing I have not figured out is how to turn the > mirror into production. > > The server itself is pretty easy as I have a record that has IP address of > production machine in a record. > > What I do not understand is how to update the clients. Production and Mirror > are on different subnets so the built client on the machine will not be able > to connect to without a change to 4Dlink file. > > What I was hoping was to use a DNS name and simply change the IP address it > points to so if I had > > Server_prod which pointed at 192.168.5.5 > Server_Mirros which pointed at 192.162.5.17 > > The IP’s are of course not the real ones in use > > I could simply change DNS name and voila each client would connect > seamlessly. This code is for a large hospital and changing DNS names like > this does not seem to be in the cards. > > Can anyone tell me how they are doing this DNS name change is definitely the way to go, but if you can’t do that, then you could do something like this. First, all of your 4D Client users need to have a network file server share that they all have mounted. On that share create a folder and put in that folder a .4Dlink file that everyone will use to connect to 4D Server. Next make a shortcut to this 4Dlink file and send this to all your users. Tell them this is the file they should double-click to connect to 4D Server. No user will have the real 4Dlink file on their hard drive. They only get to have a shortcut to the 4Dlink on the network share. When you want to switch from production to mirror server you just change the IP address inside 4Dlink file on the file server share. Tim * Tim Nevels Innovative Solutions 785-749-3444 timnev...@mac.com * ** 4D Internet Users Group (4D iNUG) Archive: http://lists.4d.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub: mailto:4d_tech-unsubscr...@lists.4d.com **
mirror to production
Hi all, We are ready to implement our new mirror code and are writing documentation on this process. The one thing I have not figured out is how to turn the mirror into production. The server itself is pretty easy as I have a record that has IP address of production machine in a record. What I do not understand is how to update the clients. Production and Mirror are on different subnets so the built client on the machine will not be able to connect to without a change to 4Dlink file. What I was hoping was to use a DNS name and simply change the IP address it points to so if I had Server_prod which pointed at 192.168.5.5 Server_Mirros which pointed at 192.162.5.17 The IP’s are of course not the real ones in use I could simply change DNS name and voila each client would connect seamlessly. This code is for a large hospital and changing DNS names like this does not seem to be in the cards. Can anyone tell me how they are doing this Thanks and regards Chuck Chuck Miller Voice: (617) 739-0306 Informed Solutions, Inc. Fax: (617) 232-1064 mailto:cjmillerinformed-solutions.com Brookline, MA 02446 USA Registered 4D Developer Providers of 4D and Sybase connectivity http://www.informed-solutions.com This message and any attached documents contain information which may be confidential, subject to privilege or exempt from disclosure under applicable law. These materials are intended only for the use of the intended recipient. If you are not the intended recipient of this transmission, you are hereby notified that any distribution, disclosure, printing, copying, storage, modification or the taking of any action in reliance upon this transmission is strictly prohibited. Delivery of this message to any person other than the intended recipient shall not compromise or waive such confidentiality, privilege or exemption from disclosure as to this communication. ** 4D Internet Users Group (4D iNUG) Archive: http://lists.4d.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub: mailto:4d_tech-unsubscr...@lists.4d.com **
