Setting up the Promote to Production Utility

Configuring the Promote to Production Utility

This video documentation will discuss how to configure the m-Power utility, Promote to Production. The purpose of this utility is to allow developers the ability to promote their applications to a production environment so they can be accessed by their users. This utility will allow the developer the ability to access all necessary components directly in the m-Power interface.

To begin click the Admin button, then click Utilities. Next, click “Promote to Production”

This is the administration section for the promotion utility. The first thing that needs to be done is to set up the locations of your m-Power environments. To do so click, hover over Administration option and select “Manage Promotion Locations.”

In this screen, specify the location of the m-Power folder of your development and production environments.  If your production instance is on a different server, you can utilize a mapped network drive, if available. If not, you can choose the .zip option. This option will create a zip-file on your development server that you can manually copy and extract on your production environment.  This option is also useful for customers who want to take regular snapshots of a projects’ changes.

Next, navigate to the Administration -> Manage CSS/HTML/XML file locations. Here you will see a list of “common” files that you can manually promote. When promoting an entire Data Dictionary, all files listed here will be promoted.  If you have other common files that need to be promoted, be sure to add them to the list. Please note that any files referenced require a root path of \mrcjava.

Lastly, under Administration, access “Manage Projects.” This utility was designed to support the ability to promote multiple groupings of projects. Here, developers can group applications from any number of dictionaries within a single project.



Please check out Part 2 of this documentation to learn how to use this feature by clicking here.

Created: February 21, 2013 | Modified: December 3, 2013