Hi, The .NET API, although not "officially" supported, has been kept updated by BMC since the original person who ported this left.
As LJ mentions, you can use a number of methods to perform the integration where it will depend on what you are comfortable with as they all have their own little differences and nuances. One main factor for a decision would be on how you plan to get the information out of the .NET application and into Remedy. If you had access to the .NET developers / code then it would make more sense to extend this using the .NET API and keep it all in the one programming language. If not you, would need to decide on how you will gather the information which then may determine what path to take based on available functionality e.g. hooking into a Windows handle to read a field, read a text/XML file, send an email, etc. All methods have examples and sample code available on the BMC Communities where people like LJ, Misi, etc add value in the different methods available so it should be fairly easy to get a POC for basic functionality happening. _____ Kind Regards, Carl Wilson From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of LJ LongWing Sent: 03 February 2015 15:57 To: arslist@ARSLIST.ORG Subject: Re: Need inputs about integration ** Amit, Last time I checked, the only supported API's are Java and C with Java quickly becoming the 'default'....the .NET API, as I understand it (please don't take this as gospel) is produced by a BMC employee, but is not supported. I believe it's a wrapper of the C API.....so, if you are wanting to only go 'supported', you would use either C or Java, with my personal preference being Java (because I don't know C all that well)....but, with all of that being said....any app you write in the API will be 'unsupported' by BMC, other than the fact that they will fix the API if it's not functioning properly, but you are required to support the app...so, as long as any given API 'works' for your needs, you don't need support on it, and are in the same bucket you are in now :) As for the question about the Java API integrating with .NET application, I can't speak to it because .NET is not my forte, but I imagine there are 'bridges' that can be either used, or built. On Tue, Feb 3, 2015 at 8:41 AM, Remedy consultant <raccons...@gmail.com> wrote: Hello , Thank you for your quick reply.As you suggested that JAVA or .NET api are good to consider ,i have question for you whether BMC support API written in .NET .I am worried about maintenance prospective. I have one more question. Can we have JAVA API to integrate .NET application ? Sorry for asking too many question. Regards, Amit On 2/3/15, LJ LongWing <lj.longw...@gmail.com> wrote: > Well, Amit, considering that there is a .NET API for Remedy, it would make > sense to look at that as a potential integration point...if that's a > language you know and understand. Web service, as you mentioned is another > option....Perl, Java, C...all have API's that you could use if you > wanted....there is even a Restful API written against the Java API you > could utilize if you wanted.... > > On Tue, Feb 3, 2015 at 8:17 AM, Remedy consultant <raccons...@gmail.com> > wrote: > >> Hello All, >> >> I have to work on a client requirement in which i need to integrate >> external application (built in .NET) with Remedy. >> >> Could you please suggest best possible way to integrate this >> application with remedy? This .NET application will create new tickets >> in remedy application. >> >> I know web service is one of the way to integrate. But would like to >> know whether .NET API would be a good option to implement this. >> >> >> Regards, >> >> Amit >> >> >> _______________________________________________________________________________ >> UNSUBSCRIBE or access ARSlist Archives at www.arslist.org >> "Where the Answers Are, and have been for 20 years" >> > > _______________________________________________________________________________ > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org > "Where the Answers Are, and have been for 20 years" > _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years" _ARSlist: "Where the Answers Are" and have been for 20 years_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
