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.
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 |
|
|
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 |
|
- System Configuration Parameters
- System parameters
- Web tier parameters
- Enter a parameter in the web client URL
- Enter a parameter in the sm.ini file
- Enter a parameter in the web.xml file
- Enter a parameter in the server’s operating system command prompt
- View parameters by function
- Alert parameters
- Application development parameters
- Background and scheduled process parameters
- Client parameters for Web clients
- Client parameters for Windows clients
- Connection parameters
- Database parameters
- Debugging parameters
- Information retrieval (IR) expert parameters
- LDAP parameters
- Localization parameters
- Regional settings parameters
- Security parameters
- Servlet parameters
- SSL parameters
- System information parameters
- Startup parameter: appversion
- Parameter: certExpireWarningDays
- Startup parameter: clean
- Parameter: corepath
- Parameter: enablecoredump
- Parameter: log4jdebug
- Parameter: reportlbstatus
- Parameter: licensefile
- Startup parameter: clustername
- Startup parameter: log
- Startup parameter: logappend
- Startup parameter: maxlogsize
- Startup parameter: logqueuesize
- Special parameters: maxreportpages
- Startup parameter: msg_buffer_size
- Special parameters: msgid
- Special parameters: msglog
- Special parameters: reportcache
- Special parameters: reportdiagnostics
- Special parameters: reportipc
- Special parameters: reportlanguages
- Special parameters: reportlic
- Special parameters: reportlocks
- Special parameters: reportsem
- Special parameters: reportshm
- Special parameters: reportstatus
- Special parameters: reporttolog
- Parameter: usedmemcompmode
- Startup parameter: version
- Parameter: reportLBInterval
- System performance parameters
System information parameters
These parameters display information about the server.
Startup parameter | Description |
---|---|
Startup parameter: appversion | Displays the version information for the Service Manager server |
Parameter: certExpireWarningDays | Specifies the number of days before the user’s certificate expires when Service Managerstarts to issue a warning message at user login |
Startup parameter: clean | Enables the Service Manager Reports functionality to exclude a message from email notifications about exported dashboards and reports. |
Startup parameter: clustername | Specifies a Microsoft cluster for failover and replaces the subnetaddress and host name with the clustername value |
Parameter: corepath | Defines the path to the core file that is generated by a system crash |
Parameter: enablecoredump | Enables Service Manager to log any information generated by a system crash |
Parameter: licensefile | Defines the path to the Autopass license file that contains the list of enabled modules and features for your Service Manager server |
Startup parameter: log | Defines the path to the Service Manager log file |
Parameter: log4jdebug | Enables certain java packages to be started in debug mode |
Startup parameter: logappend | Causes Service Manager to add log messages to the existing log file |
Parameter: logqueuesize | Controls the size of the log queue, specified by the number of messages |
Startup parameter: maxlogsize | Defines the maximum size to which a log file can grow before Service Manager rotates to a new log file |
Special parameters: maxreportpages | Defines the maximum number of pages that users can print from server-side printers |
Startup parameter: msg_buffer_size |
Defines the size (bytes) of the message buffer that is used to store the current notification message inside the Service Manager server, which is displayed in the Messages view of the client |
Special parameters: msgid | Forces the Service Manager server to display the message ID with all messages |
Special parameters: msglog | Defines the maximum number of messages the Service Manager server displays in the log file |
Special parameters: reportcache | Displays basic Service Manager CACHE statistics to the command line, which you can capture in a text file by using standard output (stdout) parameters appropriate to your operating system |
Special parameters: reportdiagnostics |
Displays the counter diagnostics report, which contains information about web services transaction count, session login/logout count, database client transmission count, heartbeat interval - request response count, event-in / event-out count, and email-in / email-out count Note By default, the Diagnostic Service is disabled. Before running the reportdiagnostics command, administrators must specify debugdiagnostics:1 to enable the Diagnostic Service. |
Special parameters: reportipc | Displays a diagnostic report of semaphore use, which you can capture in a text file by using standard output (stdout) parameters appropriate to your operating system |
Parameter: reportlbstatus | Displays information about available ports and threads in horizontal and vertical scaling servlet implementations |
Parameter: reportLBInterval | Periodically and automatically logs information (every n seconds) about available ports and threads in horizontal and vertical scaling servlet implementations |
Special parameters: reportlanguages |
Lists all the code pages that Service Manager supports Note Only those code pages that start with "mswin" are used in the context of SQL Server |
Special parameters: reportlic | Displays the Service Manager License Report, which you can capture in a text file by using standard output (stdout) parameters appropriate to your operating system |
Special parameters: reportlocks | Displays resource locks, which you can capture in a text file by using standard output (stdout) parameters appropriate to your operating system. |
Special parameters: reportsem | Displays the semaphore report, which you can capture in a text file by using standard output (stdout) parameters appropriate to your operating system. |
Special parameters: reportshm | Displays the shared memory report, which you can capture in a text file using standard output (stdout) parameters appropriate to your operating system. |
Special parameters: reportstatus | Displays a shared memory, semaphore and process report, which you can capture in a text file using standard output (stdout) parameters appropriate to your operating system. |
Special parameters: reporttolog | Allows the reportstatus , reportsem , and reportshm reports to be written to the console or to the sm.log file. |
Determines the method that is used to calculate memory usage | |
Startup parameter: version | Causes the Service Manager server to display version information |
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 ovdoc-ITSM@hp.com.
Help Topic ID:
Product:
Topic Title:
Feedback: