The third part of the "new and different" posting deals with servers and services in Project Server 2007. By servers I also include some of the other products in the Microsoft Office 2007 server family as well as the functional breakdown of servers you may have in your server "farm". Likewise "services" covers both those services found in the usual operating system services control as well as services running under the control of Windows SharePoint Services. Hopefully all will become clear.
I will not be talking too much about performance choices of the different installation topographies here - more detailing what all the different bits do. The TechCenter at http://www.microsoft.com/technet/prodtechnol/office/project/default.mspx has good documentation covering farm topography. As Project Server is now built on top of Windows SharePoint Services 3.0 (WSS) you will also find the WSS TechCenter very useful at http://www.microsoft.com/technet/windowsserver/sharepoint/default.mspx.
When you install Project Server 2007 you have a number of choices open to you regarding the split of services and servers, as well as having additional functionality from other servers in the family. The simplest installation is to just install Project Server 2007. This could even be installed on a single server although please review the other documentation on the TechCenter to understand if this makes sense for your requirements. This single install can also load and configure WSS and can install SQL Express as the database to support both WSS and Project Server. This is usually termed the "standalone" installation. You can also achieve the same end result using the "complete" installation and this gives you the flexibility to choose a different database server (or perhaps a named instance on the same server). So the next most complex installation is introduced here - having a separate database server. So on one server you are running the web server and application server services, and all the database activity happens on another server. The next split is to have the application server and the web server as different machines. This can be achieved by adding a "Web Front End" (WFE). This is one of the installation options when installing Project Server 2007 and if you are adding a WFE you need to identify the database where your SharePoint (WSS) configuration database is located and then you add the WFE to the server farm.
The three server configuration of Web Front End, Application Server and Database Server can be further extended by adding additional servers of any or all of these three types to spread the load - or even have specific application server for instance taking a particular service. This comes more into its own when running multiple servers from the Office 2007 family - so search or Excel services could be served by a particular server. Reporting from Project Server could also extend the number of servers as you could have SQL Analysis Services and SQL Reporting Services either on the same database server or additional machines.
Services break down in to two related groups; those shown on the WSS Central Admin home page as Services on Server, and those in the usual Administrative Tools location for operating system services. So in my example here I will tell what is running on my server farm where I have loaded Microsoft Office SharePoint Server 2007 (MOSS) and Project Server 2007 - and configured Project Server and Office Search, but not Excel Services.
Web Front End - WSS Services
Web Front End - Operating System Services
Application Server - WSS Services
Application Server - Operating System Services
One thing to note is that the services within WSS control those within the OS. So if you stop any of the OS services you will probably see them start right up again - and even changing the identity of the service through the "Services" applet you will see this change back to what it had been set to within WSS. All maintenance of services should be handled through Central Administration - or the command line stsadm.exe tool.
I'll concentrate mainly on the Project services here. The Project services only run on the application server - the web front end can be thought of as just running a WSS application that happens to be Project Web Access (PWA) - no more services required at the front end. The Project Application Service controls the other two operating system services and also needs to be running to provision a new PWA site. If you are familiar with the editsite tool in Project Server 2003 this function is now handled through WSS and specifically in the shared services provider (more later). The two operating system services handle the queue service and server side events. If you look in task manager on the application server you will probably see two of each service running. Basically one of each will start, and then spawn another of each for every shared service provider (SSP) configured in the farm.
The queue service is the new architectural feature of Project Server 2007 that helps to deliver consistent performance by spreading the load. It can be configured through Server Settings of PWA where you can set properties for the 2 different queues: Project and Timesheet. Many of the features within Project Server rely on the queue to move data around, and queue system ensures the server gets a steady stream of work even if everyone submits their timesheets at exactly the same time on a Friday afternoon (as if).
The event service handles the server side events that are a new programmability feature of 2007. You can now write custom code to tie in to numerous events - such as creating a project, publishing a project, submitting a timesheet and very many more. This give a great way to extend Project Server to tie in to your other line of business systems, or just to enhance the functionality of Project.
I'll only mention a couple of WSS services here - the Timer service, which is behind all of the activity on the system - similar in a way to the queue in Project, the Timer service executes timed jobs. Creation of PWA sites and building a cube are a couple of examples where the timer service gets involved. The Web Application Service is the key service for WSS that enables sites to work - including those of WSS itself. WSS is really a WSS application in the same way that Project is!
I said I would come back to shared service so here we go. Think of the shared services provider as being a collection point for the non-core WSS applications that can run on the server. If you have just loaded Project Server then this will be the only item in the SSP. If you have loaded MOSS then you will also see many other components such as the search and portal features as well as the new feature of Excel Calculation Services. You would normally only create multiple SSPs if you needed segregate your instances of Project Server - or isolate some services to specific servers. If you have 2 SSPs then you would see 3 of each of the Queue and Event service running on your application server.
That's all for now - plenty to get your heads around. If you have any areas of project Server you would like some coverage on then please let me have feedback.
Technorati Tags: Project Server 2007
Hi Brian, nice to see an article concentrating on the new infrastructure reqs of PS2007. Can we see some articles relating to PS2007 on the following - MOSS (eg how to create workflow) and SRS (eg how to create reports & publish them etc). These areas are going to be increasingly important...
Great suggestion Ben. I will do a general posting on MOSS and workflow (and even workflow without MOSS) later this week. I will put reporting on the list too. I will also check the other blogs for reporting content and post links as appropriate.
We were having a problem where workflows would not start when a new list item was created. I had read somewhere that restarting the SharePoint Services Web Application service would fix this. Through the central administration page I was able to stop the service fine, but it will not start now. The service's status is listed as "starting" and the comment is "Required on Farm, not running". Rebooting the server did not help. As a result of this we cannot create any new web part pages (get an unknown error page), and also workflows and alerts don't work. Do you have any ideas how we can get the service started again? If there is a better place I should be asking this question, please let me know. Thanks for your help!!!
The SharePoint blogs may be able to help. I would check the ULS logs, and look after a reboot so hopefully you will see the first attempt to start the service. Have you changed any accounts or passwords lately? I have seen this some time ago during the beta but don't know root cause at this stage.
Brian, I'm trying to provision project server 2007 into my farm, I installed the app server on 2 servers and added project WFE to my existing WFE servers. I confirmed that the project app service is started. But when I go to SSP and click on the "Project Web Access Sites" link it errors out with "The Project Application Service doesn't exist or is stopped. Start the Project Application Service."
I have seen this before and can happen if the installer does not have the right permissions to start the service. The following command line may get the service started correctly when run as the administrator:-
stsadm -o provisionservice -action start -servicetype "Microsoft.Office.Project.Server.Administration.ProjectApplicationService, Microsoft.Office.Project.Server.Administration, Version=22.214.171.124, Culture=neutral, PublicKeyToken=71E9BCE111E9429C" -servicename ProjectApplicationService
I can see tons of events like flooding my event log (more than 300 per second). Is this normal?
Event Type: Information
Event Source: Windows SharePoint Services 3
Event Category: E-Mail
Event ID: 6871
Time: 10:13:38 AM
The Incoming E-Mail service has completed a batch. The elapsed time was 00:00:00. The service processed 0 message(s) in total.
You could narrow down the problem by looking at the services you have enabled and try shutting off ones related to e-mail handling from lists. Operations, Configure Incoming E-mail settings would be a good place to start. You might also want to try a SharePoint blog or newsgroup.
One other thing is to see what settings you have for Operations, Doagnostic Logging. You may be able to turn down the criticality of events to report to avoid these (if they are really valid).
I tried to enable the Project Application Service after a fresh install and it wasn't in the list.
Under Central Admin>Operations>Services on server the "Custom" button is grayed out and the View is set to "All"
The Project Application service is still not there. This is a fresh install. I've uninstalled and reinstalled several times.
I've upgraded to WSS 3.01 update and also Sharepoint SP1 update...still the service doesn't show.
I've also tried the stsadm command you mentioned to start the service and I get this:
C:\Documents and Settings\EPM-FarmAdmin>stsadm -o provisionservice -action start
Service, Microsoft.Office.Project.Server.Administration, Version=126.96.36.199, Cultu
re=neutral, PublicKeyToken=71E9BCE111E9429C" -servicename ProjectApplicationServ
The service name and type specified are not valid. The service may not be instal
led or may not have been specified with the namespace or assembly qualified name
, which is case sensitive and required for services not in SharePoint. Additiona
C:\Documents and Settings\EPM-FarmAdmin>
Any help would be greatly appreciated!
Does Project Server 2007 show in Add/Remove programs? It almost seems as if it hasn't been installed. Did you run the config wizard succesfully after install of Project Server 2007?
I'm a novice in both PS and WSS. We're putting together an architecture for PS 2007, the connector, and TFS. Helpfully, PS, TFS, and WSS are being designed into different domains (and obviously on different physical servers). There's trust between the domains of TFS and PS, and between those of PS and WSS, but not between those of TFS and WSS (a long story of internal politics).
My question - is this even possible? Everything I've seen looks like PS2007 is practically a subroutine off WSS. Do they have to be on the same machine? I need to get back to my architects quick if this is not doable.
Project Server 2007 requires WSS 3.0 and will load it if it is not present - so it needs it on the same machine and cannot make use of WSS on another server/domain. It is very much a WSS 3.0 application and even the Project Web Access sites are WSS sites.
I hope this helps.
I'm having the same problem now that I had in May and I don't remember what i did then to fix it.
To answer your last question, yes- the sharepoint configuration wizard completed successfully. I even "repaired" Project Server from add/remove.
I think the problem is in the WSS Infrastructure update and office server update.
Once those are installed on a new server it removes the "project application service" from list of available services.
The stsadm.exe command errors out with the same as i had before...I wonder if it's because the service type may be different with the upgrade???
Thanks for your help.
I haven't seen this. The Office Server IU contains the stuff for Project too - so updates the Project piece and does not change any service types. Does it not show when you have "Custom" selected under Services on Server? Do you have Project Server on all servers in the farm? Re-installing the Project Server bits and re-running the configuration wizard might be one option - but the IU might then need to be re-applied.
I am having the same issue with the service not showing up. When I click on the SSP home link it says "The Project Application Service doesn't exist or is stopped. Start the Project Application Service." Were you able to find the solution to this issue? Your help would be greatly appriciated.