Building a temporary test server on the same box as development

2007-10-03 Thread Howard Richter
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

Re: Building a temporary test server on the same box as development

2007-10-03 Thread Shyam Attavar
Make sure your development server and the new server you are setting up are not using the portmapper and connecting using specific ports for each of the servers. -- Shyam - Original Message - From: Howard Richter [EMAIL PROTECTED] Newsgroups: gmane.comp.crm.arsystem.general To:

Re: Building a temporary test server on the same box as development

2007-10-03 Thread Thad K Esser
How about the email engine install folder (/usr/ar/AREmail/servername) or config properties? Thad Esser Remedy Developer Argue for your limitations, and sure enough, they're yours.-- Richard Bach Shyam Attavar [EMAIL PROTECTED] Sent by: Action Request System discussion list(ARSList)

Re: Building a temporary test server on the same box as development

2007-10-03 Thread Joe D'Souza
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

Re: Building a temporary test server on the same box as development

2007-10-03 Thread Howard Richter
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,

Re: Building a temporary test server on the same box as development

2007-10-03 Thread Joe D'Souza
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