FH Web Installation Guide

(1)

(2)

Urbandale, IA 50322

FIREHOUSE Software® is a registered trademark of Xerox Government Systems, LLC. All rights reserved. Microsoft, MS, MS-DOS, Microsoft Visual FoxPro, and Microsoft Access are registered trademarks. Windows is a trademark of Microsoft Corporation. CAMEO is a registered trademark. iPad is a registered trademark of Apple, Inc. All other products or services mentioned in this manual are identified by the trademarks or service marks of their respective companies or organizations. Xerox disclaims any responsibilities for specifying which marks are owned by which companies or organizations.

FIREHOUSE Software is protected by the copyright laws that pertain to computer software. It is illegal to make copies of the Software except for backups. It is illegal to rent, lease, sublicense, or otherwise transfer any of the materials. It is illegal to remove or obscure pro-prietary notices. It is illegal to duplicate and distribute the Software by any other means, including electronic transmission. To protect trade secrets contained in the Software, you may not decompile, reverse engineer, dissemble, or otherwise reduce the Software to human per-ceivable form. You may not modify, adapt, translate, rent, lease, or create derivative works based upon the Software or any part thereof. Xerox warrants the original media are free from defects in material and workmanship, assuming normal use, for ninety (90) days from the date of purchase. Except for express warranty of the original media set forth above, Xerox grants no other warranties, express or implied, by statute or otherwise, regarding the media related materials, their fitness for any purpose, their quality, their merchantability, or oth-erwise. The liability of Xerox, under the warranty set forth above, shall be limited to the amount paid by the customer for the product. In no event shall Xerox be liable for any special, consequential, or other damages for breach of warranty.

© 2014 Xerox Government Systems, LLC.- Printed in the United States. All rights reserved. No part of this work covered by copyright hereon may be reproduced in any form by any means -- graphic, electronic, or mechanical -- including photocopying, recording, taping, or storage in any information retrieval system, without the written permission of the copyright owner.

(3)

Technical support

FH®_{Technical Support:} Phone: 800-921-5300, option 2 [email protected]

Sales contacts

Jim Brandariz

Phone: 800-796-1614, 530-621-0981 Fax: 530-626-8582

[email protected] AZ, CA, NV, OR, WA

Peter Eleftherakis

Phone: 888-362-4446, 508-362-4446 Fax: 508-362-5932

[email protected] CT, MA, ME, NH, NY, RI, VT, Ontario

Mike Rogers

Phone: 888-941-3473, 214-504-0242 Fax: 214-504-0244

[email protected] AR, KS, LA, MO, MS, OK, TX

Forest Nace

Phone: 800-285-8685 Fax: 724-283-9086

[email protected] DE, IN, KY, MD, NJ, OH, PA, VA, WV

Roger DeDoncker Rebecca Sanger

Phone: 800-921-5300, ext. 1 Fax: 515-288-4825

[email protected]

AK, AL, CO, GA, FL, HI, ID, IA, IL, MI, MN, MT, NC, ND, NE, NM, SC, SD, TN, UT, WI, WY, International

(4)

FIREHOUSE

Software License Agreement

Carefully read the following terms and conditions before installing software fromFIREHOUSE Software. Only an Authorized Representative of the purchaser should install the software. Installing the software indicates acceptance of these terms and conditions specified in the License Agreement.

Xerox Government Systems, LLC and the party who installs this software (“you”) hereby agree as follows:

1. Licensed Software:“Licensed Software” means the software component and modules ordered and paid for by you, as listed in Xerox’s client database of licensed products, and as evidenced by your customer receipt. Licensed Software includes all documentation relating to our software. It also includes any upgrades, modi-fications, and customizations (collectively, “Improvements”) to our software, should such Improvements be delivered to you at a later time.

2. End Users:“End User(s)” means (i) your employees with a need to access the Licensed Software; and (ii) third party consultants engaged by you who have a need to access the Licensed Software, and who are fulfilling legitimate business functions for you on your behalf.

3. Materials:This document contains links to downloaded files and applicable manual(s) relating to the Licensed Software.

4. License Grant:Xerox hereby grants a revocable, non-exclusive, non-transferable license to use the Licensed Software on a single microcomputer, in the United States of America. The number of End Users authorized to access the Licensed Software concurrently is reflected on your invoice and in this License Agreement. You may increase the maximum number of concurrent End Users by procuring additional licenses from Xerox based upon the then-current license fee schedule. You may not make use of any object code for any component(s) or modules(s) for which you have not expressly obtained a license for use under this Agreement. Any rights not expressly granted in this Agreement are expressly reserved. You agree not to (a) rent, lease, sublicense, assign or otherwise transfer the Licensed Software, including any of the materials or your rights hereunder, (b) remove or obscure our proprietary notices, (c) translate, alter, decompile or disassemble any of the materials, (d) copy any of the materials without our prior written consent, (e) use the software for other agencies. You shall have no right to access, copy or otherwise use the source code for software licensed under this license. You are prohibited from causing or permitting the reverse engineering, disassembly or decompilation of the ware licensed under this license. You are prohibited from modifying, improving or otherwise enhancing the soft-ware licensed under this license.

5. Terms:This license is effective until terminated. You may terminate it at any time by destroying the materials and all copies of any material made from the original materials and notify Xerox immediately. This license ter-minates automatically upon breach of any of the conditions of this license. Upon termination, you agree to des-troy all copies of the materials. Use of the materials without a valid license of the materials is unauthorized and may subject you to monetary penalties.

6. Confidentiality:You receive the right to use the Licensed Software and materials as specified herein, but you do not become the owner of the Licensed Software and materials. The Licensed Software and materials are exclusive property of Xerox and are protected by trade secret, copyright, and trademark law. You acknowledge that the materials are Xerox property and contain valuable, confidential, unpublished information developed by Xerox at a great expense. You agree to protect the materials from unauthorized reproduction, distribution, dis-closure, or use of publication. You may not transfer any materials or software to anyone or entity without the writ-ten consent of Xerox authorized personnel.

(5)

8. Export Laws:You may not export the Licensed Software and agree to comply with all laws, regulations, orders or other restrictions of the U.S. Export Administration Regulations.

9. Warranty:We warrant the downloadable files to be free from material defect in normal use for 90 days from the date of receipt of materials. We do not warrant the error-free operation of the Licensed Software contained in the downloadable files, or that such Licensed Software will meet your requirements. The Licensed Software is licensed "as is". We will, however, attempt to correct or bypass any actual reproducible and significant error in the software, provided you notify us and describe it in writing within 90 days from the date of receipt of the mater-ials, and we will, within a reasonable time, at our option, provide either a corrected copy or work around instruc-tions. This does not cover altered software or require us to customize our software to meet your hardware or operating system requirements. Section 11 specifies your exclusive remedy for any breach by us of this section. No dealer, company, or person is authorized to expand, alter this section or any other provision of this agree-ment. Any such agreement will not bind Xerox. XEROX MAKES NO OTHER WARRANTIES WHATSOEVER, EXPRESS OR IMPLIED, WITH REGARD TO THE SOFTWARE LICENSED UNDER THIS LICENSE, IN WHOLE OR IN PART. XEROX EXPLICITLY DISCLAIMS ALL WARRANTIES OF MERCHANTABILITY AND OF FITNESS FOR A PARTICULAR PURPOSE. XEROX EXPRESSLY DOES NOT WARRANT THAT THE LICENSED

SOFTWARE, IN WHOLE OR IN PART, WILL BE ERROR FREE, WILL OPERATE WITHOUT INTERRUPTION OR WILL BE COMPATIBLE WITH ANY HARDWARE OR SOFTWARE OTHER THAN THE EQUIPMENT. LICENSEE WAIVES ANY CLAIM THAT THE LIMITED WARRANTY SET FORTH IN THIS SECTION OR THE REMEDY FOR BREACH OF SUCH LIMITED WARRANTY FAILS OF ITS ESSENTIAL PURPOSE.

10. Limitation of Liability:XEROX’S LIABILITY IN CONNECTION WITH THE LICENSED SOFTWARE UNDER THIS LICENSE, OR ANY OTHER MATTER RELATING TO THIS LICENSE WILL NOT EXCEED THE FEE THAT YOU ACTUALLY PAID TO XEROX FOR THE SOFTWARE GIVING RISE TO THE LIABILITY. REGARDLESS

WHETHER ANY REMEDY SET FORTH HEREIN FAILS OF ITS ESSENTIAL PURPOSE OR OTHERWISE, IN NO EVENT WILL XEROX BE LIABLE TO YOU FOR ANY SPECIAL, INCIDENTAL, OR CONSEQUENTIAL

DAMAGES, WHETHER BASED ON BREACH OF CONTRACT, TORT (INCLUDING NEGLIGENCE), PRODUCT LIABILITY, INDEMNIFICATION, OR OTHERWISE, AND WHETHER OR NOT XEROX HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. YOU ACKNOWLEDGE THAT XEROX HAS SET ITS FEES AND ENTERED INTO THIS LICENSE IN RELIANCE UPON THE LIMITATIONS OF LIABILITY AND THE

DISCLAIMERS OF WARRANTIES AND DAMAGES SET FORTH IN THIS LICENSE, AND THAT THE SAME FORM AN ESSENTIAL BASIS OF THE BARGAIN BETWEEN THE PARTIES.

11. Remedy:In the event that Xerox breaches this agreement, your sole remedy is to notify us of such breach within the applicable warranty period and we will at our sole option, either cure the breach or refund the license fee paid to us for the materials. In no event will Xerox be responsible for any damage beyond the amount of the license fee or for any indirect, special, incidental, consequential or similar damages or profits to you or any other person, or entity, regardless of the legal basis, even if Xerox has been advised of the possibility of such dam-ages, except to the extent applicable state law specifically prohibits such exclusion.

12. General (System Only):This license shall be governed by laws of the State of Iowa. All prior correspondence oral or written including without limitation, all understandings with respect to the Licensed Software or materials relative thereto are hereby superseded. This license constitutes your and our entire agreement and under-standing regarding the Licensed Software and materials relative thereto.

General (Evaluation Only):This evaluation program is provided free of charge to the registered requestor of the evaluation software and is to be used solely as an evaluation copy.

(6)

Soft-Table of Contents

Introduction 1

The servers and the client computer relationship 2

FH Web server system requirements 4

SQL server system requirements 5

Client system requirements 6

Checklist for installing FH Web 7

Request temporary and permanent license files 8

Install FH Enterprise 10

Install FH Web 11

(Windows Server 2008) Determine the OS bit level on your FH Web server 11

Download files needed for the installation 13

Install the FH Web components 14

Run FHWebComponentSetup.exe 18

Set Index.html as the default document, and add MIME types if necessary 22

(IIS 6.0) Set Index.html as default document 22

(IIS 6.0) Set MIME types 24

(IIS 7.0) Set Index.html as default document 27

(IIS 7.0) Set MIME types 29

Place the temporary license file in the installation directory 31

Disable automatic Windows updates 32

Configure an FH Web server 33

Map the FH Web icon to the FH Enterprise client 33

Set up session shutdown, printers, and check security 35

Access FH Web from a client computer 38

Place the permanent license file in the installation directory 42

Manage FH Web after the installation 43

Troubleshooting your installation 44

Failed to communicate with the Application Publishing Service 44

(7)

Licensing failure 49

Printer issues 49

Connection failed. The server cannot create a new session 49 Connection failed. The number of users allowed on the server has already been reached 50

Users unable to log in after update 50

(8)

Introduction

TheFIREHOUSE Software Web Installation Guideis designed to help you install FH®_{Web, or} to update your current FH Web installation to the newest version.

FH Web is a version of FH Enterprise that can be installed on a workstation with Internet access, and client computers can connect to this server and run FH Enterprise in a web browser, instead of requiring the FH Enterprise client software to be installed on individual client computers. This feature is particularly useful for accessing FH from home or from a mobile computer, such as a Toughbook in the fire truck.

FH®_{Enterprise is a fire department records management software package that maintains a SQL} database of information on a server where client computers can access it.

Note:

l The free evaluation version of FH Web, which is a functional installation with all available modules, expires 90 days after installation. However, you can not export state information in evaluation mode.

l Before installing FH Web, visithttp://fhweb.firehousesoftware.com/updates.htmlfor access to FH Web support bulletins.

l Because of the number of customization capabilities in FH Web, you may want to contact FH technical support and schedule an installation with a technician's assistance.

Additional information on FH Web is available in the (FIREHOUSE Software Web Edition Administrator's Guide), which can be downloaded from

http://www.fire-housesoftware.com/pdf/FH_Web_Administrator_Guide.pdf, or accessed as online help in the FH Web Administrator's Guide.

FH®_{technical support staff is available to answer your questions by telephone or email. Technical} support hours are from 7:00A.M. to 7:00P.M. Central time, Monday through Friday, and from 8:00 A.M. to 12:00P.M. on Saturday. Call 800-921-5300, option 2. You can also send an email to [email protected].

(9)

The servers and the client computer relationship

You will need at least three separate computers for a basic installation of FH Web.

l A FH Web server, which runs the installation of FH Web, FH Web Connection Manager, and web services,

l A SQL server that maintains the FH Web data in a SQL database and communicates with the FH Web server.

l One or more client workstations, which communicate with the FH Web server. A client workstation only needs an Internet web browser to access and run FH Web.

The FH Web Connection Manager controls client access to the FH Web server.

Caution:SQL Server should be run on a different computer than the FH Web Server.

Users on client computers view the normal FH interface through a web browser, and their com-puters send and receive FH data on the SQL server through the FH Web server.

The servers should be fast computers that can be assigned a unique address. The SQL database server should not be a computer that is also used as a file server. Ideally, it should be dedicated to hosting the database engine and the FH database. If necessary, the server can also host other SQL databases.

(10)

If you need to add additional FH Web servers to support the number of client computers access-ing the FH data, you also need to add an additional server to act as a relay server/load balancer. This relay server accepts incoming client connections and directs them to the FH Web server that currently has the lightest processing load.

WARNING:Do not cache in the FH Web configuration.

More information on load balancing an FH Web installation is available in the

FIREHOUSE Software Web Edition Administrator's Guide, which can be downloaded from http://www.firehousesoftware.com/pdf/FH_Web_Administrator_Guide.pdf, or accessed as online help in theFH Web Administrator's Guide.

(11)

FH Web server system requirements

Note:When you are planning to use FHnet with FH Web, the FHnet client component runs on the same server as FH Web. As a result, the system requirements for the FH Web server in this configuration are different than those for use with FH. Information the system requirements for running FHnet and FH Web on the same server is available at

http://www.fire-housesoftware.com/webhelp/FHnet/, underFHnet Hardware Planning Guide → FH Web large installation hardware requirements.

When you are planning to use FH with FH Web, the FH Web server requires one of the following Windows operating systems:

l Windows Server 2008 Standard or Enterprise with Service Pack 2 (32-bit and 64-bit) l Windows Server 2008 R2 Standard or Enterprise (64-bit)

WARNING:Computers upgraded from 32-bit systems to 64-bit systems have demonstrated problems and are not recommended.

The server must have TCP/IP installed as a network protocol.

The server must have an open port (by default, ports 80 and 491 are used). Microsoft Internet Information Server (IIS) 6.0 or later is required.

The FH Web server (or the FH Web load balancing server) must have Web services installed and active.

You must have unique Windows logons with modify rights to the FH program directory (by default,

C:\FIREHOUSE Software) for each user accessing FH Web.

Note:

l Where applicable, these operating systems are supported with or without the Security Rol-lup Package.

l FH Web includes support for WoW64 (Windows 32-bit on Windows 64-bit), which allows 32-bit applications to run on 64-bit versions of Windows.

l FH Web supports VMware ESXi and Hyper-V in Windows Server 2008 R2. The FH Web server requires the following hardware.

Component Minimum Recommended

RAM 512 MB, plus 10 MB of RAM for each FH Web client computer

1 GB or more

Hard disk space 80 GB of free disk space onC:\ More than 80 GB

Your hardware requirements may be higher than listed above, based on the number of concurrent users, other applications running on the server, server configuration, and network configuration. All

(12)

continuous user interaction. “Light” is defined as a user running one application with intermittent user interaction.)

The color depth of the server should be greater than 256 colors; 16 million colors is recommended. If you add a relay server for load balancing to your FH Web installation, the relay server must have Web services installed and active.

SQL server system requirements

The SQL server hosting the FH database used with FH Web is supported on the following oper-ating systems:

l Windows 7 l Windows 8

l Windows Server 2008 l Windows Server 2008 R2

Note:Extended support for environments and products that have reached Microsoft's end of mainstream support is available if you subscribe to eitherFIREHOUSE Software's Gold or Platinum support program. Information on the FH Support Programs is available at

http://www.firehousesoftware.com/pdf/FH_Support_Program.pdf. For networking, Microsoft .NET Framework 2.0 is required.

For a Web browser, use Microsoft Internet Explorer 10.0 or later. To manage your FH database, use Microsoft SQL Server 2012.

The hardware requirements for the server depend on the SQL software package you install to man-age your FH Enterprise database. Hardware requirements for SQL Server are available from Microsoft athttp://www.microsoft.com/sql/, or from your local Microsoft reseller. Your actual hard-ware requirements may be higher, based on the number of concurrent users or other applications running on the server, server configuration, and network configuration.

Tip:To qualify for U.S. General Services Administration (GSA) pricing, be sure to specify that you are a government entity when purchasing your SQL software package. You may save money by purchasing hardware and software as part of a package.

Note:If you use FH to collect data from multiple departments, such as collecting state

NFIRS transaction files or county EMS incident reports from area agencies, you should exceed the recommended hardware requirements if possible.

(13)

Client system requirements

FH Web supports the following browsers on client computers. l Internet Explorer 10.0 or later

Note:FH Web Edition is supported on Internet Explorer 11.0 in compatibility mode.

l Mozilla Firefox 24 Extended Support Release (ESR) or later, on Windows and Linux

Note:Only the Windows clients and the Mozilla Firefox and Internet Explorer browsers are fully supported. FIREHOUSE Software technical support will provide best-effort support for the other clients. FH Web Edition is not supported on Google Chrome.

Client computers access FH Web from a Web browser that supports one of the following clients. l The Mozilla Firefox client is available to Windows client computers.

l The Microsoft ActiveX client is available to Windows client computers running Internet Explorer.

WARNING:To successfully install this ActiveX plug-in, the user at the client computer must modify rights toC:\WINDOWS\Downloaded Program Files\. By default, only Power Users and Administrators have this permission.

l The Windows client is a 32-bit Windows application that can be manually installed and run on most Windows client computers.

Note:

l TCP/IP must be installed as a network protocol.

l The color depth of the client must be greater than 25; 16 million or greater is recommended.

(14)

Checklist for installing FH Web

Caution: Below is a high-level checklist of the steps you need to install FH Web for the first time. Detailed information for the steps below are available in the following pages of the FIREHOUSE Software Web Installation Guide.

Tip:Print this page off and check off the items below as you accomplish them.

(If you purchased your copy of FH Web) Verify that you received an email from

FIREHOUSE Software technical support, containing download links and a PDF file listing your serial number and an activation code

Verify that you have adequate hardware to support FH Web and your chosen version of MS SQL Server.

Request temporary and permanent license files for FH Web.

Install FH Enterprise on the FH Web server and SQL server as described in the FIREHOUSE Software Enterprise Installation Guide.

Install the FH Web application on the FH Web server.

(Windows Server 2008) Determine the OS bit level on your FH Web server. Download files needed for the installation.

Install the FH Web components. SetIndex.htmlas default document. (Safari or Firefox) Set MIME types.

Place the temporary license in the FH Web installation directory. Disable automatic Windows updates on the FH Web server. Configure the FH Web server.

Map the FH Web icon so that it launches FH Enterprise. Set up printers and check security.

Configure FH Web components. Access FH Web from a client computer.

(15)

Request temporary and permanent license files

FH Web requires a license file to run. You can use a temporary license file to run FH Web while waiting for a permanent license file to be generated and sent to you.

Note:If you plan to have multiple FH Web servers in your configuration, you need to do the steps below on each FH Web server, and obtain a separate permanent license file for each server. The same temporary license can be used on all the FH Web servers.

WARNING:The FH Web license is machine-specific and is based on the server's host name,

which must not exceed 15 characters. If you move FH Web to another server, the license file will not work.

1. Log on to the FH Web server as an administrator.

2. Verify that the host name of the FH Web server is fewer than 15 characters. 3. ChooseStart → Run.

TheRundialog box appears.

4. InOpen, typecmd, and then clickOK. A DOS command window appears.

(16)

5. At the prompt, type:

ipconfig /all > C:\host.txt

Thehost.txtis created on the C: drive, containing the server host information. 6. Close the DOS window.

7. Create an email [email protected] include the following text in the body of the email.

New Install

<Your department's name> <a contact email address>

Please send the current temporary FH Web license and create a permanent FH Web license based on the attached 'Host.txt' file.

Example: New Install

Johnsville Fire Department [email protected]

Please send the current temporary FH Web license and create a permanent FH Web license based on the attached 'Host.txt' file.

8. Attach thehost.txtfile to the email. 9. Send the email.

You will receive a reply with the temporary license file, and then you will later receive a second email with the permanent license file.

Caution:Save the first email for use after installing FH Web. The directory you need to save the license file into does not exist yet.

(17)

Install FH Enterprise

Because FH Web is a version of FH Enterprise, you must first install FH Enterprise, and then add the FH Web components for client computers to access FH Enterprise through an Internet browser.

In a normal FH Enterprise installation, you install the FH Enterprise client on each computer that will access the SQL database server. In FH Web, you install the FH Enterprise client on the FH Web server in your configuration, and client computers access the FH Web server, which in turn accesses the SQL database server.

Caution:In FH Web, you do not install the FH Enterprise client on the individual client com-puters.

An FH Enterprise installation An FH Web installation

1. Download theFIREHOUSE Software Enterprise Installation Guidefrom http://www.fire-housesoftware.com/pdf/FH7EnterpriseInstall.pdf, or access it at

http://www.fire-housesoftware.com/webhelp/FH/Default.htm, underFH Installation, Update, Upsizing, and Administration Guides → FH Enterprise → Installing FH Enterprise.

2. Follow the instructions in theFIREHOUSE Software Enterprise Installation Guideto install and configure FH Enterprise on the FH Web and SQL database servers.

Caution:Do not forget that references to client computers in theFIREHOUSE Software Enterprise Installation Guideshould be thought of as references to the FH Web server.

WARNING:Be sure to install FH Enterprise as an INI installation, not as a registry install-ation, when the appropriate screen in the FH Enterprise installation wizard appears. If FH Enterprise is installed as a registry installation, you will need to uninstall it and reinstall it as an INI installation.

(18)

Install FH Web

You also need to install FH Web on every FH Web server in your configuration. The FH Web Server does not have an automated installer, and must be installed manually.

Note:

l The FH Web server host port is set to port491. If you access the Internet from a client behind a firewall, or if you use a router, you may need to open port491to use FH Web. l Internet Information Server (IIS) 6.0 or later is a system requirement for FH Web, and must

be installed before you install FH Web.

(Windows Server 2008) Determine the OS bit level on your FH Web

server

If you are using Windows Server 2008 as your operating system or the FH Web server and are unsure whether the OS is 32-bit or 64-bit, you need to determine the bit level so that you can down-load and install the appropriate.msifiles for FH Web Server.

1. ClickStart, and then right-clickComputerin the menu that appears, and then choose

(19)

TheSystemwindow appears.

2. UnderSystem, forSystem type, note whether it displays32-bit Operating Systemor

64-bit Operating System. 3. Close theSystemwindow.

(20)

Download files needed for the installation

Note:When you purchased FH Web, you were sent an email from FIREHOUSE Software with a link for downloading a.ZIPfile containing the FH Web components you need to install. You will need this email to perform the steps below.

You will also need to download the.exefiles from theFIREHOUSE Software ftp site.

1. Open the email you were sent from FIREHOUSE Software with a link for downloading a

.ZIPfile containing the FH Web components you need to install.

2. Follow the directions in the email for downloading and unzipping the file to a location on your computer.

3. In a Web browser, download the.exefile you need that corresponds to your operating system.

If you have this Use this link

32-bit OS http://www.firehousesoftware.com/downloads/tLXfSBwk/ FHWebServer/48/fhweb-host.windows_x86.exe

64-bit OS http://www.firehousesoftware.com/downloads/tLXfSBwk/ FHWebServer/48/fhweb-host.windows_x64.exe

TheFile Downloaddialog box appears.

4. ClickSaveand specify a location for the file on the hard drive of the FH Web server. TheDownload Completedialog box appears.

5. Close the dialog box, and then close browser window.

(21)

Install the FH Web components

1. Navigate to the location where you downloadedfhweb-host.windows_xOS-bit num-ber.exeand double-click it.

A message that FH Web is preparing the Install Shield wizard appears, and then closes automatically after a moment.

TheInstall Shield wizardappears, displaying the Welcomescreen.

2. ClickNext >.

(22)

4. SelectI accept the terms in the license agreement, and then clickNext >. TheDestination Folderscreen of the wizard appears.

5. (Optional) ClickChangeand use the file browser that appears to select a different loc-ation for the FH Web installloc-ation directory.

6. ClickNext >.

(23)

TheInstalling FH Web Edition Hostscreen of the wizard appears.

Part of the way through the installation, theHardware Installationdialog box appears.

Note:If you are prompted for permission to install the drivers by the server's user account control (UAC), grant the necessary permissions. This request appears three times.

(24)

The installation continues, and then theInstallShield Wizard Completedscreen appears.

9. ClickFinish.

TheFH Web Edition Host Installer Informationdialog box appears.

10. ClickYes.

(25)

Run

FHWebComponentSetup.exe

TheFHWebComponentSetup.execopies a pair of critical FH Web files to the FIREHOUSE Software installation directory.

Caution:Any time you update your version of FH, you will need to perform the steps below again, to copy the critical FH Web files back to the FIREHOUSE Software installation directory. The version number of these files must match the version number of your current FH Enterprise installation.

1. (If you have not done so already) Download theFIREHOUSE Software Enterprise Installation Guidefromhttp://www.firehousesoftware.com/pdf/FH7EnterpriseInstall.pdf, or access it athttp://www.firehousesoftware.com/webhelp/FH/Default.htm, underFH Installation, Update, Upsizing, and Administration Guides → FH Enterprise → Installing FH Enterprise.

2. Follow the update instructions in theFIREHOUSE Software Enterprise Installation Guideto update FH Enterprise on the FH Web and SQL database servers.

Caution:Do not forget that references to client computers in the

FIREHOUSE Software Enterprise Installation Guideshould be thought of as ref-erences to the FH Web server.

3. Navigate into the location where you unzipped the.ZIPfile containing the FH Web com-ponents that you downloaded earlier, and then into theFHWeb\FHWebfolder.

4. Double-clickFHWebComponentSetup.exe.

(26)

5. (Optional, if you are sure there is only one installation of FH on the machine) SelectSkip automatic search for existing installations.

6. ClickNext >.

Depending on whether you selectedSkip automatic search for existing installations, theSelect Locationscreen orInstallation Locationscreen of the wizard appears.

(27)

7. Do one of the following.

If this screen appeared Do this

Select Location l From the list, select the path the FH Enterprise client you installed on the FH Web server.

Installation Location l ClickBrowse, and then use the file browser that appears to navigate to the location of your FH installation.

Note: You must double-click the name of the install-ation folder, and the path at the top of the file browser must include the folder name. Clicking the folder once does not update the path in the file browser.

8. ClickNext >.

(28)

The final screen of the wizard appears.

10. ClickFinish.

11. Continue withSet Index.html as the default document, and add MIME types if necessary, on page 22.

(29)

Set

Index.html

as the default document, and add MIME types if

necessary

Depending on which version of Internet Information Services (IIS) you are using, the steps for set-tingIndex.htmlas the default document and for adding MIME types are different.

l Depending on which version of IIS you are using, do one of the following.

Version Do this

6.0 (IIS 6.0) Set Index.html as default document, on page 22. 7.0 (IIS 7.0) Set Index.html as default document, on page 27.

(IIS 6.0) Set

Index.html

as default document

1. ChooseStart → Administrative Tools → Internet Information Services (IIS) Man-ager.

TheInternet Information Services (IIS) Managerwindow appears.

2. In the left pane, expandFH Web server name→ Web Sites → Default Web Site. 3. In the left pane, right-clickfhweb, and then choosePropertiesin the menu that appears.

(30)

4. Click theDocumentstab.

5. ClickAdd.

TheAdd Content Pagedialog box appears.

6. InDefault content page, typeIndex.html, and then clickOK.

Index.htmlappears at the bottom of the list on theDocumentstab. 7. SelectIndex.html, and then clickMove Upuntil it is the first item in the list.

The order of items in this list determines the order in which default documents are presen-ted to client computers.

8. ClickOK.

9. Depending on whether you use Safari or Firefox as a browser, do one of the following.

Do you use

(31)

(IIS 6.0) Set MIME types

FH Web uses.xpiand.dmgextensions for client computers that use Safari or Firefox as a browser. For these plug-ins to run, IIS 6.0 requires that you have a document with an extension that does not have a registered MIME type on that server. Additional information on this require-ment is available in "IIS 6.0 does not serve unknown MIME types," at

http://sup-port.microsoft.com/kb/326965.

1. (If you have not done so already) ChooseStart → Administrative Tools → Internet Information Services (IIS) Manager.

2. In the left pane, right-clickFH Web server name, and then choosePropertiesin the menu that appears.

(32)

TheMIME Typesdialog box appears.

4. Scan the list under Registered MIME types (file extensions)for the.dmgand.xpi

file extensions.

5. (If both file extensions are not yet registered as MIME types) Register the file extensions as MIME types.

a. ClickNew.

TheMIME Typedialog box appears.

b. InExtension, type.xpior.dmg.

(33)

e. In theMIME Typesdialog box, verify that the new MIME type appears in the list. f. (If necessary) ClickNewagain, and then repeat steps b-e to register the second file

extension as a MIME type.

6. In theMIME Typesdialog box, clickOK. 7. In thePropertiesdialog box, clickOK.

8. In the left pane, right-clickFH Web server name, and then chooseAll Tasks → Restart IISin the menu that appears.

TheStop/Start/Restartdialog box appears.

9. ClickOK.

10. Close theInternet Information Services (IIS) Managerwindow.

11. Continue withPlace the temporary license file in the installation directory, on page 31.

(34)

(IIS 7.0) Set

Index.html

as default document

1. ChooseStart → Administrative Tools → Internet Information Services (IIS) Man-ager.

TheInternet Information Services (IIS) Managerdialog box appears.

2. In the left pane, expandFH Web server name→ Sites → Default Web Site. 3. In the left pane, clickfhweb.

The middle pane updates to display the contents of the folder. 4. Scroll down in the middle pane and double-clickDefault Document.

(35)

The middle and right panes update to display information about setting default documents.

5. In the middle pane, selectindex.htmlfrom the list. 6. In the right pane, clickMove Up.

A confirmation dialog box appears.

7. ClickYes.

8. ClickMove Upuntilindex.htmlis at the top of the list in the middle pane. 9. Close theInternet Information Services (IIS) Managerdialog box.

10. Depending on whether you use Safari or Firefox as a browser, do one of the following.

Do you use Safari

or Firefox? Do this

No 1. Continue withPlace the temporary license file in the installation directory, on page 31.

(36)

(IIS 7.0) Set MIME types

FH Web uses.xpiand.dmgextensions for client computers that use Safari or Firefox as a browser. For these plug-ins to run, IIS 7.0 requires that you have a document with an extension that does not have a registered MIME type on that server.

1. (If you have not done so already) ChooseStart → Administrative Tools → Internet Information Services (IIS) Manager.

2. In the left pane, selectFH Web server name.

The large right pane is replaced by a middle pane and a narrower right pane. 3. Scroll down in the middle pane and double-clickMIME Types.

(37)

The middle and right panes update to display information about MIME types.

4. Scan the list in the middle pane for the.dmgand.xpifile extensions.

5. (If both file extensions are not yet registered as MIME types) Register the file extensions as MIME types.

a. ClickAdd.

TheAdd MIME Typedialog box appears.

b. InFile name extension, type.xpior.dmg.

Caution:If a file extension is already registered as a MIME type, do not enter it again inFile name extension.

c. InMIME type, typeapplication/octet-stream. d. ClickOK.

e. In the middle pane, verify that the new MIME type appears in the list.

(38)

Place the temporary license file in the installation directory

Early in the installation process, you emailed ahost.txtfile [email protected] received a temporary license file in return. Now that you have installed FH Web, you can place this license file in the appropriate directory. The temporary license file is not machine-specific. If you have mul-tiple FH Web servers in your configuration, you can save the same temporary license file to each FH Web server.

Note:You will need to replace this temporary license file later with the permanent one, when it is sent to you.

1. Open the email with the temporary license file attachment.

2. Save the attached license file intoFH Web installation directory\Programs.

By default,theFH Web installation directoryis located inC:\Program Files\ACSXer-ox\FH Web Edition Server\Programs.

Note:If you specified a different program directory during the installation of FH Web, you will need to modify the path toFH Web installation directoryaccordingly.

3. Check the date and time stamp on the file, or open the license file and, in the comment section at the top of the file, look for the note that lists the expiration date of the license file.

Example:

# NOTE: This is a DEMO license and will expire and become # non-functional on September 04, 2011

4. Compare the time stamp on the file or the expiration date in the comment to today's date, and determine how many more days the temporary license file is valid.

The temporary license file is generated by a third-party vendor and provided to

FIREHOUSE Software once a month. The temporary license file expires 30 days after it is generated by the vendor; depending on today's date, the license is valid for the remaining number of days from its generation date.

Note:If the remaining time on the temporary license expires before your permanent license file arrives, contact FH technical support and ask for the next temporary license from the third-party vendor.

5. Restart the FH Web license manager for the license to take effect. a. ChooseStart → Control Panel.

TheControl Panelwindow appears. b. Double-clickAdministrative Tools.

(39)

Managerlisting.

e. Right-clickFHweb Edition License Managerand then selectRestart. The service restarts.

6. Continue withDisable automatic Windows updates, on page 32.

Disable automatic Windows updates

You need to disable the automatic installations Windows security updates, as they sometimes conflict with FH Web and can cause unexpected issues. Compatibility updates for FH Web that resolve these issues are released periodically, and you can manually install the Windows security updates whenever the FH Web compatibility updates are available.

1. Right-clickMy Computerand choosePropertiesfrom the menu that appears. TheSystem Propertiesdialog box appears.

(40)

Configure an FH Web server

Once you have installed FH Web on the FH Web server, you need to configure it for your envir-onment.

Map the FH Web icon to the FH Enterprise client

1. ChooseStart → All Programs → FH Web Edition Server → Tools → Connection Manager.

TheConnection Managerdialog box appears, showing the Sessionstab in the right pane.

2. In the left pane, expandAll Serversand then select the FH Web server you want to work with.

TheProcessesandApplicationstabs appear next to theSessionstab. 3. Click theApplicationstab.

(41)

4. ClickAdd.

TheAdd Applicationdialog box appears.

5. InDisplay Name, typeFHWeb.

WARNING:If the display name is anything exceptFHWeb, unexpected results may may occur. If you have multiple FH Enterprise databases and need to have a different name for the FH Web icon, contact FH technical support for assistance renaming the icon.

6. ClickChange Icon. A file browser appears.

7. Navigate to the installation directory for the FH Enterprise client on the FH Web server, select the FH executable file, and then clickOpen.

Example:C:\FIREHOUSE Software\FH.EXE

The image besideChange Iconin the dialog box changes from a blue box to the FH icon.

This icon will appear to represent the FH Web application wherever it exists on the FH Web server.

8. InExecutable Path, click the lookup button and use the file browser that appears to navigate to the installation directory for the FH Enterprise client on the FH Web server, select the FH executable file, and then clickOpen.

TheStart Directoryfield populates automatically, based on the path inExecutable Path. 9. InCommand-Line Options, type/WEBAPP.

(42)

Set up session shutdown, printers, and check security

1. In theConnection Managerdialog box, chooseTools → Host Options. TheHost Optionsdialog box appears, set to theSession Startuptab.

2. SelectSession.

3. SelectWarning period, and then change the value inminutesto10.

4. Verify thatGrace periodis selected, and then change the value inminutesto5. 5. UnderDisconnected sessions terminate, selectAfter, and then change the value in

(43)

6. Click theClient Accesstab.

(44)

8. Click theSecuritytab.

9. Confirm thatIntegrated Windows authenticationis cleared. 10. ClickOK.

11. Close theConnection Managerdialog box.

(45)

Access FH Web from a client computer

The first time a client computer accesses the FH Web server, web browser plug-ins that run on the client computer are automatically downloaded from the FH Web server and installed on the client computer. These applications run in conjunction with the Internet browser, or can be run as a nat-ive stand-alone Windows application. You can also choose to download and run a client-side application on Windows, Mac, and Linux client machines, to access FH Web without a web browser.

The URL to access FH Web from a client computer ishttp://FH Web server IP address or domain name/fhweb/index.html.

Note:The/fhwebportion of the address is not required if the FH Web directory is set as the default home directory. Information on setting the/fhwebsub-directory as the default directory is available in the Microsoft IIS documentation.

1. Send an email containing the following information to the staff who will be using FH Web. l The URL for FH Web, using either the FH Web server's IP address or the name of the

domain the server resides in.

Example:http://192.100.255.28/fhweb/index.html

l (Internet Explorer) Information that their Internet browser security settings must allow or prompt to allow the downloading of ActiveX controls.

WARNING:The ActiveX plug-in installs automatically on the client computer at

C:\WINDOWS\Downloaded Program Files\. If the user at the client com-puter does not have Power User rights to this location, the ActiveX components will not install.

2. On a client computer, in an Internet browser, enter the URL for FH Web.

The FH Web home page appears, displaying a list of logon options. Which option you select depends on the kind of browser you are using and your printing capabilities.

(46)

FH Web does not support the following printers: l "All-in-one" (fax, copy, print) printers l Lexmark Z and X series ink jet printers l HP LJ 1000; HP LJ 1150

l HP LJ 3100 family l HP CLJ 1500 (color)

l Printers which require a licensing agreement when they are configured.

Note:The Windows client can be downloaded by clickingUseful Linkson this page, clickingFH Web Logonon the next page, and then clickingWindows Clienton the following page.

3. Depending on your Internet browser and your printing ability, click one of the options to launch FH Web.

The first time you access the FH Web server with Internet Explorer, across the top of the Web page, are prompted to allow the download of an add-on component.

If you have downloaded this component already, theConnect to FH Web Serverdialog box appears.

(47)

4. (If prompted to install the plug-in) Do the following.

a. Click the prompt message and then chooseInstall ActiveX Control.

An installation dialog box appears.

b. ClickInstall.

When the installation completes, theConnect to FH Web Serverdialog box appears.

5. InUser nameandPassword, type your network username and password, and then click

Logon.

Note:FH Web allows users three invalid logon attempts before shutting down the logon process.

The first time you log into FH Web, FH Enterprise will launch, expand the database, cre-ate settings, and more. A dialog box prompting you log out and restart FH Enterprise appears.

6. (If you are prompted to log out and restart) ClickOK, and then in a Web browser on the cli-ent computer, re-cli-enter the URL for FH Web.

(48)

FH Enterprise launches again, and prompts you for your FH username and password.

8. InUser nameandPassword, type your FH username and password, and then clickOK. The FH Enterprise user interface appears, exactly as it would if you were running it without FH Web, with no visible browser buttons.

Note:The Windows task bar lists two browser sessions for FH Web: the

(49)

WARNING:Closing the browser window that contains the FH Web session also ends FH Enterprise.

When you access FH Web from a client with print services, FH Web loads all printers installed on the client computer and installed at the FH Web Server. If the client work-station includes printers that are not installed at the server, printing is not available on those printers until you change settings in the Connection Manager.

Information on printer settings in the Connection Manager is available in the

FIREHOUSE Software Web Edition Administrator's Guide, which can be accessed as online help athttp://www.firehousesoftware.com/webhelp/FHWeb/Default.htm, or down-loaded fromhttp://www.firehousesoftware.com/pdf/FH_Web_Administrator_Guide.pdf.

Place the permanent license file in the installation

Manage FH Web after the installation

Information on managing FH Web is available in theFIREHOUSE Software Web Edition Admin-istrator's Guide, which can be which can be accessed as online help at

http://www.fire-housesoftware.com/webhelp/FHWeb/Default.htm, or downloaded from http://www.firehousesoftware.com/pdf/FH_Web_Administrator_Guide.pdf.

(51)

Troubleshooting your installation

If you encounter the following issues during your installation of FH Web, you may be able to troubleshoot and correct them yourself.

Failed to communicate with the Application Publishing Service

Issue After you install FH Web on the FH Web server, and then try to start the FH Web Con-nection Manager, an error message appears stating that there is a failure to com-municate with the Application Publishing Service.

Explanation An FH Web service did not start automatically as expected.

Workaround 1. In the error message, clickOK.

TheConnection Managerdialog box appears.

2. Close theConnection Managerdialog box. The error message dialog box reappears. 3. ClickOKagain.

4. ChooseStart → Run. TheRundialog box appears.

(52)

5. InOpen, typeservices.msc, and then clickOK. TheServicesdialog box appears.

6. In the right pane, scroll down and right-clickFH Web Edition Application Pub-lisher, and then chooseStartfrom the menu that appears.

TheService Controldialog box appears as Windows attempts to start the ser-vice.

The service will start successfully, or a new error message appears.

7. (If a new error message appears) Do the following.

(53)

The client and the server are not the same version

Issue You are using Internet Explorer on the client computer to access FH Web, and the fol-lowing error message appears.

The client and the server are not the same version.

Explanation The client computer is using an ActiveX plug-in for accessing FH Web that is not the same as the version of FH Web installed on the FH Web server. The correct version will not download to the client computer if you do not have Power User permissions to

C:\WINDOWS\Downloaded Program Files\. You may also have downloaded a newer version of the plug-in on your own than the version FH Web supports.

Workaroun-d

1. Open Internet Explorer.

2. ChooseTools → Internet Options.

TheInternet Optionsdialog box appears, displaying theGeneraltab.

(54)

TheTemporary Internet Files and History Settingsdialog box appears.

4. ClickView objects.

(55)

7. Close theDownloaded Program Fileswindow.

8. In theTemporary Internet Files and History Settingsdialog box, clickOK. 9. In theInternet Optionsdialog box, clickOK.

10. Ask your system administrator to verify that you have Power User security per-missions onC:\WINDOWS\Downloaded Program Files\.

11. In Internet Explorer, access FH Web again as normal.

The correct version of the ActiveX plug-in downloads automatically from the FHWeb server.

The version numbers of the client and server are not the same

Issue You are using Internet Explorer on the client computer to access FH Web, and the fol-lowing error message appears.

The version numbers of the client and server are not the same. Contact your System Administrator.

Explanation The client computer is using an ActiveX plug-in for accessing FH Web that is not the same as the version of FH Web installed on the FH Web server. The correct version will not download to the client computer if you do not have Power User permissions toC:\WINDOWS\Downloaded Program Files\. You may also have down-loaded a newer version of the plug-in on your own than the version of FH Web sup-ports.

Workaround This is the same problem described inThe client and the server are not the same version, on page 46.

l Follow the steps inThe client and the server are not the same versionto resolve the situation.

Unable to connect to “””

Issue You are using a Web browser on the client computer to access FH Web, and the fol-lowing error message appears.

Unable to connect to “””. Verify that the server address is correct.

Explanation The client computer is unable to contact the FH Web server because it does not recognize the server's host name.

Workaround If you are using the correct IP address or machine name of the FH Web server in your URL to the FH Web server, you may need your system administrator's assist-ance to establish communication between the client computer and the FH Web server.

(56)

The application service is not running on “”

The application service is not running on “”. Contact your system administrator.

Explanation The FH Web server is not running on port 491, the Application Publishing Service is not running, or the firewall is blocking the port.

Workaround l Ask your system administrator for assistance to establish communication between the client computer and the FH Web server.

Licensing failure

Licensing failure. Please contact your system administrator.

Explanation An issue has occurred with your license file, and can involve a number of different things.

Workaround l Contact FH technical support for assistance resolving the issue.

Printer issues

Issue You are using a Web browser on the client computer to access FH Web, and an error message involving your printer or print driver appears.

Explanation An issue has occurred with your printing capabilities, and can involve a number of dif-ferent things.

Workaround l Contact FH technical support for assistance resolving the issue.

Connection failed. The server cannot create a new session

(57)

troller.

2. ChooseStart → Run. TheRundialog box appears.

3. InOpen, typeipconfig /flushdns. 4. ClickOK.

5. From the client computer, try to access FH Web again as normal.

6. (If the error message appears again) Contact FH technical support for assist-ance resolving the issue.

Connection failed. The number of users allowed on the server has

already been reached

Connection failed. The number of users allowed on the server has already been reached.

Explanation The maximum number of sessions setting in the FH Web Connection Manager has been reached.

Workaround l Do one or both of the following.

o _{Wait until another user logs off FH Web before trying to access it again.} o Contact your FH sales representative and increase the number of licensed

users that can access the FH Web server at the same time.

Users unable to log in after update

Issue FH Web has been updated, and you are using a Web browser on the client computer to access FH Web, when an error message appears.

(58)

User-specific settings have been created

User-specific Settings Have Been Created. Please Logout and Log Back In.

Explanation ThePathvalue for the current user is not correct in the registry.