Writer instructions | |
---|---|
Page title | For most spaces, this page must be titled Space announcements. For spaces with localized content, this page must be titled Space announcements l10n. |
Purpose | Provide an announcement banner on every page of your space. |
Location | Move this page outside of your home branch. |
Guidelines |
Services log files
All of the Services use rotating log files saved in the installation directory. The file names are based on the service's short name (for example, the MVMMTopic Service is qpts; and the log file is qpts.log) and are stored in the same directory as the executable. The newest log file is .log with each subsequent log file appending a number. The larger the number, the older the log file. For instance, the MVMMTopic Service log files are:
- qpts.log
- qpts.log.1
- qpts.log.2.
The MVMMApplication Service has several different log files. They all start with qpas-*.log.
For example:
- qpas-apacheds.log
- qpas-axis.log
- qpas-certs.log
- qpas-report.log
- qpas-rpes.log
- qpas-sched.log
- qpas-slide.log
- qpas-sws.log
- qpas-tunnel.log
- qpas-webmc.log
- qpas-wrapper.log
The MVMMClient Gateway Service log file is called qpcgateway_1.log and is located in the application install directory, or the system environment variable directory if it is configured. Typically, you should not adjust any log settings without first contacting BMC Support.
To modify a service's log level
- Open a text editor and create a file named qplog.ini. On Linux systems the file name is case sensitive.
- Copy the new file to the TrueSight Middleware and Transaction Monitor installation directory.
- Add the information shown in the following sample:
Sample qplog.ini
[Settings]
OutputJavaFilenames=false
OutputXML=false
[Categories]
#com.mqsoftware=default
com.mqsoftware=full - To turn off full logging, move the # from the com.mqsoftware=default line to the com.mqsoftware=full line.