John, "Code? Who needs stinking code?"
Well, Assuming that AT&T has a published WSDL that ARS can understand. ( That is two requirements in there. 1) They choose to publish a WSDL, and 2) ARS can understand their WSDL .) If #1 is false, then you might be able to create your own WSDL for their web service. ( I personally have never seen the use in a Web Service without a WSDL.) If #2 is false, then.... you still have a few options but the path is longer. Option1) Write your own Web Service client and wrap that in an ARF plugin. (Then use as above.) Option 2) Use an intermediate to translate AT&T's web service into a Web Service that ARS can understand and has a WSDL. (AKA: Write a Web service client and a Web Service "Server" that set between ARS and AT&T.) Option 3) Use an extra tool to do ARS to XML activities. The following come to mind: http://www.kineticdata.com/products/klink/index.htm http://www.javasystemsolutions.com/products/xmlgatewayce -- Carey Matthew Black Remedy Skilled Professional (RSP) ARS = Action Request System(Remedy) Love, then teach Solution = People + Process + Tools Fast, Accurate, Cheap.... Pick two. On 11/15/06, John Smith <[EMAIL PROTECTED]> wrote:
** Hello everyone, I've been out of serious Remedy development since version 5. I've been called upon to integrate our ARS 6.3 system with AT&T's eBonding gateway using their web services. This will let us submit tickets, update tickets and schedule circuit tests with AT&T using our Remedy system. I was curious if anyone has done something similar or even done an integration with the AT&T system. I'm reading over Remedy's consumption of web services and their documentation seems vague. Any suggestions help or code examples would be of great help. Thanks in advance, John
_______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
