Searching the Help
To search for information in the Help, type a word or phrase in the Search box. When you enter a group of words, OR is inferred. You can use Boolean operators to refine your search.
Results returned are case insensitive. However, results ranking takes case into account and assigns higher scores to case matches. Therefore, a search for "cats" followed by a search for "Cats" would return the same number of Help topics, but the order in which the topics are listed would be different.
Words and Phrases
| 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. |
Using Boolean Operators
| Search for | Operator | Example |
|---|---|---|
|
Two or more words in the same topic |
|
|
| Either word in a topic |
|
|
| Topics that do not contain a specific word or phrase |
|
|
| Topics that contain one string and do not contain another | ^ (caret) |
cat ^ mouse
|
| A combination of search types | ( ) parentheses |
|
- Customize Codar
- Configure Codar Console properties
- Customize Codar Console dashboard
- Configure Codar Console to import large archives
- Customize Codar Console session timeout
- Customize Codar Console dashboard title
- Add custom graphic files or dynamic query scripts
- Customize Codar tools
- Customize Codar database user
- Customize Codar seeded users
- Integrate Codar with a common access card
- Configure Identity Management component
- Configure IPv6
- Configure JBoss password vault
- Configure Oracle RAC
- Configure Codar to use a single sign-on
- Integrate Codar with SiteMinder
- Upgrade shortcuts on Windows
Customize Codar tools
The following is a list of files that you may have customized if you ran any of the Codar tools and the actions required when you upgrade Codar:
| File | Action |
|---|---|
config.properties (content archive tool, purge tool, provider configuration tool) |
Required. Manually copy any custom configuration files from the backup directory to the Codar 1.80 directory (see the table below for more information). |
|
|
Required. Manually copy any custom configuration files from the backup directory to theCodar 1.80 directory (see the table below for more information). |
|
|
Required. Manually copy any custom input files from the backup directory to the Codar 1.80 directory (see the table below for more information). |
provider.xml (provider configuration tool) |
Required. Manually copy any custom input files from the backup directory to the Codar 1.80 directory (see the table below for more information). |
Files, actions, and locations
| config.properties | |
|---|---|
| Action | Required. Manually copy any custom configuration files from the backup directory to the Codar1.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 Codar 1.80 | |
| Backed up Codar 1.50 or 1.60 file location in Codar 1.80 | |
| db.properties | |
|---|---|
| Action | Required. Manually copy any custom configuration files from the backup directory to the Codar1.80 directory. This is the generic name of the configuration file used in some examples for the process definition tool and schema installation tool. If you used a different name for the configuration file, copy that file instead. |
| File location in Codar 1.80 | CSA_HOME\Tools\ProcessDefinitionTool\ CSA_HOME\Tools\SchemaInstallationTool\ |
| Backed up Codar 1.50 or 1.60 file location in Codar 1.80 | |
| HPOOInfoInput.xml | |
|---|---|
| Action | Required. Manually copy any custom input files from the backup directory to the Codar1.80 directory. This is the generic name of the input file used in some examples for the process definition tool. If you used a different name for the input file, copy that file instead. |
| File location in Codar 1.80 | |
| Backed up Codar 1.50 or 1.60 file location in Codar 1.80 | |
| provider.xml | |
|---|---|
| Action | Required. Manually copy any custom provider input files from the backup directory to the Codar1.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 Codar 1.80 | |
| Backed up Codar 1.50 or 1.60 file location in Codar 1.80 | |
We welcome your comments!
To open the configured email client on this computer, open an email window.
Otherwise, copy the information below to a web mail client, and send this email to clouddocs@hpe.com.
Help Topic ID:
Product:
Topic Title:
Feedback: