{"id":1035,"date":"2008-02-29T17:58:17","date_gmt":"2008-02-29T17:58:17","guid":{"rendered":"http:\/\/www.mrc-productivity.com\/techblog\/?p=1035"},"modified":"2023-09-12T14:08:07","modified_gmt":"2023-09-12T20:08:07","slug":"set-up-m-power-to-run-development-production-on-same-drive","status":"publish","type":"ht_kb","link":"https:\/\/www.mrc-productivity.com\/techblog\/?ht_kb=set-up-m-power-to-run-development-production-on-same-drive","title":{"rendered":"How to Setup an additional m-Power Production Environment"},"content":{"rendered":"\n<h2 class=\"wp-block-heading\">Overview<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">m-Power by default ships with a development and production environment. Often times on the helpdesk, I encounter inquires by administrators who are looking to create a third m-Power environment for one a few reasons:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>A QA\/Testing environment &#8211; They would like to create an intermediary stage for testing applications, between their development and production environments. Prior to promoting applications to production, they will be promoted to this QA instance first. Once vetted in the QA instance, then the applications will be promoted to the live production environment.<\/li>\n\n\n\n<li>A use as a standalone environment for automating scheduled tasks from m-Power &#8211; For m-Power customers that have a lot of scheduled task activity, creating a dedicated environment for these tasks to execute within will help ensure stability The process outlined below allows you to create a third instance of m-Power (i.e. a second &#8216;Production&#8217;). <\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-ht-blocks-messages wp-block-hb-message wp-block-hb-message--withicon\">This post will assume you have development and production installed on the same PC server, however the instructions can be apply regardless of where you install this third m-Power environment.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Steps<\/h2>\n\n\n\n<div class=\"wp-block-ht-blocks-list heroic-styled-list\" id=\"heroic-styled-list-\"><ol class=\"fa-ul\"><li>On the m-Power server in C:\\Program Files\\mrc (or whatever directory where m-Power is installed) , copy the existing production folder and rename the new copied directory. For customers creating a QA environment, I recommend naming the directory &#8216;QA&#8217;. For customers creating a scheduled task environment, I recommend naming the directory &#8216;scheduled&#8217;. In this example, I will call the third environment &#8216;production2&#8217;.<\/li><li>Go to &#8230;\\production2\\m-power\\tomcat\\conf and open server.xml. Rename line 22 so that server shutdown port <code>server port=XXXX<\/code> is different than what is currently listed. For instance, if it currently reads 8006, change it to 8007 (if available).<\/li><li>Rename line 67 so that the <code>connector port=XXXX<\/code> value is different than what is currently listed. For instance, if it currently reads 80, change to 8012 (if available).<\/li><li>Update the \/mrcjava context <code>docBase<\/code> (at the end of the server.xml file) to reference the new location of your production folder. For instance C:\/Program Files\/mrc\/<strong>production2<\/strong>\/m-power\/mrcjava<\/li><li>Save the server.xml file after completing steps 2-4.<\/li><li>Edit the messaging.properties file in \/production2\/m-power\/mrcjava\/job_streams and update the port number listed in the <code>mpower_server<\/code> property to reference the new connector port used in Step 3.<\/li><li>Edit the mrc-runtime.properties in &#8230;\/production2\/m-power\/mrcjava\/WEB-INF\/classes and update the port number on the <code>mpower_server<\/code> and <code>mrc_data_store_ip<\/code> lines.<\/li><li>Be sure to install the service for the second instance of Tomcat.<\/li><\/ol><style>#heroic-styled-list- li:before{\n\t\t\t\t\t\t   background:#000000;\n\t\t\t\t\t\t   border-radius: 0;\n\t\t\t\t\t\t   }<\/style><\/div>\n\n\n\n<p class=\"wp-block-paragraph\"><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Overview m-Power by default ships with a development and production environment. Often times on the helpdesk, I encounter inquires by administrators who are looking to create a third m-Power environment for one a few reasons: Steps<\/p>\n","protected":false},"author":1,"comment_status":"closed","ping_status":"open","template":"","format":"standard","meta":{"footnotes":""},"ht-kb-category":[],"ht-kb-tag":[],"class_list":["post-1035","ht_kb","type-ht_kb","status-publish","format-standard","hentry"],"_links":{"self":[{"href":"https:\/\/www.mrc-productivity.com\/techblog\/index.php?rest_route=\/wp\/v2\/ht-kb\/1035","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.mrc-productivity.com\/techblog\/index.php?rest_route=\/wp\/v2\/ht-kb"}],"about":[{"href":"https:\/\/www.mrc-productivity.com\/techblog\/index.php?rest_route=\/wp\/v2\/types\/ht_kb"}],"author":[{"embeddable":true,"href":"https:\/\/www.mrc-productivity.com\/techblog\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.mrc-productivity.com\/techblog\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=1035"}],"version-history":[{"count":3,"href":"https:\/\/www.mrc-productivity.com\/techblog\/index.php?rest_route=\/wp\/v2\/ht-kb\/1035\/revisions"}],"predecessor-version":[{"id":12131,"href":"https:\/\/www.mrc-productivity.com\/techblog\/index.php?rest_route=\/wp\/v2\/ht-kb\/1035\/revisions\/12131"}],"wp:attachment":[{"href":"https:\/\/www.mrc-productivity.com\/techblog\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=1035"}],"wp:term":[{"taxonomy":"ht_kb_category","embeddable":true,"href":"https:\/\/www.mrc-productivity.com\/techblog\/index.php?rest_route=%2Fwp%2Fv2%2Fht-kb-category&post=1035"},{"taxonomy":"ht_kb_tag","embeddable":true,"href":"https:\/\/www.mrc-productivity.com\/techblog\/index.php?rest_route=%2Fwp%2Fv2%2Fht-kb-tag&post=1035"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}