You are not logged in.
Announcement
Unanswered posts
|
Pages: 1

Hi,
I created a simple helloWorld Soap service and published the job to our connected archivia repository. After that I added the job in the ESB conductor section of TAC. I deployed it as a type Service.
After deployment I started the job. When I look in the Karaf sesison I see the job and it is started.
However I cannot access the Soap service, I tried to get the wsdl, bnut no result (in studio the job works). Firewall is not enabled.
When looking up the running services: : http://ourserver/8040/services/
I see this:
Available SOAP services:
MonitoringService
putEvents
Endpoint address: http://srv05.kleertjes.local:8040/servi … erviceSOAP
WSDL : {http://service.server.sam.esb.talend.org/}MonitoringWebServiceService
Target namespace: http://service.server.sam.esb.talend.org/
But now my deployed Soap service?
In the wsdl I tried different soap addresses:
http://localhost:9001/services/helloSoap
http://0.0.0.0:9001/services/helloSoap
And I tried different ports: 8040, 8090, 9001
Does the port number used matter?
0.0.0.0 should be used right?
Why is the Soap service not showing up?
Offline

Hi I found out what I did wrong. I published only the job, as I did with a REST job. However as I found out I need to publish the Service I created. The job connected to the service will then be deployed as well.
Not sure if this is a bug in studio?
Offline
Pages: 1