Re: Email link server alias
LOL! I am catching up on the List. RemedyProd is what we use for our older custom environment :) Jason On Thu, Feb 20, 2014 at 10:54 AM, Cecil, Ken kce...@hubbell.com wrote: ** So LJ, if I want to fix it for going forward on the new system I can change the Server-Name to something generic like RemedyProd. Would I then need to run the MPS Remedy Restore Tool to update the references? And does the new name just need to be resolvable by the midtier and app server (just host file change) or would you recommend creating a DNS alias for that new server name? Ken. *From:* Action Request System discussion list(ARSList) [mailto: arslist@ARSLIST.ORG] *On Behalf Of *LJ LongWing *Sent:* Thursday, February 20, 2014 1:08 PM *To:* arslist@ARSLIST.ORG *Subject:* Re: Email link server alias ** this is typically why I like my 'server name' to be an alias instead of a machine name, that way when moving to a new server, you don't need to worry about this. You need to worry about it at the moment, but if you make your 'new' name, an alias that can be re-pointed as necessary, it's the last time you will have this issue on a server move. On Thu, Feb 20, 2014 at 10:58 AM, Grooms, Frederick W frederick.w.gro...@xo.com wrote: ** Add to your ar.conf (ar.cfg) the IP-Name entry Server-Name: hubprmap2 IP-Name: hubprmap.AD.HubbellPlano.com This will allow the AR Server to know itself by both names. You can have as many IP-Name entries as needed. And you will probably need to add to your Mid-Tier the old server name and maybe a DNS alias or hosts file entry from the old name to the new Fred *From:* Action Request System discussion list(ARSList) [mailto: arslist@ARSLIST.ORG] *On Behalf Of *Cecil, Ken *Sent:* Thursday, February 20, 2014 11:34 AM *To:* arslist@ARSLIST.ORG *Subject:* Email link server alias ** When doing a migration to a new AR server, is there a way to handle all of the links that people have in existing email notifications? They will be pointing to the old server name that no longer exists. For example here is an existing link someone may have in an email http://servicedesk.hubbell.com/arsys/servlet/ViewFormServlet?form=NTE%3aNotifierserver=hubprmap.AD.HubbellPlano.comeid=NTS01013978 Here's what one generated from the new server would be like. http://servicedesk.hubbell.com/arsys/servlet/ViewFormServlet?form=NTE%3aNotifierserver=hubprmap2eid=NTS01013978 Is there a way to use server alias or something like that so that the old links could still function? Ken. _ARSlist: Where the Answers Are and have been for 20 years_ _ARSlist: Where the Answers Are and have been for 20 years_ -- Confidentiality Requirement: This communication, including any attachment(s), may contain confidential information and is for the sole use of the intended recipient(s). If you are not the intended recipient, you are hereby notified that you have received this communication in error and any unauthorized review, use, disclosure, dissemination, distribution or copying of it or its contents is strictly prohibited. If you have received this communication in error, please notify the sender immediately by telephone or e-mail and destroy all copies of this communication and any attachments. _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: Email link server alias
Add to your ar.conf (ar.cfg) the IP-Name entry Server-Name: hubprmap2 IP-Name: hubprmap.AD.HubbellPlano.com This will allow the AR Server to know itself by both names. You can have as many IP-Name entries as needed. And you will probably need to add to your Mid-Tier the old server name and maybe a DNS alias or hosts file entry from the old name to the new Fred From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Cecil, Ken Sent: Thursday, February 20, 2014 11:34 AM To: arslist@ARSLIST.ORG Subject: Email link server alias ** When doing a migration to a new AR server, is there a way to handle all of the links that people have in existing email notifications? They will be pointing to the old server name that no longer exists. For example here is an existing link someone may have in an email http://servicedesk.hubbell.com/arsys/servlet/ViewFormServlet?form=NTE%3aNotifierserver=hubprmap.AD.HubbellPlano.comeid=NTS01013978 Here's what one generated from the new server would be like. http://servicedesk.hubbell.com/arsys/servlet/ViewFormServlet?form=NTE%3aNotifierserver=hubprmap2eid=NTS01013978 Is there a way to use server alias or something like that so that the old links could still function? Ken. ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Where the Answers Are, and have been for 20 years
Re: Email link server alias
this is typically why I like my 'server name' to be an alias instead of a machine name, that way when moving to a new server, you don't need to worry about this. You need to worry about it at the moment, but if you make your 'new' name, an alias that can be re-pointed as necessary, it's the last time you will have this issue on a server move. On Thu, Feb 20, 2014 at 10:58 AM, Grooms, Frederick W frederick.w.gro...@xo.com wrote: ** Add to your ar.conf (ar.cfg) the IP-Name entry Server-Name: hubprmap2 IP-Name: hubprmap.AD.HubbellPlano.com This will allow the AR Server to know itself by both names. You can have as many IP-Name entries as needed. And you will probably need to add to your Mid-Tier the old server name and maybe a DNS alias or hosts file entry from the old name to the new Fred *From:* Action Request System discussion list(ARSList) [mailto: arslist@ARSLIST.ORG] *On Behalf Of *Cecil, Ken *Sent:* Thursday, February 20, 2014 11:34 AM *To:* arslist@ARSLIST.ORG *Subject:* Email link server alias ** When doing a migration to a new AR server, is there a way to handle all of the links that people have in existing email notifications? They will be pointing to the old server name that no longer exists. For example here is an existing link someone may have in an email http://servicedesk.hubbell.com/arsys/servlet/ViewFormServlet?form=NTE%3aNotifierserver=hubprmap.AD.HubbellPlano.comeid=NTS01013978 Here's what one generated from the new server would be like. http://servicedesk.hubbell.com/arsys/servlet/ViewFormServlet?form=NTE%3aNotifierserver=hubprmap2eid=NTS01013978 Is there a way to use server alias or something like that so that the old links could still function? Ken. _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: Email link server alias
So LJ, if I want to fix it for going forward on the new system I can change the Server-Name to something generic like RemedyProd. Would I then need to run the MPS Remedy Restore Tool to update the references? And does the new name just need to be resolvable by the midtier and app server (just host file change) or would you recommend creating a DNS alias for that new server name? Ken. From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of LJ LongWing Sent: Thursday, February 20, 2014 1:08 PM To: arslist@ARSLIST.ORG Subject: Re: Email link server alias ** this is typically why I like my 'server name' to be an alias instead of a machine name, that way when moving to a new server, you don't need to worry about this. You need to worry about it at the moment, but if you make your 'new' name, an alias that can be re-pointed as necessary, it's the last time you will have this issue on a server move. On Thu, Feb 20, 2014 at 10:58 AM, Grooms, Frederick W frederick.w.gro...@xo.commailto:frederick.w.gro...@xo.com wrote: ** Add to your ar.conf (ar.cfg) the IP-Name entry Server-Name: hubprmap2 IP-Name: hubprmap.AD.HubbellPlano.comhttp://hubprmap.AD.HubbellPlano.com This will allow the AR Server to know itself by both names. You can have as many IP-Name entries as needed. And you will probably need to add to your Mid-Tier the old server name and maybe a DNS alias or hosts file entry from the old name to the new Fred From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORGmailto:arslist@ARSLIST.ORG] On Behalf Of Cecil, Ken Sent: Thursday, February 20, 2014 11:34 AM To: arslist@ARSLIST.ORGmailto:arslist@ARSLIST.ORG Subject: Email link server alias ** When doing a migration to a new AR server, is there a way to handle all of the links that people have in existing email notifications? They will be pointing to the old server name that no longer exists. For example here is an existing link someone may have in an email http://servicedesk.hubbell.com/arsys/servlet/ViewFormServlet?form=NTE%3aNotifierserver=hubprmap.AD.HubbellPlano.comeid=NTS01013978 Here's what one generated from the new server would be like. http://servicedesk.hubbell.com/arsys/servlet/ViewFormServlet?form=NTE%3aNotifierserver=hubprmap2eid=NTS01013978 Is there a way to use server alias or something like that so that the old links could still function? Ken. _ARSlist: Where the Answers Are and have been for 20 years_ _ARSlist: Where the Answers Are and have been for 20 years_ Confidentiality Requirement: This communication, including any attachment(s), may contain confidential information and is for the sole use of the intended recipient(s). If you are not the intended recipient, you are hereby notified that you have received this communication in error and any unauthorized review, use, disclosure, dissemination, distribution or copying of it or its contents is strictly prohibited. If you have received this communication in error, please notify the sender immediately by telephone or e-mail and destroy all copies of this communication and any attachments. ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Where the Answers Are, and have been for 20 years
Re: Email link server alias
Fred, If I add the name to the Mid-Tier would I then have Two of everything in the midtier? (One for each server) Ken. From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Grooms, Frederick W Sent: Thursday, February 20, 2014 12:58 PM To: arslist@ARSLIST.ORG Subject: Re: Email link server alias ** Add to your ar.conf (ar.cfg) the IP-Name entry Server-Name: hubprmap2 IP-Name: hubprmap.AD.HubbellPlano.com This will allow the AR Server to know itself by both names. You can have as many IP-Name entries as needed. And you will probably need to add to your Mid-Tier the old server name and maybe a DNS alias or hosts file entry from the old name to the new Fred From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Cecil, Ken Sent: Thursday, February 20, 2014 11:34 AM To: arslist@ARSLIST.ORGmailto:arslist@ARSLIST.ORG Subject: Email link server alias ** When doing a migration to a new AR server, is there a way to handle all of the links that people have in existing email notifications? They will be pointing to the old server name that no longer exists. For example here is an existing link someone may have in an email http://servicedesk.hubbell.com/arsys/servlet/ViewFormServlet?form=NTE%3aNotifierserver=hubprmap.AD.HubbellPlano.comeid=NTS01013978 Here's what one generated from the new server would be like. http://servicedesk.hubbell.com/arsys/servlet/ViewFormServlet?form=NTE%3aNotifierserver=hubprmap2eid=NTS01013978 Is there a way to use server alias or something like that so that the old links could still function? Ken. _ARSlist: Where the Answers Are and have been for 20 years_ Confidentiality Requirement: This communication, including any attachment(s), may contain confidential information and is for the sole use of the intended recipient(s). If you are not the intended recipient, you are hereby notified that you have received this communication in error and any unauthorized review, use, disclosure, dissemination, distribution or copying of it or its contents is strictly prohibited. If you have received this communication in error, please notify the sender immediately by telephone or e-mail and destroy all copies of this communication and any attachments. ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Where the Answers Are, and have been for 20 years
Re: Email link server alias
I'm looking to see if there is a tomcat trick that would let me substitute the new server name in there and redirect the url. Ken. From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Cecil, Ken Sent: Thursday, February 20, 2014 1:59 PM To: arslist@ARSLIST.ORG Subject: Re: Email link server alias ** Fred, If I add the name to the Mid-Tier would I then have Two of everything in the midtier? (One for each server) Ken. From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Grooms, Frederick W Sent: Thursday, February 20, 2014 12:58 PM To: arslist@ARSLIST.ORGmailto:arslist@ARSLIST.ORG Subject: Re: Email link server alias ** Add to your ar.conf (ar.cfg) the IP-Name entry Server-Name: hubprmap2 IP-Name: hubprmap.AD.HubbellPlano.com This will allow the AR Server to know itself by both names. You can have as many IP-Name entries as needed. And you will probably need to add to your Mid-Tier the old server name and maybe a DNS alias or hosts file entry from the old name to the new Fred From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Cecil, Ken Sent: Thursday, February 20, 2014 11:34 AM To: arslist@ARSLIST.ORGmailto:arslist@ARSLIST.ORG Subject: Email link server alias ** When doing a migration to a new AR server, is there a way to handle all of the links that people have in existing email notifications? They will be pointing to the old server name that no longer exists. For example here is an existing link someone may have in an email http://servicedesk.hubbell.com/arsys/servlet/ViewFormServlet?form=NTE%3aNotifierserver=hubprmap.AD.HubbellPlano.comeid=NTS01013978 Here's what one generated from the new server would be like. http://servicedesk.hubbell.com/arsys/servlet/ViewFormServlet?form=NTE%3aNotifierserver=hubprmap2eid=NTS01013978 Is there a way to use server alias or something like that so that the old links could still function? Ken. _ARSlist: Where the Answers Are and have been for 20 years_ Confidentiality Requirement: This communication, including any attachment(s), may contain confidential information and is for the sole use of the intended recipient(s). If you are not the intended recipient, you are hereby notified that you have received this communication in error and any unauthorized review, use, disclosure, dissemination, distribution or copying of it or its contents is strictly prohibited. If you have received this communication in error, please notify the sender immediately by telephone or e-mail and destroy all copies of this communication and any attachments. _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: Email link server alias
I typically add it as a legitimate DNS Alias, although, for a Mid-Tier perspective, the only thing that matters is that the Mid-Tier knows what app server to connect to for that name, and that the app server knows itself by that name...beyond that, it doesn't matter much if it's a dns or a host file entry. Regarding adding the old server name in, yes...by default this'll give you duplicate entries (if you point the old name via host file to new app server)but reading up on this article should help avoid this problem https://docs.bmc.com/docs/display/public/ars81/Viewing+a+subset+of+entry+points#Viewingasubsetofentrypoints-298173 On Thu, Feb 20, 2014 at 11:54 AM, Cecil, Ken kce...@hubbell.com wrote: ** So LJ, if I want to fix it for going forward on the new system I can change the Server-Name to something generic like RemedyProd. Would I then need to run the MPS Remedy Restore Tool to update the references? And does the new name just need to be resolvable by the midtier and app server (just host file change) or would you recommend creating a DNS alias for that new server name? Ken. *From:* Action Request System discussion list(ARSList) [mailto: arslist@ARSLIST.ORG] *On Behalf Of *LJ LongWing *Sent:* Thursday, February 20, 2014 1:08 PM *To:* arslist@ARSLIST.ORG *Subject:* Re: Email link server alias ** this is typically why I like my 'server name' to be an alias instead of a machine name, that way when moving to a new server, you don't need to worry about this. You need to worry about it at the moment, but if you make your 'new' name, an alias that can be re-pointed as necessary, it's the last time you will have this issue on a server move. On Thu, Feb 20, 2014 at 10:58 AM, Grooms, Frederick W frederick.w.gro...@xo.com wrote: ** Add to your ar.conf (ar.cfg) the IP-Name entry Server-Name: hubprmap2 IP-Name: hubprmap.AD.HubbellPlano.com This will allow the AR Server to know itself by both names. You can have as many IP-Name entries as needed. And you will probably need to add to your Mid-Tier the old server name and maybe a DNS alias or hosts file entry from the old name to the new Fred *From:* Action Request System discussion list(ARSList) [mailto: arslist@ARSLIST.ORG] *On Behalf Of *Cecil, Ken *Sent:* Thursday, February 20, 2014 11:34 AM *To:* arslist@ARSLIST.ORG *Subject:* Email link server alias ** When doing a migration to a new AR server, is there a way to handle all of the links that people have in existing email notifications? They will be pointing to the old server name that no longer exists. For example here is an existing link someone may have in an email http://servicedesk.hubbell.com/arsys/servlet/ViewFormServlet?form=NTE%3aNotifierserver=hubprmap.AD.HubbellPlano.comeid=NTS01013978 Here's what one generated from the new server would be like. http://servicedesk.hubbell.com/arsys/servlet/ViewFormServlet?form=NTE%3aNotifierserver=hubprmap2eid=NTS01013978 Is there a way to use server alias or something like that so that the old links could still function? Ken. _ARSlist: Where the Answers Are and have been for 20 years_ _ARSlist: Where the Answers Are and have been for 20 years_ -- Confidentiality Requirement: This communication, including any attachment(s), may contain confidential information and is for the sole use of the intended recipient(s). If you are not the intended recipient, you are hereby notified that you have received this communication in error and any unauthorized review, use, disclosure, dissemination, distribution or copying of it or its contents is strictly prohibited. If you have received this communication in error, please notify the sender immediately by telephone or e-mail and destroy all copies of this communication and any attachments. _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
