P6 EPPM Quantity Info Test
Oracle Primevera uses P6 database to store the projects and related information and is able to handle very large number of projects. For P6 EPPM to perform optimally there should be appropriate hardware available to support the quantity of data and activity on P6 database, application and job servers. Administrators need to know how many projects have been stored in the database, how many new projects have been created recently, what is the number of users, what is the number of concurrent users etc. This will allow the administrators to plan data and compute capacity accordingly. For example if current deployment is going to support very small number of projects only, administrators will configure only one server and small database instance to support the same. On the other hand if the deployment is supposed to service a large number of teams across the regions and very large number of users and activity, it should be on proper cluster of application and database servers to scale an handle the load.
This test measures the key indicators of load on the system and reports metrics like number of projects, users, resources etc. which help administrators plan and provision capacity.
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
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 |
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 |
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:
|
Measurement | Description | Measurement Unit | Interpretation |
---|---|---|---|
Projects |
Indicates the count of total projects stored in P6 database |
Number |
Large number of projects means more load on database as well as application and Job Servers. Administrators have to look at this number and plan capacity accordingly. |
Project codes created recently |
Indicates the number of project codes created during last specified number of days. |
Number |
If large number of projects are being created recently means administrators may expect enhanced activity in upcoming days. |
Recent project code assignments |
Indicates the number of project codes assigned during last specified number of days. |
Number |
If the project codes and also assigned, that means users have started working on newly created projects. Administrators may need to add more capacity. |
Activities |
Indicates the total number of activities across all the projects currently active in P6 database. |
Number |
Activities is the smallest unit in P6, more the activities means more work is being done. |
Recent activity codes |
Indicates the number of activitycodes created during last specified number of days. |
Number |
If lot of projects and activities are being created and assigned , it means that lot of data is going to be created and lot more compute capacity is going to be required. You can take a call looking at existing capacity if this will suffice or more capacity is required to support enhanced activities.
|
Recent activity codes assignments |
Indicates the number of activity codes assigned during last specified number of days. |
Number |
|
Recent activity resource assignments |
Indicates the number of resource assigned to activity codes in last specified number of days. |
|
|
Users |
Indicates the total number of users across all projects currently in P6 database. |
Number |
Administrators have to plan the server capacity to respond to user requests in timely manner. large number of users can bring down the system even if number of projects is less. |
Number of user defined fields |
Indicates the number of additional fields created by users apart from existing standard fields. |
Number |
P6 provides functionality for users to define their own fields, but if the number of these fields is very high it can create aberration in capacity planning. |