P6 EPPM Users Test

The Oracle Primavera allow for a wide variety of user roles, each one with specific privileges and activity levels. The central Primavera server or cluster responds to the requests to all logged in users. The number of users logged and kind of activity performed by them directly affects the overall system performance. It is important for the administrators to know, at any given time, what is the number of logged in concurrent users, what is the activity level of user which is reflected by user role, and what is the method through which users are logged on, e.g. whether the users are logged on through Power client, API or web interface.

This test measures the number of various different kind of users logged and provides administrators with valuable insights about current and future performance issues. On the basis of these statistics administrators can plan adding more capacity to Primavera cluster if usage is high.

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.
Host	The host for which the test is to be configured.
Port	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
Logged in users	Indicates the total number of logged in users on P6 EPPM server.	Number	The number of logged in concurrent users directly affect the performance of the server. Administrators should monitor this measure for extended period to understand the user login trends and plan the server capacity accordingly.
Unique total login users	This is the total historic count of unique P6 EPPM users that have logged into the system. This count will never exceed the total number of users in the user dictionary.	Number	This is the maximum number of users that can login in the system that can system.
P6 analytics users	Indicates the number of analytics users session which are currently active.	Number	Analytics users tend to consume most compute resources. In case the number of analytics resources are high at any given point of time, administrators needs to plan system capacity accordingly.
API users	Indicates the number of users who are connected through P6 EPPM API.	Number	API users can perform mix activity
Web services users	Indicates the number of users who are accessing through P6 EPPM Web Services.	Number
Power client users	Indicates the number of users who are connected through Power Client.	Number	Power client allows enhanced functionality and allows users to carry out heavy operations like project setup, changing the structure, loading date etc. High number of active power client users can degrade the performance of the system.
Resources users	Indicates the number of users who have access to EPPM Resource Access field.	Number
Timesheet users	Indicates the number of users who have access to timesheet tab in P6 Team Member web.	Number	Timesheet users are mostly view only users who look for timeshet reports, administrators can expect a lot of database queries running if number of timesheet users is high.
Projects users	Indicates the number of users who have access to Projects section in P6 EPPM.	Number
Portfolio users	Indicates the number of users who have access to Portfolio section in P6 EPPM.	Number
Enterprise reports users	Indicates the number of logged in users who have access to run Enterprise reports.	Number	Running enterprise reports can be a heavy operation and if the users are running the reports in real time, it could really put a lot of load on the system. Ideally very few users should have access to run enterprise reports.
Team member users	Indicates the number of logged in users who have access to P6 EPPM Team Members module.	Number
Team member interface users	Indicates the number of logged in users who have access to P6 EPPM Team Members Interface module.	Number
Profile users	Indicates the number of logged in users who have access to configure and manage security profiles of other users.	Number	This mostly include operations like adding new user and configuring roles for them. These are mostly light weight operations and don't require much server resources.