Installation for WEB Server Windows 2003

(1)

Forecast Installation Page 1 of 34

Forecast 5.5

Installation for WEB Server

Windows 2003

(2)

“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.

</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.

enabled When this is “true”, the memory manager is activated and Forecast checks the memory every 30 seconds

availableMemoryLimit The limit (maximum value) of available memory (physical-RAM + virtual-swap) in percents (0 means - no limit)

mainProcessMemoryLimit 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)

(22)

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

(23)

Forecast Installation Page 23 of 34 or

(24)

Forecast Installation Page 24 of 34 If prompt is enabled, this dialog will appear every time when clipboard is used:

(25)

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:

(26)

Forecast Installation Page 26 of 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

(27)

Forecast Installation Page 27 of 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>

(28)

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>

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>

<TraceLevel>Off</TraceLevel>

<file>

<Filename>App_Data\Temp</Filename>

<Split>false</Split> </file>

(29)

Forecast Installation Page 29 of 34

<TraceLevel>Error</TraceLevel>  <SourceName>Forecast</SourceName> </windows>

(30)

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.

(31)

Forecast Installation Page 31 of 34 Select “Basic authentication(password is sent in clear text)”. Press OK.

In Forecast properties press Edit… in Secure Communications.

(32)

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:

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

(33)

Forecast Installation Page 33 of 34 To use this option:

- Open the web.config file and set these options:

- 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:

- 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

(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:

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.

Installation for WEB Server Windows 2003

Forecast 5.5