Thanks for the replies! However, upon testing in our test env and turning on the api logs then calling a web service, it didn't show the CLIENT_TYPE entry in the log. Though I did find the following lines:
user xxxx from Webservice (protocol 17) at IP address xxxxxx container HPD_IncidentInterface_WS_Original from Webservice (protocol 17) at IP address xxxxxxx Regards, Kali -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Joe Martin D'Souza Sent: Tuesday, August 14, 2012 4:57 AM To: arslist@ARSLIST.ORG Subject: Re: How to check Remedy Logins that are using Web Service There you go.. its 34.. Thank you Matt.. This is the best way to determine the Client Type value.. Guides and manuals could have a typo but this file is the source of truth.. So 8 was actually the Web Server and not Web services.. I wonder when a Web server (8) would be actually used as a client type? Joe -----Original Message----- From: Matthew Perrault Sent: Monday, August 13, 2012 4:52 PM Newsgroups: public.remedy.arsystem.general To: arslist@ARSLIST.ORG Subject: Re: How to check Remedy Logins that are using Web Service From the AR.h file: #define AR_CLIENT_TYPE_UNKNOWN 0 #define AR_CLIENT_TYPE_PRE_50 1 /* Pre 5.0 ar client tools */ #define AR_CLIENT_TYPE_WAT 2 /* Windows admin tool */ #define AR_CLIENT_TYPE_WUT 3 /* Windows user tool */ #define AR_CLIENT_TYPE_WIP 4 /* Windows import tool */ #define AR_CLIENT_TYPE_DSO 5 /* Distributed server */ #define AR_CLIENT_TYPE_ODBC 6 /* ARODBC */ #define AR_CLIENT_TYPE_APPROVAL 7 /* Approval server */ #define AR_CLIENT_TYPE_WEB_SERVER 8 /* AR web server, waserver */ #define AR_CLIENT_TYPE_MID_TIER 9 /* Mid-tier 5.0 and later */ #define AR_CLIENT_TYPE_PALM_PILOT 10 /* Palm pilot */ #define AR_CLIENT_TYPE_FLASHBOARDS 11 /* Flashboards */ #define AR_CLIENT_TYPE_FLASHBOARDS_MID_TIER 12 /* Flashboards mid-tier */ #define AR_CLIENT_TYPE_EIE 13 /* Enterprise Integration */ /* Engine */ #define AR_CLIENT_TYPE_RELOAD 14 /* arreload */ #define AR_CLIENT_TYPE_CACHE 15 /* arcache */ #define AR_CLIENT_TYPE_DIST 16 /* ardist */ #define AR_CLIENT_TYPE_RUN_MACRO 17 /* runmacro */ #define AR_CLIENT_TYPE_MAIL 18 /* armaild/armailex */ #define AR_CLIENT_TYPE_IMPORT_CMD 19 /* arimportcmd */ #define AR_CLIENT_TYPE_REPORT_PLUGIN 20 /* Report creator plugin */ #define AR_CLIENT_TYPE_ALERT 21 /* Alert tool */ #define AR_CLIENT_TYPE_MAIL_DAEMON 22 /* New AR Mail Daemon, not armaild */ #define AR_CLIENT_TYPE_SIGNAL 23 /* arsignal */ #define AR_CLIENT_TYPE_DEBUGGER 24 /* debugger */ #define AR_CLIENT_TYPE_OBJSTR 25 /* object store API */ #define AR_CLIENT_TYPE_OBJSTR_SYNC 26 /* object store sync utility */ #define AR_CLIENT_TYPE_SERVER_ADMIN_PLUGIN 27 /* Server Admin plugin */ #define AR_CLIENT_TYPE_SIM_PUBLISHING_SERVER 28 /* bmc sim publishing server */ #define AR_CLIENT_TYPE_SIM_SME 29 /* bmc sim service model editor */ #define AR_CLIENT_TYPE_CMDB_ENGINE 30 /* cmdb engine */ #define AR_CLIENT_TYPE_CMDB_DRIVER 31 /* cmdb driver */ #define AR_CLIENT_TYPE_RECON_ENGINE 32 /* cmdb reconciliation engine */ #define AR_CLIENT_TYPE_ASSIGNMENT_ENGINE 33 /*Assignment Engine */ #define AR_CLIENT_TYPE_WEBSERVICE 34 /* Webservice client type */ -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Joe Martin D'Souza Sent: Monday, August 13, 2012 3:47 PM To: arslist@ARSLIST.ORG Subject: Re: How to check Remedy Logins that are using Web Service That’s what I was thinking too as most of the lower client types were already exhausted before WS was even available as a client type. One easy way to confirm whether it is 8 or 34 is to check the ar.h file that gets bundled with the AR API's if installed.. This file will have a list of all client type variables with its numbers in the body of that header file.. I do not have it handy right now or I would check it for you guys.. This file is how I check what a client type value should be usually when coding and I am not sure through memory what it is or may be.. But I think I agree with Fred that it could probably be 34 and not 8 as those low numbers were taken well before WS was a reality as far as the ARS is concerned.. Joe -----Original Message----- From: Mueller, Doug Sent: Monday, August 13, 2012 2:08 PM Newsgroups: public.remedy.arsystem.general To: arslist@ARSLIST.ORG Subject: Re: How to check Remedy Logins that are using Web Service Fred, Well, the code that the engineer looked up for me indicated 8. Now, maybe they looked up something wrong and it is 34. EITHER WAY, it is different for Web Services and interactive mid-tier traffic. I did think it was odd to be 8 since 8 was originally the client-type of an earlier incarnation of the web support (the "waserver" for the old timers on the list). So, it may be 8, it may be 34. The key is that now that you know there is a difference, you can look for it and key off of whichever value it turns out to be... Sorry about giving the wrong number if it is indeed 34 instead of 8. Doug Mueller -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Grooms, Frederick W Sent: Monday, August 13, 2012 11:02 AM To: arslist@ARSLIST.ORG Subject: Re: How to check Remedy Logins that are using Web Service You can find the complete list of BMC defined client types for your version in the ar.h file (search for AR_CLIENT_TYPE ) in the API directory include folder. I hate to disagree with "Mr. Doug", but I thought it was client type 34 Fred -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Longwing, LJ CTR MDA/IC Sent: Monday, August 13, 2012 12:56 PM To: arslist@ARSLIST.ORG Subject: Re: How to check Remedy Logins that are using Web Service Interesting. I thought that because WS calls came through the Mid-Tier server that it would also come in as 9....good to know. -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Mueller, Doug Sent: Monday, August 13, 2012 11:54 AM To: arslist@ARSLIST.ORG Subject: Re: How to check Remedy Logins that are using Web Service ** Kali, The CLIENT_TYPE will tell you where calls are coming from (if it is used). And, for web services, it is used. Client type 8 is the client type value for Web Services. Client type 9 would be from the mid-tier. And, there are many other client types for other components of the system. The client-type can be tested for in any server side workflow using the keyword $CLIENT_TYPE$. You can test for the web service client type. The client type is listed on the starting line of an API call in the API log if you want to look in the log to see it. It should be translated to words if the server has a mapping for it or if not, the index is listed. But, you should be able to tell which client type each API comes from. Any that say 0 mean that the program interacting with the server has not specified who they are - which means either a BMC program that did not set it or a custom program. I hope this helps you find the traffic you are looking for. Doug Mueller -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Kali Obsum Sent: Monday, August 13, 2012 1:55 AM To: arslist@ARSLIST.ORG Subject: How to check Remedy Logins that are using Web Service ** Hi, Is there any logs within Remedy 7.6.03 we can check to find which Remedy logins are creating tickets via WS or accessing any Remedy WS? Regards, Kali _______________________________________________________________________________ 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" _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are" NOTICE The information contained in this email is confidential. If you are not the intended recipient, you must not disclose or use the information in this email in any way. If you received it in error, please tell us immediately by return email and delete the document. We do not guarantee the integrity of any e-mails or attached files and are not responsible for any changes made to them by any other person. _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are"
