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

Transcription

1 1 Mi

2 2009 BuilderMT, LLC, 200 Union Blvd, Suite 500, Lakewood, Colorado USA 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 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. 2

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 Section One: WMS Server Installation WMS Server Installation Server Installation Prerequisites Server Installation Prerequisites for Server 2008 and Windows Default Ports for WMS Begin the Installation Process Important Documents Pre-Installation Steps Performing the Server Installation Section Two: WMS Workstation Installation Workstation Installation Overview Workstation Installation Prerequisites Initiating a Stand-alone Setup Initiating a Network Setup Performing the Workstation Installation Section Three: Bmt.Net API Installation Bmt.Net API Overview Bmt.Net API Installation Prerequisites for Server 2008 and Windows Performing the Bmt.Net API Installation Bmt.Net API Defaults

4 Bmt.Net API Post Installation Steps Section Four: Mobile Scheduling Installation Mobile Scheduling Overview Prerequisites Physical Directory and IIS Virtual Directory Performing the Mobile Scheduling Installation Mobile Scheduling Post-Installation Required Configuration IIS Configuration (IIS 6 only) File Permissions DB/WMS Server Configuration Section Five: Superintendent Portal Installation Superintendent Portal Overview Prerequisites Physical Directory and IIS Virtual Directory Performing the Superintendent Portal Installation Superintendent Portal Post-Installation Required Configuration IIS Configuration (IIS 6 only) File Permissions DB/WMS Server Configuration Section Six: Trade Portal Installation Trade Portal Overview Prerequisites Physical Directory and IIS Virtual Directory Performing the Trade Portal Installation Trade Portal Post-Installation Required Configuration IIS Configuration (IIS 6 only) File Permissions DB/WMS Server Configuration Section Seven: BPM Installation BPM Installation Overview Performing the BPM Installation Section Eight: Variance PO Process Installation

5 VPO Installation Overview Performing the VPO Installation Section Nine: Updating the Products Updating BuilderMT Products Updating the Server Updating the Workstations Updating the Bmt.Net API Updating the Trade Portal Updating the Mobile Scheduling Updating BPM Updating the VPO Process

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 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 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. 6

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 x on CD for those not already on that version and not capable of upgrading to WMS version 4.8.x. 7

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 Microsoft Windows 2003 Server Service Pack 1 (SP1) 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 1.0 GHz Pentium Processor Recommended 2 GHz Pentium Processor Memory 1 gigabyte (GB) Recommended 2 gigabyte (GB) Disk Space Up to 500 MB of available space may be required Minimum Display: 1024 x 768, 256 colors Recommended Display: 1024 x 768 high color, 32-bit ** Check other vendors for software compatibility 8

9 Bmt.Net API / Trade Portal / Mobile Scheduling Requirements (IIS Web Server Required) Operating System.NET Frameworks Processor Speed Memory Disk Space Microsoft Windows 2003 Server Service Pack 1 (SP1) Microsoft IIS version 5.1 or 6.0 Microsoft.NET 2.0* Microsoft.NET 3.5* *Both required prior to installation 1.0 GHz Pentium Processor Recommended 2 GHz Pentium Processor 2 gigabyte (GB) Recommended 3 gigabyte (GB) Up to 500 MB of available space may be required Windows 2008 Server IIS 5.1, 6.0, 7.0 Minimum Display: 1024 x 768, 256 colors Recommended Display: 1024 x 768 high color, 32-bit ** Check other vendors for software compatibility BPM (Business Process Management) Requirements (IIS Web Server Required) Operating System.NET Frameworks Processor Speed Memory Disk Space Microsoft Windows 2003 Server Service Pack 1 (SP1) Microsoft IIS version 5.1 or 6.0 Microsoft.NET 2.0* Microsoft.NET 3.5* *Both automatically installed by the Installation 1.0 GHz Pentium Processor Recommended 2 GHz Pentium Processor 2 gigabyte (GB) Recommended 3 gigabyte (GB) Up to 500 GB of available space may be required to store process state Minimum Display: 1024 x 768, 256 colors Recommended Display: 1024 x 768 high color, 32-bit ** Check other vendors for software compatibility 9

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.) 10

11 Section One: WMS Server Installation 11

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 o 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. In this example, the installation is directed to D:\Apps\BuilderMT\. 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. 12

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 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. 1. Click on Database Validation Check. 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. 2. When the validation procedure is complete, locate and delete the following files: *.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. 14

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: Search for the term Database Maintenance Utility. 15

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. 16

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. 17

18 Section Two: WMS Workstation Installation 18

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. 19

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. 20

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. 21

22 Section Three: Bmt.Net API Installation 22

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. 23