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 < [email protected]> 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" <[email protected]> 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: > [email protected]] On Behalf Of John Sundberg > > Sent: Monday, August 13, 2012 1:54 PM > > To: [email protected] > > 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_ALERT 21 > > public static final int AR_CLIENT_TYPE_APPROVAL 7 > > public static final int AR_CLIENT_TYPE_CACHE 15 > > public static final int AR_CLIENT_TYPE_CHANGE_ID 4009 > > 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_RANGE 5000 > > 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_PLUGIN 20 > > public static final int AR_CLIENT_TYPE_RUN_MACRO 17 > > public static final int AR_CLIENT_TYPE_SIM_PUBLISHING_SERVER 28 > > public static final int AR_CLIENT_TYPE_SIM_SME 29 > > public static final int AR_CLIENT_TYPE_SQLED 4007 > > 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 <[email protected]> > 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: [email protected] > > 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: > [email protected]] On Behalf Of Grooms, Frederick W > > Sent: Monday, August 13, 2012 11:02 AM > > To: [email protected] > > 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: > [email protected]] On Behalf Of Longwing, LJ CTR MDA/IC > > Sent: Monday, August 13, 2012 12:56 PM > > To: [email protected] > > 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: > [email protected]] On Behalf Of Mueller, Doug > > Sent: Monday, August 13, 2012 11:54 AM > > To: [email protected] > > 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: > [email protected]] On Behalf Of Kali Obsum > > Sent: Monday, August 13, 2012 1:55 AM > > To: [email protected] > > 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" > > > > -- > > John Sundberg > > > > Kinetic Data, Inc. > > "Your Business, Your Process" > > Recipient of: > > > > WWRUG10 Best Customer Service/Support Award > > WWRUG09 Innovator of the Year Award > > > > [email protected] > > 651.556.0930 I www.kineticdata.com > > > > > _______________________________________________________________________________ > > 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" > _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are"
