Dan,
Why a general WS client to do ARS Submit, Modify, Delete?:
Because a general purpose Web Service for Remedy API to create,
modify, delete records should not be much harder than a Java
application(command line client) to do the same thing. In fact the
might even share the exact same line of code to "talk to ARS". If you
go so far with the command line client as to read an "XML config file"
then the code would look almost identical. So the "effort difference"
seems very, very small between the two for me.
And...
If you implement an ARS hosted Web service then it would need to
be implemented per form. A general WS could cover all forms in one
shot. (and the community as a whole could use the same WS for any
form. Custom application or OOB application.)
--
Carey Matthew Black
Remedy Skilled Professional (RSP)
ARS = Action Request System(Remedy)
Solution = People + Process + Tools
Fast, Accurate, Cheap.... Pick two.
Never ascribe to malice, that which can be explained by incompetence.
On 7/6/06, Dan Hardy <[EMAIL PROTECTED]> wrote:
Just curious - for the latter case, why wouldn't you just create a Web
Service for your application using the admin tool, and then use Java to
talk to that?
Regarding the original question, there are many options depending on
your platform. The ones I am familiar with - Remedy's own C API,
Remedy's own Java API, Remedy's .NET and COM API (from the dev
community), and then open source: RTL (C++), joarse (Java on
Windows/Linux, hopefully soon Solaris), coarse (again, JScript or
VBScript), and ARSPerl. My opinion? If you are on Windows and want
something quick, simple, and dirty, just install either one of the two
COM apis and write a quick JScript file. If you're on Linux, I'd
probably pick joarse.
Dan
_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at http://www.wwrug.org
