We are trying to apply hotfix "16.1 Hotfix Package A" to Appian 16.1

vamsib over 9 years ago

We are trying to apply hotfix "16.1 Hotfix Package A" to Appian 16.1 and while starting the Application Server getting the below error saying invalid Appian Datasource

The one which is currently working with primary data source without applying hotfix is as follows

conf.data.primary.datasource=jdbc/primaryds

==============================================================================================================================
07:33:33,941 INFO [stdout] (ServerService Thread Pool -- 82) 2016-02-25 07:33:33,941 [ServerService Thread Pool -- 82] ERROR com.appiancorp.common.config.ConfigObjectRepository - Cannot load the config object [locale-config:com.appiancorp.ap2.LocaleConfig], because it depends on the following config object which failed to load: initializeAdmin

07:33:34,050 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/suite]] (ServerService Thread Pool -- 82) JBWEB000287: Exception sendi...

Discussion posts and replies are publicly visible

0 vamsib over 9 years ago

...ng context initialized event to listener instance of class com.appiancorp.common.config.ConfigurationLoader: com.appiancorp.common.config.FatalConfigurationException: com.appiancorp.suiteapi.common.exceptions.AppianException: An unexpected error occurred while trying to initialize and validate the Appian data source. (APNX-1-4179-004)

Caused by: com.appiancorp.rdbms.config.PrimaryDataSourceNotConfiguredException: com.appiancorp.suiteapi.common.exceptions.AppianException: FATAL: No value configured for conf.data.APPIAN_DATA_SOURCE in custom.properties. An Appian datasource is required. The Appian application will fail to deploy. (APNX-1-4179-003)
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Stefan Helzle
A Score Level 3
over 9 years ago

I think in 16.1 the name of the parameter in custom.properties changed. See

forum.appian.com/.../Configuring_Relational_Databases.html

For customers upgrading from 7.11 or earlier, the name of the property that was conf.data.primary.datasource was changed to conf.data.APPIAN_DATA_SOURCE in version 16.1 and you must adjust your version of custom.properties to reflect this.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 vamsib over 9 years ago

Thanks stefanh for your response on this. We found root cause and this was due to incorrect custom properties file.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel