There are two types of Message Handlers in DataStage.
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 a MettleCI plugin 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.
Anti-Pattern
Message Handlers are not an asset of DataStage. See Note below for an explanation why.
| 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. |
...
Organizations should refrain from using Message Handlers and should configure their Job Schedulers to be able to allow Warnings in exceptional circumstances. That way, high standards of development are generally maintained but in the unlikely situation that there is no alternative, Job Warnings can be allowed.
Message Handler Deployment Plug-In
There is a Bamboo Plugin to support deployment of Job-Level Message Handlers: dm-dsmsgh-plugin.
...
In order to use this MettleCI feature:
All Job-Level Message Handlers in a particular DataStage Project will need to be added to the corresponding Git repository, alongside the existing ISX files. These files need to be named following the "<Job Name>.msh" convention.
Continuous Integration Build Plans and Deployment Environments in Bamboo will need to be updated to execute the new "DataStage Message Handlers Task" immediately before the "DataStage Incremental Deployment Task".
For each Message Handler added to Git, the corresponding <Job Name>.isx jobs need to be checked in to Git again. This is necessary to ensure that the subsequent CI Build Plan deployment (triggered by the check-in) will process the Message Handler as necessary.
No changes to Bamboo Deployment Environment configuration is required.
How to Find the relevant Local.msh in the Information Server File System.
For example: There is a Job called “GR_ACCOUNTS_LOCAL"
Within the relevant Project filesystem, find the RT_SC<Job Number> directory that corresponds to the Job. The simplest method is to use Director to open up a log entry for the Job then get the "Job No." entry from that dialog box.
...
Within the RT_SC<Job Number> directory, find the Job-Level Message Handler config file (Local.msh)
Once found, copy and rename that file to GR_ACCOUNTS_LOCAL.msh and check it into Git alongside the existing ISX
...
file
Once this file has been checked in, re-check in the corresponding Job. This ensures that automated deployments pick it up.
The (updated) Continuous Integration Bamboo Plan for the corresponding DataStage Project will be auto-triggered and must complete successfully. This will ensure that subsequent deployments to other environments (Test, QA, Production) will include Job-Level Message Handlers.
Changes to CI Plans
Continuous Integration Build Plans in Bamboo will need to be updated to execute the "DataStage Message Handlers" Task.
...
Both the 'Root ISX directory' and 'Root message handler directory' fields must contain: datastage.
...
| Warning |
|---|
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. Even in the absence of such automation challenges, we suggest the general situation with Job Level Message Handlers ought to trigger customers to reconsider their use (or at least modify the tolerance of Warning Messages by dependent systems) and refactor accordingly. |
...