decouple daily rdahmm service and portlet

The daily rdahmm service must run on the same machine as the portlet under the previous configuration. Obviously this is not good, cause the service is doing the same thing on every machine deployed, costing a specific amount of resources; and it is hard to update the service once some changes are applied.

The portlet is now modified so that every portlet will try to fetch the xml result file from gf13 through http. This puts two requirements for gf13: 1) the web server should always be running; 2) the service should run there, and be updated in time. Since the xml file is updated once per day, the portlet will cache the file for a day after getting it every time. Since the portal servers are all deployed near gf13 presently, fetching the xml file (whose size is around 1.5M) only adds a trivial latency to the response time of the portlet, and this only happens once every day when the portlet is first requested.