Installing Vovici EFM Community Version Fall 2007 (3.00) on Windows 2003 Server. November For support, contact Vovici Technical Support.

Transcription

1 Installing Vovici EFM Community Version Fall 2007 (3.00) on Windows 2003 Server November 2007 For support, contact Vovici Technical Support. Please contact Vovici Technical Support if you believe any of the information shown here is incorrect. Companies, names, and data used in examples herein are fictitious unless otherwise noted. No part of this document may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without the express written permission of Vovici.

2 2007 Vovici. All other company and product names are trademarks or registered trademarks of their respective holders. This Document Was Printed in the United States of America. V

3 Table of Contents Setup... 5 Installing Prerequisites... 7 Software Requirements... 7 Installing EFM Community... 8 A. Download EFM Community B. Running the Installer... 9 Options.lic file C. Authentication and Permissions EFM Community Authentication Windows Authentication D. Configuring Database Connections E. Edit Connections Testing the tables in the Database F. Creating an Administrator User Account Add the Administrator User Account Workgroups G. System Options Mail Setup Password Security System Administrator H. Configuring EFM Community Groups Appendix: Determining the web server root in IIS: ASP.NET Framework Troubleshooting and Best Practices Administrative Portal

4 - 4 -

5 Setup EFM Community can be installed on a single server machine, or on a separate App Server and a Web Server. See the sample diagram below: A Database Server is required that must also be available to save the survey responses (The Database Server can also be on the same machine that EFM Community is installed on, but is not recommended for performance reasons). Before EFM Community can be installed, the database must be configured with a user that should have permission to create, update, alter, and delete tables and rows in the database. SQL Server Notes: 1. If dbdatareader and dbdatawriter Security Roles have been assigned to the account the ability to create tables must be added in order for the account to perform all needed database functions. 2. The account must use SQL Authentication in order to function. 3. EFM Community only works with the default instance. Named instances will not work - 5 -

6 Oracle Notes: Assigning the Security Roles Create and Resource to a user generally contains the required permissions for our application. When running the EFM Community installer on the Application Server, the user must be logged into Windows as a Local Administrator account (Not a Domain Administrator) in order for the installer to be able to apply permissions correctly. If this is not the case the permissions must be assigned manually in Section C. It is always recommended that the permissions be verified before proceeding to Section D, since security settings on the Application Server may prevent the installer from assigning valid permissions. A full list of required permissions is listed in the Appendix

7 Web Service Extensions Inside IIS the ASP.NET Web Service Extension must be set to Allow in order for EFM Community to function properly. Follow the steps below to achieve this: 1. Open IIS 2. Click Web Service Extensions 3. Highlight ASP.NET Click Allow Installing Prerequisites Perseus EFM Community requires the following application to be installed on the App server that will host it. Note: Perseus EFM Community will not function correctly unless the prerequisite is installed before continuing the EFM Community install process. Microsoft.NET Framework (version Older versions of EFM Community only used version 1.1 of the.net Framework) Available at : 8edd-aab15c5e04f5 Service Pack 1 for Windows 2003 Server must be installed and the server re-started before the installation of EFM Community can begin. Software Requirements The software requirements for EFM Community Fall 2007 (v3.0) can be found at the URL below: This is in addition to the requirements and prerequisites listed earlier in this document

8 Installing EFM Community Please follow the steps below to install and configure EFM Community. A. Download EFM Community 3.00 To begin the installation process, please perform the following steps: 1. Downloading EFM Community requires a username and password that will be provided by our Installation experts. Please contact them at mailto:installefmc@vovici.com for assistance downloading and installing EFM Community. Our technicians will prove invaluable in assisting the server configuration and EFM Community installation. 2. In a web browser, navigate to the following URL: 3. Click Save (Steps 3, 4, and 5 refer specifically to Microsoft Internet Explorer and may be different on other browsers.) 4. Choose a local directory to save the installer in. Make a note of this directory. 5. Click Save to begin downloading the installer. Once the download is complete, proceed to the next section

9 B. Running the Installer Once the installer has been downloaded, locate the file and follow the steps below to unzip it and begin the installation. 1. Double click on the file. 2. This will launch the Windows installer and the following start message will appear: Note: The version of the EFM Community installer can be found by following the steps below. 1. Right click on the file and click Properties 2. Click Summary 3. The version number is in the Comments field This is the version of the installer not the application itself and can help our Installation Specialists and/or Technical Support staff discover which version of the software is being installed. Note: Click Cancel at any time to stop the installation. 3. Click Next 4. This will display the License Agreement page. If it is acceptable, select the I accept the terms in the License Agreement option. 5. Click Next. 6. Select the web site from the dropdown where the application will be installed. 7. Enter the name for the virtual directory in IIS that will be used to access the application via a URL. The default value is: Community - 9 -

10 So the URL to access the main application will be: Note: Ensure that the virtual directory name is not already in use as a web site name or virtual directory name on the server. 8. Click Next. 9. The Custom Setup page will appear. Multiple options can be selected on this page. On the top part of the window you will see the option Complete with a + next to it. Click the + sign to expose the following two components (Both of these options are installed by default): EFM Community Fall 2007 This determines the installation options for the main application (Includes the Administrative Portal used in Section D to configure the main application). Vovici Service Determines the installation options for the Vovici Service that controls the scheduling feature within the main application. Note: The Vovici Service will be installed by default. It provides time-based services to users such as deployment of invitations, opening and closing of surveys, etc. It is highly recommended that the Vovici Service is installed because certain functions require this service to work properly. o Installing the service on multiple servers that are in a single web farm may result in duplicate invitations being sent. Although if the Vovici Service is disabled on all but one server this will prevent any duplicate invitations from being sent. This

11 solution allows for a quick failover if the one server running the Service goes down: simply enable the Vovici Service on one of the other servers and it will restore the functionality without the need of locating the installer and re-running it to install the service on another server. o Please contact our Installation Specialists for other information regarding the installation of EFM Community on a web farm. Selecting the text for either installation component will display how much disk space is taken up by it. 10. To toggle whether to install one component or the other click the icon ( ) next to its name. Select the X icon to choose not to install the component. The following buttons (other than the three navigation buttons, Back, Next and Cancel) are available on this page: Reset Used to return all options to the original default states. Disk Usage Click to open a page that displays the following information about every drive partition either physically connected to the computer and/or mapped over a network: Disk Size The total available disk space Available The amount of free space available Required How much disk space will be taken by the application 11. Once all desired options have been configured click Next 12. Click Install to start the installation of selected components. 13. Click Finish after installation is complete. 14. If prompted, please Restart before continuing this installation procedure or EFM Community will not function correctly. Note: The EFM Community installer file will check to see how many subfolders are underneath the AppData directory (Located within the Community Virtual Directory) and if it only finds the _default (which is included in the installation) directory listed it will automatically access the setupconfig.aspx script in a web browser. Otherwise the section at the beginning of Section D must be followed. Options.lic file Along with the username and password provided by the Vovici installation experts a file should also be provided called options.lic. This file needs to be copied into the following directory before proceeding: Drive Letter:\pathto\Vovici\AppData The path for Drive Letter:\pathto\ should be the path to the root of the web site specified in Step 6 above

12 C. Authentication and Permissions Once the machine has been restarted the authentication mode to use to allow access to the application must be decided and configured inside IIS. EFM Community has two authentication modes: 1. EFM Community authentication The authentication process is handled by EFM Community via users added under Manage Users in the Administrative Portal. When the main application URL is accessed the EFM Community login prompt will appear. 2. Windows authentication IIS handles the authentication of the user. EFM Community only verifies that the Windows account used to log into the computer itself was added to the list of authorized users under Manage Users in the Administrative Portal. No login screen to the application is displayed to the user. Each of the two authentication modes has a different set of permissions which must be allowed in order for EFM Community to function correctly. Both authentication modes still require the users to be added within Administrative Portal - Manage Users or within the application itself under Group Administration Manage Users. These two authentication modes are displayed in more detail below: EFM Community Authentication Anonymous access must be enabled inside IIS in order for EFM Community Authentication to function correctly. Note: Integrated Windows authentication must be disabled inside IIS in order to attempt to login into EFM Community using EFM Community Authentication. To Enable "Anonymous access" and disable "Integrated Windows authentication" in IIS follow the steps below: 1. Open IIS 2. Right click the Community Virtual Directory 3. Select Properties 4. Click the Directory Security tab 5. Click Edit 6. Select (to enable) Anonymous access 7. Deselect (to disable) Integrated Windows authentication 8. Click OK twice

13 EFM Community Authentication Permissions The following permissions must be assigned after the EFM Community 3.0 installer has been run in order for EFM Community Authentication to function. Note: The accounts used in most cases can be replaced with another account, but whatever account is used must have these minimum permissions in order for the application to function properly. To change an account being used, follow the instructions in the sections labeled Determining the account list at the bottom of the Windows NTFS permissions chart. While the installer does try to define most of these permissions by default, in some environments it is possible that the installer does not have enough privileges to set the permissions as intended or something on the server has prevented the permissions from being applied properly. I. Windows NTFS Permissions Community Virtual Directory Network Service* IIS_WPG# Vovici Service** Read Read None List List Read and Execute None AppData Full Control Read List Surveys Full Control Read List Read List Write (Modify) None Reports Full Control Read List Temporary ASP.NET Full Control N/A N/A Files## C:\Program None None Read Files\Vovici\Service List Windows Temp Dir### None Read List Write Read and Execute None * - See the section regarding Determining the account running the default Application Pool. # - See the section regarding Determining the account that the web server runs as in IIS. ** See the section regarding Determining the account that the Vovici Service runs as (On some servers Modify permissions might be needed for the Vovici Service to function properly) ## - This is a Microsoft.NET Framework created directory and whatever account runs the Application Pool needs to have access to it. Otherwise.NET applications will not function. ### - This directory is a Windows environment setting. The default value is: C:/Windows/Temp, but this can be verified under, Control Panel System Advanced inside the Environment Variables tab under System Variables : it will be the TEMP variable. This permission requirement is out of our control and is a ASP.NET requirement not an EFM Communiy requirement

14 Note: It is advisable to verify that permissions have propagated down to files inside each of these directories for each account. In some cases child objects (files inside directories) are not allowed to receive permissions from the parent objects (directories). II. IIS Permissions Community Virtual Directory AppData Surveys Reports Permissions Read Read Write Read Write Read Write III. Determining the Application Pool used by EFM Community By default EFM Community is run by the default Application Pool but this varies. Please use the information listed above to determine the exact Application Pool. 1. Open IIS 2. Select the web site that is being used to host EFM Community 3. Right click the Community Virtual Directory folder (specified during the original installation, typically called Perseus) 4. Select Properties 5. Select the Virtual Directory tab 6. Record the Application Pool setting at the bottom of the page. IV. Determining the account that runs the Application Pool In IIS 6.0 the Account that the default Application Pool runs as is typically Network Service. This can be verified by doing the following: 1. Open IIS 2. Click the + next to Application Pools 3. Right click Default Application Pool 4. Select Properties 5. Select the Identify Tab 6. Record the username that is specified. This is the account that needs the permissions labeled for the Network Service account in the Windows Permissions column

15 V. Determining the account that the web server runs as in IIS In IIS the Account that the Web Server runs as is typically IUSR_machinename or the IWAM_machinename account. This can be checked by doing the following: 1. Open IIS 2. Right click the web site that is being used to host EFM Community 3. Select Properties 4. Select the Directory Security Tab 5. Under Anonymous access and authentication control click Edit Note: Please verify the username that is specified. If IUSR_machinename is listed sometimes this is not used when EFM Community is used, instead the IWAM_machinename account will be used by IIS. On Windows 2003 Server the IIS_WPG account is used in most scenarios instead of the IUSR_machinename account: both the IUSR and IWAM local machine accounts are included in the IIS_WPG account by Windows. VI. Determining the account that the Vovici Service runs as The Vovici Service used by EFM Community performs all the scheduled functions within the Schedule Events section of the main application. The only exception is if the Now lightning bolt icon is clicked under List view inside Schedule Events. This can be checked by doing the following: 1. Inside the Control Panel open Administrative Tools 2. Double-click (open) Services 3. Look for the Vovici Service, it is typically named Vovici Service and right click it 4. Select Properties 5. Select the Login Tab Note: the username that is specified. This account needs the permissions specified under the column Vovici Services in order to open and close surveys

16 Windows Authentication Integrated Windows authentication must be enabled inside IIS in order to attempt to login into EFM Community using Windows Authentication. Note: Anonymous access must be disabled in order for Windows Authentication to function correctly. Edit the Web.Config File for Windows Authentication Inside the perseus root directory the web.config file must be found (this path was specified when the installer was run earlier in the process). The following line needs to be changed: <authentication mode="none" /> To: <authentication mode="windows" /> To Enable "Integrated Windows authentication" and disable "Anonymous access" in IIS follow the steps below: 1. Open IIS 2. Right click the Community Virtual Directory 3. Select Properties 4. Click the Directory Security tab 5. Click Edit 6. De-select (to disable) Anonymous access 7. Select (to enable) Integrated Windows authentication 8. Click OK twice Note: Some networks require that Digest Authentication for Windows domain servers be checked in order for users to have access to all features within EFM Community. Windows Authentication Permissions The following permissions must be assigned after the EFM Community 3.0 installer has been run in order for EFM Community Authentication to function. Note: The accounts used in most cases can be replaced with another account, but whatever account is used must have these minimum permissions in order for the application to function properly. To change an account being used, follow the instructions in the sections labeled Determining the account list at the bottom of the Windows NTFS permissions chart. While the installer does try to define most of these permissions by default, in some environments it is possible that the installer does not have enough privileges to set the permissions as intended or something on the server has prevented the permissions from being applied properly

17 I. Windows (NTFS) Permissions Community Virtual Directory Network Service* Read List Read and Execute Windows User Accounts# Read List AppData Full Control Read List Surveys Full Control Read List Vovici Service** None None Read List Write (Modify) None Reports Full Control Read List Temporary ASP.NET Full Control N/A N/A Files## C:\Program None None Read Files\Vovici\Service List Windows Temp Dir### None Read List Write Read and Execute None * - See the section regarding Determining the account running the default Application Pool. # - In certain IIS configurations (for example when Impersonation is enabled) all the domain users that will access EFM Community will need these permissions in order to access the product correctly. It is also recommend that the IIS_WPG group be added with these permissions as IIS might use this account to access files. ## - This is a Microsoft.NET Framework created directory and whatever account runs the Application Pool needs to have access to it. Otherwise.NET applications will not function. ### - This directory is a Windows environment setting. The default value is: C:/Windows/Temp, but this can be verified under, Control Panel System Advanced inside the Environment Variables tab under System Variables : it will be the TEMP variable. This permission requirement is out of our control and is a ASP.NET requirement not an EFM Communiy requirement. Note: In some cases Write and Modify permissions might need to be assigned to these users over the AppData, Surveys and Reports subdirectories. It is recommended that a group be created containing all these users under Control Panels Administrative Tools Computer Management Local Users and Groups. This will make assigning the permissions in Windows easier, but the group must be maintained every time a new user is added. ** See the section regarding Determining the account that the Vovici Service runs as (On some servers Modify permissions might be needed for the Vovici Service to function properly)

18 Note: It is advisable to verify that permissions have propagated down to files inside each of these directories for each account. In some cases child objects (files inside directories) are not allowed to receive permissions from the parent objects (directories). II. IIS Permissions Community Virtual Directory AppData Surveys Reports Permissions Read Read Write Read Write Read Write III. Determining the Application Pool used by EFM Community By default EFM Community is run by the default Application Pool but this varies. Please use the information listed above to determine the exact Application Pool. 1. Open IIS 2. Select the web site that is being used to host EFM Community 3. Right click the Community Virtual Directory folder (specified during the original installation, typically called Community) 4. Select Properties 5. Select the Virtual Directory tab 6. Record the Application Pool setting at the bottom of the page. IV. Determining the account that runs the Application Pool In IIS 6.0 the Account that the default Application Pool runs as is typically Network Service. This can be verified by doing the following: 1. Open IIS 2. Click the + next to Application Pools 3. Right click Default Application Pool 4. Select Properties 5. Select the Identify Tab 6. Record the username that is specified. This is the account that needs the permissions labeled for the Network Service account in the Windows Permissions column

19 V. Determining the account that the Vovici Service runs as The Vovici Service used by EFM Community performs all the scheduled functions within the Schedule Events section of the main application. The only exception is if the Now lightning bolt icon is clicked under List view inside Schedule Events. This can be checked by doing the following: 1. Inside the Control Panel open Administrative Tools 2. Double-click (open) Services 3. Look for the Vovici Service, it is typically named Vovici Service and right click it 4. Select Properties 5. Select the Login Tab Note: the username that is specified. This account needs the permissions specified under the column Vovici Services in order to open and close surveys

20 D. Configuring Database Connections Enter the URL below in a web browser to access the EFM Community Administrative Portal. Note: Internet Explorer 5.5 or 6.0 is required to access the EFM Community Administrative Portal. Depending on the authentication method designated in Section C access to the EFM Community Administration Portal will be different: EFM Community Authentication The first time the EFM Community 3.0 installer is run it is required that access be made on the server that EFM Community is installed on or by remotely connecting to it. The Administrative Portal will be accessed through the following URL: Note: If a virtual directory other than community was used in Section B, Step 7 above, replace community in the URL with the name of the virtual directory used. Attempting to access this URL from a different computer by changing localhost to the server s name or IP will fail on all initial installations performed until the administrator account is enabled inside the EFM Community Administrative Portal. This is by design and is intended as an extra security feature. Using Localhost on a Web Server Hosting Multiple Web Site In a web server hosting multiple web sites, in order to use localhost as a URL for a specific web site, a unique port needs to be assigned for localhost for that web site. The steps below explain how to do this. This example assumes the port will be 8080, but any viable port that IIS supports and is not currently in use will work. 1. Open IIS 2. Right click the web site that is being used to host EFM Community 3. Select Properties 4. Select the Web Site Tab 5. Click Advanced 6. Click Add 7. Leave the IP Address (All Unassigned) 8. Enter 8080 for the TCP Port 9. In the Host Header Name enter localhost 10. Click OK After the initial setup is configured you will be able to use an administrator account to access the EFM Community Administrative Portal remotely

21 Windows Authentication If Windows Authentication was chosen access can be from any machine but the login to the machine will need to be a local system administrator (Not a Domain Administrator) on the EFM host application server. The Administrative Portal will be accessed through the following URL: Or via the server either locally or by remotely connecting to it: Note: If a virtual directory other than community was used in Section B, Step 11 above, replace community in the URL with the name of the virtual directory used. Attempting to access this URL from a different computer by changing localhost to the server s name or IP will fail on all initial installations performed after SurveySolutions/EFM 2.1 Build 901 or later (earlier versions/builds did not have the ability for remote access) until the administrator account is enabled inside the EFM Community Administrative Portal. This is by design and is intended as an extra security feature

22 Accessing the URL for the first time will display the Setup Database Connection page: To configure the database connections, follow the steps below: 1. Step 1: Select the type of database server. Note: Please see the database notes listed in the Setup section listed above. 2. Step 2: Enter the Name or IP address of the database server. Use localhost if the App and database servers are the same. 3. Step 3: Enter the Port number used to access the database server. 4. Step 4: Enter the Name of the database to store the survey data. This database will serve as the Master Connection. Note: This database must be created manually and must exist before continuing. Please see the database server s documentation for details. Oracle Note: The Service Name must be entered during this step

23 5. Step 5: Enter the User name to connect to the database. Note: The user should have permission to create, update, and delete tables and rows in the database. 6. Step 6: Enter the user s password. 7. Step 7: Enter a name for the default Workgroup. (It is recommended the name either exactly match the name of the database used in Step 4 above or at the very least be easy to know which name corresponds later) When using a one-workgroup license of EFM Community, all users will need to be members of this workgroup. Note: Please record the name of this Workgroup. If a problem occurs during the installation of EFM Community this information will be needed to properly re-connect EFM Community with the master database. 8. Click Setup You will be prompted to select a password for the System Administrator account (Username will always be and cannot be edited: administrator). This account can be used after the initial setup is finished to access the EFM Community Administrative Portal remotely. Note: The System Administrator account cannot access the main application. This is by design

24 If the above information was correct, the Welcome Page for the EFM Community Administrative Portal will be displayed (See image below). If not, please re-check the settings and try again. Typically a message will appear in the ToolTip at the bottom of the page:

25 E. Edit Connections Click Edit Connections on the Welcome Page to open the following window: Testing the tables in the Database Once the database connection has been setup, it is necessary to test the connection. These instructions begin at the EFM Community Administrative Portal: 1. Click Edit Connections 2. This will display the database connection information and all Workgroups 3. Click the Test icon under Master Connection Note: If passed, proceed, otherwise the Tooltip at the bottom of the window will display information regarding the error message. 4. Update each Workgroup by clicking the Update icon 5. Click Run Table Setup to run the table setup. This will step will make sure that all the necessary database information exists for the application to operate properly

26 F. Creating an Administrator User Account Add the Administrator User Account This section explains how to add an Administrator Account to access EFM Community to complete the installation process. 1. Click Manage Users 2. Click Add New User a. Enter the following information: 3. User Name - The user will use to log in to EFM Community 4. Display Name - The name that will be displayed to other users when they are referring to that user, such as viewing the user s surveys, adding the user as a survey administrator, and inviting the user to a survey. 5. address - The address that EFM Community will contact that user at with invitations and other survey notifications. 6. Language Define the language the user will see when they log into the application. Note: Not all languages have been translated in the application at this time. If a language is needed that is not on this list, please contact the account s Sales Representative for pricing information to add the language to the application. 7. Default Workgroup This will be the first Workgroup the user will access when they log into the application. They can still toggle to any other Workgroup they have access to within the application via the Workgroup Banner. 8. Status Defines whether the user is active, suspended or deleted. The default value is Active, allowing the user to log into the application. 9. Password Either define the password for the account or force the user to define their password when they first log into the main application. 10. Confirm Password Used to confirm the password entered above, leave blank to force the user to define their password. 11. Click Security Role a. Assign the desired security role for the user in each Workgroup. The recommended value is Group Administrator in order to perform the required steps for the installation. 12. Click OK to confirm Note: The option to import users directly from Active Directory is not enabled within the EFM Community Administrative Portal in version 3.0. This is expected to be added in version 3.1 and will be possible within the Manage Users in the EFM Community Administrative Portal. In the meantime there are two options to import users from Active Directory. From File If the list of users can be exported from Active Directory to a flat file (.CSV or.tsv) they can be imported following the steps below: Web Services (this is a per fee add-on charge) An API call can be used to import the users from Active Directory. Web Services are not included with the main application and need to be purchased separately. Import user account If it is desired to import the Administrative user from a file, instead of manually creating an

27 account, follow the steps below (these instructions assume that the Administrative Portal has been accessed): 1. Click Manage Users 2. Click Actions 3. Click Import Users From File 4. Click Select to specify the file to upload 5. Click Next 6. This page will allow you to confirm that the fields in the file will map properly to fields in the application Note: Certain fields will map automatically such as: username displayname culture 7. Click Next 8. A screen should appear either confirming the import or displaying an error message if there was a problem encountered. Information on adding other users and edit users can be found with the EFM Community Application Administration Guide. Workgroups A Workgroup is a way to define collections of users that will want to collaborate in EFM Community. A user can quickly and easily share questionnaires and other data in his or her workgroup, allowing other users in the same workgroup to view, edit, and analyze the same data. Note: This section only applies to multiple-workgroup licenses of EFM Community. A user must have a default workgroup in order to log in: usually, this is the first workgroup that a user is assigned to, though this may be changed in Manage Users. To change the workgroup a user sees on login, change the default workgroup for that user. Note: A user may hold membership in more than one workgroup. These instructions begin at the EFM Community Administrative Portal, which can be accessed via the URL used in Section C. Completing the initial database setup in step C will automatically open this page. Create Additional Workgroups Follow the steps below to create a new workgroup: Note: A single-workgroup license of EFM Community does not have the ability to create additional workgroups. Users will still need to be added to the default workgroup before they will be able to log in to the system. 1. Click Edit Connections 2. Click Add Workgroup 3. Enter the name of the new workgroup. 4. Click Add

28 5. Click Run Table Setup EFM Community Fall 2007 (3.00) Installation Guide for Windows 2003 Server Follow the steps below to Add the Administrative user to a workgroup: 1. Click Manage Workgroups 2. Select the name of the workgroup to be modified. 3. The users will appear in the All Users box. 4. To add a user, move the user from the All Users box to Workgroup Administrators and Workgroup Users to add users to the selected workgroup. A Workgroup Administrator has all of the privileges of a Workgroup User, but is always able to access the data of other users in the workgroup even if it has not been explicitly shared. Accounts added as a Workgroup Administrator are automatically assigned the Security Role of Group Administration. Note: A Workgroup Administrator is needed to complete the installation in Section F

29 G. System Options System Options are used to define multiple global settings for the EFM Community environment. These settings are: settings for the Triggers feature. Define the security level required for user accounts' passwords. Assign a password for the "Administrator" account that allows for remote access of the EFM Community Administrative Portal. Mail Setup Assign the settings for the Survey Engine to use, when the Triggers feature is used with the EFM Community application. 1. Click System Options 2. Enter the SMTP Server: Defines the (outgoing) server used 3. Enter the SMTP Port: Specify the SMTP port for the SMTP server specified (On most SMTP servers this is 25). 4. Enter the SMTP Time Out: The time in seconds that EFM Community will wait for a response from the SMTP server (By default this value is usually 300). 5. Authentication - Define whether Authentication is used when sending via the SMTP Server specified or if Authentication is required. There are three options: a. None - Select if no Authentication is required. b. Auth Login - A method of Authentication that passes the username and password encrypted via base-64 encryption

30 c. CRAM-MD5 - A method of Authentication used by LDAP servers. The password is encrypted using the MD5 algorithm. 6. (Optional: Only entered if step 5 had either Auth Login or CRAM-MD5 selected) a. Account - Enter the Account to use during Authentication b. Password - Enter the Accounts password during Authentication 7. Invitation Control - Define the maximum number of invitations that can be sent out in a given number of minutes. This applies to all surveys in every Workgroup in the environment. This setting will vary from environment to environment as different hardware and network set configurations can radically affect the realistic upward limit on the number of invitations sent. Tip: If 0 is entered for both values no limitation is in place and the application will attempt to send all invites to all participants specified under Select Participants. Password Security Determine the security level of the passwords for all user accounts inside the EFM Community system. Require Strong Password - Force new passwords entered inside the EFM Community' Administrative Portal to fulfill three of the following five criteria: a. lowercase b. uppercase c. numbers d. punctuation - Examples include,.!'":; e. Unicode So a password of: T3stP2s5 would fulfill three of the five criteria. Since the password has a three lowercase letters, two capital letters and three numbers. As would a password of: t,st9a5s This is a valid strong password since it contains 5 lowercase letters two numbers and one punctuation character. Minimum Password Length (Characters) - Determine the shortest possible password for all user accounts

31 Select the desire settings and when you are done click Save to record them. Note: Accounts added via Active Directory do not have their passwords verified. Only the existence of the user name is checked. This is done because we assume that the account has been verified by Windows when they logged into their computer. This setting is enabled inside IIS as Noted in the Section C of this guide. Maximum Password Age (Days) - Determine the longest a password can be maintained within the application before the user is prompted for a new password. The default value is 120 days but this can be modified. System Administrator Assign the password for the "administrator" user in order to access EFM Community' Administrative Portal remotely under the System Administrator tab. When you are done click Save to enable the new password

32 H. Configuring EFM Community Groups 1. Log into EFM Community with an account that has Group Administrator as its security role, and is a member of every workgroup. Please see Section F for more information. a. The URL will, by default, be where SERVERNAME is the system name or fully-qualified domain name (such as of the server that EFM Community was installed on. 2. Click Administration 3. Click Setup 4. Click the Publishing tab 5. By default the path to the EFM Community Survey Engine, se.ashx, should be in the Survey Engine Path field but if it is not enter it. This file is located in the virtual directory specified earlier. Note: This must be an absolute path that can be accessed by survey respondents, such as instead of 6. By default the root path for the current workgroup s surveys should be auto-filled in the Web Survey Location field (the current workgroup is listed at the top of the page) Note: At the end of this path is the Workgroup ID listed under Edit Connections in the Administrative Portal. Each workgroup publishes content to a separate directory. The Survey Engine uses this to find the survey for a particular workgroup. 7. Confirm that the Local Publish Path exists and that all permissions listed in Section C are applied. a. Alternatively, specify a Network share path or an FTP server name, account, and subfolder. b. In all cases, the folder pointed to by the publisher should be the same folder referred to by the Web Survey Location so that files uploaded/saved to that FTP server subfolder, network share, or local directory are accessible at the Web Survey Location URL. 8. Click the Mail tab 9. Enter the location of a SMTP server (Simple Mail Transfer Protocol). 10. Specify the port used by the SMTP server. 11. Enter the time out in number of seconds for the SMTP server. 60 seconds is the default setting and should work in most environments. 12. If the server is an open SMTP server, select None in the Authentication section. a. If the server requires authentication, choose the appropriate method of authentication and enter a username and password that can access the SMTP server. 13. Change the From Address to Other in order to have automatically-generated s (including, but not limited to, invitations) always appear to be sent from the same address. By default, s will appear to be from the survey owner. 14. Change the Reply To Address to Other in order to have replies to automaticallygenerated s (including, but not limited to, invitations) always be directed to the same address. By default, replies will be directed to the survey owner. 15. Click Save Setup 16. Click Test Setup 17. In the Workgroup Banner at the top of the page change the Workgroup via the dropdown list and repeat from step 2 for each workgroup. At this point EFM Community 3.0 is completely configured and ready for use

33 Appendix: 1. Determining the web server root in IIS: The web server root can be checked under IIS by performing the following steps: 1. Open IIS 2. Right click the web site that is being used to host EFM Community 3. Select Properties 4. Click the Home Directory tab Note: the path specified in the Local Path field

34 2. ASP.NET Framework EFM Community 3.0 only works with version of the Microsoft ASP.NET Framework. Microsoft ASP.NET Framework 1.1 will not function. If both are installed on the Application Server inside IIS it is possible to enable the version over the version 1.1 by following the steps below: 1. Open IIS 2. Right click the Community Virtual Directory 3. Select Properties 4. Click the ASP.NET tab 5. Select in the ASP.NET version dropdown box. 6. Click OK

35 3. Troubleshooting and Best Practices The following link is to the Best Practices and Troubleshooting Guide for EFM Community version 3.0: This contains valuable recommendations on maintaining the server EFM Community is installed on as well as troubleshooting advice that should prove helpful

36 4. Administrative Portal The following link contains information about using the Administrative Portal. It has more detail than the installation document does and should be consulted in order to properly administer the application: