Axton, You are correct, configuration and how a person connects with the admin tools makes a difference.
Your explanation helps explain some of the issues I was seeing on our older servers. Dave ________________________________ From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of Axton Sent: Monday, June 29, 2009 8:38 PM To: arslist@ARSLIST.ORG Subject: Re: Test System to Production System, Would Ghost Image work ? what is BMC recommendation? ** I believe this can still be an issue even in later versions depending on how the server is configured. Say the hostname of the arserver host is remedy1, it has ip address 10.1.1.1 and the following dns aliases: remedy remedy.company.com<http://remedy.company.com> ars ars.company.com<http://ars.company.com> Let's say the Server-Name parameter in ar.conf has a value of remedy1. If you connect using the admin tool to the arserver with a hostname of remedy, that name will be embedded in the workflow unless you have configured the proper IP-Name parameters in ar.conf. The valid IP-Name parameters would be any hostname with which arserver can be accessed, so you would want the following lines in ar.conf: IP-Name: remedy IP-Name: remedy.company.com<http://remedy.company.com> IP-Name: ars IP-Name: ars.company.com<http://ars.company.com> This problem is more common with arsystem configurations where multiple arservers are in use. Take the following example: hostname for arserver1: remedy01 (10.0.0.1) hostname for arserver2: remedy02 (10.0.0.2) hostname for arserver3: remedy03 (10.0.0.3) hostname for load balancer: remedy (10.1.0.1) Aliases/other names for load balancer: arsystem, arsystem.company.com<http://arsystem.company.com> Aliases/other names for remedy01: arsvr01, arsvr01.company.com<http://arsvr01.company.com>, remedy01.company.com<http://remedy01.company.com> Aliases/other names for remedy02: arsvr02, arsvr02.company.com<http://arsvr02.company.com>, remedy02.company.com<http://remedy02.company.com> Aliases/other names for remedy03: arsvr03, arsvr03.company.com<http://arsvr03.company.com>, remedy03.company.com<http://remedy03.company.com> You could now potentially access each arserver using several names (strings). The ar.conf (IP-Name parameters) needs to be different on each arserver. The IP-Name parameter seems to be used to parse the workflow when committing workflow to the db; it is used to strip server name references and replace them with the desired @ symbol (global local server reference). If no match is found to Server-Name or IP-Name, the workflow will think the reference is to and external ARServer and store the actual name of the server in the workflow when written to the db. Axton Grams These are my opinions and observations. On Mon, Jun 29, 2009 at 5:51 PM, Shellman, David<dave.shell...@tycoelectronics.com<mailto:dave.shell...@tycoelectronics.com>> wrote: > Lee, > > The 4.x versions and 5.x versions were a bugger with retaining server and IP > address information. There were scripts that could be run against def files > to clean up remainder of server info that remained in the files. Menus were > the worst offenders. > > I don't remember any issues with exporting as server independent with 6.x > nor have I seen any with 7.0.1. > Dave > ------------------------- > dave.shell...@tycoelectronics.com<mailto:dave.shell...@tycoelectronics.com> > (Wireless) > > ________________________________ > From: Action Request System discussion list(ARSList) > <arslist@ARSLIST.ORG<mailto:arslist@ARSLIST.ORG>> > To: arslist@ARSLIST.ORG<mailto:arslist@ARSLIST.ORG> > <arslist@ARSLIST.ORG<mailto:arslist@ARSLIST.ORG>> > Sent: Mon Jun 29 18:27:19 2009 > Subject: Re: Test System to Production System, Would Ghost Image work ? what > is BMC recommendation? > > Server Name AND IP address. > > Just as a precaution, I'd suggest that when you look for server references > that you include searches for IP addresses. We moved a 5.x server from one > segment to another. We kept the server name the same but the IP address > changed. We found hundreds of IP references imbedded in the code that > prevented the server from coming up. There is a knowledge base instruction > on a fix this in MSSQL DB's. BMC Support folks sent us the instructions. I > don't know if the same is true for other systems since our 7.0 install was a > clean install with limited data migration and no custom code. > > Folks probably know to equate the server name and IP address, but it caught > us a little off guard at the time. > > Lee Marsh > > > ************************************* > Lee Marsh > Remedy Administrator > BAE Systems Office Automation Systems Team > Antitrust Division, U.S. Department of Justice > Phone: 202-305-9725 > Cell: 202-528-1749 > Email: lee.ma...@usdoj.gov<mailto:lee.ma...@usdoj.gov> > <mailto:lee.ma...@usdoj.gov<mailto:lee.ma...@usdoj.gov>> > ************************************* > > > > > -----Original Message----- > From: Action Request System discussion list(ARSList) > [mailto:arslist@ARSLIST.ORG<mailto:arslist@ARSLIST.ORG>] > Sent: Monday, June 29, 2009 6:10 PM > To: arslist@ARSLIST.ORG<mailto:arslist@ARSLIST.ORG> > Subject: Re: Test System to Production System, Would Ghost Image work ? > what is BMC recommendation? > > > I would like to verify if I do or don't. In looking at diffs between our > environments in Migrator, I've seen system-maintained code that _appeared_ > to have specific server references in it, if you can trust Migrator here. > They were usually in the Approval module, I think, but there may have been > others. We also have a fair amount of custom code that has been maintained > by various people over time, and I would like to make sure that we don't > have things that need to be fixed there (I have found a few cases as I've > worked on parts of the system, and I'd like to find out if there are more). > > We've got half of the ITSM suite, so I'm not too keen on trying to export it > all - I know we've tried in the past (albeit with the rest of the suite > installed) and never succeeded. > > Thanks, > Lyle > > -----Original Message----- > From: Action Request System discussion list(ARSList) > [mailto:arslist@ARSLIST.ORG<mailto:arslist@ARSLIST.ORG>] On Behalf Of > Shellman, David > Sent: Monday, June 29, 2009 2:59 PM > To: arslist@ARSLIST.ORG<mailto:arslist@ARSLIST.ORG> > Subject: Re: Test System to Production System, Would Ghost Image work ? what > is BMC recommendation? > > Not sure what you have but exporting all our workflow for custom helpdesk, > surveys, contract maintenance, bug tracking, modeling service requests, > Telecommunication billing, etc takes only a few minutes. > > Maybe we need to step back. Do you know you have workflow that has the > server name embedded in it? Or are you just concerned that you have? > Dave > ------------------------- > dave.shell...@tycoelectronics.com<mailto:dave.shell...@tycoelectronics.com> > (Wireless) > > ----- Original Message ----- > From: Action Request System discussion list(ARSList) > <arslist@ARSLIST.ORG<mailto:arslist@ARSLIST.ORG>> > To: arslist@ARSLIST.ORG<mailto:arslist@ARSLIST.ORG> > <arslist@ARSLIST.ORG<mailto:arslist@ARSLIST.ORG>> > Sent: Mon Jun 29 16:41:00 2009 > Subject: Re: Test System to Production System, Would Ghost Image work ? what > is BMC recommendation? > > Exporting all the workflow would be way too time consuming. I'm thinking > (hoping) there must be an easier way to find out. > > Thanks, > Lyle > > -----Original Message----- > From: Action Request System discussion list(ARSList) > [mailto:arslist@ARSLIST.ORG<mailto:arslist@ARSLIST.ORG>] On Behalf Of > Shellman, David > Sent: Monday, June 29, 2009 2:35 PM > To: arslist@ARSLIST.ORG<mailto:arslist@ARSLIST.ORG> > Subject: Re: Test System to Production System, Would Ghost Image work ? what > is BMC recommendation? > > Lyle, > > Export all the workflow. Make sure when you export, the checkbox for export > as server independent is checked. This should remove workflow that is > linked to the server. > > It's not guaranteed as there could be some custom workflow that may some how > reference the server. As Raj noted you can open the def file with notepad, > wordpad, notepad++, etc and search for instances of the server name. > Dave > ------------------------- > dave.shell...@tycoelectronics.com<mailto:dave.shell...@tycoelectronics.com> > (Wireless) > > ----- Original Message ----- > From: Action Request System discussion list(ARSList) > <arslist@ARSLIST.ORG<mailto:arslist@ARSLIST.ORG>> > To: arslist@ARSLIST.ORG<mailto:arslist@ARSLIST.ORG> > <arslist@ARSLIST.ORG<mailto:arslist@ARSLIST.ORG>> > Sent: Mon Jun 29 16:24:18 2009 > Subject: Re: Test System to Production System, Would Ghost Image work ? what > is BMC recommendation? > > What's an easy way to locate workflow that has specific server references in > it? > > Thanks, > Lyle > > -----Original Message----- > From: Action Request System discussion list(ARSList) > [mailto:arslist@ARSLIST.ORG<mailto:arslist@ARSLIST.ORG>] On Behalf Of Ken > Pritchard > Sent: Saturday, June 27, 2009 7:43 AM > To: arslist@ARSLIST.ORG<mailto:arslist@ARSLIST.ORG> > Subject: Re: Test System to Production System, Would Ghost Image work ? what > is BMC recommendation? > > I just did something similar with HP-UX (Remedy V6.3). In my case, I hooked > a new server into a servergroup (db was the same). > > Needed to change two items in the ar.conf file (IP addr and SERVERNAME > entries), adjust the armonitor.conf file to reflect new servername and > remove all licenses that were brought over from the prior server. Needed to > have the /remedy and /etc/arsystem dir structures restored. Had to make > sure the database name was in the tnsnames.ora file on the new server. > > We also had the source server hooked in a cluster (so the arsystem file in > /remedy/<svrname>/bin also needed a modification since there was a > servername embedded in that file. > > Once I did the above, the server came up in evaluation mode and I was able > to apply the new licenses. > > One of the important things to look at is that the workflow in your ARS > system needs to be server independent. If there are references to specific > servers in your workflow, you'll need to clean the workflow to make it > server independent. > > - pritch > > -----Original Message----- > From: Action Request System discussion list(ARSList) > [mailto:arslist@ARSLIST.ORG<mailto:arslist@ARSLIST.ORG>] On Behalf Of Axton > Sent: Saturday, June 27, 2009 2:03 AM > To: arslist@ARSLIST.ORG<mailto:arslist@ARSLIST.ORG> > Subject: Re: Test System to Production System, Would Ghost Image work ? what > is BMC recommendation? > > What OS are you dealing with? > > Axton Grams > > On Fri, Jun 26, 2009 at 11:36 AM, > Raj<ravi6...@gmail.com<mailto:ravi6...@gmail.com>> wrote: >> Hello All, >> >> I completed fresh install of ARS 7.5.00 Patch 001/ITSM 7.5.01 Patch >> 001 on a test system. >> Now, next task is to build the production system, so my question is, >> will taking the ghost image of test system and putting it on >> production system will work ? or do i have to start fresh >> installations of ARS and ITSM again on production system ? >> >> What is ideal approach ? What does BMC recommend ? Please advice. >> >> Regards, >> Raj >> rki...@spike.dor.state.co.us<mailto:rki...@spike.dor.state.co.us> >> >> > ____________________________________________________________________________ > ___ >> UNSUBSCRIBE or access ARSlist Archives at >> www.arslist.org<http://www.arslist.org> >> Platinum >> Sponsor:rmisoluti...@verizon.net<mailto:sponsor%3armisoluti...@verizon.net> >> ARSlist: "Where the Answers Are" >> > > ____________________________________________________________________________ > ___ > UNSUBSCRIBE or access ARSlist Archives at > www.arslist.org<http://www.arslist.org> > Platinum > Sponsor:rmisoluti...@verizon.net<mailto:sponsor%3armisoluti...@verizon.net> > ARSlist: "Where the Answers Are" > > _______________________________________________________________________________ > UNSUBSCRIBE or access ARSlist Archives at > www.arslist.org<http://www.arslist.org> > Platinum > Sponsor:rmisoluti...@verizon.net<mailto:sponsor%3armisoluti...@verizon.net> > ARSlist: "Where the Answers Are" > > > NOTICE: This email message is for the sole use of the intended recipient(s) > and may contain confidential and privileged information. Any unauthorized > review, use, disclosure or distribution is prohibited. If you are not the > intended recipient, please contact the sender by reply email and destroy all > copies of the original message. > > _______________________________________________________________________________ > UNSUBSCRIBE or access ARSlist Archives at > www.arslist.org<http://www.arslist.org> > Platinum > Sponsor:rmisoluti...@verizon.net<mailto:sponsor%3armisoluti...@verizon.net> > ARSlist: "Where the Answers Are" > _Platinum Sponsor: rmisoluti...@verizon.net ARSlist: "Where the Answers Are"_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor:rmisoluti...@verizon.net ARSlist: "Where the Answers Are"
