Skip to Content mrc logo mrc logo
  • What is m-Power?
    Overview Demos Build Process Case Studies Specs Pricing Trial
    m-Power Resources
    Overview How-To Videos Webinars & Podcasts White Papers Fact Sheets
  • What does m-Power build?
    Overview Database Front-Ends Reporting CRM Systems Business Intelligence Dashboards Inventory Management Mobile Apps ERP Enhancements Modernization Spreadsheets to the Web MS Access to the Web B2B/Web Portals Scheduling Embedded Analytics Web Forms Workflow Data Exploration Budgeting & Forecasting APIs & Web Services Db2 Web Query Alternative
    Solutions by Industry
    Overview Manufacturing Government Foodservice Software Vendors Logistics & Supply Chain Software Consultants Healthcare
  • Development Services Training Mentoring
  • Overview Partners Press Releases Careers Events Contact Blog
  • Support Home FAQ Documentation Customer Portal Enhancements Updates Roadmap Techblog
Try m-Power

m-Power Manual

Browse:

  • Home
  • Build Process
  • m-Power Build Process
Back to Manual

m-Power Build Process

The m-Power build process has two components:

  1. Template
  2. Application Specifications

The Template is the program shell that controls the functionality and the general layout for the application.

The m-Power Application Specifications are the detailed program definitions including, but not limited to: necessary tables, fields, table joins, record selections, work fields, and external program calls. m-Power users access the Application Specifications with a point-and-click interface.

The m-Power compile process combines the Application Specifications with the selected Template to generate the application. The compile process automates these steps:

  • Generate the Java source code, including the SQL database access statements.
  • Compile the Java source code into a J2EE Java servlet program.
  • Create the HTML presentation file.
  • Create the XML properties file for setting application-level options.
  • Deploy the entire package to the application server (Tomcat, by default.)

All layers of the generated program are fully customizable for the m-Power user. m-Power includes m-Painter, which has both a What-You-See-Is-What-You-Get (WYSIWYG) interface and a source code editor for maintaining the HTML presentation file and the XML properties file.

Learn more about making your first application by clicking here.

Created: January 20, 2010 | Modified: December 13, 2013

Search


Browse By Category

Build Process (13)
Starting with m-Power (8)
Retrievals (10)
Reports (15)
Summaries (4)
Maintainers (17)
Graphs (8)
m-Power Data Explorer (4)
General (24)
Calculations (5)
Utilities (9)
m-Power Administration (23)
Security (11)
Freemarker (6)
m-Painter (29)
Form Validation (5)
External Objects & UDFs (12)
Deprecated Documentation (23)
Bootstrap Templates (7)

Popular Tags

Application Properties Bar Graphs Excel App Properties Retrieval Record Selections Security Retrievals Dropdowns DB2 m-Painter Report Dates Graph Properties SQL Reports Administration Summaries Maintainer Parameters Compiling Maintainers Data Dictionary Production Build Process Advanced RPG Graphs Getting Started Database Graphing Email External Objects Performance Video Calculations Bootstrap Templates Freemarker Java mrc-Productivity Series Popular Prompt Screens Form Validation Admin Tomcat

See all tags »

michaels, ross & cole, ltd. (mrc)

Privacy Policy Cookie Policy Cookie Settings Notice at Collection Do Not Sell or Share My Personal Information

mrc (US)

2001 Midwest Road
Suite 310
Oak Brook, IL 60523
630-916-0662

mrc (UK)

Mortlake Business Centre
20 Mortlake High Street
London, SW14 8JN
+44-20-335-59566


© mrc. All rights reserved.