<version>11</version>

                    <include src="base-other-termlistitem.xml"/>

                    <include src="base-other-reporting.xml"/>

                    <include src="base-other-reportingoutput.xml"/>

            </records>

    </spec>

Hi Elayne, This does ring a bell. When I do CollectionSpace upgrades and I want to see what needs to be changed in my configuration files, I diff the configuration files of the tenants that ship with CollectionSpace, to see how they've changed between the two versions. I can then use this as a guide for making changes to my own configuration files. It would be nice if there were documentation, but this works well enough for me. For example, diffing core-tenant.xml between 4.4 and 5.0 shows this: ray@rays-mbp-2 application (v5.0-branch)$ git diff --patch v4.4-branch -- tomcat-main/src/main/resources/core-tenant.xml *diff --git a/tomcat-main/src/main/resources/core-tenant.xml b/tomcat-main/src/main/resources/core-tenant.xml* *index a3e85c1..c7f6ec7 100644* *--- a/tomcat-main/src/main/resources/core-tenant.xml* *+++ b/tomcat-main/src/main/resources/core-tenant.xml* @@ -1,7 +1,6 @@ <cspace-config tenantname="core"> - <version>11</version> - <include src="settings.xml,local-core-settings.xml" merge="xmlmerge-settings.properties" + <include src="settings.xml,local-core-settings.xml" required="false" merge="xmlmerge-settings.properties" strip-root="yes" /> <spec> @@ -69,10 +68,10 @@ <include src="base-other-termlistitem.xml"/> <include src="base-other-reporting.xml"/> <include src="base-other-reportingoutput.xml"/> + <include src="base-other-batch.xml"/> + <include src="base-other-batchoutput.xml"/> + <include src="base-other-invocationresults.xml"/> <include src="base-other-searchall.xml"/> - - </records> - </spec> </cspace-config> I think you might be running into the need to add required="false" to the top <include> tag, if any of the files in the src list don't exist. Or you could change the src list to omit any file that doesn't exist. I believe the local-* file is in the list in the expectation that you might add one, but it's up to you. Ray On Sat, Oct 13, 2018 at 4:50 PM Elayne Glantzberg < solinox@solinoxenterprises.com> wrote: > Ok, I thought I might have dug up all the relevant stuff I needed, but I > must have missed something, because the core tenant is up but my custom > tenant is not. I do still not find any upgrade instructions anywhere that > covers moving from 4.4 to 5.0, and I also see that none of the pages for > creating custom tenants have been updated for 5.0. I'll keep digging and > trying, but in the meantime I'll throw my notes up here in case anything > rings a bell, or if anybody knows of something obviously needed that I've > missed. Please help if you can. > > Thanks, > > Elayne Glantzberg > Database Administrator, Aquarian Tabernacle Church > > Notes: > Documentation on CollectionSpace upgrade is lacking. I have a link to a > SQL script for modifying the postgre database to be compliant with the > current edition (5.0); however, the script was written for 4.1-5.0, so I > need to see if it will still work for 4.4 or if it need to be changed. > First, I am creating a new snapshot. It took about half the time as before > the system upgrade...nice! > Next, going through full install instructions step-by-step to make sure > packages are updated, but manually upgrading postgre and making script > changes; also minding post on Talk list re: upgrading from 4.5 to 5.0 > (fingers crossed) > sudo apt-get install ant maven imagemagick openjdk-8-jdk wget git > CSpace 5.0 requires postgre 9.6. Current version is 9.5. Need to upgrade. > Following instructions here: > https://gist.github.com/delameko/bd3aa2a54a15c50c723f0eef8f583a44 > made it through download and unpacking of tarball > > Still following instructions at > https://wiki.collectionspace.org/display/DOC/Installing+on+Ubuntu+LTS and > need to return to finish testing and running > Editing .bashrc to add/revise environment variables > Grabbing new source code -- renamed old source directory to save > installing source code -- BUILD SUCCESS > installing application code -- BUILD SUCCESS > deploying database -- failed -- "Target 'undeploy' does not exist in the > project 'app-tenant-mgmt'." Oh. Forgot to switch directories. That helped. > BUILD SUCCESSFUL > Moving on to the custom client code instructions at > https://wiki.collectionspace.org/display/DOC/Creating+your+new+tenant > Clone tenant, NOTE THERE IS NO LONGER A UI DIRECTORY IN 5.0, WIKIS HAVE > NOT BEEN UPDATED. Charging forward anyway. > Rebuild application successful, rebuild services successful, run "ant > undeploy deploy" and "ant import" successful > Moving on to post-install upgrade instructions at > https://wiki.collectionspace.org/display/DOC/Post-install+step+for+upgrading+to+v5.0 > modified security.properties > download and install UI...it's looking like pretty much everything on this > page has been done already > skip that, go on to adding our custom mods > services clean install, application clean install, services ant undeploy > deploy and import > start up server, clear browser cache, wait 5 minutes...and failed > going to http://50.116.6.153:8180/cspace/core/login successfully brings > up the core tenant, so obviously the failure is in the custom tenant > modified atcmuseum-tenant.xml to remove "merge" statement and just include > the modified file, run all the compiles---failure on "ant undeploy deploy" > with "Error encountered generating service bindings for > '/home/cspace/collectionspace-source/application/tomcat-main/src/main/resources/atcmuseum-tenant.xml' > tenant configuration." > Undo change, check config files, atcmuseum-tenant.xml is looking for > settings.xml, local-atcmuseum-settings.xml, and xmlmerge-settings.properties > Renamed atcmuseum/settings.xml to atcmuseum/local-atcmuseum-settings.xml, > run compiles...failed > switch to services/services/JaxRsServiceProvider folder, run "ant > deploy_services_artifacts"; shutdown and restart server...failed > > _______________________________________________ > Talk mailing list > Talk@lists.collectionspace.org > > http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org >