Mi - Home Builder Software - BuilderMT Install Guide.pdf · communication to the Firebird database on the BuilderMT server. Network security/integrity best practices strongly recommend

1

Mi

2

© 2009 BuilderMT, LLC, 200 Union Blvd, Suite 500, Lakewood, Colorado USA 80228. All rights reserved.

Workflow Management Suite, ProHome, BuilderMT are registered trademarks and are the express

property of BuilderMT, LLC. All other trademarks referenced in this material are the express property of

their respective owner.

Acknowledgements:

Screen captures supporting the creation of jobs and estimates were taken directly from Sage

Timberline® Office (accounting and estimating) programs, with permission from Sage Software,

Inc®.

Screen captures supporting the use of the Palm® m130 were taken directly from the Palm OS®

Emulator 3.x with the permission of Palm Inc.

Screen captures supporting the use of the BlackBerry 7510™ were taken directly from the

BlackBerry® Handheld Simulator 2.1.0.76 with the permission of Research In Motion, LTD.

Notice to end user: The features and screen captures in this document refer to BuilderMT's Workflow

Management Suite version 4.x. This includes the Purchasing, Scheduling and Sales Pricing modules.

This document contains information which is the proprietary property of BuilderMT, LLC. No part of this

publication may be reproduced, stored in a retrieval system, or transmitted, in any form or by any

means, electronic, mechanical, recording or otherwise, without the prior written permission of

BuilderMT, or as allowed within the terms of the applicable software license agreement.

3

Table of Contents Introduction and System Requirements ....................................................................................................... 6

Introduction .............................................................................................................................................. 6

Intended Audience ................................................................................................................................ 6

Citrix and Terminal Services Installations ............................................................................................. 6

Compatibility with Sage Timberline Office® ......................................................................................... 6

System Requirements ............................................................................................................................... 7

WMS Server Requirements ................................................................................................................... 8

WMS Workstation Requirements ......................................................................................................... 8

Bmt.Net API / Trade Portal / Mobile Scheduling Requirements (IIS Web Server Required) ................ 9

BPM (Business Process Management) Requirements (IIS Web Server Required) ............................... 9

Recommended Configuration ............................................................................................................. 10

Section One: WMS Server Installation ....................................................................................................... 11

WMS Server Installation ......................................................................................................................... 12

Server Installation Prerequisites ......................................................................................................... 12

Server Installation Prerequisites for Server 2008 and Windows 7 ..................................................... 12

Default Ports for WMS ........................................................................................................................ 13

Begin the Installation Process ................................................................................................................. 13

Important Documents ......................................................................................................................... 13

Pre-Installation Steps .......................................................................................................................... 13

Performing the Server Installation ...................................................................................................... 14

Section Two: WMS Workstation Installation ............................................................................................. 18

Workstation Installation Overview ......................................................................................................... 19

Workstation Installation Prerequisites ............................................................................................... 19

Initiating a Stand-alone Setup ............................................................................................................. 19

Initiating a Network Setup .................................................................................................................. 20

Performing the Workstation Installation ................................................................................................ 20

Section Three: Bmt.Net API Installation ..................................................................................................... 22

Bmt.Net API Overview ............................................................................................................................ 23

Bmt.Net API Installation Prerequisites for Server 2008 and Windows 7 ........................................... 23

Performing the Bmt.Net API Installation ................................................................................................ 23

Bmt.Net API Defaults .......................................................................................................................... 24

4

Bmt.Net API Post Installation Steps ........................................................................................................ 25

Section Four: Mobile Scheduling Installation ............................................................................................. 26

Mobile Scheduling Overview .................................................................................................................. 27

Prerequisites ........................................................................................................................................... 27

Physical Directory and IIS Virtual Directory ............................................................................................ 27

Performing the Mobile Scheduling Installation ...................................................................................... 27

Mobile Scheduling Post-Installation Required Configuration ................................................................. 28

IIS Configuration (IIS 6 only) .................................................................................................................... 28

File Permissions ....................................................................................................................................... 28

DB/WMS Server Configuration ............................................................................................................... 28

Section Five: Superintendent Portal Installation ........................................................................................ 29

Superintendent Portal Overview ............................................................................................................ 30

Prerequisites ........................................................................................................................................... 30


Performing the Superintendent Portal Installation ................................................................................ 30

Superintendent Portal Post-Installation Required Configuration ........................................................... 31




Section Six: Trade Portal Installation .......................................................................................................... 32

Trade Portal Overview ............................................................................................................................ 33

Prerequisites ........................................................................................................................................... 33


Performing the Trade Portal Installation ................................................................................................ 33

Trade Portal Post-Installation Required Configuration ........................................................................... 34




Section Seven: BPM Installation ................................................................................................................. 35

BPM Installation Overview ...................................................................................................................... 36

Performing the BPM Installation ............................................................................................................ 36

Section Eight: Variance PO Process Installation.......................................................................................... 38

5

VPO Installation Overview ...................................................................................................................... 39

Performing the VPO Installation ............................................................................................................. 39

Section Nine: Updating the Products .......................................................................................................... 41

Updating BuilderMT Products ................................................................................................................. 42

Updating the Server ............................................................................................................................ 42

Updating the Workstations ................................................................................................................. 43

Updating the Bmt.Net API................................................................................................................... 43

Updating the Trade Portal .................................................................................................................. 44

Updating the Mobile Scheduling ........................................................................................................ 44

Updating BPM ..................................................................................................................................... 44

Updating the VPO Process .................................................................................................................. 44

6

Introduction and System Requirements

Introduction Thank you for purchasing the BuilderMT Workflow Management Suite (WMS) software package. We

strive to provide the best support for BuilderMT products. Please take the time to read this installation

guide and follow the instructions.

Before beginning the installation of WMS, BuilderMT strongly recommends following the preparation

steps in each section.

Intended Audience

BuilderMT recommends that a system administrator or other experienced IT professional perform the

installation steps outlined in this guide.

The WMS 4.8 installation consists of the following separate processes:

WMS Server Installation

WMS Workstation Installation

.NET 2.0 and .NET 3.5, if not detected (this is a requirement for all WMS Workstations and may take several minutes to download)

Bmt.Net API Installation (this is optional and applies for those using Mobile Scheduling, Trade Portal and the VPO process)

Trade Portal Installation (this is optional and for those using Trade Portal)

VPO Process Installation (this is optional and for those using VPO)

BPM Installation

Mobile Scheduling Installation

It is required to complete the server installation before the workstation installation. When proceeding

through the server installation, some steps are applicable only if upgrading from Production

Management 3.1.7.x. These steps are flagged with “Upgrade Step Only.” If performing a new

installation, skip these steps. If upgrading an existing version of Production Management 3.1.7.x, make

sure to perform a backup of the server before performing the upgrade.

Citrix and Terminal Services Installations

The installation for both the server and workstation are exactly the same whether installing to a Citrix

machine or a Terminal Services machine. Follow either the Server or Workstation steps below, whether

using the Citrix or Terminal Services machine as a server or workstation. If using the Citrix or Terminal

Services machine for both the server and workstation (stand-alone installation), perform both the Server

steps and the Workstation steps on that same machine. Please refer to the respective Citrix and

Terminal Services documentation for installing software in these environments.

Compatibility with Sage Timberline Office®

The installation with Sage Timberline Office® requirements apply to clients integrating with Sage

Timberline Office accounting and estimating.

7

The WMS 4.8 compatibility with Sage Timberline Office estimating and accounting is the same as

previous versions of WMS 4.x, with the exception of added compatibility for Sage Timberline Office

accounting 9.5 and 9.6.

Note for Sage Timberline Office and BuilderMT Trade Portal Compatibility:

If the client is integrated with Sage Timberline Office and they will use the Trade Portal, then it is

required that the version of Sage Timberline Office accounting they are using is 9.4x or newer in order to

have functionality of the Payments tab.

System Requirements The guidelines below will help you prepare for installation. The following are minimum hardware

requirements for the Bmt.Net Framework, WMS Server (including stand-alone configuration) and WMS

Workstation.

IMPORTANT WINDOWS 2003 SERVER AND .NET 3.5 REQUIREMENTS FOR WMS 4.8.x:

Microsoft Corporation has mandated that Windows 2003 Server Service Pack 1 (SP1) be

installed, at a minimum, with .NET 3.5 framework. Microsoft Corporation does not support

Windows 2000 Server with the .NET 3.5 framework.

Because the Bmt.Net Framework 1.0, .NET 2.0 and .NET 3.5 are automatically installed with the

4.8.x version of WMS Server, clients are required to have Windows 2003 Server Service Pack 1

(SP1) installed, at a minimum. Additionally, Windows 2003 SP1 is the minimum operating

system requirement for the WMS 4.8.x Workstation. If either the WMS Server or WMS

Workstation does not meet the minimum operating system requirements, the installations

will terminate.

Note for Windows 2000 Server Clients or Windows 2000 Professional Workstation:

For customers not running Windows 2003 Server SP1 at a minimum, we will continue to provide WMS

version 4.5.17.x on CD for those not already on that version and not capable of upgrading to WMS

version 4.8.x.

8

WMS Server Requirements

Operating System .NET Frameworks

Processor Speed

Memory Disk Space

Microsoft Windows 2003 Server Service Pack 1 (SP1)

Microsoft Windows 2008 Server (32bit, 64bit)

Windows XP Service Pack 2 (SP2) Stand-alone only

Microsoft .NET 2.0*

Microsoft .NET 3.5*

*All frameworks are required prior to installation

2.0 GHz Pentium Processor

2 gigabyte (GB)

minimum

Recommended 3 gigabytes (GB)

Up to 500 MB of available

space may be required

Recommend installation to a

large data drive if available

Minimum Display: 800 x 600, 256 colors

Recommended Display: 1024 x 768 high color, 32-bit

WMS Workstation Requirements

Operating System .NET Frameworks Processor Speed

Memory Disk Space


Microsoft Windows 2008 Server Terminal Services (32bit, 64bit)

Windows7 (32bit, 64bit)

Windows XP SP2

Windows Vista**

Microsoft .NET 2.0*

Microsoft .NET 3.5*

*Both automatically installed by the Workstation Installation


Recommended 2 GHz Pentium Processor

1 gigabyte (GB)

Recommended 2 gigabyte (GB)

Up to 500 MB of

available space may

be required



** Check other vendors for software compatibility

9

Bmt.Net API / Trade Portal / Mobile Scheduling Requirements (IIS Web Server Required)

Operating System .NET Frameworks Processor Speed Memory Disk Space


Microsoft IIS version 5.1 or 6.0

Windows 2008 Server

Microsoft .NET 2.0*

Microsoft .NET 3.5*

*Both required prior to installation

IIS 5.1, 6.0, 7.0



2 gigabyte (GB)


Up to 500 MB of

available space

may be required




BPM (Business Process Management) Requirements (IIS Web Server Required)

Operating System

.NET Frameworks Processor Speed

Memory Disk Space


Microsoft IIS version 5.1 or 6.0

Microsoft .NET 2.0*

Microsoft .NET 3.5*

*Both automatically installed by the Installation



2 gigabyte (GB)


Up to 500 GB of available

space may be required to

store process state




10

Recommended Configuration

As with previous WMS 4.x installations, the server and workstation can be installed on the same

machine to create a stand-alone configuration. All of the other executables included in 4.8.x can also be

installed to the same machine as long as the requirements are met for IIS. The defaults contained in

each installation are designed for the stand-alone configuration. In a true production environment, the

recommended configuration is to have two separate server machines, one for WMS (commonly referred

to as the “BuilderMT Server”), and one for the web server, where the Bmt .Net Service Framework (for

BPM and Warranty Management), Bmt. Net API, Mobile Scheduling and Trade Portal should reside.

These two machines are separated by a firewall, which needs to have a port open to allow

communication to the Firebird database on the BuilderMT server.

Network security/integrity best practices strongly recommend having separate machines as reflected

above, one that houses the BMT database that is secure behind a firewall, and the web server that is

accessible from the Internet.

It is also acceptable to have Trade Portal on a separate web server from the Bmt.Net API, as long as that web server is configured to communicate with the Bmt.Net API. (The Bmt.Net API is the communication layer between the WMS database and the Trade Portal.)

11

Section One: WMS Server Installation

12

WMS Server Installation For installations shipped on a CD-ROM, the installation guide, BuilderMT Client ID, and password are

provided in the package. In this case, run the installation directly from the CD-ROM.

If the installation was downloaded in the form of a zipped file containing the server installation files,

unzip the files to a temporary directory (for example, C:\BuilderMT Install) and run the install from that

directory.

Server Installation Prerequisites

BuilderMT requires that these steps are completed prior to the WMS Server installation.

Schedule Installation during Non-production Hours. This installation requires a reboot of the server. The procedure should be performed during non-production hours in order to minimize potential interruption.

Always perform replication with Sage Timberline Office estimating before any installation or upgrade.

Always perform the Send to Sales procedure to clear the Sales Update log prior to any installation or upgrade.

Always perform a complete synchronization for wireless devices associated with WMS before any installation or upgrade.

Always perform a FULL BACKUP before installing any software (including WMS). It is recommended that backup files be saved to an alternate drive or media.

Windows Logon Requires Administrator Rights. All WMS Server Installations require an Administrator login or an operator with administration rights. Verify that the person installing is logged into the server as the Administrator. If proper rights have not been granted, the server installation process may not complete properly.

The Server Installation must be physically performed on the Server machine.

Do not install to a mapped drive on the server. The server must not be installed to any drive other than the local, physical drive, i.e. C:\Program Files\BuilderMT.

Review the directory structure. For the remainder of this install guide, the following directory examples will be used. BuilderMT applications will be installed onto a shared folder on the server.

o For the example, D:\Apps\BuilderMT, a partitioned D: drive on the server is located where all applications are installed. Clients on the network are mapped as a T: drive to the server share 'Apps'. The default Server Installation location is C:\ProgramData\BuilderMT. It is not required to install to this location; the installation provides the opportunity to redirect this path.

o In this example, the installation is directed to D:\Apps\BuilderMT\. o If installing both the server and workstation on the same machine, also known as a

stand-alone setup, run the Workstation setup after the server installation.

Server Installation Prerequisites for Server 2008 and Windows 7

BuilderMT requires that these steps are completed prior to the WMS Server installation when the

installation is being performed on Windows 7 or Server 2008 Operating Systems.

Data Execution Prevention (DEP). If this setting in Windows is turned on for all programs and services, it prevents the BuilderMT WMS Services from communicating to the licensing service.

13

The setting needs to be turned on only for essential Windows programs and services. Changing this setting will require a reboot of the server.

IE Enhanced Security Configuration (ESC). ESC must be turned off for Administrators and users prior to installing WMS.

Default Ports for WMS

The WMS default service configuration information for the BuilderMT Distributed Access Server can be

found on the WMS Services tab in the BuilderMT Enterprise Configuration Utility. This utility can be run

after WMS is installed from ..\BuilderMT\BmtNet\bin\BmtEnterpriseConfiguration.Exe.

Note: These are default configuration settings only. A qualified IT professional with your company

should make modifications to these settings as needed.

Begin the Installation Process CD-ROM

Insert the WMS Server Installation CD into the CD-ROM drive of the computer that is to be used as the

server.

If the auto-run screen does not appear, navigate to the WMS CD-ROM and double-click on the Setup.exe.

Downloaded .ZIP

If a .zip file was downloaded from the Internet:

Create a BMT Install folder on the server's local drive and extract the contents of the .zip file into that folder.

From the new BMT Install folder, run the Setup.exe file.

The BuilderMT WMS Installation Steps window is the launching platform for all activities associated with

the installation. Please follow the instructions for each section of the Installation Steps window.

Important Documents

Click View End User License Agreement to read the details of the license agreement that applies to this installation.

Click View Support Agreement to view details of the support agreement that applies to this installation.

Click What’s New in Version 4.8 to view the Release Notes for the software.

Pre-Installation Steps

If prior versions of WMS are detected, users may be required to perform one or more brief procedures

to ensure that the new installation runs smoothly. For each active (bold font) Pre-Installation step, click

on the link in the WMS software and follow the associated instructions given below in this guide.

If the Pre-Installation steps are dimmed in the software, proceed to Server Installation on page 14.

14

Note: If no prior versions of WMS are detected, no pre-installation steps are required, and these links

will be disabled.

Database Validation Check

WMS 4.8.x requires that all existing databases be validated for integrity prior to

installation. This procedure backs up the existing database and restores it after validation.

Click on Database Validation Check. 1.Note: If errors exist in the database, an error message will appear. Contact BuilderMT

Support, and do not continue with the installation until the issue is resolved.

When the validation procedure is complete, locate and delete the following files: 2. *.fbk *.fdb DO NOT REMOVE THE WMS.fdb file. The WMS.fdb file is the new production database.

Uninstall Interbase 6.5

The Interbase 6.5 database server engine must be removed prior to installing WMS 4.8.x.

Click on Uninstall InterBase 6.5 to initiate the Uninstall Procedure.

This is a silent uninstall process. The user is notified when Interbase 6.5 has been

successfully uninstalled.

Note: If an error message appears indicating that the program has not been removed,

contact BuilderMT Support for assistance before proceeding with the WMS 4.8.x

Installation.

Uninstall Production Management

1. Click on Uninstall Production Management. 2. In the Add/Remove Programs window, navigate to BuilderMT Production

Management System and click on it. 3. Click the Change/Remove button. 4. In the Uninstall window, select Automatic, then select Next to remove the program. 5. In the Perform Uninstall window, click Finish. 6. When the uninstall is complete choose Restart Later, then click Finish.

Performing the Server Installation

Note: The Server Installation must be performed prior to installing the WMS Workstation(s). Verify all

production users are logged off prior to starting these steps. Failure to ensure that all production users

are logged off can result in loss of data.

15

1. In the Installation Steps screen, click Perform Server Installation to begin the installation.

2. In the Server Install window, read the advisories, then click Next.

3. Read the End User License Agreement, then mark the checkbox to accept the terms and conditions of the agreement. Click Next.

If a previous installation is detected, the default path to the PMServer.ini file will be displayed.

Verify that the path is correct. Or

Use the Browse button to navigate to a different file.

When the correct location for the PMServer.ini file is displayed, click Next.

The Database Upgrade Required screen appears only if a previous version is found. It is required to upgrade one company database at a time to version 4.8 prior to installing the WMS Server.

4. Click the Run DB Upgrade Utility button to launch the Database Maintenance Utility.

Beginning in WMS 4.8.x, it is no longer possible to create new company databases, remove, or

upgrade existing company databases from a WMS workstation. All of these functions must be done

using the Database Maintenance Utility on the server.

For complete instructions on the Upgrade function within the Database Maintenance Utility, refer to

the WMS 4.8 online help: http://www.buildermt.com/pmonlinedocs. Search for the term “Database

Maintenance Utility.”

http://www.buildermt.com/pmonlinedocs

16

5. Select the company database to upgrade from the Company drop-down menu.

6. Under Company on the left, click the Logon link and log in to the Database Maintenance Utility.

7. Click the Upgrade link that appears under Maintenance on the left.

8. After the upgrade function has completed successfully, a prompt will appear saying the upgrade completed. Click OK. (Upgrade other databases as desired by repeating steps 5-8.)

9. Close the Database Maintenance Utility to resume the WMS Server installation and proceed to the next step. The server installation must complete in its entirety in order for the WMS workstations to connect.

NOTE: If a database upgrade fails, the database will be restored to its previous version and the WMS Server installation will close. Contact BuilderMT Support for assistance before proceeding with the WMS 4.8 Server Installation.

10. In the Select Installation Type screen, review the installation definitions, then select:

Standard Installation to initiate the installation and accept the recommended defaults. [Default program files directory: C:\Program Files\BuilderMT] [Default server directory: C:\Program Files\Firebird] Or

Custom Installation to configure data and paths associated with the installation (BuilderMT does not provide instructions for custom installations). Australian sample data is one of the custom options, therefore select Custom if this set of sample data is needed.

Note: BuilderMT strongly recommends that Custom Installations be performed only by qualified professionals who have experience with WMS software.

11. Click Next to proceed with the installation.

12. In the Start Installation window, click Next to install the software. Bmt.Net 1.0 is the first piece

of software installed.

13. If the File Version Conflict message appears, click Yes to All.

14. If the server does not have the Microsoft .NET 2.0 or 3.5 framework, the installation process will detect this and prompt the user run these .NET installations (required).

Click Next to proceed with the .NET 2.0 and/or 3.5 framework installation(s).

Read the End User License Agreement, then mark the checkbox to accept the terms and conditions of the agreement. Click Install.

17

The Setup Complete screen appears, recommending the administrator visit the Microsoft support center to retrieve the latest service packs and security updates for installation. Click Finish.

If neither .NET 2.0 or 3.5 existed, the next .NET setup will kick off.

IMPORTANT! Do NOT choose to restart the server at this time. Click Restart Later.

After all .NET installations complete, the WMS server installation resumes.

15. When the server components have been installed, you will be prompted to register (Internet connection required). In the Registration for licensing screen click Register Now to register the software. When the BuilderMT Product Registration screen opens: Update Users - Click Update. Or New Users – Click Yes, Register my products now. If prompted, enter the BuilderMT Client ID and Password included with the CD-ROM, then click OK.

16. If a message appears indicating that the system is “running in Demo mode,” scroll to the Server License (Production) pane, and click Register this system as a server.

17. In the Server Install successful installation screen, click Finish to complete the server installation. When prompted, Restart your computer.

18

Section Two: WMS Workstation Installation

19

Workstation Installation Overview Stand-alone - A workstation installation performed on the same machine on which the server has been

physically installed is known as a Stand-alone Setup.

Network - A workstation installation performed on any machine on which the server is not physically installed is known as a Network Setup. Aside from the initiation method, the Stand-alone Setup and Network Setup for workstations are essentially the same. Follow the instructions below to initiate either the Stand-alone Setup or Network Setup, then follow the Workstation Installation Instructions.

Workstation Installation Prerequisites

The steps below are prerequisites for the workstation installation. In order for BuilderMT to provide

support during workstation installation, these steps must be completed.

Map the server’s drive on each workstation. The server drive must be mapped on each computer that is to be used as a workstation, unless the workstation is housed on the same computer as the server (Stand-alone).

Schedule Installation for Non-production Hours. Because a reboot may be required after the workstation installation, the installation procedure should be scheduled during non-production hours.

All workstations must have the same drive mapping. All workstations running the WMS software must have the same drive mapping to the Server directory share. In other words, you cannot have a workstation mapped to T:\ and another workstation mapped to the same share as F:\. This will cause conflicts and will cause the software to work improperly.

UNC paths to run workstation installation setup from the server are not supported and will cause failures.

Paths resembling the following are not permitted:

\\server\Apps\BuilderMT\PMWinstall\WorkstationInstall\Setup.exe.

The Workstation installation executable that is located on the server under the workstation install directory cannot be moved from its original location. The executable must be run from the original directory in order to properly access the relative server information.

Initiating a Stand-alone Setup

1. From the CD-ROM auto-run application, in the BuilderMT Workflow Management Installation

Steps window, click Perform Workstation Installation (Optional).

Or

From either of the following sources, locate the WMSWorkstationInstall.exe and double-click on it.

WMS CD-ROM > Explorer > Explore CD-ROM. Program Files > BuilderMT > PMWinstall > WorkstationInstall.

20

Initiating a Network Setup

1. Using Windows Explorer, navigate to the mapped drive that houses the server, and locate the BuilderMT program file and open it.

2. Navigate to ..\BuilderMT\PMWinstall\WorkstationInstall, and double-click on the WMSWorkstationInstall.exe.

Performing the Workstation Installation

1. In the Workstation Install screen, select Next.

2. Read the BuilderMT End User License Agreement (EULA), then mark the checkbox to accept the terms and conditions of the license agreement.

3. Click Next.

4. In the Select Installation Type screen, review the installation definitions, then select: Standard Installation to initiate the installation and accept the recommended defaults. [Default program directory: C:\Program Files\BuilderMT] Or Custom Installation to configure data and paths associated with the installation (BuilderMT cannot provide instructions for custom installations).

5. Click Next to proceed with the installation.

6. In the Start Installation window, click Next to install the workstation. The Installing screen displays the install progress.

If the workstation does not have the Microsoft .NET 2.0 or 3.5 framework, the installation process will detect this and prompt the user run these .NET installations (required). Click Next to proceed with the .NET framework installation.

Read the End User License Agreement, then mark the checkbox to accept the terms and conditions of the agreement. Click Install.

The Setup Complete screen appears, recommending the administrator visit the Microsoft support center to retrieve the latest service packs and security updates for installation. Click Finish.

If neither .NET 2.0 or 3.5 existed, the next .NET setup will kick off.

Do NOT choose to restart the workstation at this time. Click Restart Later. The WMS workstation installation resumes.

7. When the Workstation Install screen appears, indicating the process has completed successfully, click Finish.

21

8. When prompted to restart the computer, click Cancel to restart at a later time.

9. In the workstation Install successful installation screen, click Finish to complete the workstation installation.

10. If prompted, Restart the workstation.

22

Section Three: Bmt.Net API Installation

23

Bmt.Net API Overview If installing from the Bmt.Net API installation files, navigate to

..\BuilderMT\PMWinstall\Installations\BMTNETAPIInstall folder. The installation directories can be

saved to a CD and copied to the web server if the installation files on the WMS server are not accessible

by the web server.

Two files are needed:

BMTNETAPIInstall.exe

Dotnetfx.exe

Bmt.Net API Installation Prerequisites for Server 2008 and Windows 7

BuilderMT requires that these steps are completed prior to the WMS Server installation when the

installation is being performed on Windows 7 or Server 2008 Operating Systems.

Data Execution Prevention (DEP). If this setting in Windows is turned on for all programs and services, it prevents the BuilderMT WMS Services from communicating to the licensing service. The setting needs to be turned on only for essential Windows programs and services. Changing this setting will require a reboot of the server.

IE Enhanced Security Configuration (ESC). ESC must be turned off for Administrators and users prior to installing WMS.

Performing the Bmt.Net API Installation 1. Access the folder on the server where the WMS Server Install was performed and browse to the

\BuilderMT\PMWinstall\Installations\BMTNETAPIInstall directory. Double-click the BMTNETAPIInstall.exe.

2. The BuilderMT – Bmt.Net API Setup welcome screen appears. Click Next.

3. Accept the default destination, or browse to a different location. Click Next.

4. In the Installation Configuration screen, if this is not a stand-alone installation, assign the Server Name Address by replacing localhost with the IP address of the server (Database Server) where the WMS Server Install was performed. Next set the BuilderMT Session Manager Port to the port that is configured for the WMS Server. This will always default to port 9005 unless you reconfigured that port using the BuilderMT Enterprise Configuration utility. Next set the port number to the setting of your Default Web site for which the current installation is being performed.

24

Bmt.Net API Defaults

Server Name Address: localhost

BuilderMT License Manager Port: 5000 Microsoft IIS Website Port: 80 Note: These are default configuration settings only. A qualified IT professional with your company should make

modifications to these settings as needed.

5. Under Accounting Integration, select Contract Manager if you are integrated with Explorer’s Contact Manager Product. Otherwise, leave the default option (Other or None) selected. Click Next.

6. Click Next.

7. In the Start Installation screen, click Next to begin. The Updating System progress bar displays.

8. When the Successfully Installed screen appears, click Finish to complete the installation.

25

Bmt.Net API Post Installation Steps 1. On the web server where you installed the Bmt.Net API, go into the Control Panel > Administrative

Tools > Internet Information Services utility.

2. Expand out the Default Website, locate the BuilderMT virtual directory folder and expand this folder.

3. Locate the SecurityService folder and click that folder to select it.

4. On the right side of the screen, you will see the list of files under this folder. Right-click on the SecurityService.asmx file and select Browse.

5. This will bring up the list of methods the SecurityService supports. Locate the CheckServiceStatus method and click that link.

6. This will display a screen with an Invoke button. Click Invoke to test the connection to the BuilderMT WMS Server. If the connection is successful, you will receive back a message that states Success. If there are problems with the connection, the error message will be displayed. You will need this error message when contacting BuilderMT support.

26

Section Four: Mobile Scheduling Installation

27

Mobile Scheduling Overview Mobile Scheduling transfers data directly to and from the User’s workstation or hand-held device

through the Bmt.Net API. The Mobile Scheduling installation file is found in the

..\BuilderMT\PMWinstall\Installations\MobileSchedulingInstall folder. The installation directory can

be saved to a CD and copied to the web server if the installation files on the WMS server are not

accessible by the web server.

These files include:

MobileSchedulingInstall.exe

Prerequisites

IIS (IIS 6 Compatibility must be installed if running IIS 7.5 or higher)

Active Server Pages as well as ASP.NET v2.0.50727 must be set to “Allow” under Web Service Extensions

Microsoft .NET Framework v3.5 must be installed

IP Addresses of the Web Server and the Database Server

Bmt.Net API must be installed (be sure to enter Database Server IP Address during the Bmt.Net API Install)

Physical Directory and IIS Virtual Directory

The Mobile Scheduling files physically get installed to the root web site as …\BuilderMT\MobileScheduling (typically C:\Inetpub\wwwroot\BuilderMT\MobileScheduling)

The Mobile Scheduling virtual directory will get created under the Default Web site under BuilderMT\MobileScheduling

Performing the Mobile Scheduling Installation

Note for Upgrade Users: When installing upgrades that include Mobile Scheduling improvements or

features, upgrade users must re-install the Bmt.Net API and Mobile Scheduling after performing the

WMS Server and WMS Workstation installations.

These installation executables are located in the BuilderMT > PMWinstall > Installations folder.

After installing the Bmt.Net API, return to the 1...\BuilderMT\PMWinstall\Installations\MobileSchedulingInstall folder and double-click the MobileSchedulingInstall.exe file.

Click Next in the Welcome to Mobile Scheduling Installation screen. 2.

28

Accept the default destination. Click Next. 3.

In the Configuration Settings screen, assign the IP Address of the Bmt.Net API Server in the first 4.field (this needs to be the external IP address of the server where the Bmt.Net API is installed). Also configure the port that the Bmt.Net API is running on that web server in the second field. Click Next.

In the third field, select the appropriate choice for the country code (United States (US), Canada (CA) 5.or Australia (AU). This ensures that the dates are displayed properly in the Portal. Click Next.

Click Next at the Start Installation screen. The Installation progress bar appears. 6.

When the Successfully Installed screen appears, click Finish to complete the installation. 7.

To access Mobile Scheduling, use http://webservername/BuilderMT/MobileScheduling. 8.

Mobile Scheduling Post-Installation Required Configuration

IIS Configuration (IIS 6 only)

Open IIS, browse to the “Default Website” and modify the “Default Web Site” Properties. 1.a. Check the “Enable Default Document” box on the Documents Tab. b. Make sure that “Default.aspx” is in the list of documents on the Documents Tab. c. Click Apply and Select ALL virtual directories that appear in the pop-up box if it appears and

apply. d. Select ASP.NET version 2.0.50727 from the drop-down list on the ASP.NET Tab. e. Restart the Website (Stop/Start).

File Permissions

Set File Permissions on the Web Server directories by adding the “LOCAL” NETWORK SERVICE group 2.(NOT the domain) with “Modify” privileges on the “C:\inetpub\wwwroot\buildermt\mobilescheduling\documents” directory and the “C:\inetpub\wwwroot\buildermt\mobilescheduling\images” directory.

Set File Permissions on the physical path for the Report Output folder specified in step 5 (example 3.“C:\inetpub\wwwroot\buildermt\mobilescheduling\documents”) with “Write” privileges for the user specified as the Anonymous User under Anonymous Authentication in IIS.

DB/WMS Server Configuration

Open the BuilderMT Enterprise Configuration utility and map Document Drives where Document 4.Attachments live by clicking on the “Configure Document Drive Mappings” link on the WMS Services tab and enter the drive letter and UNC path to the Network share where the Document Attachments are pointed.

29

Section Five: Superintendent Portal Installation

30

Superintendent Portal Overview Superintendent Portal transfers data directly to and from the Superintendent’s workstation through the

Bmt.Net API. The Superintendent Portal workstation installation files, including the executable, are

found in the ..\BuilderMT\PMWinstall\Installations\SuperintendentPortalInstall folder. The

installation directories can be saved to a CD and copied to the web server if the installation files on the

WMS server are not accessible by the web server.


SuperintendentPortalInstall.exe

Prerequisites







The Superintendent Portal files physically get installed to the root web site as …\BuilderMT\SuperintendentPortal (typically C:\Inetpub\wwwroot\BuilderMT\SuperintendentPortal)

The Superintendent Portal virtual directory will get created under the Default Web site under BuilderMT\SuperintendentPortal

Performing the Superintendent Portal Installation

Note for Upgrade Users: When installing upgrades that include Superintendent Portal improvements or

features, upgrade users must re-install the Bmt.Net API and Superintendent Portal after performing

the WMS Server and WMS Workstation installations.


After installing the Bmt.Net API, return to the 1...\BuilderMT\PMWinstall\Installations\SuperintendentPortalInstall folder and double-click the SuperintendentPortalInstall.exe file.

Click Next in the Welcome to Superintendent Portal Installation screen. 2.


31

In the Configuration Settings screen, assign the IP Address of the Bmt.Net API Server in the first 4.

field (this should be localhost). Also configure the port that the Bmt.Net API is running on that web server in the second field.

In the third field, select the appropriate choice for the country code (United States (US), Canada (CA) 5.or Australia (AU)). This ensures that the dates are displayed properly in the Portal. Click Next.

Click Next on the Start Installation screen. The Installation progress bar appears. 6.


To access Superintendent Portal, use http://webservername/BuilderMT/SuperintendentPortal. 8.

Superintendent Portal Post-Installation Required Configuration


Open IIS, browse to the “Default Website” and modify the “Default Web Site” Properties. 1.a. Check the “Enable Default Document” box on the Documents Tab. b. Make sure that “Default.aspx” is in the list of documents on the Documents Tab. c. Click Apply and Select ALL virtual directories that appear in the pop-up box (if it appears) and

then click OK. d. Select ASP.NET version 2.0.50727 from the drop-down list on the ASP.NET Tab. e. Restart the Website (Stop/Start).

File Permissions

Set File Permissions on the Web Server directories by adding the “LOCAL” NETWORK SERVICE group 2.(NOT the domain) with “Modify” privileges on the “C:\inetpub\wwwroot\buildermt\SuperintendentPortal\documents” directory and the “C:\inetpub\wwwroot\buildermt\SuperintendentPortal\images” directory.


Open the BuilderMT Enterprise Configuration utility and map Document Drives where Document 3.

Attachments live by clicking on the “Configure Document Drive Mappings” link on the WMS Services tab and enter the drive letter and UNC path to the Network share where the Document Attachments are pointed.

32

Section Six: Trade Portal Installation

33

Trade Portal Overview Trade Portal transfers data directly to and from the Trade User’s workstation through the Bmt.Net API.

The Trade Portal workstation installation files, including the executable, are found in the

..\BuilderMT\PMWinstall\Installations\TradePortalInstall folder. The installation directories can be

saved to a CD and copied to the web server if the installation files on the WMS server are not accessible

by the web server.


TradePortalInstall.exe

Dotnetfx.exe

Prerequisites







The Trade Portal files physically get installed to the root web site as …\BuilderMT\TradePortal (typically C:\Inetpub\wwwroot\BuilderMT\TradePortal)

The Trade Portal virtual directory will get created under the Default Web site under BuilderMT\TradePortal

Performing the Trade Portal Installation

Note for Upgrade Users: When installing upgrades that include Trade Portal improvements or features,

upgrade users must re-install the Bmt.Net API and Trade Portal after performing the WMS Server and

WMS Workstation installations.


After installing the Bmt.Net API, return to the 1...\BuilderMT\PMWinstall\Installations\TradePortalInstall folder and double-click the TradePortalInstall.exe file.

Click Next in the Welcome to Trade Portal Installation screen. 2.


34

In the Configuration Settings screen, assign the IP Address of the Bmt.Net API Server in the first 4.field (this should be localhost). Also configure the port that the Bmt.Net API is running on that web server in the second field.

In the third field, select the appropriate choice for the country code (United States (US), Canada (CA) 5.or Australia (AU)). This ensures that the dates are displayed properly in the Portal. Click Next.

Click Next on the Start Installation screen. The Installation progress bar appears. 6.


To access Trade Portal, use http://webservername/BuilderMT/TradePortal. 8.

Trade Portal Post-Installation Required Configuration


Open IIS, browse to the “Default Website” and modify the “Default Web Site” Properties. 1.f. Check the “Enable Default Document” box on the Documents Tab. g. Make sure that “Default.aspx” is in the list of documents on the Documents Tab. h. Click Apply and Select ALL virtual directories that appear in the pop-up box (if it appears) and

then click OK. i. Select ASP.NET version 2.0.50727 from the drop-down list on the ASP.NET Tab. j. Restart the Website (Stop/Start).

File Permissions

Set File Permissions on the Web Server directories by adding the “LOCAL” NETWORK SERVICE group 2.(NOT the domain) with “Modify” privileges on the “C:\inetpub\wwwroot\buildermt\tradeportal\documents” directory and the “C:\inetpub\wwwroot\buildermt\tradeportal\images” directory.


Open the BuilderMT Enterprise Configuration utility and map Document Drives where Document 3.Attachments live by clicking on the “Configure Document Drive Mappings” link on the WMS Services tab and enter the drive letter and UNC path to the Network share where the Document Attachments are pointed.

35

Go to Integration>Timberline Accounting>Accounting DB Settings and change the Drive Letter (i.e. 4.

“T:”) to the UNC path that points to the T: drive to insure that the Payments tab will work.

Section Seven: BPM Installation

36

BPM Installation Overview BPM is used to create custom processes that integrate to multiple back-end systems. The BPM

installation files are found in the ..\BuilderMT\PMWinstall\Installations\BPMInstall folder. This

installation will be performed on your web server.

Important! – When you perform upgrades to WMS, it is critical that you re-install BPM to ensure the

latest BPM components are installed that integrate to the Bmt.Net API.

Performing the BPM Installation

1. Run the BPMInstall.exe to begin the setup.

2. On the Welcome screen, click the Next button.

3. On the EULA screen, check the I accept checkbox after reading the license agreement and click the

Next button.

4. On the Installation Environment screen, please choose from the following two options:

Production BPM Server – Choose this option to install both the designer and BPM server.

OR

Development BPM Workstation (Designer Only) – Choose this option if processes will not be

deployed to this machine.

Click the Next button.

5. On the Production Server Licensing screen, please choose from the following two options:

Integrated with BuilderMT Workflow Management Suite – Choose this option if you already

have BuilderMT WMS installed on your network. BPM will connect to the already-existing

licensing service.

OR

Standalone BPM Install – Choose this option if BPM is the only product you have purchased.

Click the Next button.

6. On the Destination Location screen, choose the folder to which you wish to install (we recommend

the default) and click the Next button.

37

7. On the Start Installation screen, click the Next button.

8. On the Complete screen, click the Finish button.

38

Section Eight: Variance PO Process Installation

39

VPO Installation Overview VPO is used to create variance purchase orders from a web-based process. The VPO installation files are

found in the ..\BuilderMT\PMWinstall\Installations\BPMProcesses\BMTVPOProcessInstall folder.

This installation will be performed on your web server.

Performing the VPO Installation

1. Run the BMTVPOProcessInstall.exe to begin the installation process.

2. On the Welcome screen, click the Next button to continue.

3. On the Destination Location screen, click the Next button to continue.

4. On the VPO Process Settings screen, there are several items that need to be configured:

Process Name – You can configure the name of the process to be anything you wish. Enter the

name of the process that will show up on the top of each screen.

Variance Custom Description – If you wish to call a variance something else, you can configure

the terminology into this field.

Process Color Scheme - Select screen display color - Blue, Green, Gray, Orange, Red, Silver.

Default One-Time Phase Code - Allows the superintendent to add a custom item during the VPO

process. Create a new Phase/Item and Material Class in the Sage Timberline Office estimating

database, Replicate in WMS. In WMS (Purchasing - Purchasing Activity) assign the One-Time

Purchasing Activity to the appropriate JC Cost Code and Category.

The final step in the VPO process is Issue PO. For that reason, you may want to create a new JC

Cost Code called Miscellaneous and associate it with the One-Time Purchasing Activity. After

the Purchase Order has been issued, you can use the Edit Purchase Order function on the Send

to Accounting screen to change the assigned JC Cost Code before the Purchase Order is sent to

accounting.

(Note: The One-Time Item feature should only be used for items that will never be used again.

All other items should be added to the database.)

VPO Approval Threshold - Enter dollar amount. Any VPOs that are equal to or exceed this

amount will be sent to the Project Manager for approval. Upon approval by the Project

Manager, a Purchase Order will be issued in WMS. If the VPO is below this amount, a Purchase

Order will be issued upon completion of the VPO process.

40

Click the Next button to continue. Note: If you ever need to change any of these configuration

items you will need to re-run the installation.

5. On the Server Configuration Settings screen, there are several items to configure:

Internal Process Server Address – Because the VPO process will be accessed by personnel both

internal to the network and external to the network, the process needs to be configured

appropriately. The internal process server address is the name of the server onto which you are

loading the process. This can be a server name (MYWEBSERVER), IP Address (192.168…) or DNS

name (mydomain.com). This will be the internal address that is used to access the process.

External Process Server Address and Port – The external process server address is the address

of the server onto which you are loading the process externally. This can be an IP Address

(192.168…) or DNS name (mydomain.com). This will be the external address that is used to

access the process. Also, since the process will be accessed from outside of the firewall, you

need to configure which port will be opened on the firewall. This port needs to be configured

on your Default Web Site in Microsoft IIS.

Bmt.Net API Server Address and Port – Because the VPO process communicates with the

Bmt.Net API for data transfers, you must configure the process accordingly. Most clients will

have the Bmt.Net API installed on the same web server as you are installing the VPO process in

which case you can leave the address localhost. If you have the Bmt.Net API installed on

another web server, then enter that server name.

If you have changed the Default Web Site port in Microsoft IIS, then you will need to change the

port from the default 80 to whatever port you configured.

Click the Next button to continue.

6. On the Start Installation screen, click the Next button to continue.

7. On the Complete screen, you will have a process URL that will be displayed. Copy this URL to be

used in the browser to launch the VPO process. This URL will be the internal URL to launch the

process. If you want to launch it externally, replace the local server name (i.e. MYSERVER) with your

external address.

41

Section Nine: Updating the Products

42

Updating BuilderMT Products When BuilderMT releases new updates, they need to be downloaded and installed to maintain the most

updated functionality of the software. Below are the steps to follow to keep the product updated with

the latest release from BuilderMT.

After completing the WMS server installation from Section One, an update utility is installed that allows

the system administrator to check for product updates on a periodic basis. When updates are available

on the BuilderMT update server, the utility can download them and run the installation on the server.

Updating the Server

Server Update Prerequisites

Complete the following prerequisites prior to updating the server.

Ensure all users are logged out of WMS. 1.Before updating the server, make sure that all users are logged out of the software. If attempting to update the server while users are logged in, they will be disconnected and unable to save work in progress.

Caution: It is recommended that the server restart be performed only at a time when all production users are logged off. Failure to ensure that all production users are logged off can result in loss of data.

Read the Release Notes. 2.Before continuing with the update installation, read the release notes to fully understand how new updates will impact the organization. Check to see if the update requires a database upgrade, which will be stated in the release notes, in order to properly plan for the update.

Database Upgrades may be required. 3.If a database upgrade is required after the update, it is required to perform the upgrade from a workstation. To do this, log into a workstation, update the software by running it, and open the companies that will be impacted by the database upgrade.

From the server, click Start > BuilderMT > Check for BuilderMT Product Updates shortcut. This 4.launches the wizard that will walk through each step of downloading the updates.

On the Check for Updates screen, either select Next to begin the check for updates on the 5.BuilderMT update server, or set up Advanced settings while checking for updates.

Note: For advanced settings, configure the proxy settings for the software update wizard, add the

update to the startup group, and set an interval in days that the wizard will automatically check.

If the Add BuilderMT Update Check to Startup Group option was selected, each time the server

computer boots up, the updater silently checks the time elapsed since it last ran. If the number of days

43

elapsed is greater than the number entered in the Check Interval (days) field, then the updater opens

automatically.

To begin the check for updates, select Next. 6.

If unable to access the Internet or HTTP server from the client server, an error screen may appear.

Note: Make sure the appropriate Internet connection and user rights are available to disable a firewall.

If a connection problem exists, click on the Web Page for access to the BuilderMT support center.

When a successful Internet connection and access to an HTTP server outside the firewall are established,

the software updater will check for a valid support and maintenance contract with BuilderMT.

Note: If a support and maintenance contract has expired, the following error message may appear:

Updates will download only if a valid support and maintenance contract exists with BuilderMT.

If a valid support and maintenance contract exists and updates are available, a Release Notes screen 7.appears, listing the new features and enhancements for the software version. Select Next to continue with the download.

After reviewing the release notes, the next screen initiates the download. Select Next to continue. 8.

The updater will download the software updates while displaying a progress bar. 9.

Once the download is complete, a screen will appear that initiates the update installation. Select 10.Finish to begin the update.

Once the server installation update begins, follow the server installation section in this guide. The 11.update will read default settings so the update installation processes quickly.

If no updates are available on the BuilderMT update server, the “Update Checked!” message 12.appears. Select OK to finish with the updater.

Updating the Workstations

There are two ways you can update the workstations.

1. You can run the installation from the mapped drive off the server located under

..BuilderMT\PMWinstall\WorkstationInstall.

2. You can launch WMS on the workstation, and it will prompt you to upgrade the workstation.

When prompted to restart your computer during an upgrade, Do NOT restart.

Updating the Bmt.Net API

Updating the Bmt.Net API is necessary after a server upgrade in order for the Mobile Scheduling, Trade

Portal and VPO Process to work correctly. This is as simple as re-running the Bmt.Net API install over

itself on your web server. Please refer to the section Bmt.Net API Installation.

44

Updating the Trade Portal

Updating the Trade Portal is necessary after a server upgrade in order for the Trade Portal to work

correctly. This is as simple as re-running the Trade Portal install over itself on your web server. Please

refer to the section Trade Portal Installation.

Updating the Mobile Scheduling

Updating the Mobile Scheduling is necessary after a server upgrade in order for the Mobile Scheduling

to work correctly. This is as simple as re-running the Mobile Scheduling install over itself on your web

server. Please refer to the section Mobile Scheduling Installation.

Updating BPM

Updating the BPM is necessary after a server upgrade in order for the BPM to work correctly. This is as

simple as re-running the BPM install over itself on your web server. Please refer to the section BPM

Installation.

Updating the VPO Process

Updating the VPO Process is necessary after a server upgrade in order for the VPO Process to work

correctly. This is as simple as re-running the VPO Process install over itself on your web server. Please

refer to the section VPO Process Installation.