Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

There are two types of Message Handlers in DataStage.

  1. 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.

  2. 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.

...

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.

...

How to Find the relevant Local.msh in the Information Server File System.

  1. For example: There is a Job called “GR_ACCOUNTS_LOCAL"

  2. 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.

    Image Modified
  3. Within the RT_SC<Job Number> directory, find the Job-Level Message Handler config file (Local.msh)

  4. Once found, copy and rename that file to GR_ACCOUNTS_LOCAL.msh and check it into Git alongside the existing ISX file 

...

  1. Image Added
  2. Once this file has been checked in, re-check in the corresponding Job. This ensures that automated deployments pick it up.

  3. 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.

...