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, this is not a problem as m-Power handles the above steps without issue. m-Power simply issues a reload command directly on the m-Power server utilizing the localhost address and whatever port the developer used to access m-Power.
However, if your server setup is unique (For instance you are running SSL or are utilizing a reverse proxy setup), there is a chance that Tomcat will not automatically reload. In cases of SSL users, it is likely that your SSL certificate was not authorized to the “localhost” address and our automatic reload command will be denied. For users who utilize a reverse proxy, it is likely that the port the user has entered via m-Power, is not the true m-Power port.
If you find that you compile a new application, but receive a 404 error when you try to run the application in development and can only rectify this issue by restarting Tomcat, it is likely this document pertains to you.
To resolve this problem, please do the following: Edit the mrctool.properties file in \m-power\proddata\conf. Add the following line to the end of the document:
mpower_server=https://servername:serverport
Note: Be sure to use a valid servername that is accessible to your m-Power server. This should be the server name that this machine would call itself. A great way to test this is to try to PING the machine from itself using the servername you plan on specifying.
Be sure to use a valid serverport. You should use the serverport that Tomcat is listening on, found in \m-power\tomcat\server.xml
If you are still having issues, contact our support department, and we will be happy to assist.