Hi Jake, A simple Tomcat Context fragment should work. That's all I tend to use. So, for example, having a file named:
[tomcat]/conf/Catalina/localhost/ROOT.xml All that file needs to contain is one line...something like this: <Context docBase="[dspace path]/webapps/xmlui" /> Technically, this same sort of configuration should also work in your server.xml, under the <Host> section (though, in that situation you'd want to specify a "path="/"" attribute, like in your example) If that's *not* working for you, you may want to look closer at whether Tomcat is reporting errors in its log files. The errors in the Tomcat logs may provide us with more information about what Tomcat doesn't like about your configuration. So, please send any errors to this list and hopefully we can help you figure them out. Tim On Wed, Oct 31, 2018 at 10:13 AM Cameron, Jacob <[email protected]> wrote: > Hi Everyone, > > > > Windows Server 2016, Tomcat 8.5, DSpace 6.3. > > > > I’ve setup the context path in server.xml to be path=“/” docBase=”[dspace > path]\webapps\xmlui” and I get a blank page when I go to > http://localhost:8080/, however if I go to http://localhost:8080/xmlui it > works fine. > > > > I’ve tried the context fragments, with ROOT.xml in > tomcat\conf\catalina\localhost\ and still have the same issue. Restarted > the tomcat server, restarted the server, still having not luck. Any > suggestions? > > > > <Host name="localhost" appBase="[dspace path]webapps" > unpackWARs="true" autoDeploy="true"> > > <context path="/" docBase="[dspace > path]\webapps\xmlui" reloadable="true" cachingAllowed="False" > allowLinking="true"/> > > > > Jake > > -- > > Jake Cameron, BCS(UNB) > > Systems Support Specialist III > > Information Systems and Technical Services University of Lethbridge Library > > Phone:(403)329-2756 <(403)%20329-2756> > > This e-mail, including any and all attachments, is only for the use of the > intended recipient(s) and may contain information that is confidential or > privileged. If you are not the intended recipient, you are advised that any > dissemination, copying or other use of this e-mail is prohibited. Please > notify the sender of the error in communication by return e-mail and > destroy all copies of this e-mail. Thank you. > > > > -- > All messages to this mailing list should adhere to the DuraSpace Code of > Conduct: https://duraspace.org/about/policies/code-of-conduct/ > --- > You received this message because you are subscribed to the Google Groups > "DSpace Technical Support" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at https://groups.google.com/group/dspace-tech. > For more options, visit https://groups.google.com/d/optout. > -- Tim Donohue Technical Lead for DSpace & DSpaceDirect DuraSpace.org | DSpace.org | DSpaceDirect.org -- All messages to this mailing list should adhere to the DuraSpace Code of Conduct: https://duraspace.org/about/policies/code-of-conduct/ --- You received this message because you are subscribed to the Google Groups "DSpace Technical Support" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/dspace-tech. For more options, visit https://groups.google.com/d/optout.
