Skip to main content

Qlik

cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Announcements
SYSTEM MAINTENANCE: Thurs., Sept. 19, 1 AM ET, Platform will be unavailable for approx. 60 minutes.
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
FrancoisSmfy
Contributor III
Contributor III
‎2019-11-21 08:20 AM

What actions does the TAC perform to deploy a route from Nexus?

Hello,

We currently use a Talend Data Service 6.4.1 and wish to automate some actions outside the TAC.

Our goal is to be able to deploy route/services from the Nexus to the Runtime, using Jenkins or another software.

 

The issue is that we couldn't find the list of action performed by the TAC.

It seems to have the following one, but it's not sufficient :

  • create/edit a file with the context to use : <TalendRuntime-path>/container/etc/<bundlename>.cfg
  • download the <bundleName>-feature-<version>.xml in the local repository
  • execute the Karaf command : feature:install <bundleName>-feature/<Version>

Does anyone could tell me what I miss? Or redirect me to a tutorial explaining it all?

Labels (2)
Labels
86 Views
0 Likes
1 Reply
Anonymous
Not applicable
‎2019-12-02 02:05 AM

Hello,

There are essentially two deployment options:

1. Direct deployment of Data Service / Route in Runtime
2. Publishing the Route/Service to Artifact repository. then create a task in ESB conductor and deploy it to the runtime server.

(+ one more for Restful Data-Services and Routes where we also support a Microservice (Spring Boot) based deployment).

 

Mode 1 (via KAR-File): is suitable if you have access to the deployment folder or if you like to deploy the routes / features in an automated way by file copy to the deploy folder. This is an easy way to deploy Routes/Service to the runtime but it uses the auto install from Runtime via the deploy folder and by this e.g. no easy way to change the context properties during deployment and you need file access to the deployment folder. It is by still a possible production deployment option but in most cases more used during testing.

 

Mode 2 (via Artifact Repo) is more the standard deployment option for Routes and Services but only available in the Subscription products as it depends also on TAC ESB Conductor. By this an ESB Route/Service can be published to the Artifact Repo (Nexus) and then you create a Deployment Task in the TAC ESB Conductor to install it to the Runtime. Technically we only send JMX commands to the Runtime and the Runtime will download and install the feature directly from the Artifact Repo (means the Runtime needs also access to the Aritfact-Repository). With this option you can use the TAC ESB Conductor screen to deploy / undeploy a feature to one or many Runtimes (either by individual tasks or using the Virtual Server concept in TAC).
Beside the user interface for remote deployment (ESB Conductor) you have also a more easy way to select the context (e.g. PROD, QA, DEV) and to overwrite individual context parameter at deployment time. This is the biggest difference between the two options. The running Route/Service is essentially the same independent of your decision to go with Mode 1 or Mode 2.

Best regards

Sabrina

86 Views
0 Likes