Solutions for Popular Administrative Maintenance Tasks | Part 3

Using Migration Manager to package and deploy certain attribute changes without migrating the whole object

Use Case: 

Many organizations launch multiple parallel projects or a project with parallel delivery lines, those projects often require making different changes to the same object, such as attribute changes in our example, and they can eventually be deployed separately to UAT environment or Production. The most popular way to deploy those changes is Maximo Migration Manager. However, that can create a predicament to project managers and consultants, because using Migration Manger we can only migrate whole objects, which consequently will deploy unwanted changes.

Method and Reasoning: 

Migration Manager utilizes Object Structures to export and import changes from environment to another, so, the solution should be as easy as creating an Object Structure for MAXATRRIBUTECFG object and use it in a Migration Group. Unfortunately, it is not that straight forward, because Maximo will throw a NullPointerException once we try to deploy the package, as it expects the Attributes MboSet to have an owner.

So, in order to work around this problem, we will write an Inbound Integration Automation Script against the Object Structure to force Maximo to deploy the attributes.

Implementation: 

1. Create an Object Structure DMMAXATTRCFG to be consumed by Migration manger Application, with only one source object MAXATTRIBUTECFG.

2. Make sure only the columns in the screenshot are restricted:

3. Create a Migration Group with only one Migration Object DMMAXATTRCFG

4. Create an Inbound Integration Automation Script against the new Object Structure

5. Copy and paste the below script source code, then click Create

6. Deploy the Object Structure and the Automation Script on the destination environments as well.

*Click to see Part 1 and Part 2 of Solutions for Popular Administrative Maintenance Tasks.