Jack -
Maybe I am not reading this correctly... It's Friday, and I am a bit short
in the sleep department again...
Essentially what I am getting here is that you cannot connect to your web
service over an SSL connection. SSL is the "Secure Sockets Layer" that is
used for securing the connections between the client and the browser (and
represents the S on the tail end of HTTPS).
This is fairly strange to me, since the SSL layer is actually "added on"
so-to-speak via the web server. If you're on a Unix platform, this would
be (preferrably) Apache, or perhaps Sun one. If you're on Windows, then
it's probably IIS. The process involves either generating your own SSL
certs, or getting a service to do so for you.
A web service - from the web servers point of view - is just another bit
of content that it serves up, so it does not differenciate between SOAP
and HTML. The request *should* -IMHO - actually be passed from the web
server to your servlet engine (Tomcat, or Atlanta) for processing. The
whole key here is that the web server is responsible for establishing a
sercure connection with the client, and that the midtier handles the
request that is passed to it over the connection.
Unless you have specifically enabled SSL on your web server, or servlet
engine, then SSL and - hence - HTTPS - will not work.
If you are running Tomcat and Apache, add the SSL certs to your Apache web
server first, and then use the connector to route requests for the midtier
back to the Tomcat server. Yeah, a person could install just tomcat and
add the SSL certs there, but that just begs the question - why? Apache is
faster performance-wise for serving static content anyway. (Then there is
that nagging question of design.)
If you're on IIS and Atlanta, bug your admin to add the certs and start
the HTTPS service.
In a nutshell, a web service is the way to go, if you need to be able to
"interact using XML" with the AR System server. The server has to be
configured to do so correctly first, however.
HTH.
On Fri, 6 Jul 2007, Covert, Jack wrote:
Hi all. I have a need to be able to interact w/ Remedy using XML over
HTTPS. Web Services would be nice but they can't handle the SOAP
wrapper. KLink doesn't work w/ 5.1.2 (our version), any other
suggestions?
TIA
Jack Covert
Corporate IT
Enterprise Systems Management
Remedy Support Team
Remedy Support Team Home Page
<http://collaborate.mckesson.com/sites/esm/remedy>
http://collaborate.mckesson.com/sites/esm/remedy
_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers
Are"
_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers
Are"
