PROJECT SERVER 2013. “WHITE PAPER” SOBRE LAS SOLUCIONES ONLINE Y “ON-PREMISES”.
Buenas,
Queríamos haceros llegar la información respecto a este “white paper” que ha publicado recientemente nuestro colega Rob Bowers, donde nos explica las mejores prácticas para implementar Project Server 2013 en su organización. Esto le puede servir de guía a aquellas personas que pretendan llevar esto a cabo, y para cualquiera que pretenda tener más claro determinados conceptos de estas versiones de Project, ya que nos ofrece una comparación analítica entre ambas versiones (Online vs On-Premises), y describe escenarios donde sería recomendable seleccionar una solución sobre la otra.
Esta información está recomendada a partners, consultores, personal técnico y a personas encargadas de tomar este tipo de decisiones, que necesiten entender los requisitos para implementar y desplegar Project Server 2013 en sus entornos, ya sean la versión “On- Premises” o la "Online”, con Office 365.
Se puede descargar del siguiente enlace: Online and On-Premises Solutions for Project Server 2013.
No voy a añadir nada del artículo aquí, salvo esta tabla comparativa, la cual considero bastante relevante, a fin de ir estableciendo los criterios iniciales al respecto:
Differentiator |
On Line |
On Premises |
Administrative backup and restore for Projects (used to restore a slightly older version of a project without pulling a tape and impacting an entire organization) |
|
x |
Archival Environments to retain data |
|
x |
Multi-Dimensional Olap Cubes |
|
x |
Direct access to SQL Server Databases and OLAP Databases |
|
x |
Direct SQL Query Access to Project Server and SharePoint Databases |
|
x |
Team Foundation Server Connectivity (including 2012) (Note: The version of Project used must have the Team Foundation Server extensions installed. These extensions are not present, out of the box, in the online version.) |
|
x |
Standard Windows Installation (MSI) |
|
x |
Event Handlers can use both full trust event handlers and remote event receivers |
|
x |
Full access to PSI and CSOM |
|
x |
Access to ULS Logs By default ULS Logs are located at C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\15\LOGS directory |
|
x |
As a result of full access to the databases, PSI and CSOM there is more flexibility for Business Intelligence, Dashboards, and Reports |
|
x |
Recycling Bin for documents, projects, and sites Note: –Caution should be exercised when emptying the recycle bin. Once a project or a site is deleted from the recycle bin. It is deleted (gone) and cannot be recovered. |
x |
x |
Project Web Applications (Add applications to PWA) |
x |
x |
SharePoint Permission Mode or ProjectServer Permission Mode |
x |
x |
Monitoring Enhancements |
x |
x |
SharePoint Designer for workflows |
x |
x |
No database administration |
x |
|
Security handled by Microsoft |
x |
|
Latest and greatest service packs and cumulative updates |
x |
|
Click-to-run installation |
x |
|
No direct access to SQL Server and OLAP Databases (Reporting is done via OData ) |
x |
|
Access using CSOM (Note: PSI interfaces do not support O- Authentication) |
x |
|
Event Handlers require remote event receivers |
x |
|
Extensibility is accomplished via the use of the SharePoint Extensibility Model – (as a result there is no full-trust code) |
x |
|
Esperamos os resulte de interés y utilidad, un saludo
Jorge Puig