• State Not Answered
  • Replies 9 replies
  • Subscribers 10 subscribers
  • Views 3518 views
  • Users 0 members are here
Related Discussions
Home » Discussions » Administration

I have recently upgraded a 7.11 install to a 16.1 install, and was unable to reu

PhilB
Certified Lead Developer
I have recently upgraded a 7.11 install to a 16.1 install, and was unable to reuse my configuration repository. I've been able to reuse that same repository from 7.9 through to 7.11, but doing so for 16.1 resulted in various errors (such as Exception: ObjectNotFoundException[SYSTEM_RECORD_TYPE_USER]), despite applying the (very few) changes recorded in the documentation.

My main concern was with the changes in the web.xml file; there are quite a few new items in the new version (com.appiancorp.common.logging.ConfigureLog4j, com.appiancorp.rdbms.datasource.BusinessDataSourceValidator, com.appiancorp.applications.BundledApplicationsLoader for example), and simply inserting the new web.xml into the old repository does not work.

I understand that the way around this is to create a new repository, then merge my changes from the old repository into the new one, but that seems to rather defeat the object of...

repositories.zip

OriginalPostID-191179

OriginalPostID-191179

  Discussion posts and replies are publicly visible

Parents
  • 0
    Certified Lead Developer
    @Eliot, The structural problem with that upgrade document is that in reality you're performing steps 9,10,11,12 before step 5 when using a config repo. And step 5 becomes a loaded step in the process. I've been around long enough that I know that this doc was written before the config repo, or before even ACM was made a public tool, so it was designed for folks who are doing the upgrade manually. In my experience, it just doesn't match reality. I'll be happy to discuss more offline.
Reply
  • 0
    Certified Lead Developer
    @Eliot, The structural problem with that upgrade document is that in reality you're performing steps 9,10,11,12 before step 5 when using a config repo. And step 5 becomes a loaded step in the process. I've been around long enough that I know that this doc was written before the config repo, or before even ACM was made a public tool, so it was designed for folks who are doing the upgrade manually. In my experience, it just doesn't match reality. I'll be happy to discuss more offline.
Children
No Data

© 2024 Appian. All rights reserved.