Skip to main content Skip to complementary content

Exporting a Service for deployment

The Integration perspective of Talend Studio enables you to export a Service to a .kar file that can be deployed at runtime. To do so:

Procedure

  1. In the Repository tree view, right-click the Service you want to export and select Export Service from the contextual menu.
  2. The Export service wizard displays. Click Browse to browse to where you want to store the exported Service.
  3. If you want to rebuild the exported Service into your own .kar with Maven, select the Add maven script check box in the Options area to include the required Maven script in the target archive, which is a .zip file in this case.
    Information noteNote: Talend Studio provides a default Maven script template for this option. You can customize this template based on your actual needs.
  4. Click Finish to complete the export operation and close the wizard.

Results

A .kar or .zip file for the Service is created in the defined place that can be deployed, or, in the case of a .zip file, rebuilt in to a .kar using the included Maven script and then deployed on your Talend Runtime.

Note that the archive file for the Service contains all the dependent libraries required to start the Service in Runtime. But the JDBC jar is an exception. If a data source for the same database is configured in the runtime container, with the JDBC jar, there will be LinkageError during the execution of the Service. So in this case, it is recommended to use the data source instead for connecting to databases.

When exporting a Service, all the contexts used in the Service are also included in the archive file. When you deploy the .kar file in runtime, the default context configured in the Service will be used.

To change the default context after you deploy the Service to runtime, complete the following steps:

  1. Go to subdirectory <TalendRuntimePath>\container\etc of Talend Runtime installation directory.

  2. Create a configuration file named <yourservicename>.cfg and set the context in this file:context=<contextName>

  3. Restart runtime.

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – please let us know!

Leave your feedback here