Anuj,

And is it absolutely business critical that the users perform large
searches? If not, consider setting the server not to run unqualified
searches, and limit the result list from the server to a hard limit of about
5 to 10 K records.. Bear in mind that if you set the server to run
unqualified searches, then any customization that you might have done that
runs unqualified searches might also have to be modified to add a
qualification even if it means a qualification like 1=1. Besides table
fields in a form that has search criteria's, you would also need to check
your qualifications on other objects like search menus or Active Links or
Filters/Escalations that may have unqualified searches in the Set Field or
Push Fields actions..

The solution, you are hoping doesn't exist in the Remedy world (to the best
of my knowledge). The server cannot be configured to only create or only
search. Having a large number of users would be a good business case for
your company to consider a load balanced solution even if you'll do not
currently have it set that way. It is a minimum impact change, in terms of
risks involved.

Yes there would be costs associated with it in terms of additional AR Server
licenses, hardware, implementation costs, etc. but having a large user base
justifies that doesn't it?

Joe
  -----Original Message-----
  From: Action Request System discussion list(ARSList)
[mailto:[email protected]]on Behalf Of Anuj DUA
  Sent: Thursday, July 08, 2010 1:34 AM
  To: [email protected]
  Subject: Re: Directing Search based reports to another ARS and DB


  **
  Hi Joe,



  Yes, our user base is very large.



  We have observed that when large search is fired on our production server,
then the performance deteriorates. Hence we want the search to be fired on
other ARS and DB (having backup of the production data).



  Moreover, we are not going for load balancer, we simply want that through
workflows we should be able to achieve this.



  With Regards,

  Anuj Dua



  From: Action Request System discussion list(ARSList)
[mailto:[email protected]] On Behalf Of Joe D'Souza
  Sent: Wednesday, July 07, 2010 8:03 PM
  To: [email protected]
  Subject: Re: Directing Search based reports to another ARS and DB



  **

  Anuj,



  Why would you want to do something like that? Are the number of concurrent
users on your system extremely large? What kind of a usage do you expect in
terms of numbers both total and concurrent??



  And even if you do have an extremely large user base, are you aware that
the creation threads on the ARS are different from the search threads? If
you have more than one server pointing to the same database, wouldn't you
rather configure them to be a part of a server group?



  An RPC call sent from a client doesn't get assigned to a Fast or a List
thread until the transaction hits the server, so it may not be possible to
direct this call from a load balancer configuration to one or the other
server based on what kind of a thread the server would assign this call to.



  Joe

    -----Original Message-----
    From: Action Request System discussion list(ARSList)
[mailto:[email protected]]on Behalf Of Anuj DUA
    Sent: Wednesday, July 07, 2010 4:19 AM
    To: [email protected]
    Subject: Directing Searchbased reports to another ARS and DB

    **

    Hello,



    We have a requirement to directing searchbased reports in remedy to
another server.



    For ex.

    1.        We have server A and server B

    2.       Both the server has ARS and DB installed.

    3.       We want user from server A to fire search to server B (with
data coming from server B)



    The objective of this exercise is to keep the Server A lighter to be
used only for creation of ticket and keeping server B for reporting only.



    Please suggest how to proceed on it.





    With Regards,

    Anuj Dua

_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
attend wwrug10 www.wwrug.com ARSlist: "Where the Answers Are"

Reply via email to