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)`

Codar1.80

Upgrade > Update Codar > Customize SSL/Security

Customize SSL/Security

If you generated or copied SSL certificates that are used by Codar, you must copy these files to the appropriate directory in Codar 1.80.

The following is a list of files that you may have customized for SSL/security and the actions required when you upgrade Codar.

File	Action
certificate files	Required. Manually copy certificate files that do not use the .cer extension that are used by Codar from the backup directory to the Codar 1.80 directory (see the table below for more information).
`.cacerts`	Required. Because the JRE has been upgraded, you should not re-use the truststore from the old version of the JRE (it may contain public Certificate Authority certificates that are no longer trusted). Instead, you must export any root and/or self-signed certificates from the old truststore (certificates that you had manually imported into the old truststore) and import them into the new JRE truststore. You should have backed up the old version of the truststore prior to running the upgrade installer (see Initial setup).
Keystore file defined by the `certificate-key-file` property of the connector attribute in `standalone.xml`	Required (if not using the default keystore file). Manually copy the custom keystore file back from the location outside of the `CSA_HOME` installation directory where you manually backed it up.
`standalone.xml`	No action required.

Files, actions, and locations

certificate files
Action	Required. Manually copy certificate files that do not use the .cer extension that are used by Codar from the backup directory to the Codar 1.80 directory. Files that use the .cer extension are automatically restored. If you saved .cer files in a different directory, you must manually copy these files back after upgrade.
File location in Codar 1.80	`CSA_HOME\jboss-as\standalone\configuration\`
Backed up Codar 1.50 or 1.60 file location in Codar 1.80	`CSA_HOME\_Codar_1_70_0_installation\Backup\security\`

cacerts

Action Required. Because the JRE has been upgraded, you should not re-use the truststore from the old version of the JRE (it may contain public Certificate Authority certificates that are no longer trusted). Instead, you must export any root and/or self-signed certificates from the old truststore (certificates that you had manually imported into the old truststore) and import them into the new JRE truststore. You should have backed up the old version of the truststore prior to running the upgrade installer (see Initial setup).

cacerts
Action	Required. Because the JRE has been upgraded, you should not re-use the truststore from the old version of the JRE (it may contain public Certificate Authority certificates that are no longer trusted). Instead, you must export any root and/or self-signed certificates from the old truststore (certificates that you had manually imported into the old truststore) and import them into the new JRE truststore. You should have backed up the old version of the truststore prior to running the upgrade installer (see Initial setup).
File location in Codar 1.80	`CSA_HOME\openjre\lib\security\` where `CSA_HOME\openjre` is the directory in which the JRE (used exclusively by Codar) is installed.
Backed up Codar 1.50 or 1.60 file location in Codar 1.80	This file is not backed up.

File location in Codar 1.80

CSA_HOME\openjre\lib\security\

where CSA_HOME\openjre is the directory in which the JRE (used exclusively by Codar) is installed.

Backed up Codar 1.50 or 1.60 file location in Codar 1.80 This file is not backed up.

Keystore file defined by the `certificate-key-file` property of the connector attribute in `standalone.xml`
Action	Required (if not using the default keystore file). Manually copy the keystore file back from the location outside of the `CSA_HOME` installation directory where you manually backed it up. If you are using the default keystore file, no action is required (the default keystore file is automatically backed up and restored). Windows default keystore file: `C:\Program Files\Hewlett-Packard\Codar\jboss-as\standalone\configuration\.keystore` Linux default keystore file: `ult value: /usr/local/hpe/codar/jboss-as/standalone/configuration/.keystore`
File location in Codar 1.80	The file and its location are determined by the value defined by the `certificate-key-file`. Windows default value: `C:\Program Files\HPE\Codar\jbos-as\standalone\configuration\.keystore` Linux default value: `/usr/local/hpe/codar/jboss-as/standalone/configuration/.keystore`
Backed up Codar 1.50 or 1.60 file location in Codar 1.80	If you are using a custom keystore file, this file is not backed up. The default keystore file is backed up to `CSA_HOME\_Codar_1_70_0_installation\Backup\security\keystores\`

Keystore file defined by the certificate-key-file property of the connector attribute in standalone.xml

Action

Required (if not using the default keystore file). Manually copy the keystore file back from the location outside of the CSA_HOME installation directory where you manually backed it up. If you are using the default keystore file, no action is required (the default keystore file is automatically backed up and restored).

Windows default keystore file:
C:\Program Files\Hewlett-Packard\Codar\jboss-as\standalone\configuration\.keystore
Linux default keystore file:
ult value: /usr/local/hpe/codar/jboss-as/standalone/configuration/.keystore

File location in Codar 1.80

The file and its location are determined by the value defined by the certificate-key-file.

Windows default value:
C:\Program Files\HPE\Codar\jbos-as\standalone\configuration\.keystore
Linux default value:
/usr/local/hpe/codar/jboss-as/standalone/configuration/.keystore

Backed up Codar 1.50 or 1.60 file location in Codar 1.80

If you are using a custom keystore file, this file is not backed up.

The default keystore file is backed up to
CSA_HOME\_Codar_1_70_0_installation\Backup\security\keystores\

`standalone.xml`
Action	No action required. If this file was customized, the customizations have been merged with the upgraded file.
File location in Codar 1.80	`CSA_HOME\jboss-as\standalone\configuration\`
Backed up Codar 1.50 or 1.60 file location in Codar 1.80	`CSA_HOME\_Codar_1_70_0_installation\standalone\configuration\`

Send Help Center feedback