Was just checking. Another suggestion would be to use 2 separate Unix logins to start the services for accountability. Its not absolutely necessary to do so but would be good to have at some point especially if you would want 2 independent teams to use the 2 different instances for the purpose of administration.
Cheers Joe D'Souza -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] Behalf Of Howard Richter Sent: Wednesday, October 03, 2007 4:28 PM To: [email protected] Subject: Re: Building a temporary test server on the same box as development ** To all thanks. It sounds like I have the correct thought process and Joe I know I need new licenses for that server. When I said relicense, I meant it due to the fact that it will see the first servers licenses and I need to apply the new ones. Once again thanks to all. Howard On 10/3/07, Joe D'Souza <[EMAIL PROTECTED]> wrote: ** You will need to modify your armonitor.conf file too. What do you mean by relicense the server - reuse the development license? If so, that won't work. You will require a fresh license apart from the license you got for your development server. Each server license has a remedy server Id and you cannot have 2 Remedy servers with the same Id running on the same network, leave alone the same box. Joe D'Souza -----Original Message----- From: Action Request System discussion list(ARSList) [mailto: [EMAIL PROTECTED] Behalf Of Howard Richter Sent: Wednesday, October 03, 2007 10:38 AM To: [email protected] Subject: Building a temporary test server on the same box as development ** All, I need to build a temporary test server on the same box that development is on and I am going to try something to save a couple of days of work, but I am not sure it will work. My licenses were built with multi server enabled and I am on Solaris. 1. I was going to copy my binaries from my install directory to another directory. 2. Modify ar.conf and arsystem with the new directory name. 3. Copy /etc/arsystem/current server name to /etc/arsystem/new server name 4. Then point the server to another database copy of production And then at the end relicense the new server. Is there something missing? Should I just not go down this path and just do a full install and then copy the production database? As always thanks for your advice, -- Howard Richter Remedy ServiceDesk Manager CedarCrestone Managed Services Center __20060125_______________________This posting was submitted with HTML in it___ -- Howard Richter Remedy ServiceDesk Manager CedarCrestone Managed Services Center [EMAIL PROTECTED] No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.5.488 / Virus Database: 269.14.0/1046 - Release Date: 10/3/2007 10:08 AM _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
