Search for	Example	Results
A single word	`cat`	Topics that contain the word "cat". You will also find its grammatical variations, such as "cats".
A phrase. You can specify that the search results contain a specific phrase.	`"cat food"` (quotation marks)	Topics that contain the literal phrase "cat food" and all its grammatical variations. Without the quotation marks, the query is equivalent to specifying an OR operator, which finds topics with one of the individual words instead of the phrase.

Search for	Operator	Example
Two or more words in the same topic	`AND` `and` `+` (plus symbol) `&` (ampersand)	`cat AND dog` `"cat food"+milk` `"cat food"&"dog food"`
Either word in a topic	`OR` `or` `\|` (pipe)	`cat OR dog` `cat \| dog`
Topics that do not contain a specific word or phrase	`NOT` `not` `!` (exclamation point)	`NOT cat` `! dog`
Topics that contain one string and do not contain another	`^` (caret)	`cat ^ mouse`
A combination of search types	`( )` parentheses	`cat + (dog \| mouse)` `cat \| dog + (! mouse)`

Cloud Service Automation4.80

Upgrade > Upgrade tasks > Recustomize CSA

Recustomize CSA

Note: You must recustomize CSA for the features configured, customized, or used prior to the upgrade only (complete only the tasks for features that were already configured, customized, or used prior to the upgrade).

If you want to configure, customize, or use any of these features for the first time, refer to the following guides for more information:

The following page lists files you may have customized in previous CSA installations and the necessary actions to complete for the CSA upgrade:

Configure the Cloud Service Management Console properties
Recustomize the Cloud Service Management Console dashboard
Configure the Cloud Service Management Console to import large archives
Recustomize the Cloud Service Management Console session timeout
Recustomize the Cloud Service Management Console dashboard title
Add custom graphic files or dynamic query scripts
Recustomize the CSA tools
Recustomize the CSA database user
Recustomize the CSA seeded users
Add Marketplace Portal themes
Add Marketplace Portal widgets
Configure ArcSight Logger
Integrate CSA with a common access card
Configure the Identity Management component
Configure IPv6
Configure the JBoss Password Vault
Configure Oracle RAC
Configure CSA to use a Single Sign-On
Integrate CSA with CA SiteMinder
Delete the sample consumer organization
Upgrade shortcuts
Marketplace Portal configuration

Configure the Cloud Service Management Console Properties

The following is the file that you may have customized for the Cloud Service Management Console and the actions required when you upgrade CSA:

File	Action
csa.properties	No action required.

File, Actions, and Locations

csa.properties

Action No action required. If this file was customized, the customizations have been merged with the upgraded file.

csa.properties
Action	No action required. If this file was customized, the customizations have been merged with the upgraded file.
File Location in CSA 4.80	Windows: `%CSA_HOME%\jboss-as\standalone\deployments\csa.war\WEB-INF\classes\` Linux: `$CSA_HOME/jboss-as/standalone/deployments/csa.war/WEB-INF/classes/`
Backed Up CSA 4.6x or 4.7x File Location in CSA 4.80	Windows: `%CSA_HOME%\_CSA_4_80_0_installation\Backup\standalone\csa.war\WEB-INF\classes\` Linux: `$CSA_HOME/_CSA_4_80_0_installation/Backup/standalone/csa.war/WEB-INF/classes/`

File Location in CSA 4.80

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

Linux: $CSA_HOME/jboss-as/standalone/deployments/csa.war/WEB-INF/classes/

Backed Up CSA 4.6x or 4.7x File Location in CSA 4.80

Windows: %CSA_HOME%\_CSA_4_80_0_installation\Backup\standalone\csa.war\WEB-INF\classes\

Linux: $CSA_HOME/_CSA_4_80_0_installation/Backup/standalone/csa.war/WEB-INF/classes/

Recustomize the Cloud Service Management Console dashboard

The following is a list of files that you may have customized for the Cloud Service Management Console dashboard and the actions required when you upgrade CSA:

File	Action
*.jsp	Required. Manually copy the JSP files from the backup directory to the appropriate directory in CSA 4.80 directory (see table below for more information).
config.json	Required. If this file was customized, you must recustomize this file (see table below for more information).
messages.properties	Required. Manually copy the file from the backup directory to the CSA 4.80 directory (see table below for more information).
index.jsp	No action required.

Files, Actions, and Locations

*.jsp
Action	Required. If you created custom Java server page (JSP) files for the CSA dashboard and saved them in a directory within the CSA 4.6x or 4.7x installation but not in a directory whose content is backed up by the upgrade installer, you should have backed up these files to preserve them. Otherwise, they will be deleted by the upgrade installer. Manually copy the JSP files from the backup directory to the appropriate directory in CSA 4.80 directory.
File Location in CSA 4.80	The directory where the Cloud Service Management Console expects to find these files, defined in the `config.json` dashboard configuration file.
Backed Up CSA 4.6x or 4.7x File Location in CSA 4.80	The directory to which the JSP files were backed up, either manually or by the upgrade installer, depending on where the files were located in CSA 4.6x or 4.7x.

config.json

config.json
Action	Required. If `config.json` file is customized, you must re-customize this file. In case you do not remember the customizations made to the file, refer to the back up copy and compare it to the file installed with CSA 4.80. Note: Port property has to be verified to contain a custom port, if such a port is used (or you can use the property from the backup of the previous CSA installation).
File Location in CSA 4.80	Windows: `%CSA_HOME%\jboss-as\standalone\deployments\csa.war\dashboard\` Linux: `$CSA_HOME/jboss-as/standalone/deployments/csa.war/dashboard/`
Backed Up CSA 4.6x or 4.7x File Location in CSA 4.80	Windows: `%CSA_HOME%\_CSA_4_80_0_installation\Backup\standalone\csa.war\dashboard\` Linux: `$CSA_HOME/_CSA_4_80_0_installation/Backup/csa.war/dashboard/`

Action

Required. If config.json file is customized, you must re-customize this file. In case you do not remember the customizations made to the file, refer to the back up copy and compare it to the file installed with CSA 4.80.

Note: Port property has to be verified to contain a custom port, if such a port is used (or you can use the property from the backup of the previous CSA installation).

File Location in CSA 4.80

Windows: %CSA_HOME%\jboss-as\standalone\deployments\csa.war\dashboard\

Linux: $CSA_HOME/jboss-as/standalone/deployments/csa.war/dashboard/

Backed Up CSA 4.6x or 4.7x File Location in CSA 4.80

Windows: %CSA_HOME%\_CSA_4_80_0_installation\Backup\standalone\csa.war\dashboard\

Linux: $CSA_HOME/_CSA_4_80_0_installation/Backup/csa.war/dashboard/

messages.properties

Action Required. Manually copy the file from the backup directory to the CSA 4.80 directory.

messages.properties
Action	Required. Manually copy the file from the backup directory to the CSA 4.80 directory.
File Location in CSA 4.80	Windows: `%CSA_HOME%\jboss-as\standalone\deployments\csa.war\dashboard\messages\dashboard\` Linux: `$CSA_HOME/jboss-as/standalone/deployments/csa.war/dashboard/messages/dashboard/`
Backed Up CSA 4.6x or 4.7x File Location in CSA 4.80	Windows: `%CSA_HOME%\_CSA_4_80_0_installation\Backup\standalone\csa.war\dashboard\messages\dashboard\` Linux: `$CSA_HOME/_CSA_4_80_0_installation/Backup/csa.war/dashboard/messages/dashboard/`

File Location in CSA 4.80

Windows: %CSA_HOME%\jboss-as\standalone\deployments\csa.war\dashboard\messages\dashboard\

Linux: $CSA_HOME/jboss-as/standalone/deployments/csa.war/dashboard/messages/dashboard/

Backed Up CSA 4.6x or 4.7x File Location in CSA 4.80

Windows: %CSA_HOME%\_CSA_4_80_0_installation\Backup\standalone\csa.war\dashboard\messages\dashboard\

Linux: $CSA_HOME/_CSA_4_80_0_installation/Backup/csa.war/dashboard/messages/dashboard/

index.jsp

Action No action required. If this file was customized, the customizations have been merged with the upgraded file.

index.jsp
Action	No action required. If this file was customized, the customizations have been merged with the upgraded file.
File Location in CSA 4.80	`Windows: %CSA_HOME%\jboss-as\standalone\deployments\csa.war\custom-content\` `Linux: $CSA_HOME/jboss-as/standalone/deploy ments/csa.war/custom-content/`
Backed Up CSA 4.6x or 4.7x File Location in CSA 4.80	`Windows: %CSA_HOME%\_CSA_4_80_0_installation\Backup\standalone\deployments\csa.war\custom-content\` `Linux: $CSA_HOME/_CSA_4_80_0_installation/Backup/standalone/deployments/csa.war/custom-content/`

File Location in CSA 4.80

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

Linux: $CSA_HOME/jboss-as/standalone/deploy ments/csa.war/custom-content/

Backed Up CSA 4.6x or 4.7x File Location in CSA 4.80

Windows: %CSA_HOME%\_CSA_4_80_0_installation\Backup\standalone\deployments\csa.war\custom-content\

Linux: $CSA_HOME/_CSA_4_80_0_installation/Backup/standalone/deployments/csa.war/custom-content/

Configure the Cloud Service Management Console to Import Large Archives

The following is the file that you customized to import large archives using the Cloud Service Management Console or REST API and the actions required when you upgrade CSA:

File	Action
Windows:standalone.conf.batLinux:standalone.conf	Required. If this file was customized, you must recustomize this file (see table below for more information).

File, Action, and Locations

Windows:standalone.conf.batLinux:standalone.conf
Action	Required. If this file was customized, you must recustomize this file. If you do not remember the customizations you made to the file, refer to the backed up copy and compare it to the file installed with CSA 4.80.
File Location in CSA 4.80	Windows: `%CSA_HOME%\jboss-as\bin\`Linux: `$CSA_HOME/jboss-as/bin/`
Backed Up CSA 4.6x or 4.7x File Location in CSA 4.80	Windows: `%CSA_HOME%\_CSA_4_80_0_installation\Backup\standalone\` Linux: `$CSA_HOME/_CSA_4_80_0_installation/Backup/standalone/`

Windows:standalone.conf.batLinux:standalone.conf

Action

Required. If this file was customized, you must recustomize this file. If you do not remember the customizations you made to the file, refer to the backed up copy and compare it to the file installed with CSA 4.80.

File Location in CSA 4.80

Windows: %CSA_HOME%\jboss-as\bin\Linux: $CSA_HOME/jboss-as/bin/

Backed Up CSA 4.6x or 4.7x File Location in CSA 4.80

Windows: %CSA_HOME%\_CSA_4_80_0_installation\Backup\standalone\

Linux: $CSA_HOME/_CSA_4_80_0_installation/Backup/standalone/

Recustomize the Cloud Service Management Console Session Timeout

The following file may have been customized if you updated the Cloud Service Management Console session:

File	Action
web.xml	Required. If this file was customized, you must recustomize this file (see table below for more information).

File, Action, and Locations

web.xml

web.xml
Action	Required. If this file was customized, you must recustomize this file. If you do not remember the customizations you made to the file, refer to the backed up copy and compare it to the file installed with CSA 4.80.
File Location in CSA 4.80	Windows: `%CSA_HOME%\jboss-as\standalone\deployments\csa.war\WEB-INF\` Linux: `$CSA_HOME/jboss-as/standalone/deployments/csa.war/WEB-INF/`
Backed Up CSA 4.6x or 4.7x File Location in CSA 4.80	Windows: `%CSA_HOME%\_CSA_4_80_0_installation\Backup\standalone\csa.war\WEB-INF\` Linux: `$CSA_HOME/_CSA_4_80_0_installation/Backup/standalone/csa.war/WEB-INF/`

Action

File Location in CSA 4.80

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

Linux: $CSA_HOME/jboss-as/standalone/deployments/csa.war/WEB-INF/

Backed Up CSA 4.6x or 4.7x File Location in CSA 4.80

Windows: %CSA_HOME%\_CSA_4_80_0_installation\Backup\standalone\csa.war\WEB-INF\

Linux: $CSA_HOME/_CSA_4_80_0_installation/Backup/standalone/csa.war/WEB-INF/

Recustomize the Cloud Service Management Console dashboard Title

The following file may have been customized if you updated the Cloud Service Management Console dashboard title:

File	Action
messages.properties	Required. Manually copy the file from the backup directory to the CSA 4.80 directory (see table below for more information).

File, Action, and Locations

messages.properties

Action Required. Manually copy the file from the backup directory to the CSA 4.80 directory.

messages.properties
Action	Required. Manually copy the file from the backup directory to the CSA 4.80 directory.
File Location in CSA 4.80	Windows: `%CSA_HOME%\jboss-as\standalone\deployments\csa.war\custom\` Linux: `$CSA_HOME/jboss-as/standalone/deployments/csa.war/custom/`
Backed Up CSA 4.6x or 4.7x File Location in CSA 4.80	Windows: `%CSA_HOME%\_CSA_4_80_0_installation\Backup\standalone\csa.war\custom\` Linux: `$CSA_HOME/_CSA_4_80_0_installation/Backup/csa.war/custom/`

File Location in CSA 4.80

Windows: %CSA_HOME%\jboss-as\standalone\deployments\csa.war\custom\

Linux: $CSA_HOME/jboss-as/standalone/deployments/csa.war/custom/

Backed Up CSA 4.6x or 4.7x File Location in CSA 4.80

Windows: %CSA_HOME%\_CSA_4_80_0_installation\Backup\standalone\csa.war\custom\

Linux: $CSA_HOME/_CSA_4_80_0_installation/Backup/csa.war/custom/

Add Custom Graphic Files or Dynamic Query Scripts

The following is a list of custom files that you may have added and the actions required when you upgrade CSA:

File	Action
*.jsp (dynamic query scripts)	Required. Manually copy any custom dynamic query scripts from the backup directory to the CSA 4.80 directory (see table below for more information).
*.jar (dynamic query scripts)	Required. Manually copy any custom dynamic query scripts from the manual backup copies you made before running the upgrade installer.
.jpg, .jpeg, .gif, .png	No action required.

Files, Actions, and Locations

*.jsp (dynamic query scripts)

Action Required. Manually copy any custom dynamic query scripts from the backup directory to the CSA 4.80 directory.

*.jsp (dynamic query scripts)
Action	Required. Manually copy any custom dynamic query scripts from the backup directory to the CSA 4.80 directory.
File Location in CSA 4.80	Windows: `%CSA_HOME%\jboss-as\standalone\deployments\csa.war\propertysources\` Linux: `$CSA_HOME/jboss-as/standalone/deployments/csa.war/propertysources/`
Backed Up CSA 4.6x or 4.7x File Location in CSA 4.80	Windows: `%CSA_HOME%\_CSA_4_80_0_installation\Backup\standalone\csa.war\propertysources\` Linux: `$CSA_HOME/_CSA_4_80_0_installation/Backup/csa.war/propertysources/`

File Location in CSA 4.80

Windows: %CSA_HOME%\jboss-as\standalone\deployments\csa.war\propertysources\

Linux: $CSA_HOME/jboss-as/standalone/deployments/csa.war/propertysources/

Backed Up CSA 4.6x or 4.7x File Location in CSA 4.80

Windows: %CSA_HOME%\_CSA_4_80_0_installation\Backup\standalone\csa.war\propertysources\

Linux: $CSA_HOME/_CSA_4_80_0_installation/Backup/csa.war/propertysources/

*.jar (dynamic query scripts)
Action	Required. Manually copy any custom dynamic query scripts from the manual backup copies you made before running the upgrade installer.
File Location in CSA 4.80	<user-specified location>
Backed Up CSA 4.6x or 4.7x File Location in CSA 4.80	<user-specified location>

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

Action No action required. All custom graphics of the listed types in the associated directory are automatically restored.

.jpg, .jpeg, .gif, .png
Action	No action required. All custom graphics of the listed types in the associated directory are automatically restored.
File Location in CSA 4.80	Windows: `%CSA_HOME%\jboss-as\standalone\deployments\csa.war\images\` Linux: `$CSA_HOME/jboss-as/standalone/deployments/csa.war/images/`
Backed Up CSA 4.6x or 4.7x File Location in CSA 4.80	Windows: `%CSA_HOME%\_CSA_4_80_0_installation\Backup\standalone\csa.war\images\` Linux: `$CSA_HOME/_CSA_4_80_0_installation/Backup/csa.war/images/`

File Location in CSA 4.80

Windows: %CSA_HOME%\jboss-as\standalone\deployments\csa.war\images\

Linux: $CSA_HOME/jboss-as/standalone/deployments/csa.war/images/

Backed Up CSA 4.6x or 4.7x File Location in CSA 4.80

Windows: %CSA_HOME%\_CSA_4_80_0_installation\Backup\standalone\csa.war\images\

Linux: $CSA_HOME/_CSA_4_80_0_installation/Backup/csa.war/images/

Recustomize the CSA Tools

The following is a list of files that you may have customized if you ran any of the CSA tools and the actions required when you upgrade CSA:

File	Action
config.properties (Content Installer, Health Tool, Purge Tool, Provider Configuration Tool)	Required. Manually copy any custom configuration files from the backup directory to the CSA 4.80 directory (see table below for more information).
provider.xml (Provider Configuration Tool)	Required. Manually copy any custom input files from the backup directory to the CSA 4.80 directory (see table below for more information).

Files, Actions, and Locations

config.properties

config.properties
Action	Required. Manually copy any custom configuration files from the backup directory to the CSA 4.80 directory. This is the generic name of the configuration file used in some examples for the Content Archive Tool, Purge Tool, and Provider Configuration Tool. If you used a different name for the configuration file, copy that file instead.
File Location in CSA 4.80	Windows:`%CSA_HOME%\Tools\DBPurgeTool\ %CSA_HOME%\Tools\ProviderTool\` Linux:`/ $CSA_HOME/Tools/DBPurgeTool/ $CSA_HOME/Tools/ProviderTool/`
Backed Up CSA 4.6x or 4.7x File Location in CSA 4.80	Windows:`%CSA_HOME%\_CSA_4_80_0_installation\Backup\Tools\DBPurgeTool\ %CSA_HOME%\_CSA_4_80_0_installation\Backup\Tools\ProviderTool\` Linux:`$CSA_HOME/_CSA_4_80_0_installation/Backup/Tools/DBPurgeTool/ $CSA_HOME/_CSA_4_80_0_installation/Backup/Tools/ProviderTool/`

Action

Required. Manually copy any custom configuration files from the backup directory to the CSA 4.80 directory. This is the generic name of the configuration file used in some examples for the Content Archive Tool, Purge Tool, and Provider Configuration Tool. If you used a different name for the configuration file, copy that file instead.

File Location in CSA 4.80

Windows:%CSA_HOME%\Tools\DBPurgeTool\ %CSA_HOME%\Tools\ProviderTool\

Linux:/ $CSA_HOME/Tools/DBPurgeTool/ $CSA_HOME/Tools/ProviderTool/

Backed Up CSA 4.6x or 4.7x File Location in CSA 4.80

Windows:%CSA_HOME%\_CSA_4_80_0_installation\Backup\Tools\DBPurgeTool\ %CSA_HOME%\_CSA_4_80_0_installation\Backup\Tools\ProviderTool\

Linux:$CSA_HOME/_CSA_4_80_0_installation/Backup/Tools/DBPurgeTool/ $CSA_HOME/_CSA_4_80_0_installation/Backup/Tools/ProviderTool/

provider.xml

Action Required. Manually copy any custom provider input files from the backup directory to the CSA 4.80 directory. This is the generic name of the input file used in some examples for the Provider Configuration Tool. If you used a different name for the provider input file, copy that file instead.

provider.xml
Action	Required. Manually copy any custom provider input files from the backup directory to the CSA 4.80 directory. This is the generic name of the input file used in some examples for the Provider Configuration Tool. If you used a different name for the provider input file, copy that file instead.
File Location in CSA 4.80	Windows: `%CSA_HOME%\Tools\ProviderTool\` Linux: `$CSA_HOME/Tools/ProviderTool/`
Backed Up CSA 4.6x or 4.7x File Location in CSA 4.80	Windows: `%CSA_HOME%\_CSA_4_80_0_installation\Backup\Tools\ProviderTool\` Linux: `$CSA_HOME/_CSA_4_80_0_installation/Backup/Tools/ProviderTool/`

File Location in CSA 4.80

Windows: %CSA_HOME%\Tools\ProviderTool\

Linux: $CSA_HOME/Tools/ProviderTool/

Backed Up CSA 4.6x or 4.7x File Location in CSA 4.80

Windows: %CSA_HOME%\_CSA_4_80_0_installation\Backup\Tools\ProviderTool\

Linux: $CSA_HOME/_CSA_4_80_0_installation/Backup/Tools/ProviderTool/

Recustomize the CSA Database User

The following is the file that you may have customized if you updated the password of the CSA database user and the actions required when you upgrade CSA:

File	Action
standalone.xml	Required. If this file was customized, you must recustomize this file (see table below for more information).

Files, Actions, and Locations

standalone.xml
Action	Required. If this file was customized, you must recustomize this file. The customization required for this file is different from the previous release. Refer to the Cloud Service Automation Configuration Guide for more information. Caution Do NOT copy the backed up file over the new file. The file has changed in CSA 4.80 and the backed up file is different from the current version.
File Location in CSA 4.80	Windows: `%CSA_HOME%\jboss-as\standalone\configuration\` Linux: `$CSA_HOME/jboss-as/standalone/configuration/`
Backed Up CSA 4.6x or 4.7x File Location in CSA 4.80	Windows: `%CSA_HOME%\_CSA_4_80_0_installation\Backup\standalone\configuration\` Linux: `$CSA_HOME/_CSA_4_80_0_installation/Backup/standalone/configuration/` Backup - Windows: `C:\csabackup\` Linux: `/tmp/csabackup/`

standalone.xml

Action

Required. If this file was customized, you must recustomize this file. The customization required for this file is different from the previous release. Refer to the Cloud Service Automation Configuration Guide for more information.

Caution Do NOT copy the backed up file over the new file. The file has changed in CSA 4.80 and the backed up file is different from the current version.

File Location in CSA 4.80

Windows: %CSA_HOME%\jboss-as\standalone\configuration\

Linux: $CSA_HOME/jboss-as/standalone/configuration/

Backed Up CSA 4.6x or 4.7x File Location in CSA 4.80

Windows: %CSA_HOME%\_CSA_4_80_0_installation\Backup\standalone\configuration\

Linux: $CSA_HOME/_CSA_4_80_0_installation/Backup/standalone/configuration/

Backup - Windows: C:\csabackup\ Linux: /tmp/csabackup/

Recustomize the CSA Seeded Users

The following is a list of files that you may have customized if you updated the password of one or more seeded users and the actions required when you upgrade CSA:

File	Action
applicationContext-security.xml	Required. If this file was customized, you must recustomize this file (see table below for more information).
csa-consumer-users.properties	Required. If this file was customized, you must recustomize this file (see table below for more information).
provider-users.properties	Required. If this file was customized, you must recustomize this file (see table below for more information).
integrationusers.properties	No action required.
applicationContext.properties	Required. If this file was customized, you must recustomize this file (see table below for more information).

Files, Actions, and Locations

applicationContext-security.xml

applicationContext-security.xml
Action	Required. If `config.json` file is customized, you must re-customize this file. In case you do not remember the customizations made to the file, refer to the back up copy and compare it to the file installed with CSA 4.80. Note: Port property has to be verified to contain a custom port, if such a port is used (or you can use the property from the backup of the previous CSA installation).
File Location in CSA 4.80	Windows: `%CSA_HOME%\jboss-as\standalone\deployments\csa.war\WEB-INF\` Linux: `$CSA_HOME/jboss-as/standalone/deployments/csa.war/WEB-INF/`
Backed Up CSA 4.6x or 4.7x File Location in CSA 4.80	Windows: `%CSA_HOME%\_CSA_4_80_0_installation\Backup\standalone\csa.war\WEB-INF\` Linux: `$CSA_HOME/_CSA_4_80_0_installation/Backup/standalone/csa.war/WEB-INF/`

Action

Note: Port property has to be verified to contain a custom port, if such a port is used (or you can use the property from the backup of the previous CSA installation).

File Location in CSA 4.80

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

Linux: $CSA_HOME/jboss-as/standalone/deployments/csa.war/WEB-INF/

Backed Up CSA 4.6x or 4.7x File Location in CSA 4.80

Windows: %CSA_HOME%\_CSA_4_80_0_installation\Backup\standalone\csa.war\WEB-INF\

Linux: $CSA_HOME/_CSA_4_80_0_installation/Backup/standalone/csa.war/WEB-INF/

csa-consumer-users.properties

csa-consumer-users.properties
Action	Required. If you customized the roles of a seeded user, you must manually restore those roles. If you customized the password of a seeded user, the password is automatically restored. If you deleted a seeded user, the seeded user is automatically restored and you must manually remove that user. If you added a custom user, that user is automatically restored. If you do not remember the customizations you made to the file, refer to the backed up copy and compare it to the file installed with CSA 4.80.No action required.
File Location in CSA 4.80	Windows: `%CSA_HOME%\jboss-as\standalone\deployments\idm-service.war\WEB-INF\classes\` Linux: `$CSA_HOME/jboss-as/standalone/deployments/idm-service.war/WEB-INF/classes/`
Backed Up CSA 4.6x or 4.7x File Location in CSA 4.80	Windows: `%CSA_HOME%\_CSA_4_80_0_installation\Backup\standalone\idm-service.war\WEB-INF\classes\` Linux: `$CSA_HOME/_CSA_4_80_0_installation/Backup/idm-service.war/WEB-INF/classes/`

Action

Required. If you customized the roles of a seeded user, you must manually restore those roles. If you customized the password of a seeded user, the password is automatically restored. If you deleted a seeded user, the seeded user is automatically restored and you must manually remove that user. If you added a custom user, that user is automatically restored. If you do not remember the customizations you made to the file, refer to the backed up copy and compare it to the file installed with CSA 4.80.No action required.

File Location in CSA 4.80

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

Linux: $CSA_HOME/jboss-as/standalone/deployments/idm-service.war/WEB-INF/classes/

Backed Up CSA 4.6x or 4.7x File Location in CSA 4.80

Windows: %CSA_HOME%\_CSA_4_80_0_installation\Backup\standalone\idm-service.war\WEB-INF\classes\

Linux: $CSA_HOME/_CSA_4_80_0_installation/Backup/idm-service.war/WEB-INF/classes/

provider-users.properties

provider-users.properties
Action	Required. If you customized the roles of a seeded user, you must manually restore those roles. If you customized the password of a seeded user, the password is automatically restored. If you deleted a seeded user, the seeded user is automatically restored and you must manually remove that user. If you added a custom user, that user is automatically restored. If you do not remember the customizations you made to the file, refer to the backed up copy and compare it to the file installed with CSA 4.80.
File Location in CSA 4.80	Windows: `%CSA_HOME%\jboss-as\standalone\deployments\idm-service.war\WEB-INF\classes\` Linux: `$CSA_HOME/jboss-as/standalone/deployments/idm-service.war/WEB-INF/classes/`
Backed Up CSA 4.6x or 4.7x File Location in CSA 4.80	Windows: `%CSA_HOME%\_CSA_4_80_0_installation\Backup\standalone\idm-service.war\WEB-INF\classes\` Linux: `$CSA_HOME/_CSA_4_80_0_installation/Backup/idm-service.war/WEB-INF/classes/`

Action

File Location in CSA 4.80

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

Linux: $CSA_HOME/jboss-as/standalone/deployments/idm-service.war/WEB-INF/classes/

Backed Up CSA 4.6x or 4.7x File Location in CSA 4.80

Windows: %CSA_HOME%\_CSA_4_80_0_installation\Backup\standalone\idm-service.war\WEB-INF\classes\

Linux: $CSA_HOME/_CSA_4_80_0_installation/Backup/idm-service.war/WEB-INF/classes/

integrationusers.properties

integrationusers.properties
Action	Required. If you customized the roles of a seeded user, you must manually restore those roles. If you customized the password of a seeded user, the password is automatically restored. If you deleted a seeded user, the seeded user is automatically restored and you must manually remove that user. If you added a custom user, that user is automatically restored. If you do not remember the customizations you made to the file, refer to the backed up copy and compare it to the file installed with CSA 4.80.
File Location in CSA 4.80	Windows: `%CSA_HOME%\jboss-as\standalone\deployments\idm-service.war\WEB-INF\classes\` Linux: `$CSA_HOME/jboss-as/standalone/deployments/idm-service.war/WEB-INF/classes/`
Backed Up CSA 4.6x or 4.7x File Location in CSA 4.80	Windows: `%CSA_HOME%\_CSA_4_80_0_installation\Backup\standalone\idm-service.war\WEB-INF\classes\` Linux: `$CSA_HOME/_CSA_4_80_0_installation/Backup/idm-service.war/WEB-INF/classes/`

Action

File Location in CSA 4.80

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

Linux: $CSA_HOME/jboss-as/standalone/deployments/idm-service.war/WEB-INF/classes/

Backed Up CSA 4.6x or 4.7x File Location in CSA 4.80

Windows: %CSA_HOME%\_CSA_4_80_0_installation\Backup\standalone\idm-service.war\WEB-INF\classes\

Linux: $CSA_HOME/_CSA_4_80_0_installation/Backup/idm-service.war/WEB-INF/classes/

applicationContext.properties

applicationContext.properties
Action	Required. If you customized the password of a seeded user, the password is automatically restored. If you deleted a seeded user, the seeded user is automatically restored and you must manually remove that user. If you added a custom user, that user is automatically restored. If you do not remember the customizations you made to the file, refer to the backed up copy and compare it to the file installed with CSA 4.80. Note: The parameter `idm.csa.hostname` has to be fixed to contain the correct value (you can use the corrected value from the previous version of CSA).
File Location in CSA 4.80	Windows: `%CSA_HOME%\jboss-as\standalone\deployments\idm-service.war\WEB-INF\spring\` Linux: `$CSA_HOME/jboss-as/standalone/deployments/idm-service.war/WEB-INF/spring/`
Backed Up CSA 4.6x or 4.7x File Location in CSA 4.80	Windows: `%CSA_HOME%\_CSA_4_80_0_installation\Backup\standalone\idm-service.war\WEB-INF\spring\` Linux: `$CSA_HOME/_CSA_4_80_0_installation/Backup/standalone/idm-service.war/WEB-INF/spring/`

Action

Required. If you customized the password of a seeded user, the password is automatically restored. If you deleted a seeded user, the seeded user is automatically restored and you must manually remove that user. If you added a custom user, that user is automatically restored. If you do not remember the customizations you made to the file, refer to the backed up copy and compare it to the file installed with CSA 4.80.

Note: The parameter idm.csa.hostname has to be fixed to contain the correct value (you can use the corrected value from the previous version of CSA).

File Location in CSA 4.80

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

Linux: $CSA_HOME/jboss-as/standalone/deployments/idm-service.war/WEB-INF/spring/

Backed Up CSA 4.6x or 4.7x File Location in CSA 4.80

Windows: %CSA_HOME%\_CSA_4_80_0_installation\Backup\standalone\idm-service.war\WEB-INF\spring\

Linux: $CSA_HOME/_CSA_4_80_0_installation/Backup/standalone/idm-service.war/WEB-INF/spring/

Add Marketplace Portal Themes

The following are directories where you may have added customized themes for the Marketplace Portal and the action required when you upgrade CSA:

Directory	Action
<theme_directory>	Required. If you created a customized theme for the Marketplace Portal, you must manually copy these directories (one for the Marketplace Portal and one for the Identity Management component) and their content from the backup directory to the CSA 4.80 directory (see table below for more information).

Directories, Actions, and Locations

<theme_directory> (Marketplace Portal)
Action	Required. If you created a customized theme for the Marketplace Portal, you must manually copy this directory and its content from the backup directory to the CSA 4.80 directory.
File Location in CSA 4.80	Windows: `%CSA_HOME%\portal\node_modules\mpp-ui\dist\bower_components\mpp-theme\` Linux: `$CSA_HOME/portal/node_modules/mpp-ui/dist/bower_components/mpp-theme/`
Backed Up CSA 4.6x or 4.7x File Location in CSA 4.80	Windows: `%CSA_HOME%\_CSA_4_80_0_installation\Backup\portal\node_modules\mpp-ui\dist\bower_components\mpp-theme\` Linux: `$CSA_HOME/_CSA_4_80_0_installation/Backup/portal/node_modules/mpp-ui/dist/bower_components/mpp-theme/`

<theme_directory> (Marketplace Portal)

Action Required. If you created a customized theme for the Marketplace Portal, you must manually copy this directory and its content from the backup directory to the CSA 4.80 directory.

File Location in CSA 4.80

Windows: %CSA_HOME%\portal\node_modules\mpp-ui\dist\bower_components\mpp-*theme\

Linux: $CSA_HOME/portal/node_modules/mpp-ui/dist/bower_components/mpp-*theme/

Backed Up CSA 4.6x or 4.7x File Location in CSA 4.80

Windows: %CSA_HOME%\_CSA_4_80_0_installation\Backup\portal\node_modules\mpp-ui\dist\bower_components\mpp-*theme\

Linux: $CSA_HOME/_CSA_4_80_0_installation/Backup/portal/node_modules/mpp-ui/dist/bower_components/mpp-*theme/

<theme_directory> (Identity Management component)
Action	Required. If you created a customized theme for the Marketplace Portal, you must recreate this theme by creating a new directory in the CSA 4.80 directory : `idm-service.war/ui/bower_components`. This directory contains the Enterprise and Playful themes. The default theme is in the `idm-service.war/ui/styles` directory. The backup directory contains the previous versions of your themes; however, due to changes in the Identity Management component, that CSS is no longer applicable.
File Location in CSA 4.80	Windows: `%CSA_HOME%\jboss-as\standalone\deployments\idm-service.war\themes\bower_components` Linux: `$CSA_HOME/jboss-as/standalone/deployments/idm-service.war/themes\bower_components`
Backed Up CSA 4.6x or 4.7x File Location in CSA 4.80	Windows: `%CSA_HOME%\_CSA_4_80_0_installation\Backup\standalone\idm-service.war\themes\` Linux: `$CSA_HOME/` `4_80_0_installation\Backup\standalone\idm-service.war\themes\`

<theme_directory> (Identity Management component)

Action

Required. If you created a customized theme for the Marketplace Portal, you must recreate this theme by creating a new directory in the CSA 4.80 directory : idm-service.war/ui/bower_components.

This directory contains the Enterprise and Playful themes.
The default theme is in the idm-service.war/ui/styles directory.
The backup directory contains the previous versions of your themes; however, due to changes in the Identity Management component, that CSS is no longer applicable.

File Location in CSA 4.80

Windows: %CSA_HOME%\jboss-as\standalone\deployments\idm-service.war\themes\bower_components

Linux: $CSA_HOME/jboss-as/standalone/deployments/idm-service.war/themes\bower_components

Backed Up CSA 4.6x or 4.7x File Location in CSA 4.80

Windows: %CSA_HOME%\_CSA_4_80_0_installation\Backup\standalone\idm-service.war\themes\

Linux: $CSA_HOME/ 4_80_0_installation\Backup\standalone\idm-service.war\themes\

Add Marketplace Portal Widgets

The following is the directory where you may have added customized widgets for the Marketplace Portal and the action required when you upgrade CSA:

Directory	Action
<iFRAME_URL_structure>	Required. If you created a customized widget that uses an iFRAME that serves HTML pages for the Marketplace Portal, you must manually copy its URL structure and contents from the backup directory to the CSA 4.80 directory (see table below for more information).

Directory, Action, and Locations

<iFRAME_URL_structure>

Action Required. If you created a customized widget that uses an iFRAME that serves HTML pages for the Marketplace Portal, you must manually copy its URL structure and contents from the backup directory to the CSA 4.80 directory.

<iFRAME_URL_structure>
Action	Required. If you created a customized widget that uses an iFRAME that serves HTML pages for the Marketplace Portal, you must manually copy its URL structure and contents from the backup directory to the CSA 4.80 directory.
File Location in CSA 4.80	Windows: `%CSA_HOME%\portal\node_modules\mpp-ui\dist\` Linux: `$CSA_HOME/portal/node_modules/mpp-ui/dist/`
Backed Up CSA 4.6x or 4.7x File Location in CSA 4.80	Windows: `%CSA_HOME%\_CSA_4_80_0_installation\Backup\portal\node_modules\mpp-ui\dist\` Linux: `$CSA_HOME/_CSA_4_80_0_installation/Backup/portal/node_modules/mpp-ui/dist/`

File Location in CSA 4.80

Windows: %CSA_HOME%\portal\node_modules\mpp-ui\dist\

Linux: $CSA_HOME/portal/node_modules/mpp-ui/dist/

Backed Up CSA 4.6x or 4.7x File Location in CSA 4.80

Windows: %CSA_HOME%\_CSA_4_80_0_installation\Backup\portal\node_modules\mpp-ui\dist\

Linux: $CSA_HOME/_CSA_4_80_0_installation/Backup/portal/node_modules/mpp-ui/dist/

Configure ArcSight Logger

The following is the file that you may have customized if you integrated with the ArcSight Logger and the actions required when you upgrade CSA:

File	Action
log4j.xml properties	Required. You must recustomize the `log4j2.xml` file (see table below for more information).

File, Actions, and Locations

log4j.xml properties

log4j.xml properties
Action	Required. You must recustomize the `log4j2.xml` file. Refer to the Cloud Service Automation Integration with ArcSight Logger whitepaper for more information. Caution Do NOT copy the backed up file over the new file. The logger has been upgraded in CSA 4.80 and the backed up file is not compatible with the current version.
File Location in CSA 4.80	Windows: `%CSA_HOME%\jboss-as\standalone\deployments\csa.war\WEB-INF\classes\` Linux: `$CSA_HOME/jboss-as/standalone/deployments/csa.war/WEB-INF/classes/`
Backed Up CSA 4.6x or 4.7x File Location in CSA 4.80	Windows: `%CSA_HOME%\_CSA_4_80_0_installation\Backup\standalone\csa.war\WEB-INF\classes\` Linux: `$CSA_HOME/_CSA_4_80_0_installation/Backup/standalone/csa.war/WEB-INF/classes/`

Action

Required. You must recustomize the log4j2.xml file. Refer to the Cloud Service Automation Integration with ArcSight Logger whitepaper for more information.

Caution Do NOT copy the backed up file over the new file. The logger has been upgraded in CSA 4.80 and the backed up file is not compatible with the current version.

File Location in CSA 4.80

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

Linux: $CSA_HOME/jboss-as/standalone/deployments/csa.war/WEB-INF/classes/

Backed Up CSA 4.6x or 4.7x File Location in CSA 4.80

Windows: %CSA_HOME%\_CSA_4_80_0_installation\Backup\standalone\csa.war\WEB-INF\classes\

Linux: $CSA_HOME/_CSA_4_80_0_installation/Backup/standalone/csa.war/WEB-INF/classes/

Integrate CSA with a Common Access Card

Note
The CSA upgrade will detect the current Common Access Card (CAC) configuration and load it from the current JBoss directory during the pre-install phase via an InstallAnywhere context. This configuration is then later used to configure CAC during the post-install phase.

See the Cloud Service Automation Configuration Guide for more information on configuring CAC.

The following is a list of files that you customized when integrating CSA with a Common Access Card (CAC) and the actions required when you upgrade CSA:

File	Action
applicationContext.xml (Cloud Service Management Console)	Required. If this file was customized, you must recustomize this file (see table below for more information).
applicationContext.xml (Identity Management component)	Required. If this file was customized, you must recustomize this file (see table below for more information).
applicationContext-security.xml (Identity Management component)	Required. If this file was customized, you must recustomize this file (see table below for more information).
applicationContext-v0.xml (Identity Management component)	Required. This is a new file that must be customized (see table below for more information).
csa.properties	Required. If this file was customized, you must recustomize this file (see table below for more information).
java.security	Required. If this file was customized, you must recustomize this file (see table below for more information).
standalone.xml	Required. If this file was customized, you must recustomize this file (see table below for more information).

File	Action
rb.json	Required. If this file was customized, you must recustomize this file (see table below for more information).
main.css (default)	Required. If this file was customized, you must recustomize this file (see table below for more information).
main.css (pilot)	Required. If this file was customized, you must recustomize this file (see table below for more information).
main.css (custom theme)	Required. If this file was customized, you must recustomize this file (see table below for more information).
java.security	No action required.

Files, Actions, and Locations

applicationContext.xml (Cloud Service Management Console)
Action	Required. If this file was customized, you must recustomize this file. The customization required for this file is different from the previous release. Refer to the Cloud Service Automation Configuration Guide for more information. Caution Do NOT copy the backed up file over the new file. The file has changed in CSA 4.80 and the backed up file is different from the current version.
File Location in CSA 4.80	Windows: `%CSA_HOME%\jboss-as\standalone\deployments\csa.war\WEB-INF\` Linux: `$CSA_HOME/jboss-as/standalone/deployments/csa.war/WEB-INF/`
Backed Up CSA 4.6x or 4.7x File Location in CSA 4.80	Windows: `%CSA_HOME%\_CSA_4_80_0_installation\Backup\standalone\csa.war\WEB-INF\` Linux: `$CSA_HOME/_CSA_4_80_0_installation/Backup/standalone/csa.war/WEB-INF/`

applicationContext.xml (Cloud Service Management Console)

Action

Caution Do NOT copy the backed up file over the new file. The file has changed in CSA 4.80 and the backed up file is different from the current version.

File Location in CSA 4.80

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

Linux: $CSA_HOME/jboss-as/standalone/deployments/csa.war/WEB-INF/

Backed Up CSA 4.6x or 4.7x File Location in CSA 4.80

Windows: %CSA_HOME%\_CSA_4_80_0_installation\Backup\standalone\csa.war\WEB-INF\

Linux: $CSA_HOME/_CSA_4_80_0_installation/Backup/standalone/csa.war/WEB-INF/

applicationContext.xml (Identity Management component)
Action	Required. If `config.json` file is customized, you must re-customize this file. In case you do not remember the customizations made to the file, refer to the back up copy and compare it to the file installed with CSA 4.80. Note: Port property has to be verified to contain a custom port, if such a port is used (or you can use the property from the backup of the previous CSA installation).
File Location in CSA 4.80	Windows: `%CSA_HOME%\jboss-as\standalone\deployments\idm-service.war\WEB-INF\spring\` Linux: `$CSA_HOME/jboss-as/standalone/deployments/idm-service.war/WEB-INF/spring/`
Backed Up CSA 4.6x or 4.7x File Location in CSA 4.80	Windows: `%CSA_HOME%\_CSA_4_80_0_installation\Backup\standalone\idm-service.war\WEB-INF\spring\` Linux: `$CSA_HOME/_CSA_4_80_0_installation/Backup/standalone/idm-service.war/WEB-INF/spring/`

applicationContext.xml (Identity Management component)

Action

Note: Port property has to be verified to contain a custom port, if such a port is used (or you can use the property from the backup of the previous CSA installation).

File Location in CSA 4.80

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

Linux: $CSA_HOME/jboss-as/standalone/deployments/idm-service.war/WEB-INF/spring/

Backed Up CSA 4.6x or 4.7x File Location in CSA 4.80

Windows: %CSA_HOME%\_CSA_4_80_0_installation\Backup\standalone\idm-service.war\WEB-INF\spring\

Linux: $CSA_HOME/_CSA_4_80_0_installation/Backup/standalone/idm-service.war/WEB-INF/spring/

applicationContext-security.xml (Identity Management component)
Action	Required. If this file was customized, you must recustomize this file. The customization required for this file is different from the previous release. Refer to the Cloud Service Automation Configuration Guide for more information. Caution Do NOT copy the backed up file over the new file. The file has changed in CSA 4.80 and the backed up file is different from the current version. .
File Location in CSA 4.80	Windows: `%CSA_HOME%\jboss-as\standalone\deployments\idm-service.war\WEB-INF\spring\` Linux: `$CSA_HOME/jboss-as/standalone/deployments/idm-service.war/WEB-INF/spring/`
Backed Up CSA 4.6x or 4.7x File Location in CSA 4.80	Windows: `%CSA_HOME%\_CSA_4_80_0_installation\Backup\standalone\idm-service.war\WEB-INF\spring\` Linux: `$CSA_HOME/_CSA_4_80_0_installation/Backup/standalone/idm-service.war/WEB-INF/spring/`

applicationContext-security.xml (Identity Management component)

Action

Caution Do NOT copy the backed up file over the new file. The file has changed in CSA 4.80 and the backed up file is different from the current version.

File Location in CSA 4.80

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

Linux: $CSA_HOME/jboss-as/standalone/deployments/idm-service.war/WEB-INF/spring/

Backed Up CSA 4.6x or 4.7x File Location in CSA 4.80

Windows: %CSA_HOME%\_CSA_4_80_0_installation\Backup\standalone\idm-service.war\WEB-INF\spring\

Linux: $CSA_HOME/_CSA_4_80_0_installation/Backup/standalone/idm-service.war/WEB-INF/spring/

applicationContext-v0.xml (Identity Management component)
Action	Required. This is a new file that requires customization. Refer to the Cloud Service Automation Configuration Guide for more information.
File Location in CSA 4.80	Windows: `%CSA_HOME%\jboss-as\standalone\deployments\idm-service.war\WEB-INF\spring\` Linux: `$CSA_HOME/jboss-as/standalone/deployments/idm-service.war/WEB-INF/spring/`
Backed Up CSA 4.6x or 4.7x File Location in CSA 4.80	N/A

applicationContext-v0.xml (Identity Management component)

Action

Required. This is a new file that requires customization. Refer to the Cloud Service Automation Configuration Guide for more information.

File Location in CSA 4.80

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

Linux: $CSA_HOME/jboss-as/standalone/deployments/idm-service.war/WEB-INF/spring/

Backed Up CSA 4.6x or 4.7x File Location in CSA 4.80 N/A

csa.properties

csa.properties
Action	User has to validate or add the following properties in `csa.properties`: `csaKeystore=C:/Program Files/HPE/CSA/jboss-as/standalone/configuration/.keystore` `csaKeystorePassword=ENC(oreBTzwQRoHyaKoELUqpHLOzganbIkQg)`
File Location in CSA 4.80	Windows: `%CSA_HOME%\jboss-as\standalone\deployments\csa.war\WEB-INF\classes\` Linux: `$CSA_HOME/jboss-as/standalone/deployments/csa.war/WEB-INF/classes/`
Backed Up CSA 4.6x or 4.7x File Location in CSA 4.80	Windows: `%CSA_HOME%\_CSA_4_80_0_installation\Backup\standalone\csa.war\WEB-INF\classes\` Linux: `$CSA_HOME/_CSA_4_80_0_installation/Backup/standalone/csa.war/WEB-INF/classes/`

Action

User has to validate or add the following properties in csa.properties:

csaKeystore=C:/Program Files/HPE/CSA/jboss-as/standalone/configuration/.keystore

csaKeystorePassword=ENC(oreBTzwQRoHyaKoELUqpHLOzganbIkQg)

File Location in CSA 4.80

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

Linux: $CSA_HOME/jboss-as/standalone/deployments/csa.war/WEB-INF/classes/

Backed Up CSA 4.6x or 4.7x File Location in CSA 4.80

Windows: %CSA_HOME%\_CSA_4_80_0_installation\Backup\standalone\csa.war\WEB-INF\classes\

Linux: $CSA_HOME/_CSA_4_80_0_installation/Backup/standalone/csa.war/WEB-INF/classes/

java.security

java.security
Action	Required. If `config.json` file is customized, you must re-customize this file. In case you do not remember the customizations made to the file, refer to the back up copy and compare it to the file installed with CSA 4.80. Note: Port property has to be verified to contain a custom port, if such a port is used (or you can use the property from the backup of the previous CSA installation).
File Location in CSA 4.80	Windows: `<csa_jre>\lib\security\` Linux: `<csa_jre>/lib/security/`
Backed Up CSA 4.6x or 4.7x File Location in CSA 4.80	This file is not backed up. You should have manually backed this file up prior to running the upgrade installer.

Action

Note: Port property has to be verified to contain a custom port, if such a port is used (or you can use the property from the backup of the previous CSA installation).

File Location in CSA 4.80

Windows: <csa_jre>\lib\security\

Linux: <csa_jre>/lib/security/

Backed Up CSA 4.6x or 4.7x File Location in CSA 4.80

This file is not backed up. You should have manually backed this file up prior to running the upgrade installer.

standalone.xml
Action	Required. If this file was customized, you must recustomize this file. The customization required for this file is different from the previous release. Refer to the Cloud Service Automation Configuration Guide for more information. Caution Do NOT copy the backed up file over the new file. The file has changed in CSA 4.80 and the backed up file is different from the current version.
File Location in CSA 4.80	Windows: `%CSA_HOME%\jboss-as\standalone\configuration\` Linux: `$CSA_HOME/jboss-as/standalone/configuration/`
Backed Up CSA 4.6x or 4.7x File Location in CSA 4.80	Windows: `%CSA_HOME%\_CSA_4_80_0_installation\Backup\standalone\configuration\` Linux: `$CSA_HOME/_CSA_4_80_0_installation/Backup/standalone/configuration/` Backup - Windows: `C:\csabackup\` Linux: `/tmp/csabackup/`

standalone.xml

Action

Caution Do NOT copy the backed up file over the new file. The file has changed in CSA 4.80 and the backed up file is different from the current version.

File Location in CSA 4.80

Windows: %CSA_HOME%\jboss-as\standalone\configuration\

Linux: $CSA_HOME/jboss-as/standalone/configuration/

Backed Up CSA 4.6x or 4.7x File Location in CSA 4.80

Windows: %CSA_HOME%\_CSA_4_80_0_installation\Backup\standalone\configuration\

Linux: $CSA_HOME/_CSA_4_80_0_installation/Backup/standalone/configuration/

Backup - Windows: C:\csabackup\ Linux: /tmp/csabackup/

Configure the Identity Management component

The following is a list of files that you may have customized for the Identity Management component and the actions required when you upgrade CSA:

File	Action
applicationContext.xml (Identity Management component)	Required. If this file was customized, you must recustomize this file (see table below for more information).
applicationContext.properties	No action required.
applicationContext-common.xml	No action required.

Files, Actions, and Locations

applicationContext.xml (Identity Management component)
Action	Required. If `config.json` file is customized, you must re-customize this file. In case you do not remember the customizations made to the file, refer to the back up copy and compare it to the file installed with CSA 4.80. Note: Port property has to be verified to contain a custom port, if such a port is used (or you can use the property from the backup of the previous CSA installation).
File Location in CSA 4.80	Windows: `%CSA_HOME%\jboss-as\standalone\deployments\idm-service.war\WEB-INF\spring\` Linux: `$CSA_HOME/jboss-as/standalone/deployments/idm-service.war/WEB-INF/spring/`
Backed Up CSA 4.6x or 4.7x File Location in CSA 4.80	Windows: `%CSA_HOME%\_CSA_4_80_0_installation\Backup\standalone\idm-service.war\WEB-INF\spring\` Linux: `$CSA_HOME/_CSA_4_80_0_installation/Backup/standalone/idm-service.war/WEB-INF/spring/`

applicationContext.xml (Identity Management component)

Action

Note: Port property has to be verified to contain a custom port, if such a port is used (or you can use the property from the backup of the previous CSA installation).

File Location in CSA 4.80

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

Linux: $CSA_HOME/jboss-as/standalone/deployments/idm-service.war/WEB-INF/spring/

Backed Up CSA 4.6x or 4.7x File Location in CSA 4.80

Windows: %CSA_HOME%\_CSA_4_80_0_installation\Backup\standalone\idm-service.war\WEB-INF\spring\

Linux: $CSA_HOME/_CSA_4_80_0_installation/Backup/standalone/idm-service.war/WEB-INF/spring/

applicationContext.properties

Action No action required. If this file was customized, the customizations have been merged with the upgraded file.

applicationContext.properties
Action	No action required. If this file was customized, the customizations have been merged with the upgraded file.
File Location in CSA 4.80	Windows: `%CSA_HOME%\jboss-as\standalone\deployments\idm-service.war\WEB-INF\spring\` Linux: `$CSA_HOME/jboss-as/standalone/deployments/idm-service.war/WEB-INF/spring/`
Backed Up CSA 4.6x or 4.7x File Location in CSA 4.80	Windows: `%CSA_HOME%\_CSA_4_80_0_installation\Backup\standalone\idm-service.war\WEB-INF\spring\` Linux: `$CSA_HOME/_CSA_4_80_0_installation/Backup/standalone/idm-service.war/WEB-INF/spring/`

File Location in CSA 4.80

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

Linux: $CSA_HOME/jboss-as/standalone/deployments/idm-service.war/WEB-INF/spring/

Backed Up CSA 4.6x or 4.7x File Location in CSA 4.80

Windows: %CSA_HOME%\_CSA_4_80_0_installation\Backup\standalone\idm-service.war\WEB-INF\spring\

Linux: $CSA_HOME/_CSA_4_80_0_installation/Backup/standalone/idm-service.war/WEB-INF/spring/

applicationContext-common.xml

applicationContext-common.xml
Action	No action required. If this file was customized, the customizations have been merged with the upgraded file.
File Location in CSA 4.80	Windows: `%CSA_HOME%\jboss-as\standalone\deployments\idm-service.war\WEB-INF\spring\` Linux: `$CSA_HOME/jboss-as/standalone/deployments/idm-service.war/WEB-INF/spring/`
Backed Up CSA 4.6x or 4.7x File Location in CSA 4.80	Windows: `%CSA_HOME%\_CSA_4_80_0_installation\Backup\standalone\idm-service.war\WEB-INF\spring\` Linux: `$CSA_HOME/_CSA_4_80_0_installation/Backup/standalone/idm-service.war/WEB-INF/spring/`

Action

No action required. If this file was customized, the customizations have been merged with the upgraded file.

File Location in CSA 4.80

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

Linux: $CSA_HOME/jboss-as/standalone/deployments/idm-service.war/WEB-INF/spring/

Backed Up CSA 4.6x or 4.7x File Location in CSA 4.80

Windows: %CSA_HOME%\_CSA_4_80_0_installation\Backup\standalone\idm-service.war\WEB-INF\spring\

Linux: $CSA_HOME/_CSA_4_80_0_installation/Backup/standalone/idm-service.war/WEB-INF/spring/

Configure IPv6

The following is the file that you may have customized if you configured IPv6 and the actions required when you upgrade CSA:

File	Action
standalone.xml	Required. If this file was customized, you must recustomize this file (see table below for more information).

File, Actions, and Locations

standalone.xml

Action

Caution Do NOT copy the backed up file over the new file. The file has changed in CSA 4.80 and the backed up file is different from the current version.

File Location in CSA 4.80

Windows: %CSA_HOME%\jboss-as\standalone\configuration\

Linux: $CSA_HOME/jboss-as/standalone/configuration/

Backed Up CSA 4.6x or 4.7x File Location in CSA 4.80

Windows: %CSA_HOME%\_CSA_4_80_0_installation\Backup\standalone\configuration\

Linux: $CSA_HOME/_CSA_4_80_0_installation/Backup/standalone/configuration/

Backup - Windows: C:\csabackup\ Linux: /tmp/csabackup/

Configure the JBoss Password Vault

The following is the file that you may have customized if you configured the JBoss password vault and the actions required when you upgrade CSA:

File	Action
Windows:vault.batLinux:vault.sh	Required. If this file was customized, you must recustomize this file (see table below for more information.

File, Actions, and Locations

Windows:vault.batLinux:vault.sh

Action

Caution Do NOT copy the backed up file over the new file. The file has changed in CSA 4.80.

File Location in CSA 4.80

Windows: %CSA_HOME%\jboss-as\bin\

Linux: $CSA_HOME/jboss-as/bin/

Backed Up CSA 4.6x or 4.7x File Location in CSA 4.80

Windows: %CSA_HOME%\_CSA_4_80_0_installation\Backup\standalone\

Linux: $CSA_HOME/_CSA_4_80_0_installation/Backup/standalone/

Configure Oracle RAC

The following is the file that you may have customized if you configured Oracle RAC and the actions required when you upgrade CSA:

File	Action
standalone.xml	Required. If this file was customized, you must recustomize this file (see table below for more information).

File, Actions, and Locations

standalone.xml

Action

Caution Do NOT copy the backed up file over the new file. The file has changed in CSA 4.80 and the backed up file is different from the current version.

File Location in CSA 4.80

Windows: %CSA_HOME%\jboss-as\standalone\configuration\

Linux: $CSA_HOME/jboss-as/standalone/configuration/

Backed Up CSA 4.6x or 4.7x File Location in CSA 4.80

Windows: %CSA_HOME%\_CSA_4_80_0_installation\Backup\standalone\configuration\

Linux: $CSA_HOME/_CSA_4_80_0_installation/Backup/standalone/configuration/

Backup - Windows: C:\csabackup\ Linux: /tmp/csabackup/

Configure CSA to Use a Single Sign-On

The following is a list of files that you customized when configuring CSA to use a single sign-on (SSO) and the actions required when you upgrade CSA:

File	Action
applicationContext.xml	Required. If this file was customized, you must recustomize this file (see table below for more information).
applicationContext-security.xml	Required. If this file was customized, you must recustomize this file (see table below for more information).
hpssoConfiguration.xml	Required. If this file was customized, you must recustomize this file (see table below for more information).
main.css (default)	Required. If this file was customized, you must recustomize this file (see table below for more information).
main.css (pilot)	Required. If this file was customized, you must recustomize this file (see table below for more information).
main.css (custom theme)	Required. If this file was customized, you must recustomize this file (see table below for more information).
rb.json	Required. If this file was customized, you must recustomize this file (see table below for more information).

Files, Actions, and Locations

applicationContext.xml

Action

Note: Port property has to be verified to contain a custom port, if such a port is used (or you can use the property from the backup of the previous CSA installation).

File Location in CSA 4.80

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

Linux: $CSA_HOME/jboss-as/standalone/deployments/csa.war/WEB-INF/

Backed Up CSA 4.6x or 4.7x File Location in CSA 4.80

Windows: %CSA_HOME%\_CSA_4_80_0_installation\Backup\standalone\csa.war\WEB-INF\

Linux: $CSA_HOME/_CSA_4_80_0_installation/Backup/standalone/csa.war/WEB-INF/

applicationContext-security.xml

Action

Note: Port property has to be verified to contain a custom port, if such a port is used (or you can use the property from the backup of the previous CSA installation).

File Location in CSA 4.80

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

Linux: $CSA_HOME/jboss-as/standalone/deployments/csa.war/WEB-INF/

Backed Up CSA 4.6x or 4.7x File Location in CSA 4.80

Windows: %CSA_HOME%\_CSA_4_80_0_installation\Backup\standalone\csa.war\WEB-INF\

Linux: $CSA_HOME/_CSA_4_80_0_installation/Backup/standalone/csa.war/WEB-INF/

hpssoConfiguration.xml

Action

Note: Port property has to be verified to contain a custom port, if such a port is used (or you can use the property from the backup of the previous CSA installation).

File Location in CSA 4.80

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

Backed Up CSA 4.6x or 4.7x File Location in CSA 4.80

%CSA_HOME%\_CSA_4_80_0_installation\Backup\standalone\csa.war\WEB-INF\

main.css (<theme_directory>)

Action

Note: Port property has to be verified to contain a custom port, if such a port is used (or you can use the property from the backup of the previous CSA installation).

File Location in CSA 4.80

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

Linux: $CSA_HOME/portal/node_modules/mpp-ui/dist/themes/<theme_directory>/styles/

Backed Up CSA 4.6x or 4.7x File Location in CSA 4.80

Windows: %CSA_HOME%\_CSA_4_80_0_installation\Backup\portal\node_modules\mpp-ui\themes\<theme_directory>\styles\

Linux: $CSA_HOME/_CSA_4_80_0_installation/Backup/portal/node_modules/mpp-ui/dist/themes/<theme_directory>/styles/

rb.json

Action

Note: Port property has to be verified to contain a custom port, if such a port is used (or you can use the property from the backup of the previous CSA installation).

File Location in CSA 4.80

Windows: %CSA_HOME%\portal\node_modules\mpp-ui\dist\locales\<locale>\

Linux: $CSA_HOME/portal/node_modules/mpp-ui/dist/locales/<locale>/

Backed Up CSA 4.6x or 4.7x File Location in CSA 4.80

Windows: %CSA_HOME%\_CSA_4_80_0_installation\Backup\portal\node_modules\mpp-ui\dist\locales\<locale>\

Linux: $CSA_HOME/_CSA_4_80_0_installation/Backup/portal/node_modules/mpp-ui/dist/locales/<locale>/

Delete the Sample Consumer Organization

If you deleted the sample consumer organization on your CSA 4.6x or 4.7x system, you should delete the sample consumer organization (if it still exists) if you are no longer using it, if you are moving the application to production, or if you are upgrading a production system. See the Cloud Service Automation Configuration Guide for more information if you are deleting this organization for the first time.

Upgrade Shortcuts

If you created CSA shortcuts in the default directory (for example, C:\Users\<user>\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Hewlett-Packard\Cloud Service Automation), these shortcuts are automatically upgraded. If you created CSA shortcuts and saved them to another directory other than the default directory (for example, in a Program Group, in the Start Menu, on the desktop, or in the Quick Launch Bar), you should delete these shortcuts as they will no longer work. Optionally, you can change the target of the shortcuts to %CSA_HOME%\_CSA_4_80_0_installation\Change HPE Cloud Service Automation Installation.exe.

Marketplace Portal Configuration

If you customized the Marketplace Portal configuration file, the customizations will be merged with the upgrade file. Refer to the Cloud Service Automation Configuration Guide for more information about the configurable properties in this file.

File	Action
mpp.json	No action required. If this file was customized, the customizations have been merged with the upgraded file.
index.html	No action required. If this file was customized, the customizations have been restored.

Files, Actions, and Locations

mpp.json

Action

No action required. If this file was customized, the customizations have been merged with the upgraded file.

File Location in CSA 4.80

Windows: %CSA_HOME%\portal\conf\

Linux: $CSA_HOME/portal/conf/

Backed Up CSA 4.6x or 4.7x File Location in CSA 4.80

Windows: %CSA_HOME%\_CSA_4_80_0_installation\Backup\portal\conf\

Linux: $CSA_HOME/_CSA_4_80_0_installation/Backup/portal/conf/

index.html

Action No action required. If this file was customized, the customizations have been restored.

File Location in CSA 4.80

Windows: %CSA_HOME%\jboss-as\standalone\deployments\mpp.war\

Linux: $CSA_HOME/jboss-as/standalone/deployments/mpp.war/

Backed Up CSA 4.6x or 4.7x File Location in CSA 4.80

Windows: %CSA_HOME%\_CSA_4_80_0_installation\Backup\standalone\mpp.war\

Linux: $CSA_HOME/_CSA_4_80_0_installation/Backup/standalone/mpp.war/

Send Help Center feedback