Yes but the traffic itself, is outgoing from the Mid-Tier so connection / network / port validations are all done as if the Mid-Tier was doing all the work.. Technically the network engineer does not even need to know about the AR Server or the Web Service plugin.. Rick was asking about a published web service.. So it’s a external system consuming the Remedy web service case..
When Remedy consumes, you are right, it’s the filter that calls the web service which connects to the plugin. You are right in that when Remedy consumes, the Mid-tier is not touched at all.. All the consumption logs are found in the arjavaplugin logs that are written after the plugin processes the call.. Nothing is seen on the mid-tier logs.. Sorry I wasn’t clear about what system is the consumer earlier.. To answer Jason I assumed (I think correctly) Rick meant outgoing application data queried from Remedy.. Joe From: Jason Miller Sent: Friday, September 07, 2012 1:10 PM Newsgroups: public.remedy.arsystem.general To: [email protected] Subject: Re: Web service source ** LJ, I was about to reply with the same thing but then I realized that I was probably reading this with the flow reversed. Before I hit send I took a look at the emails again and deleted the draft. I think "outgoing" can be looked at two different ways and when I reversed my train of thought nothing false had been said. So does "outgoing" mean data going out from Remedy? Or does "outgoing" mean Remedy is going out to get data. Rick gave all the necessary details I think people (like you and me) just read them differently :) Jason On Fri, Sep 7, 2012 at 10:02 AM, Longwing, LJ CTR MDA/IC <[email protected]> wrote: Joe, Sorry, but I think you are wrong here.... When Remedy consumes a web service, that is done through the plugin When someone else consumes a Remedy Web Service, that is done through Mid-Tier Remedy can consume external services without Mid-Tier being in existence...and vis versa, Remedy can publish web services without the plugin being loaded. -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Joe Martin D'Souza Sent: Friday, September 07, 2012 10:53 AM To: [email protected] Subject: Re: Web service source ** The outgoing traffic you are correct in saying that it goes from the Mid-Tier.. the external client communicates with the Mid-Tier when communication comes in as a web service, and the Mid-tier communicates to the AR Server through the Web Server Plugin.. I think the process of the actual generation of the WSDL however happens on the AR Server. At least that is my understanding. When you attempt to create a WSDL, using the Web Service creation object from the Dev Studio or the Remedy Admin Tool, the plugin creates the WSDL, and using the default web server path, connects to the web server, and saves it on the web server.. I may be wrong, but that’s my understanding, so if I am wrong, please someone correct me.. Joe From: Rick Cook <mailto:[email protected]> Sent: Wednesday, September 05, 2012 3:08 PM Newsgroups: public.remedy.arsystem.general To: [email protected] Subject: Web service source ** We are in the process of setting up a connection between our Remedy system and an external system. As part of our network/port validation, we need to know whether the outgoing traffic for a published web service (one that is consumed by the external system) is taken from the mid-tier server or the AR server. I contend that it is the mid-tier server, because that is where the WSDL is generated. My boss disagrees. Can you settle this for us? I've looked in the docs, but didn't really see anything. Rick Cook _attend WWRUG12 www.wwrug.com ARSlist: "Where the Answers Are"_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are" _attend WWRUG12 www.wwrug.com ARSlist: "Where the Answers Are"_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are"
