This discussion is now locked
Posted by Ed Matthews on 16 August 2011 at 13:04
Is there a companion piece that begins with a use case of a multi env deployment engine installation on one admin box, incorporates a source manager, and then shows
* migrate an internal customization
* download and deploy a hot fix
* download and deploy a Fix Pack
and accounts for the role of the Deployment Engine vs. Source Control and migrations?
Posted by Mr. Sampath Sriramadhesikan on 16 September 2011 at 11:51
@Ed: Migration Manager (MM) is a content migration tool. It does not support code migration or application of product fixes and patches. The installation of patches and fixes must be done in the respective environments using the appropriate 'Update Installer' tooling from IBM. Some clients store MM generated packages in a source control system. A collection of packages in source control is deemed to be their 'golden' build. MM offers no specific integrations to source control systems.
Posted by Mr. Jason Uppenborn on 6 April 2015 at 8:03
The way this document says to migrate Escalations doesn't work: trying to activate the escalation causes an error to be thrown. However, it seems that setting up an inbound rule to set ESCALATION.INSTACENAME to blank / null makes activating the escalation work.
Posted by Mr. Vasfi Gucer on 7 April 2015 at 7:24
Thank you Jason for sharing this with us.