Hi,
You can check the $CLIENT-TYPE$, but in theory you can set this to any
number you like when you build your API-program. For example RRR|Chive
uses $CLIENT-TYPE$=6666 to make it easier to do special filter handling
for that API-program.
If you turn on API/ESCL/FLTR/SQL-logging into the same file, you should be
able to find the bulky queries easy enough. I find that the user name is
the easiest way to work from in these cases. You will also see
IP-addresses of the calling system. Find the user, and talk to that
person.
Remedy is not really designed to prevent bad queries when users do ad-hoc
searching. It is hard to do both in the normal client and in an
API-program.
As a general rule, I always design my applications to allow access from
any type of client. Be that Mid-Tier, AR User, Web-Services or any
API-program. It should be impossible to break your system.
But on the other hand, bad searches are hard to prevent...
Best Regards - Misi, RRR AB, http://www.rrr.se (ARSList MVP 2011)
Products from RRR Scandinavia (Best R.O.I. Award at WWRUG10/11):
* RRR|License - Not enough Remedy licenses? Save money by optimizing.
* RRR|Log - Performance issues or elusive bugs? Analyze your Remedy logs.
Find these products, and many free tools and utilities, at http://rrr.se.
> Hello everyone,
>
> Is there a way to get the type of client that is signing to AR System? I
> would like to implement something like this: if the client that is trying
> to access AR Server is a custom API program (client is not Mid Tier / AR
> User) then the system should not allow the program to sign in. There is
> probably an offending API program that is executing large queries and
> causing performance problems, so we would like to detect which is the
> client that is causing this behaviour
>
> Thank you and Regards,
>
> Mauricio
>
> _______________________________________________________________________________
> UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
> attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are"
>
_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are"
