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.
![Closed](../../../Skins/Default/Stylesheets/Images/transparent.gif)
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. |
![Closed](../../../Skins/Default/Stylesheets/Images/transparent.gif)
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 |
|
- Configure HTML Email Notifications
- Configure the Notification Properties
- Configure the Default Notification Templates
- HTML Notification for Pause on Failure
- Customize the Default Notification Templates
- Unsupported HTML Notification Functionality
- Configure HTML Notification for Pause on Failure
- HTML Template Configuration/Troubleshooting Notes
HTML Template Configuration/Troubleshooting Notes
- Be sure the HTML template file names are correct. The names must be the same as the default HTML template file names, with the exception of the design-specific email templates, which also follow a specific naming convention. Only the contents of the HTML files can be changed.
-
The name of the directory under
csa.war/WEB-INF/classes/notifications
must be the same as the Organization Identifier, and not the Organization Display Name. - Two or more versions of a service design will use the same template if a design-specific template is defined. If the components differ widely across these versions, it is not possible to create different design-specific templates for each version.
- The notification tokens are case-sensitive. For example:
${INFRASTRUCTURE_SERVICE-SERVER_GROUP.serverCount}
is not the same as${infrastructure_service-Server_group.serverCount}
. -
If tokens are seen as-is in email notifications, check to see if the tokens are entered correctly. Verify that the components containing these properties, and the properties, are visible. Properties with encrypted data cannot be accessed.
-
Only visible components and visible properties will be available.
-
The parent component need not be visible. So if the parent component is hidden, but the child component is visible, then all placeholder tokens corresponding to their visible properties of the child component will be resolved.
-
However, if the parent component is visible, but the child component is hidden, then the property values of the child component cannot be accessed using placeholder tokens.
-
- The tokens must be entered exactly as shown in the
HTML Template Configuration/Troubleshooting Notes section. If the token is entered incorrectly, the email notification will show the token name rather than the name that the token represents. For example, if you use
Subscriber.name
instead ofsubscriber.name
, the email content will show Subscriber.name instead of the person's name. -
Be sure that the following characters are not used in the names of custom components:
$ { [ ( . ) ] } and whitespace
If CSA finds these characters in the name of the components, then they will be removed. For example, if a component name is
SERVER{TEST COMPONENT.NAME}
, then CSA will use the name SERVERTESTCOMPONENTNAME. -
To debug any possible issues in collecting data required for HTML notifications, enable debug logging for the following in
log4j2.xml
. This file can be found undercsa.war/WEB-INF/classes
:com.hp.csa.service.notification.NotificationMailServiceImpl
com.hp.csa.service.notification.templates
Debug log entries will be seen in the
csa.log
file.
Note For Clustered CSA nodes, email templates, hcm-csa.yaml
and log4j2.xml
must be identical across all nodes so that the behavior is consistent in a cluster. The HTML templates and any modifications to the templates must be applied to each CSA node in the cluster.
Legacy text notifications will be sent under these conditions:
- If there is an error while creating emails in HTML. Look up
csa.log
and correct any parsing issues. -
If notifications are sent for Service Instance Upgrade and Transfer Subscription.
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: