Never worked with certificates and WS's but yes its logical that those would
need to be on the Remedy server for the Remedy server to be able to use
those certificates and keys..
Just so you know (since you thought it was going through the mid tier) if
you have trouble with your WS consumption, your error logs would be on the
arjavaplugin.log on your AR Server.. The mid-tier logs will be clean and not
have anything pertaining to any consumption errors, which is an indication
too that its not used during the process of consumption..
Good luck.. You might have trouble with using the WS itself on the road
ahead even after you get the connections setup.. The AR Server has a number
of limitations consuming WS's. This is because of some of the constructs
that the AR Web service plugin does not support or understand. I wasn't
fully aware of these limitations when I embarked on this same road a few
weeks ago.. They are documented on the Integration guide, so it may help if
you read that whole section on using the Web Service integration, and get a
grasp of the different constructs that the AR Web service plugin will not
comprehend..
If it’s a simple web service and not a complex one, you are in luck...
Joe
-----Original Message-----
From: Sean O'Sullivan
Sent: Thursday, June 28, 2012 11:04 AM Newsgroups:
public.remedy.arsystem.general
To: [email protected]
Subject: Re: Web Service questions
Joe,
Thanks very much...that helps a lot. We were set up all wrong. We're using
a Web Service gateway that our company has set up. We had all our verisign
certificates and connections set up to the mid tier not the main Remedy box.
We will swing all of that to the main Remedy box and give it another try.
Thanks again
Sean O
_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are"
