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 |
|
FIPS mode log messages
Service Manager writes FIPS mode related messages in the Server log and client log files.
Messages in the SM Server log
When FIPS mode is enabled on the Server side, the clients (Windows, Web Tier, Mobility, SRC, and Web Services) can connect to the Server through https (either FIPS validated TLS or normal TLS); however, the recommended best security practice is to run all of them in FIPS mode as well.
When FIPS mode is successfully enabled on the Server side, the following messages appear in the Server log (Server\logs\sm.log):
FIPS mode is set successfully.
FIPS provider was initialized successfully.
Additionally, when FIPS mode is enabled on the Server side and the Windows Client is running in non-FIPS mode, the following warning message appears in the Server log:
Your Client is running in non-FIPS mode, but the Service Manager Server is running in FIPS mode. For the highest security, we recommend you enable FIPS mode for the Client.
Note This message will also appear in the Windows Client user interface.
Messages in SM client logs
When FIPS mode is enabled successfully on the client sides, messages are written to the client logs. See the following table.
| Client | Example messages | Log file |
|---|---|---|
| Web Tier |
Examples: 2016-03-12 12:35:03,830 INFO [localhost-startStop-1] [com.hp.ov.sm.client.common.util.JCEProviderHelper] JCE Provider has registered in java.security:JsafeJCE 2016-03-12 12:35:03,830 INFO [localhost-startStop-1] [com.hp.ov.sm.client.common.util.JCEProviderHelper] Fips mode enabled. |
The sm.log file in the web application server installation directory. For example, <Tomcat>\bin\sm.log. |
| Mobility Client |
Examples: [localhost-startStop-1] (12/03/2016 12:30:39,906) [INFO ] client.util.JCEProviderHelper - JCE Provider has registered in java.security:JsafeJCE [localhost-startStop-1] (12/03/2016 12:30:39,906) [INFO ] client.util.JCEProviderHelper - Fips mode enabled. |
The mobility.log file in the web application server installation directory. For example, <Tomcat>\bin\mobility.log. |
| SRC | SunJSSE initialized in FIPS Mode. | The server.log file in Tomcat: <Tomcat>\logs \server.log |
Related topics
