System Requirements
- Last updated
- Save as PDF
This page is not applicable to Planview Hub Cloud.
Beginning in May 2024 (Planview Hub version 24.2), support for the MySQL database will be dropped and extended support for operational databases will be ended. If using a MySQL database, a migration procedure will be provided to move to a supported database.
If you have any questions, please contact customer care.
General Requirements
Planview Hub is a web application which runs centrally on a server. Users interact with it through a web browser from any computer that has network access to the server.
For best results, Hub should be deployed in an environment that has good network throughput and low latency to its operational databases and all repositories involved in an integration.
Below are general requirements to meet the needs of typical deployment scenarios.
- Hub must be installed in a server environment and only one instance of Hub should be installed on each server.
-
The Hub operational database should have its own machine and should be co-located with the Hub server to reduce latency.
Note: TLS 1.2 is required for all encrypted connections. The database used for storing Hub operational data and any repositories being used must support TLS 1.2
User Requirements
To install and configure Hub, you need an account with administrative privileges on your server. The account must also have read/write access to the default file locations.
Supported Operating Systems
Note: For Windows, Powershell 4 must be installed on your server.
The following 64-bit operating systems and versions are supported:
- Windows 10
- Windows 11
- Windows Server 2019
- Windows Server 2022
- Oracle Enterprise Linux 7+
- Oracle Enterprise Linux 8+
- Red Hat Enterprise Linux 8.x
- Red Hat Enterprise Linux 9.x
- Ubuntu Linux 20.04 LTS
- Ubuntu Linux 22.04 LTS
- SUSE Linux Enterprise Server 12.x
- SUSE Linux Enterprise Server 15.x
Note: Certain connectors (e.g., IBM DOORS) only run on Windows operating systems. Before installing Planview Hub, we recommend consulting with your customer care to determine which operating system best fits your integration scenario.
Supported Browsers
Note: Planview Hub runs with a minimum screen resolution of 1280 pixels x 800 pixels.
The Planview Hub web interface is supported on the following browsers:
- Firefox 111+
- Google Chrome 111+
- Microsoft Edge 111+
Java Runtime Environment
Planview Hub is packaged with a JRE; there is no need to install a JRE separately. Planview Hub uses and ships with Oracle Java.
Note: Partner branded editions of Planview Hub use and ship with Azul OpenJDK.
Deploying Hub on a Cloud Environment
To ensure reliable performance, all virtual machines (on-prem and private cloud) must meet the requirements listed in the General Requirements section.
Hub can be deployed in operating systems on physical servers within virtual machines hosted on dedicated on-prem virtual machine hosts. Hub can also be deployed within private cloud deployments, such as AWS or Azure. If deploying on a private cloud environment, Hub and its operational database must be deployed using a full image and not a container, with the exception of AWS RDS PostgreSQL. Hub cannot run in containerized deployments (Kubernetes, OpenShift, etc.).
Planview has qualified AWS RDS PostgreSQL deployments for use as the operational database for Hub instances hosted in AWS private cloud environments. Planview does not offer direct support for private cloud hosting infrastructure (i.e., AWS networking and configuration) beyond the operation of Planview’s own products within the hosted environment. See the section below for recommended configuration settings.
AWS RDS PostgreSQL Recommendations
The recommendations below offer a general guideline only. We recommend consulting with customer care to determine the exact needs for your integration scenario, and for guidance on how to efficiently configure Hub.
Note: Planview does not troubleshoot or maintain AWS RDS PostgreSQL. Please ensure your database is configured in a way that is aligned with your security policy and that the associated risks are understood and accepted.
|
Setting |
Recommended Value |
|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Hardware Sizing for Deployment Scenarios
General Notes and Considerations
Below are recommendations on sizing hardware and virtual machine capacity to meet the needs of typical deployment scenarios.
These recommendations are guidelines intended to provide a starting point when deciding on hardware allocation for a specific deployment. We recommend monitoring system load including CPU usage, memory pressure and disk queue length, and adjusting the system sizing accordingly.
For best results, Hub should be deployed in an environment that has good network throughput and low latency to all repositories and databases involved in an integration.
Based on real-life metrics, we approximate database sizing at about 40 KB per artifact. For 100,000 artifacts total (including artifacts on both sides of an integration), that equates to about 4 GB of database storage, not including log files, rollback space, etc.
This is a rough estimate, and will depend on customer-specific configuration and usage. For example, artifacts that have hundreds of fields and many large comments will require more space. Likewise, short change detection intervals, frequent full scans, or frequent changes to large numbers of artifacts will require more processing power.
Hub Server Sizing Recommendations
Note: The recommendations below offer a general guideline only. The performance needs of Hub integrations depend on how integrations are configured, the specifications of connected end systems, and the volume and type of changes made in the end systems.
Note that it is possible for a deployment to have a low number of integrations and users, but a high number of artifact updates (or vice versa). We recommend consulting with customer care to determine the exact sizing needs for your integration scenario, and for guidance on how to efficiently configure Hub.
Small Deployment
A deployment managing up to 20,000 artifacts in up to 100 projects with up to 10,000 updates/month (typically up to 200 active users, and up to 5 integrations).
- 4 GB system memory
- 3 GHz processor, 2 cores
- 50 GB free disk space
Medium Deployment
A deployment managing up to 150,000 artifacts in up to 500 projects with up to 50,000 updates/month (typically up to 1,000 active users, and up to 15 integrations).
- 8 GB system memory
- 2 x 3 GHz processor, 4 cores
- 150 GB free disk space
Large Deployment
A deployment managing up to 1,000,000 artifacts in up to 2000 projects with up to 200,000 updates/month (typically more than 2,000 active users, and 20+ integrations).
- 16 GB system memory
- 4 x 3 GHz processors, 8 cores
- 250 GB free disk space
Extra-Large Deployment
If your deployment exceeds any of the guidelines from the Large Deployment, please consult with customer care.
For extra-large deployments, the specific characteristics of the integrations are crucial when determining proper instance sizing. As a result, no general recommendations can be offered for extra-large deployments.
External Database Sizing
The system that the external database is deployed on should also follow the sizing recommendations listed above. For example, the database for a large deployment should run on a separate machine with 16 GB of memory, 8 cores, and 250 GB of disk space.
Java Heap Size
We recommend setting the maximum Java heap size value to 50-75% of your system’s memory.
Learn more about setting Java heap size here.
Beginning in May 2024 (Planview Hub version 24.2), support for the MySQL database will be dropped and extended support for operational databases will be ended. If using a MySQL database, a migration procedure will be provided to move to a supported database.
If you have any questions, please contact customer care.
General Requirements
Planview Hub is a web application which runs centrally on a server. Users interact with it through a web browser from any computer that has network access to the server.
For best results, Hub should be deployed in an environment that has good network throughput and low latency to its operational databases and all repositories involved in an integration.
Below are general requirements to meet the needs of typical deployment scenarios.
- Hub must be installed in a server environment and only one instance of Hub should be installed on each server.
-
The Hub operational database should have its own machine and should be co-located with the Hub server to reduce latency.
Note: TLS 1.2 is required for all encrypted connections. The database used for storing Hub operational data and any repositories being used must support TLS 1.2
User Requirements
To install and configure Hub, you need an account with administrative privileges on your server. The account must also have read/write access to the default file locations.
Supported Operating Systems
Note: For Windows, Powershell 4 must be installed on your server.
The following 64-bit operating systems and versions are supported:
- Windows 10
- Windows 11
- Windows Server 2019
- Windows Server 2022
- Oracle Enterprise Linux 7+
- Oracle Enterprise Linux 8+
- Red Hat Enterprise Linux 8.x
- Red Hat Enterprise Linux 9.x
- Ubuntu Linux 20.04 LTS
- Ubuntu Linux 22.04 LTS
- SUSE Linux Enterprise Server 12.x
- SUSE Linux Enterprise Server 15.x
Note: Certain connectors (e.g., IBM DOORS) only run on Windows operating systems. Before installing Planview Hub, we recommend consulting with your customer care to determine which operating system best fits your integration scenario.
Supported Browsers
Note: Planview Hub runs with a minimum screen resolution of 1280 pixels x 800 pixels.
The Planview Hub web interface is supported on the following browsers:
- Firefox 111+
- Google Chrome 111+
- Microsoft Edge 111+
Java Runtime Environment
Planview Hub is packaged with a JRE; there is no need to install a JRE separately. Planview Hub uses and ships with Oracle Java.
Note: Partner branded editions of Planview Hub use and ship with Azul OpenJDK.
Deploying Hub on a Cloud Environment
To ensure reliable performance, all virtual machines (on-prem and private cloud) must meet the requirements listed in the General Requirements section.
Hub can be deployed in operating systems on physical servers within virtual machines hosted on dedicated on-prem virtual machine hosts. Hub can also be deployed within private cloud deployments, such as AWS or Azure. If deploying on a private cloud environment, Hub and its operational database must be deployed using a full image and not a container, with the exception of AWS RDS PostgreSQL. Hub cannot run in containerized deployments (Kubernetes, OpenShift, etc.).
Planview has qualified AWS RDS PostgreSQL deployments for use as the operational database for Hub instances hosted in AWS private cloud environments. Planview does not offer direct support for private cloud hosting infrastructure (i.e., AWS networking and configuration) beyond the operation of Planview’s own products within the hosted environment. See the section below for recommended configuration settings.
AWS RDS PostgreSQL Recommendations
The recommendations below offer a general guideline only. We recommend consulting with customer care to determine the exact needs for your integration scenario, and for guidance on how to efficiently configure Hub.
Note: Planview does not troubleshoot or maintain AWS RDS PostgreSQL. Please ensure your database is configured in a way that is aligned with your security policy and that the associated risks are understood and accepted.
|
Setting |
Recommended Value |
|---|---|
|
"DBInstanceClass" |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Hardware Sizing for Deployment Scenarios
General Notes and Considerations
Below are recommendations on sizing hardware and virtual machine capacity to meet the needs of typical deployment scenarios.
These recommendations are guidelines intended to provide a starting point when deciding on hardware allocation for a specific deployment. We recommend monitoring system load including CPU usage, memory pressure and disk queue length, and adjusting the system sizing accordingly.
For best results, Hub should be deployed in an environment that has good network throughput and low latency to all repositories and databases involved in an integration.
Based on real-life metrics, we approximate database sizing at about 40 KB per artifact. For 100,000 artifacts total (including artifacts on both sides of an integration), that equates to about 4 GB of database storage, not including log files, rollback space, etc.
This is a rough estimate, and will depend on customer-specific configuration and usage. For example, artifacts that have hundreds of fields and many large comments will require more space. Likewise, short change detection intervals, frequent full scans, or frequent changes to large numbers of artifacts will require more processing power.
Hub Server Sizing Recommendations
Note: The recommendations below offer a general guideline only. The performance needs of Hub integrations depend on how integrations are configured, the specifications of connected end systems, and the volume and type of changes made in the end systems.
Note that it is possible for a deployment to have a low number of integrations and users, but a high number of artifact updates (or vice versa). We recommend consulting with customer care to determine the exact sizing needs for your integration scenario, and for guidance on how to efficiently configure Hub.
Small Deployment
A deployment managing up to 20,000 artifacts in up to 100 projects with up to 10,000 updates/month (typically up to 200 active users, and up to 5 integrations).
- 4 GB system memory
- 3 GHz processor, 2 cores
- 50 GB free disk space
Medium Deployment
A deployment managing up to 150,000 artifacts in up to 500 projects with up to 50,000 updates/month (typically up to 1,000 active users, and up to 15 integrations).
- 8 GB system memory
- 2 x 3 GHz processor, 4 cores
- 150 GB free disk space
Large Deployment
A deployment managing up to 1,000,000 artifacts in up to 2000 projects with up to 200,000 updates/month (typically more than 2,000 active users, and 20+ integrations).
- 16 GB system memory
- 4 x 3 GHz processors, 8 cores
- 250 GB free disk space
Extra-Large Deployment
If your deployment exceeds any of the guidelines from the Large Deployment, please consult with customer care.
For extra-large deployments, the specific characteristics of the integrations are crucial when determining proper instance sizing. As a result, no general recommendations can be offered for extra-large deployments.
External Database Sizing
The system that the external database is deployed on should also follow the sizing recommendations listed above. For example, the database for a large deployment should run on a separate machine with 16 GB of memory, 8 cores, and 250 GB of disk space.
Java Heap Size
We recommend setting the maximum Java heap size value to 50-75% of your system’s memory.
Learn more about setting Java heap size here.
Beginning in May 2024 (Planview Hub version 24.2), support for the MySQL database will be dropped and extended support for operational databases will be ended. If using a MySQL database, a migration procedure will be provided to move to a supported database.
If you have any questions, please contact customer care.
General Requirements
Planview Hub is a web application which runs centrally on a server. Users interact with it through a web browser from any computer that has network access to the server.
For best results, Hub should be deployed in an environment that has good network throughput and low latency to its operational databases and all repositories involved in an integration.
Below are general requirements to meet the needs of typical deployment scenarios.
- Hub must be installed in a server environment and only one instance of Hub should be installed on each server.
-
The Hub operational database should have its own machine and should be co-located with the Hub server to reduce latency.
Note: TLS 1.2 is required for all encrypted connections. The database used for storing Hub operational data and any repositories being used must support TLS 1.2
User Requirements
To install and configure Hub, you need an account with administrative privileges on your server. The account must also have read/write access to the default file locations.
Supported Operating Systems
Note: For Windows, Powershell 4 must be installed on your server.
The following 64-bit operating systems and versions are supported:
- Windows 10
- Windows 11
- Windows Server 2019
- Windows Server 2022
- Oracle Enterprise Linux 7+
- Oracle Enterprise Linux 8+
- Red Hat Enterprise Linux 8.x
- Red Hat Enterprise Linux 9.x
- Ubuntu Linux 20.04 LTS
- Ubuntu Linux 22.04 LTS
- SUSE Linux Enterprise Server 12.x
- SUSE Linux Enterprise Server 15.x
Note: Certain connectors (e.g., IBM DOORS) only run on Windows operating systems. Before installing Planview Hub, we recommend consulting with your customer care to determine which operating system best fits your integration scenario.
Supported Browsers
Note: Planview Hub runs with a minimum screen resolution of 1280 pixels x 800 pixels.
The Planview Hub web interface is supported on the following browsers:
- Firefox 111+
- Google Chrome 111+
- Microsoft Edge 111+
Java Runtime Environment
Planview Hub is packaged with a JRE; there is no need to install a JRE separately. Planview Hub uses and ships with Oracle Java.
Note: Partner branded editions of Planview Hub use and ship with Azul OpenJDK.
Deploying Hub on a Cloud Environment
To ensure reliable performance, all virtual machines (on-prem and private cloud) must meet the requirements listed in the General Requirements section.
Hub can be deployed in operating systems on physical servers within virtual machines hosted on dedicated on-prem virtual machine hosts. Hub can also be deployed within private cloud deployments, such as AWS or Azure. If deploying on a private cloud environment, Hub and its operational database must be deployed using a full image and not a container, with the exception of AWS RDS PostgreSQL. Hub cannot run in containerized deployments (Kubernetes, OpenShift, etc.).
Planview has qualified AWS RDS PostgreSQL deployments for use as the operational database for Hub instances hosted in AWS private cloud environments. Planview does not offer direct support for private cloud hosting infrastructure (i.e., AWS networking and configuration) beyond the operation of Planview’s own products within the hosted environment. See the section below for recommended configuration settings.
AWS RDS PostgreSQL Recommendations
The recommendations below offer a general guideline only. We recommend consulting with customer care to determine the exact needs for your integration scenario, and for guidance on how to efficiently configure Hub.
Note: Planview does not troubleshoot or maintain AWS RDS PostgreSQL. Please ensure your database is configured in a way that is aligned with your security policy and that the associated risks are understood and accepted.
|
Setting |
Recommended Value |
|---|---|
|
"DBInstanceClass" |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Hardware Sizing for Deployment Scenarios
General Notes and Considerations
Below are recommendations on sizing hardware and virtual machine capacity to meet the needs of typical deployment scenarios.
These recommendations are guidelines intended to provide a starting point when deciding on hardware allocation for a specific deployment. We recommend monitoring system load including CPU usage, memory pressure and disk queue length, and adjusting the system sizing accordingly.
For best results, Hub should be deployed in an environment that has good network throughput and low latency to all repositories and databases involved in an integration.
Based on real-life metrics, we approximate database sizing at about 40 KB per artifact. For 100,000 artifacts total (including artifacts on both sides of an integration), that equates to about 4 GB of database storage, not including log files, rollback space, etc.
This is a rough estimate, and will depend on customer-specific configuration and usage. For example, artifacts that have hundreds of fields and many large comments will require more space. Likewise, short change detection intervals, frequent full scans, or frequent changes to large numbers of artifacts will require more processing power.
Hub Server Sizing Recommendations
Note: The recommendations below offer a general guideline only. The performance needs of Hub integrations depend on how integrations are configured, the specifications of connected end systems, and the volume and type of changes made in the end systems.
Note that it is possible for a deployment to have a low number of integrations and users, but a high number of artifact updates (or vice versa). We recommend consulting with customer care to determine the exact sizing needs for your integration scenario, and for guidance on how to efficiently configure Hub.
Small Deployment
A deployment managing up to 20,000 artifacts in up to 100 projects with up to 10,000 updates/month (typically up to 200 active users, and up to 5 integrations).
- 4 GB system memory
- 3 GHz processor, 2 cores
- 50 GB free disk space
Medium Deployment
A deployment managing up to 150,000 artifacts in up to 500 projects with up to 50,000 updates/month (typically up to 1,000 active users, and up to 15 integrations).
- 8 GB system memory
- 2 x 3 GHz processor, 4 cores
- 150 GB free disk space
Large Deployment
A deployment managing up to 1,000,000 artifacts in up to 2000 projects with up to 200,000 updates/month (typically more than 2,000 active users, and 20+ integrations).
- 16 GB system memory
- 4 x 3 GHz processors, 8 cores
- 250 GB free disk space
Extra-Large Deployment
If your deployment exceeds any of the guidelines from the Large Deployment, please consult with customer care.
For extra-large deployments, the specific characteristics of the integrations are crucial when determining proper instance sizing. As a result, no general recommendations can be offered for extra-large deployments.
External Database Sizing
The system that the external database is deployed on should also follow the sizing recommendations listed above. For example, the database for a large deployment should run on a separate machine with 16 GB of memory, 8 cores, and 250 GB of disk space.
Java Heap Size
We recommend setting the maximum Java heap size value to 50-75% of your system’s memory.
Learn more about setting Java heap size here.
Beginning in May 2024 (Planview Hub version 24.2), support for the MySQL database will be dropped and extended support for operational databases will be ended. If using a MySQL database, a migration procedure will be provided to move to a supported database.
If you have any questions, please contact customer care.
General Requirements
Planview Hub is a web application which runs centrally on a server. Users interact with it through a web browser from any computer that has network access to the server.
For best results, Hub should be deployed in an environment that has good network throughput and low latency to its operational databases and all repositories involved in an integration.
Below are general requirements to meet the needs of typical deployment scenarios.
- Hub must be installed in a server environment and only one instance of Hub should be installed on each server.
-
The Hub operational database should have its own machine and should be co-located with the Hub server to reduce latency.
Note: TLS 1.2 is required for all encrypted connections. The database used for storing Hub operational data and any repositories being used must support TLS 1.2
User Requirements
To install and configure Hub, you need an account with administrative privileges on your server. The account must also have read/write access to the default file locations.
Supported Operating Systems
Note: For Windows, Powershell 4 must be installed on your server.
The following 64-bit operating systems and versions are supported:
- Windows 10
- Windows 11
- Windows Server 2019
- Windows Server 2022
- Oracle Enterprise Linux 7+
- Oracle Enterprise Linux 8+
- Red Hat Enterprise Linux 8.x
- Red Hat Enterprise Linux 9.x
- Ubuntu Linux 20.04 LTS
- Ubuntu Linux 22.04 LTS
- SUSE Linux Enterprise Server 12.x
- SUSE Linux Enterprise Server 15.x
Note: Certain connectors (e.g., IBM DOORS) only run on Windows operating systems. Before installing Planview Hub, we recommend consulting with your customer care to determine which operating system best fits your integration scenario.
Supported Browsers
Note: Planview Hub runs with a minimum screen resolution of 1280 pixels x 800 pixels.
The Planview Hub web interface is supported on the following browsers:
- Firefox 111+
- Google Chrome 111+
- Microsoft Edge 111+
Java Runtime Environment
Planview Hub is packaged with a JRE; there is no need to install a JRE separately. Planview Hub uses and ships with Oracle Java.
Note: Partner branded editions of Planview Hub use and ship with Azul OpenJDK.
Deploying Hub on a Cloud Environment
To ensure reliable performance, all virtual machines (on-prem and private cloud) must meet the requirements listed in the General Requirements section.
Hub can be deployed in operating systems on physical servers within virtual machines hosted on dedicated on-prem virtual machine hosts. Hub can also be deployed within private cloud deployments, such as AWS or Azure. If deploying on a private cloud environment, Hub and its operational database must be deployed using a full image and not a container, with the exception of AWS RDS PostgreSQL. Hub cannot run in containerized deployments (Kubernetes, OpenShift, etc.).
Planview has qualified AWS RDS PostgreSQL deployments for use as the operational database for Hub instances hosted in AWS private cloud environments. Planview does not offer direct support for private cloud hosting infrastructure (i.e., AWS networking and configuration) beyond the operation of Planview’s own products within the hosted environment. See the section below for recommended configuration settings.
AWS RDS PostgreSQL Recommendations
The recommendations below offer a general guideline only. We recommend consulting with customer care to determine the exact needs for your integration scenario, and for guidance on how to efficiently configure Hub.
Note: Planview does not troubleshoot or maintain AWS RDS PostgreSQL. Please ensure your database is configured in a way that is aligned with your security policy and that the associated risks are understood and accepted.
|
Setting |
Recommended Value |
|---|---|
|
"DBInstanceClass" |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Hardware Sizing for Deployment Scenarios
General Notes and Considerations
Below are recommendations on sizing hardware and virtual machine capacity to meet the needs of typical deployment scenarios.
These recommendations are guidelines intended to provide a starting point when deciding on hardware allocation for a specific deployment. We recommend monitoring system load including CPU usage, memory pressure and disk queue length, and adjusting the system sizing accordingly.
For best results, Hub should be deployed in an environment that has good network throughput and low latency to all repositories and databases involved in an integration.
Based on real-life metrics, we approximate database sizing at about 40 KB per artifact. For 100,000 artifacts total (including artifacts on both sides of an integration), that equates to about 4 GB of database storage, not including log files, rollback space, etc.
This is a rough estimate, and will depend on customer-specific configuration and usage. For example, artifacts that have hundreds of fields and many large comments will require more space. Likewise, short change detection intervals, frequent full scans, or frequent changes to large numbers of artifacts will require more processing power.
Hub Server Sizing Recommendations
Note: The recommendations below offer a general guideline only. The performance needs of Hub integrations depend on how integrations are configured, the specifications of connected end systems, and the volume and type of changes made in the end systems.
Note that it is possible for a deployment to have a low number of integrations and users, but a high number of artifact updates (or vice versa). We recommend consulting with customer care to determine the exact sizing needs for your integration scenario, and for guidance on how to efficiently configure Hub.
Small Deployment
A deployment managing up to 20,000 artifacts in up to 100 projects with up to 10,000 updates/month (typically up to 200 active users, and up to 5 integrations).
- 4 GB system memory
- 3 GHz processor, 2 cores
- 50 GB free disk space
Medium Deployment
A deployment managing up to 150,000 artifacts in up to 500 projects with up to 50,000 updates/month (typically up to 1,000 active users, and up to 15 integrations).
- 8 GB system memory
- 2 x 3 GHz processor, 4 cores
- 150 GB free disk space
Large Deployment
A deployment managing up to 1,000,000 artifacts in up to 2000 projects with up to 200,000 updates/month (typically more than 2,000 active users, and 20+ integrations).
- 16 GB system memory
- 4 x 3 GHz processors, 8 cores
- 250 GB free disk space
Extra-Large Deployment
If your deployment exceeds any of the guidelines from the Large Deployment, please consult with customer care.
For extra-large deployments, the specific characteristics of the integrations are crucial when determining proper instance sizing. As a result, no general recommendations can be offered for extra-large deployments.
External Database Sizing
The system that the external database is deployed on should also follow the sizing recommendations listed above. For example, the database for a large deployment should run on a separate machine with 16 GB of memory, 8 cores, and 250 GB of disk space.
Java Heap Size
We recommend setting the maximum Java heap size value to 50-75% of your system’s memory.
Learn more about setting Java heap size here.
Beginning in May 2024 (Planview Hub version 24.2), support for the MySQL database will be dropped and extended support for operational databases will be ended. If using a MySQL database, a migration procedure will be provided to move to a supported database.
If you have any questions, please contact customer care.
General Requirements
Planview Hub is a web application which runs centrally on a server. Users interact with it through a web browser from any computer that has network access to the server.
For best results, Hub should be deployed in an environment that has good network throughput and low latency to its operational databases and all repositories involved in an integration.
Below are general requirements to meet the needs of typical deployment scenarios.
- Hub must be installed in a server environment and only one instance of Hub should be installed on each server.
-
The Hub operational database should have its own machine and should be co-located with the Hub server to reduce latency.
Note: TLS 1.2 is required for all encrypted connections. The database used for storing Hub operational data and any repositories being used must support TLS 1.2
User Requirements
To install and configure Hub, you need an account with administrative privileges on your server. The account must also have read/write access to the default file locations.
Supported Operating Systems
Note: For Windows, Powershell 4 must be installed on your server.
The following 64-bit operating systems and versions are supported:
- Windows 10
- Windows 11
- Windows Server 2019
- Windows Server 2022
- Oracle Enterprise Linux 7+
- Oracle Enterprise Linux 8+
- Red Hat Enterprise Linux 8.x
- Red Hat Enterprise Linux 9.x
- Ubuntu Linux 20.04 LTS
- Ubuntu Linux 22.04 LTS
- SUSE Linux Enterprise Server 12.x
- SUSE Linux Enterprise Server 15.x
Note: Certain connectors (e.g., IBM DOORS) only run on Windows operating systems. Before installing Planview Hub, we recommend consulting with your customer care to determine which operating system best fits your integration scenario.
Supported Browsers
Note: Planview Hub runs with a minimum screen resolution of 1280 pixels x 800 pixels.
The Planview Hub web interface is supported on the following browsers:
- Firefox 111+
- Google Chrome 111+
- Microsoft Edge 111+
Java Runtime Environment
Planview Hub is packaged with a JRE; there is no need to install a JRE separately. Planview Hub uses and ships with Oracle Java.
Note: Partner branded editions of Planview Hub use and ship with Azul OpenJDK.
Deploying Hub on a Cloud Environment
To ensure reliable performance, all virtual machines (on-prem and private cloud) must meet the requirements listed in the General Requirements section.
Hub can be deployed in operating systems on physical servers within virtual machines hosted on dedicated on-prem virtual machine hosts. Hub can also be deployed within private cloud deployments, such as AWS or Azure. If deploying on a private cloud environment, Hub and its operational database must be deployed using a full image and not a container, with the exception of AWS RDS PostgreSQL. Hub cannot run in containerized deployments (Kubernetes, OpenShift, etc.).
Planview has qualified AWS RDS PostgreSQL deployments for use as the operational database for Hub instances hosted in AWS private cloud environments. Planview does not offer direct support for private cloud hosting infrastructure (i.e., AWS networking and configuration) beyond the operation of Planview’s own products within the hosted environment. See the section below for recommended configuration settings.
AWS RDS PostgreSQL Recommendations
The recommendations below offer a general guideline only. We recommend consulting with customer care to determine the exact needs for your integration scenario, and for guidance on how to efficiently configure Hub.
Note: Planview does not troubleshoot or maintain AWS RDS PostgreSQL. Please ensure your database is configured in a way that is aligned with your security policy and that the associated risks are understood and accepted.
|
Setting |
Recommended Value |
|---|---|
|
"DBInstanceClass" |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Hardware Sizing for Deployment Scenarios
General Notes and Considerations
Below are recommendations on sizing hardware and virtual machine capacity to meet the needs of typical deployment scenarios.
These recommendations are guidelines intended to provide a starting point when deciding on hardware allocation for a specific deployment. We recommend monitoring system load including CPU usage, memory pressure and disk queue length, and adjusting the system sizing accordingly.
For best results, Hub should be deployed in an environment that has good network throughput and low latency to all repositories and databases involved in an integration.
Based on real-life metrics, we approximate database sizing at about 40 KB per artifact. For 100,000 artifacts total (including artifacts on both sides of an integration), that equates to about 4 GB of database storage, not including log files, rollback space, etc.
This is a rough estimate, and will depend on customer-specific configuration and usage. For example, artifacts that have hundreds of fields and many large comments will require more space. Likewise, short change detection intervals, frequent full scans, or frequent changes to large numbers of artifacts will require more processing power.
Hub Server Sizing Recommendations
Note: The recommendations below offer a general guideline only. The performance needs of Hub integrations depend on how integrations are configured, the specifications of connected end systems, and the volume and type of changes made in the end systems.
Note that it is possible for a deployment to have a low number of integrations and users, but a high number of artifact updates (or vice versa). We recommend consulting with customer care to determine the exact sizing needs for your integration scenario, and for guidance on how to efficiently configure Hub.
Small Deployment
A deployment managing up to 20,000 artifacts in up to 100 projects with up to 10,000 updates/month (typically up to 200 active users, and up to 5 integrations).
- 4 GB system memory
- 3 GHz processor, 2 cores
- 50 GB free disk space
Medium Deployment
A deployment managing up to 150,000 artifacts in up to 500 projects with up to 50,000 updates/month (typically up to 1,000 active users, and up to 15 integrations).
- 8 GB system memory
- 2 x 3 GHz processor, 4 cores
- 150 GB free disk space
Large Deployment
A deployment managing up to 1,000,000 artifacts in up to 2000 projects with up to 200,000 updates/month (typically more than 2,000 active users, and 20+ integrations).
- 16 GB system memory
- 4 x 3 GHz processors, 8 cores
- 250 GB free disk space
Extra-Large Deployment
If your deployment exceeds any of the guidelines from the Large Deployment, please consult with customer care.
For extra-large deployments, the specific characteristics of the integrations are crucial when determining proper instance sizing. As a result, no general recommendations can be offered for extra-large deployments.
External Database Sizing
The system that the external database is deployed on should also follow the sizing recommendations listed above. For example, the database for a large deployment should run on a separate machine with 16 GB of memory, 8 cores, and 250 GB of disk space.
Java Heap Size
We recommend setting the maximum Java heap size value to 50-75% of your system’s memory.
Learn more about setting Java heap size here.