You do not need to run the upgrade option. Since you have cloned both the application and the database servers, all you would need to do is, massage the configuration files, and services to reflect the new server names wherever applicable. Do not forget massaging the armonitor file as well. That file will have old server references as well. You may need to touch the host file as well depending on how your network is configured.
Your second step would be to clean configuration data off any server references. Applications like AIE, SRM keep hard coded server references in the configuration data so if you have the AIE component installed as a part of CMDB, you will need to export the AIE configurations, and re-import them after cleaning the references. Export and import this data from the configuration utility using the export and import functions built there.. Ideally the workflow should be free of server references, but in the real world this hardly is ever true. So you might need to deal with cleaning server references, from the workflow, before you can really use the new pre-production/test environment. This may take you the longest time.. The easiest way to do this is to export all the def files to XML format, and look for the old server names both FQDN (do this first) and just the domain name after you look for FQDN's and replace these with "@". Also look for old IP addresses in the workflow and replace these with "@". I've seen numerous developers use IP addresses, to connect their development tool to the AR System leaving their workflow infested with server references by way of IP addresses. Do not really bother about licensing. Just install the new applicable licenses for the new server, the ARS will simply ignore the old licenses after it doesn't match that license with its new server name. If you really want to be anal about it (like I usually am), yes you can delete the license records of the old server. Cheers Joe -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[email protected]]on Behalf Of Frex Popo Sent: Tuesday, February 16, 2010 5:45 AM To: [email protected] Subject: Setting up a pre-production server. ** Dear arlisters, Anyone would like to share the steps/experience on how to set up a pre-production/test environment for ARS7.1/CMDB2.1/ITSM7.0.3. We have a server group consisting of two nodes (node1 passive and node2 active) pointing to the same database: DB: Database MS SQL 2005 (X64) ARS 7.1.0 Patch 004 OS: MS 2003 Enterprise Edition SP2 (X64) WebServer: IBM WebSphere Application Server/6.1 Mid-Tier: 7.1.0 Patch 004 OS: Windows Server 2003 Java Version: 1.5.0 Node1 has been cloned to a VM-Ware and about to do the same with the databse instance. My question is what's next? re-run the server installer and use the upgrade option? Massage the config files for all the remedy services or re-run the installers? How do you get rid of all the server group refernces in the databse? How about licensing? etc etc... The whole process is really to test the new 7.5 version. Many thansk in advance frex _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor:[email protected] ARSlist: "Where the Answers Are"
