Wsstack and SSL

, ,
1

I’m attempting to enable SSL on an EntireX webservice. At this point I only want Transport-level security enabled so I’ve selected that in the .aar file

The service deploys and I can access the WSDL via https. However when I attempt to call/test the service in a testing tool like SoapUI, I cannot call the service.

The Request looks like this:

<soap:Envelope xmlns:soap=“http://www.w3.org/2003/05/soap-envelope” xmlns:urn=“urn:com-softwareag-entirex-rpc:RSSA”>
soap:Header/
soap:Body
urn:RSSA000S/
</soap:Body>
</soap:Envelope>

And the response is the following:

<soapenv:Envelope xmlns:soapenv=“http://www.w3.org/2003/05/soap-envelope”>
soapenv:Body
soapenv:Fault
soapenv:Code
soapenv:ValueSender</soapenv:Value>
</soapenv:Code>
soapenv:Reason
<soapenv:Text xml:lang=“en-US”>SOAP Envelope can not have children other than SOAP Header and Body</soapenv:Text>
</soapenv:Reason>
soapenv:Detail/
</soapenv:Fault>
</soapenv:Body>
</soapenv:Envelope>

I’m not sure if I’ve misconfigured something? I’ve reviewed the documentation to no avail.

Any help is appreciated.

2

looks like an issue with the request rather than an SSL issue.

  • Does the service (RSSA000S) have no inputs?
  • Does the whitespace within the request contain extraneous non-printable characters? (try pasting it into an editor where you can view non-printable characters)
3

Thanks for the reply Douglas! That’s what I’m thinking but I still can’t figure it out.

RSSA000S has no inputs and only the one output (it’s essentially a heartbeat service).
I pasted it into an editor and the only non printable characters are CRLF.

4

Are you following the steps in Common Integration Scenarios > Calling Natural from a WebService?
https://techcommunity.softwareag.com/ecosystem/documentation/webmethods/entireX/exx10-3/10-3_EntireX/nat2ws/overview.htm

What version of EntireX are you on?

5

did you set the Message Receiver? In the aar editor, Services tab, Message Receivers panel, Edit the first line and try selecting the “out-only” Message Exchange Pattern.

6

Thank you so much Douglas, I was able to get this working.
It was the fact that the Request was poorly formed, as you thought initially. Once I tweaked the params in the IDL file and regenerated the service the test request was formed properly and returned results.

I discovered this by trying the process on a service that had In AND Out params and it worked fine.

Thank you for the assistance!