What’s new in Talend Framework 1.7
Introduction of a new Template Job, which replaces Job: TemplateChild.
These two Jobs are functionally equivalent, however, Job: TemplateTask has additional documentation for improved Exception handling, as well as having a more meaningful name.
Job: TemplateChild has been deprecated.
Job: TemplateOrchestrate, TemplateOrchestrateCP
Introduction of two new Template Jobs, which allow you to orchestrate your task Jobs.
Job: TemplateOrchestrate is now called by Job: TemplateProcess (the default). Job: TemplateOrchestrateCP (recommend) includes checkpointing; however, is will be necessary for you to install the custom component (also by the authors of the Talend Framework) tCheckpoint.
It is permissible for an orchestration Job to call another orchestration Job, or Job: TemplateTask directly.
For an example of orchestration, take a look at the template Job: TMigrate.
Job: TMigrate is a new template Job that is built for Data Migration and other similar activities.
Introduction of a new example Job that demonstrates many of the features of the Talend Framework 1.7.
Class: Framework (Routines)
The static Framework class now includes some additional features.
The Framework class now supports a Concurrent Hash Map that is available to all Jobs. A number of setters and getters are provided, for convenience. This new, globally accessible, object simplifies the passing of certain parameters from a Job to its parent and sibling Jobs.
A number of standard sharedMap objects are made available for interacting with the Framework.
Determines if the next orchestration Job should be executed. Allows a graceful end to orchestration, when set to false.
Allows an error message to be set prior to Job termination, in the event of an error. This message may be used during Framework exception handling and reporting. This value may be set by the Framework as well as being set or appended to by developer-generated code.
Allows a documentation URL to be specified, which may be incorporated within error messages.
Allows the retention period of aged log files, to be specified.
Added the ability to prune statsDir, using the same retention policy as logDir.
Improvements and bug fixing to the following routines.
If you are installing the Talend Framework version 1.7 in to a project where a previous version of the Talend Framework has not been installed, please follow these instructions.
If you are upgrading from a previous version of the Talend Framework, you should follow these same instructions; but you should also take note of the recommendations under Upgrading, below.
If you’re upgrading your project from a version of the Talend Framework prior to version 1.4, then should should follow the usual installation instructions; however, you should note the following.
If you have made your own changes to the default values of any Framework Context Groups, then you will need to re-apply these changes. Prior to installation, you should ensure that you have made a note of what these changes are.
It is not, normally, expected that that you will be changing these values; however, there may be some circumstances where you have chosen to modify default values within the following two Context Groups.
File System Default Value Changes
Version 1.4 of the Talend Framework introduced some changes to the default File System locations. This was to simplify your file system structure and administration.
It is recommended that you use these new defaults; however, you may amend these to the previous values, if you choose.