When you start using m-Power, what pieces should be saved for backups? m-Power is simple. The default setup is comprised of a development and production environment installed in the application server’s program files.


  • C:/Program Files/mrc/development/m-power
  • C:/Program Files/mrc/production/m-power

UNIX-Style OS (Linux)

  • /root/mrc/development/m-power
  • \root\mrc\production\m-power

Generated Applications

The generated applications are stored by default in a sub-directory:

  • \m-power\mrcjava\WEB-INF\classes\DD (for Windows)
  • /m-power/mrcjava/WEB-INF/classes/DD (for UNIX-style OS)

Where DD is the Data Dictionary name.

If you add “m-power” or “/m-Power” to your backup procedure, that will save the m-Power interface and all generated apps.

Be sure to do this for development and production.

Development Interface Metadata

The metadata (application specifications) are stored in a derby database folder:

\m-power\derby (for Windows)
/m-power/derby (for UNIX-style OS)

Adding the “derby” location to the backup procedure will ensure all application specs are saved.

SQL Database

In the database, m-Power will create one general schema named MRCAPPLLIB and another for each Data Dictionary to hold dictionary specific objects.

MRCAPPLLIB and each Data Dictionary should be added to the backup procedure on the database server.

Updated on April 5, 2023

Was this article helpful?

Related Articles

Need Support?
Can’t find the answer you’re looking for? Don’t worry we’re here to help!
Contact Support