One of the most flexible uses of m-Power is the ability to use a table from anywhere on your database within an application. This is very useful for times where you have an ERP that needs to be used across multiple dictionaries. Alternatively, there will also be times where a…
Overview While there are many reasons why having a development instance and a production instance of m-Power is necessary, one of the strongest reasons is the instability of the development environment. With recompiling, constant changes, and Tomcat restarts, development is not designed for end users to access applications. This separation…
Overview m-Power can easily be configured to use any existing encrypted column for password values when securing your applications against a flat file. For more on how to do this, see this page. While this works great for existing encryptions, it is also possible to use m-Power to encrypt new…
A security feature of Tomcat is that prior to an application being eligible to be hosted by Tomcat, it first must be enrolled into the web.xml file located in \m-power\mrcjava\WEB-INF. Before the change can be recognized by Tomcat, the run-time context must be restarted. For the majority of our clients,…
A little known, but useful, feature within m-Power Sign-on Security Logic is the ability to call database procedures immediately after a user signon and/or immediately before a user signoff. While there are numerous applications for such a utility, perhaps the most popular use is to track user activity. Here is…