PWA On-Premises has the same look and feel as Project On-Line. What this means is that it is the same Project Server, you can add lists, libraries, and other applications. You can do everything you can do online and more. One of the key differentiators of an On-Premises solution is that you have direct access to the databases, access to OLAP Cubes, and more control and responsibility. Reporting: More flexibility with reporting. Data does not need to be time-phased and unlike the online solution where no direct access is provided to the SQL or OLAP Databases, here you have full control. Do you want to see your reports on an iPad or with another browser such as Safari, Firefox, or Chrome? You can. What does an On-Premises Architecture look like? Project Server 2013 is based on SharePoint Server 2013. The diagrams below shows both on premises and online applications. For an On Premises Solution there would be an additional layer of security provided by your Data Centers. Project Server 2013 Diagram Extranet Environments for Project Server 2013 On-Premises Solutions Project Server 2013 runs as a service in SharePoint Server 2013. What this means is that Project Server 2013 uses the same architectural criteria that SharePoint Server 2013 uses. Capacity Management for a Project Server 2013 On-Premises Solution. This section provides insight into Capacity Management for Project Server 2013 On Premises Solutions. For more information please see the Project Server 2013 capacity planning document located at Ideally when planning for load/capacity management it is a good idea to plan for and to project needs for several years out. When considering what to plan for, there are many factors which influence hardware configuration as well as capacity management. Some of these factors include the following: User Profile: There are several types of users ranging from real people to Interface Feeds simulating what a real person would perform as well as the Project Server threading model on how many queue operation to run concurrently in the back end processing data. The various user profiles place stress on the web front end, application server as well as SQL Server depending on the operation being performed. Feature Usage/Workload: The type of workflow and features used change the performance characteristics of the system. Usage profiles can change the design on all tiers of the solution.
PWA On-Premises has the same look and feel as Project On-Line. What this means is that it is the same Project Server, you can add lists, libraries, and other applications. You can do everything you can do online and more. One of the key differentiators of an On-Premises solution is that you have direct access to the databases, access to OLAP Cubes, and more control and responsibility. Reporting: More flexibility with reporting. Data does not need to be time-phased and unlike the online solution where no direct access is provided to the SQL or OLAP Databases, here you have full control. Do you want to see your reports on an iPad or with another browser such as Safari, Firefox, or Chrome? You can. What does an On-Premises Architecture look like? Project Server 2013 is based on SharePoint Server 2013. The diagrams below shows both on premises and online applications. For an On Premises Solution there would be an additional layer of security provided by your Data Centers. Project Server 2013 Diagram Extranet Environments for Project Server 2013 On-Premises Solutions Project Server 2013 runs as a service in SharePoint Server 2013. What this means is that Project Server 2013 uses the same architectural criteria that SharePoint Server 2013 uses. Capacity Management for a Project Server 2013 On-Premises Solution. This section provides insight into Capacity Management for Project Server 2013 On Premises Solutions. For more information please see the Project Server 2013 capacity planning document located at Ideally when planning for load/capacity management it is a good idea to plan for and to project needs for several years out. When considering what to plan for, there are many factors which influence hardware configuration as well as capacity management. Some of these factors include the following: User Profile: There are several types of users ranging from real people to Interface Feeds simulating what a real person would perform as well as the Project Server threading model on how many queue operation to run concurrently in the back end processing data. The various user profiles place stress on the web front end, application server as well as SQL Server depending on the operation being performed. Feature Usage/Workload: The type of workflow and features used change the performance characteristics of the system. Usage profiles can change the design on all tiers of the solution.