Scott,
the /arsys/WSDL is the URL to the WSDL, the /arsys/services is the URI that
the WSDL points to for execution....two different pieces of the same puzzle.

On Wed, Mar 11, 2015 at 12:55 PM, Scott Hallenger <[email protected]> wrote:

> Ok here is what I dont understand:
>
> This is the url of the webs service that is called externally:
>
> http://mywebserver/arsys/services/ARService?server=myappsever&webService=HPD_IncidentInterface_Create_WS_3
>
> This is the URL of the web service as defined in remedy (admin tool/web
> services):
>
> http://mywebserver/arsys/WSDL/public/myappserver/HPD_IncidentInterface_Create_WS_3
>
>
> If past the below url from the admin tool into my browser I runs and the
> soap code is returned but if use the external url above.. it does not run.
> I get the "Hi there, this is an AXIS service!" error.
>
> http://mywebserver/arsys/WSDL/public/myappserver/HPD_IncidentInterface_Create_WS_3
>
> Now it get srange because I can't call the external url from my production
> server either, but when I run the same script against prod it creates the
> incident as it is suppose to do.
>
>
> --------------------------------------------
> On Wed, 3/11/15, Terry Bootsma <[email protected]> wrote:
>
>  Subject: Re: web service logging
>  To: [email protected]
>  Date: Wednesday, March 11, 2015, 1:34 PM
>
>  **
>
>
>  Scott:
>  On your dev mid-tier, can you access the WSDL and the
>  web-service end-point that defines your web service (via a
>  browser) to ensure that your mid-tier has the web service
>  defined and available ?   If it is available, it
>  doesn't even look like the calling program is hitting
>  your midtier at all and I would debug from that point.
>  Terry
>
>
>
>  On 2015-03-11 13:22, Scott Hallenger wrote:
>
>  If you can see my previous post with attachment. my
>  Midtier logs isnt showing anything relating to a web
>  service. The cache clear that you see in the log was long
>  before i made any calls to the web service.
>
>  --------------------------------------------
>  On Wed, 3/11/15, Terry Bootsma <[email protected]>
>  wrote:
>
>   Subject: Re: web service logging
>   To: [email protected]
>   Date: Wednesday, March 11, 2015, 12:46 PM
>
>   **
>
>
>
>   Scott:
>   If you are consuming your remedy-based web service from
>   another application (other than Remedy itself) , it will
>  not
>   utilize the java plugin server.  The java plugin server is
>   only used for outbound web-service calls from Remedy.
>   You should be able to see your web services being called
>   in the mid-tier log.  From there, you would have to enable
>   filter/API logging on your Remedy server to debug
>   further.
>   HTH
>   Terry
>
>
>   On 2015-03-11 12:18, Scott Hallenger wrote:
>
>   Hi can anyone help me find my webservice loggs? We have
>   a web service that creates an incident in ttsm 7.0.1. it
>   work in our prduction invironment, but the moment we
>   re-point it to our dev system it does not generate the
>   incident. The midtier web service logs dont really show
>   anything useful. What I'm really looking for is the
>   arjavaplugin.log file which does nost seem to exist. I am
>   seriously frustrated at this point. I do not have the
>   ability to install soapUI in my environment so I have to
>   rely on the log if I can find it... help please.
>
>
> _______________________________________________________________________________
>   UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
>   "Where the Answers Are, and have been for 20
>   years"
>
>
>
>   _ARSlist: "Where the Answers Are" and have been
>   for 20 years_
>
>
>  
> _______________________________________________________________________________
>  UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
>  "Where the Answers Are, and have been for 20
>  years"
>
>
>
>  _ARSlist: "Where the Answers Are" and have been
>  for 20 years_
>
>
> _______________________________________________________________________________
> UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
> "Where the Answers Are, and have been for 20 years"
>

_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
"Where the Answers Are, and have been for 20 years"

Reply via email to