[ISS.0085.9104] Access denied to invoke on remote server webMethods_<alias_name>

, ,
1

Hi Experts,

We have two servers in our environment wm 6.1 and wm 7.1.

We have a requirement for establishing communication between 61 and71.

So we configured 71 as remote server at 61 and given a alias name(webMethods_712QA_6969).

We have a service A at 61 which is accepting a soap Request transforming the soap request to required document type and sending it as input to service pub.remote:invoke(for invoking service at remote server 71).

So we have generated a WSDL for service A and loaded the WSDL at SOAP UI(web service testing tool), while testing the webservice we are getting the following exception:

<SOAP-ENV:Envelope xmlns:SOAP-ENV="[URL]http://schemas.xmlsoap.org/soap/envelope/[/URL]" xmlns:xsi="[URL]http://www.w3.org/2001/XMLSchema-instance[/URL]" xmlns:xsd="[URL]http://www.w3.org/2001/XMLSchema[/URL]">
   <SOAP-ENV:Body>
      <SOAP-ENV:Fault>
         <faultcode>SOAP-ENV:Client</faultcode>
         <faultstring>[ISS.0088.9134] Exception occurred while processing the body of the message</faultstring>
         <faultactor>https://mycompany.com:myport/soap/default</faultactor>
         <detail xmlns:webM="[URL]http://www.webmethods.com/2001/10/soap/encoding[/URL]">
            <webM:exception>
               <webM:className>com.wm.app.b2b.client.ServiceException</webM:className>
               <webM:message xml:lang="">[ISS.0085.9104] Access denied to
 invoke on remote server [I]<alias_name>[/i]</webM:message>
            </webM:exception>
         </detail>
      </SOAP-ENV:Fault>
   </SOAP-ENV:Body>
</SOAP-ENV:Envelope>

But while we are saving the soapRequest in a pipeline file and debugging the service A through restorePipelineFromFile we are successfully invoking pub.remote:invoke service and getting the desired output from 71.

We have checked out all the possibilities, even we have changed the Execute ACL property at wm 61 and wm 71 as Anonymous, but still we are gettingthe above exception.

Could any one please comment on this strange behaviour.

Regards,
Vikram

2

Does the remote server definition on 61 use an account that has the proper privileges on 71?

If you’re doing SOAP data, why are you calling 71 via (the proprietary) interface of remote:invoke? You might consider treating 71 as though it isn’t an IS instance and instead interact with it using SOAP over HTTP–as a typical web services call.

3

I believe you have created WSD (consumer or provider) on 71 and the endpoint address invoking an IS service (a operation in WSDL) you changed the Execute ACL to Anonymous??

Rob’s point mentioned above you can think about it as preferred way…

HTH,
RMg

4

The remote server definition on 61 use an account that has the proper privileges on 71, we are testing the connectivity of the remote server at 61 through test option at remote server configuration and the test was successful.

When we are trying to connect from soap ui, the test was unsuccessful.

We are having a requiremnt of using RIPS in place of 61 in near future so we are calling 71 via (the proprietary) interface of remote:invoke?.

5

Did you also increase the logging level on both the IS’s and check to see whats going on behind in the server log??

HTH,
RMG

6

What is “RIPS?”

7

we have increased the logging level on both the IS’s and check to see whats going on behind in the server log, but didn’t got any clue.

RIPS(Remote invoke proxy server).

8

Beside troubleshooting,open SR and talk to techsupport as you use 712 they can help more.

HTH,
RMG