P6 EPPM Job Service Test

The Job Service process run as standalone for better performance and scalability. The Job Service can either run on the same server or a separate server or cluster. The Job Service is responsible for executing scheduled and real time application Jobs. Some of the key jobs processed by Job Service are Summarizer, scheduler, leveler, publications, updating baselines, adding/creating baselines, export-import project etc.

The Job service is capable of processing large number of projects, activities and resource assignments. The number of concurrent jobs affect the CPU and memory requirement of the Job Server and the load on database server. That's the reason it is important for administrators to be aware of job status, and server performance while the jobs are running. With these insights administrators can take necessary action to manage the jobs and increase server capacity if required.

This test monitors the Job Server to measusre key paramaters like memory utilization, number of jobs executing etc. to understand the performance of job execution and load on the server.

Target of the test : An Oracle Primavera P6 EPPM Server

Agent deploying the test : An internal/external agent

Outputs of the test : One set of results for P6 EPPM Server

Configurable parameters for the test
Parameter Description

Test period

How often should the test be executed.


The host for which the test is to be configured.


The port number at which the specified host listens. By default, this is NULL.

JMX Remote Port

Specify the port at which the JMX listens for requests from remote hosts. Ensure that you specify the same port that you configured in the management.properties file in the <JAVA_HOME>\jre\lib\management folder used by the target application Java Applications chapter.

JMX UserName and JMX Password

If JMX requires authentication only (but no security), then ensure that the User and Password parameters are configured with the credentials of a user with read-write access to JMX. To know how to create this user, refer to the Java Applications chapter. Confirm the password by retyping it in the Confirm Password text box

Confirm Password

Confirm the password by retyping it here.

DD Frequency

Refers to the frequency with which detailed diagnosis measures are to be generated for this test. The default is 1:1. This indicates that, by default, detailed measures will be generated every time this test runs, and also every time the test detects a problem. You can modify this frequency, if you so desire. Also, if you intend to disable the detailed diagnosis capability for this test, you can do so by specifying none against DD frequency.

Detailed Diagnosis

To make diagnosis more efficient and accurate, the eG Enterprise embeds an optional detailed diagnostic capability. With this capability, the eG agents can be configured to run detailed, more elaborate tests as and when specific problems are detected. To enable the detailed diagnosis capability of this test for a particular server, choose the On option. To disable the capability, click on the Off option.

The option to selectively enable/disable the detailed diagnosis capability will be available only if the following conditions are fulfilled:

  • The eG manager license should allow the detailed diagnosis capability
  • Both the normal and abnormal frequencies configured for the detailed diagnosis measures should not be 0
Measurements made by the test
Measurement Description Measurement Unit Interpretation

Used memory

Indicates the amount of memory that is being used by Job Service.


If the memory usage is really high over multiple measurements, it could eventually lead to memory full resulting in Job Failure.

Max memory

Indicates the maximum memory available on the server for Job Service.


If memory usage is repeatedly reaching max memory, the administrator may need to kill some jobs to relieve the load on the system.

Jobs running this server

Indicates the number of jobs running on the server.


You can check if some jobs are running for too long, they may be in stalled state, and may need to be killed to make resources available for waiting jobs to execute


Jobs pending system wide

Indicates the number of jobs pending for Job Service thread


Job executions

Indicates the number of times a job has executed successfully.


If the job has executed successfully a few times before, the probability of it running successfully will be high.

Jobs executed in last hour

Indicates the number of jobs finished in last hour.


Signifies the rate at which jobs are executing. If the number is too low, the jobs may need to be broken down.

Jobs failed in last hour

Indicates the number of jobs failed in last hour.


If there are too many job failures, there may be an issues in system performance.


Percentage of jobs failed in last hour

Indicates the percentage of jobs failing in last hour against total number of jobs started.


Average execution time

Indicates the average time taken by a job to complete.


You should look for trend in this data. If the average job execution time is increasing over a range of measurements, it might be an indicator of deteriorating performance of the server.