Migrator


Migrator is currently in beta for its first release.  Please download and follow the setup instructions in the Manual. You can do everything except deploy without a license, but you can get a free 1 month license by contacting me with your Remedy host id.

APL Migrator was born out of a simple philosophy. The need to readily, and reliably move a release from one server to to another. The problem with existing tools was that they require you to define, at the time of migration what needs to be moved. Unfortunately, a given release could have been developed over a period of months, from multiple different developers, and the task of keeping track of what was changed several months ago is often daunting and problematic. The problem is often compounded by the fact that code has been migrated from Dev to Test in a piecemeal fashion, and it’s often difficult to verify that everything that has been migrated to Test makes it to Production when it comes time.
This tool was developed to address those problems and make it easier, streamlined, and automated. The concept is that each developer will add their code to a release package as they work on it. That package is then used to migrate to the Test server. Because the migration to Test is done by the tool, it’s no longer necessary for the developers to have an account on Test, nor is there a need to keep track of what was moved to Test because it was moved from the package. Then, when it comes time to deploy to Production, you simply change the destination server, press a button, and the same workflow that went to Test is then pushed to Production.

Licensing
This tool is licensed per migration server. That is to say, you only need one migration server in any environment. It is not restricted in how many packages are developed, not restricted in how many source or destination servers are used. The license is used only for deployments, this means that you can setup packages, setup environments and stage any/all workflow you need, but will require to be licensed in order to initiate a deployment. A free trial license can be obtained that will allow testing out of the software without purchase. A license to the tool entitles you to unlimited perpetual use of the version purchased and provides you with a 1 year support subscription. The support subscription entitles you to free license upgrades during your subscription period as well as support of the tool.

Current features include:

Setup/Manage Packages
Setup/Manage Environments
Stage Workflow:
-Active Link
-Active Link Guide
-Application
-Escalation
-Field
-Filter
-Filter Guide
-Form
-Image
-Menu
-Packing List
-Web Service
Deploy to destination environment

The future for this tool is very bright. I have a complete list of features that I’ll be adding as I move forward including automatic staging of workflow through the Version Control system, Data manipulation, and even Direct SQL commands.


Leave a comment

Your email address will not be published. Required fields are marked *

5 thoughts on “Migrator

    • LJ LongWing Post author

      Susanne,
      All I need for a Trial/Full license key is the Host ID (same one used to license Remedy server itself). The only thing the license is necessary for is to deploy, all other aspects of the application can be used without a license key.

    • LJ LongWing Post author

      Susanne,
      APL Migrator takes a different approach to migration. APL Migrator is a migration package that is designed to be built by the developer(s) of a given release as they develop it, utilizing the same App server they are developing and unit testing on, allowing iterative deployments to the Test environment during a given release cycle, always maintaining a consistent deployment methodology. AR Migrator provided by BMC requires you to keep track of your changes as you make them in a word doc, excel spreadsheet, etc, and then either script it all at the end of a cycle, or manually applying the changes on release day.

      APL Migrator also allows the people setting up the migration package to be completely isolated from the Test/Prod environments that are being deployed to because the deployment is push button simple, the ‘Release’ team can be responsible for pushing that button.