If I get this right, you have server1 (192.168.1.1) and server2 (192.168.1.2), with a consolidation to server2.
Another DNS mapping after the cutover: 192.168.1.2 server1 (with server2 intact)
You may specify "IP-Name: server1" in the ar.conf with your Server-Name parameter as server2 (no change). That way all server ref for server1 and server2 will always get resolved to '@' i.e. the current connected to server. Your users may connect to server1 or 2, the ARS server will always resolve both the connections to itself.
Other than this if your network admins don't mind hardcoding IP addresses you might also want to specify server1 in server2's hosts file.
Regards, Vivake
On 8/25/06,
McKenzie, James J C-E LCMC HQISEC/L3 <[EMAIL PROTECTED]> wrote:
This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.
------_=_NextPart_001_01C6C87F.BA59ACDE
Content-Type: text/plain
Rick:
I would do an export of the server metadata (forms, workflow, applications,
menus, etc.) and do a search for the current server's name on it. That way
you will be ahead when you get to the new server and know what you have to
change over. I would NOT do this after the import as you would have to go
back and change information already on the new server.
Having done an emergency move of data taught me that lesson at 2 am.
James McKenzie
L-3 GSI
________________________________
From: Action Request System discussion list(ARSList)
[mailto:arslist@ARSLIST.ORG] On Behalf Of Rick Cook
Sent: Friday, August 25, 2006 12:40 PM
To: arslist@ARSLIST.ORG
Subject: Re: Moving to a New Server
**
One more thing - menus. Even if you migrate or export as server
independent, the server name may still be embedded. Easiest way to find the
problem children is to do a full export of the new server AFTER all of your
imports are done, then do a search for the old server name in the file.
There might be some table fields affected, too, and macros.
That's about all I can think of at the moment.
Rick
On 8/25/06, McKenzie, James J C-E LCMC HQISEC/L3
<[EMAIL PROTECTED]> wrote:
**
Chris:
You may want to look at internal server references and have them
point to the new server rather than te old. At some point you are going to
have to drop the old server's Name reference in DNS.
James McKenzie
L-3 GSI
________________________________
From: Action Request System discussion list(ARSList)
[mailto: arslist@ARSLIST.ORG] On Behalf Of Chris Cook
Sent: Friday, August 25, 2006 12:25 PM
To: arslist@ARSLIST.ORG <mailto: arslist@ARSLIST.ORG>
Subject:
**
No CP.
Thanks for bringing up the .ini file, I'd overlooked it. I think the
references might come forward to the new server, since the old DNS will
still exist and all form names/request ID's will stay the same. I'll do some
testing to determine what will need to change.
Thanks again
Christopher Cook
**
I agree with James, but in addition, if you're using Centralized
preferences, I think you could plug a server alias name in the client
settings that pointed to only the new server. Regardless, you'll also have
to clear out the Recently accessed forms, etc that reference the old server
name, unless you want to field 100 calls from users who don't know why they
can't access the application. If you're not using CP, you will probably
have to clear out some local ar.ini file settings that point to forms on the
old server.
Rick
On 8/25/06, McKenzie, James J C-E LCMC HQISEC/L3
<[EMAIL PROTECTED] < mailto: [EMAIL PROTECTED]> > wrote:
**
Chris:
If the user logs in with a Float license for both logins, two tokens
will be consumed instead of one.
Because of this, I would suggest migrating over the user base and
consolidating it too at or about the same time.
James McKenzie
L-3 GSI
________________________________
From: Action Request System discussion list(ARSList)
[mailto: arslist@ARSLIST.ORG < mailto:arslist@ARSLIST.ORG
<mailto:arslist@ARSLIST.ORG> > ] On Behalf Of Chris Cook
Sent: Friday, August 25, 2006 11:09 AM
To: arslist@ARSLIST.ORG < mailto:arslist@ARSLIST.ORG>
Subject:
**
Hi List -
I'm consolidating 2 ARS servers to 1.
Server 1 - ARS 5.1.2 + Custom applications
Server 2 - ARS 6.0 + ITSM applications.
'Server 1' apps will be migrated to 'Server 2' and 'Server 1'
decommissioned.
Due to hundreds of Crystal reports that run against 'Server 1', The
DNS 'Server 1' will point to 'Server 2' after the migration which allows the
reports to still run without modification.
Users log into both servers through the application shortcut. Anyone
know of user tool or licensing issues I could encounter having two servers
specified in the user tool account , that ultimately log the user into the
same server?
Thanks!
Christopher Cook
__20060125_______________________This posting was submitted with HTML in it___
