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 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"
How to check Remedy Logins that are using Web Service
John, It modifies the IP address AR System reports to the AREA plugins, which doesn't seem particularly intelligent. It took me about 100 SSO Plugin deployments before the penny dropped. John -- SSO Plugin for BMC and HP ITSM. http://www.javasystemsolutions.com/jss/ssoplugin ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are"
Re: How to check Remedy Logins that are using Web Service
The WS log at the mid-tier is the only way I see. But, let's talk the experts... Jose Manuel Huerta http://theremedyforit.com/ On Mon, Aug 13, 2012 at 10:54 AM, Kali Obsum wrote: > ** > > 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? > ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are"
Re: How to check Remedy Logins that are using Web Service
Kali, The WS created tickets are really just another 'client' of the Mid-Tier...so I can't think of anything outside of if your Mid-Tier is setup for anonymous authentication with a specific user, you could trace those users and such, or if you have specific interfaces you could write workflow on those forms to keep track of the records going through there. -Original Message- From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Kali Obsum Sent: Monday, August 13, 2012 2: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 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. _attend WWRUG12 www.wwrug.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"
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 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 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. _attend WWRUG12 www.wwrug.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"
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 9good 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 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 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. _attend WWRUG12 www.wwrug.com ARSlist: "Where the Answers Are"_ _attend WWRUG12 www.wwrug.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"
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 9good 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 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"
Re: How to check Remedy Logins that are using Web Service
LJ, Yeah, but sometimes we think ahead We do know that the traffic arriving is from a browser interaction or from a web service. So, we set the client type differently so that you can know which it is. This is just like we set the client type of the Web Reporting (at least we are supposed to be setting it) to 6 (may be tagged in the ar.h file as CLIENT_TYPE_ODBC) instead of 9 (for mid-tier). This way, you can tell that the interaction is for the web reporting engine rather than for the mid-tier interaction in general. So, there are three different client types that all come from the "mid-tier" -- mid-tier interactive use -- 9 -- web reporting -- 6 -- web services -- 8 This allows you to know to a finer level of detail what subsystem of the mid-tier is causing the interaction and there is value in differentiating these three aspects. Doug Mueller -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 10:56 AM 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 9good 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 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 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. _attend WWRUG12 www.wwrug.com ARSlist: "Where the Answers Are"_ _attend WWRUG12 www.wwrug.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"
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 9good 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 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" ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are"
Re: How to check Remedy Logins that are using Web Service
Hi, This might be a little off topic, but it is not in ar.h, so... If you use RRR|Chive, the $CLIENT-TYPE$ is set to . Makes it easy to add or disable workflow for various clients. Best Regards - Misi, RRR AB, http://rrr.se > 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 9good 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 > > > 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" > ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are"
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 9good 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"
Re: How to check Remedy Logins that are using Web Service
It's not in there?? That's a little surprising as it should have technically been a separate client type.. Maybe it should be something that should be flagged up for enhancement so it can be recognized as a separate individual client - its not unknown so cant be 0. Neither can it be considered to be the Mid-Tier although the MT is used as a backbone to support WS's.. I wonder if anyone could run a quick test to see what the WS Client Type gets reported as.. Joe -Original Message- From: Misi Mladoniczky Sent: Monday, August 13, 2012 2:26 PM Newsgroups: public.remedy.arsystem.general To: arslist@ARSLIST.ORG Subject: Re: How to check Remedy Logins that are using Web Service Hi, This might be a little off topic, but it is not in ar.h, so... If you use RRR|Chive, the $CLIENT-TYPE$ is set to . Makes it easy to add or disable workflow for various clients. Best Regards - Misi, RRR AB, http://rrr.se 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 9good 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"
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_ODBC6 /* ARODBC */ #define AR_CLIENT_TYPE_APPROVAL7 /* Approval server */ #define AR_CLIENT_TYPE_WEB_SERVER 8 /* AR web server, waserver */ #define AR_CLIENT_TYPE_MID_TIER9 /* Mid-tier 5.0 and later */ #define AR_CLIENT_TYPE_PALM_PILOT 10 /* Palm pilot */ #define AR_CLIENT_TYPE_FLASHBOARDS11 /* Flashboards */ #define AR_CLIENT_TYPE_FLASHBOARDS_MID_TIER 12 /* Flashboards mid-tier */ #define AR_CLIENT_TYPE_EIE13 /* 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_DAEMON22 /* 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_SYNC26 /* object store sync utility */ #define AR_CLIENT_TYPE_SERVER_ADMIN_PLUGIN27 /* Server Admin plugin */ #define AR_CLIENT_TYPE_SIM_PUBLISHING_SERVER 28 /* bmc sim publishing server */ #define AR_CLIENT_TYPE_SIM_SME29 /* bmc sim service model editor */ #define AR_CLIENT_TYPE_CMDB_ENGINE30 /* cmdb engine */ #define AR_CLIENT_TYPE_CMDB_DRIVER31 /* 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 wi
Re: How to check Remedy Logins that are using Web Service
Its 34. -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:52 PM To: arslist@ARSLIST.ORG Subject: Re: How to check Remedy Logins that are using Web Service It's not in there?? That's a little surprising as it should have technically been a separate client type.. Maybe it should be something that should be flagged up for enhancement so it can be recognized as a separate individual client - its not unknown so cant be 0. Neither can it be considered to be the Mid-Tier although the MT is used as a backbone to support WS's.. I wonder if anyone could run a quick test to see what the WS Client Type gets reported as.. Joe -Original Message- From: Misi Mladoniczky Sent: Monday, August 13, 2012 2:26 PM Newsgroups: public.remedy.arsystem.general To: arslist@ARSLIST.ORG Subject: Re: How to check Remedy Logins that are using Web Service Hi, This might be a little off topic, but it is not in ar.h, so... If you use RRR|Chive, the $CLIENT-TYPE$ is set to . Makes it easy to add or disable workflow for various clients. Best Regards - Misi, RRR AB, http://rrr.se > 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 9good 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"
Re: How to check Remedy Logins that are using Web Service
Just wondering - any reason why BMC does not have an external facing version of their Javadoc??? I always seem to search and find it on JavaSystemSolutions site - but never on BMC. From: http://www.javasystemsolutions.com/documentation/thirdparty/arapi/constant-values.html#com.remedy.arsys.api.Constants.AR_FUNCTION_LENGTHC public static final int AR_CLIENT_TYPE_ALERT21 public static final int AR_CLIENT_TYPE_APPROVAL 7 public static final int AR_CLIENT_TYPE_CACHE15 public static final int AR_CLIENT_TYPE_CHANGE_ID4009 public static final int AR_CLIENT_TYPE_CHANGE_SEL 4008 public static final int AR_CLIENT_TYPE_DISPATCHER 4001 public static final int AR_CLIENT_TYPE_DIST 16 public static final int AR_CLIENT_TYPE_DRIVER 4000 public static final int AR_CLIENT_TYPE_DSO 5 public static final int AR_CLIENT_TYPE_EIE 13 public static final int AR_CLIENT_TYPE_END_OF_PRODUCT 3999 public static final int AR_CLIENT_TYPE_END_OF_RESERVED_RANGE5000 public static final int AR_CLIENT_TYPE_FLASHBOARDS 11 public static final int AR_CLIENT_TYPE_FLASHBOARDS_MID_TIER 12 public static final int AR_CLIENT_TYPE_HELP 4002 public static final int AR_CLIENT_TYPE_IMPORT_CMD 19 public static final int AR_CLIENT_TYPE_JANITOR 4003 public static final int AR_CLIENT_TYPE_MAIL 18 public static final int AR_CLIENT_TYPE_MAIL_DAEMON 22 public static final int AR_CLIENT_TYPE_MENU 4004 public static final int AR_CLIENT_TYPE_MID_TIER 9 public static final int AR_CLIENT_TYPE_ODBC 6 public static final int AR_CLIENT_TYPE_PALM_PILOT 10 public static final int AR_CLIENT_TYPE_PRE_50 1 public static final int AR_CLIENT_TYPE_RELOAD 14 public static final int AR_CLIENT_TYPE_REPORT_PLUGIN20 public static final int AR_CLIENT_TYPE_RUN_MACRO17 public static final int AR_CLIENT_TYPE_SIM_PUBLISHING_SERVER28 public static final int AR_CLIENT_TYPE_SIM_SME 29 public static final int AR_CLIENT_TYPE_SQLED4007 public static final int AR_CLIENT_TYPE_STRUCT 4005 public static final int AR_CLIENT_TYPE_TEXT 4006 public static final int AR_CLIENT_TYPE_UNKNOWN 0 public static final int AR_CLIENT_TYPE_UNPRODUCTIZED_START 4000 public static final int AR_CLIENT_TYPE_WAT 2 public static final int AR_CLIENT_TYPE_WEB_SERVER 8 public static final int AR_CLIENT_TYPE_WEBSERVICE 34 public static final int AR_CLIENT_TYPE_WIP 4 public static final int AR_CLIENT_TYPE_WUT 3 -John On Aug 13, 2012, at 3:47 PM, Joe Martin D'Souza wrote: 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
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_ODBC6 /* ARODBC */ #define AR_CLIENT_TYPE_APPROVAL7 /* Approval server */ #define AR_CLIENT_TYPE_WEB_SERVER 8 /* AR web server, waserver */ #define AR_CLIENT_TYPE_MID_TIER9 /* Mid-tier 5.0 and later */ #define AR_CLIENT_TYPE_PALM_PILOT 10 /* Palm pilot */ #define AR_CLIENT_TYPE_FLASHBOARDS11 /* Flashboards */ #define AR_CLIENT_TYPE_FLASHBOARDS_MID_TIER 12 /* Flashboards mid-tier */ #define AR_CLIENT_TYPE_EIE13 /* 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_DAEMON22 /* 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_SYNC26 /* object store sync utility */ #define AR_CLIENT_TYPE_SERVER_ADMIN_PLUGIN27 /* Server Admin plugin */ #define AR_CLIENT_TYPE_SIM_PUBLISHING_SERVER 28 /* bmc sim publishing server */ #define AR_CLIENT_TYPE_SIM_SME29 /* bmc sim service model editor */ #define AR_CLIENT_TYPE_CMDB_ENGINE30 /* cmdb engine */ #define AR_CLIENT_TYPE_CMDB_DRIVER31 /* 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
Re: How to check Remedy Logins that are using Web Service
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 from Webservice (protocol 17) at IP address xx container HPD_IncidentInterface_WS_Original from Webservice (protocol 17) at IP address xxx 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_ODBC6 /* ARODBC */ #define AR_CLIENT_TYPE_APPROVAL7 /* Approval server */ #define AR_CLIENT_TYPE_WEB_SERVER 8 /* AR web server, waserver */ #define AR_CLIENT_TYPE_MID_TIER9 /* Mid-tier 5.0 and later */ #define AR_CLIENT_TYPE_PALM_PILOT 10 /* Palm pilot */ #define AR_CLIENT_TYPE_FLASHBOARDS11 /* Flashboards */ #define AR_CLIENT_TYPE_FLASHBOARDS_MID_TIER 12 /* Flashboards mid-tier */ #define AR_CLIENT_TYPE_EIE13 /* 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_DAEMON22 /* 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_SYNC26 /* object store sync utility */ #define AR_CLIENT_TYPE_SERVER_ADMIN_PLUGIN27 /* Server Admin plugin */ #define AR_CLIENT_TYPE_SIM_PUBLISHING_SERVER 28 /* bmc sim publishing server */ #define AR_CLIENT_TYPE_SIM_SME29 /* bmc sim service model editor */ #define AR_CLIENT_TYPE_CMDB_ENGINE30 /* cmdb engine */ #define AR_CLIENT_TYPE_CMDB_DRIVER31 /* 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
Re: How to check Remedy Logins that are using Web Service
Set that value to a hidden field Kali... Create a hidden field of an integer type, or character, I think it should not matter as the system automatically typecasts it.. Then use a filter to set that field in a set field action that ALWAYS fires, to set the keyword $CLIENT-TYPE$ value into it.. That way you will get all records whose value for that field is 34. You may need to index that field if you would be frequently running searches to find records that have a Client type of 34.. Joe -Original Message- From: Kali Obsum Sent: Tuesday, August 14, 2012 4:08 AM Newsgroups: public.remedy.arsystem.general To: arslist@ARSLIST.ORG Subject: Re: How to check Remedy Logins that are using Web Service 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 from Webservice (protocol 17) at IP address xx container HPD_IncidentInterface_WS_Original from Webservice (protocol 17) at IP address xxx 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_ODBC6 /* ARODBC */ #define AR_CLIENT_TYPE_APPROVAL7 /* Approval server */ #define AR_CLIENT_TYPE_WEB_SERVER 8 /* AR web server, waserver */ #define AR_CLIENT_TYPE_MID_TIER9 /* Mid-tier 5.0 and later */ #define AR_CLIENT_TYPE_PALM_PILOT 10 /* Palm pilot */ #define AR_CLIENT_TYPE_FLASHBOARDS11 /* Flashboards */ #define AR_CLIENT_TYPE_FLASHBOARDS_MID_TIER 12 /* Flashboards mid-tier */ #define AR_CLIENT_TYPE_EIE13 /* 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_DAEMON22 /* 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_SYNC26 /* object store sync utility */ #define AR_CLIENT_TYPE_SERVER_ADMIN_PLUGIN27 /* Server Admin plugin */ #define AR_CLIENT_TYPE_SIM_PUBLISHING_SERVER 28 /* bmc sim publishing server */ #define AR_CLIENT_TYPE_SIM_SME29 /* bmc sim service model editor */ #define AR_CLIENT_TYPE_CMDB_ENGINE30 /* cmdb engine */ #define AR_CLIENT_TYPE_CMDB_DRIVER31 /* 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
Re: How to check Remedy Logins that are using Web Service
Just to be clear... Yes, the Webservice client type is 34. The search that was done for me did a partial match (left off SERVICE) and found the wrong match. The client type of 8 was for the waserver -- an earlier version of the mid-tier. It is no longer used -- since version 7.0 or so. So, you will not find client type of 8 being used by any current client. Again, sorry for the confusion in the number. But, what is important is the fact that the Client Type value can be used to tell what program the activity is coming from when you are trying to determine that or when you need to run different workflow based on where the activity is from. So, it is mid-tier is 9 and web service is 34. Doug Mueller -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 1:57 PM 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_ODBC6 /* ARODBC */ #define AR_CLIENT_TYPE_APPROVAL7 /* Approval server */ #define AR_CLIENT_TYPE_WEB_SERVER 8 /* AR web server, waserver */ #define AR_CLIENT_TYPE_MID_TIER9 /* Mid-tier 5.0 and later */ #define AR_CLIENT_TYPE_PALM_PILOT 10 /* Palm pilot */ #define AR_CLIENT_TYPE_FLASHBOARDS11 /* Flashboards */ #define AR_CLIENT_TYPE_FLASHBOARDS_MID_TIER 12 /* Flashboards mid-tier */ #define AR_CLIENT_TYPE_EIE13 /* 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_DAEMON22 /* 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_SYNC26 /* object store sync utility */ #define AR_CLIENT_TYPE_SERVER_ADMIN_PLUGIN27 /* Server Admin plugin */ #define AR_CLIENT_TYPE_SIM_PUBLISHING_SERVER 28 /* bmc sim publishing server */ #define AR_CLIENT_TYPE_SIM_SME29 /* bmc sim service model editor */ #define AR_CLIENT_TYPE_CMDB_ENGINE30 /* cmdb engine */ #define AR_CLIENT_TYPE_CMDB_DRIVER31 /* 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
Re: How to check Remedy Logins that are using Web Service
Doug, Wondering -- does the server do anything different based on the client-id? Or is it all just for info? -John On Wed, Aug 15, 2012 at 7:06 AM, Mueller, Doug wrote: > Just to be clear... > > Yes, the Webservice client type is 34. The search that was done for me > did a > partial match (left off SERVICE) and found the wrong match. > > The client type of 8 was for the waserver -- an earlier version of the > mid-tier. It > is no longer used -- since version 7.0 or so. So, you will not find > client type of > 8 being used by any current client. > > Again, sorry for the confusion in the number. > > But, what is important is the fact that the Client Type value can be used > to tell > what program the activity is coming from when you are trying to determine > that or > when you need to run different workflow based on where the activity is > from. > > So, it is mid-tier is 9 and web service is 34. > > Doug Mueller > > -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 1:57 PM > 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_ODBC6 /* ARODBC */ > #define AR_CLIENT_TYPE_APPROVAL7 /* Approval server */ > #define AR_CLIENT_TYPE_WEB_SERVER 8 /* AR web server, > waserver > */ > #define AR_CLIENT_TYPE_MID_TIER9 /* Mid-tier 5.0 and later > */ > #define AR_CLIENT_TYPE_PALM_PILOT 10 /* Palm pilot */ > #define AR_CLIENT_TYPE_FLASHBOARDS11 /* Flashboards */ > #define AR_CLIENT_TYPE_FLASHBOARDS_MID_TIER 12 /* Flashboards mid-tier > */ > #define AR_CLIENT_TYPE_EIE13 /* 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_DAEMON22 /* 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_SYNC26 /* object store sync > utility */ > #define AR_CLIENT_TYPE_SERVER_ADMIN_PLUGIN27 /* Server Admin plugin */ > #define AR_CLIENT_TYPE_SIM_PUBLISHING_SERVER 28 /* bmc sim publishing > server */ > #define AR_CLIENT_TYPE_SIM_SME29 /* bmc sim service model > editor */ > #define AR_CLIENT_TYPE_CMDB_ENGINE30 /* cmdb engine */ > #define AR_CLIENT_TYPE_CMDB_DRIVER31 /* 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 >
OT: Externally available doc (was: How to check Remedy Logins that are using Web Service)
Currently, BMC Legal designates BMC documentation as intellectual property that is only available to customers with a valid Support contract. Thus it is protected behind Support Central and not publicly available. A change in this interpretation is being considered (for about 2 years now). If it does change, I'll let the list know. -David J. Easter Manager of Product Management, AR System BSM & Atrium Solutions Management BMC Software, Inc. The opinions, statements, and/or suggested courses of action expressed in this E-mail do not necessarily reflect those of BMC Software, Inc. My voluntary participation in this forum is not intended to convey a role as a spokesperson, liaison or public relations representative for BMC Software, Inc. -Original Message- From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of John Sundberg Sent: Monday, August 13, 2012 1:54 PM To: arslist@ARSLIST.ORG Subject: Re: How to check Remedy Logins that are using Web Service Just wondering - any reason why BMC does not have an external facing version of their Javadoc??? I always seem to search and find it on JavaSystemSolutions site - but never on BMC. From: http://www.javasystemsolutions.com/documentation/thirdparty/arapi/constant-values.html#com.remedy.arsys.api.Constants.AR_FUNCTION_LENGTHC public static final int AR_CLIENT_TYPE_ALERT21 public static final int AR_CLIENT_TYPE_APPROVAL 7 public static final int AR_CLIENT_TYPE_CACHE15 public static final int AR_CLIENT_TYPE_CHANGE_ID4009 public static final int AR_CLIENT_TYPE_CHANGE_SEL 4008 public static final int AR_CLIENT_TYPE_DISPATCHER 4001 public static final int AR_CLIENT_TYPE_DIST 16 public static final int AR_CLIENT_TYPE_DRIVER 4000 public static final int AR_CLIENT_TYPE_DSO 5 public static final int AR_CLIENT_TYPE_EIE 13 public static final int AR_CLIENT_TYPE_END_OF_PRODUCT 3999 public static final int AR_CLIENT_TYPE_END_OF_RESERVED_RANGE5000 public static final int AR_CLIENT_TYPE_FLASHBOARDS 11 public static final int AR_CLIENT_TYPE_FLASHBOARDS_MID_TIER 12 public static final int AR_CLIENT_TYPE_HELP 4002 public static final int AR_CLIENT_TYPE_IMPORT_CMD 19 public static final int AR_CLIENT_TYPE_JANITOR 4003 public static final int AR_CLIENT_TYPE_MAIL 18 public static final int AR_CLIENT_TYPE_MAIL_DAEMON 22 public static final int AR_CLIENT_TYPE_MENU 4004 public static final int AR_CLIENT_TYPE_MID_TIER 9 public static final int AR_CLIENT_TYPE_ODBC 6 public static final int AR_CLIENT_TYPE_PALM_PILOT 10 public static final int AR_CLIENT_TYPE_PRE_50 1 public static final int AR_CLIENT_TYPE_RELOAD 14 public static final int AR_CLIENT_TYPE_REPORT_PLUGIN20 public static final int AR_CLIENT_TYPE_RUN_MACRO17 public static final int AR_CLIENT_TYPE_SIM_PUBLISHING_SERVER28 public static final int AR_CLIENT_TYPE_SIM_SME 29 public static final int AR_CLIENT_TYPE_SQLED4007 public static final int AR_CLIENT_TYPE_STRUCT 4005 public static final int AR_CLIENT_TYPE_TEXT 4006 public static final int AR_CLIENT_TYPE_UNKNOWN 0 public static final int AR_CLIENT_TYPE_UNPRODUCTIZED_START 4000 public static final int AR_CLIENT_TYPE_WAT 2 public static final int AR_CLIENT_TYPE_WEB_SERVER 8 public static final int AR_CLIENT_TYPE_WEBSERVICE 34 public static final int AR_CLIENT_TYPE_WIP 4 public static final int AR_CLIENT_TYPE_WUT 3 -John On Aug 13, 2012, at 3:47 PM, Joe Martin D'Souza wrote: 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
Re: OT: Externally available doc (was: How to check Remedy Logins that are using Web Service)
Ok thx for info. If they are looking for votes - I vote the API should be openly documented and marketed and pushed to the larger community. I think it would be a positive for BMC ITSM/ Remedy to work easily with the bigger environment. And side note - I can think of ZERO that would be lost by BMC by making it available. Oh - except for the trade secret that BMC uses integers for their Status field. -John Sent from my iPhone On Aug 16, 2012, at 6:06 PM, "Easter, David" wrote: > Currently, BMC Legal designates BMC documentation as intellectual property > that is only available to customers with a valid Support contract. Thus it > is protected behind Support Central and not publicly available. > > A change in this interpretation is being considered (for about 2 years now). > If it does change, I'll let the list know. > > -David J. Easter > Manager of Product Management, AR System > BSM & Atrium Solutions Management > BMC Software, Inc. > > The opinions, statements, and/or suggested courses of action expressed in > this E-mail do not necessarily reflect those of BMC Software, Inc. My > voluntary participation in this forum is not intended to convey a role as a > spokesperson, liaison or public relations representative for BMC Software, > Inc. > -Original Message- > From: Action Request System discussion list(ARSList) > [mailto:arslist@ARSLIST.ORG] On Behalf Of John Sundberg > Sent: Monday, August 13, 2012 1:54 PM > To: arslist@ARSLIST.ORG > Subject: Re: How to check Remedy Logins that are using Web Service > > Just wondering - any reason why BMC does not have an external facing version > of their Javadoc??? > I always seem to search and find it on JavaSystemSolutions site - but never > on BMC. > > From: > http://www.javasystemsolutions.com/documentation/thirdparty/arapi/constant-values.html#com.remedy.arsys.api.Constants.AR_FUNCTION_LENGTHC > > > > public static final intAR_CLIENT_TYPE_ALERT21 > public static final intAR_CLIENT_TYPE_APPROVAL7 > public static final intAR_CLIENT_TYPE_CACHE15 > public static final intAR_CLIENT_TYPE_CHANGE_ID4009 > public static final intAR_CLIENT_TYPE_CHANGE_SEL4008 > public static final intAR_CLIENT_TYPE_DISPATCHER4001 > public static final intAR_CLIENT_TYPE_DIST16 > public static final intAR_CLIENT_TYPE_DRIVER4000 > public static final intAR_CLIENT_TYPE_DSO5 > public static final intAR_CLIENT_TYPE_EIE13 > public static final intAR_CLIENT_TYPE_END_OF_PRODUCT3999 > public static final intAR_CLIENT_TYPE_END_OF_RESERVED_RANGE5000 > public static final intAR_CLIENT_TYPE_FLASHBOARDS11 > public static final intAR_CLIENT_TYPE_FLASHBOARDS_MID_TIER12 > public static final intAR_CLIENT_TYPE_HELP4002 > public static final intAR_CLIENT_TYPE_IMPORT_CMD19 > public static final intAR_CLIENT_TYPE_JANITOR4003 > public static final intAR_CLIENT_TYPE_MAIL18 > public static final intAR_CLIENT_TYPE_MAIL_DAEMON22 > public static final intAR_CLIENT_TYPE_MENU4004 > public static final intAR_CLIENT_TYPE_MID_TIER9 > public static final intAR_CLIENT_TYPE_ODBC6 > public static final intAR_CLIENT_TYPE_PALM_PILOT10 > public static final intAR_CLIENT_TYPE_PRE_501 > public static final intAR_CLIENT_TYPE_RELOAD14 > public static final intAR_CLIENT_TYPE_REPORT_PLUGIN20 > public static final intAR_CLIENT_TYPE_RUN_MACRO17 > public static final intAR_CLIENT_TYPE_SIM_PUBLISHING_SERVER28 > public static final intAR_CLIENT_TYPE_SIM_SME29 > public static final intAR_CLIENT_TYPE_SQLED4007 > public static final intAR_CLIENT_TYPE_STRUCT4005 > public static final intAR_CLIENT_TYPE_TEXT4006 > public static final intAR_CLIENT_TYPE_UNKNOWN0 > public static final intAR_CLIENT_TYPE_UNPRODUCTIZED_START4000 > public static final intAR_CLIENT_TYPE_WAT2 > public static final intAR_CLIENT_TYPE_WEB_SERVER8 > public static final intAR_CLIENT_TYPE_WEBSERVICE34 > public static final intAR_CLIENT_TYPE_WIP4 > public static final intAR_CLIENT_TYPE_WUT3 > > > > > -John > > > > > On Aug 13, 2012, at 3:47 PM, Joe Martin D'Souza wrote: > > 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
Re: OT: Externally available doc (was: How to check Remedy Logins that are using Web Service)
http://theremedyforit.com/2011/12/the-secret-documents-of-bmc/ Jose Manuel Huerta http://theremedyforit.com/ On Fri, Aug 17, 2012 at 2:51 AM, John Sundberg < john.sundb...@kineticdata.com> wrote: > Ok thx for info. > > If they are looking for votes - I vote the API should be openly documented > and marketed and pushed to the larger community. I think it would be a > positive for BMC ITSM/ Remedy to work easily with the bigger environment. > > And side note - I can think of ZERO that would be lost by BMC by making it > available. > > Oh - except for the trade secret that BMC uses integers for their Status > field. > > > -John > > Sent from my iPhone > > On Aug 16, 2012, at 6:06 PM, "Easter, David" wrote: > > > Currently, BMC Legal designates BMC documentation as intellectual > property that is only available to customers with a valid Support contract. > Thus it is protected behind Support Central and not publicly available. > > > > A change in this interpretation is being considered (for about 2 years > now). If it does change, I'll let the list know. > > > > -David J. Easter > > Manager of Product Management, AR System > > BSM & Atrium Solutions Management > > BMC Software, Inc. > > > > The opinions, statements, and/or suggested courses of action expressed > in this E-mail do not necessarily reflect those of BMC Software, Inc. My > voluntary participation in this forum is not intended to convey a role as a > spokesperson, liaison or public relations representative for BMC Software, > Inc. > > -Original Message- > > From: Action Request System discussion list(ARSList) [mailto: > arslist@ARSLIST.ORG] On Behalf Of John Sundberg > > Sent: Monday, August 13, 2012 1:54 PM > > To: arslist@ARSLIST.ORG > > Subject: Re: How to check Remedy Logins that are using Web Service > > > > Just wondering - any reason why BMC does not have an external facing > version of their Javadoc??? > > I always seem to search and find it on JavaSystemSolutions site - but > never on BMC. > > > > From: > http://www.javasystemsolutions.com/documentation/thirdparty/arapi/constant-values.html#com.remedy.arsys.api.Constants.AR_FUNCTION_LENGTHC > > > > > > > > public static final intAR_CLIENT_TYPE_ALERT21 > > public static final intAR_CLIENT_TYPE_APPROVAL7 > > public static final intAR_CLIENT_TYPE_CACHE15 > > public static final intAR_CLIENT_TYPE_CHANGE_ID4009 > > public static final intAR_CLIENT_TYPE_CHANGE_SEL4008 > > public static final intAR_CLIENT_TYPE_DISPATCHER4001 > > public static final intAR_CLIENT_TYPE_DIST16 > > public static final intAR_CLIENT_TYPE_DRIVER4000 > > public static final intAR_CLIENT_TYPE_DSO5 > > public static final intAR_CLIENT_TYPE_EIE13 > > public static final intAR_CLIENT_TYPE_END_OF_PRODUCT3999 > > public static final intAR_CLIENT_TYPE_END_OF_RESERVED_RANGE5000 > > public static final intAR_CLIENT_TYPE_FLASHBOARDS11 > > public static final intAR_CLIENT_TYPE_FLASHBOARDS_MID_TIER12 > > public static final intAR_CLIENT_TYPE_HELP4002 > > public static final intAR_CLIENT_TYPE_IMPORT_CMD19 > > public static final intAR_CLIENT_TYPE_JANITOR4003 > > public static final intAR_CLIENT_TYPE_MAIL18 > > public static final intAR_CLIENT_TYPE_MAIL_DAEMON22 > > public static final intAR_CLIENT_TYPE_MENU4004 > > public static final intAR_CLIENT_TYPE_MID_TIER9 > > public static final intAR_CLIENT_TYPE_ODBC6 > > public static final intAR_CLIENT_TYPE_PALM_PILOT10 > > public static final intAR_CLIENT_TYPE_PRE_501 > > public static final intAR_CLIENT_TYPE_RELOAD14 > > public static final intAR_CLIENT_TYPE_REPORT_PLUGIN20 > > public static final intAR_CLIENT_TYPE_RUN_MACRO17 > > public static final intAR_CLIENT_TYPE_SIM_PUBLISHING_SERVER28 > > public static final intAR_CLIENT_TYPE_SIM_SME29 > > public static final intAR_CLIENT_TYPE_SQLED4007 > > public static final intAR_CLIENT_TYPE_STRUCT4005 > > public static final intAR_CLIENT_TYPE_TEXT4006 > > public static final intAR_CLIENT_TYPE_UNKNOWN0 > > public static final intAR_CLIENT_TYPE_UNPRODUCTIZED_START4000 > > public static final intAR_CLIENT_TYPE_WAT2 > > public static final intAR_CLIENT_TYPE_WEB_SERVER8 > > public static final intAR_CLIENT_TYPE_WEBSERVICE34 > > public static final intAR_CLIENT_TYPE
Re: OT: Externally available doc (was: How to check Remedy Logins that are using Web Service)
Jose, Please do us a favor and explain links when you post them. With the amount of spam email many of us get with just a link, many may just delete the email. In addition. It makes it easier for people to decide if they want to open the link if they know it's not spam. Dave On Aug 18, 2012, at 10:36 AM, "Jose Manuel Huerta Guillén" mailto:arsl...@theremedyforit.com>> wrote: ** http://theremedyforit.com/2011/12/the-secret-documents-of-bmc/ Jose Manuel Huerta http://theremedyforit.com/ On Fri, Aug 17, 2012 at 2:51 AM, John Sundberg mailto:john.sundb...@kineticdata.com>> wrote: Ok thx for info. If they are looking for votes - I vote the API should be openly documented and marketed and pushed to the larger community. I think it would be a positive for BMC ITSM/ Remedy to work easily with the bigger environment. And side note - I can think of ZERO that would be lost by BMC by making it available. Oh - except for the trade secret that BMC uses integers for their Status field. -John Sent from my iPhone On Aug 16, 2012, at 6:06 PM, "Easter, David" mailto:david_eas...@bmc.com>> wrote: > Currently, BMC Legal designates BMC documentation as intellectual property > that is only available to customers with a valid Support contract. Thus it > is protected behind Support Central and not publicly available. > > A change in this interpretation is being considered (for about 2 years now). > If it does change, I'll let the list know. > > -David J. Easter > Manager of Product Management, AR System > BSM & Atrium Solutions Management > BMC Software, Inc. > > The opinions, statements, and/or suggested courses of action expressed in > this E-mail do not necessarily reflect those of BMC Software, Inc. My > voluntary participation in this forum is not intended to convey a role as a > spokesperson, liaison or public relations representative for BMC Software, > Inc. > -Original Message- > From: Action Request System discussion list(ARSList) > [mailto:arslist@ARSLIST.ORG<mailto:arslist@ARSLIST.ORG>] On Behalf Of John > Sundberg > Sent: Monday, August 13, 2012 1:54 PM > To: arslist@ARSLIST.ORG<mailto:arslist@ARSLIST.ORG> > Subject: Re: How to check Remedy Logins that are using Web Service > > Just wondering - any reason why BMC does not have an external facing version > of their Javadoc??? > I always seem to search and find it on JavaSystemSolutions site - but never > on BMC. > > From: > http://www.javasystemsolutions.com/documentation/thirdparty/arapi/constant-values.html#com.remedy.arsys.api.Constants.AR_FUNCTION_LENGTHC > > > > public static final intAR_CLIENT_TYPE_ALERT21 > public static final intAR_CLIENT_TYPE_APPROVAL7 > public static final intAR_CLIENT_TYPE_CACHE15 > public static final intAR_CLIENT_TYPE_CHANGE_ID4009 > public static final intAR_CLIENT_TYPE_CHANGE_SEL4008 > public static final intAR_CLIENT_TYPE_DISPATCHER4001 > public static final intAR_CLIENT_TYPE_DIST16 > public static final intAR_CLIENT_TYPE_DRIVER4000 > public static final intAR_CLIENT_TYPE_DSO5 > public static final intAR_CLIENT_TYPE_EIE13 > public static final intAR_CLIENT_TYPE_END_OF_PRODUCT3999 > public static final intAR_CLIENT_TYPE_END_OF_RESERVED_RANGE5000 > public static final intAR_CLIENT_TYPE_FLASHBOARDS11 > public static final intAR_CLIENT_TYPE_FLASHBOARDS_MID_TIER12 > public static final intAR_CLIENT_TYPE_HELP4002 > public static final intAR_CLIENT_TYPE_IMPORT_CMD19 > public static final intAR_CLIENT_TYPE_JANITOR4003 > public static final intAR_CLIENT_TYPE_MAIL18 > public static final intAR_CLIENT_TYPE_MAIL_DAEMON22 > public static final intAR_CLIENT_TYPE_MENU4004 > public static final intAR_CLIENT_TYPE_MID_TIER9 > public static final intAR_CLIENT_TYPE_ODBC6 > public static final intAR_CLIENT_TYPE_PALM_PILOT10 > public static final intAR_CLIENT_TYPE_PRE_501 > public static final intAR_CLIENT_TYPE_RELOAD14 > public static final intAR_CLIENT_TYPE_REPORT_PLUGIN20 > public static final intAR_CLIENT_TYPE_RUN_MACRO17 > public static final intAR_CLIENT_TYPE_SIM_PUBLISHING_SERVER28 > public static final intAR_CLIENT_TYPE_SIM_SME29 > public static final intAR_CLIENT_TYPE_SQLED4007 > public static final intAR_CLIENT_TYPE_STRUCT4005 > public static final intAR_CLIENT_TYPE_TEXT4006 > public static final intAR_CLIENT_TYPE_UNKNOWN0 > public static final intAR_CLIENT_TYPE_UNPRODUCTIZED_START4000 > public static final intAR_CLIENT_TYPE_WAT2 > public static final i
Re: OT: Externally available doc (was: How to check Remedy Logins that are using Web Service)
Why would anyone in BMC think that their competitors wouldn't have the software, documentation etc? So I see no really reason to keep it to people who pay money. It also brings back the old conversation of having a developer license so people could learn independently. The only option is get a job with a customer or partner and get the software/documents that way. Let's hope there is a positive change On 17 Aug 2012, at 01:51, John Sundberg wrote: > Ok thx for info. > > If they are looking for votes - I vote the API should be openly documented > and marketed and pushed to the larger community. I think it would be a > positive for BMC ITSM/ Remedy to work easily with the bigger environment. > > And side note - I can think of ZERO that would be lost by BMC by making it > available. > > Oh - except for the trade secret that BMC uses integers for their Status > field. > > > -John > > Sent from my iPhone > > On Aug 16, 2012, at 6:06 PM, "Easter, David" wrote: > >> Currently, BMC Legal designates BMC documentation as intellectual property >> that is only available to customers with a valid Support contract. Thus it >> is protected behind Support Central and not publicly available. >> >> A change in this interpretation is being considered (for about 2 years now). >> If it does change, I'll let the list know. >> >> -David J. Easter >> Manager of Product Management, AR System >> BSM & Atrium Solutions Management >> BMC Software, Inc. >> >> The opinions, statements, and/or suggested courses of action expressed in >> this E-mail do not necessarily reflect those of BMC Software, Inc. My >> voluntary participation in this forum is not intended to convey a role as a >> spokesperson, liaison or public relations representative for BMC Software, >> Inc. >> -Original Message- >> From: Action Request System discussion list(ARSList) >> [mailto:arslist@ARSLIST.ORG] On Behalf Of John Sundberg >> Sent: Monday, August 13, 2012 1:54 PM >> To: arslist@ARSLIST.ORG >> Subject: Re: How to check Remedy Logins that are using Web Service >> >> Just wondering - any reason why BMC does not have an external facing version >> of their Javadoc??? >> I always seem to search and find it on JavaSystemSolutions site - but never >> on BMC. >> >> From: >> http://www.javasystemsolutions.com/documentation/thirdparty/arapi/constant-values.html#com.remedy.arsys.api.Constants.AR_FUNCTION_LENGTHC >> >> >> >> public static final intAR_CLIENT_TYPE_ALERT21 >> public static final intAR_CLIENT_TYPE_APPROVAL7 >> public static final intAR_CLIENT_TYPE_CACHE15 >> public static final intAR_CLIENT_TYPE_CHANGE_ID4009 >> public static final intAR_CLIENT_TYPE_CHANGE_SEL4008 >> public static final intAR_CLIENT_TYPE_DISPATCHER4001 >> public static final intAR_CLIENT_TYPE_DIST16 >> public static final intAR_CLIENT_TYPE_DRIVER4000 >> public static final intAR_CLIENT_TYPE_DSO5 >> public static final intAR_CLIENT_TYPE_EIE13 >> public static final intAR_CLIENT_TYPE_END_OF_PRODUCT3999 >> public static final intAR_CLIENT_TYPE_END_OF_RESERVED_RANGE5000 >> public static final intAR_CLIENT_TYPE_FLASHBOARDS11 >> public static final intAR_CLIENT_TYPE_FLASHBOARDS_MID_TIER12 >> public static final intAR_CLIENT_TYPE_HELP4002 >> public static final intAR_CLIENT_TYPE_IMPORT_CMD19 >> public static final intAR_CLIENT_TYPE_JANITOR4003 >> public static final intAR_CLIENT_TYPE_MAIL18 >> public static final intAR_CLIENT_TYPE_MAIL_DAEMON22 >> public static final intAR_CLIENT_TYPE_MENU4004 >> public static final intAR_CLIENT_TYPE_MID_TIER9 >> public static final intAR_CLIENT_TYPE_ODBC6 >> public static final intAR_CLIENT_TYPE_PALM_PILOT10 >> public static final intAR_CLIENT_TYPE_PRE_501 >> public static final intAR_CLIENT_TYPE_RELOAD14 >> public static final intAR_CLIENT_TYPE_REPORT_PLUGIN20 >> public static final intAR_CLIENT_TYPE_RUN_MACRO17 >> public static final intAR_CLIENT_TYPE_SIM_PUBLISHING_SERVER28 >> public static final intAR_CLIENT_TYPE_SIM_SME29 >> public static final intAR_CLIENT_TYPE_SQLED4007 >> public static final intAR_CLIENT_TYPE_STRUCT4005 >> public static final intAR_CLIENT_TYPE_TEXT4006 >> public static final intAR_CLIENT_TYPE_UNKNOWN0 >> public static final intAR_CLIENT_
