Implementing Enterprise Portfolio Management with Microsoft Project Server 2002

The Microsoft Project Server setup process creates registry entries that identify the locations of various components and contain information necessary for the Project Web Access application to connect to its data stores. You should also be aware of registry keys pertinent to your STS and SQL Server installations, as it may become necessary for you to manipulate these.

Project Server Registry Keys

Registry keys for Project Server are created under HKEY_LOCAL_MACHINE\ Software \Microsoft \Office \10.0\MS Project\WebClient Server. Under the WebClient Server key, entries are created under Languages and the virtual directory name that you gave your Project Server installation. By default, this is equal to “projectserver” (without the quotes). Figure 7-17 shows the registry expanded, revealing two Project Server sites on the machine. In this case, registry keys are created under two virtual directories, ProjectServer and projectserver3. This information is taken from the Microsoft Project 2002 Resource Kit, which is available on TechNet at http://www.microsoft.com/technet/treeview/default.asp?url=/ technet/prodtechnol/project/project2002/reskit/default.asp.

Figure 7-17. Registry expanded to reveal two Project Server instances

\Datasets Keys

The \Datasets key contains the physical data locations for Microsoft Project Server. The subkeys to \Datasets include the keys presented in the following sections.

\Application

This key contains the connection information for the Project Server database corresponding to the named virtual directory.

• connectInfo: Stores the database connection string for the Microsoft Project Server database. The string contains the following key/value pairs separated by a semicolon:

  Provider = SQLOLEDB;

  User ID = MSProjectServerUser;

  Password = The database password;

  Persist Security Info = False;

  Initial Catalog = ProjectServer;

  Data Source = <SQL Server Name>

• Proj Password: The password for the user specified in Proj Username.

  Value = Password set during installation

• Proj Username: The database user identity with which Microsoft Project Professional connects to the Microsoft Project Server database.

  Value = MSProjectUser

• QueryFileExt: Points to the Microsoft Project Server extended SQL Query Library.

  Value = <drive>:\Program Files\Microsoft Project Server\Bin\QYLIBSQL.sql

• QueryFileStd: Points to the Microsoft Project Server standard SQL Query Library.

  Value = <drive>:\Program Files\Microsoft Project Server\Bin\QYLIBSTD.sql

• QueryTimeout: The amount of time the component will wait for the SQL Server.

  Value = 1200

\EnterpriseDatabase

This key contains information specific to the enterprise features of the Microsoft Project Server database.

• DSN: The views processing engine uses this DSN to access the Microsoft Project OLE DB provider.

  Value = PC10DSN (default)

• UserName: The username associated with the preceding DSN.

  Value = MicrosoftProjectServerUser

• Password: The password for the previously specified UserName.

  Value = <system assigned Password for UserName>

\STS

This is the key that contains connection values for Microsoft Project Server to connect to the STS database.

• connectInfo: Stores the database connection string for the STS database. The string contains the following key/value pairs separated by a semicolon:

  Provider = SQLOLEDB

  Integrated Security = SSPI

  Persist Security Info = False

• QueryFileExt: Contains a pointer to the extended Microsoft Project Server SQL Query Library.

  Value = <drive>:\Program Files\Microsoft Project Server\Bin\QYLIBSQL.sql

• QueryFileStd: Contains a pointer to the standard Microsoft Project Server SQL Query Library.

  Value = <drive>:\Program Files\Microsoft Project Server\Bin\QYLIBSTD.sql

\ViewsFileDrop

This key contains the location where the views processing service receives new view files.

• connectInfo: Contains the path to where the views processing service listens for new publish action view files.

  Value = <drive>:\Program Files\Microsoft Project Server\Bin\View Drop\

\ViewsSchedulingDatabase

This key contains connection information for the views scheduling database.

• connectInfo: Contains the database connection string for the Microsoft Project Server database. The string contains the following key/value pairs separated by a semicolon:

  Provider = SQLOLEDB;

  User ID = MSProjectServerUser;

  Password = The database password;

  Persist Security Info = False;

  Initial Catalog = ProjectServer;

  Data Source = <SQL Server Name>

• QueryFileExt: Contains a pointer to the extended Microsoft Project Server SQL Query Library.

  Value = <drive>:\Program Files\Microsoft Project Server\Bin\QYLIBSQL.sql

• QueryFileStd: Contains a pointer to the standard Microsoft Project Server SQL Query Library.

  Value = <drive>:\Program Files\Microsoft Project Server\Bin\QYLIBSTD.sql

\Services Keys

The \Services key contains configuration information Microsoft Project Server services. The Configuration key has two subkeys, which I describe in the following section.

\SessionMgr

This key contains a GUID for a name. The (Default) entry in the GUID folder points to the server running Session Manager.

\Languages Keys

The \Languages key contains the languages supported by the current Microsoft Project Server instance.

• defLCID: Stores the locale ID (LCID) for the Project Server default language.

• LCIDXXXX: XXXX equals the LCID of the first language supported by the Microsoft Project Server instance.

• LCIDXXXn: XXXn equals the LCID of the nth language (2 through n) supported by the Microsoft Project Server instance.