I have created a RESTful service and successfully tested it using the java client from the sonic MQ samples folder. ie I POST a message it it is accepted and processed through the ESB.
But i would like to confirm that I have created it correctly by using an external client other than the sonic sample. In this case the SoapUI tool.
This is from the Sonic java sample client:
[11/07/25 12:06:33] ID=MgmtBroker (trace) Received HTTP Direct inbound message, containing details...
Client IP=10.30.1.168
User=bpfuels
Request Line=POST /Schedule HTTP/1.1
Status Code=200
[req]Content-Length=1118
[req]Content-Type=text/xml; charset="ASCII"
[req]SampleHeader-AppName=JSSEHttpsClient
[req]SampleHeader-FileName=sample.xml
[req]Content-Length=1118
This is from the SoapUI client:
[11/07/25 08:58:59] ID=MgmtBroker (warning) Unauthorized HTTP access, Client IP=10.30.1.168, UserName=AUTHENTICATED
[11/07/25 08:58:59] ID=MgmtBroker (trace) Received HTTP Direct inbound message, containing details...
Client IP=10.30.1.168
User=
Request Line=POST /Schedule?UserName=bpfules&password=iesfuels*bp HTTP/1.1
Status Code=401
[req]Content-Length=12
[req]Content-Type=text/xml;charset=UTF-8
[req]Content-Length=12
[resp]WWW-Authenticate=Basic
Has anyone used the SoapUI tool to test RESTful services or for that matter any other tool.
Any suggestions would be appreciated.
Tony.
It looks like you are invoke the service via a broker HTTPD acceptor, rather than via Sonic Connect?
I did create the service as an HTTPS direct acceptor on the broker.
While you might be able to do REST via a HTTPS broker acceptor, there will be many limitations on the use case. You should consider using Sonic Connect instead.