Deployment of DI Job on TAC

[Anonymous]

Hi, there,

I am having DI Talend jobs based on REST/SOAP services, means the DI jobs have the following components:

tRESTRequest

tESBProviderRequest

How can I deploy these jobs to TAC? Under which node(ESB Conductor/Publisher/Job Conductor) I can publish these jobs along with the Context variables?

Thanks,

Stuti G

[Anonymous]

Hello Stuti G,

are you implementing the webservice? Or do you have a DI Job (BatchJob) that uses webservices?

The components tRESTRequest an tESBProviderRequest are the "Inbound"-Components for implementing the services. Then you have to deploy it in ESBConductor.

In ESB Conductor you can provide services (webservice/route) that are permanently running and are waiting to be called / to get data. They are starting automatically when the runtime is restarted. In JobCondutor you can deploy Jobs, that are started by schedule or trigger. You can also run a "neverending" job in JobScheduler (for example with components like tWaitForFile) but that is not the usually way to use.

Best regards

[Anonymous]

Hi @aoh ,

In ESB Conductor Job Deployment, we can deploy using JAR files. How to provide context to them?

Example: I have a tRESTRequest-tRESTResponse job, under which I am using Context Groups, how to chosse context for such jobs in TAC?

Thanks,

Stuti

[Anonymous · Accepted solution]

Hello Stuti,

it should be possible to select the context on ESB Conductor.

What are you doing in Detail? My Suggestion:

- Build the Job in Studio

- Publish to Artifact Repository as OSGI Bundle for ESB

- Select the Feature on ESB Conductor from Artifact Repository

- In section "RuntimeConfig" there should be the selection of the context

Is the selection missing?

Best regards,

aoh