If a Dynamo module has any configuration specific to running on JBoss or any other application server, those configuration overrides should be made in one of the following layers, shown in ascending order of precedence for each supported application server:
Property Name | Directory Name | Usage |
|---|---|---|
|
| JBoss-specific live configurations |
|
| JBoss-specific configurations in named layer |
|
| JBoss-specific configurations |
|
| Any third-party application server configuration |
Property Name | Directory Name | Usage |
|---|---|---|
|
| WebLogic-specific live configurations |
|
| WebLogic-specific configurations in named layer |
|
| WebLogic-specific configurations |
|
| Any third-party application server configuration |
Property Name | Directory Name | Usage |
|---|---|---|
|
| WebSphere-specific live configurations |
|
| WebSphere-specific configurations in named layer |
|
| WebSphere-specific configurations |
|
| Any third-party application server configuration |
Note: If JBoss configuration files are stored in the ATG-3rdPartyConfig-Path layer, you might see errors when starting up some applications on other application servers, because the datasources are configured to point to JNDI names that are not set up on that application server. Datasource configuration files that are specific to JBoss should be in the ATG-JBossConfig-Path rather than the ATG-3rdPartyConfig-Path of those data source configurations.
