Reducing the CPU usage of JQM servers in SAP environment

2 Technical Note
Reducing the CPU usage of JQM servers in an SAP environment
Solution
List of default indexed attributes in the JQM server database
-job-identifier
-job-name
-job-owner
-destination
-current-job-state
-queue-assigned
-job-completion-status
-physical-printer-assigned
-job-retention-time
Re-indexing the JQM server jobs table
The following example describes the steps needed to re-index a jobs table of the JQM server and assumes that the
-erp-job-retention-period attribute is the identified attribute to be indexed and the JQM server is named
jqm1.
NOTE: HP recommends that you backup your MySQL installation before re-indexing the
attributes.
To re-index the jobs table of the JQM server, perform the tasks given below:
Task 1: Modify the DPAOIDs file.
1. Create a backup for the DPAOIDs file.
2. Locate the DPAOIDs file installed on your system.
For a Windows operating system, the file is at:
$DAZEL_HOME/bin
For a UNIX operating system, the file is at:
$DAZEL_HOME/nls/oid/$LANG
3. Use a text editor to edit the file. The text file should be greater than 80 columns wide.
4. Find the attribute to be indexed (-erp-job-retention-period in this example) and locate the fourth
column. This column might contain numerics or just a dash (-.)
Example
The -erp-job-retention-period attribute is displayed as:
erp-job-retention-period ..1.0.10175.1.0.0.3.1.230 TBSJ - pm3 DeltaTime 001
Here, the fourth column (-) contains a dash, which indicates that this attribute is currently not indexed for any
server. The server for which the attribute will be indexed is designated by one of the following values:
Server Name Value
CM 1
DLM 2
JQM 3
DSM 4