How comes the WSDL to the Job Server

One Star

How comes the WSDL to the Job Server

Hello Everybody!
We have a whole Talend DI Job created and this job is wrapped as a complete functional
web service. The belonging WSDL file was imported to Talend Studio to its Services and
referenced in that DI Job.
As long as I run the job locally in conjunction with Talend Open Studio the web services
starts trouble-free. But now when the Job is deployed via TAC and starts on a Job Server
the following error occurs:
javax.wsdl.WSDLException: WSDLException: faultCode=PARSER_ERROR: Problem parsing 'C:/Talend/5.3.1/Talend-Studio-r104014-V5.3.1/workspace/DI2012_DISTRIBUTION/services/WarehouseUploadWSDL_0.1.wsdl'.: /C:/Talend/5.3.1/Talend-Studio-r104014-V5.3.1/workspace/DI2012_DISTRIBUTION/services/WarehouseUploadWSDL_0.1.wsdl (No such file or directory)
at Source)
at Source)
at Source)
at org.apache.cxf.wsdl11.WSDLManagerImpl.loadDefinition(
at org.apache.cxf.wsdl11.WSDLManagerImpl.getDefinition(
at org.apache.cxf.service.factory.ReflectionServiceFactoryBean.isEmptywsdl(
at org.apache.cxf.service.factory.ReflectionServiceFactoryBean.isFromWsdl(
at org.apache.cxf.service.factory.ReflectionServiceFactoryBean.initializeServiceModel(
at org.apache.cxf.service.factory.ReflectionServiceFactoryBean.create(
at org.apache.cxf.frontend.AbstractWSDLBasedEndpointFactory.createEndpoint(
at org.apache.cxf.frontend.ServerFactoryBean.create(
at org.apache.cxf.jaxws.JaxWsServerFactoryBean.create(
at di2012_distribution.warehouseuploadwsjob_0_1.WarehouseUploadWSJob$
Caused by: /C:/Talend/5.3.1/Talend-Studio-r104014-V5.3.1/workspace/DI2012_DISTRIBUTION/services/WarehouseUploadWSDL_0.1.wsdl (No such file or directory)
at Method)

Please help and give some hints.
Kind regards
One Star

Re: How comes the WSDL to the Job Server

There are a few options. Many companies have a web server on the internal network that is used to host WSDLs. That way the WSDL can be referenced from services, from clients, and so on with a common URI. Your deployment process then is adjusted to include a step for deploying the WSDL to the web server.
A hint... Think through your naming conventions for imported or referenced WSDLs. Also consider how you will handle multiple versions of the "same" WSDL. Adding elements, for example, is pretty simple. Changing elements and supporting backward compatibility is harder . This gets pretty ugly pretty quickly.
If you are exposing the web service to the clients outside the firewall, you will also need to (a) work with the network team to set up a proxy so that external and internal clients can access the WSDL; or (b) host the WSDL inside and outside the firewall. Setting up the correct proxy, or XML firewall, or similar network infrastructure is beyond the scope of this forum.
One Star

Re: How comes the WSDL to the Job Server

Hello wrlawton!
Many thanks for your reply.
Your suggestion to reference the WSDL by URI doesn't work because
in Talend Studio under "Services" you can either create a WSDL from scratch or
select a WSDL by a local path. I have not the choice to type in a web site location.
How can I achieve this in Talend Studio.


Talend named a Leader.

Get your copy


Kickstart your first data integration and ETL projects.

Download now

What’s New for Talend Summer ’19

Watch the recorded webinar!

Watch Now

Best Practices for Using Context Variables with Talend – Part 2

Part 2 of a series on Context Variables


Best Practices for Using Context Variables with Talend – Part 1

Learn how to do cool things with Context Variables


Migrate Data from one Database to another with one Job using the Dynamic Schema

Find out how to migrate from one database to another using the Dynamic schema