OSGi Services - Cloud

Talend Remote Engine User Guide for Linux

author
Talend Documentation Team
EnrichVersion
Cloud
EnrichProdName
Talend Cloud
task
Design and Development
Installation and Upgrade
EnrichPlatform
Talend Remote Engine

Deployment

Every deployment is bounded to the OSGi deployment directory, and installed in Talend Runtime. The deployments are linked to a unique identifier, and multiple Data Services and Routes can be deployed to the same Talend Runtime. However, the deployment of the same binary Artifact (or a different version) multiple times to the same Talend Runtime is not supported. This means you cannot create multiple deployment Tasks in Talend Cloud with the same Artifact (same or different versions) and deploy these Tasks to the same Talend Remote Engine.

By default, the deployment consists of the following parts:
  • an Artifact (OSGi KAR to deploy)
  • an environment context
  • running the KAR in Talend Runtime

Undeployment

After an OSGi Service is deployed, the only action linked to its unique identifier is undeployment. Undeployment means that the OSGi feature is undeployed from Talend Runtime and every trace of its deployment is deleted from the <OSGiExecutionDirectory>.

Recovery

If Talend Remote Engine or the host machine is stopped, every deployed OSGi is stopped and kept in the <OSGiExecutionDirectory>. When all services are started again, the OSGi is started with the same configuration as before. To avoid recovery, OSGis should be undeployed.