Appian Community
Site
Search
Sign In/Register
Site
Search
User
DISCUSS
LEARN
SUCCESS
SUPPORT
Documentation
AppMarket
More
Cancel
I'm looking for ...
State
Not Answered
Replies
9 replies
Subscribers
7 subscribers
Views
4032 views
Users
0 members are here
Share
More
Cancel
Related Discussions
Home
»
Discussions
»
Administration
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
OriginalPostID-191179
OriginalPostID-191179
Discussion posts and replies are publicly visible
Parents
0
PhilB
A Score Level 1
over 9 years ago
Yes, I read the release notes and implemented the required changes. They did not affect the errors I was seeing when using the 7.11 repository.
Whilst I was there, I noticed that the recommended JNDI naming had changed from java:jdbc/MyDatasource to jdbc/MyDatasource - though that, again, was not the issue. I assume the java: was redundant anyway.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
Reply
0
PhilB
A Score Level 1
over 9 years ago
Yes, I read the release notes and implemented the required changes. They did not affect the errors I was seeing when using the 7.11 repository.
Whilst I was there, I noticed that the recommended JNDI naming had changed from java:jdbc/MyDatasource to jdbc/MyDatasource - though that, again, was not the issue. I assume the java: was redundant anyway.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
Children
No Data