We're just trying to keep all of the servers identical.  It's easier long term 
to just have one standard build.

From: Action Request System discussion list(ARSList) 
[mailto:arslist@ARSLIST.ORG] On Behalf Of LJ LongWing
Sent: Tuesday, December 10, 2013 10:25 AM
To: arslist@ARSLIST.ORG
Subject: Re: Adding servers to the server group

**
William,
I can't verify this...but I'm not entirely sure you need to install ITSM on the 
reporting boxes....I honestly don't know for sure...but being the users won't 
actually be 'working' in this environment, they may just need a Remedy instance 
that can query the tables.

On Tue, Dec 10, 2013 at 8:41 AM, William Rentfrow 
<wrentf...@stratacominc.com<mailto:wrentf...@stratacominc.com>> wrote:
**
So we currently have 6 AR servers in a server group - I'm adding some more.

Two of the new servers will be solely to support reporting.

I'm sort of mulling my options.  I do not need them to be in the server group - 
at least in the sense of taking over any functions if a task goes down.  The 
only reason we are adding these is so we can change the # of records returned 
in a query to unlimited.  The users who use these servers will access them via 
a separate URL and separate MT servers.  For example, our normal users access 
it internally via something like http://remedy - our reporting users will 
access it via an URL like http://remedy_rptg.

These AR servers also connect  to the database in a slightly different way, 
using a defined service instead of a regular listener - this gives the DB the 
ability to throttle their queries, so they do not receive more than X% of the 
total Oracle RAC computing power (and hence can't slow down regular users).

So here's my rough plan - tell me if you'd do this differently (this is 7.6.04 
for AR/Apps running on SuSe Linux with Websphere and Oracle, if you need to 
know)


1.)    Install ARS, license, configure threads, etc

2.)    Install CMDB, ITSM, RKM, SLM, SRM using the environment variable "Skip" 
option method to avoid loading the app in the database.

3.)    Comment out the SLM and CMDB processes in the armonitor.con

4.)    Add them to the server group but have NO entries in the Server Group 
Operation Ranking form - the only real reason to do this is to disable 
escalations and admin functions, as well as making them "aware" that they are 
not the top dog in the SG.

5.)    Modify the ar.conf for all of servers and adding the IP-Name entries 
that are appropriate


William Rentfrow
wrentf...@stratacominc.com<mailto:wrentf...@stratacominc.com>
Office: 715-204-3061<tel:715-204-3061>
Cell: 715-398-5056<tel:715-398-5056>

_ARSlist: "Where the Answers Are" and have been for 20 years_

_ARSlist: "Where the Answers Are" and have been for 20 years_
________________________________
No virus found in this message.
Checked by AVG - www.avg.com<http://www.avg.com>
Version: 2014.0.4158 / Virus Database: 3658/6902 - Release Date: 12/08/13

_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
"Where the Answers Are, and have been for 20 years"

Reply via email to