Callis Reviewer Installation Guide

Transcription

1 Callis Reviewer Installation Guide Contents Introduction... 2 Installation environment... 2 Prerequisites... 2.Net Framework Contents of the release package... 3 Webapp... 3 Setup... 3 Additional packages... 3 JSLibs... 3 Create Web-application System Administration group in Active Directory... 4 Install web-application... 4 Copy data... 4 Create/Setup web-application in IIS... 4 Configure web-application applicationsettings.config... 5 Apply License file... 5 IIS notes... 6 ASP.NET v Application Pools... 6 Create/Setup database... 6 Create the database... 6 Create/Setup login... 6 Verify installation... 7 Configure Callis Reviewer... 7 Trouble shooting... 7 Database connection... 7 License file... 7 Browser says: Service unavailable... 7 Active Directory names... 7 Registering.Net 2 in IIS... 8

2 Introduction The following document describes how to install Callis Review Applikation (CRA). Installation environment The application is a Microsoft.NET web-application for use in a regular Microsoft Windows Domain environment. The figure below shows an example scenario: AD Windows 2003 Server, Domain controller Windows client PCs accessing the webapplication Web-applikation server hosting Callis Reviewer Database server Windows 2003 Server, IIS Windows 2003 Server MS SQL 2005 The web-application is hosted in an IIS on a Windows 2003 Server. The web-application uses a database hosted by a MS SQL 2005 Server on a Windows 2003 server. The web-application knows about the domaincontroller (active directory) to resolve users and groups. The web-application is accessed from individual PCs in the domain through a web-browser. Prerequisites.Net Framework 3.5 The server hosting the web-application must have Microsoft.Net Framework 3.5 installed.

3 Contents of the release package The release package consists of the following: Webapp This folder contains the.net web-application to be hosted by the IIS Setup This folder contains SQL script to create the database and sample data configurations files. Additional packages JSLibs The folder jslibs contains standard javascript libraries the web-application depends upon.

4 Create Web-application System Administration group in Active Directory The web-application needs an active directory group holding users that will be system-administrators within the application. Create a new group in Active Directory named CRASystemAdminGroup Add users to this group. It s also possible to use an existing Active Directory group. NB: Do NOT use the pre-win-2000 group name. Install web-application The following describes the installation of the web-application into the IIS on a Windows 2003 server. Copy data Copy the contents of the JSLIBS package to a folder on the Windows 2003 server (ex. Into the folder C:\Callis\jslibs) Copy the contents of webapp to a folder on the Windows 2003 server (C:\Callis\CRA\versionx.x.x) Create/Setup web-application in IIS Open the IIS Manager, Administrative Tools -> Internet Information Services (IIS) Manager Right click Web Sites -> New -> Web Site... Description: Callis Reviewer (click Next) Port: select available port. Fx. port 80. It may be necessary to disable Default website already using this port Set host header if any (click next) Path: set path to web-application files ex. C:\Callis\CRA\versionx.x.x Uncheck Allow anonymous access to this Web site (click next) Set permissions: Read, Run scripts, Excecute (click Next + Finish) Right click the new web site Callis Reviewer -> Properties Select tab Documents o Add index.html o Move index.html up to the top Select tab ASP.NET o Select ASP.NET version: Select tab Directory Security o Click Edit Authentication and access control o Make sure only Integrated Windows Authentication is checked Select tab Home Directory o Set Application name: Callis Reviewer Click OK to save and apply the changes

5 Right click the web site Callis Reviewer -> New -> Virtual Directory o Alias: lib (click next) o Path: path to JSLIBS fx. C:\Callis\jslibs o Set permissions: Read, Run scripts, Execute o Click Finish to create virtual directory Configure web-application applicationsettings.config The applicationsettings.config file for the web-application needs to be configured. Open applicationsettings.config (located in the web-application root folder ex. (C:\Callis\CRA\versionx.x.x) in a text/xml editor. Set each setting o DomainServer: DNS-address to Domain Controller (ex. server.local.company.com) o DomainName: The suffix to the user logon id. Ex if the user has logon name user@company.com set the value to company.com o LDAP_DC: LDAP DC specification for pointing to the root of the Active Directory. Ex. If the domain is called local.company.com the LDAP_DC string is DC=local;DC=company;DC=com o DomainNameSAM: The pre Windows 2000 domain name (if users logon with MYDOMAIN\user then DomainNameSAM is MYDOMAIN o DBODBCConnection: Modify the server part of the string. If the database is located on server DBSERVER on the SQL database instance MSSQL2005 then set the server part to server=dbserver\mssql2005 o ADUseTrustedConnection: Set this to true if the user identity used by the application pool is trusted to query the Active Directory. If the identity is Network Service then this should be set to true. Else set this to false and set ADQueryUserName and ADQueryUserPassword accordingly. ADQueryUserName will be the name of a user that is allowed to query Active Directory. o ADUserFullNameField: Specify which field in the Active Directory database to use when querying users by their full name. Default is the field cn. Other alternatives could be name, displayname. o DefaultSystemAdminGroup: Specify a Active Directory user group that implies the users who will be system administrators in the web-application (fx. CRASystemAdminGroup) Apply License file Copy the license file (lic.bin) to the web-application App_Data folder fx. C:\Callis\CRA\versionx.x.x\App_Data Restart the Web-Site

6 IIS notes ASP.NET v Make sure ASP.NET v is allowed under Web Service Extensions. If ASP.NET v is note present reregister.net 2 with IIS see Registering.Net 2 in IIS below. Application Pools If not changed, the web-application runs under the DefaultAppPool. The DefaultAppPool excecutes in context of an identity which implies the web-application runs under this identity context also. Make sure that the Application Pool is running properly and is allowed to access the folder where the web-application is located (ex. C:\Callis\CRA\versionx.x.x). If the identity of the application pool is the built in Windows user Network Service it should be allowed access to this folder by default. Create/Setup database The following describes the steps necessary to setup the database on the MS SQL Server 2005 Create the database On the server hosting the web-server open the SQL Server Management Studio and logon to the database engine. Open the query file createdb.sql located in the release package under setup\sql Excecute the query this will create the database: callisreview Create/Setup login The following assumes that the web-application is run under the identity of the builtin user: Network Service. If the database is located on the same server as the web-server: Create database login that allows the server hosting the web-application to logon to this webserver and read and write the database callisreview o Right click Security -> Logins -> New Login o Login name: NT AUTHORITY\NETWORK SERVICE o Select User Mapping Check the database callisreview Check the roles: db_datareader, db_datawriter If the database is located on separate server: Create database login that allows the server hosting the web-application to logon to this webserver and read and write the database callisreview o Right click Security -> Logins -> New Login o Login name: DOMAIN\server$, where server is the name of the windows 2003 server with the IIS hosting the web-application. o Select User Mapping

7 Check the database callisreview Check the roles: db_datareader, db_datawriter Verify installation Open the web-application in a web-browser Check the log file!<web-app root>\logs\ Log4Net.log for exceptions and errors Correct the problem Restart the application pool and web-site and open the web-application in a browser and check log file again. Configure Callis Reviewer Once the web-application is running properly it needs to be configured with the organizational and project specific data such as document types, checklists, findings types, severity types etc in order to making reviews. See Callis Reviewer User Manual for information about configuration and use of the application. Trouble shooting Typical problems and errors: Database connection Make sure the connection string in applicationsettings.config is correct and that a suitable login on the SQL server is available. If the SQL server is located on a remote server from the IIS make sure the SQL server has TCP/IP connections enabled (setup in SQL Server Configuration Manager). License file The application needs a valid license file, lic.bin, in the web-application App_Data folder. If the file is missing or invalid, the web-application will not run properly and will display error message when opened in a browser. Browser says: Service unavailable Check that both the web site and application pool is running. Active Directory names In the Windows 2003 Active Directory each user and group is identified by 2 different names: A shortnamed pre-windows-2000 and the normal name. Be sure to use the new name when referring to users and groups in the system.

8 Registering.Net 2 in IIS If the.net 2 framework is somehow not available to the IIS it s possible to configure the IIS using the command: C:\WINDOWS\Microsoft.NET\Framework\v \aspnet_regiis.exe -i