Upgrade > Customized files affected by upgrade

Customized files affected by upgrade

Before Codar is upgraded (now called Codar, you may need to back up customized files if they are not automatically restored or backed up by the upgrade installer. Automatically restored files retain their customizations after the upgrade. Automatically backed up files have been saved to the backup directory but must be manually restored after the upgrade.

This section lists customized files by location. The customized files listed are based on the features that you selected as being configured, customized, or used prior to the upgrade.

If you want to configure, customize, or use any of these features for the first time, see the following guides for more information: Codar Configuration Guide and Codar Console Help.

For files listed by feature and the actions to perform, see Customize Codar. For a list of customized files that must be manually backed up, see Initial setup.

Caution If you customized a file that is not listed here, you must manually back up this file (to a directory outside of CSA_HOME) before running the upgrade installer and then manually restore the file after running the upgrade installer. If you do not back up this file, the customizations will be lost after running the upgrade installer.

Customized files by location

CSA_HOME\jboss-as\bin\

Field Action
standalone.bat(Windows) Automatically restored
vault.bat (Windows) Automatically restored

standalone.conf (Linux)

 Automatically restored
vault.sh (Linux) Automatically restored

CSA_HOME\jboss-as\standalone\configuration\

Field Action
*.cer Automatically restored
.keystore Automatically restored
standalone.xml Automatically backed up, manually restore (for common access card)
Automatically restored (for all other features)

 

CSA_HOME\jboss-as\standalone\deployments\csa.war\custom\

Field Action

message.properties

Automatically restored

 

CSA_HOME\jboss-as\standalone\deployments\csa.war\custom-content\

Field Action

index.jsp

Automatically restored

 

CSA_HOME\jboss-as\standalone\deployments\csa.war\dashboard\

Field Action

config.json

Automatically backed up, manually restore

 

CSA_HOME\jboss-as\standalone\deployments\csa.war\dashboard\messages\common\

Field Action

message.properties

Automatically backed up, manually restore

 

CSA_HOME\jboss-as\standalone\deployments\csa.war\images\

Field Action

*.gif, *.jpeg, *.jpg, *.png

Automatically restored

 

CSA_HOME\jboss-as\standalone\deployments\csa.war\propertysources\

Field Action

*.jsp

Automatically backed up, manually restore

 

CSA_HOME\jboss-as\standalone\deployments\csa.war\WEB-INF\

Field Action

applicationContext.xml

Automatically backed up, manually restore
applicationContext-security.xml Automatically restored (for SiteMinder only) Automatically backed up, manually restore (for the following feature(s): single sign-on, common access card, Codar seeded users)

ssologout.jsp

Automatically backed up, manually restore
web.xml Automatically backed up, manually restore (for the following feature(s): Codar Console: session timeout, SiteMinder)

 

CSA_HOME\jboss-as\standalone\deployments\csa.war\WEB-INF\classes\

Field Action

csa.properties

Automatically restored
log4j.properties Automatically backed up, manually restore

 

CSA_HOME\jboss-as\standalone\deployments\idm-service.war\WEB-INF\classes\

Field Action

csa-consumer-users.properties

Automatically backed up, manually restore
web.xml Automatically backed up, manually restore
hpssoConfig.xml Automatically backed up, manually restore

 

CSA_HOME\jboss-as\standalone\deployments\idm-service.war\WEB-INF\spring\

Field Action

applicationContext.properties

Automatically restored
applicationContext.xml Automatically backed up, manually restore
applicationContext-common.xml Automatically restored
applicationContext-security.xml Automatically backed up, manually restore
applicationContext-v0.xml Automatically backed up, manually restore

 

CSA_HOME\jboss-as\standalone\logs\

Field Action
* all Automatically backed up, manually restore

CSA_HOME\portal\conf\

Field Action
* all Automatically restored

 

CSA_HOME\portal\node_modules\mpp-ui\dist\locales\*\

Field Action
rb.json Automatically backed up, manually restore

 

CSA_HOME\portal\node_modules\mpp-ui\dist\themes\<theme_directory>\styles\

Field Action
main.css Automatically backed up, manually restore

 

CSA_HOME\portal\node_modules\mpp-ui\dist\themes\default\styles\

Field Action
main.css Automatically backed up, manually restore

 

CSA_HOME\portal\node_modules\mpp-ui\dist\themes\pilot\styles\

Field Action
main.css Automatically backed up, manually restore

 

CSA_HOME\Tools\db-purge-tool\

Field Action
config.properties Automatically backed up, manually restore

 

CSA_HOME\Tools\ProcessDefinitionTool\

Field Action
db.properties Automatically backed up, manually restore
HPOOInfoInput.xml Automatically backed up, manually restore

 

CSA_HOME\Tools\ProviderTool\

Field Action
config.properties Automatically backed up, manually restore
provider.xml Automatically backed up, manually restore

CSA_HOME\Tools\SchemaInstallationTool\\

Field Action
config.properties Automatically backed up, manually restore

 

CSA_HOME\openjre\lib\security\

Field Action
cacerts Manually back up, manually restore
java.security Manually back up, manually restore

 

<user-specified location>

Field Action

*.jar (for dynamic queries)

 Manually back up, manually restore

*.jsp (custom for the Codar dashboard defined in the CSA_HOME\jboss-as\standalone/deployments/
csa.war/dashboard/config.json configuration file)

 Manually back up, manually restore

keystore file (defined by the certificate-key-file property of the connector attribute in
CSA_HOME\jboss-as\ standalone\configuration\
standalone.xml)

 Manually back up, manually restore

Send Help Center feedback