Install and Upgrade Guide. Front Office v7.2

c Install and Upgrade Guide Front Office v7.2

Contents 1.0 Introduction... 3 2.0 Prerequisites... 3 3.0 New Install... 4 4.0 Upgrade... 6 5.0 Post Install/Upgrade Validation... 8 6.0 Applying a Service Pack... 9 7.0 Uninstall... 10 8.0 Appendices... 11 8.1 Appendix A Software Requirements... 11 8.2 Appendix B Upgrading from previous versions of Front Office... 12 8.3 Appendix C What the Configurator does in a new install... 13 8.4 Appendix D What the Configurator does on an upgrade... 14 8.5 Appendix E Manual Configuration of Image Upload... 16 8.6 Appendix F Manual Configuration of Public Web Service... 17 8.7 Appendix G Side by Side Install... 18 8.8 Appendix H Load Balanced Install... 19 8.9 Appendix I Error in Email Task... 19 8.10 Appendix J Check Configuration of Windows Service... 20 8.11 Appendix K Upgrade to.net 4... 21 8.12 Appendix L Installing Under Web Root... 23 8.13 Appendix M - Manually changing the Database Connection String... 24 Page 2

1.0 Introduction There are four components in a Front Office install: 1. Web Site 2. Public Web Service 3. Windows Service 4. Database There are a number of different ways the components can be distributed, but the main focus of this guide is the two-server install: The standard install scenario is a two server install, with a Web Server hosting the web site, public web service and windows service, and a database server hosting the database. The two server install is the focus of this install guide. Other configurations are supported 1, in particular: 1. Side by Side install - Multiple independent Front Office systems installed on the same hardware. This configuration is covered in detail in appendix 8.7. 2. Load balanced install - A load balanced install has a single database server and database, but multiple instances of the web site, public web service and windows service, which provide load balancing and redundancy. This configuration is covered in detail in appendix 8.8. 2.0 Prerequisites It is assumed that the person installing Front Office has a basic knowledge of IIS, Windows Services and SQL Server. Front Office can be installed on a Windows Server 2003 or Windows Server 2008 platform. Detailed software requirements are given in section 8.1. 1 Please contact support@biomni.com for further information on specific alternative implementation models Page 3

The prerequisites for each component are: 2.1.1 Database Microsoft SQL Server 2005 or Microsoft SQL Server 2008 manual install At least 5 GB free disk space for data and 2 GB for logs 2.1.2 Web Site & Public Web Service Server running IIS with ASP.Net enabled manual install Microsoft.NET Framework version 4 manual install Microsoft WSE 3.0 runtime installed by Configurator Microsoft Report Viewer 2010 installed by Configurator At least 1 GB free disk space 2.1.3 Windows Service Microsoft.NET Framework version 4 manual install Access to an SMTP server At least 1 GB free disk space 3.0 New Install Installing and Configuring Front Office is a three step process: This section focuses on the first two steps of this process. Post install configuration of Front Office is covered in section 5.0. The Front Office install is packaged as a single executable, Front Office 7.2.exe. Double clicking on the exe launches windows installer, which copies all the relevant files onto disk. By default the install location is C:\Program Files\Biomni\Front Office 7.2, though this can be changed. The install produces the following folder structure: Page 4

After the windows installer has run, the Configurator is launched automatically. If you need to start the configurator manually, double click on Configurator.exe in the root of the install location. The configurator is a wizard which asks for a number of parameters required to configure the system, such as Database name, Web Site name etc. Once these parameters have been entered the configurator configures IIS, installs the database, windows service, WSE 3.0 and Report Viewer. At this stage it should be possible to log onto the website via the shortcut in the Start Menu, with the credentials: User ID: Admin Password: password Once logged in to Front Office, the remainder of the system configuration is performed in the web site. Navigate to the Admin->Configuration Check screen. This screen lets you examine the configuration of the system, and is discussed further in section 5.0 In detail the installation process is as follows: 1. Installation should be run on the web server or application server. Installation should NOT be run on the database server 2. Launch Front Office 7.2.exe and after accepting Terms and Conditions select a directory into which the components should be installed. The default is C:\Program Files\Biomni\Front Office 7.2. 3. Click Install. Once the installation has completed click Configure, to launch the Configurator. 4. Select Installation - click on Install a New Front Office System 5. Select Components leave all checkboxes checked; click next 6. New Install Configuration Options first select the IIS Web Site to install under. Then choose the Site Name, which will be used for the virtual directory and windows service name. Also select a Base Currency and Language. The base currency cannot be changed after install, so please check this carefully. You may also choose to Install Sample Data, which will populate the database with a set of Sample Data designed to illustrate the capabilities of Front Office. 7. Application Connection select the database server, and enter the Database name, web username and web password. These credentials will be used to create a database login and Page 5

database user, and in the connection strings for the web site, public web service and windows service. 8. Database Installer Connection select the credentials that the installer will use to create and build the database. The user may have either Windows or SQL Server authentication, but must have System Administrator privileges for SQL Server. The configurator will create the database during the install. If the database already exists the install will fail. 9. Confirm Options this screen gives a summary of what the configurator is going to create. If you want to change anything click the button in the top left corner to go back though the configurator wizard. If you are satisfied, click Install to begin the installation 10. Once the install in complete, click on the hyperlink to login, or uses the link in All Programs/Biomni/Front Office 7.2/. Log in using User ID: Admin Password: password You will be forced to change the password after login. 11. In the website, navigate to Admin->Support->Configuration Check. This page summarizes the configuration of the system, and checks that it is configured correctly. See section 5.0 for further details about this page. 4.0 Upgrade Upgrading Front Office is a three step process: This section focuses on the first two steps of this process. Post upgrade validation of Front Office is covered in Section 5.0. Upgrading from any recent version of Front Office should be straight forward. Upgrading from an older version of Front Office is more complex and is described in section 8.2. Before upgrading Front Office make a backup of the database. The Recovery Model should be set to Simple during upgrade. For large databases (10GB plus) the upgrade may take several hours to complete. We recommend setting file growth for both mdf and ldf files to 500MB for a balance between speed of upgrade and disk space usage. The database can be shrunk after upgrade to release the log file space, then a database maintenance plan run to ensure indexes are not fragmented and that statistics are up to date. Recovery Mode and file growth settings should be reverted to their previous settings. Page 6

An upgrade of Front Office uses the same executable as a new install, Front Office 7.2.exe. Double clicking on the exe launches windows installer, which copies all the relevant files onto disk. By default the install location is C:\Program Files\Biomni\Front Office 7.2, though this can be changed. An upgrade of Front Office puts a new set of files on the hard disk in a new location it does not replace the existing install. After the windows installer has run, the Configurator is launched automatically. If you need to start the configurator manually, double click Configurator.exe in the root of the install location. The configurator is a wizard which asks for a number of parameters required to upgrade the system, such as Database name, Web Site name etc. Once these parameters have been entered the configurator will: Upgrade the database. Repoint the website virtual root to the new code, and copy the connection string from the old website. It will also copy the z-override file which is used for customer styling of the website. Repoint the public web service to the new code, and copy the connection string from the old public web service. Install a new windows service pointing at the new code. Copy the connection strings and email settings from the old windows service. Installs WSE 3.0 and Report Viewer prerequisites, if they are required. At this stage it should be possible to log onto the website via the shortcut in the Start Menu. Login using the Admin user, and navigate to the Admin->Configuration Check screen. This screen let you examine the configuration of the system. It is discussed further in section 5.0. Once you are confident that the system has upgraded successfully, you can uninstall the old version via Control Panel -> Add or Remove Programs. This will remove the old windows service, and the old files on the hard disk. In detail the upgrade process is as follows: 1. Backup the existing database and set its recovery mode to simple. 2. Install the new version of Front Office using Front Office 7.2.exe. 3. At the Configure stage, click Upgrade a Front Office System. 4. Select Components Select the components which are installed on the server. Click next. 5. Upgrade Website and Public Web Service - Select the website virtual root to upgrade, and select the public web service virtual root to upgrade. If the server does not have a public web service, select (None) for this option. You will have to configure a public web service manually as described in section 8.6. Click next. 6. Upgrade Windows Service Enter a name for the windows service instance. This name is used to distinguish different windows services on the system. The full service name will be FrontOfficeService7.2$<InstanceName>. Select the old windows service you wish to upgrade, this is where the connection string will be copied from. Click next. 7. Upgrade Database Choose the database server, and database you wish to upgrade. Select the authentication method for the upgrade this is the user that the installer will run the upgrade as. Click next. 8. Confirm Options This screen summarizes the parameters you have entered. Check the details carefully. If you want to change anything click the button in the top left corner to go back though the configurator wizard. If you are satisfied, click Install to begin the upgrade. 9. Once the install in complete, click on the hyperlink to login, or use the link in All Programs/Biomni/Front Office 7.2/. Log in as Admin. Page 7

10. In the website navigate to Admin->Support->Configuration Check. This page summarizes the configuration of the system, and checks that it is configured correctly. See section 5.0 for further details about this page. 11. Once you are confident that the system has upgraded correctly you may uninstall the old version via Control Panel -> Add or Remove Programs. This will remove the old windows service, and the old files on the hard disk. 5.0 Post Install/Upgrade Validation After installation or upgrade, check that the system is configured correctly and configure the email settings for the system. This can be done via the Configuration Check screen: Navigate to Admin->Configuration Check 5.1.1 Server Tab Check the Windows Services. This section shows the status of windows services which are pointing at the Front Office database. Each windows service writes heartbeat information into the database, every 5 minutes. If the database has not received a heartbeat within 7 minutes this will be detected and the service highlighted in red. In the default install a single windows service is configured for each database. This service should write three records into the windows service table. It is possible to configure the system with multiple windows services pointing at a single database, a configuration useful for redundancy. In this scenario each service will write three rows into the service table, so if there are two windows services, six records will be displayed. After upgrade or manual reconfiguration of the windows services, the table may contain records for services that are no longer active. To remove these records click the Clear All button; this clears the entire table but active services will insert new records in the table when they next update their heartbeat. See also section 8.10, which describes checking the configuration of the windows service on the server where it runs. Check the web root address. This should be the URL of the home page of Front Office, as seen by a user of the system. This setting is used when constructing emails which hyperlink into Front Office. Changes can be made via Admin-> System Configuration. Check the Public Web Service URL. If this URL is incorrect the web page will display an error message. Changes can be made via Admin-> System Configuration. Checks include: (1) Public web service can be contacted via the URL. (2) Web server and public web service are the same version (Assembly Version in the table). (3) Web site and public web service are pointing at the same database. Page 8

5.1.2 Base Settings Tab Check that the base settings for Front Office are appropriate. This includes System Language, System Time Zone and Country Code. Changes can be made via Admin-> System Configuration. Base system currency is also shown, though this is set at install time, and cannot be changed subsequently. 5.1.3 Email Tab Configure SMTP settings for outbound email by clicking the Edit SMTP Settings. On an upgrade these settings should have been migrated forward. It is however still worth checking that they are correct. Review core email addresses for the system. The Administrator Email is set by amending the Admin user ID via Organization -> User; the Support Team Email and From Email Address is set up via Admin-> System Configuration. Send test email. Click on the Send Test Email button to send a test email from the Front Office system. For the email to be sent successfully a windows service must be running, the email task must be enabled and the SMTP settings must be correct. Check the Email Queue. Queued emails can be viewed via the Email Queue button. The email queue will show any error encountered sending the email. When the mail is sent successfully it is removed from the queue. If your server is not fully up to date with Windows updates, you may get an error sending email - see Appendix 8.9. 6.0 Applying a Service Pack The Front Office Service Pack updates a single Front Office instance to the latest service pack release; details of the service pack changes can be found in the Front Office 7.1 Service Pack Contents.pdf. By default the patch will be applied to the website located in \Program Files\Biomni\Front Office 7.1\, or, elsewhere if Front Office was originally installed to a custom location. If updating sites that were installed using the Side by Side install method, refer to the section Applying a Service Pack to a Side by Side (Manual) Install (below). 6.1.1 Applying a Service Pack 1. Copy the Service Pack onto the web server. 2. Log into web server as Administrator. 3. Run Front Office 7.1.xxxx Service Pack.msp. 4. For each load balanced web server repeat steps 1 3. 5. Login to Front Office as a supervisor and click on the Complete System Update link on the home page; this will apply any database changes. 6.1.2 Applying a Service Pack to a Side by Side (Manual) Install 1. If the Front Office Service has been installed, the service should be stopped (Biomni Front Office Service in services). 2. Copy the contents of the Front Office 7.1.xxxx Service Pack for Manual Install folder over the Front Office 7.1 site. Page 9

3. Restart the Front Office Service. 4. Login to Front Office as a supervisor and click on the Complete System Update link on the home page; this will apply any database changes. 6.1.3 Applying a Service Pack when Front Office Service is running on a separate Application Server If you are running a separate application server for the Front Office Service you must also apply the service pack to this install. If you have any questions, contact support@biomni.com. 7.0 Uninstall To uninstall a Front Office system: 1. In Windows Server 2003, navigate to Control Panel -> Add or Remove Programs In Windows Server 2008, navigate to Control Panel -> Programs and Features 2. Locate the Front Office System you want to uninstall 3. Click Remove The uninstall process will remove the windows service, the web site and the public web service which are pointing at the install location. It will then delete the software on the hard disk and the start menu shortcut. The uninstall will NOT delete the database; this must be done manually. Page 10

8.0 Appendices 8.1 Appendix A Software Requirements Legend Recommended The latest service pack should always be used Supported o Not Supported Server Operating Systems Front Office 7.2 Windows Server 2003 (64bit) x Windows Server 2003 (32bit) o Windows Server 2008 (32/64bit) Windows Server 2008 R2 Windows 7, XP & Vista x SQL Server (32/64bit) Front Office 7.2 SQL Server 2005 SQL Server 2008 SQL Server 2008 R2 SQL Server 2012 o x Client Browsers Front Office 7.2 Internet Explorer 7 Internet Explorer 8 Internet Explorer 9 Firefox Google Chrome Safari o o o o o Page 11

8.2 Appendix B Upgrading from previous versions of Front Office This table shows when specific components were added or removed from Front Office. Version Database Current Components Web Site Windows Service Public Web Service Mobile Site BBIS Legacy Components Biomni Mail DOCS Session State 7.2 x x x x x 7.1 x x x x x x 7.0 x x x x x x 6.1 x x x x x x 6.0 x x x x 5.40 x x x x 5.32 x x 5.31 x x 5.30 x x 5.20 x x x 4.50 x x x Classic ASP 8.2.1 Upgrade from 5.20 or below Front Office (aka Directa) 5.20 did not have the public web service or windows service components, so you must add them: Public Web Service Manually Configure Public Web Service, see section 8.6. Windows Service Use the configurator to make a new windows service Run the configurator Choose New Install Select only the windows service option Follow the instructions on the remainder of the configurator 8.2.2 Uninstall Legacy Components Session State - From Front Office (aka Directa) 6.1 session state is incorporated into the main Front Office database, so it is no longer necessary to configure session state as a separate step. If SQL Session state or State Server have been set up previously, and those processes are only used by the Front Office system you are upgrading, then after upgrade they may safely be removed. Biomni Mail - Front Office (aka Directa) 5.40 removed support for Biomni Mail, and moved the email functionality into the windows service. In Biomni mail remove the database from the list of monitored databases Page 12

DOCS Front Office (aka Directa) 5.40 removed support for DOCS, and incorporated the functionality in the windows service. Communication with Connecta is now configured using External System Maintenance within the web site In the external system maintenance page in the website, Point the Connecta External System to <Connecta Public Web Service>/ClientWS.asmx In DOCS, remove the System from DOCS configuration BBIS - Front Office (aka Directa) 5.30 removed support for the BBIS Service, and moved its functionality into the windows service. To ensure a smooth uninstall of the old version of Front Office, BBIS must be reconfigured so that it no longer monitors this database: Set the 'Biomni Business Integration Service (BBIS)' service Startup type to Manual Stop the 'Biomni Business Integration Service (BBIS)' service Restart the server 8.3 Appendix C What the Configurator does in a new install This section describes the actions the Configurator performs under the covers, during a new install. This section is provided for informational purposes, to help with troubleshooting and to allow the configuration to be reproduced manually if needed. In the following paragraphs the text in < > has been entered via the Configurator UI. Some parameters such as <Site Name> are used in multiple places, for multiple purposes. <Install Location> is used to represent the path where the software is installed. By default the software is installed in C:\Program Files\Biomni\Front Office 7.2, though this path may be changed when running windows installer. The configurator writes a log file to <Install Location>\MSBuild\InstallAll<DateTime>.log 8.3.1 Database If <Database> already exists, the installation will halt. Creates a database, named <Database> Creates a login <Web Username>, with password <Web Password> Creates a user <Web Username> in <Database>, with db_owner role Builds the contents of <Database> with the relevant tables, stored procedures etc. Sets the following system settings: System Base Currency to <System Base Currency> System Base Language to <System Base Language> Site Code (Comms Code) to <Site Name> Web Root to http://<machine Name>:<IIS Port>/<Site Name> Public Web Service URL to http://<machine Name>:<IIS Port>/<Site Name>PublicWebService Page 13

8.3.2 Web Site and Public Web Service The web site and public web service are both set up as virtual roots, under the Default Web Site in IIS. The connection string information is written into the web.config files. If the virtual roots or application pool already exist, they will be deleted and recreated from scratch. Specifically it does the following: Creates an Application Pool, <IIS WebSite>-<Site Name>AppPool, running the.net4 framework Creates a virtual root <SiteName>, under <IIS Web Site>, pointing at <InstallLocation>\WebSite Creates a virtual root, Mobile, under the <SiteName> virtual root. This points at <InstallLocation>\MobileSite. Creates a virtual root, UploadedImages, under the <SiteName> virtual root. This points at C:\inetpub\Biomni\Images. Images which are uploaded via the website are stored in this location. Inserts the connection string into <InstallLocation>\WebSite\web.config Sets the cookie names in <InstallLocation>\WebSite\web.config and <InstallLocation>\MobileSite\web.config Sets the file system permission on <InstallLocation>\WebSite, to allow access by the website Sets the file system permission on <InstallLocation>\MobileSite, to allow access by the website Sets the file system permissions on C:\inetpub\Biomni\Images, to allow access by the website Creates an Application Pool, <IIS WebSite>-<Site Name>PublicWebServiceAppPool, running the.net4 framework Creates a virtual root, <Site Name>PublicWebService, under <IIS Web Site> pointing at <InstallLocation>\PublicWebService Inserts the connection string into <InstallLocation>\PublicWebService\web.config Sets the files system permissions on <InstallLocation>\PublicWebService to allow access by the public web service Creates a shortcut in the website named <SiteName> on <IIS WebSite>.url, in Start->All Programs->Biomni->Front Office 7.2 8.3.3 Windows Service If the windows service already exists, it will be deleted and recreated. Creates a windows service named, FrontOfficeService7.2$<SiteName> The service points at <InstallLocation>\ServiceHost\FrontOfficeSvcHost.exe Inserts the connection string into <InstallLocation>\ServiceHost\FrontOfficeSvcHost.exe.config In the config file, writes the service name into the exception management publisher config. This ensures that the service name is shown in error messages written to the windows event log In the config file, writes the service name into the SystemName application setting. This ensures that the service name will be displayed correctly in the website 8.4 Appendix D What the Configurator does on an upgrade This section describes the actions the Configurator performs under the covers, during upgrade. This section is provided for informational purposes, to help with troubleshooting and to allow the configuration to be reproduced manually if needed. Page 14

A key point to note is that an upgrade of Front Office places a new set of code in a new location on the server. The old install remains in place, and can be uninstalled once the upgrade is complete. Configuration is copied from the old install into the new install during upgrade. In the following paragraphs the text in < > has been entered via the Configurator UI. <Install Location> is used to represent the path where the software is installed. By default the software is installed in C:\Program Files\Biomni\Front Office 7.2, though this path may be changed when running windows installer. The configurator writes a log file to <Install Location>\MSBuild\InstallAll<DateTime>.log 8.4.1 Database Runs a series of upgrade scripts on the specified database, to alter the database structure and migrate the data. The upgrade scripts query the database to determine which version it is, and what upgrade scripts to run. 8.4.2 Web Site If it does not exist, creates an Application Pool, <IIS WebSite>-<Site Name>AppPool, running the.net4 framework Repoints the Web Site virtual root to the new code location, <InstallLocation>\WebSite Repoints the Mobile virtual root to the new code location, <InstallLocation>\MobileSite. Or, if Mobile virtual root does not exist, it is created. If it does not exist, creates a virtual root UploadedImages, under the <SiteName> virtual root. UploadedImages points at C:\inetpub\Biomni\Images. Images which are uploaded via the website are stored in this location. Copies the connection string out of the old web.config file, and inserts it into <InstallLocation>\WebSite\web.config Legacy systems may have a virtual root, under the Web Site virtual root, called ASPAdmin. If ASPAdmin is present it is deleted Copies the Z-Override.css file from the old web site and adds it to the new web site. Note that the Z-Override file is used to make customer specific alterations to the style of the web site The style sheets of Front Office may change between versions, so it is likely that the Z-Override style sheet will require further tweaking after the upgrade Inserts a shortcut to the website in the start menu 8.4.3 Public Web Service If it does not exist, creates an Application Pool, <IIS WebSite>-<Site Name>PublicWebServiceAppPool, running the.net4 framework Repoints the Public Web Service virtual root to the new code location <InstallLocation>\PublicWebService Copies the connection string out of the old web.config file, and inserts it into <InstallLocation>\PublicWebService\web.config Page 15

8.4.4 Windows Service Creates a windows service named FrontOfficeService7.2$<Windows Service Instance Name>. In the configurator the <Windows Service Instance Name> can be named as desired but by convention it should be the same name as the Front Office Web Site virtual root The service points at <InstallLocation>\ServiceHost\FrontOfficeSvcHost.exe Copies the connection string out of the old config file, and inserts the it into <InstallLocation>\ServiceHost\FrontOfficeSvcHost.exe.config Copies the email settings out of the old config file, and inserts them into the new config file. From Front Office (aka Directa) 6.1 the email settings are stored in the database, and configured by the web site. However to allow data migration, if the email service finds no settings in the database, it will copy the email settings out of the config file and insert them in the database In the config file, writes the service name into the exception management publisher config. This ensures that the service name is shown in error messages written to the windows event log In the config file, writes the service name into the SystemName application setting. This ensures that the service name will be displayed correctly in the website 8.5 Appendix E Customizing Image Upload In a new install or upgrade image upload is configured automatically. By default the uploaded images are stored on disk at path, C:\inetpub\Biomni\Images. This section describes how to change this storage location: 8.5.1 IIS 7 8.5.2 IIS 6 Launch Internet Information Services (IIS) Manager. Navigate to the Front Office Application. Expand the view, and locate the UploadedImages virtual directory. Right click->manage Virtual Directory->Advanced Settings. In the physical path text box enter a path to where the virtual directory will exist on disk. This path is where any uploaded images will be stored. The path can either be a path on the local server e.g. c:\uploadedimages or a UNC share e.g. \\myshare\uploadedimages. In a new install this path is set to C:\inetpub\Biomni\Images. By default the connection to the physical directory is set to be pass-through authentication. If a UNC Shares was chosen then click Physical Path Credentials, choose Specifice User and enter the credentials. In either scenario the connecting credentials will require read and write access to the physical location. Launch Internet Information Services (IIS) Manager Navigate to the Front Office Virtual Directory Expand the view, and locate the UploadedImages virtual directory. Right Click->Properties. Select the Virtual Directory Tab. If you want to use a local location on disk: Choose A directory located on this computer In the Local path: text box enter a path to where the virtual directory will exist on disk. Page 16

If you want to choose a UNC path: Choose A share located on another computer In the Network directory: text box enter the path where the physical location. Click Connect As and enter the credential you want to use to connect to the share. In either scenario the connecting credentials will require read and write access to the physical location. 8.5.3 Checking Image Upload Once the UploadedImage virtual directory has been created, it can be verified in the website by using the HTML editor to upload a test image to a field. Using a web browser, login to the web site as Admin Admin -> Service Catalog. Click the Edit button and then click the Image Manager icon When configured correctly the Image Manager should list a folder named UploadedImages Select the UploadedImages folder and click the upload button Browse to an image file and upload, if successfully uploaded the image should appear on the right hand side of the image manager dialog 8.6 Appendix F Manual Configuration of Public Web Service In a new install of Front Office the Public Web Service is configured automatically. If upgrading from a system which does not have a Public Web Service, three elements must be configured: An IIS Virtual Root/Application The connection string in the web.config file The Public Web Services URL system setting, set via the web site 8.6.1 For IIS 7 Add an Application for the site under the Default Web Site. The application can have any name, but the convention is <Site Name>PublicWebService. For example if the main web site virtual root is FrontOffice the public web service virtual root should be FrontOfficePublicWebService Configure the "FrontOfficePublicWebService" Application In ASP.NET, Connection Strings set MainDBConnectionString to point to the Front Office database 8.6.2 For IIS 6 Create a Virtual directory for the site under the Default Website. The virtual root can have any name, but the convention is <Site Name>PublicWebService e.g. if the main web site virtual root is FrontOffice the public web service virtual root should be FrontOfficePublicWebService Point the virtual root to <Install Location>\PublicWebService Select Read and Run scripts (such as ASP) in the access permissions Configure the Properties of the Public Web Service Virtual Root: In the ASP.NET tab, ensure the ASP.NET version is set to v4.0 In the Virtual Directory tab, ensure that under the Application settings section, Execute permissions is set to Scripts only Page 17

Set the Application Pool to be the same as the application pool used for the main web site Select the ASP.NET tab then click on Edit Configuration. On the General tab in the Connection string manager, set MainDBConnectionString to point to the Front Office Database 8.6.3 Final Configuration and Validation Login to the Front Office website as Admin Navigate to Admin->System Configuration Locate the Public Web Services URL system setting, and edit Set the URL to the public web service address, for example http://<webserver>/frontofficepublicwebservice Navigate to Admin->Configuration Check. The Public Web Service section should display without error 8.7 Appendix G Side by Side Install A side by side install has multiple independent Front Office systems installed on the same hardware. The windows installer install of Front Office, Front Office 7.2.exe only supports a single instance of Front Office, due to technical limitations of windows installer technology. However Front Office can also be installed from a zip file, which is available from the Download website. 1. Create a folder on the web server where you want to place the installation. 2. Copy the Front Office install zip file into this location. 3. Extract the zip to this location. 4. Double click on Configurator.exe to run the configurator. 5. Follow the instruction on the configurator (it s identical to the installation described in section 3.0). Page 18

To uninstall a Front Office, that was installed from a zip file: 1. In Windows Explorer, navigate to the root installation folder. 2. Double click on uninstall.bat and follow the instructions. This will uninstall the web site, public web service, windows service and shortcut. It will not delete the database you must do this manually. 3. In Windows explorer, delete the root installation folder. 8.8 Appendix H Load Balanced Install A load balanced install has a single database server and database, but multiple instances of the web site, public web service and windows service, which provide load balancing and redundancy. It is now possible to run the install on any web server or application server. The install process copies all of the required files onto the server. The components to install or upgrade can be selected at the Configurator stage e.g. if configuring an application server which will host the windows service, simply choose to configure only the windows service. 8.9 Appendix I Error in Email Task On Windows Server 2003 or Windows Server 2008 SP1, you may experience an email error if you have not installed the latest Windows updates from Microsoft. To Diagnose to problem: Navigate to Admin-> Configuration Check->Email Tab If Last Error: Method not found: 'Void System.Net.Mail.SmtpClient.set_TargetName(System.String)' You should apply windows updates (see below) (Note that Last Error is only visible if there has been an error; no error = no problem) The issue is that a security update from Microsoft adds a property TargetName, to the SmtpClient class. This property is part of a feature Extended Protection for Authentication, http://www.microsoft.com/technet/security/advisory/973811.mspx, which allows customers to enhance email credential security. Page 19

To resolve the problem you must install the latest Windows updates from Microsoft. The exact update required depends on the operating system version: Windows Server 2003 - KB982167 (http://support.microsoft.com/kb/982167 Windows Server 2008 SP1 KB982532 (http://support.microsoft.com/kb/982532) Windows Server 2008 R2 ships with extended protection for authentication, so no update is necessary. 8.10 Appendix J Check Configuration of Windows Service After an install or upgrade, it is advisable to check that the windows service is working correctly. On the server where the windows service is installed: 1. Open Event Viewer, and navigate to the Application Log. 2. Look for messages from the Front Office Windows Service, i.e. Messages with a Source of Service7.2$Front Office. The name may vary slightly - the naming convention is Service7.2$<SiteName>, where <SiteName> is the name of the website. 3. If the windows service has logged any errors then it is possible you have a configuration problem. Examine the detail of the error. There are two common types of configuration problem which can occur with the windows service are: 1. Windows service cannot connect to database. The windows service checks connectivity to the database defined in its config file. If the service cannot connect to the database it will log an error in the windows event log. 2. Windows service and database at different versions. The windows service is tied to a specific version of the Front Office database. So for example, a Front Office 6.1 service will work with a Front Office 6.1 database, and a 6.0 service will work with a 6.0 database. If the service detects that it is pointing at a database which is a different version of Front Office, it will log an error in the windows event log. If you need to change the database connection string for the windows service 1. In Windows Explorer, navigate to <Install Location>\ServiceHost 2. Open the file FrontOfficeSvcHost.exe.config in notepad. 3. Find the <FrontOfficeSystems> section of the config file. It should look something like this: 4. The windows service can be configured to point at multiple Front Office databases. However the recommended configuration is that a windows service should point at a single database; Page 20

this is conceptually simpler and easier to manage. In the <FrontOfficeSystems> section of the config file, each <FrontOfficeSystem> entry defines a database that the service will connect to. In the example shown above only a single database is monitored, in line with recommendations. 8.11 Appendix K Upgrade to.net 4 Front Office 7.2 uses.net 4. The upgrade from a pre 7.1 version of Front Office should be simple as the installer changes the application pool to.net 4 automatically. However an IIS configuration issue occurs, if the.net 4 framework was installed before IIS was enabled. We have seen two different symptoms of the same problem: 8.11.1 Symptom 1 The solution is to register.net 4 with IIS. Open a command prompt as administrator Navigate to C:\Windows\Microsoft.NET\Framework64\v4.0.30319 Run aspnet_regiis.exe iru See http://msdn.microsoft.com/en-us/library/k6h9cz8h(v=vs.100).aspx for more information. Page 21

8.11.2 Symptom 2 The solution is to register.net 4 with IIS. Open a command prompt as administrator Navigate to C:\Windows\Microsoft.NET\Framework64\v4.0.30319 Run aspnet_regiis.exe iru Page 22

At this point you may get a second different error: The solution is to allow ISAPI to serve.net 4 applications. Open IIS manager Navigate to the server level (the top node in the tree on the left hand side of the screen) In the centre panel click on ISAPI and CGI Restrictions Right click on the ASP.NET v4 configuration and select Allow 8.12 Appendix L Installing Under Web Root The configurator supports the option of installing Front Office at the root level of IIS, rather than under a virtual directory. This is not the recommended configuration. To launch the configurator in this mode, hold down the left Shift key when launching the configurator. It is necessary to keep the shift key pressed throughout the elevate stage, until the application proper has started. Page 23

The New Install Configuration Options page, will now have an extra option Install Under IIS Website Root : By checking the checkbox, the main website will be installed in the root of the specified website. The public web service will be created in a virtual directory PublicWebService under this website. This configuration is not recommended for two reasons: If any other application is present in the website, it is likely to be broken by the install of Front Office. This is because the web.config files are inherited in the website hierarchy. The PublicWebService will be operating in the same security context as the main web site. Further configuration is recommended if the main website is exposed over the internet, since it is not secure to expose the PublicWebService over the public internet. (For example, secure the Front Office (Directa) API or move the PublicWebService to a different web site). 8.13 Appendix M - Manually changing the Database Connection String If using II7 or higher, the connection string stored in the web.config file is encrypted to enhance security. If you need to change it, you will need to decrypt it first. Open a command prompt as an administrator and navigate <InstallLocation>\WebSite Decrypt by running C:\WINDOWS\Microsoft.NET\Framework\ v4.0.30319\aspnet_regiis pdf connectionstrings Update the connection string as required Re encrypt by running C:\WINDOWS\Microsoft.NET\Framework\v4.0.30319\aspnet_regiis pef connectionstrings You will need to do the same for the public web service web.config file in <InstallLocation>\PublicWebService folder. Page 24

8.14 Appendix N Mobile Site 403 Error When installing Front Office on a Windows Server 2008 (R1) 32-bit machine, we encountered the following error when navigating to the mobile site: http://localhost/frontoffice/mobile The problem is related to IIS s handling of extensionless urls, as described in this Microsoft knowledge base article: http://support.microsoft.com/kb/980368. The fix is to download the appropriate hotfix package from the article, install it and reboot the machine. Page 25