Skip to main content

Old Eclipse-based runtime

This runtime is not installed automatically. To install it, see Using Talend Data Mapper with Talend Runtime.
Information noteNote: The old Eclipse-based runtime does not support the deployment of Jobs as OSGi bundles when these Jobs contain a tHMap component.

When the runtime executes it depends on various files to be present in the local file system. To do this, it automatically creates these files, installing the product from the content in the runtime Jar file if they are not already present.

The following folders are created:

  • osdtInstall_xxx

    This installation directory is expected to be a local directory named by the ODT_INSTALL_DIR Java System property. This directory is automatically created if it does not exist on the first execution of the runtime. You can use the same ODT_INSTALL_DIR property for all installations, since the installation is installed into a subdirectory that is qualified by product identification (across all companyName transformation product variants and brandings), user name (to prevent permissions problems), and the full version string.

    If the ODT_INSTALL_DIR Java System property is not set, the installation will take place into a temporary directory (

    Whether or not the ODT_INSTALL_DIR property is specified, these files may be freely deleted at any time (when the product is not running) and they will be automatically and silently recreated. If you are interested in the details about exactly where these files are created and seeing when the are created, specify the log="all" attribute in your transformer or service configuration.

    Deleting this folder while a map is executing may lead to unpredictable results.

  • osdtConfiguration_xxx and osdtWorkspace_xxx

    These provide the Eclipse Configuration and the Eclipse Workspace, respectively. They are created for each map execution in the temporary folder.

    They should not be deleted while a map is still executing. Special care must apply for long running jobs as these typically require their Eclipse Configuration and Workspace to remain present until the job finishes.

    The folders can be removed once the map is done executing. They are not removed automatically, as support may ask customers to provide internal Eclipse log files produced in either osdtConfiguration_xxx or osdtWorkspace_xxx folders when a map execution issue occurs.

    It is therefore a user responsibility to delete these folders periodically. For instance having a weekly cron job that deletes such folders whose creation date is one week old should safely remove unused folders (unless some jobs take more than a week to complete).

    Deleting this folder while a map is executing may lead to unpredictable results.

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 – let us know how we can improve!