1 (34) Forecast 5.5 Installation for WEB Server Windows 2003 Aditro Oy, 2012 Forecast Installation Page 1 of 34
2 (34) Contents Installation for WEB Server... 3 Installing Forecast... 3 After installation... 9 Act as part of the operating system... 9 Allow ASP.NET in Web Service Extensions... 11 Enable computer and user accounts to be trusted for delegation... 12 Open XML SDK 2.0 for Microsoft Office... 12 Trust this computer for delegation to specified services only... 13 Users... 17 Forecast folders access rights... 18 Forecast menu changes... 19 More than one forecast report menu... 19 Adjusting the timeout parameter... 20 Adjusting the Transactions Row Count and Add Row Count parameters... 21 Forcing Forecast to restart automatically if memory runs low... 21 Logo on the reports... 22 If client workstations are in different domain that the servers... 22 Database login options... 22 Log in to Forecast... 22 MS Internet Explorer... 22 Mozilla Firefox... 25 Enable 32-bit web applications in 64-bit Windows... 28 Creating a log file or Windows log... 28 Appendix A... 30 Using secure communication (HTTPS)... 30 Appendix B... 32 Four different ways to log into the database... 32 DBUserMaintenance tool installation... 34 Forecast Installation Page 2 of 34
3 (34) Installation for WEB Server Installing Forecast Note! Installation must always be done by a person with full administrative rights. Start selecting Forecast from the setup main page. Forecast installation will work only in Windows Server 2003 operating system. In the Documentation folder there are also this document and other server installation documents. Forecast Installation Page 3 of 34
4 (34) License Before you can continue Forecast setup you must have Fakta license file ( Fakta.lic ): For a new installation you get the license file via a diskette or e-mail, for an update the default is your old license file. Forecast Installation Page 4 of 34
5 (34) Select destination folder Choose destination folder for all programs, help-files etc Default destination folder is C:\Program Files\Personec\Forecast. If you want to change the folder, press Browse and select folder. Select report folder This folder is the place for your own reports. Press Browse in order to change the folder. Forecast Installation Page 5 of 34
6 (34) Choose the language of Forecast Choose default language for Forecast and press Next. Each user can change the UI language from the Forecast options. Some messages from the engine libraries always use the language that is selected here. The language of these messages can t be changed by the user. The language can be changed by editing the HKEY_LOCAL_MACHINE.xml file in..\forecast\app_data\preferences folder and it effects all users. Parameter UILanguage defines the language. 1033 English 1035 Finnish 1053 Swedish Forecast Installation Page 6 of 34
7 (34) Check setup information Check the components and folders selected. Pressing Next starts the actual installation. If you don t have.net v3.5 SP1 framework and Visual Studio 2010 redistributables installed they are installed. Press OK to this message: Forecast Installation Page 7 of 34
8 (34) Setup Complete If this dialog is shown after the installation, it is recommended that the server is restarted before using Forecast: Forecast Installation Page 8 of 34
9 (34) After installation Act as part of the operating system This right is needed for the security account running Forecast application pool. The security account must have this right to impersonate Forecast users sessions to use their Windows authentication. Check first the identity of the security account. Computer management - Services and Applications - Internet Information Services - Application Pools - Forecast - Properties - Identity tab. Forecast Installation Page 9 of 34
10 (34) Then Administrative Tools Local Security Policy User Rights Assignments Act as part of operating system Properties - Add User or Group. Add local NETWORK SERVICE to the user list. Forecast Installation Page 10 of 34
11 (34) Allow ASP.NET in Web Service Extensions Check that ASP.NET is allowed in Internet Information Services/Web Service Extensions. 32-bit Windows: 64-bit Windows: If ASP.NET v2.0.50727 (32-bit) is missing from this dialog, run this: C:\WINDOWS\microsoft.net\Framework\v2.0.50727\aspnet_regiis.exe. Forecast Installation Page 11 of 34
12 (34) Enable computer and user accounts to be trusted for delegation This setting is needed ONLY if the database is not on the same server as the IIS. This right makes NETWORK SERVICE account trusted for delegation. Open XML SDK 2.0 for Microsoft Office If the feature Export to Microsoft Excel 2007 or Word 2007 formats is used in Forecast and there isn t Microsoft Office 2007 or later installed on the web server, Open XML SDK 2.0 for Microsoft Office have to be installed. This msi package is in CPM installation CD folder OpenXMLSDK. Forecast Installation Page 12 of 34
13 (34) Trust this computer for delegation to specified services only This settings gives the computer account (IIS server) right to delegate credentials to the database server (MSSQLSvc) or to the report server(cifs).. Active Directory Users and Computers Computers IIS Server (Basilika in example) Properties Delegation tab Check Trust this computer for delegation to specified services only Check Use any authentication protocol Click Add button Click Users and Computers button Write or Select the database server (minttu in example) press OK Forecast Installation Page 13 of 34
14 (34) If SQL Server service is running under an AD account, MSSQLSvr services are not shown in this dialog. In this case: Use setspn command to get MSSQLSvr services shown. When you install the Setspn.exe tool from Windows Server 2003 Support Tools, you should be able to access the tool at a command prompt (cmd.exe). Enter commands: setspn -A MSSQLSvc/server.company.local DOMAIN\Account setspn -A MSSQLSvc/ server.company.local:1433 DOMAIN\Account In Select Users or Computers dialog, select the AD account that SQL Server service uses. Select all MSSQLSvc services of the db server Press OK Press OK Forecast Installation Page 14 of 34
15 (34) Add service cifs (report server is kaneli in example) Forecast Installation Page 15 of 34
16 (34) Forecast Installation Page 16 of 34
17 (34) Users Create a new User Group "FaktaWebUsers" (local or domain group). Add all users who are authorized to use Forecast to the FaktaWebUsers group. If FaktaWebUsers is a local group, add also NETWORK SERVICE to FaktaWebUsers. If FaktaWebUsers is a domain group, NETWORK SERVICE has to be given rights to access Forecast install folders (see Forecast folders access rights on the next page). Forecast Installation Page 17 of 34
18 (34) Forecast folders access rights Give permissions for the "FaktaWebUsers" group. If FaktaWebUsers is a domain group, give permissions also for NETWORK SERVICE. Give permission Read & Execute, List Folder Contents and Read to the install folder (in example to the Forecast). Give permission Modify to the folders App_Data and XceedTemp Forecast Installation Page 18 of 34
19 (34) Forecast menu changes Open Windows Vision Open forecast menu (forecast.qrm) Make changes to the menu (enter the directory path of your Vision reports) Save forecast menu Location of forecast menu More than one forecast report menu Add the menu menu and the path of the menu into the file web.config. <economa> <forecast> <menus> <menu file="c:\program Files\Personec\Forecast\App_Data\Menus\Forecast.qrm"/> <!-- More menus <menu file=" C:\Program Files\Personec\Forecast\App_Data\Menus\Forecastmenu2.qrm "/> --> </menus> </forecast> </economa> Make changes to the new menu and save it. Forecast Installation Page 19 of 34
20 (34) Location of web.config Adjusting the timeout parameter Default time, after connection is lost to the web server, is 60 minutes. The time can be changed in web.config. <system.web> <sessionstate mode="inproc" cookiename="sid" timeout="60" cookieless="autodetect"/> </system.web> When time expires a message is shown: Timeout parameter can be changed. If the parameter value is set very big (several hours), the message may not be shown, when connection is lost. This may happen because IIS doesn t always fire "timeout expired" event, when timeout parameter is big. Forecast Installation Page 20 of 34
21 (34) Adjusting the Transactions Row Count and Add Row Count parameters Transaction Row Count parameter limits the amount of rows that can be fetched to the Transactions tab of Forecast. If row count is higher than the parameter value, any rows are fetched. Default value is 100000. This parameter effects to the load of the IIS server, not the workstation. Value can be changed in web.config. Add Row Count parameter limits the amount of rows that can be selected in Add rows dialog. Default value is 100. These parameters can be changed in web.config. <configuration xmlns="http://schemas.microsoft.com/.netconfiguration/v2.0"> <economa> <forecast> <settings> <setting name="transactionsrowcount" value="100000"/> <setting name="addrowcount" value="100"/> </settings> Forcing Forecast to restart automatically if memory runs low Forecast can be set to restart the application pool if memory runs low in the Forecast server. Parameters to set this option on and parameters to adjust the restart, are set in memorymanager section of web.config. <configuration xmlns="http://schemas.microsoft.com/.netconfiguration/v2.0"> <economa> <forecast> <settings/> <memorymanager enabled="true" availablememorylimit="70" mainprocessmemorylimit="70" restartconfirmationtimeout="10" timeoutbeforerestart="15" /> enabled availablememorylimit mainprocessmemorylimit When this is true, the memory manager is activated and Forecast checks the memory every 30 seconds The limit (maximum value) of available memory (physical-ram + virtual-swap) in percents (0 means - no limit) The limit (maximum value) of physical memory (RAM) in percents that w3wp process uses (0 means - no limit) restartconfirmationtimeout Timeout in minutes. If either of the limits is exceeded longer than this, restart process is started timeoutbeforerestart The timeout in minutes between memory overloading (restart process is started)and server restarting (Time to save changes before restart) When either of the memory limits exceeds longer time than is defined in the restartconfirmationtimeout parameter, a message like this is shown to all users: Forecast Installation Page 21 of 34
22 (34) Logo on the reports If you want to see logo on the reports, you have to add the path where the logo exist to the HKEY_LOCAL_MACHINE.xml file in the APP_DATA\Preferences folder. Vision looks for a logo in the specified folder ( Header Frame must be selected in the Options): 1. If the logo file exists under the name UnitID_Logo.bmp, it is used. 2. If the logo file exists under the name Logo.bmp, it is used. The contents of HKEY_LOCAL_MACHINE.xml: <?xml version="1.0" encoding="utf-16"?> <HKEY_LOCAL_MACHINE> <Software> <TietoEnator> <Fakta> <Vision> <Settings HtmlTemplatePath="C:\Program Files\Personec\Forecast\App_Data\Preferences"/> </Vision> </Fakta> </TietoEnator> </Software> </HKEY_LOCAL_MACHINE> If client workstations are in different domain that the servers See Appendix A. Database login options Default way to log into the database is Windows authentication. If some other database login is needed see Appendix B. Log in to Forecast Start browser and connect to default start page //server/forecast. MS Internet Explorer To use copy/paste feature in Forecast, IE 7 requires -Forecast should be in Local Intranet zone (recommendable) Forecast Installation Page 22 of 34
23 (34) or -Internet Options/Security/Settings/Scripting/Allow Programmatic Clipboard Access set to. Forecast Installation Page 23 of 34
24 (34) If prompt is enabled, this dialog will appear every time when clipboard is used: If Forecast is used with IE from the IIS server, the use of chart requires that Protected Mode is not enabled: Forecast Installation Page 24 of 34
25 (34) Mozilla Firefox If you do not want that the browser asks user and password when the user is logging in to forecast, you can add the FireCast add-on. Start browser and write the next url: Server/forecast/firefox/firecast.xpi For example Forecast Installation Page 25 of 34
26 (34) You can see the add_ons by selecting Tools(Työkalut) Add_ons(Lisäosat) Extensions(Laajennukset). To use copy/paste feature in Forecast the FireCast add-on updates also signed.applets.codebase_principal_support property value to true. First time when Forecast tries to access the clipboard following dialog will appear and user will decide allow or deny to the clipboard: Forecast Installation Page 26 of 34
27 (34) In case of user check Remember this decision and answer Deny the Paste functionality will not work silently. To fix it: Go to \Documents and Settings\<USER>\ApplicationData\Mozilla\Firefox\Profiles\<prefix>.default folder Find <pref.js> file Remove all rows started with user_pref("capability.principal from the <pref.js> file Save <pref.js> Next time FF will ask user for permission for copy to clipboard Forecast Installation Page 27 of 34
28 (34) Enable 32-bit web applications in 64-bit Windows If Forecast doesn t work after installation enable 32-bit web applications by entering this command in command prompt: cscript.exe C:\Inetpub\AdminScripts\adsutil.vbs set W3SVC/AppPools/Enable32BitAppOnWin64 1 Command is reversed when last parameter is 0. Creating a log file or Windows log To write log from Forecast there are some settings in web.config file that can be adjusted. Log is defined in <configuration><log> branch of web.config file. Log is turned on or off using <TraceLevel>. Possible values of TraceLevel are Off, Error, Warning, Info and Verbose. TraceLevel can be set in three different branches: <configuration><log><tracelevel> <configuration><log><file><tracelevel> <configuration><log><windows><tracelevel> If only the first is defined, file and Windows logs uses that one. The second and third TraceLevel definitions overrides the first. <configuration><log><file><filename> defines the path and the file name for the log file or just the path where the trace.txt file is created. If this is not defined, setting <configuration><appsettings><add key="tempdirectory" value="xxx\yyy" /> is used. <configuration><log><file>< SizeLimitInMb > defines the maximum size of the log file. <configuration><log><file>< Split > value false stores log in one file. value true splits the file according to the trace level. <configuration><log>< windows >< SourceName > defines the name of the application to the Windows log. Example: <log> <!-- Defines the TraceLevel - [Off, Error, Warning, Info, Verbose] --> <TraceLevel>Off</TraceLevel> <!-- Enables logging to file --> <file> <!-- Defines file or folder name for logging--> <Filename>App_Data\Temp</Filename> <!-- Overrides TraceLevel --> <TraceLevel>Off</TraceLevel> <!-- Defines log file limit --> <SizeLimitInMb>10</SizeLimitInMb> <!-- Stores old logs in one file or splits it to different files according to the trace level --> <Split>false</Split> </file> <!-- Enables logging to Windows log --> <windows> Forecast Installation Page 28 of 34
29 (34) <!-- Overrides TraceLevel --> <TraceLevel>Error</TraceLevel> <!-- Defines the source name --> <SourceName>Forecast</SourceName> </windows> </log> Forecast Installation Page 29 of 34
30 (34) Appendix A Using secure communication (HTTPS) Secure communication is needed in case when database, reports or menus are not on same server as IIS and client workstations are in different domain than servers. A certificate is needed in IIS server. In IIS Manager choose properties from WebSites/Default Web Sites/Forecast. Press Edit in Authentication and access control Forecast Installation Page 30 of 34
31 (34) Select Basic authentication(password is sent in clear text). Press OK. In Forecast properties press Edit in Secure Communications. Select Require secure Channel (SSL). Press OK. Forecast Installation Page 31 of 34
32 (34) Appendix B Four different ways to log into the database When Forecast is installed, it has to be decided how to log into the database. Only one of these four options can be used in a Forecast instance. In three of these four options login information is saved in the DATABASE_LOGIN_INFORMATION.xml file in Forecast installation folder. All data in that file is encrypted. 1. Windows authentication When user opens a report from the report menu of Forecast, Forecast looks the name of the database server and database from the report and tries to log into the database using the same windows user identity that is used to open Forecast. This is the default option that is used if any configurations are made regarding the database login after Forecast installation. To use this option: - These options have to be set in the web.config file: <appsettings> <add key=" UseDBAuthentication" value="false" /> <add key=" UserSavedDBLogin " value="false" /> </appsettings> If these rows are missing from the web.config file (like in old installations), it means that their value is false. 2. Database user from XML file by Forecast user This option makes it possible for one report to log into several databases. Database is always looked from the xml file and never from the report (qrd). Database username and password are never shown to the user. - Forecast opens DATABASE_LOGIN_INFORMATION.xml file from the Forecast installation folder...\forecast\app_data\preferences. - When a report is opened, Forecast looks for the Forecast user from the XML file. If user is found, Forecast looks for databases defined for the user. - If there is only one database defined for the user, Forecast connects to that database using the user name and password found from the xml file alongside the database. - If there are more than one database defined for the user, a dialog is shown where user can choose the database Forecast Installation Page 32 of 34
33 (34) To use this option: - Open the web.config file and set these options: <appsettings> <add key=" UseDBAuthentication" value="true" /> <add key=" UserSavedDBLogin " value="false" /> </appsettings> - Use DBUserMaintenance tool to create the DATABASE_LOGIN_INFORMATION.xml file to the folder...\forecast\app_data\preferences - In DBUserMaintenance tool choose the login type Database users by Forecast user and create the needed logins. 3. Database user from XML file by Database Database username and password are never shown to the user. - Forecast opens DATABASE_LOGIN_INFORMATION.xml file from the Forecast installation folder...\forecast\app_data\preferences. - Forecast looks the database server and database from the report (qrd) and tries to find the same server and database from the xml file. - If the server and database matches, Forecast connects to the database using the username and password found alongside the database in the xml file. To use this option: - Open the web.config file and set these options: <appsettings> <add key=" UseDBAuthentication" value="true" /> <add key=" UserSavedDBLogin " value="false" /> </appsettings> - Use DBUserMaintenance tool to create the DATABASE_LOGIN_INFORMATION.xml file to the folder...\forecast\app_data\preferences - In DBUserMaintenance tool choose the login type Database users by database server and create the needed logins. Forecast Installation Page 33 of 34
34 (34) 4. Connect dialog. Database user asked from the user. - Database user and password are asked from the user in the connect dialog. Forecast user can save the database user and password and connect automatically next time. - Users and passwords are saved in the file in the xml file in the Forecast installation folder...\forecast\app_data\preferences\database_login_information.xml. To use this option: - Open the web.config file and set these options: <appsettings> <add key=" UseDBAuthentication" value="true" /> <add key=" UserSavedDBLogin " value="true" /> </appsettings> DBUserMaintenance tool can be used to view the DATABASE_LOGIN_INFORMATION.xml file but it can t be edited. DBUserMaintenance tool installation DBUserMaintenance tool can be installed from the CPM installation CD folder InstallationCD\DatabaseUserMaintenanceTool. This tool needs.net framework version 2.0 or newer. If the framework is missing from the computer, it can be installed from the same folder as the tool..net_3.5_setup.bat starts the installation of.net framework 3.5 SP1. Forecast Installation Page 34 of 34