Generating WSDL with Reverse Invoke in place

[kzelonis]

Is there any difference (besides hostname and port) in the WSDL when using Reverse Invoke in Integration Server? Do we specify the RI hostname & proxy port or the hostname and proxy port of the internal IS?

We had successfully connected our SOAP client directly to the integration server box through WSDL's but have not been able to successfully connect the SOAP client to the same services proxied through a reverse invoke server.

Has anyone had any luck with this? Any help is greatly appreciated.

[kzelonis]

Thank you for your reply!

Is there a way to apply the one fix only, without applying a whole service pack? In the past, service packs have broken more than they've fixed!

[fredh666]

IS 4.6 Fix 5 is just for the two reserve invoke problems (maybe one bug was the root of both problems, I don't know), so it is a small as a patch as is possible.

[kzelonis]

We've applied the fix, but we're still having troubles. Here is our error message:

Connector error '800a1527'

Connector:Connection time out. HRESULT=0x800A1527 - Client:An unanticipated error occurred during the processing of this request. HRESULT=0x800A1527 - Client:Sending the Soap message failed or no recognizable response was received HRESULT=0x800A1527 - Client:Unspecified client error. HRESULT=0x800A1527

/ibe/includes/Utils.inc, line 22