(C) 2000 Microsoft Corporation. All rights reserved.
Web server installation requirements
Install the Microsoft Project Central server
Get
your team ready to start using Microsoft Project Central
To add Microsoft Project Central
Accounts for team members
To add a resource's e-mail address to your project
Customize and administer the server
Set the server to single-user mode
Delete items from the
database
Merge user accounts
Specify
authentication options
Enable
the "Log on using your Microsoft Windows user account" option from the
Logon page
Set
up and manage views and portfolios
About views
Create a view
Use categories to allow team members to see
specific views and information from specific projects
Configure the Microsoft
Project Central server to display project views in shared files or databases
Using a single DSN and database
user ID to see projects belonging to different table owners
Create a view by using data access
pages
Create multiple Microsoft Project Central Web sites on the same server
Set up the Browser Module for Microsoft Project Central
Additional information and troubleshooting
This file documents the installation of Microsoft Project Central, a companion product to Microsoft Project. It includes information on how to install the Microsoft Project Central server, and how to use it to set up a communication center for project managers and team members.
For more information on the structure of the Microsoft Project Central database, see the file svrdb.htm on the Microsoft Project CD at \Pjcntrl\Help\1033\svrdb.htm folder (This folder, 1033, contains the files for the English version. Files for other languages are contained in the folder that corresponds to the locale ID [LCID] for that language).
Hardware and system requirements for the Microsoft Project Central server installations are as follows:
To obtain either the Windows NT Service Pack or the Windows NT 4.0 Option Pack, go to: http://www.microsoft.com/NTServer/.
\IE5\EN\ie5setup.exe
Note If you want to use data access pages, you will needed Microsoft Internet Explorer 5.0 or later, and in addition an Office 2000 license.
The hard disk and memory requirements are for a default installation. Your hard disk and memory requirements may vary depending on your configuration and the options you choose to install.
Microsoft Project Central server and Microsoft Project can be installed on the same computer if necessary. Shared components of Microsoft Project Central server and Microsoft Project 2000 will be installed in the folder, \Program Files\Microsoft Office\Office\1033 (or the appropriate folder for the language version you use).
Hardware, software, and system requirements for the browser client are as follows:
If you choose not to use Internet Explorer, an alternate browser client is available.
Once installed, clients can connect to the Microsoft Project Central server using either Internet Explorer or the Browser Module for Microsoft Project Central. Clients accessing the Microsoft Project Central server must have a Microsoft Project Central client access license.
If you have installed a beta version of Microsoft Project Central, you must remove it before installing the new version.
To remove the beta version of Microsoft Project Central use the following steps:
If you are using Microsoft Windows 2000, from the Control Panel, click Administrative Tools, and then click Internet Services Manager.
Note Uninstalling Microsoft Project Central server does not remove MSDE. To remove MSDE manually, do the following:
- Stop the MSDE service using the Services program in the Control Panel. In the Services dialog box, stop the service named MSSQLServer.
- From the Windows Task Manager, end the program named sqlmangr.exe.
- Remove MSDE using Add/Remove Programs in the Control Panel.
- Delete the data files under the \mssql7\data folder on the server.
- Remove the following registry key:
HKEY_LOCAL_MACHINE\Software\Microsoft\Office\9.0\Web Server\SQLInstalledByPrj
To install Microsoft Project Central server:
Choose this option if you want to use MSDE as your database store for Microsoft Project Central and if you do not have another database you can use. MSDE is suitable if there are no more than 10–15 concurrent users of Microsoft Project Central. The default MSDE database is created with the username "sa" and a password that you specify during installation. If you want a more secure and scalable solution, use a SQL Server or Oracle database as described below.
You cannot choose this option if the computer you are installing on already has either SQL Server or MSDE installed.
To create the SQL server, MSDE, or Oracle database and tables, perform the following actions. For Microsoft SQL Server and MSDE, you can either choose a default installation of the database, or you can create your own database. For Oracle, you cannot create a default installation.
To create a default database and table installation for a SQL Server or MSDE:
From Windows, go to the MS-DOS Prompt.
Change directories to the CD-ROM drive, and on the Microsoft Project CD, go to the folder \Pjcntrl\Isapi\1033 (or the appropriate folder for your language).
Type the following commands to create a database and tables in the database and to insert default records for the tables:
osql -U <account name> -P <password> -i Crttable.sql
osql -U <account name> -P <password> -d <db name> -i Insdefsq.sql
osql -U <account name> -P <password> -d <db name> -i Insdefsi.sql
For example, if the account name is sa, the password is ProjectPW, the commands would be:
osql -U sa -P ProjectPW -i Crttable.sql
osql -U sa -P ProjectPW -d Project_CentralDB -i Insdefsq.sql
osql -U sa -P ProjectPW -d Project_CentralDB -i Insdefsi.sql
Note The parameter letters U, P, d, and i are case sensitive.
To create your own custom database and table installation for SQL Server and MSDE, use the SQL Server Enterprise Manager, as explained below:
Open Enterprise Manager for SQL Server.
Create a new database for ProjectCentral, for example, "Project_CentralDB", or other database name. Add a new logon user with the SQL Server Authentication option selected, and type a password to allow access to the database. Make the new database the default database for the user.
This new logon user should have the db_owner role in the Project Central database to allow the user to save Project Central tables and data in that database.
From Windows, go to the MS-DOS Prompt.
Change directories to the CD-ROM drive, and on the Microsoft Project CD, go to the folder \Pjcntrl\Isapi\1033 (or the appropriate folder for your language).
Copy the files, Crttable.sql, Insdefsq.sql, and Insdefsi.sql to c:\ProjectCentral. You need to modify Crttable.sql so that it references the database you just created by replacing the occurrence of Project_CentralDB with your database name.
Note Since you have now created a database in step 2 above, you need to comment out the following two lines in Crttable.sql:
CREATE DATABASE Project_CentralDB
go
After modifying Crttable.sql to reference your database, type the following commands to create tables in the database and to insert default records for the tables:
osql -U <account name> -P <password> -i Crttable.sql
osql -U <account name> -P <password> -d <db name> -i Insdefsq.sql
osql -U <account name> -P <password> -d <db name> -i Insdefsi.sql
NoteSQL Server Query Analyzer can be used instead of the Osql tool.
To create a custom database and table installation for Oracle:
Note You cannot create a default installation with Oracle. You can only create a custom installation.
Start the Oracle Security Manager.
On the General tab of the Create User dialog box, type a new name for the database.
In the Authentication list, select Password.
Under Tablespaces, select the tablespace you created.
Click the Roles/Privileges tab,
Select Connect and Resource in the Available list, and then click Roles in the Privilege Type list to grant the user CONNECT and RESOURCE roles.
Note Instead of granting the RESOURCE role to the new user, you can grant CREATE TABLE to the user instead.
Click the Quotas tab, and grant this user unlimited quotas in the Microsoft Project Central database.
Log on as the new user to perform the remaining actions.
From Windows, go to the MS-DOS Prompt.
Change directories to the CD-ROM drive, and on the Microsoft Project CD, go to the folder \Pjcntrl\Isapi\1033 (or the appropriate folder for your language).
Type the following commands to create tables in the database and to insert default records for the tables:
Crttblor.sql
Insdefor.sql
Insdefoi.sql
Note You need to install the Oracle Net8 Client on the Microsoft Project Central server before Microsoft Project Central will work correctly.
To create the Microsoft Project Central server:
After you have set up the database, you can run the custom installation of Microsoft Project Central server. You will need to specify the database server, database name, and a valid logon ID and password. For Oracle, you don't need to specify the database name.
After you have installed the Microsoft Project Central server, users can connect to it using the URL http://[servername]/ProjectCentral, where servername is the name of the Web server where you have installed Microsoft Project Central server, and where ProjectCentral is the outermost folder name (or virtual directory) specified in the installation path.
Notes
When the Microsoft Project Central server is installed, it creates a default user called Administrator. The password for this user is blank by default; therefore, one of the first things you should do after installation is log on to Microsoft Project Central (by going to the URL http://[server name]/ProjectCentral either on the server or on a client computer), log on as Administrator and change the password.
After you have installed the Microsoft Project Central server, most of the features can be used without further configuration. The administrator needs to tell project managers what the URL is for the Microsoft Project Central server so that this information can be entered into Microsoft Project.The following procedure describes how project managers can use Microsoft Project to connect their team to Microsoft Project Central after it has been installed and set up by the administrator.
By default, your password will be blank the first time you log on to Microsoft Project Central. You can set your password during your initial session.
Before team members can log on to Microsoft Project Central, their account information needs to be entered into Microsoft Project. Learn more about creating team members' accounts.
Note You need an account before you can work with Microsoft Project Central, but one is created for you automatically when you send a workgroup message. Perform this step only if you want to work with Microsoft Project Central before sending a workgroup message.
Workgroup members receive workgroup messages only in Microsoft Project Central, and must check the application regularly for new messages.
The manager tells the team members to enter the same URL into their browser to respond to workgroup messages from managers, respond to status report requests, and report their status on tasks. However, you can have Microsoft Project send an e-mail message to workgroup members (which includes a URL to Microsoft Project Central) whenever they receive a new workgroup message in Microsoft Project Central.
You can now assign team members to tasks and send them workgroup messages, such as TeamAssign, TeamStatus, and TeamUpdate. For more information on using the workgroup functionality of Microsoft Project, see online Help for Microsoft Project.
Notes
To add Microsoft Project Central accounts for team members
When a project manager sends workgroup messages to team members, Microsoft Project Central accounts are created automatically for them by default. To set up team members' Microsoft Project Central accounts to use their Windows user accounts, the project manager needs to add this information within Microsoft Project.
If you don’t know the resource’s Microsoft Windows user account, and you have already entered the URL for the Microsoft Project Central server in the Workgroup tab of the Options dialog box, click Windows Account to find the resource’s Windows user account through your e-mail address book.
If Windows user accounts are not specified in Microsoft Project, then resource names will be used to create Microsoft Project Central accounts. These accounts will be authenticated using Microsoft Project Central authentication; team members will see a logon screen when they go to the Microsoft Project Central site, and they will have to enter their resource names and passwords. By default, team members' passwords will be blank the first time they log on to Microsoft Project Central; they can set their password during their initial session.
Note In addition to creating accounts from within Microsoft Project, an administrator can create user accounts from within Microsoft Project Central. On the menu bar in Microsoft Project Central, point to Admin, click Users, and then click Add User.
If you will be using an e-mail workgroup system for some resources or if you selected the Send hyperlink in E-mail note check box in the Options dialog box, you may need to enter e-mail addresses for your resources. This procedure is necessary only if the resource’s e-mail address is not exactly the same as the resource’s name in Microsoft Project. For instance, if a resource’s name and e-mail address are both Chris, then you don’t need to perform this procedure. However, if the e-mail address is ChrisL instead of just Chris, then you need to add that resource’s e-mail address.
If the resource is located outside your organization, be sure to include the entire address. For example, if the resource’s
e-mail name is Chris and that resource can be reached through an Internet service provider called Provider (whose Web server is registered as provider.com), the following address would be correct:
Chris@provider.com
To administer Microsoft Project Central, you need to log on as a user with administrator privileges. You can start by logging on using the Administrator account, which Microsoft Project Central creates by default. You can then add additional administrators by pointing to Admin on the menu bar of Microsoft Project Central, and then clicking Users. Most administrative functions are explained in online Help for Microsoft Project Central. However, there are some administrative functions for which more detailed information is provided below.
To perform certain administrative tasks such as deleting items from the
Microsoft Project Central database, merging user accounts, and changing
nonworking
time categories, you must put the Microsoft Project Central server
in single-user mode. Single-user mode ensures that
users cannot connect to the Microsoft Project Central database and
change data while you are performing these administrative tasks, which could
corrupt the database.
Before you put the server in single-user mode, you should make sure that no users are currently connected to the database. A simple way to do this is to send e-mail to all your users and warn them to stop using the server (either as a browser or browser module client or from Microsoft Project) at a specified time. Then, to be sure that no users are connected, you can run the following database procedures sp_who. The procedure, sp_who, provides information about current Microsoft SQL Server users and processes. The result set returned from executing sp_who includes the following information:
Column | Data type | Description |
spid | smallint | The system process ID |
status | nchar(30) | The process status |
loginame | nchar(128) | The logon name associated with the particular process |
hostname | nchar(128) | The host or computer name for each process |
blk | char(5) | The system process ID for the blocking process, if one exists. Otherwise, this column is zero. |
dbname | nchar(128) | The database used by the process. |
cmd | nchar(16) | The SQL Server command (Transact-SQL statement, SQL Server internal engine process, and so on) executing for the process. |
Note If you are using Oracle, you can view user connections and processes by viewing the sessions in the Oracle Instance Manager.
To see the current processes, type the command osql -S<server> -U<userID> -P<password> -Q"sp_who" at the MS-DOS prompt. If you have chosen the default Install Now option and installed MSDE on the Microsoft Project Central server computer, then you can run this command from the MS-DOS prompt on the server. If you have chosen a custom install, then you should run this command on the computer that hosts the Microsoft Project Central database. After running the command, you will see several system processes listed. These are normal system processes that should be disregarded. Check the dbname, loginame, and hostname fields in the result set for Microsoft Project Central connections. If only one Microsoft Project Central user is listed (your administrator session), you can set the server to single-user mode.
To put the server in single-user mode, point to
the Admin on the menu bar, and then click Server Mode.
Important When you have finished your administrative tasks, reset the
server to Normal mode so that users can reconnect and start using it again.
Note Relatively few administrative tasks require the server to be in
single-user mode—deleting items from the database, merging user accounts,
changing nonworking time categories, and changing authentication options. The
user interface for these functions documents the fact that single-user mode is
required and does not allow you to perform the tasks until you have set the
server to single-user mode.
You can delete items from the Microsoft
Project Central database to free up space and remove data that is no longer
needed. You need to set the server to single-user mode before you can delete
information.
Caution Items removed from the database are permanently deleted from the database. However, they are not removed from the project files that are the original source of the data.
When project managers set up their resources in Microsoft Project and send them
workgroup messages, Microsoft Project Central uses either the
resource names or, if specified, the Windows user accounts for the resources to
create their Microsoft Project Central accounts.
If project managers do not use the same names for the resources in their projects, then a single resource could have multiple Microsoft Project Central accounts. For example, one project manager may call a resource Jane while another project manager could call her JaneD or specify her Windows user account, so this resource would have multiple Microsoft Project Central accounts.
You can consolidate or merge multiple accounts so that the user does not have to log on to Microsoft Project Central under several different names to receive all information. To merge accounts, point to Admin on the menu bar, click Users, and then click Merge User Accounts. However, you should only merge accounts that actually refer to the same person—you should not try to merge accounts for different people.
Notes
Ideally, all project managers in an organization should name resources in their projects using the same convention—either a full name or an e-mail alias, for example—to avoid creating multiple Microsoft Project Central accounts for the same person.
The Microsoft Project Central server can authenticate users using either Windows
NT Authentication using a Windows user account, or Microsoft Project Central
authentication using a logon ID and password, or both.
As an administrator, you can choose one of three authentication options.
While setting up their resources, there is a new Windows User Account field in Microsoft Project, which project managers can use to specify the Windows User Accounts for their resources. If a Windows User Account is specified for a resource, then when a workgroup message is sent to that resource, the Windows User Account is used to create the resource's account on Microsoft Project Central, and the resource gets authenticated via Windows NT Authentication. If no Windows User Account is specified, then by default, the resource name is used to create an account on Microsoft Project Central, and the resource gets authenticated via Microsoft Project Central authentication.
If a user's authentication method is Windows NT Authentication, then when the user goes to the Microsoft Project Central site, he or she will be authenticated automatically and taken to the Microsoft Project Central Home page. If a user's authentication method is Microsoft Project Central authentication, then the user will see a logon page when connecting to the Microsoft Project Central site and will have to type or select a user name and password.
Note If a project manager sends workgroup messages to his or her resources without specifying their Windows user accounts, then by default the resources will get accounts based on their resource names, with blank passwords. They can change their passwords when they log on to Microsoft Project Central.
While setting up their resources, there is a new Windows User Account field in Microsoft Project that project managers can use to specify the Windows user accounts for their resources. If you choose the Windows NT Authentication only option, then all project managers must specify a Windows user account for all their resources before sending workgroup messages.
By default, resources' accounts will be based on their resource names with blank passwords. They can change their passwords when they log on to Microsoft Project Central.
Note You must be in single-user mode to change authentication
types. Changing the authentication method to Windows NT Authentication only will
inactivate all user accounts using Microsoft Project Central authentication and
vice versa. If you change authentication types again, the original accounts will
be not be reactivated automatically.
By default, when Microsoft Project Central attempts to authenticate a user with Windows NT Authentication, it assumes that the user is using a computer from which they have already logged on to the network, using their Windows user account. However, this may not always be the case. For example, a user may want to check Microsoft Project Central information using someone else's computer, or using a common computer that is shared by several people and from which the user has not already logged on with his or her Windows user account.
In this case, when the user goes to a Microsoft Project Central site, the Logon page will open instead of the Home page. The user must then click the Log on using your Microsoft Windows user account link on the left side of the page. After entering his or her Windows user account information, the user is authenticated using Windows NT authentication, and is then taken to the Home page.
However, to enable this procedure, the administrator must configure the Microsoft Project Central server. To allow users to use the Log on using your Microsoft Windows user account link on the Logon page, the administrator must give users "log on locally" rights on the Microsoft Project Central server. This can be done using Windows NT administration tools on the server computer.
For example, one way to do this is to add the user or users to the Guests group on the Microsoft Project Central server computer, which by default has "log on locally" rights. On Windows 2000, right- click My Computer from the desktop, and then click Manage. Under Local Users and Groups, select Groups, and then double-click Guest in the right pane. You can then add the user or users you want as Guests. You can also add entire departments or groups of users if they have been set up in your Windows NT domain. On Windows NT 4.0, this can be done using User Manager. For more information on the Windows NT administration tools, see your Windows NT documentation.
Once you have installed Microsoft Project Central server, team members can start using most features without further configuration. However, for Microsoft Project Central views, which are accessed from the Views menu, an administrator needs to configure the server to display views of different projects.
The Microsoft Project Central views feature allows users to see information about a collection of projects, see the details of an individual project, or look at assignments made through Microsoft Project Central. Views make it possible for your executives to see high-level information or team members to see more complete information about the projects they are working on. However, there is some configuration work that an administrator needs to do in order to get the full functionality for views.
Microsoft Project Central can display views of three kinds of information:
Project managers can publish information about their projects to the Microsoft Project Central server by clicking the Tools menu within Microsoft Project, pointing to Workgroup, and then clicking Update Project to Web Server. Updated information about the project summary task will be sent to the Microsoft Project Central server database, so that it becomes visible through a project portfolio view. Information about the individual tasks and resources in a project is not stored in the Microsoft Project Central server database and is not visible through a portfolio view; this information remains in the project file or in the project database and can be accessed through a project view as described below.
Views allow your team members to see only selected project information, based on fields and filters. Microsoft Project Central includes predefined views that allow you to see different aspects of project information. You can also create and define your own views to see a portfolio of projects, to view details about an individual project, or to look at Microsoft Project Central assignment information. Only a person logged on as an administrator can perform the following actions.
You can also add ASP pages (active server pages), data access pages, and HTML files to specific folders on the Microsoft Project Central server to make them available to Microsoft Project Central as additional views. On the server, add these files to the respective folders under \views\portfolio\, \views\project\, or \views\assignment\. To make these files available when setting up views and permissions, add these files to the table of views by clicking Get Additional Views on the Specify Views page. To make these new views available to users, select the view in the Specify Views page, click Modify View, and then scroll down the page to specify a category or categories of users who can see the view.
Note HTML files should be added to the \views\portfolio\ folder.
After views have been created, you need to specify which views a team member can see by assigning the views to a category. A category is a mapping of users to projects and views with which they can see project information. There are four pre-defined categories: Team Member, Project Manager, Resource Manager, and Executive. By default, all users defined as resources in Project Central belong to the Team Member category, and users defined as project managers belong to the Project Manager category. By default, users in these categories can see high-level information in a portfolio view for all projects they are working on. The Project Manager and Team Member categories cannot be deleted. The Resource Manager and Executive categories do not contain any users by default. You can add users to these categories manually either in the Specify Categories page or in the User Permissions for Views page.
Note You can also create new categories by clicking New Category, and then assign users to the category and specify the types of views that users in this category can use.
If you have not already done so, you need to set permissions to control which assignments can be seen by users in a category. Until you set permissions, users can only see their own assignment data in Microsoft Project Central assignment views.
To set permissions:
Examples
The resource managers in your company want to view resource assignments across projects. Assign them to the Resource Manager category in the Specify Categories page, and then specify which resources' assignments they can see in the User Permissions for Views page.Users who are in the Team Member and Project Manager categories can by default see only those projects they are working on. If there are some high visibility projects that you want all project managers to see, then you can add these specific projects to the Project Manager category.
Your company has contracted with some external vendors who need to view certain project information. Create a new category for these vendors, allow them to see only certain projects, and specify the views with which they can see the information in these projects. You may want to make sure that these views do not expose sensitive information like costs.
In your company there may be a special view that executives will want to use to see top level information across all projects. Create a new portfolio view to display this information and add it to the Executive category.
Microsoft Project includes the predefined project view, Tasks Summary, but you want it to show cost information. Modify this view to include cost fields, such as Actual Cost or Baseline Cost.
Sarah joins your company as a new resource manager. You want to assign her to the Resource Manager category and allow her to view resource assignments for all resources whom she supervises. You can do this is in the User Permissions for Views page.Bob gets promoted to an executive level, but he currently belongs to the Project Manager category. Modify his permissions in the Users Permissions for Views page and add him to the Executive category as well.
Using project views, the Microsoft Project Central server can display information from projects whether they are stored in a file or in a database; however, the following conditions must apply:
For projects stored in files:
The project file must be stored on a network share. While saving the project to a network share, the project manager must use a UNC path, for example \\servername\sharename, and not a drive letter. The project manager must then update the Microsoft Project Central server by clicking the Tools menu within Microsoft Project, pointing to Workgroup, and then clicking Update Project to Web Server.
The Microsoft Project Central server must be able to access the project file on the network share.
The first step in making project files available to Microsoft Project Central is to set the Anonymous account for Internet Information Server to be a domain account that has access to the network share.
If you are using Microsoft Internet Information Server 5.0, make sure that the Allow IIS To Control Password check box is not selected. (If you are using Microsoft Internet Information Server 4.0, this check box is labeled Enable Automatic Password Synchronization.)
Note If you specify an account with an expiring password, make sure you change the password manually every time your domain password changes.
The domain account you specify above should have access to the network share where the project file is stored.
In addition to the Default Web Site, you must set anonymous access for the Microsoft Project Central virtual directory.
Finally, after you have changed the ProjectCentral virtual directory to allow anonymous access, you need to change the security permissions on the Default.asp file for Windows NT Authentication to work.When you change the ProjectCentral virtual directory to allow anonymous access, you may get a dialog box asking if you want to override the security permissions for the files Isapi\Pjdbcomm.dll and Logon\Basicauth.asp. Do not select any of these files in the dialog box, and then click OK.
For projects stored in a database:
If your organization's projects are stored in a SQL Server, Microsoft Access, MSDE, or Oracle database, you can allow users to look at information through Microsoft Project Central views without allowing access to the database itself.
The Data Sources for Views page lists all the DSNs that project managers use to store their projects.
For each DSN, specify a user ID and password: Select the DSN, and then click Modify Data Source. Below the table, type a user ID and password. This user ID should have access to the projects stored in the database using that DSN name.
The Data Sources for Views page in Microsoft Project Central lists all the DSNs used by projects in Microsoft Project Central. For each DSN name that is used to store projects, you must create the same-named DSN on the Microsoft Project Central server, pointing to the same database using the appropriate user ID and password. You can create DSNs using the ODBC Data Sources Administrator program in Control Panel on the server.
Your company stores all projects in a central database. You need to make sure that all the DSNs that project managers are using to save to this database also exist on Microsoft Project Central server. On the Data Sources for Views page, you must specify a user ID and password for each DSN. This user ID must have access to the projects saved using the DSN. This will allow users to use Microsoft Project Central views to see the information you have given them access to even though they may not have direct access to the database. Learn more about configuring the server so that team members can see information in project views.
Notes
For project views to display information from projects stored in a database, all project managers must save their projects to the database in a consistent manner. There are three ways to do this.
- Create a new database user ID and password.
- To see all projects in tables belonging to different table owners, a view must be created for each project table (e.g. MSP_PROJECTS, MSP_TASKS, et al) which performs a UNION ALL of all owners' instances of the table. To allow Microsoft Project to differentiate between projects in different table owner's tables that happen to have identical project IDs, the project IDs across all owners' tables must be made unique. In the following example, the value of the column PROJ_ID in user2's table MSP_TEXT_FIELDS is incremented by 1000. By incrementing the value of PROJ_ID in all of user2's tables, Microsoft Project will perceive projects in user2's tables as different projects. Project information retrieved through these views cannot be updated.
create view MSP_TEXT_FIELDS as
select PROJ_ID,
TEXT_CATEGORY,
TEXT_REF_UID,
TEXT_FIELD_ID,
TEXT_VALUE
from user1.MSP_TEXT_FIELDS
union all
select PROJ_ID + 1000,
TEXT_CATEGORY,
TEXT_REF_UID,
TEXT_FIELD_ID,
TEXT_VALUE
from user2.MSP_TEXT_FIELDSIf a third owner's tables were added to the view, the project IDs in his or her tables could be incremented by 2000. Project IDs in all twenty one tables belonging to each table owner must be made unique in the same way.
The Microsoft Project Central administrator must now create the same-named DSN on the Microsoft Project Central server that project managers are using to save their projects. Then in the Data Sources for Views page, the administrator should specify the database user ID and password created in Step 1 above for this DSN. This will allow Microsoft Project Central to access projects belonging to different table owners in the database using a single DSN and a single database User ID.
You can use data access pages as additional views to use within Microsoft Project Central. On the server, add these files to the \datapage folder under \views\project\. For more information on creating data access page reports using data from Microsoft Project, see the file OLE_DB.htm on the Microsoft Project CD at \Pfiles\Msoffice\Office\1033\OLE_DB.htm (This folder, 1033, contains the files for the English version. Files for other languages are contained in the folder that corresponds to the locale ID [LCID] for that language.)
To make data access pages available for viewing in Microsoft Project Central, then you must change the HTML page to include specific lines of HTML code, as described in the following procedure.
If you want to use data access pages, you will needed Microsoft Internet Explorer 5.0 or later, and in addition an Office 2000 license.
Note To use views based upon data access pages, you need to use the password for the DSN that the project manager used to save the project. Users will be prompted for the password when they attempt to view the data page. The password is not strongly encrypted; therefore, if there are security concerns within your organization, you should not use data access pages against project stored in a database.
Note The page may not work as a standalone page once this change has been made. You may want to make a copy of the original page for use as a standalone page.
<!--#include file="../../../Library/sig.asp" -->
<% // // Begin Project Central section // %> <!-- #include file="../../../Includes/build.inc" --> <!-- #include file="../../../Library/Constants.asp" --> <!-- #include file="../../../Library/datetime.asp" --> <!-- #include file="../../../Library/PJQuery.asp" --> <!-- #include file="../../../Library/Application.asp" --> <!-- #include file="../../../Library/LocalizedStrings.asp" --> <!-- #include file="../../../Library/PJSession.asp" --> <!-- #include file="../../../Library/User.asp" -->
Note To copy this code into your HTML editor without retyping it, copy and then paste the code into a text editor, such as Notepad. Then copy and paste the code again from Notepad into your HTML editor at the point where you want the code to appear.<% var oPJSession = new PJSession(); var oUser = new User; oUser.Authenticate(true); if (typeof(oPJSession.oUser.nUserID) == "undefined" || oPJSession.oUser.nUserID == null) Response.Redirect(const_sHomePage); var nProjectID = Request.QueryString("_projectID").Item; if (typeof(nProjectID) == "undefined") Response.Redirect("..\\..\\PortfolioView.asp"); var oPJQuery = new PJQuery; oPJQuery.Connect(); var sProjectName = ""; var sDataSource = "&quot;&quot;"; var sUserID = "&quot;&quot;"; var sPassword = "&quot;&quot;"; var rsProject = oPJQuery.OpenRecordset(const_PjQuery_GetNamePathFromFileID,nProjectID,oPJSession.oUser.nUserID); if (!rsProject.EOF()) { if (rsProject.GetColumn(const_dbWDSN_ID) > 0) { sProjectName = rsProject.GetColumn(const_dbPROJ_NAME); sDataSource = rsProject.GetColumn(const_dbWDSN_NAME); sUserID = rsProject.GetColumn(const_dbWDSN_LOGIN_ID); } else { sProjectName = rsProject.GetColumn(const_dbWPATH); } } rsProject.Close(); if (sProjectName == "" || sProjectName == null) Response.Redirect("..\\..\\PortfolioView.asp"); %> <% // // End Project Central section // %>
<a:ConnectionString>Provider=Microsoft.Project.OLEDB.9.0;User ID=<%=sUserID%>
;Data Source=<%=sDataSource%>;Project Name=<%=sProjectName%>
;Initial Catalog=<%=sProjectName%>;Persist Security Info=False</a:ConnectionString>
Team members will now be able to view the data access page as a portfolio view by pointing to Views on the menu bar, clicking View Your Portfolio, selecting the project the data access page points to, and then selecting this view.
Microsoft Project Central server setup will install a Web site on a Web server, and have the site point to a database. If you need to install another Web site on the same server pointing to a different database, you'll can add the new Web site using Internet Service Manager, and add the necessary registry keys for that site and database servers. A tool to automatically create another Web site is available in the Toolbox on the Microsoft Project Resource Kit site.
\Default Web Site\ProjectCentral\Custerror\401-1.html and \Default Web
Site\ProjectCentral\Custerror\401-2.html.
Note Make sure you are browsing for .html files, and not
just .htm files.
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\9.0\MS Project\WebClient Server\Projectcentralnew] "Provider"="sqloledb" "ConnectString"="Data Source=SQLServerMachineName;lnitial Catalog=SQLServerDatabaseName" "UserName"="username" "Password"="Password" "QueryFileStd"="\\ProjectCentral\\isapi\\QueryLibStd.sql" "QueryFileExt"="\\ProjectCentral\\isapi\\QueryLibSQL.sql"
If you're connecting to an Oracle database, add the following keys:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\9.0\MS Project\WebClient Server\Projectcentralnew]
"Provider"="msdaora"
"ConnectString"="Data Source=OracleMachineName;"
"UserName"="username"
"Password"="password"
"QueryFileStd"="\\ProjectCentral\\isapi\\QueryLibStd.sql"
"QueryFileExt"="\\ProjectCentral\\isapi\\QueryLibOracle.sql"
If you are using Microsoft NT server 5.0 or later, you only need to restart Internet Services Manager.
The Browser Module for Microsoft Project Central is for those who do not wish to use Microsoft Internet Explorer as their browser client. The module uses the Microsoft Internet Explorer functionality in Windows, but does not register itself as a browser. It can only view a Microsoft Project Central site. To set up the Browser Module for Microsoft Project Central:
It may be easier to install the Browser Module for Microsoft Project Central using a network server by creating an administrative installation point. The administrative installation point is a server share that contains all of the setup files for the Browser Module for Microsoft Project Central. Users connect to this share and run setup.
To do an administrative setup:
and on the Microsoft Project CD, go to the folder \Pjcntrl\Isapi\1033 (or the appropriate folder for your language).
[CD-ROM]drive:\setupclt.exe /a
Note Make sure users have access to the share.
The default connection state for the Browser Module is LAN without proxy server. If you need to use a proxy server to communicate with your Web server, do the following:
The following are miscellaneous issues that are not covered elsewhere in this file.
You can also select the Trusted Sites icon in the Security tab of the Internet Options dialog box for Microsoft Internet Explorer 5.0, and then add the Microsoft Project Central site to the list of trusted sites. Select the Trusted Sites icon, click Sites, and then add the Site in the Trusted Sites dialog box. Clear the Require server verification for all sites in this zone check box. If you are using Microsoft Internet 4.01, select Trusted Internet zone in the zone box of the Security tab, click Add Sites, and then add the Web site in the Trusted Sites Zone dialog box. Clear the Require server verification for all sites in this zone check box.
In addition, you need to make the following changes to the Microsoft Project Central virtual directory:
- Using the Internet Service Manager, expand the Default Web Site folder, which is the default server root, right-click the Microsoft Project Central virtual directory, and then click Properties.
- Click the Directory Security tab, and then under Anonymous Access and Authentication Control, click Edit.
- Select the Anonymous Access check box, and then click Edit for Account used for Anonymous Access.
- make sure the user name is IUSR_[machine name].
- If you are using Microsoft Internet Information Server 5.0, make sure that the Allow IIS To Control Password check box is selected. (If you are using Microsoft Internet Information Server 4.0, this check box is labeled Enable Automatic Password Synchronization.)
If you are prompted to change settings for certain files so they inherit the settings you've made above, select only pjdbcomm.dll, and then click OK.
If your organization has an extranet that allows allows external users access to some or all parts of your network, then Microsoft Project Central will work in this environment.
Microsoft Project central views can be seen across the internet. However, projects can only be updated from within the intranet. These projects need to be saved on a UNC server or database within the intranet that the server has access to.
If you want to use the internet, it is best to select Microsoft Project Central Authentication when setting up your authentication method. However, you can use Windows NT Authentication provided Windows user accounts are first created locally on the server in the form server name\user name. Then, when users log on, they would select the Log on using your Microsoft Windows user account link from the logon page. They would then get the basic authentication dialog box in which they enter their authentication credentials in the form server name\user name.
Warning If you log on this way, your Microsoft Windows user account is passed via basic authentication which does not use strong encryption.
A project manager cannot use a Windows user account to identify himself while communicating with a Microsoft Project Central server over the internet; using Windows user accounts from within Microsoft Project requires that the project manager's current network logon belongs to the domain that the Microsoft Project Central Server is a part of, so it can be recognized and validated by the Project Central server.
Installing another language version To install another language version of Microsoft Project Central, do not use the Microsoft Project Central setup program. If you attempt to run the installation program twice, you will not be able to install a second copy of Microsoft Project Central. Use the Microsoft Project Central Language Packs to install different language versions of Microsoft Project Central. These can be found in the Toolbox on the Microsoft Project Resource Kit Web Site.
Using Secured Sockets Layer Secured Sockets Layer (SSL) cannot be used with Microsoft Project Central server.
Domain password no longer works When setting up Microsoft Project Central to display information from shared files or database on a network domain that uses expiring passwords, make sure that you change your password manually every time your domain password changes.