We could put a Save button inside the webpart but, that would lead to an inconsistent user interface. The user may get confused between the Save button on the ribbon and the save button in the webpart.

We could trap the Save button event by creating an Elements.xml file with a CommandUIHandler for the SaveProject Command.

We’d put in our own javascript in the CommandUIHandler’s CommandAction. However, doing this would override the Save functionality on the PDP ribbon permanently and only our custom code would get called all the time. The out-of-box (OOB) save functionality would be completely overridden, and clicking the Save button on any OOB PDP or a PDP with OOB webparts would not save any of the data.

The problem is, we need to hook into the Save button, but at the same time, we do not want to override the OOB save. We can accomplish this with PageComponents (thank you Abhishek Kumar (abhiku), Microsoft)

Here is what Abhishek said:
“I think what you need is to write a PageComponent. These are javascript snippets which you can register to the Ribbon PageManager to listen to commands. Find out the command for the Save button and set your custom page component to listen for it. The PageManager would call your associated function too when the button is clicked.”

Here’s what you need to do

1. Create the webpart with your desired functionality.
2. Create a custom page component. The page component should listen for the ‘SaveProject’ command. (you can find out this command and others from the pwaribbon.xml file)
   Refer the PageComponent creation part of the following link. The PageComponent on this article is simple and straightforward.
   https://blogs.msdn.com/b/sharepointdeveloperdocs/archive/2010/01/28/how-to-create-a-web-part-with-a-contextual-tab.aspx
3. Implement ICallbackEventHandler on your webpart.
   https://msdn.microsoft.com/en-us/library/ms153106.aspx
4. From within the page component javascript code, perform a callback when the SaveProject command is received.

The complete source code can be downloaded from the attachment.

Testing it

1. Open the solution file in Visual Studio
2. Update the project properties to point to your PWA
1. 
3. From visual studio, you can directly hit F5 to Debug or right click on the project and select deploy
4. Add the webpart to one of the PDPs, preferably a PDP which shows some project fields that can be updated.
1. Navigate to PWA > Server Settings > Project Detail Pages.
2. Create a new page or edit an existing one.
3. Add the DescriptionWebPart webpart on the page
1. 
5. Ensure that the PDP is available in the desired stage
1. PWA > Server Settings > Workflow Stages
2. Select a stage (Proposal Details, for example)
3. Add the desired PDP to the list of Visible Project Detail Pages
1. 
6. Ensure that a project is in the stage to which the PDP was added (eg., Proposal Details)
7. From project center, click on the project > Navigate to the PDP on which the web part was added.

What it finally looks like

1. Hitting the Save button
1. 
2. Custom callback
1. 
3. Custom callback complete
1. 
4. OOB Save triggered
1. 

Note:

1. If the webpart is added on a PDP which does not have any editable project fields (and hence does not required the project to be saved), then the webpart will only perform its own save logic and the OOB save will not be called.
2. When you make changes in the custom page component script or the user interface that is defined in Elements.xml, you must clear the Internet Explorer cache before deploying the solution again. On the General tab of the Internet Options dialog box, click Delete. Select Temporary Internet Files, and then click Delete.
3. The concepts in this article are not new. Existing concepts have been collated together to create a sample which is meaningful in the development world of Project Server 2010.

SaveButtonHandler.zip

https://blogs.msdn.com/chrisfie/archive/2009/04/28/announcing-service-pack-2-sp2-for-microsoft-project-2007-and-microsoft-project-server-2007.aspx

"

Project Service Pack 2 High Level Benefits

Project Standard and Project Professional

·         The scheduling engine, Active Cache, and Gantt charts all have improvements.

·         There is additional reliability with earlier versions of the .mpp format.

Project Server

·         Better memory management in the queue service.

·         Performance to certain database table indexes is improved.

·         Resource plans, build team, cost resources, and the server scheduling engine have improved.

Once your farm has been properly updated the new SP2 product version will be: 12.0.6422.1000 (please referer to the TechNet deployement article for instructions on how to verify an installation).

Getting Ready for Project Server 2010

As part of the SP2 release we announced the following requirements for the next release of SharePoint and Project Server: Windows Server 2008 and 64 bit.

We will be publishing guidance on how to upgrade your existing Project Server 2007 farm to Windows Server 2008 64 bit in the coming weeks on TechNet.

Expect full system requirements for Project Server 2010 at a latter date.

Please note we will release a Service Pack 2 for Project Portfolio Server 2007 within the next two months

"

https://technet.microsoft.com/en-us/library/cc197466.aspx

(1a) User opens a project for the first time.

(1b) Project is cached.

(2a) User opens the project for the second time. Project is opened from the cache.

(2b) Project changes (if any) are downloaded from Project Server.

(3a) User saves the project. Project is saved to the cache. User gets control back with minimal delay.

(3b) Project Professional saves the cached project to the server.

1.       Web Parts which come with SQL Server Reporting Services

2.       Web Parts which come with the Reporting Services Add-in for Sharepoint

Although both these sets of web parts have the same names, they are actually different. The difference between them is that the web parts which come with the add-in will work only with Reporting Services in SharePoint Integrated Mode.

The web parts which come with SQL Server Reporting Services work with Reporting Services in native mode.

The SSRS web parts can be found on the server where Reporting Services is installed. The default location is “C:\Program Files\Microsoft SQL Server\100\Tools\Reporting Services\SharePoint\RSWebParts.cab”. However these web parts are available in x86. Therefore, on a x64 server, the default location would be “C:\Program Files (x86)\Microsoft SQL Server\100\Tools\Reporting Services\SharePoint\ RSWebParts.cab”.

To install these web parts, copy the RSWebParts.cab file on the SharePoint Server and run the following command at the command prompt.

“STSADM.EXE -o addwppack -filename "RSWebParts.cab" -globalinstall”

Refer this link for more details: https://msdn.microsoft.com/en-us/library/ms159772.aspx

The Web Parts which come with the add-in are installed when the add-in is installed. Refer this link for more details: https://technet.microsoft.com/en-us/library/bb326356.aspx

I was not aware of this earlier. Allows programmatic access to Portfolio Server data.

https://code.msdn.microsoft.com/PPSSolutionConnector

The purple one highlighted below is a good one to know – esp when you are customer facing.

The yellow one is an excellent listen – it is totally hilarious

Please find below an inventory of all the Project 2007 content recently published broken out by audience:

Office Online

• Watch this: Up to speed with Project 2007  This six-part video series is designed to help you ramp up on project management and Microsoft Office Project 2007.
• How your project fits into the big picture  This article describes how a project relates to other organizational terms, such as phases, processes, portfolios, and products. It also covers a project’s deliverables, including products, results, and services.
• Ten Things You Can Learn about Project Management from Britney Spears  This podcast is a light-hearted explanation of basic project management concepts, using Britney Spears career as an example.
• Video: Connect to Project Server from Project Professional  This video explains how to connect to Project Server from within Project Professional, and helps to demystify the ambiguities in the process.
• Every Project Plan is a triangle  This article explains at a very high level the underlying premise of project management—that every successful project needs to weigh three critical things.
• Up to speed with Project [This is a few months old, but has continually been updated, and is now complete with all new videos]  Take a tour across Project with videos about core concepts.

TechNet

• Requirements for using SQL Server 2008 Analysis Services with the Project Server 2007 Cube Building Service  This article provides instructions and guidance to use the Project Server 2007 Cube Building Service with Microsoft SQL Server 2008 Analysis Services. It describes configuration requirements, procedures, best practices, and error messages that you might encounter.
• Resource Management  This is the newest article in the "From the Trenches - Deploying the EPM Solution in the Real World" column by Chris Vandersluis. Additional articles by Chris Vandersluis can also be found at the Project Server TechCenter (https://go.microsoft.com/fwlink/?LinkId=134762&clcid=0x409).
• Deploy cumulative updates (Project Server 2007)  This article describes how to install Microsoft Office Project Server 2007 cumulative updates.
• Office Project Server 2007 Technical Library in Compiled Help format (Updated for November)  The entire library for Office Project Server 2007 is now available as a downloadable .chm file. This download includes all content in the library as of November 6, 2008. This download will be updated monthly.
• TechNet Virtual Lab: Enterprise Project Management and Data Visualization using Microsoft BI Tools and Solutions  This lab shows you how to leverage the portfolio of Microsoft business intelligence tools and solutions applied—but not limited to—Enterprise Project Management (EPM) data. This lab will also help you discover how to leverage Excel Services in Microsoft Office SharePoint Server 2007, Office Project Server 2007, SQL Reporting Services 2005, Microsoft Office Visio 2007, Microsoft Office SharePoint Server 2007 Dashboard, and Project KPIs to provide full-feature solutions to solve customer requirements for Office Project Server 2007.
• Plan for disaster recovery in Project Server 2007  This series of articles describes best practices for planning a disaster recovery solution for Project Server 2007.
• Planning for fault tolerance and availability in Project Server 2007  This topic provides planning guidance for fault tolerance and availability in a Project Server 2007 deployment.
• Enterprise disaster recovery for Project Server 2007  This series of topics describes procedures and best practices for backing up and restoring Project Server 2007 using SQL Server tools.
• On-Demand Webcasts
• TechNet Webcast: Microsoft Office Project Server 2007: Solution Overview and System Elements (Level 300)
• TechNet Webcast: Microsoft Office Project Server 2007: Solution Elements and Data Flow (Level 300)
• TechNet Webcast: Microsoft Office Project Server 2007: Workload Scenarios and Reference Architecture (Level 300)
• Live Webcast
• TechNet Webcast: Microsoft Office Project Server 2007: Network Communication (Level 300)
• December 3, 2008, 11am Pacific Time
• TechNet Webcast: Performance Management Using Project Server 2007 and PerformancePoint Server 2007 (Level 200)
• December 4, 2008, 11am Pacific Time

MSDN

• The Project 2007 Resource Center includes descriptions and links to three videos that were posted in October:
• Timesheet Customizations for Project Server 2007
• Working with the Project Server 2007 Reporting Database
• Visual Studio Team Foundation Server and Project Server 2007

Key Enterprise Project Management Resources

Microsoft Project Server 2007 supports Microsoft SQL Server 2008 (released last august).

You’ll find below related links including how to configuration the Cube Building Service.

Key reasons why consider SQL 2008:

·         Performance, by implementing database backup compression.

·         Availability, by implementing log stream compression.

·         Security, by implementing Transparent Data Encryption (TDE).

·         Resource management, by using SQL Server 2008 Resource Governor

·         Reporting Services 2008 (much easier to author custom reports and rich rendering using the acquired Dundas control)

·         Analysis Services 2008

Check the related TechNet article for more information:

·         Determine hardware and software requirements (Project Server)

Check the note at the bottom of the article:

Office Project Server 2007 supports Microsoft SQL Server 2008. However, you must install Windows SharePoint Services 3.0 with Service Pack 1 (SP1) or later as well as Office Project Server 2007 SP1 or later before you install SQL Server 2008.

·         Requirements for using SQL Server 2008 Analysis Services with the Project Server 2007 Cube Building Service

This article describes requirements for using SQL Server 2008 Analysis Services with the Microsoft Office Project Server 2007 Cube Building Service.

·         Integration of SQL Server 2008 and Office SharePoint Server 2007

This article provides prescriptive guidance for implementing some of the new features in Microsoft SQL Server 2008 that enhance the deployment of Microsoft Office SharePoint Server.

·         SQL Server TechCenter

Good to know, given the fact that WSS / MOSS is the platform for Project Server.

https://office.microsoft.com/en-us/sharepointserver/HA101978031033.aspx