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

PhilB

A Score Level 1

over 9 years ago

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

Discussion posts and replies are publicly visible

Parents

0 Jim Schweitzer
Certified Lead Developer
over 9 years ago

@Eliot, I think we'd all be better off if you (Appian) did look at supporting the repos as a tool to use across migrations. Some of us have some fairly complex installations to support, and putting together the repos are non-trivial.

I, like Phil, was able to use the same repo across 7.9, .10, and .11, which was very helpful. At a very minimum, tracking the config repo deltas in release notes like you do for the config file changes would be a start.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Reply

0 Jim Schweitzer
Certified Lead Developer
over 9 years ago

@Eliot, I think we'd all be better off if you (Appian) did look at supporting the repos as a tool to use across migrations. Some of us have some fairly complex installations to support, and putting together the repos are non-trivial.

I, like Phil, was able to use the same repo across 7.9, .10, and .11, which was very helpful. At a very minimum, tracking the config repo deltas in release notes like you do for the config file changes would be a start.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Children

No Data