BUILDER 3.0 Installation Guide with Microsoft SQL Server 2005 Express Edition January 2008

(1)

BUILDER 3.0 Installation Guide

with

Microsoft SQL Server 2005

Express Edition

(2)

Chapter 1: Installation Overview

Introduction

BUILDER 3.0 with IMPACT is a web-based application developed by ERDC/CERL. It replaces the BUILDER 2.2 Windows desktop version and features many improvements. IMPACT is now an integrated module within BUILDER 3.0 and runs within the BUILDER Application Service. See the “What's New in BUILDER 3.0” document available on the ERDC-CERL SMS portal and within the BUILDER 3.0 application Help system.

INFO: SMS Users Group URL: http://sms.cecer.army.mil/BUILDER/tabid/54/Default.aspx

The following components are part of the BUILDER 3.0 installation. Chapter 2 discusses each component in greater detail.

NOTE: BUILDER 3.0 is a web application that’s installed and configured on a web server.

1. BUILDER Web Site—a web application hosted on your web server.

2. BUILDER Application Service—processes IMPACT scenarios and BUILDER statistics. 3. BUILDER Database Management—tools to manage the BUILDER databases.

4. BUILDER Web Application Configuration Utility—used to configure database connections. 5. BUILDER Application Service Configuration Utility—configures BUILDER Application Service.

Minimum Requirements

Minimum hardware: Refer to Microsoft OS requirements

Operating Systems supported: Windows 2000/2003 Server, and XP Professional Recommended memory: 2 Gigabytes, minimum

Disk space required: Application Server: 7 MB Database Tools: 269 MB Web Application: 97 MB Minimum required screen resolution: 1024 x 768

Recommended internet browser : Microsoft Internet Explorer v. 5.X and higher Browser configuration: Disable all Popup Blockers

Relational database: SQL Server 2005 Studio Express or Enterprise Edition; and SQL Server 2000 Standard or Enterprise Edition Language Runtime: .NET 1.1 Framework for BUILDER and .NET 2.0

Framework for SQL Server 2005

General Guidelines and Preparation

To prepare for the installation, follow these general guidelines: The detailed installation procedures are documented in Chapter 2.

NOTE: Have your Operating System installation disc handy; you'll need it to install Internet Information Services (IIS).

(4)

4. Run the BUILDER 3.0 installation program. 5. Create empty databases on your database server

6. Run database schema scripts to create data tables, views, etc. 7. Load example data or upgrade a BUILDER 2.2 database

INFO: Windows Server 2003 requires special instructions, see Appendix A for details.

Configuration Options

BUILDER 3.0 installation options can vary greatly. From stand-alone configurations that run on an individual workstation to enterprise-level configurations and network architectures. An

administrator can choose to manually install only selected components for a custom installation or run a complete install using the InstallShield wizard application provided on the CD. The option to install the web application, database, and service on a single machine is the default “Complete” option in the InstallShield wizard. The installation options are configurable for a variety of network environments.

Standalone Configuration

When installing the BUILDER 3.0 application on a standalone system, you are configuring your Internet Information Server (IIS), SQL Server, and BUILDER Application Service to run on the same machine. The application will run disconnected from the Internet ( no Internet connection is required ) and you'll be able to access the BUILDER 3.0 web application using your local

browser. The following URL will access the application on a standalone local machine: http:/localhost/builder3/default.aspx

NOTE: A standalone setup is the default installer configuration for BUILDER 3.0 when the Complete Setup Type is selected in the InstallShield wizard.

Enterprise System Configuration

For an enterprise system configuration, install the BUILDER 3.0 web application on a dedicated Application Server that is hosting IIS. Install Microsoft SQL Server 2000 or 2005 Express Edition or Enterprise Edition on a Database Server. The BUILDER Application Service can also be installed separately, using the BUILDER Application Service Configuration Tool to define the connection strings. The BUILDER Web Application Configuration Tool is used to define all the connections strings for the web application.

Since you can install the database on a dedicated database server, you'll most likely prefer to use SQL Server 2005 Enterprise Edition for this type of configuration. Select the Custom Setup Type in the InstallShield Wizard for individual installation options.

NOTE: At this time, SQL Server is the only database supported with BUILDER 3.0

Client Workstation

(5)

Chapter 2: Component Overview

This chapter discusses the various components of the BUILDER product. You can skip this section for Chapter 3, to begin the installation process.

BUILDER Web Application

The installer will create a virtual directory, with web content files located in <drive>\Program Files\ERDC-CERL\Builder3\WWW folder.

And a web application directory in IIS as: <domain>/builder3/default.aspx

BUILDER 3.0 is designed to run in its own browser window--meaning that we remove all browser related navigation menus and commands from the interface. On initial launch of BUILDER 3.0, a javascript method opens a new window--as a popup, disables the browser interface, and renders the BUILDER 3.0 application. If you have a popup blocker, an error will occur—the application will not load and the browser window will close. It will “disappear”.

NOTE: Disable all popup blockers when using BUILDER 3.0

BUILDER Application Service

Included in BUILDER 3.0 is a Windows Service called BUILDER Application Service. The service is designed to process IMPACT scenarios and update metrics. In addition, the service helps improve application performance by moving computational work into a background process. The service will run nightly or as scheduled and will process the current application data in the database. It will require configuration using the BUILDER Application Service Configuration Utility.

BUILDER Database Management

In the BUILDER Database Management tool there are two options available and they are executed during the installation process.

Option 1: Create NEW databases or UPGRADE an existing database. Use the New database option when creating a new installation; use the Upgrade option when importing data from a BUILDER 2.2 database.

Option 2: Apply PATCH scripts to existing databases. Run this option when patches become available.

BUILDER Web Application Configuration Utility

Use this tool to configure database connectivity for the web site. It is run during the installation process or at any other time when your database location or connection information changes. When you save the settings in the Utility, the values in the web.config file are saved using encryption method.

(6)

BUILDER Application Service Configuration Utility

Use this tool to configure the BUILDER Application Service. It is run during the installation process or at any other time there are changes to your database locations or connection information.

Chapter 3: Installation Prerequisites

Prerequisites

The BUILDER 3.0 Web Application Installer requires Microsoft Internet Information Services (IIS) prior to running. Additionally, the .NET 1.1 Framework will install if it’s not already on your machine. If you already have .NET 1.1 Framework on your machine, the installer will begin with the web application.

To determine your configuration of IIS and .NET 1.1 Framework, read the next two sections. Otherwise, continue with Chapter 4, Running the Builder 3.0 Installer.

Internet Information Services (IIS)

(7)

3.0 Web Application Server.

1. Open the Control Panel by clicking “Start” and then “Control Panel” 2. Open “Add or Remove Programs”

Note: If you are running the Classic Windows menu, the access is through Start | Settings | Control Panel.

If the .NET 1.1 Framework is installed, the Add or Remove Programs dialog will display the framework as noted in the figure below.

NOTE: You must install IIS prior to running the installer for BUILDER 3.0. If you forget, the installer will remind you, and will allow the install to continue. The virtual director, however, will not be created, leaving a partial installation. In this case, the virtual directory will need manual configuration; the content files will be installed in either case.

Also, if for some reason the .NET Framework was installed prior to IIS, the web server will not know about .NET file extensions and BUILDER 3.0 will not run. This condition would be true for all .NET applications running on the Application Server. To remedy this condition, run the following tool: It registers .NET with IIS and provides the web server knowledge about ASP.NET files:

<drive>:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\aspnet_regiis.exe

NOTE: You must have administrative rights on the machine to run this tool.

(8)

Chapter 4: Running the BUILDER 3.0 Installer

Stepping through the InstallShield Wizard

To begin, login to your server or workstation as an Administrator. Insert the BUILDER 3.0 Setup CD and double click the setup.exe file if your system didn’t auto-start the installer. The following screen will appear after the BUILDER banner is displayed if you do NOT have .NET 1.1

Framework installed.

(9)

An Installation complete dialog with appear when done.

(10)

(11)

The license agreement will appear. Read the license agreement and select “I accept the terms in the license agreement.”

Click “Next”

(12)

(13)

The “Setup Type” Screen will appear. We recommend choosing the “Complete” installation, unless you are planning on splitting up the web application and the BUILDER service on separate machines. See Chapter 1, Configuration Options.

(14)

(15)

A screen with a message about Virtual Directories will appear. After installing the web

application, the setup application will create a virtual directory on the local Internet Information Service (IIS) that aliases the install directory as BUILDER. If you are planning on running multiple web applications for BUILDER or wish to change the alias name, you can change the name of the virtual directory with the Internet Information Services management console located in the

Administrative Tools folder. If you need further assistance, please contact your local systems administrator for help changing this alias.

(16)

The installation application is ready to install Builder 3.0.

(17)

(18)

Click “Finish” after the installation is complete. If this is a new installation, you will need to create a new database, or optionally upgrade an existing BUILDER 2.2 database. See Chapter 5 to create a new database and Chapter 6 if you are upgrading your existing BUILDER 2.2 database.

Click “Finish”

You can validate the installation by selecting the Start menu All Programs command. You’ll see the following menu commands:

To verify the IIS web application installation, use the Computer Management console to view the web application. To access the Computer Management screen, go to Start, Control Panels, Administrative Tools, Computer Management. The following screen will display:

(19)

At this point, the BUILDER 3.0 application installation is complete. Next, install the databases as described in the next Chapter.

Chapter 5: Creating new BUILDER 3.0 Databases

Configuration Options

BUILDER 3.0 currently only runs with Microsoft SQL Server. If you are planning on running BUILDER as a stand alone application on a workstation or laptop, we recommend you install SQL Server 2005 Express Edition and SQL Server Management Studio Express. You can download a freely available copy of SQL Server 2005 Express Edition and SQL Server Management Studio Express from the following Microsoft website.

http://msdn2.microsoft.com/en-us/sql/Aa336346.aspx

If you are installing BUILDER 3.0 on a Database Server, your preferred database is SQL Server 2000 or 2005 Enterprise Edition. You will require the appropriate number of client access licenses (CAL’s).

(20)

1. SQL Server 2000 Standard or Enterprise Edition 2. SQL Server 2005 Standard or Enterprise Edition 3. SQL Server 2005 Express Edition

SQL Server Security

We highly recommend configuring SQL Server 2005 using Microsoft’s Best Practices. The following URL points to a good reference document: “SQL Server 2005 Security Best Practices - Operational and Administrative Tasks”.

http://www.microsoft.com/technet/prodtechnol/sql/2005/sql2005secbestpract.mspx

NOTE: Our screen shots show the use of Mixed-Mode Authentication and SQL Server logins using the “sa” user id. This is NOT a recommended practice.

Microsoft recommends these best practices for authentication mode: • Always use Windows Authentication mode if possible.

• Use Mixed Mode Authentication only for legacy applications and non-Windows users. • Use the standard login DDL statements instead of the compatibility system procedures. • Change the sa account password to a known value if you might ever need to use it. Always

use a strong password for the sa account and change the sa account password periodically. • Do not manage SQL Server by using the sa login account; assign sysadmin privilege to a

knows user or group.

• Rename the sa account to a different account name to prevent attacks on the sa account by name.

Database Installation

To install SQL Server 2005 Express Edition you’ll need the following software: 1. Microsoft .NET 2.0 Framework

2. Microsoft Installer Version 3.1

Both products are available for free download from Microsoft. Search the Microsoft downloads web site for the most recent download URLs.

NOTE: The complete installation instructions for .NET 2.0 and MS Installer 3.1 are beyond the scope of this document.

(21)

(22)

Once the database is installed, proceed with the SQL Server 2005 Management Studio Express Edition installation. This step will complete the database requirement for BUILDER 3.0.

Connect to SQL Server

(23)

Login to SQL Server 2005 using Windows Authentication as noted below, or use SQL Server Authentication is configured during installation.

You are now connected to SQL Server.

Create Empty SQL Server Databases

(24)

(25)

Type in the name of your Inventory database, you may use any name you wish. In this example, we are using Inventory as our database name.

NOTE: BUILDER 3.0 connects to three databases. We recommend that each database name refer to its described purpose—simplifying administration tasks.

(26)

Repeat the last two steps for the Lookup and Impact databases.

When you are finished, exit the SQL Server Management Studio Express application and run the Builder Database Management tool.

Define the BUILDER 3.0 Databases

Open the Builder Database Management tool from the start menu. This tool is used to run schema scripts against the three previously created databases.

(27)

Click “Next”.

1. Lookup Database

Create the lookup database before any other databases. This is very important. There are schema dependencies with the other two databases.

(28)

(29)

Click the “Finish” button to confirm the settings.

A screen will appear to notify you of the progress.

(30)

Inventory Database

(31)

Enter the login information to your SQL Server or use integrated security if running locally. Also enter the name of your Lookup database. In this example, our database is named “Lookup”.

(32)

Click the “Finish” button to confirm the settings.

(33)

Impact Database

After the Lookup and Inventory databases have been created, create the Impact database.

(34)

Enter the login information to your SQL Server or use integrated security if running locally. Also enter the name of your Lookup database. In this example, our database is named “Lookup”.

(35)

You have finished creating and defining the BUILDER 3.0 databases.

Chapter 6: Configuring the BUILDER Web Application

Before BUILDER 3.0 runs for the first time, you need to configure the web application and specify the location of the databases. Open the “BUILDER Web Application Configuration Utility” from the “Start” menu.

(36)

(37)

(38)

(39)

Enter the server name and database for each section. You should use the same names used when creating the databases in SQL Server.

(40)

If you want to use trusted security, check the trusted security checkboxes for each of the databases and make sure the server names and database names are correct.

Click “File”, “Save” and then “Exit

Chapter 7: Configuring the BUILDER Application Service

(41)

(42)

(43)

Change the Server Name and Database to the workstation or server hosts your database and use the database names previously created. If you are using trusted security, check the “Use Trusted Security” check box or enter the UserID and Password for the databases. Click “File” and “Save”. Click “File” and “Exit” when finished.

(44)

You will need to stop and restart the BUILDER Application Service from the “Control Panel” “Administrative Tools”, “Services” management console. Click on the service, then Restart button circled below.

Chapter 8: Running the BUILDER 3.0 Web Client

From the “Start” menu, select the “BUILDER 3 Login” menu item. This menu item will only be available on the machine that was used for the web application installation. Otherwise, you’ll need to know the URL for the Application Server web site created during the installation.

NOTE: See you administrator for the correct URL to access BUILDER 3.0 from any desktop.

(45)

(46)

(47)

Appendix A: Special Instructions for Installing BUILDER

3.0 on a Windows Server 2003 Computer

Windows Server 2003 requires special attention for BUILDER 3.0 to install successfully. Follow the normal BUILDER 3.0 installation instructions described in this document, then, complete these additional steps:

1. Configure the computer as an Application Server. 2. Enable Web Service Extensions for ASP.NET v.1.1.4322 3. Create a BUILDER Application Pool

4. Set the ASP.NET version for the web application to version 1.1.4322 5. Create folder permissions for the NETWORK SERVICE user

NOTE: Administrator rights are required to complete the changes. Also, the Windows Server 2003 server must be set to Application Server tasks.

1. Configure the computer as an Application Server.

For the purpose of this discussion, the server must be configured to act as an Application Server, with the appropriate administrative, network, or security properties correctly configured.

(48)

2. Enable Web Service Extensions for ASP.NET

v.1.1.4322

Within the Computer Management console, expand the Internet Information Services (IIS) Manager. Select the Web Service Extensions folder and right-click for Properties. In the right window pane, set the ASP.NET v.1.1.4322 Web Service Extension to “Allowed”. If you do not see the v1.1 extension, Add a new Web service extension using the Task link. See Figure 1. below.

Figure 1.

3. Create a BUILDER Application Pool.

(49)

Figure 2

Keep the “Use default settings for a new pool” selection. Press OK.

Figure 3

(50)

Figure 4

(51)

Figure 5

4. Set the ASP.NET version for the web application to

version 1.1.4322

(52)

Figure 6

5. Create folder permissions for the NETWORK SERVICE

user

(53)

Figure 6

Right click on the following folders and add the NETWORK SERVICE user to each directory. Set the permission to “Modify” and press OK.

NOTE: MapImages resides within the GIS folder.

1. ChartImages 2. Exports 3. Files

4. GIS\MapImages.

(54)

Figure 7

(55)

Appendix B: Upgrading BUILDER 2.2 Databases

The BUILDER Database Management tool features an Upgrade Existing Database option. This feature will allow you to import BUILDER 2.2 data into a BUILDER 3.0 database.

Once your data is imported, you’ll need to setup BUILDER 3.0. The data conversion process only imports your data; to work with your data in BUILDER 3.0, you’ll need to properly configure your new application environment. The following application settings may need attention prior to using some of the advanced features of the application:

• Security and Permissions • Reference Settings • Work Planning

• Knowledge-based Inspections • IMPACT scenarios

We recommend that your organization thoroughly review your Facility Management strategy, and configure BUILDER 3.0 in accordance with your needs.

Data Conversion

Your first step is to convert your BUILDER 2.2 data. Open the BUILDER Database Management application from the start menu.

NOTE: You must run the schema scripts as outlined in Chapter 5: Define the BUILDER 3.0 databases, prior to importing BUILDER 2.2 data.

(56)

(57)

Browse for your Builder 2.2 Database, usually located in the C:\Program

Files\ERDC-CERL\Builder\Database directory. Browse for your Reference Database, usually located in the C:\Program Files\ERDC-CERL\Builder\System Tables directory.

If you plan to convert your inventory to Uniformat II, select the Convert into Uniformat II hierarchy option.

For online help search: “ASTM UNIFORMAT II”

Click “Next”

(58)

Click “Next”.

Once converted, your BUILDER 2.2 data will be available in the new 3.0 format. You’ll notice during the import process that user accounts have been processed as well. With Administrator rights to the application, you’ll have the ability to manage these accounts and their permissions. This is the first administrative action needed after you have successfully converted your data.

Security and Permissions

Plan your security needs. BUILDER 3.0 has new inventory management features and will provide you with greater flexibility in security management.

Your security plan should account for multiple levels of organizational and inventory hierarchy; permissions and authentication settings should follow this plan accordingly.

For online help search: “Users and Groups”

Reference Settings

By default, BUILDER 3.0 includes Cost Book, Inflation Book, and Service Life Book data. If you have customized references in previous versions, review the settings and validate your inventory hierarchy. They are part of your upgrade; check the selection of these settings at the Site level. Reference settings are available at the Organizational level down to the Site level in your inventory hierarchy.

(59)

settings. While BUILDER 3.0 includes advanced patent-pending technologies to help you manage your facilities, the system must be properly administered.

NOTE: Functionality Standards are new. Prior to generating work items, you will need to define and assign them to a Policy Sequence.

For online help search: “Work Planning Overview”

Knowledge-Based Inspection Schedule

The Inspection Schedule feature in BUILDER 3.0 is a patented technology that uses your Work Management settings, inventory, and assessment data to create an automated inspection schedule. This is a powerful money-saving feature. For best results, you must attend to your Work Management settings, including Work and Inspection triggers located within the Work Management Standards and Policies screens.

NOTE: You must configure your inspection scheduling values for your standards prior to using Knowledge-based Inspection Schedule.

For online help search: “KBI”

IMPACT Scenarios

The BUILDER 3.0 web application now includes IMPACT as an integral part of the user interface. Scenarios are created, monitored and analyzed within BUILDER.

NOTE: The BUILDER Application Service must be running and configured to monitor your database for scenarios to be processed. See Chapter 7 for instructions on ensuring this is setup properly.

BUILDER 3.0 Installation Guide with Microsoft SQL Server 2005 Express Edition January 2008