Roger,
A *super special* thing about the Web Service standard is that WSDL's are
optional. So you might have to tell your .NET developers that they need to
go learn that standard well enough to describe their .NET web service. Or
they might already have built their web service from a predefined WSDL.
There are tools that take a WSDL and build client code handlers and Server
code frameworks to allow a person to keep a chunk of code that is
"generated" from the WSDL and then just plugin some other stuff to actually
make the Web Service do something. :)
It is generally considered a "good thing" to start by defining the WSDL then
after both parties have agreed on the structure, go implement the actual Web
Service (server side).
However, in the ARS universe there are a few special things here..
1) ARS requires a WSDL for you to consume a Web Service.
2) ARS does not fully support all structures that are possible in the full
WSDL standard too.
See the Admin tool Help for the topic: "limitations for consumption"
That is a must read for your .NET coders. (If they have not seen it
yet.)
I am sure there are other stuff to consider, but that should at least get
you the 80%(work)-20%(time) rule. :)
HTH.
--
Carey Matthew Black
Remedy Skilled Professional (RSP)
ARS = Action Request System(Remedy)
Love, then teach
Solution = People + Process + Tools
Fast, Accurate, Cheap.... Pick two.
From "Nall, Roger" <[EMAIL PROTECTED]>
Sent by: "Action Request System discussion list(ARSList)" <
[email protected]>
16/03/2007 12:55
Please respond to
[email protected]
To [email protected]
Subject Web Service Newbie
**
Okay everyone please take it easy on me with this one. Here is my
configuration:
ARS 6.03 patch 16
WINDOWS 2003
SQL 2K
No mid-tier
We are creating a .NET help desk ticket application for our Engineering
group. Currently they use Remedy but due to some personal issues the
decision was made to move the Remedy application to a move advanced
platform. Please do not ask any questions as to why this decision was made.
My mother always told me if you can't say something nice about someone don't
say anything at all.
That being said we need to integrate Remedy with this new .NET system. I
need to be able to create tickets in the new system and they need to be able
to update my tickets as well as create tickets in Remedy. They have
developed a Web Service for me to use to create tickets in the new system.
As I understand it this will allow me to pass data to the new system and
receive their ticket number back.
We were originally going to user the .NET API to allow them to
update/create tickets in my system. It was suggested to me that maybe we
could use a Web Service created on the Remedy side instead of the API. I
have been looking at the documentation for creating a Web Service and that
has led me to this posting.
My first question is how is this possible without using the Mid-Tier? As
I stated, this is new to me and I am not sure I fully understand it. Any
help would be greatly appreciated.
Thanks,
Roger A. Nall
Manager, OSSNMS Remedy
T-Mobile USA
Desk: 813-348-2556(New)
Cell: 973-652-6723
FAX: 813-348-2565
sf49fanv AIM IM
RogerNall Yahoo IM
_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers
Are"
