TechNet Home > Common IT Scenarios > Information Worker Productivity

Clinical Trial Initiation Reference Implementation for Microsoft Office 2003 Guide

Chapter Three – Installing and Configuring Your Development Environment

Published: December 14, 2004

This chapter describes the process for installing and configuring the Clinical Trial Initiation reference implementation for Microsoft® Office 2003 in your development environment. This chapter covers the following topics:

•	Software and hardware prerequisites
•	Installing the required software on the server
•	Installing and configuring the reference implementation
•	Using the reference implementation
•	Uninstalling the reference implementation

This chapter assumes you will be performing a clean installation of all required software. You need only one computer to install and run all of the reference implementation's features. This chapter describes how to install and configure all of the components on the same computer, including client and server components. You can also install client components on a separate computer; however, these instructions focus on a single-computer installation.

These instructions are intended for installing the reference implementation on a development computer only. Do not use this installation method when deploying a solution based on this reference implementation in your production environment. Additionally, it is not recommended that you install the development tools on production servers. Installing the development tools in a production environment could increase security risks. For information about security considerations in a production environment, see Chapter 6, Security and Deployment Considerations.

Before you start the installation, review the Readme.htm file for the most current information.

Note: The reference implementation is configured to install on the C: drive; therefore, all of the procedures in this chapter reference the C: drive. You can install the reference implementation and the required software on a different drive letter as long as you update the reference implementation setup script (CTI-Install_All.cmd) to reflect the drive letter you want to use. Updating the setup script is described in the "Configuring the Reference Implementation Setup Script" section later in this chapter.

Hardware and Software Prerequisites

The minimum hardware requirements for the reference implementation include the following:

•	550 megahertz (MHz) or higher Intel Pentium-compatible CPU
•	256 megabytes (MB) of RAM minimum, 512 MB recommended
•	6 gigabytes (GB) available hard disk space formatted NTFS for server applications and an additional 100 MB for the reference implementation
•	An Internet connection (only required for downloading software updates, patches, etc., from Microsoft.com)

The following software is required and must be installed on the computer as described in this chapter prior to installing the reference implementation.

Note: Setup and configuration of this reference implementation requires that all the components be installed on one physical computer. You must be a local system administrator on this computer.

The prerequisite software that is required to run the reference implementation is listed in the following list. Detailed instructions for installing this software on the developer computer are provided in the subsequent sections.

•	Microsoft Windows Server™ 2003 – Standard or Enterprise Edition
•	Microsoft SQL Server™ 2000a with Service Pack 3a (SP3a) or later – Developer, Standard, or Enterprise Edition
•	Internet Information Services (IIS) 6.0
•	Microsoft Windows® SharePoint® Services 2.0
•	Microsoft Visual Studio® .NET 2003 Enterprise Architect, Enterprise Developer, Special Edition, or Professional Edition
•	Microsoft Information Bridge Framework 1.0 (Server and Client)
•	Microsoft Office 2003 Professional Edition
•	Microsoft Internet Explorer 6.0 SP1
•	All recommended critical updates from the Windows Update Web site at: http://go.microsoft.com/fwlink/?LinkId=37314

Top of page

Installing the Required Software on the Development Computer

This section describes how to install and configure the required software in the order listed in Table 3.1. The instructions describe where you can use default configurations and where you will need to customize the setup. Also included is information about setting permissions for products during initial installation, for example, the specific permissions you must set in SQL Server.

Table 3.1: Software Installation Order

Order	Product
1	Microsoft Windows Server 2003
2	Microsoft SQL Server 2000a Database Server
3	Microsoft SQL Server 2000 SP3a
4	Microsoft Windows SharePoint Services v2.0
5	Microsoft Visual Studio® .NET 2003
6	Microsoft Information Bridge Framework 1.0 Server
7	Microsoft Office 2003 Professional Edition
8	Microsoft Information Bridge Framework 1.0 Client

These instructions assume that you are performing a clean installation of all required software and that you are installing all software on the C: drive. Throughout this procedure, accept default values except where specified. Record the account and site names you assign during installation in Table 3.12 in the "Installation Reference Worksheet" section later in this chapter.

These instructions refer to your computer name as <computername> and the domain as <domainname>.

Installing and Configuring Windows Server 2003

This section describes how to perform the following steps:

Note: The following text is only a conceptual overview. Use the detailed steps following this overview to complete your prerequisite installation tasks.

•

Install Windows Server 2003 – Follow your standard process for installing Windows Server 2003 and joining a domain.

•

Disable the Internet Explorer Enhanced Security Configuration – Using Internet Explorer Enhanced Security Configuration on a Web server running Microsoft Windows SharePoint Services prevents some code that is necessary for viewing site pages or HTML administration pages from running. Remote users with proper access rights can still view the pages correctly, but a user running Internet Explorer on the server computer is unable to view or manage the site. For more information, see Internet Explorer Enhanced Security and Windows SharePoint Services product documentation at:

http://go.microsoft.com/fwlink/?LinkId=37315

•

Install critical updates – It is recommended that you install all critical updates from Windows Update:

http://go.microsoft.com/fwlink/?LinkId=37314

•

Add the Application Server role – The Windows Server 2003 family includes core technology with the Application Server Role that provides key infrastructure and services to applications hosted on a system. For more information, see product documentation for configuring an application server at:

http://go.microsoft.com/fwlink/?LinkId=37316

•

Add the SMTP service to the computer if an external SMTP server is not available – If you use an external SMTP service to handle e-mail messages, you will reference that server later when you configure the reference implementation setup script. However, if no external SMTP server is available, you must add the SMTP service to your development computer so that SharePoint notifications can be sent to users in e-mail.

•

Create Service Accounts – You must create three new service accounts on your server computer to use for the various services and software programs that you install and configure for this reference implementation. These service accounts are listed in Table 3.2. Create these three local accounts with low-level privileges; it is not recommended that you grant Administrator rights to any of these accounts. Later in this chapter, there are specific instructions for adding these accounts to local computer groups to grant them necessary privileges. For now, creating the accounts and noting their names and passwords is sufficient.

Note:

•	For this reference implementation, you must install Windows on a partition that is formatted using NTFS.
•	These instructions do not support upgrading from Windows 2000 Server.
•	These instructions assume that you are installing Windows Server 2003 on the C: drive

To install Windows Server 2003

Run Setup from the Windows Server 2003 CD or from the network and follow your standard installation process.

During or after Windows Setup, connect the computer to an existing domain. To join a domain after installation, do the following:

1.	Right-click My Computer, and then click Properties.
2.	Click the Computer Name tab, and then click Change.
3.	Click Domain and type the domain name.

Log on to the server using the Administrator account you created during installation.

To disable the Internet Explorer Enhanced Security Configuration

1.	Click Start, point to Control Panel, and then click Add or Remove Programs.
2.	Click Add/Remove Windows Components.
3.	Clear the Internet Explorer Enhanced Security Configuration check box.
4.	Click Next, and then click Finish.

To install critical updates

1.	In Internet Explorer, click Tools, and then click Windows Update.
2.	Scan for updates and install all critical updates. Because some updates must be installed separately from others, you may have to continue scanning your computer for updates after each reboot until all updates have been installed.

To add the Application Server role

1.	Click Start, point to All Programs, point to Administrative Tools, and then click Manage Your Server.
2.	Click Add or remove a role. This starts the Configure Your Server Wizard. Click Next.
3.	On the Server Role page, select Application Server (IIS, ASP.NET), and then click Next.
4.	There are two check boxes on the Application Server Options page. Verify that the FrontPage® Server Extensions check box is cleared, and then select Enable ASP .NET. Click Next.
5.	Continue clicking Next, and then click Finish to complete the wizard.
6.	To check your server role configuration, on the Manage Your Server screen, click Add or remove a role and verify that the Application Server role is the only active role, as shown in Figure 3.1. If you need to remove a role, click the role, and then click Next to start the Configure Your Server Wizard. Figure 3.1 The Configure Your Server Wizard showing the Application server role See full-sized image

To add the SMTP service to the computer if an external SMTP server is not available

1.	Click Start, point to Control Panel, and then click Add or Remove Programs.
2.	Click Add/Remove Windows Components.
3.	Click Application Server, and then click Details.
4.	Click Internet Information Services (IIS), and then click Details.
5.	Select the SMTP Service check box.
6.	Click OK to close the Internet Information Services (IIS) page.
7.	Click OK to close the Application Server page.
8.	Click Next.
9.	Click Start, point to All Programs, point to Administrative Tools, and then click Internet Information Services (IIS) Manager.
10.	Expand the local computer node.
11.	Right-click the Default SMTP Virtual Server, and then click Properties.
12.	Click the Access tab, and then click Authentication. Verify that the Anonymous Access check box is selected, and then close the Authentication dialog box.
13.	Click Relay, and then click the All except the list below radio button.
14.	Clear the Allow all computers which successfully authenticate to relay, regardless of the list above check box, and then click OK to close the Relay dialog box.
15.	Click the Delivery tab, and then click Advanced.
16.	In the Smart Host text box, enter the server name for your SMTP server, and then click OK to close the Advanced dialog box. Note: If you do not have access to a SMTP server on your network, you can leave the default value for the Smart Host text box. Mail will not be routed from your server, but the features of the reference implementation will work correctly.
17.	Click OK to close the Default SMTP Virtual Server Properties dialog box.

To create service accounts

Click Start, right-click My Computer, and then click Manage.

Expand Local Users and Groups.

Right-click the Users folder, and then click New User.

In the New User dialog box, repeat the following steps for each account (as listed in Table 3.2):

1.	Create a new user making sure you use a strong password.
2.	Clear the User must change password at next logon check box, and then select the User cannot change password check box and the Password never expires check box.
3.	Click Create.

After you have added all three accounts, click Close.

Table 3.2 Service Accounts

Type of Service Account	Suggested User Name	Referred to in this document as:
SQL Server Service Account	SQLService	Your SQL Server service account
Application Pool Service Account	CTIAppService	Your application pool service account
SharePoint Administration Site Application Pool Account	WSSAdmin	Your Windows SharePoint Services administrative site service account

To remove privileges for the service accounts

Remove the new account from the Users group because this group is granted liberal access to the computer:

1.	Click the Groups folder.
2.	In the right pane, double-click Users.
3.	Under Members, click one of the new user accounts, and then click Remove.
4.	Repeat step 3 for each of the three new accounts.
5.	Click OK.

Installing SQL Server

To meet the pre-installation requirement of running SQL Server, you must install the latest versions of SQL Server 2000a. All configuration of SQL Server occurs while you are installing it. Following the installation of SQL Server, you must verify that it is running before continuing to install Windows SharePoint Services.

Microsoft has replaced all editions of SQL Server 2000 with SQL Server 2000 Release A. The update helps to protect a SQL Server 2000 installation because it includes the Slammer security patch. Because Microsoft recommends that you replace your current SQL Server 2000 media with SQL Server 2000 Release A, all instructions in this chapter refer to Release A as SQL Server 2000a. SQL Server 2000a only includes the Slammer worm security patch. It does not include any fixes that have been made to SQL Server 2000 since its original release, so you must still install the latest service pack after installing SQL Server 2000a.

To order SQL Server 2000a replacement CDs for SQL Server 2000, see the Microsoft Knowledge Base Article 826818 "SQL Server 2000 Release A replaces SQL Server 2000" at:

http://go.microsoft.com/fwlink/?LinkId=37318

SQL Server 2000a editions include the Enterprise, Standard, Personal, Developer, and Evaluation editions. You must install the Enterprise, Standard, Evaluation, or Developer edition. SQL Server Enterprise Evaluation Edition is for evaluation purposes only and you can use it for up to 120 days. The Personal Edition of SQL Server creates a personal database on your client computer and typically only installs the client tools and client connectivity components along with the database engine.

SQL Server SP3a must be installed and is available on a SQL Server 2000 Service Pack 3a CD-ROM or in three self-extracting files that you can download from the Microsoft SQL Server Downloads Web site. If you have an SP3a CD, you can install SP3a directly from the CD. The instructions in this section explain how to install SP3 by downloading it from the Internet. For Database Components SP3a and Analysis Services SP3a, the setup process is the same for both the CD-ROM and the extracted files.

For more information, see the SQL Server Books Online Overview of Installing SQL Server 2000 at:

http://go.microsoft.com/fwlink/?LinkId=37319

This section details the following steps:

•	Installing SQL Server 2000a
•	Installing SQL Server Service Pack 3a (SP3a)
•	Verifying that the SQL Server service is running

To install SQL Server 2000a

1.	Run Setup from the CD or network.
2.	On the Microsoft SQL Server 2000a screen, click the SQL Server 2000 Components link.
3.	Click Install Database Server. When you see a message indicating that SQL Server 2000 SP2 and earlier is not supported, click Continue. You will upgrade SQL Server to SP3 in a later step.
4.	Accept the default values by clicking Next until you reach the Service Accounts page.
5.	On the Services Accounts page, select Use a Domain User account. For Username, enter the SQL service account you created earlier (for example, SQLService). For Domain, enter the <computername>. Do not choose LocalSystem. Click Next.
6.	Select Windows Authentication Mode and click Next.
7.	Click Next until the Choose Licensing Mode page opens.
8.	Select the Per Seat or Processor License for licensing mode in accordance with your licensing agreement. Click Continue. The installation wizard now installs and configures SQL Server.
9.	Click Finish to complete the installation.

To install SQL Server SP3a

1.	Go to the SQL Server 2000 SP3a download page at: http://go.microsoft.com/fwlink/?LinkId=35721
2.	Run sql2ksp3.exe to extract SQL Server SP3 files to your hard disk.
3.	In Windows Explorer, navigate to the sql2ksp3 folder on the C: drive.
4.	Double-click setup.bat to start the installation.
5.	Click Next and accept defaults values until you reach the SA Password Warning page. Select I do not want a blank password, set password and enter a valid password as your SA password. Click Next.
6.	On the Backward Compatibility Checklist page, select Upgrade Microsoft Search and apply SQL Server 2000 SP3.
7.	Click Continue.
8.	Optionally, select Automatically send fatal error reports to Microsoft, and then click OK. Click Next to install the service pack.

To verify that the SQL Server service is running

1.	Click Start, point to All Programs, point to Microsoft SQL Server, and then click Service Manager. The SQL Server Service Manager dialog box opens.
2.	In the Server list, select your computer.
3.	In the Services list, select SQL Server and verify that the SQL Server service is running. The service is running if the Start/Continue button in the dialog box is unavailable. A message at the bottom of the dialog box also states that the MSSQLServer service is running.
4.	If the service is not running, click Start/Continue to start the service.

Installing and Configuring Windows SharePoint Services

This section details the following steps for installing and configuring Windows SharePoint Services:

•	Bypassing the Proxy Server – If you are installing the new server in an environment that uses a proxy server, you must enable a bypass for the proxy server to prevent errors when viewing locally hosted pages on Windows SharePoint Services.
•	Configuring SQL Server 2000a to work with Windows SharePoint Services – You will need to create a new SQL Server logon ID for the Windows SharePoint Services administrative site service account you created earlier and grant this account the appropriate server roles so that Windows SharePoint Services can connect to your SQL Server database. These server roles will be required later in the setup and configuration of Windows SharePoint Services.
•	Installing Windows SharePoint Services – By default, when you install Windows SharePoint Services, the setup program installs Microsoft SQL Server 2000 Desktop Engine (Windows) (WMSDE). To use Windows SharePoint Services with a remote SQL Server, you must install Windows SharePoint Services without installing WMSDE. SQL Server is treated as a remote installation even if it is installed on the same physical computer.
•	Configuring the virtual server and connecting to your SQL Server database – After Windows SharePoint Services has been installed, configure the administrative virtual server—including specifying an application pool to use for the virtual server processes—and connect to SQL Server.
•	Extending the virtual server with Windows SharePoint Services – After you set up the connection to SQL Server, you are ready to extend the virtual server with Windows SharePoint Services. When you do this, Windows SharePoint Services is applied to a virtual server and a top-level Web site is created.

To bypass the proxy server

1.	Open Internet Explorer.
2.	Click Tools, and then click Internet Options.
3.	Click the Connections tab, and then click LAN Settings.
4.	If Use a Proxy Server for your LAN is selected, select the Bypass proxy server for local addresses check box and then click OK twice to complete this task.

To configure SQL Server to work with Windows SharePoint Services

1.	Click Start, point to All Programs, point to Microsoft SQL Server, and then click Enterprise Manager.
2.	In Enterprise Manager, expand the Microsoft SQL Servers node.
3.	Expand the SQL Server Group node.
4.	Expand the SQL Server name node, named (local) (WindowsNT) by default.
5.	Expand the Security node.
6.	Right-click Logins, and then select New Login.
7.	In the Name field, enter or select your Windows SharePoint Services administrative site service account. Be sure to enter both the computer name and the account (for example, <computername>\WSSAdmin)
8.	Click the Server Roles tab.
9.	In the Server Role list, select Security Administrators and Database Creators, and then click OK to close the dialog box.
10.	Close the SQL Server Enterprise Manager.

To install Windows SharePoint Services without installing WMSDE

1.	Go to the Microsoft Windows SharePoint Services Web site at: http://go.microsoft.com/fwlink/?LinkId=37320
2.	Under Download, click Windows SharePoint Services.
3.	Download STSV2.exe to extract the installation files to your hard disk.
4.	On the End-User License Agreement page, click I accept the terms in the License Agreement, and then click Next.
5.	On the Type of Installation page, click Server Farm, and then click Next.
6.	On the Summary page, verify that only Microsoft Windows SharePoint Services will be installed, and then click Install.
7.	When installation is complete, the Windows SharePoint Services Configure Administrative Virtual Server page opens.

To configure the administrative virtual server and connect to the SQL Server database

On the Configure Administrative Virtual Server page that opens automatically after installation, in the Application Pool section, select Create a new application pool, and then enter a name for it in the Application pool name text box (for example, WSSAdminSiteAppPool).

Select Configurable, and then enter the Windows SharePoint Services administrative site service account (for example, <computername>\WSSAdmin) and password.

Note: Make sure that you enter the computer name (<computername>), followed by a backward slash (\), and then the account name. Otherwise, you may receive an error indicating “System Error 1057 while trying to query service ’SPTimer’”

Click OK to complete the configuration.

The Application Pool Changed page opens; before you continue, restart IIS by doing the following:

1.	Click Start, point to All Programs, point to Accessories, and then click Command Prompt.
2.	At the command prompt, type iisreset, and then press ENTER.

After IIS resets, click OK on the Application Pool Changed page to continue configuring Windows SharePoint Services to work with your SQL Server computer.

On the Set Configuration Database Server page, in the Configuration Database section, type the database server name (for example, <computername>) and a database name (for example, SharePointConfigDb).

Under Database connection type, select Use Windows authentication (recommended security level).

Click OK.

To extend the virtual server with Windows SharePoint Services and connect to a remote SQL Server

1.	On the Central Administration page, under Virtual Server Configuration, click Extend or upgrade virtual server.
2.	On the Virtual Server List page, click the name of the virtual server to extend (Default Web Site).
3.	On the Extend Virtual Server page, in the Provisioning Options section, click Extend and create a content database.
4.	In the Application Pool section, select Create a new application pool, and then enter a name for it in the Application pool name text box (for example, CTIAppPool). This is a different application pool than the one you used for the Configuration database. Do not use WSSAdminSiteAppPool here.
5.	Select Configurable and enter your application pool service account (for example, <computername>\CTIAppService) and password in the appropriate text boxes. Note: Make sure that you enter the computer name (<computername>) with the backward slash (\) prior to the account name. Otherwise, you may receive an error indicating “System Error 1057 while trying to query service ‘SPTimer.’”
6.	In the Site Owner section, in User name, type the user name for the site owner (in the format <domainname>\User Name). In E-mail, type the e-mail address that corresponds to the account.
7.	In the Database Information section, clear Use default content database server check box, and type the database server (<computername>) and database name to use for a new content database (for example, SharePointContentDb).
8.	In the Site Language section, select the language to use.
9.	Click OK, wait until processing is complete, and then close all browser windows.

Installing Visual Studio .NET

Install Visual Studio .NET 2003 Enterprise Architect, Enterprise Developer, Special Edition, or Professional Edition. If necessary, Visual Studio .NET Setup will prompt you to install any prerequisites prior to starting the Visual Studio .NET installation. Click Visual Studio .NET Prerequisites and follow the instructions for installing the required components.

Only Microsoft Visual C#® .NET is required for this reference implementation. You can clear all options other than Visual C# .NET in the Options page. You do not need to install MSDN for this reference implementation.

Note: After completion of this installation, we recommend that you update your operating system and applications with Windows Update. The Visual Studio .NET installation wizard prompts you to update.

Installing Microsoft Office Information Bridge Framework 1.0 Server Components

This section details the following steps:

•	Downloading the Information Bridge Framework installation files – Download the Information Bridge Framework from the Microsoft Download Center. The download includes both server and client components.
•	Installing the server component of Information Bridge – Install the server components of Microsoft Office Information Bridge Framework 1.0. You will install the client components in a later step.
•	Installing Information Bridge Metadata Designer – Install the Information Bridge Metadata Designer so that you can open Metadata projects in Visual Studio .NET 2003.

To download the Information Bridge Framework installation files

Go to the Microsoft Office Information Bridge Framework 1.0 site at:

http://go.microsoft.com/fwlink/?LinkId=37321

Click the link to the download page. Run MOIBF1.0.exe to extract the Information Bridge files to your hard disk.

To Install the server component of Information Bridge Framework

1.	In Windows Explorer, navigate to the MOIBF1.0 folder on the C: drive.
2.	Double-click Microsoft.InformationBridge.Framework.Server1.0.msi.
3.	Click Next. Accept the End User License Agreement, and then click Next
4.	On the Configure Database page, click Next to accept all defaults.
5.	On the Installation Options page, click Next to accept all defaults. When the Path not found dialog box opens, click Yes to create the path.
6.	Keep the default port numbers and click Next.
7.	Click Next to begin the installation.
8.	When installation is complete, click Finish to close.

To install Information Bridge Metadata Designer

1.	In Windows Explorer, navigate to the MOIBF1.0 folder on the C: drive.
2.	Double click Microsoft.InformationBridge.MetadataDesigner1.0.msi.
3.	Click Next. Accept the End User License Agreement, and then click Next.
4.	Click Next to accept the default path.
5.	Click Finish to close.

Installing Microsoft Office 2003

Because you are installing the entire reference implementation on your development computer, including client applications, you need to install Microsoft Office 2003 Professional Edition by choosing the Complete Install option. Although this reference implementation requires only Microsoft Word 2003, the Complete Install option installs all of the required primary interop assemblies for programmability with .NET Framework 1.1.

Note: The required primary interop assemblies are .NET Programmability Support for each Office application installed and Smart Tag .NET Programmability Support under Office Tools. When you install these primary interop assemblies, other referenced assemblies such as Office.dll and microsoft.vbe.interop.dll are added automatically.

To install Microsoft Office 2003 Professional Edition

1.	Start Microsoft Office 2003 installation by running Setup from the CD or network.
2.	On the Type of Installation page, select Complete Install.

Installing the Information Bridge Client Component

Because you are installing client components on your development computer, the Information Bridge client component is also required. Office 2003 must already be installed so that all the required primary interop assemblies are enabled.

To install the Information Bridge client component

1.	In Windows Explorer, navigate to the MOIBF1.0 folder on the C: drive.
2.	Double click Microsoft.InformationBridge.Framework.Client1.0.msi.
3.	Click Next. Accept the End User License Agreement, and then click Next.
4.	On the Installation Options page, under the Metadata Service location, type http://<computername>:8081. Select the Validate Metadata Service Location check box, and then click Next.
5.	Click Finish to close.

Top of page

Installing and Configuring the Reference Implementation

This section details the procedures for installing and configuring the reference implementation, including the following tasks:

•	Preparing for Installation – First, download the reference implementation files from the Microsoft Download Center, use the setup wizard to install the files on your development computer, and configure the reference implementation setup script to customize it for your environment.
•	Installing the reference implementation – Next, install the reference implementation on your development computer, and then install and set up permissions for the various accounts.
•	Installing on a separate client computer – If you want to set up a separate client computer, follow these instructions to ensure that the required software is installed on the computer and to install the client components.

Preparing for Installation

First, prepare for installing the reference implementation by performing the following procedures:

•	Download the reference implementation
•	Build the reference implementation developer image
•	Configure the reference implementation setup script
•	Customize other setup variables

To download the reference implementation

1.	Open Internet Explorer and browse to Microsoft.com Download Center at: http://go.microsoft.com/fwlink/?LinkId=38237
2.	Download the file CTIRIMO1.0.
3.	Click Open or Run this program from its current location.
4.	In the Clinical Trial Initiation reference implementation wizard, on the Welcome screen, click Next.
5.	On the License Agreement page, select I Agree and click Next.
6.	On the Select Installation Folder page, in Folder, make sure you are installing files to the following folder on the C: drive: C:\Program Files\Microsoft Office 2003 Developer Resources\Clinical Trial Initiation
7.	Click Next.
8.	On the Confirm Installation page, click Next.
9.	When the Installation Complete page opens, click Close.

To build the reference implementation developer image

1.	Click Start, point to All Programs, point to Microsoft Visual Studio .NET 2003, and then point to Visual Studio .NET Tools.
2.	Click Visual Studio .NET 2003 Command Prompt.
3.	Change the directory by typing the following at the command prompt: cd C:\Program Files\Microsoft Office 2003 Developer Resources\Clinical Trial Initiation\
4.	Start the build script by typing the following at the command prompt: CTIBuildAll Debug

To configure the reference implementation setup script

The Setup script uses default variable settings. For proper installation, you must update the setup script with the local computer name and the SMTP server name. You can also modify other setup variables; see Tables 3.3 through 3.7.

Note: If the Command Prompt window is still open from the previous step, skip to Step 3.

Click Start, point to All Programs, point to Microsoft Visual Studio .NET 2003, and then point to Visual Studio .NET Tools.

Click Visual Studio .NET 2003 Command Prompt.

Go to the setup directory by typing the following at the command prompt:

cd C:\Program Files\Microsoft Office 2003 Developer Resources\Clinical Trial Initiation\Setup\Server

Open the main installation file in Notepad by typing the following:

notepad CTI-Install-All.cmd

Find the line that reads Set ServerName="localhost". Replace "localhost" with your computer name, for example:

Set ServerName="<computername>"

Find the line that reads Set SMTP Server="localhost" and do one of the following:

•	If your computer is the SMTP server, replace "localhost" with your computer name.
•	If you connect to a separate SMTP server, replace "localhost" with the SMTP server name.

Save the installation file and close it.

To customize other setup variables

The default installation uses the variables listed in Tables 3.3 through 3.7. You can customize the setup script by changing these variables in the CTI-Install-All.cmd file.

Table 3.3: Windows SharePoint Services Variables

Variable	Value
WSSPath	C:\Program Files\Common Files\Microsoft Shared\web server extensions\60
SiteDefinitionPath	..\Server\SharePoint\CTI Site Definition
IISRootPath	C:\Inetpub\wwwroot

Table 3.4: Clinical Trial Initiation Web Service Variables

Variable	Value
WebServiceSitePath	..\Server\WebServices
WebServiceSiteName	CTI Web Services
WebServiceSitePort	6002
CTIVirtualDirPath	..\Server\WebServices\ClinicalTrials
CTIVirtualDirName	ClinicalTrials
ContentLibURL	http://%ServerName%/sites/CTI-Home/ContentLib

Table 3.5: Investigators Web Service Variables

Variable	Value
InvVirtualDirPath	..\Server\WebServices\Investigators
InvVirtualDirName	Investigators
DBServer	%ServerName%
DBName	CTI_Investigator
InstallSQL	InstallInvestigators.sql
DataSQL	AddDummyInvestigators.sql

Table 3.6: Metadata and Client Variables

Variable	Value
MetadataPath	..\Metadata\Current Metadata\MSIBFMetadata.xml
ClinicalTrialsPath	http:// %ServerName%:%:%WebServiceSitePort%/%CTIVirtualDirName%/ClinicalTrials.asmx
InvestigatorsPath	http:// %ServerName%:%:%WebServiceSitePort%/%InvVirtualDirName%/Investigators.asmx
UI-DLLName	Company.ClinicalTrialInitiation.UserInterface.dll
UI-DLLSrc	bin\Company. ClinicalTrialInitiation.UserInterface.dll
UI-DLLPath	C:\Program Files\Microsoft Office 2003 Developer Resources\Clinical Trial Initiation\bin
MetadataServer	http:// %ServerName%:%:8082/IBFWriteService.asmx

The CTI-Install-All.cmd file installs all of the individual reference implementation components. To install individual components with customized variables, use the commands listed in Table 3.7.

Table 3.7: Additional customizable variables

Component	Installation variables
Installing Windows SharePoint Services components	CTI-WSS-Install %WSSPath% %SiteDefinitionPath% %IISRootPath%
Installing Clinical Trials Web Service	CTI-ClinicalTrialsWebService-Install %WebServiceSitePath% %CTIVirtualDirPath% %WebServiceSiteName% %WebServiceSitePort% %CTIVirtualDirName% %ContentLibURL%
Installing the Investigators Web Service	CTI-InvestigatorsWebService-Install %WebServiceSiteName% %InvVirtualDirName% %InvVirtualDirPath% %DBServer% %DBName% %InstallSQL% %DataSQL%
Updating metadata	CTI-Metadata-Install %MetadataPath% %ClinicalTrialsPath% %InvestigatorsPath% %UI-DLLPath% %UI-DLLName% %MetadataServer%
Installing client components	CTI-Client-Install %UI-DLLSrc% %UI-DLLPath% %UI-DLLName%

Installing and Configuring the Server Components

Next, install and configure the server components of the reference implementation on the development computer by performing the following procedures:

•	Run the setup script – Install the reference implementation's server components by using the main setup script.
•	Install the metadata – After setup is complete, publish the Clinical Trial Initiation Information Bridge metadata to the metadata server.
•	Disable anonymous access to Web services – Disable anonymous access to the Web services so that users cannot access services without providing credentials.
•	Define application pools for Web services – Configure the Web services so that they reference the application pool you created when you extended the SharePoint virtual server.
•	Grant database access to the Application Service account – Grant the appropriate permissions to the Application Service account used by the application pool so that the Investigators Web service can run properly.
•	Grant stored procedure permissions to the application service account – The application service account requires execute permissions on the sp_GetInvestigators stored procedure in the CTI_Investigator database.

To run the setup script

Note: If the Command Prompt window is still open from the previous step, skip to Step 4.

1.	Click Start, point to All Programs, point to Microsoft Visual Studio .NET 2003, and then point to Visual Studio .NET Tools.
2.	Click Visual Studio .NET 2003 Command Prompt.
3.	Go to the server setup directory by typing the following at the command prompt: cd C:\Program Files\Microsoft Office 2003 Developer Resources\Clinical Trial Initiation\Setup\Server
4.	Start the setup script by typing the following at the command prompt: CTI-Install-All.cmd
5.	If the message ”This script does not work with WScript” appears, click OK. When the message "Would you like to register CScript as your default host for VB Script?" appears, click Yes. Then click OK to continue setup.
6.	When setup is complete, close the command window.

To publish the metadata

1.	In Windows Explorer, navigate to the installation folder (C:\Program Files\Microsoft Office 2003 Developer Resources\Clinical Trial Initiation). Double-click ClinicalTrialInitiation.sln.
2.	Make sure that the Metadata Explorer pane is visible. If not, click View, Other Windows, and then click Metadata Explorer.
3.	In the Solution Explorer pane, click Company.ClinicalTrialInitiation.
4.	In the Properties pane, click the field to the right of Metadata Service Location. Type the following: http://<computername>:8082/IBFWriteService.asmx
5.	Click anywhere outside of the Metadata Service Location field. When the Information Bridge Warning appears, click Yes.
6.	In the Metadata Explorer pane, click the Publish Metadata button.
7.	In the Publish Metadata dialog box, select Metadata Service.
8.	Make sure that the Metadata server path is the following: http://<computername>:8082/IBFWriteService.asmx.
9.	Click OK.
10.	When the message "Publish Succeeded" appears in the Output pane, close Visual Studio and save the changes to the project.

To disable anonymous access to Web services

1.	Click Start, point to All Programs, point to Administrative Tools, and then click Internet Information Services (IIS) Manager.
2.	Expand the local computer node.
3.	Expand Web Sites.
4.	Right-click CTI Web Services, and then click Properties.
5.	Click the Directory Security tab. Under Authentication and access control, click Edit.
6.	Clear the Enable anonymous access check box, and then click OK.
7.	Click Apply. The Inheritance Overrides dialog box opens.
8.	Click Select All, and then click OK.
9.	Click OK to close the properties dialog box.

To define application pools for Web services

1.	In Internet Information Services (IIS) Manager, expand the local computer node.
2.	Expand Web Sites.
3.	Expand CTI Web Services
4.	Right-click the ClinicalTrials virtual directory, and then click Properties.
5.	On the Virtual Directory tab, in Application Pool, select the application pool name you created when you extended the virtual server (for example, CTIAppPool.)
6.	Click OK.
7.	Repeat steps 4, 5, and 6 for the Investigators virtual directory.
8.	Close IIS Manager.

To grant database access to the application service account

1.	Click Start, point to All Programs, point to Microsoft SQL Server, and then click Enterprise Manager.
2.	In Enterprise Manager, expand the Microsoft SQL Servers node.
3.	Expand the SQL Server Group node.
4.	Expand the SQL Server name node, named (local) (WindowsNT) by default.
5.	Expand the Security folder.
6.	Click Logins.
7.	In the right pane, double-click the application pool service account (for example, <computername>\CTIAppService).
8.	Click the Database Access tab.
9.	Scroll through the list of databases and find the CTI_Investigator database. Check the Permit box. In the Database roles for CTI_Investigator, verify that only Public is checked.
10.	Click OK.

To grant stored procedure permissions to the application service account

1.	In SQL Server Enterprise Manager, expand the Databases folder.
2.	Expand the CTI_Investigator node.
3.	Click Users.
4.	In the right pane, double-click the application pool service account (for example, CTIAppService).
5.	Click Permissions.
6.	Scroll the list of database objects to find the sp_GetInvestigators stored procedure.
7.	In the EXEC column, select the check box, and then click OK.
8.	Click OK to close the database properties.
9.	Close SQL Server Enterprise Manager.

Configuring Windows SharePoint Services and Installing Client Components

In this section, you create the Clinical Trial Site and a Protocol site in SharePoint, and configure user permissions. You also install the client components of the reference implementation so that you can use the reference implementation features on the development computer.

This section describes the following steps:

•	Create a top-level Clinical Trial Site – The Clinical Trial Site is the main SharePoint home site for the reference implementation.
•	Create the Content Library Site – Create the SharePoint site that contains reusable text for protocol documents.
•	Add users as Authors to the Clinical Trial Site – The two SharePoint groups used in this reference implementation are Authors and Contributors. An Author can create study-specific protocol sites and protocol documents. By creating a protocol document, the Author becomes the owner of the document and can assign sections to various Contributors. To evaluate the various features of the reference implementation, set up at least one account with Author credentials and one account with Contributor credentials.
•	Add users as Contributors to the Clinical Trial Site – Contributors can update protocol document sections.
•	Assign Metadata permissions to the Clinical Trial Site – In order for authors and contributors to use the task pane in protocol documents, they must have access to the metadata on the Information Bridge metadata server. To grant permissions to author and contributor user accounts, you should define a new role for the Clinical Trial Initiation metadata, assign Administrator permissions to this role, and then add the user accounts to this role.
•	Configure the client setup script - Before you run the client setup script, you must update the script to reflect the correct URL for the Clinical Trial Site.
•	Install client components – Run the client setup script to install the client components of the reference implementation on the development computer.

To create a top-level Clinical Trial Site

1.	Click Start, point to All Programs, point to Administrative Tools, and then click SharePoint Central Administration.
2.	In the Virtual Server Configuration section, click Create a top-level Web site.
3.	If the Virtual Server List page opens, click Default Web Site. Otherwise, go to step 4.
4.	In the Web Site Address section, select Create site under this URL. In the URL name text box, type CTI-Home. Note: This reference implementation is configured to use the URL name CTI-Home. You can use a different URL name; however, you must also modify the web.config file in the Clinical Trial Web service folder with the URL name you chose.
5.	In the URL path drop-down list, select sites.
6.	In the Site Collection Owner section, enter your User name and e-mail address.
7.	Click OK.
8.	On the Top-Level Site Successfully Created notification page, click the link to your new Web site.
9.	On the Template Selection page, select Clinical Trial Site, and then click OK.
10.	When your Clinical Trial Site page opens, add it to Favorites or set it as your home page.

To create the Content Library site

1.	In Internet Explorer, open the Clinical Trial Site by selecting the site from Favorites or typing the following URL: http://<computername>/sites/CTI-Home
2.	Click Create at the top of the page.
3.	Under Web Pages, click Sites and Workspaces.
4.	Under Title, enter a title for the Content Library site, for example Content Library, and then type a description.
5.	Under URL name, type ContentLib. Note: This reference implementation is configured to use the URL name ContentLib. You can use a different URL name; however, you must also modify the web.config file in the Clinical Trial Web service folder (appSetting with key="ContentLibrary.SiteUrl"). The Web.config file is located at C:\Program Files\Microsoft Office 2003 Developer Resources\Clinical Trial Initiation\Server\WebServices\ClinicalTrials\Web.config.
6.	Click Create.
7.	On the Template Selection page, select Clinical Trial Content Library, and then click OK.

To add users as Authors to the Clinical Trial Site

1.	In Internet Explorer, open the Clinical Trial Site by selecting the site from Favorites or typing the following URL: http://<computername>/sites/CTI-Home
2.	Click Site Settings in the top menu bar.
3.	In the Administration section, click Manage Users.
4.	Click Add Users.
5.	In the Users text box, type the complete user name of the Author, including the domain (<domainname>\<username>). If there are multiple authors, use semicolons (;) to separate them.
6.	In the Site Groups section, select Administrator.
7.	Click Next.
8.	Click Finish.

To add users as Contributors to the Clinical Trial Site

Note: If the Manage Users page is still open from the previous step, skip to Step 4.

1.	In Internet Explorer, open the Clinical Trial Site by selecting the site from Favorites or typing the following URL: http://<computername>/sites/CTI-Home
2.	Click Site Settings in the top menu bar.
3.	In the Administration section, click Manage Users.
4.	Click Add Users.
5.	In the Users text box, type the complete user name of Contributors, including the domain (<domainname>\<username>). If there are multiple contributors, use semicolons (;) to separate them.
6.	In the Site Groups section, select Contributor.
7.	Click Next.
8.	Click Finish.

To assign metadata permissions to the users

1.	Click Start, and then click Run. In the Run dialog box, type the following: azman.msc
2.	Right-click Authorization Manager, and then click Open Authorization Store.
3.	For the authorization store type, select XML file. Under Store name, enter the complete path to the Information Bridge Framework authorization store: C:\Inetpub\azRoles\Microsoft.InformationBridge.Roles.xml
4.	Expand the microsoft.informationbridge.roles.xml node. Expand Microsoft Information Bridge Framework Metadata Service, and then expand urn:Company.ClinicalTrialInitiation.
5.	Expand Definitions.
6.	Right-click Role Definitions, and then click New Role Definition.
7.	In the Role Definition dialog box, for Name, type the name of the role that you want to create (for example, CTIMetadata).
8.	Under The tasks and lower-level roles that define this role, click Add. In the Add Definition dialog box, click the Operations tab.
9.	Select the following operation definitions: Note: If you are performing a clean install, select all operations except the Administrator Access Operation. urn%3ACompany.C – ExecuteAction.DefaultClinicalTrialInitia urn%3AService%3 – CallComponent.Configure.ClinicalTrialInit urn%3AService%3 – ClinicalTrialInitiation.GetActionResult urn%3AService%3 – ClinicalTrialInitiation.GetActionResults urn%3AService%3 – GetInvestigators urn%3AService%3 – MSIBF.UI.LoadExtension.ReturnValue urn%3AService%3 – MSIBF.UI.ShowRegion.Ivnvestigators urn%3AService%3 – MSIBF.UI.ShowRegion.Library urn%3AService%3 – MSIBF.UI.ShowRegion.Options urn%3AService%3 – MSIBF.UI.ShowRegion.Sections urn%3AService%3 – Soap.ClinicalTrialInitiation.xxxxxxxx (8 instances) urn%3AService%3 – TransformationAggregation.SendNotificat urn%3AService%3 – TransformationAggregation.SendWmiEvent
10.	Click OK to close the Add Definition dialog box.
11.	Click OK to close the Role Definition dialog box.
12.	Under the same urn: node, right-click Role Assignments, and then click Assign Roles.
13.	In the Add Role dialog box, select the new role (for example, CTIMetadata), and then click OK. The role is added to the Role Assignments folder.
14.	Click the Role Assignments folder. In the right pane, right-click the new role, and then click Assign Windows Users and Groups.
15.	In the Select Users, Computers, or Groups dialog box, add the users (both Authors and Contributors) that you want to assign to this role, including the domain (<domainname>\<username>). These users will be able to access reference implementation metadata and use the task pane in Microsoft Office Word 2003.
16.	Expand the urn:Service:ClinicalTrialInitiation node and repeat Steps 5 through 15.
17.	Expand the urn:Service:Investigators node and repeat Steps 5 through 15.

To configure the client setup script

1.	Click Start, point to All Programs, point to Accessories, and then click Command Prompt.
2.	Change the directory to the client directory by typing the following at the command prompt: cd C:\Program Files\Microsoft Office 2003 Developer Resources\Clinical Trial Initiation\Setup\Client
3.	To open the client installation script in Notepad, type the following at the command prompt: Notepad CTI-Client-Install.cmd
4.	Find the line that reads the following: Set SCHEMALOCATION="http://[ProtocolsHomeURL]/Schemas/ ClinicalTrialInitiationSchema.xsd
5.	Replace [ProtocolsHomeURL] with the URL of the Clinical Trial Site created earlier so that the line reads as follows: Set SCHEMALOCATION="http://<computername>/sites/CTI-Home/Schemas/ ClinicalTrialInitiationSchema.xsd
6.	Save and close the file.

To install client components

Run the setup file by typing the following at the command prompt:

CTI-Client-Install.cmd

Close the Command Prompt window.

Note: The reference implementation uses the Windows SharePoint Services search feature to search the snippets in the Content Library. When you are finished installing the reference implementation, you should enable full-text indexing and searching in the reference implementation. See Chapter 5, "Development Considerations" for instructions on how to do this.

Installing Client Components on Other Computers

If you want to install the client component of the reference implementation on a separate computer, ensure that the client computer contains the following required software:

•	Microsoft Windows 2000 Professional SP3 or later, Microsoft Windows XP Professional SP1 or later, or Microsoft Windows Server 2003, Standard or Enterprise Edition
•	Microsoft .NET Framework 1.1 (for information about installing .NET Framework 1.1 on the client computer, see http://go.microsoft.com/fwlink/?LinkId=37322)
•	Microsoft Office 2003 Professional Edition with the latest service pack (perform a complete installation of Microsoft Office 2003 so that all required primary interop assemblies are installed automatically)
•	Internet Explorer 6
•	Information Bridge client component

To install the reference implementation on the client computer

Copy the following folder from the server to any folder on the client computer:

C:\Program Files\Microsoft Office 2003 Developer Resources\Clinical Trial Initiation\Setup\Client

On the client computer, open the Command Prompt window.

1.	Click Start, point to All Programs, and then click Accessories.
2.	Click Command Prompt.

Change the directory to the location of the Client folder you copied in step 1 by typing the following at the command prompt:

cd <path to folder>\Client

Run the setup file by typing the following at the command prompt:

CTI-Client-Install.cmd

Close the Command Prompt window.

Top of page

Using the Reference Implementation

After you install and configure the reference implementation software, you can try the following features:

•	Creating a study-specific protocol site – When a new study is initiated, the protocol document author creates a study-specific protocol site. A new protocol document is automatically created in the new site's document library. Creating a new protocol site also creates a new protocol document.
•	Working with a protocol document – Any user (Contributor or Author) can open the protocol specific site and use the protocol document.

Chapter 4, "Testing and Troubleshooting," contains detailed instructions for testing your installation, including steps that walk through the major features of the reference implementation,

To create a Protocol Site

1.	Log onto Windows using Author credentials.
2.	Open the Clinical Trial Site in Internet Explorer by typing the following URL: http://<computername>/sites/CTI-Home
3.	Click Protocols Library on the top menu bar.
4.	Click Create Protocol Site.
5.	On the Library page enter a title, description and URL name for the site.
6.	The Protocol Document Template defaults to Protocol.xml.
7.	Click Create to create the site.

To work with a Protocol Document

1.	Log on to Windows using Author or Contributor credentials.
2.	Open the Clinical Trial Site in an Internet Explorer window by typing the following URL: http://<computername>/sites/CTI-Home
3.	Click Protocols Library.
4.	Click the name of the protocol site. The home page for the study-specific protocol site will appear.
5.	In the left pane, click Shared Documents. This is the default document library for the protocol site.
6.	Point to the protocol document (named Protocol **SiteName.xml**). A smart menu button will appear on the right side of the document.
7.	Click the smart button.
8.	On the smart menu, select Edit in Microsoft Office Word. The Protocol smart document opens in Microsoft Office Word and an Information Bridge Framework information window appears.
9.	Update the document by using the features in the Information Bridge Framework information window.
10.	Save the document and close Microsoft Office Word.

Top of page

Uninstalling the Reference Implementation

This section details the steps to follow if you want to uninstall the reference implementation components on your development computer. The standard uninstallation procedure uses the default setup options defined in the "Alternate Uninstallations" section of this chapter. The uninstallation procedure can be customized or can be executed for individual components as explained in "Alternate Uninstallations."

Open the Visual Studio .NET 2003 Command Prompt window by doing the following:

1.	Click Start.
2.	Point to All Programs, point to Microsoft Visual Studio .NET 2003, and then point to Visual Studio .NET Tools.
3.	Click Visual Studio .NET 2003 Command Prompt.

Change the directory by typing the following at the command prompt:

cd C:\Program Files\Microsoft Office 2003 Developer Resources\Clinical Trial Initiation\Setup\Server

Start the setup script by typing the following at the command prompt:

CTI-UnInstall-All.cmd

Alternate Uninstallations

If you did not customize any setup variables when you installed the reference implementation, you can run the standard uninstall script to remove the reference implementation. However, if you customized setup variables (for example, if you installed the reference implementation on a drive other than the C: drive) you can customize the uninstall script accordingly.

The default uninstall script uses the variables listed in Tables 3.8 through 3.11. To customize the uninstall script, change the variables listed in tables 3.8, 3.9, and 3.10 in the CTI-UnInstall-All.cmd file.

Table 3.8: Windows SharePoint Services Variables

Variable	Value
WSSPath	C:\Program Files\Common Files\Microsoft Shared\web server extensions\60
SiteDefinitionPath	..\..\Server\SharePoint\CTI Site Definition
IISRootPath	C:\Inetpub\wwwroot

Table 3.9: CTI Web Service Variables

Variable	Value
WebServiceSiteName	CTI Web Services
CTIVirtualDirName	ClinicalTrials

Table 3.10: Investigators Web Service Variables

Variable	Value
InvVirtualDirName	Investigators
DBServer	Localhost
DBName	CTI_Investigator

You can also customize the uninstallation of the individual components by changing the variables listed in Table 3.11.

Table 3.11: Additional customizable variables

Component	Installation variables
UnInstall Windows SharePoint Services Components	CTI-WSS-UnInstall %WSSPath%
UnInstalling Clinical Trials Web Service	CTI-ClinicalTrialsWebService-UnInstall %WebServiceSiteName%
UnInstalling Investigators Web Service	CTI-InvestigatorsWebService-UnInstall %WebServiceSiteName% %InvVirtualDirName% %DBServer% %DBName%
UnInstalling Metadata	CTI-Metadata-UnInstall %MetadataPath% %MetadataServer%
UnInstalling Client components	CTI-Client-UnInstall

Top of page

Installation Reference Worksheet

Table 3.12 is a worksheet that you can use to record the information you use during installation and configuration of the reference implementation. The examples used throughout this chapter are shown in italics.

Table 3.12: Values you used during reference implementation installation

Document Section	Description	Value
Creating Windows service accounts	Computer name	*Example*: <computername> Your value: ________________________
Creating Windows service accounts	SQL service account	*Example*: SQLService Your value: ________________________
Creating Windows service accounts	Application pool service account	*Example*: CTIAppService Your value: ________________________
Creating Windows service accounts	SharePoint admin site application pool account	*Example*: WSSAdmin Your value: ________________________
Configuring the administrative virtual server	Application pool name	*Example*: WSSAdminSiteAppPool Your value: ________________________
Configuring the administrative virtual server	SQL configuration database name	*Example*: SharePointConfigDb Your value: ________________________
Extending the virtual server	Application pool name	*Example*: CTIAppPool Your value: ________________________
Extending the virtual server	SQL content database name	*Example*: SharePointContentDb Your value: ________________________
Creating the Clinical Trial Site	URL name for the Clinical Trial Site	*Example*: CTI-Home Your value: ________________________
Creating the Content Library Site	Title for the Content Library	*Example*: Content Library Your value: ________________________
Creating the Content Library Site	URL name for the Content Library	*Example*: ContentLib Your value: ________________________
Assigning metadata permissions	Role for metadata permissions	*Example*: CTIMetadata Your value: ________________________

Top of page

4 of 7

Clinical Trial Initiation Reference Implementation for Microsoft Office 2003 Guide

Chapter Three – Installing and Configuring Your Development Environment

On This Page

Hardware and Software Prerequisites

Installing the Required Software on the Development Computer

Installing and Configuring Windows Server 2003

Installing SQL Server

Installing and Configuring Windows SharePoint Services

Installing Visual Studio .NET

Installing Microsoft Office Information Bridge Framework 1.0 Server Components

Installing Microsoft Office 2003

Installing the Information Bridge Client Component

Installing and Configuring the Reference Implementation

Preparing for Installation

Installing and Configuring the Server Components

Configuring Windows SharePoint Services and Installing Client Components

Installing Client Components on Other Computers

Using the Reference Implementation

Uninstalling the Reference Implementation

Alternate Uninstallations

Installation Reference Worksheet