Community
Participate
Working Groups
Build Identifier: Spring DM Server 2.0.0.RELEASE 1. I am running multiple instances of Spring DM Server on a single VM, each instance for a different Application Domain. I have updated the PLAN file in the pickup directory as specified below - $ cat com.springsource.server.admin-2.0.0.RELEASE.plan <?xml version="1.0" encoding="UTF-8"?> <plan name="com.springsource.server.admin.plan" version="2.0.0" scoped="false" atomic="true" xmlns="http://www.springsource.org/schema/dm-server/plan" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.springsource.org/schema/dm-server/plan http://www.springsource.org/schema/dm-server/plan/springsource-dm-server-plan.xsd"> <artifact type="bundle" name="com.springsource.server.admin.content" version="[2.0,3.0)"/> <artifact type="bundle" name="com.springsource.server.admin.web" version="[2.0,3.0)"> <property name="header:Web-ContextPath" value="/appname/admin"/> </artifact> </plan> The PLAN starts fine. However, when I go to the http://host:8080/appname/admin/, the index page does not load due to the following hard-coding in index.htm - <meta http-equiv="REFRESH" content="0;url=/admin/web/info/overview.htm"> I have changed it as below in my environment to make it work - <meta http-equiv="REFRESH" content="0;url=web/info/overview.htm"> Reproducible: Always Steps to Reproduce: 1. Update the PLAN file as stated in the 'Details' section above. 2. Start the DM Server. 3. Go to http://localhost:8080/appname/admin/
Note that even if the index page redirection does not work with mentioned modification to the Web-ContextPath header, going directly to http://host:8080/appname/admin/web/artifact/overview.htm works.
The normal way to run multiple instances of dm Server on the same (virtual) machine is to assign each of them a different set of ports. Once that is done, there is no clash between the URLs of the admin consoles of the different instances. I'd like to understand how you are setting up ports. BTW this bugzilla is for Virgo so I presume you are looking for a fix on Virgo. Please confirm.
Yes, I understand that different instances of the server will need to run on different ports. However, I was looking to modify the context relative to the application, So that a similar security can be enforced to the Admin UI as well which is applied to the WAR bundles in the application domain. Yes, I am looking for a fix for this in Virgo.
Assigning to Chris for consideration.
Hi, Well spotted, it's a simple change so I have made it in master and it will be available in 2.2.0.M02. I have also left the property in the plan file so it is obvious to others that the context path can be changed easily. Does this resolve this issue for you or are you after something more? Chris.
Thank you Chris and Glyn for considering this. I liked the idea of leaving the property meta in the PLAN file to make it more obvious to the users if they want to change the context path. Thank you again for fixing it quickly.
