Re: Server Alias Production and COOP
Thanks for the info. I pushed to put load balancers when we upgraded to 9.1, but the customer didn't want to spend the money. I'll mess around with the aliases in the ar.cfg file. From: Action Request System discussion list(ARSList) on behalf of Grooms, Frederick W Sent: Wednesday, May 17, 2017 10:42:58 AM To: arslist@ARSLIST.ORG Subject: Re: Server Alias Production and COOP ** The way we handle it here is to never use the real server names, always use an alias for both the web server and the AR Server. In the AR System you can add the IP-Name entries to the ar.conf (ar.cfg for Windows) so the AR System will recognize both names as the same server i.e. Server-Name: name1 IP-Name: name1.fqdn.com IP-Name: alias1 IP-Name: alias1.fqdn.com We typically also add the alias to the hosts file so from inside the server it will resolve the alias to itself always From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Brian Pancia Sent: Wednesday, May 17, 2017 9:19 AM To: arslist@ARSLIST.ORG Subject: Server Alias Production and COOP ** We have a number of integrations with our remedy environment using web services. We want to seamlessly switch between Production and COOP without impacting the integrations, since the remedy application server name is in the mid-tier url. I'm assuming we can setup a DNS server alias and then just mess with DNS when switching between environments. How have other people managed this and are there any things to lookout for? Ideally I would like to be able to swap in and out of environments without the integrations or end users realizing we are switching. Current sample settings, names changed to protect the innocent: https://productionmidtierserver/arsys/forms/productionappserver/... https://coopmidtierserver/arsys/forms/coopappserver/... Would like both to use: https://remedy.com/arsys/forms/remedyappserver/... Thanks, Brian DISCLAIMER: The information contained in this e-mail and its attachments contain confidential information belonging to the sender, which is legally privileged. The information is intended only for the use of the recipient(s) named above. If you are not the intended recipient, you are notified that any disclosure, copying, distribution or action in reliance upon the contents of the information transmitted is strictly prohibited. If you have received this information in error, please delete it immediately. _ARSlist: "Where the Answers Are" and have been for 20 years_ _ARSlist: "Where the Answers Are" and have been for 20 years_ DISCLAIMER: The information contained in this e-mail and its attachments contain confidential information belonging to the sender, which is legally privileged. The information is intended only for the use of the recipient(s) named above. If you are not the intended recipient, you are notified that any disclosure, copying, distribution or action in reliance upon the contents of the information transmitted is strictly prohibited. If you have received this information in error, please delete it immediately. ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
Re: Server Alias Production and COOP
The way we handle it here is to never use the real server names, always use an alias for both the web server and the AR Server. In the AR System you can add the IP-Name entries to the ar.conf (ar.cfg for Windows) so the AR System will recognize both names as the same server i.e. Server-Name: name1 IP-Name: name1.fqdn.com IP-Name: alias1 IP-Name: alias1.fqdn.com We typically also add the alias to the hosts file so from inside the server it will resolve the alias to itself always From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Brian Pancia Sent: Wednesday, May 17, 2017 9:19 AM To: arslist@ARSLIST.ORG Subject: Server Alias Production and COOP ** We have a number of integrations with our remedy environment using web services. We want to seamlessly switch between Production and COOP without impacting the integrations, since the remedy application server name is in the mid-tier url. I'm assuming we can setup a DNS server alias and then just mess with DNS when switching between environments. How have other people managed this and are there any things to lookout for? Ideally I would like to be able to swap in and out of environments without the integrations or end users realizing we are switching. Current sample settings, names changed to protect the innocent: https://productionmidtierserver/arsys/forms/productionappserver/... https://coopmidtierserver/arsys/forms/coopappserver/... Would like both to use: https://remedy.com/arsys/forms/remedyappserver/... Thanks, Brian DISCLAIMER: The information contained in this e-mail and its attachments contain confidential information belonging to the sender, which is legally privileged. The information is intended only for the use of the recipient(s) named above. If you are not the intended recipient, you are notified that any disclosure, copying, distribution or action in reliance upon the contents of the information transmitted is strictly prohibited. If you have received this information in error, please delete it immediately. _ARSlist: "Where the Answers Are" and have been for 20 years_ ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
Re: Server Alias Production and COOP
Brian, In the past I have used DNS, but that's problematic because dns has local caches (on machines) and such, the much more elegant solution is load balancers, this is typically done between two or more machines within the server group of course, but if you have an alternate lb (load balanced load balancer) in your coop site that the primary lb talks to, then when you want to switch to your coop, the LB simply points to the other site, it's just like you are in a server group that only half of which is being used, then when it's time to COOP, the other half gets used and the first half doesn't... On Wed, May 17, 2017 at 8:19 AM, Brian Pancia wrote: > ** > > We have a number of integrations with our remedy environment using web > services. We want to seamlessly switch between Production and COOP without > impacting the integrations, since the remedy application server name is in > the mid-tier url. I'm assuming we can setup a DNS server alias and then > just mess with DNS when switching between environments. How have other > people managed this and are there any things to lookout for? Ideally I > would like to be able to swap in and out of environments without the > integrations or end users realizing we are switching. > > > Current sample settings, names changed to protect the innocent: > > > https://productionmidtierserver/arsys/forms/productionappserver/... > > > https://coopmidtierserver/arsys/forms/coopappserver/... > > > Would like both to use: > > > https://remedy.com/arsys/forms/remedyappserver/... > > > > Thanks, > > > Brian > > > DISCLAIMER: The information contained in this e-mail and its attachments > contain confidential information belonging to the sender, which is legally > privileged. The information is intended only for the use of the > recipient(s) named above. If you are not the intended recipient, you are > notified that any disclosure, copying, distribution or action in reliance > upon the contents of the information transmitted is strictly prohibited. If > you have received this information in error, please delete it immediately. > _ARSlist: "Where the Answers Are" and have been for 20 years_ ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
