Dear List

 

We are trying to set up a Server Group.  Below is our environment.  We
are running ARS 7.0.1 patch 3 on Sun Unix serverss with Solaris 9 with
and  Oracle 10.  DB #1 and DB #2 are remote databases.

 

In our development environment, the primary server is Server #1.  In our
production environment, the primary server is Server #2.  We have
another server that we are using for test, Server #3.  It will be part
of the production environment at the conclusion of our testing.  We have
different ar.conf files to point Server #3 to either the production or
the development databases.  Both Server #1 and server #2 are fully
licensed with an AR Server and AR User Floating licenses.  The floating
licenses have been generated with the hostid for Server #1 in
development and the hostid for Server #2 in production, each with a
server group name of sg1.  The license keys were also defined with
SERVERGROUP=sg1 in the License Key Information field.   Server #3 is
fully licensed with an AR Server license key.  

 

When we first brought up Server #3 as part of the development
environment using the ar.conf #1 file, we installed the same AR User
Floating license key we have on Server #1.  We checked the License Tab
under the Server Information menu item in the Admin tool and saw 3 fixed
write licenses and 5 floating write licenses corresponding to the
license keys we had installed.  We ran tests with users logging on to
both machines.  Each was able to see the data in the database.  Each
received warnings when the same records was being updated by moth.  It
appears to work as designed.

 

After testing in the development environment, we shut down Server #3 and
restarted it with the ar.conf file #2 to reflect the production
environment.  The server came up.  According to the Server Group logs,
Server #3 recognized it coming online and connecting to the Server
Group.  We still had the user floating license from Server #1 installed
on Server #3.  We deleted it and installed a key from Server #2.
However, when we went to check the licenses in the license tab, it
showed 3 fixed write licenses and 0 floating write licenses.  We tried
logging from both Server #2 and Server #3 with user floating licenses.
We were able to work on Server #2 but only got a floating read licenses
on Server #3.   We tried several combination but never could get the
floating write licenses to appear in the production environment.

 

We then shut down Server #3 and restarted it with ar.conf file #1 to put
it back into the development environment.  But we saw the same results
as in  production.  ARS is recognizing the server license but not the
floating licenses.  We have tried many difference combinations to get
ARS to recognize the floating licenses but we have not been successful

 

Has anyone had issues setting up a server group and floating write
licenses and could not get the user licenses to connect?  We feel we are
overlooking something simple.  But after a week of trial and error, we
are no closer to solving this than when we started.  Any ideas as to why
the licenses are not connecting?

 

 

Development Environment                         Production Environment

Primary Server = Server #1                          Primary Server =
Server2

Database = DB #1                                             Database =
DB #2

SERVERGROUP=sg1                                        SERVERGROUP=sg1

 

Test Server = Server 3

ar.conf for Development environment = ar.conf #1

ar.conf for Production environment = ar.conf #2

 

 

Dan Wangler,   Team Lead,  STARS Group

Phone: 214-567-8304; email: [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> 

Client/Server Services, IT Operations

Texas Instruments, Inc.

6500 Chase Oaks Blvd., MS 8401

Plano, Texas, 75023 

 

 

 

 

 


_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"

Reply via email to