...
Project Level Message Handlers: These are installed in an application directory per Engine and and aren't supported by MettleCI so should be migrated manually.
Job Level Message Handlers: There is MettleCI functionality to support their deployment only. While MettleCI deploys Job Level Message Handler files from a Project's Git repository, it doesn't offer native check-in and deletion functions for them so they must be managed via command line Git.
The following observations about Message Handlers, based on field experience, lead us to suggest switching away from using them.
Message Handlers are not DataStage assets
Message Handlers are not an asset of DataStage. IBM documentation notes that they cannot be managed the same way as jobs, sequences, parameter set definitions, etc., are managed. They cannot be placed in an ISX export of their own, they have to be associated with a job.
| Note |
|---|
"You can use the IBM® InfoSphere® Information Server Manager (the deployment tool) to move, deploy, and control your IBM InfoSphere DataStage® and QualityStage® assets." However, message handlers cannot be managed individually using the IS Manager or istool command line tool. |
...
As previously highlighted, the very nature of IBM’s tools for managing Job Level Message Handlers in Information Server means any automation solution for them will be at risk of permanent regression with future IBM Fix Packs and Releases. SInce Since they are not “assets”, they may be regarded as “second class citizens” when breaking changes are introduced.
...