Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Qlik Open Lakehouse is Now Generally Available! Discover the key highlights and partner resources here.
cancel
Showing results for 
Search instead for 
Did you mean: 
Anonymous
Not applicable

Mediation: tRouteInput cannot return XML using tESBProviderResponse

Hello Team,
I'm new to Talend. I am facing a problem for past 2 days using Mediation.
I have the following:

[list=*]

  • Service : Created using a wsdl file

 

  • Job1 : Accepts and XML (tESBProviderRequest) and calls a Mediation Route and pass the xml

 

  • Mediation Route : Has a cCXF that listents for calls and uses a cRoutingSlip to redirect the xml to say 'Job2'

 

  • Job2 (Invoked indirectly by Medication Route) : Starts with a tRouteInput. I need to return an XML Response for the tESBProviderResponse from Job1. 


When fire a request using Soap UI to Job1. I get the error in Route saying [1]. I will really appreciate if I get some help with Job2. I am curious on what can I return from my Job2 so that I will get a proper response in SoapUI.  Is there any extra configuraiton I should do to get this working? Or should I use a different component to return the xml? Is this the right approach? I am free to change the components but should maintain Request-> Job1-> Route -> Job2 -> Response

[1] [WARN] nonsense: tESBProviderResponse component used without tESBProviderRequest component on the job

Job1 ( -> tESBConsumer will call the Route)





Route ( -> route will call the Talend Job)





Job2 (-> Trying to return the same xml as response, I will add logic later)


Any suggestions?

Labels (2)
1 Reply
Anonymous
Not applicable
Author

The request-response pairs only works within the same job. I suggest you build a service job containing the request and response component and use another job (with perhaps embedded jobs) to process the request and build the response. You can get back any result from a job by the help of tBufferOutput (write the result within the job) and the output flow of the tRunJob component (click here on Get Schema from child job).