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

PhilB

Certified Lead Developer

over 8 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 Eliot Gerson
Appian Employee
over 8 years ago

Reusing a repository created with the configure script after updating Appian is not a documented or supported procedure. I'm actually quite surprised to hear this worked for you in the past. The idea of the repository isn't to carry configurations over across updates; it is to act as a change management tool for a given build of Appian and also facilitates setting up Appian in tandem with the configure script. The files within a repository may well need to be updated as improvements are made to Appian. Your best bet is to follow the documentation whenever you update Appian.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Reply

0 Eliot Gerson
Appian Employee
over 8 years ago

Reusing a repository created with the configure script after updating Appian is not a documented or supported procedure. I'm actually quite surprised to hear this worked for you in the past. The idea of the repository isn't to carry configurations over across updates; it is to act as a change management tool for a given build of Appian and also facilitates setting up Appian in tandem with the configure script. The files within a repository may well need to be updated as improvements are made to Appian. Your best bet is to follow the documentation whenever you update Appian.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Children

No Data