SelectHR Installation & Upgrade Instructions

Transcription

1 SelectHR Installation & Upgrade Instructions 1

2 Table of Contents Important Notes... 4 Components of SelectHR... 4 New Installations... 4 Upgrades... 4 Understanding SSUs... 4 Windows Authentication & Single Sign On... 4 SQL Database Passwords... 5 New Installations... 6 Common Components... 6 Installing the Databases... 6 Installing & Configuring the Administrator Installing & Configuring the Web Application Installing & Configuring the Windows Service Upgrading an Existing Installation Common Components Backups Installation of Multiple Versions Important Notes Relating to the Currently Installed Version Important Notes Relating to the Web Application Installing the Master Administrator & Upgrade SSUs Installing & Configuring the New Web Application Installing & Configuring the New Windows Service Installing & Configuring Additional New Administrator Applications (Optional) Installing & Configuring Mobile Installing & Configuring the Mobile Web Application Installing & Configuring recruit Installing the recruit Web Service Installing the recruit Client Multiple recruit Installations Option One: On a Single Web Server Option Two: On Multiple Web Servers (Single Web Service) Option Three: On Multiple Web Servers (Multiple Web Services)

3 Registering Websites Installing & Configuring the Web Services (Optional) Appendix 1: Configuring a New Application Pool Appendix 2: Configuring Secure Web Connections using SSL Creating a Self Signed SSL Certificate Configuring Web Sites for SSL Communication Example: Accessing SelectHR when SSL Secured

4 Important Notes This document details the installation or upgrade process for Access SelectHR v2.0 and recruit v2.5 released on 25/Jul/2014. Components of SelectHR There are several components to a SelectHR installation: SQL Databases hold all the configuration, documents and HR data for SelectHR Administrator Application the Windows application to configure SelectHR Web Application the main application for staff, managers and HR professionals Web Services optional services for integration with specific third party software Windows Service processes occasional jobs and sends & calendar entries recruit Web Service (optional) provide the data for the web recruitment application recruit Web Client (optional) the web recruitment application New Installations Please refer to the Access SelectHR v2.0 - IT Approval Form (New Installation)/(Upgrade) for details of the required server configurations for the SelectHR components to be installed. Please read all sections in this document except the section titled Upgrading an Existing Installation. Upgrades Please read all sections in this document except the section titled New Installations. Understanding SSUs You should read and understand the concept of SSU updates before you begin, and the decisions you may need to make when applying them. Please refer to separate documentation Access SelectHR SSU Updates & FAQ. Windows Authentication & Single Sign On This document covers installation using SQL Authentication for each application component and not setup for end user Windows authentication. However, it is important to understand that this setup does not impact on setup required for end users to Single Sign On. They are different concepts. It details the configuration of each part of the application to SQL data. End users do NOT have or require any level of individual database access. Please read this document carefully before embarking on an upgrade to your live or test systems. Ensure you follow the installation instructions sequentially to minimise downtime for end users of SelectHR. 4

5 SQL Database Passwords The default installation uses SQL Authentication for the application components to communicate with SQL Server. The SELECTADMIN, SELECTWEB and SELECTSERVER SQL Server logins referenced below should have strong passwords assigned, and should be privy ONLY to the customer s IT administrators who are permitted to have access to the Select databases. End users, including HR professionals, should NOT normally be privy to these account passwords. NT or another SQL login should be created for these users who require access to the database to create reports etc. See separate documentation relating to database access. It is possible to configure SelectHR to use Windows authentication for database communication. The IT Approval Form dictates that SQL Authentication (Mixed Mode) is required, but please discuss with your installation engineer if using Windows authentication is your part of your IT policy. Configuration using Windows authentication is beyond the scope of this document. 5

6 New Installations Common Components The installer folder contains a batch file called Run to Distribute Common Components.bat. This batch file should be run to copy the files in the Common Components folder into the relevant installer folder(s). Common components are deployed in this way to reduce overall installer size by only including one copy of each component with the installers (e.g. the.net framework). Installing the Databases 1. Copy the following 9 files (8 data files and 1 script file) to your SQL server data folder, or suitably secure folder location on a drive accessible by SQL Server. The files are in pairs each database comprises an mdf (primary data file) and ldf (transaction log file). This is to support a default installation and backup/restore strategy. 2. Select all the files, right click and go to Properties. Ensure all the files are NOT read only. 3. Open Microsoft SQL Server Management Studio and connect to the SQL instance you want to host SelectHR using an administrator account. 6

7 4. Once connected, right click on the Databases node in the Object Explorer tree, and select Attach 5. From the attach window, click Add and locate the first mdf file detailed above. Repeat this for the other mdf files until you have all 4 databases registered with the Attach window as below. a. Change the database Owner for each database in the list to sa or an administrator account. b. DO NOT change the database names ( Attach As ) at this point. You should do this from the Database Manager feature in the SelectHR Administrator later if required. 7

8 6. Click OK and the 4 databases will now be connected to the SQL Server. 8

9 7. Next, click File, Open, File and browse to the script file alongside the data files. This script creates the accounts required for the service, web and administrator applications to access the databases, as well as some other options. If prompted, enter administrator SQL connection details. 8. Execute the script. Note that it does not matter which database you execute it against. 9. The databases are now configured. 9

10 Installing & Configuring the Administrator 1. Run the setup.exe file from within the Installers\Administrator folder. 2. Follow the instructions in the setup wizard. 3. Launch the SelectHR Administrator from the shortcut under the Access Applications / SelectHR v2.x.0 program group. You will receive the following message. 4. Click Yes, and you will be prompted for a connection to the SelectSystem database. This should be done using the SELECTADMIN SQL login and password. 5. Click Test Connection to ensure the details you entered are correct, and then click OK. 10

11 6. You will receive the following message indicating the connection strings are yet to be configured. Click Yes. 7. You will then be prompted with the Database Manager screen. This configures the connections to the other databases, and configures the connections between them. 8. Simply click Use Current Connection which will copy the server and connection information for the SelectSystem connection set in the previous step. You will get the following confirmation message. 9. Click Yes to this message box, and then click OK on the Database Manager. The system will then go through a number of synchronisation activities, displaying a progress meter while it does so. 10. Once finished, you will be able to log into the application as administrator using the default password. Further configuration via the SelectHR Administrator is beyond the scope of this document. 11

12 Installing & Configuring the Web Application 1. To isolate this web application from other applications in the same web site, create a new app pool as per section Configuring a New Application Pool. 2. For servers running IIS 7.0 or later, the IIS Metabase and IIS 6 configuration compatibility option must be enabled in Windows Features before running the installer. 3. Now run the setup.exe file from within the Installers\Web Application folder. 4. Follow the instructions in the setup wizard. It is important to select the new app pool created in step 1 as part of this process. 5. Launch SelectHR Configuration from the shortcut under the Access Applications / SelectHR v2.x.0 program group. You will receive the following connection dialog for a connection to the SelectSystem database. This should be done using the SELECTWEB SQL login and password. 12

13 6. Click Test Connection to ensure the details you entered are correct, and then click OK. You will get a confirmation message that the connection was saved successfully. 7. Now you should be able to launch SelectHR via the combination of web server and application name provided during the web application installation (default being accessselecthr ). Assuming it s installed on the local machine, the following link will work by default. This confirms that the web application is correctly configured, as the license information is retrieved from the database. 8. Edit the web configuration file. Towards the bottom, there is a section called appsettings. The default for the SiteName setting is LocalHost. Change the SiteName to a unique, friendly name for this installation. It must be unique across all your web application installations. <add key="sitename" value="localhost"/> See section Registering Websites for details of how to register this site with the system for the purposes of communications and links. 13

14 Installing & Configuring the Windows Service 1. Run the setup.exe file from within the Installers\Service folder. 2. Follow the instructions in the setup wizard. 3. Launch the SelectHR Service Administrator from the shortcut under the Access Applications / SelectHR v2.x.0 program group. 4. Click Configure and Add Tenant. Use the connection dialog to set the connection to the SelectSystem database. This should be done using the SELECTSERVER SQL login and password. 14

15 5. Click OK and the tenant name will appear in the drop down. Click Configure and Mail Server. Depending on your mail setup and configuration, you may be required to enter user names and passwords, but for a simple SMTP mail service, you only need to enter the SMTP server address and the default sender and recipient addresses. 6. Click Test Mail Server to check the server can be contacted. For more assistance with settings in the dialog above, please contact your consultant or Access support. 7. Configuring the link to SelectPay is beyond the scope of this document. Please refer to separate documentation. 8. Set the polling interval to something reasonable (in the range of 3 to 5 minutes) and ensure the Simulator Mode option is off for live installations. You may want to tick this for a test system tenant. Then click Apply. 9. Start the notification service using the Start button. The service is now running. 15

16 Upgrading an Existing Installation Common Components The installer folder contains a batch file called Run to Distribute Common Components.bat. This batch file should be run to copy the files in the Common Components folder into the relevant installer folder(s). Common components are deployed in this way to reduce overall installer size by only including one copy of each component with the installers (e.g. the.net framework). Backups Before you apply this update, please take backups of all the Select databases. These are: SelectCDMS SelectHR SelectPersist SelectSystem Please be aware that these databases may have been renamed, so you should check via the SelectHR Administrator Database Manager what the actual database names are if you are not sure. These databases are interdependent and can NOT be restored individually. If your update is not successful, you should restore all four databases and contact Access. You should also take a backup of the Windows service and web application (web.config) configuration file. Installation of Multiple Versions From SelectHR v1.6 onwards, you can install the service, web application and administrator without uninstalling previous versions. These components are now versioned, and are installed to different physical locations. As long as the upgrade SSUs are not applied, this allows you to configure the application connections alongside your existing test or live system. These applications will NOT work until the upgrade SSUs are applied due to database incompatibilities, so only apply the upgrade SSUs at point of switchover. Once ready to switch to the new version, you can take your test or live site offline (e.g. out of hours), apply the upgrade SSUs using the new SelectHR Administrator (see section Installing the Master Upgrade Administrator, step 3) and reconfigure IIS to maintain end user URL shortcuts. Remember that once you ve applied the upgrade SSUs, you will not be able to connect using the previous version. Important Notes Relating to the Currently Installed Version For v1.5 or earlier installations, the v1.6 administrator and SSU updates MUST be applied BEFORE upgrading to v2.0. I.e. you can NOT upgrade an installation directly from v1.5 or earlier to v2.0. The Upgrade\_Files for Upgrade from v1.5 or Below folder contains all the files needed to upgrade to v1.6 from v It is only necessary to run the script Access SelectHR v1.6 Upgrade - Prerequisite Script.sql, connect the v1.6 administrator to the system to be upgraded, and allow the critical SSU 16

17 updates to run. This is because the zipped administrator contains all the necessary updates within that zip file to upgrade to v1.6. For installations of v1.6 or later, v2.0 can be installed in parallel, the upgrade and switch over carried out before uninstalling that previous version. Important Notes Relating to the Web Application The only components which are often customised but NOT held in the database are your style sheet customisations within the web application installation directory. Before you begin you should take a copy of the entire web application installation directory. By default this folder is normally under C:\inetpub\wwwroot. After the upgrade to the web application, you can reapply your style sheet customisations. Any branding changes (e.g. simple changes of the web application image through to fully customised stylesheets) will need to be reapplied. Please notify Access of any branding changes you have made to the system before you perform this upgrade so that we can assist if required. The web application will, by default, be installed to the same virtual directory and therefore physical directory of an existing SelectHR web application. If you want to upgrade the web application to the current installation s virtual directory (i.e. not performing a parallel installation and subsequent switch over) the web application MUST be uninstalled fully, and the physical directory deleted. You might want to do this so that end users do not need any reconfiguration or notification of changed web application address. o o o Take a copy of the existing web.config file, and make a note of the name of the physical directory, virtual directory, application pool, anonymous authentication security settings before uninstalling. Once uninstalled, ensure the old physical directory is deleted, including any remaining files and folders. During installation of the new version, ensure that the location of your previous installation s virtual directory is specified in the setup wizard. If you are installing the web application in parallel with an existing version, you MUST ensure the virtual directory name during the installation wizard does not clash with your existing installation to ensure the files are copied to a new physical directory. o On switch over, you will need to amend settings in IIS to ensure end users do not need any reconfiguration or notification of changed web application address. IIS administration is beyond the scope of this document, but you could: Remove the previous and new web application in IIS and reregister the new web application with the original virtual directory Create or amend a virtual directory alias to redirect shortcuts and workflow hyperlinks from the previous web application URL to the new one. 17

18 Installing the Master Administrator & Upgrade SSUs NOTE: All administrator applications should be upgraded, but the SSUs are only installed by one master administrator application. 1. Run the setup.exe file from within the Installers\Administrator folder. 2. Follow the instructions in the setup wizard. 3. Run the script Access SelectHR v2.0 Upgrade Prerequisite Script.sql via SQL Management Studio connected to the SQL server instance on which the earlier version of SelectHR is installed. NOTE: You may receive the warning following warning which can be ignored and is caused by the SQL Service Broker resetting. Nonqualified transactions are being rolled back. Estimated rollback completion: 100%. 4. Extract the contents of Access SelectHR v2.0 Updates.zip file to root directory of the administrator installation. This is usually C:\Program Files (x86)\access Applications\SelectHR v2.x.0\administrator. NOTE: This zip file contains an Updates folder and will either create that folder or merge with an existing one. Accept any file overwrites, as you may have received a hot fix for a particular problem which is also packaged with this update. Ensure that the extracted SSU files are correctly extracted to the root Updates folder. 5. Launch the SelectHR Administrator from the shortcut under the Access Applications / SelectHR v2.x.0 program group. You will receive the following message. 6. Click Yes, and you will be prompted for a connection to the SelectSystem database. This should be done using the SELECTADMIN SQL login and password. 18

19 7. Click Test Connection to ensure the details you entered are correct, and then click OK. 8. Follow the instructions about applying critical updates. See Access SelectHR SSU Updates and FAQ for more information on critical updates. First you need to confirm that you want to apply the critical updates now. The SSUs will then be installed. NOTE: The upgrade SSUs can take a significant amount of time to run. Some single instructions can take several minutes, so please remain patient. If an SSU fails, you will get an error message, so no error message appearing means the SSU is still executing as required. And a confirmation dialog displayed when complete. 19

20 9. Logon when prompted and click Import/export objects in the Maintenance section. 10. The updates with a yellow star icon are the updates which are either recommended or optional and have not been automatically applied. If you want to apply all updates, click Select All Not Installed, and follow the instructions. Generally, an upgrade will only comprise of critical updates so there may not be any recommended or optional updates to install. 11. Uninstall the administrator application for the previous version after switch over to the new version. The databases have now been upgraded. 20

21 Installing & Configuring the New Web Application 1. To isolate this web application from other applications in the same web site, ensure there is a dedicated app pool for the web application as per section Configuring a New Application Pool. 2. For servers running IIS 7.0 or later, the IIS Metabase and IIS 6 configuration compatibility option must be enabled in Windows Features before running the installer. 3. Now run the setup.exe file from within the Installers\Web Application folder. 4. Follow the instructions in the setup wizard. It is important to select the new app pool created in step 1 as part of this process. a. If upgrading, ensure the web site, virtual directory and application pool are the same as the uninstalled application. E.g. accessselecthr. b. If installing in parallel, be sure to change the virtual directory to something new. E.g. accessselecthr_new 5. Launch SelectHR Configuration from the shortcut under the Access Applications / SelectHR v2.x.0 program group. You will receive the following connection dialog for a connection to the SelectSystem database. This should be done using the SELECTWEB SQL login and password. 21

22 6. Click Test Connection to ensure the details you entered are correct, and then click OK. You will get a confirmation message that the connection was saved successfully. 7. From this point, it will depend whether you are doing a direct upgrade or parallel install as to whether the web site will load. 8. Return to IIS Manager to configure any previous settings for authentication and SSL. 9. Check the SiteName setting in the appsettings section of the web configuration file, and ensure it is the correct unique, friendly name for this installation. See section Registering Websites for details of how to register this site with the system for the purposes of communications and links. 10. Uninstall the web application for the previous version after switch over to the new version. 22

23 Installing & Configuring the New Windows Service 1. If upgrading from v1.4 or above, take a backup copy of the service configuration file for the existing installation. 2. Run the setup.exe file from within the Installers\Server Service folder. 3. Follow the instructions in the setup wizard. 4. If upgrading from v1.4, copy the backup of the service configuration file back into the service folder to restore tenant settings. 5. Launch the SelectHR Service Administrator from the shortcut under the Access Applications / SelectHR v2.x.0 program group. 6. If upgrading: a. From v1.3 or earlier i. Follow the instructions for a new installation from step 4. b. From v1.4 or later i. Check the database configuration has been retained. ii. Check the configuration has been retained. iii. Check the payroll configuration has been retained (if applicable). 7. Configuring the link to SelectPay is beyond the scope of this document. Please refer to separate documentation. 8. Start the notification service using the Start button. The service is now running. 9. Uninstall the service application for the previous version after switch over to the new version. 23

24 Installing & Configuring Additional New Administrator Applications (Optional) NOTE: All other administrator applications can and should now be upgraded using the new installers. Also please note that NO SSU updates need to be extracted or run from these additional installations. SSU updates make centralised data changes only. 1. Run the setup.exe file from within the Installers\Administrator folder. 2. Follow the instructions in the setup wizard. 3. Launch the SelectHR Administrator from the shortcut under the Access Applications / SelectHR v2.x.0 program group. You will receive the following message. 4. Click Yes, and you will be prompted for a connection to the SelectSystem database. This should be done using the SELECTADMIN SQL login and password. 5. Click Test Connection to ensure the details you entered are correct, and then click OK. You will be able to log into the application. 6. Uninstall the additional administrator applications for the previous version after switch over to the new version. 24

25 Installing & Configuring Mobile The mobile web application must be installed on a web server which can be accessed via the internet. For this reason, it is imperative that an SSL certificate is employed, and the IT infrastructure (e.g. DMZ) is secured for this type of access. Installing & Configuring the Mobile Web Application 1. To isolate this web service from other applications in the same web site, create a new app pool as per section Configuring a New Application Pool. 2. For servers running IIS 7.0 or later, the IIS Metabase and IIS 6 configuration compatibility option must be enabled in Windows Features before running the installer. 3. Now run the setup.exe file from within the Installers\Mobile folder. 4. Follow the instructions in the setup wizard. It is important to select the new app pool created in step 1 as part of this process. 5. Once the installation has completed, launch SelectHR Configuration from the shortcut under the Access Applications / SelectHR v2.x.0 program group. You will receive the following connection dialog for a connection to the SelectSystem database. 25

26 This should be done using the SELECTWEB SQL login and password. 6. Click Test Connection to ensure the details you entered are correct, and then click OK. You will get a confirmation message that the connection was saved successfully. 7. Now you should be able to launch the mobile SelectHR application via the combination of web server and application name provided during the web application installation (default being accessselectmobile ). Assuming it s installed on the local machine, the following link will work by default. This confirms that the mobile web application is correctly configured. 8. You should now configure the https binding for the web site and enable SSL for this web service as per the section Configuring Secure Web Connections using SSL. If you have already created the SSL site bindings, you should simply set the Require SSL option under the SSL Settings section for this web service. 26

27 Installing & Configuring recruit There are 2 components to recruit recruit Web Service this often sits within a DMZ and is responsible for all the SQL communication. recruit Client this allows separation of the web pages from the data access, although they are very often installed alongside the recruit Web Service. Please see separate diagrams in relation to network topology options. Installing the recruit Web Service 1. To isolate this web service from other applications in the same web site, create a new app pool as per section Configuring a New Application Pool. 2. For servers running IIS 7.0 or later, the IIS Metabase and IIS 6 configuration compatibility option must be enabled in Windows Features before running the installer. 3. Now run the setup.exe file from within the Installers\rEcruit\Web Service folder. 4. Follow the instructions in the setup wizard. It is important to select the new app pool created in step 1 as part of this process. 5. Once the installation has completed, launch SelectHR recruit Configuration from the shortcut under the Access Applications / SelectHR v2.x.0 program group. You will receive the following connection dialog for a connection to the SelectSystem database. 27

28 This should be done using the SELECTWEB SQL login and password. 6. Click Test Connection to ensure the details you entered are correct, and then click OK. You will get a confirmation message that the connection was saved successfully. 7. Assuming a local install with the default virtual directory name, the following link should correctly return details of the service, similar to the image below. It is important to include the.svc part at the end but amend the link as required This confirms the service is installed correctly. You should now configure the https binding for the web site and enable SSL for this web service as per the section Configuring Secure Web Connections using SSL. If you have already created the SSL site bindings, you should simply set the Require SSL option under the SSL Settings section for this web service. 28

29 Installing the recruit Client 1. Create a new app pool as per section Configuring a New Application Pool. 2. For servers running IIS 7.0 or later, the IIS Metabase and IIS 6 configuration compatibility option must be enabled in Windows Features before running the installer. 3. Now run the setup.exe file from within the Installers\rEcruit\Web Application folder. 4. Follow the instructions in the setup wizard. It is important to select the new app pool created in step 1 as part of this process. 5. You now need to set the web service endpoint for the client application. To do this, open Internet Information Services (IIS) Manager, or refresh the web sites if already open. 6. Expand the Sites tree and locate the recruit client application. Right click and go to Explore. This will take you to the physical root folder of the virtual directory. 7. Browse to the web.config file, right click it and choose Edit. This should open the configuration file in Notepad. Find the section client <client> <endpoint address=" binding="custombinding" bindingconfiguration="custombinding_irecruitmentservice" contract="recruitmentservicereference.irecruitmentservice" name="custombinding_irecruitmentservice" /> </client> Ensure the address attribute is the URL used in the section above to access the recruit Web Service. Again, ensure the full path to the.svc file is provided. 29

30 8. Further down the web config file, there is a section called appsettings. Change the SiteName to a unique, friendly name for this installation. It must be unique across all your web application installations. <add key="sitename" value="recruit"/> See section Registering Websites for details of how to register this site with the system for the purposes of communications and links. 30

31 Multiple recruit Installations From recruit v2.2, it is possible to configure multiple client installations for different branding and vacancy listings. For information on configuring site-specific settings, please refer to separate documentation. Option One: On a Single Web Server This option is recommended due to reduced IT infrastructure overhead and number of installations, but may be impractical in some instances (e.g. multi-national installations). 1. Perform a recruit Web Service install and configure. 2. Perform a recruit Client install and the web service configuration. 3. Create as many copies of this virtual directory as required within the same root published web folder. 4. Register each with IIS, either using the same application (app) pool or a separate one per site. 5. All of these clients should be configured to go through a SINGLE recruit Web Service when there are multiple installations on a single web server. Option Two: On Multiple Web Servers (Single Web Service) 1. Perform a recruit Web Service install and configure on ONE web server. 2. Perform a recruit Client install on EACH web server. 3. Configure each recruit client to point to the single recruit Web Service installed in Step 1. Option Three: On Multiple Web Servers (Multiple Web Services) 1. Perform a recruit Web Service install and configure on EACH web server. 2. Perform a recruit Client install on EACH web server. 3. Configure each recruit client to point to the recruit Web Service installed on that web server. IMPORTANT NOTE: Ensure all installations have a unique SiteName application setting in the client web configuration file. 31

32 Registering Websites You must register your SelectHR and recruit installations via the SelectHR Administrator so that password reset links can be sent out to users with the correct URL. 1. Open the SelectHR Administrator, and go to Configuration / Web Servers section. 2. By default, there is one HR entry for LocalHost. This can be edited to reflect the URL and friendly name (web config SiteName app setting) of your primary SelectHR installation. 3. Other SelectHR, recruit and mobile sites should be registered by clicking Create a new server. Give you web server locations a friendly name, select the protocol and enter the remainder of the URL to get to the website. IMPORTANT NOTE: The friendly name for your recruit installations MUST match the SiteName application setting in the web.config file for the recruit client application. 4. Ensure you select the correct Server Type, and select any additional options which become available. Additional configuration of web applications is beyond the scope of this document. 32

33 Installing & Configuring the Web Services (Optional) 1. To isolate the web services from other applications in the same web site, create a new app pool as per section Configuring a New Application Pool. 2. For servers running IIS 7.0 or later, the IIS Metabase and IIS 6 configuration compatibility option must be enabled in Windows Features before running the installer. 3. Run the setup.exe file from within the Installers\Generic Web Services folder. 4. Follow the instructions in the setup wizard. It is important to select the new app pool created in step 1 as part of this process. 5. Launch the SelectHR Web Service Configuration from the shortcut under the Access Applications / SelectHR v2.x.0 program group. 6. Configure the web services database connection to the relevant server, selecting the SelectSystem database. This should be done using the SELECTWEB SQL login and password. 7. Click Test Connection to ensure the details you entered are correct, and then click OK. You will get a confirmation message that the connection was saved successfully. 33

34 The web services are now installed. Additional configuration of third party web service links is beyond the scope of this document. 34

35 Appendix 1: Configuring a New Application Pool Before installing any web component, it is recommended that you create a dedicated application pool ( app pool ) in IIS to enable that application to run in a sandbox from other web applications installed on the same server. This documentation covers installation within IIS 7. The instructions for IIS 6 are beyond the scope of this document. 1. Open Internet Information Services (IIS) Manager, and expand the Application Pools section. 2. On the Actions panel on the far right, click Add Application Pool. 3. Give the app pool an appropriate name, select the.net 4 framework, and choose Integrated for managed pipeline mode. 4. Highlight the newly created app pool. On the Edit panel on the far right, click Advanced Settings. Because a new app pool inherits it s settings from a default, it is important to check the settings are right for SelectHR to operate. Check the following basic settings, and click OK. i. Enable 32-Bit Applications: False (to force the application to utilise 64 bit processing power) ii. Start Automatically: True (so that users are not delayed after a server reboot, for example) iii. Identity: ApplicationPoolIdentity (defines the user account during processing) 35

36 Further app pool settings are beyond the scope of this document. 36

37 Appendix 2: Configuring Secure Web Connections using SSL It is strongly recommended to enforce SSL secure communication for mobile and recruit installations, or if you are exposing SelectHR over the internet without the need for employees to log onto a VPN. SSL will ensure that any web traffic from client to web server is encrypted and an expected security measure with web sites processing personal data. The default configuration for web sites is to communicate over http (default port 80). However, you can configure an SSL certificate and force communication over https (default port 443). If you have not purchased an SSL certificate for other web applications, you will have to apply for an SSL certificate from a third party certificate provider which guarantees your organisation. For testing purposes, a self-signed SSL certificate can be generated within IIS. For the purposes of this documentation, we will create a self-signed certificate, but this is not a deployable option as users will receive an error similar to this every time they access the solution: Creating a Self Signed SSL Certificate 1. Open Internet Information Services (IIS) Manager, and click on the root item. On the right hand side under the IIS section, there will be a Certificates option. 2. Double click this option, and look to the right hand Actions pane a. If creating a self-signed certificate, click Create Self-Signed Certificate. Give the certificate an appropriate name and click Next. 37

38 b. If importing a certificate from a third party certificate provider, click Import. Browse to the.pfx file and provide the appropriate password. Configuring Web Sites for SSL Communication 1. Open Internet Information Services (IIS) Manager. 2. Expand Sites, Default Web Site (assuming that s where SelectHR is installed) and click on the Bindings link in the Actions pane on the far right. 3. In the Site Bindings dialog, click Add 38

39 4. Choose https and the certificate created in the earlier step. You can also change the IP address range that is allowed to access the website and change the port. The latter would require additional firewall changes which are beyond the scope of this document. 5. Click OK and Close. Now highlight the application you want to force SSL communication for, and double click the SSL Settings option. 39

40 6. To force all users of the application to use https (i.e. SSL encrypted communication), tick Require SSL and then Apply in the Actions tab. 7. If you are using an SSL Certificate, it is recommended you change the following setting in the web.config file to enforce SSL cookies as well. <httpcookies httponlycookies="true" requiressl="true" /> Example: Accessing SelectHR when SSL Secured Once SSL has been enforced on the site in IIS, you should be able to verify that the application cannot operate over http: But you can access it over https: 40