visual message center dashboard server installation guide · step 1. download microsoft .net...

DashboardsInstallation Guide

8.0VMC-DSB

VISUAL Message Center Dashboards - Installation Guide

The software described in this book is furnished under a license agreement and may be used only in

accordance with the terms of the agreement.

Copyright Notice

Copyright © 2014 Tango/04 All rights reserved.

Document date: August 2013

Document version: 1.2

Product version: 8.0

No part of this publication may be reproduced, transmitted, transcribed, stored in a retrieval system, or translated into any language or computer language, in any form or by any means, electronic mechani-cal, magnetic, optical, chemical, manual, or otherwise, without the prior written permission of Tango/04.

Trademarks

Any references to trademarked product names are owned by their respective companies.

Technical Support

For technical support visit our web site at www.tango04.com.

Tango/04 Computing Group S.L. Avda. Meridiana 358, 5 A-B Barcelona, 08027 Spain

Tel: +34 93 274 0051

http:\\www.tango04.com

http:\\www.tango04.com

Table of Contents

Table of Contents

Table of Contents .............................................................................. iii

How to Use this Guide........................................................................vi

Chapter 1

Introduction ...................................................................................... 1

Chapter 2

Product Directories ............................................................................. 8

Chapter 3

Before you Begin ............................................................................... 9

Chapter 4

Upgrading from DashboardServer...................................................... 114.1. Upgrading from DashboardServer ................................................................11

4.1.1. Manual Migration.....................................................................................11

Chapter 5

Installation Steps............................................................................. 12

© 2014 Tango/04 Computing Group Page iii

Table of Contents

5.1. Internet Information Services (IIS) ................................................................12

5.2. Microsoft .Net Framework.............................................................................12

5.3. Dashboards...................................................................................................13

Chapter 6

Installation Summary....................................................................... 22

Chapter 7

Post-Installation Adjustments ........................................................... 237.1. Enabling Windows Integrated Authentication - Dashboards Settings...........23

7.2. For IIS 6 / Windows 2003..............................................................................24

7.3. For IIS 7 ........................................................................................................25

Chapter 8

Removing Dashboards...................................................................... 27

Appendices

Appendix A: Dashboards Manual Installation...................................... 28A.1. Before You Get Started ................................................................................28

A.2. Installing and Configuring the Web Site .......................................................28

Appendix B: Manual Installation Tasks for IIS..................................... 33B.1. Configuring Feature Delegation....................................................................33

B.2. ISAPI and CGI Restrictions ..........................................................................34

Appendix C: Enabling Windows Integrated Authentication.................... 36C.1. Internet Information Server Settings.............................................................36

C.1.1. IIS 5 and IIS 6.........................................................................................36

C.1.2. IIS 7.x .....................................................................................................37

C.2. Web Browser Settings..................................................................................38

C.2.1. Firefox 3.x...............................................................................................38

C.2.2. Internet Explorer .....................................................................................38

© 2014 Tango/04 Computing Group Page iv

Table of Contents

Appendix D: Manual Configuration for Windows 2003 x64 .................. 41

Appendix E: Manual Configuration for Windows 2008 x64 and Vista x6442

Appendix F: How to Configure Machine Keys on ASP.NET When Installing on a Web Farm (Cluster) .................................................. 43

F.1. Generating the Keys .....................................................................................43

F.2. Setting the Keys............................................................................................43

Appendix G: Configuring SSL Connections........................................... 45G.1. IIS 6..............................................................................................................45

G.1.1. Prepare a Certificate Signing Request (CSR) ........................................45

G.1.2. Request a Certificate from a Certificate Vendor.....................................47

G.1.3. Install the Certificate...............................................................................48

G.2. IIS 7..............................................................................................................49

G.2.1. Prepare a Certificate Signing Request (CSR) ........................................49

G.2.2. Request a Certificate from a Certificate Vendor.....................................51

G.2.3. Install the Certificate...............................................................................51

Appendix H: Using a SQL Server Session State in ASP.NET................... 54

Appendix I: Contacting Tango/04 ...................................................... 57

About Tango/04 Computing Group .................................................... 59

Legal Notice .................................................................................... 60

© 2014 Tango/04 Computing Group Page v

How to Use this Guide

© 2014 Tango/04 Computing Group Page vi

How to Use this Guide

This chapter explains how to use Tango/04 User Guides and understand the typographical conventions

used in all Tango/04 documentation.

Typographical Conventions

The following conventional terms, text formats, and symbols are used throughout Tango/04 printed

documentation:

Convention Description

Boldface Commands, on-screen buttons and menu options.

Blue Italic References and links to other sections in the manual or further documentation containing relevant information.

Italic Text displayed on screen, or variables where the user must substitute their own details.

Monospace Input commands such as System i commands or code, or text that users must type in.

UPPERCASEKeyboard keys, such as CTRL for the Control key and F5 for the function key that is labeled F5.

Notes and useful additional information.

Tips and hints that will improve the users experience of working with this product.

Important additional information that the user is strongly advised to note.

Warning information. Failure to take note of this information could potentially lead to serious problems.

Introduction

© 2014 Tango/04 Computing Group Page 1

Chapter 11. Introduction

There are two ways to install the product:

• Download from our Web site

• Install VISUAL Message Center Dashboards from the product DVD

With either method, all components are installed from your PC.

VISUAL Message Center Dashboards is a Web application. This manual will show you how to install

VISUAL Message Center Dashboards

Important When installing VISUAL Message Center Dashboards please follow these instructions carefully. If you have any questions, please contact your Tango/04 Business Partner.

Product Directories

© 2014 Tango/04 Computing Group

Chapter 22 Product Directories

By default VISUAL Message Center Dashboards is installed on your PC in the directory

C:\Program Files\Tango04\Dashboards

You can override the default locations to a different one if you choose.

Before you Begin

Chapter 33 Before you Begin

Please make sure that all the following prerequisites are in place before you begin the installation

process:

Prerequisites

You must have administration rights on the client pc where you want to install the product.

Please read the VISUAL Message Center Installation Overview guide.

Operating System:

• Microsoft Windows Server (2003, 2008, 2012)

For complete details of which operating systems are compatible please refer to the Supported Operating Systems and Applications guide.

Dashboards will need access to the following database (recommended data-base name in parenthesis):

• the database storing the ThinkServer statistical data to be accessed

by Dashboards (T04_Statistics)1

One of the following database engines is required:

• Microsoft SQL Server (2005, 2008, 2012)

• PostgreSQL (8.1.3 or later)

• Oracle (10g or 11g)

Please see the Supported Databases guide for full details of which database can be used with this product.

Please make sure you have the IP address where AccessServer is installed.

If AccessServer has not been installed already on your network, the following database will also be needed for use with this product:

• a database for storing AccessServer data (T04_AccessServer)


http://customers.tango04.com/content/704



Before you Begin

ODBC System Data Source Names (DSNs) must be created in order to enable the connections between Dashboards and the relevant databases.

We recommend using the name of the database for the relevant ODBC con-nections:

• T04_Statistics

• T04_AccessServer

The following additional software must be already be installed:

Internet Information Services (IIS) version 5 or above

Microsoft .NET Framework 3.5

The Dashboards Installer will install Microsoft .Net Framework if it is not already installed on your server. However, IIS must be installed manually.

NOTE: If you have previously installed IIS and then changed the name of your PC, it is strongly recommended that IIS is re-installed to avoid new web sites using an incorrect anonymous account user name.

Microsoft Internet Explorer 7.0 or Microsoft Internet Explorer 8.0 in compatibility mode, or Mozilla Firefox 3.0 or above.

The following Tango/04 products should already be installed:

ThinkServer

Database Settings Administrator

NiceLink2

AccessServer2

Scheduler2 (Optional - Required for use with scheduled macros. Must be installed on the same domain as Dashboards).

Important upgrading information is available regarding this product. Please see Chapter 4. - Upgrading from DashboardServer on page 11 before con-tinuing the installation.

If you have a previous version of this product installed, we strongly recom-mend you save your configuration.

Please refer to the Backup and Restore Appendix in the VISUAL Message Center Dashboards User Guide before continuing the installation.

1. Please refer to the VISUAL Message Center ThinkServer User Guide for fur-ther details.

2. Can be installed during the Dashboards installation process if not already installed.

Prerequisites






Upgrading from DashboardServer


Chapter 44. Upgrading from DashboardServer

4.1 Upgrading from DashboardServerPrior to install, you may be interested in backing up any existing tables and dashboards created in

DashboardServer, which can also be used in Dashboards.

Step 1. In order to migrate the dashboards and tables created with DashboardServer, use the

export utility to create a dashboard and / or table export file for every item you want to

keep.

Step 2. Then, in Dashboards, use the import utility to recover your data. If you need assistance

with the export and import utilities, please refer to the corresponding section in the

Dashboards User Guide.

4.1.1 Manual MigrationTo do a manual migration, copy the /data/public folder from your previous DashboardServer

installation into the /data/public folder of the current Dashboards location. Then restart IIS, so that

the new tables and dashboards become available.

Also copy:

• images\icons\userCustom

• images\icons\userIconSets.xml

• and the following files in the config folder:

− AccessServer.xml

− dasboards.config

− databaseConfig.cml

− datasources.xml

Important Dashboards and tables must be exported from DashboardServer before you begin the

upgrade to Dashboards.

Installation Steps

Chapter 55 Installation Steps

To publish custom dashboards VISUAL Message Center Dashboards requires Internet Information

Server (IIS) and Microsoft .Net Framework.

The installation steps for each component are described here.

5.1 Internet Information Services (IIS)IIS is available on any Microsoft Windows installation disc. You will need a Microsoft Windows

installation disc to install IIS.

Step 1. Insert the Microsoft Windows installation disc

Step 2. Select Optional Components

Step 3. Select the Internet Information Services check-box to add it to the default selections

Step 4. Click Next to begin the installation

Step 5. When the installation is complete, click Finish

Step 6. Click Exit

5.2 Microsoft .Net FrameworkMicrosoft .Net Framework is free to download from the Microsoft Web site.

Step 1. Download Microsoft .Net Framework version 3.5

Step 2. Double click the .exe file to begin the installation

Step 3. Click Run

Step 4. Click Install to begin the installation

Step 5. When the installation is complete, click Finish

Note The version of IIS on a Microsoft Windows installation disc is only a limited version, it is not the full version of the product.


Installation Steps

5.3 DashboardsFrom DVD: If you are installing from the DVD, Select VISUAL Message Center Dashboards and follow

the prompts to complete the installation. If, for whatever reason, you must install using the Windows

Explorer view, please contact your Tango/04 Business Partner for further assistance.

From ZIP: If you are installing from a downloaded zip file, double click on the zip file icon, and follow the

prompts. This will decompress the files into a temporary directory and start the install process.

The entire installation process should take between five and ten minutes, depending on the performance

of your PC.

To install VISUAL Message Center Dashboards:

Step 1. Initial product installation setup.

The Dashboards Installation Wizard opens.

Figure 1 – Dashboards Installation Wizard

Click Next to begin the installation.

Step 2. The License Agreement window opens.

Read the License Agreement information and select the I accept the terms in the

license agreement option button, and click Next.

Figure 2 – The Software License agreement


Installation Steps

Step 3. The Custom Setup window opens. Select the features you wish to install.

The installer will install the following features by default:

• VISUAL Message Center Dashboards

• VISUAL Message Center Scheduler

Figure 3 – Custom Setup

Click Next to continue.

Figure 4 – Website Configuration dialog


Step 4. Enter a name for the Dashboards Web Site and the TCP Port. Although the default

values are sufficient in most cases, you can change these settings to meet your

organization’s environment.


Installation Steps

Figure 5 – Dashboards Web Site information.


The Installation is ready to install the selected components

Figure 6 – Ready to install.

Click Next to Continue.

Step 5. AccessServer registration.

Before installing the selected Dashboards features, you must first register the product

with AccessServer.

If AccessServer is not already installed, it will be installed during this step. For further

information please refer to the AccessServer Installation Guide.

For more information regarding AccessServer please refer to the AccessServer User

Guide.





Installation Steps

Figure 7 – AccessServer Registration


If AccessServer is already installed, the installer will select it by default, otherwise it will

be necessary to install AccessServer.

Figure 8 – AccessServer Location


Enter the Security Administrator credentials for AccessServer.


Installation Steps

Figure 9 – AccessServer Security Administrator credentials


Select the Dashboards Security Model. Click Next to accept the default model.

Figure 10 – Dashboards Security Model

Click Next to select the default option and update the current security model.

Tip Make a note of the Domain details for AccessServer which are selected here, this

information will be useful when connecting to Dashboards.

Note If you are upgrading your version of Dashboards we recommend changing the default

selection here and to select the Overwrite the existing security model option.


Installation Steps

Figure 11 – The default option to keep the current security model is selected

AccessServer Registration is complete.

Figure 12 – Registration completed

Click Finish to continue with the installation of the selected Dashboards features.

Step 6. Scheduler setup.

If Scheduler is not already installed, it will be installed during this step. For further

information please refer to the Scheduler Installation Guide.



Installation Steps

Figure 13 – Scheduler selection


The License Agreement window opens.

Read the License Agreement information and select the I accept the terms in the

license agreement option button, and click Next.

Figure 14 – The Software License agreement

Select the destination folder.

Figure 15 – Select the destination folder


Installation Steps


Ready to install Scheduler.

Figure 16 – SharedObjects selection complete

Click Install to install Scheduler.

Install Shield Wizard completed..

Figure 17 – Scheduler installation complete

Click Finish.

Step 7. Dashboards installation complete.

When the installer has finished you will be presented with the following window.


Installation Steps

Figure 18 – Dashboards Installation Wizard complete


Installation Summary


Chapter 66 Installation Summary

Now you are ready to start creating dashboards for your monitored servers. Before getting started in

VISUAL Message Center Dashboards we suggest you read the section “How VISUAL Message Center

Dashboards Works” in the VISUAL Message Center Dashboards User Guide. It will help you understand

how to get the most out of the program. The User Guide will help you to implement the dashboards on

your system.

To quickly learn more about the many functions and tools available to you, we recommend a scheduled

walk-through or conference call with your Sales Representative.

We hope that you enjoy working with VISUAL Message Center Dashboards


Post-Installation Adjustments

Chapter 77 Post-Installation Adjustments

Once the installer has completed a few adjustments must be made, depending on the operating system

of the server. This chapter describes the required adjustments.

7.1 Enabling Windows Integrated Authentication - Dashboards SettingsTo enable the use of Windows integrated authentication from Dashboards:

Step 1. Click the Management tab and select Configure Dashboards

Step 2. In the Login Settings panel. select the Enable WIA check box.

Step 3. Ensure the WIA confirmation screen time parameter is not set to 0 (zero).

This parameter represents the time in seconds that the confirmation screen to accept or

deny WIA authentication will be shown. If it is set to zero, the WIA confirmation screen

will not appear.

Note See also Appendix C: Enabling Windows Integrated Authentication on page 36 for further

instructions regarding configuring IIS and the Web browser for Windows Integrated

Authentication.

Note Login with WIA requires AccessServer Version 1.2.9 or greater.



Figure 19 – Dashboard Settings

7.2 For IIS 6 / Windows 2003Creating an application pool for Dashboards is highly recommended. Running Dashboards in its own

application pool will ensure maximum resource availability and isolate the application in case of

unexpected events in other application pools.

Step 1. Disable Recycling in the Application Pool where Dashboards is installed. Recycling

periodically can improve performance, but it will log out every user that's logged in. If

you want to enable recycling, you can use SQL Server Session States to avoid this

problem, as described in Appendix H: Using a SQL Server Session State in ASP.NET

on page 54.

Figure 20 – Shows Recycling disabled in Application Pool

Step 2. Modify the Application Pool to work with only one process, as shown below:



Figure 21 – The application pool should work with only one process

7.3 For IIS 7Creating an application pool for Dashboards is highly recommended. Running Dashboards in its own

application pool will ensure maximum resource availability and isolate the application in case of

unexpected events in other application pools.

If you are using IIS 7, you will need to:

• set the web application path

• change the managed pipeline mode of the application pool

• change the user account for the application pool identity (if using Windows 2008 R2)

• make sure .Net Framework version is set to v4.0

To set the Web Application Path:

Step 1. Open IIS Manager.

Step 2. Browse to the created Web Site or Virtual Directory.

Step 3. In the side bar, under Actions click Basic Settings...

Step 4. In the Physical path field, enter the path you used during the installation. For Example:

C:\Inetpub\wwwroot\Dashboards or c:\program files\tango04\Dashboards

Figure 22 – Enter the Physical path.



To change the managed pipeline mode:

Step 1. Open the Application Pool.

Step 2. Set the Managed pipeline mode to Classic.

Figure 23 – .Net Framework version should be set to v2.0 and managed pipeline of the Application Pool to Classic.

To change the user account for the application pool identity (for Windows 2008 R2):

Step 1. Open IIS Manager.

Step 2. In the Connections panel, expand the server name of the server which is used to run

Dashboards. Click Application Pools. Your application pools are listed to the right.

Step 3. Select Dashboards from the list of application pools, and click Advanced Settings from

the Edit Application Pool menu to the right. The Advanced Settings window opens.

Step 4. In the Process Model group of settings, select Identity, and click the option button

next to ApplicationPoolIdentity. The Application Pool Identity dialog box opens.

Step 5. Select NetworkService from the Built-in account drop-down list, and click OK.

Step 6. Click OK again in the Advanced Settings window to save your changes.


Removing Dashboards


Chapter 88 Removing Dashboards

In the event you want to uninstall VISUAL Message Center Dashboards you can remove Dashboards

using the Windows Control Panel.

For a complete uninstall:

• Remove Dashboards

• Manually remove the Web Site definition from the IIS configuration.

Removing IIS and .Net is optional.

Appendix A : Dashboards Manual Installation

Appendix AAppendix A: Dashboards Manual Installation

The purpose of this appendix is to explain how to configure the Dashboards Web site by hand on a

Windows Server Operating System.

Normally, the Dashboards Web site is created automatically when installing the Dashboards. However,

in the event that the Dashboards installation fails in any way, follow the instructions in this appendix.

A.1 Before You Get StartedBefore starting this procedure, it is important that you check that the following requirements are met on

the target machine:

• The server has Internet Information Services (IIS) installed.

• The server has .NET Framework 3.5 installed.

IIS is a Windows component and can be installed from the Control Panel using Add/Remove Windows

Components.

.NET Framework 3.5 is available for download from the Microsoft Web site.

A.2 Installing and Configuring the Web SiteTo install and configure the Dashboards Web site:

Step 1. Open the IIS Manager.

On the task bar click the Start button and select Administrative Tools and click

Internet Information Services (IIS) Manager.



Figure 24 – Opening IIS Manager

Step 2. Make sure that the ASP .NET 2.0 extensions are allowed.

Double-click the Web Service Extensions folder in the folder tree. All Web Services

Extensions and their status appear on the right. Select ASP .NET 2.0 from the Web

Service Extensions list and click the Allow button to change the status to Allowed.

Figure 25 – Allow ASP .Net 2.0 extensions

Step 3. Now it is time to configure the new Web site.

In the tree on the left, right-click the Web Sites folder. Click New and select Web Site…

The Web Site Creation Wizard appears to guide you through the necessary steps to

create your new Web site.



Figure 26 – Open the Web site Wizard

Step 4. Add a description for the Web site for identification later. In our example we entered

Dashboards.

Figure 27 – Web Site Wizard - Description

Step 5. Next you will be asked to configure the IP address and Port.

Enter the IP address of the server that will handle petitions for requests of the site. If you

use the All Unassigned value, the user will be able to access the new Web site using

any of the server's IP addresses. If you want the site to only be enabled on a certain IP

address, select the desired IP address from the drop-down list box. This could be useful

if for example, you want to make the Web site only available on an Intranet not via the

Internet.

Enter the port you want the Web site to listen to. Bear in mind that it is highly probable

that the default port (80) is already being used by the main Web site of the server. As it

is not possible for more than one Web site to listen to the same port, you will probably

have to select a new port, or stop the main Web site before trying to start the



Dashboards Web site. If you are not sure what port is available check with your

Systems Administrator.

Figure 28 – IP Address and Port Settings

Step 6. In the next window select the directory where your Web site is located. To select the

desired directory simply browse to the root folder of the Dashboards files (i.e. the

installation directory of the failed automatic installation). Remember to select the Allow

anonymous access to the Web site option, or an HTTP login screen will appear every

time anyone tries to access the Web page.

Figure 29 – Web Site Wizard - Home Directory

Step 7. Finally, you need to configure the Access settings of the new Web site.

Select the following check boxes:

• Read

• Run scripts

• Write

Click Next to complete the Wizard.



Figure 30 – Web Site Wizard - Access Permission

Once the wizard is complete, the new Web site will appear in the tree at the left of the window. Check

that the ASP.NET version used is version 2. To do this right-click the newly created Web site, click

Properties and open the ASP.NET tab. Make sure that the selected ASP.NET version is version 2.

Figure 31 – Check that the ASP.NET version is version 2.0

Now you are ready to start working with Dashboards.


Appendix B : Manual Installation Tasks for IIS

Appendix BAppendix B: Manual Installation Tasks for IIS

This appendix provides details of the manual installation tasks required to configure IIS 7.0 (Windows

Server 2008) or IIS 7.5 (Windows Server 2008 R2 / Windows 7).

B.1 Configuring Feature DelegationFrom IIS V7.0 onwards, there are some circumstances where you will have to configure feature

delegations manually. Failure to do so may result in an error message when browsing the Dashboards

Web site, warning that a configuration section cannot be overridden.

To configure feature delegations:

Step 1. Run the inetmgr command, which will launch the Internet Information Services (IIS)

Manager as shown in the following image.

Figure 32 – Configuring feature delegations



Step 2. Select the correct server in the connections tree and double-click Feature Delegation.

Figure 33 – Feature Delegation

Step 3. Set all parameters to the Read/Write or Configuration Read/Write values.

B.2 ISAPI and CGI RestrictionsBeginning with Dashboards 8 SP 1, it is necessary to allow the 32-bit ASP.NET v4.x ISAPI and CGI

extension to run on your Web server.

To allow the extension:

Step 1. Open the IIS Manager (Start > Administrative Tools > Internet Information Services (IIS)

Manager).

Step 2. Select the server where Dashboards is installed at left and double click the ISAPI and

CGI Restrictions icon at center.



Figure 34 – Accessing ISAPI and CGI Restrictions

Step 3. Allow the 32-bit ASP:NET v4.x extension. To do this, right click the first ASP.NET v4.x

extension and select Allow from the options menu that appears.

Figure 35 – Enabling the 32-bit extension


Appendix C : Enabling Windows Integrated Authentication

Appendix CAppendix C: Enabling Windows Integrated Authentication

This section will explain how to enable Windows Integrated Authentication in VISUAL Message Center

Web applications. This solution requires editing preferences in the following applications:

• Internet Information Services (IIS) Manager

• Web Browser

C.1 Internet Information Server Settings

C.1.1 IIS 5 and IIS 6

To enable Windows Integrated Authentication in IIS 5 and IIS 6:

Step 1. Open the Internet Information Services Manager.

Click the Windows Start button> Administrative Tools > Internet Information

Services (IIS) Manager

Step 2. Expand the Web Sites branch if it is collapsed and right-click on the specific application

Web Site to open the Properties window

Step 3. Click the Directory Security tab and click the Edit button in the Authentication and

access control dialog box.

Step 4. Make sure the Enable anonymous access check box is cleared.



Figure 36 – Clear the Enable anonymous access check box

C.1.2 IIS 7.xTo enable Windows Integrated Authentication in IIS 7:

Step 1. Open the Control Panel

Step 2. Click Turn Windows features on or off under the Programs option to open the

Windows Features window.

Step 3. Navigate to Windows Authentication by expanding the following branches: Internet

Information Services > World Wide Web Services > Security and select the

Windows Authentication check box.

Figure 37 – Installing Windows Authentication component

Step 4. Open the Internet Information Services Manager.

Click the Windows Start button > Administrative Tools > Internet Information

Services (IIS) Manager

Step 5. Expand the Sites branch if it is collapsed and right-click on the Web Site for the specific

application to open the Properties window and double-click Authentication.

Step 6. Disable Anonymous Authentication and enable Windows Authentication by selecting

them in list and clicking the enable or disable action in the Actions panel.



Figure 38 – Enable Windows authentication

C.2 Web Browser Settings

C.2.1 Firefox 3.xTo enable Windows Integrated Authentication in Firefox 3.x:

Step 1. Open Firefox

Step 2. Type: about:config In the address bar

Step 3. Navigate to the network.automatic-ntlm-auth.trusted-uris preference in the

Preference List.

Right-click on the Preference Name, select Modify and type: http://serverName

where serverName is the name of the server where specific application is installed.

TIP: Multiple sites can be added separated by a comma.

Figure 39 – Modify the network.automatic-ntlm-auth.trusted-uris preference in Firefox

C.2.2 Internet Explorer To enable Windows Integrated Authentication in Internet Explorer:

Step 1. Open Internet Explorer

Step 2. Click Tools from the menu bar and select Internet Options.

Step 3. Click the Security tab, select Local intranet and click the Sites button to add a new

site.



Figure 40 – Select Local intranet and click the Sites button

Step 4. In the Internet Options window click the Advanced tab and select the Enable

Integrated Windows Authentication check box.

Click OK to exit and save settings.

Note If you are using Internet Explorer 8 a pop up will be appear.

Click the Advanced button, enter the base URL address where the specific application is

installed and then click Add.

Figure 41 – Adding a new intranet site in Internet Explorer 8



Figure 42 – Enable Integrated Windows Authentication


Appendix D : Manual Configuration for Windows 2003 x64


Appendix DAppendix D: Manual Configuration for Windows 2003 x64

When running in 32-bit mode on a 64-bit OS Microsoft Windows 2003 Server, once the application has

been deployed, the following configurations may need to be performed:

Step 1. Run Internet Information Services (IIS) in 32-bit mode by running the following line in a

command window:

Cscript %SystemDrive%\inetpub\AdminScripts\adsutil.vbs set w3svc/AppPools/Enable32bitAppOnWin64 1

The last number in the above line is to set 32-bit to True. See the Microsoft Knowledge

Base article 894435.

Step 2. Restart the IIS service. Type the following in the command window:

net stop w3svc /y & net start w3svc

The net stop and net start commands force IIS services to re-read the registry.

Step 3. Navigate to the Windows folder in the command window. Locate the

Microsoft.NET\Framework\v2.0.50727 folder.

Step 4. Run the aspnet_regiis -i command. This will register the 32-bit .NET subsystem.

Step 5. Open IIS Manager (inetmgr) and ensure that the web extension for ASP.NET (.NET

Framework 2.0 32 bits) is allowed.

Step 6. Open IIS Manager (inetmgr) and ensure that your application is able to use ASP.NET

framework version 2.0.

Tip Leave the command window open because it will be needed again

Note The above will require all applications to run in 32-bit mode only. If there are other

applications running on the IIS server that must run in 64-bit mode, then the 32-bit

application should be run on a different server.

Appendix E : Manual Configuration for Windows 2008 x64 and Vista x64


Appendix EAppendix E: Manual Configuration for Windows 2008 x64

and Vista x64

If you are running Windows 2008 x64 / Vista x64 (IIS7 for 64 bits), an extra modification step is required.

To modify a Windows 2008 x64 / Vista x64 (IIS7 for 64 bits) system:

Step 1. Open the IIS Manager, navigate to Application Pools, right-click in the

DefaultAppPool, and select Advanced Settings.

Step 2. In the General section, change the property for the Enable 32-Bit Applications to True.

Figure 43 – Enable 32-Bit Applications to True

Appendix F : How to Configure Machine Keys on ASP.NET When Installing on a Web Farm (Cluster)

Appendix FAppendix F: How to Configure Machine Keys on ASP.NET

When Installing on a Web Farm (Cluster)

When installing a .NET web application on a Web Farm, it is important that all the servers of the farm

generate the same machine key. This has to be done because when a web page is served by a server

and then served by another in a further request, the engine fires an exception if the keys do not match.

This happens because it thinks that someone might have tempered with the View State.

F.1 Generating the KeysTo generate the keys:

Step 1. Download the generateKey.exe program from:

http://www.tango04.info/products/generateKey.exe

Step 2. Run the program using the following command line argument:

generateKey.exe 24 64

More detailed information on both the problem and the solution can be found in the following KB articles

from Microsoft:

http://support.microsoft.com/default.aspx?scid=kb;en-us;323744

http://support.microsoft.com/kb/312906/EN-US/

F.2 Setting the KeysTo set the keys:

Step 1. After running the program, copy the output to the clipboard.

Step 2. Then open the file:

C:\Windows\Microsoft.NET\Framework\v2.0.50727\config\machine.config

Note The two integer values 24 and 64 represent the size of the decryption and the validation

keys respectively.

Because the code is using a random number generator, the output is different every time.


Appendix F : How to Configure Machine Keys on ASP.NET When Installing on a Web Farm (Cluster)

Step 3. In the machine.config file, find the <system.web> XML tag and add the contents of

the clipboard (the output of the program) inside the tag.

You will have to copy the same machine key to this file on every server of the cluster.

Note The path might be different if the system is a 64 bit OS.

Remember to make a backup of the file first!


Appendix G : Configuring SSL Connections

Appendix GAppendix G: Configuring SSL Connections

This appendix explains how to configure a Secure Sockets Layer (SSL) connection for Internet

Information Server (IIS).

G.1 IIS 6

G.1.1 Prepare a Certificate Signing Request (CSR)

To prepare a CSR:

Step 1. Open the Internet Information Services (IIS) Manager: Click Start > Administrative

Tools > Internet Information Services (IIS) Manager.

Step 2. Expand the server (local computer) and Web Sites branches and right-click on the Web

site on which you want to install the new certificate and select Properties.

Step 3. In the Web Site tab enter a port to be used for SSL in the SSL port field.

Figure 44 – Web site properties

Tip Make sure you use a port that is not already being used. You can check the properties of

each configured Web site in the IIS Manager to see what ports are currently in use.



Step 4. Click the Directory Security tab and click the Server Certificate button to open the Web

Server Certificate Wizard.

Figure 45 – Directory Security tab, click the Server Certificate button to start the wizard

Step 5. Click Next to continue, select the Create a new certificate selection box and click

Next.

Figure 46 – Create a new certificate

Step 6. Accept the default options and complete the organizational information and

geographical information fields as required until you reach the Certificate Request File

Name window.

Note If the View Certificate button is not grayed out, you already have a certificate protecting this

site. Check the certificate has not expired.



Figure 47 – Certificate Request File Name

Step 7. Enter a file name and location for the certificate request to be saved in. Click Next to

continue and view a summary of the certificate.

Figure 48 – Certificate summary

Click Next and then click Finish to complete the process.

G.1.2 Request a Certificate from a Certificate VendorAfter creating a CSR the next step is to apply for a certificate from the appropriate certification authority.

The text file that contains the certificate request created in the steps above will be required in order to

complete the certificate order form. Copy and paste the encrypted certificate request in the appropriate

field in the order form.

Complete the vendor's certificate request form, return it complete with the required payment and wait for

the SSL certificate to be delivered by e-mail.

Important The certificate request process varies for each certification authority, so we cannot provide

details of the process in this document. Please contact the appropriate authority for further

information.



G.1.3 Install the CertificateWhen you receive the certificate ensure that your Web server has access to the certification authority’s

response. Now you need to install the new certificate by completing the certificate process started in

section G.1.1 - Prepare a Certificate Signing Request (CSR) on page 45.

To install the certificate:



Step 2. Expand the server (local computer) and Web Sites branches and right-click on the Web

site on which you want to install the new certificate and select Properties.

Step 3. Click the Directory Security tab and click the Server Certificate button to open the Web

Server Certificate Wizard.

Step 4. Select the Process the pending request and install the certificate selection box and

click Next.

Figure 49 – Process the pending request

Step 5. Enter the path and the file name of the certificate file received from the certification

authority.

Figure 50 – Enter the path and file name of the file that contains the certification authority’s response


Step 6. Specify the SSL port to be used by the Web Site.



Figure 51 – Enter the SSL port


Step 7. A summary window will display the information found in the certificate. Click Finish to

complete the process.

Figure 52 – Finish the Certificate Wizard

G.2 IIS 7

G.2.1 Prepare a Certificate Signing Request (CSR)

To prepare a CSR:



Step 2. Select the server (local computer) and double-click Server Certificates to open.



Figure 53 – Open Server Certificates in IIS Manager

Step 3. Click Create Certificate Request in the Actions pane.

Figure 54 – Create Certificate Request

Step 4. Enter the required information for the certificate and click Next.

Figure 55 – Enter the certificate information



Step 5. Enter a file name and location for the certificate request to be saved in and click Finish

to complete the process.

Figure 56 – Certificate Request File Name

G.2.2 Request a Certificate from a Certificate VendorAfter creating a CSR the next step is to apply for a certificate from the appropriate certification authority.

The text file that contains the certificate request created in the steps above will be required in order to

complete the certificate order form. Copy and paste the encrypted certificate request in the appropriate

field in the order form.

Complete the vendor's certificate request form, return it complete with the required payment and wait for

the SSL certificate to be delivered by e-mail.

G.2.3 Install the CertificateWhen you receive the certificate ensure that your Web server has access to the certification authority’s

response. Now you need to install the new certificate by completing the certificate process started in

section G.2.1 - Prepare a Certificate Signing Request (CSR) on page 49.

To install the certificate:



Step 2. Select the server (local computer) and double-click Server Certificates to open.

Step 3. Click Complete Certificate Request in the Actions pane.

Important The certificate request process varies for each certification authority, so we cannot provide

details of the process in this document. Please contact the appropriate authority for further

information.



Figure 57 – Complete Certificate Request

Step 4. Enter the path and the file name of the certificate file received from the certification

authority. Click OK.

Figure 58 – Enter the path and file name of the file that contains the certification authority’s response

Step 5. To associate the certificate with the site, click Bindings... in the Actions pane.

Figure 59 – Associate the certificate with the site

Click Add... to create a new Web site connection for the certificate.



Figure 60 – Create a new Web site connection for the certificate

Enter the Web site port details and select the certificate from drop-down list box and

click OK.

Figure 61 – Select the certificate

The new binding appears in the list. Click Close to complete the process.

Figure 62 – Click Close to finish


Appendix H : Using a SQL Server Session State in ASP.NET

Appendix HAppendix H: Using a SQL Server Session State in ASP.NET

By default, VISUAL Message Center Dashboards uses the In Process session state (mode session) in

ASP.NET. This is not wrong in itself, but can lead to IIS closing a user’s session if IIS is restarted or

Application Pool Recycling is desired (and enabled). Recycling the application pool can improve

performance by reducing the memory consumption of the application, by removing ASP.NET objects

that are not being used anymore from memory. Therefore, if you are having memory issues after a

period of time with the application, it is recommended that you enable recycling. To prevent user

sessions from being closed, you can change the session state that ASP.net uses for Dashboards to SQL

Server session state, thus transferring the burden of session state memory from the Dashboards Web

server to a SQL Server database.

First, create the database in your SQL Server:

Step 1. Open a Windows command console.

Step 2. Go to C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727>

Step 3. Enter the following command:

aspnet_regsql.exe -S SERVERNAME -U username -P password -ssadd -sstype c -d T04_ASPState

where:

− SERVERNAME is the name of the server where the SQL Server engine is located

− username is the user name of a user with database-creation permissions on said

SQL Server, or the user name of a Windows user with said authority

− password is said user’s password

You have added an ASPState database to your SQL Server: the database T04_ASPState.

Warning Using SQL Server Session State will degrade Dashboards’ performance. Nevertheless,

generally, this performance degradation will not be noticed by the end user.

For example:

C:\Windows\Microsoft.NET\Framework\v2.0.50727>aspnet_regsql.exe -S localhost -U jdoe -P pass5678 -ssadd -sstype c -d T04_ASPState



Next, update the Dashboards web.config file:

Step 1. Open the file web.config, usually located here:

C:\Program Files\Tango04\Dashboards\Web

Step 2. Find the key word sessionState.

Step 3. Change the existing line:

<sessionState cookieless="false" timeout="30" />

to:

<sessionState allowCustomSqlDatabase="true" mode="SQLServer" sqlConnectionString="data source=SERVERNAME;initial catalog=T04_ASPState;user id=username;password=password" cookieless="false" timeout="30"/>

where:

− SERVERNAME is the name of the server where the SQL Server engine is located

− username is the user name of a user with database-creation permissions on said

SQL Server, or the user name of a Windows user with said authority

− password is said user’s password

Also note:

• If you don’t insert the line allowCustomSqlDatabase="true" you will see the error: Parser Error Message: The sqlConnectionString attribute or the connection string it refers to cannot contain the connection options 'Database', 'Initial Catalog' or 'AttachDbFileName'. In order to allow this, allowCustomSqlDatabase attribute must be set to true and the application needs to be granted unrestricted SqlClientPermission. Please check with your administrator if the application does not have this permission.

• If you don’t specify an initial catalog (e.g. initial catalog=T04_ASPState),

ASP.NET assumes you want to use the default ASPState database. If you have a

default ASPState database and it isn't an ASP.NET 2.0 database, you will get this

error: Exception Details: System.Web.HttpException: Unable to use SQL Server because ASP.NET version 2.0 Session State is not installed on the SQL server. Please

For example:

<sessionState allowCustomSqlDatabase="true" mode="SQLServer" sqlConnectionString="data source=localhost; initial catalog=T04_ASPState; user id=T04StateSession;password=Tango1234" cookieless="false" timeout="30"/>

Note:

Notice that user id does not necessarily have to be the SQL SysAdmin user

you chose when creating the database in your SQL Server.

T04StateSession or other users (and passwords) can be used, as long as

they have full access to the new database.



install ASP.NET Session State SQL Server version 2.0 or above. Stack Trace: [HttpException (0x80004005): Unable to use SQL Server because ASP.NET version 2.0 Session State is not installed on the SQL server. Please install ASP.NET Session State SQL Server version 2.0 or above.] System.Web.SessionState.SqlPartitionInfo.GetServerSupportOptions(SqlConnection sqlConnection) +252 System.Web.SessionState.SqlPartitionInfo.InitSqlInfo(SqlConnection sqlConnection) +91 System.Web.SessionState.SqlStateConnection..ctor(SqlPartitionInfo sqlPartitionInfo) +426 System.Web.SessionState.SqlSessionStateStore.GetConnection(String id, Boolean& usePooling) +282 System.Web.SessionState.SqlSessionStateStore. SetAndReleaseItemExclusive(HttpContext context, String id, SessionStateStoreData item, Object lockId, Boolean newItem) +178 System.Web.SessionState.SessionStateModule.OnReleaseState(Object source, EventArgs eventArgs) +355 System.Web.SyncEventExecutionStep.System.Web.HttpApplication. IExecutionStep.Execute() +92 System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +64

Step 4. Save and close the file web.config.


Appendix I : Contacting Tango/04

Appendix IAppendix I: Contacting Tango/04

EMEA (European, Middle-Eastern & African) Headquarters

Tango/04 Computing Group S.L.

Avda. Meridiana 358, 12 B-C

08027 Barcelona Spain

Phone: +34 93 274 0051

Fax: +34 93 345 1329

[email protected]

www.tango04.com

Latin American Headquarters

Barcelona/04 Computing Group SRL

Avda. Federico Lacroze 2252, Piso 6

1426 Buenos Aires Capital Federal

Argentina

Phone: +54 11 4774-0112

Fax: +54 11 4773-9163

[email protected]

www.barcelona04.com

North America (USA & Canada)

Tango/04 Computing Group USA

PO Box 3301

Peterborough, NH 03458 USA

Phone: 1-800-304-6872

Fax: 858-428-2864

[email protected]

www.tango04.com

Sales Office in Brazil

Tango/04 Computing Group Brasil

Rua Turiassú, 591 - 5º Andar

Perdizes

Cep: 05005-001 São Paulo

Brasil

Phone: +55 (11) 3675 6228

Fax: +51 1 211-2526

[email protected]

www.tango04.com.br

Sales Office in Chile

Barcelona/04 Computing Group Chile

Guardia Vieja 255, Of. 1601

Providencia

Santiago

Chile

Phone: +56 2 234 0898

Fax: +56 2 234 0865

[email protected]

www.barcelona04.com

Sales Office in Columbia

Barcelona/04 Computing Group Colombia

Calle 125 nº 19-89, Piso 5º

Bogotá, D.C.

Colombia

Phone: + 57(1) 658 2664

Fax: +51 1 211-2526

[email protected]

www.barcelona04.com


Mailto:[email protected]

www.tango04.com


www.barcelona04.com


www.barcelona04.com


www.tango04.com


www.barcelona04.com

www.tango04.com.br


www.barcelona04.com

www.barcelona04.com

Sales Office in France

Tango/04 France

La Grande Arche

Paroi Nord 15ème étage

92044 Paris La Défense France

Phone: +33 01 40 90 34 49

Fax: +33 01 40 90 31 01

[email protected]

www.tango04.fr

Sales Office in Italy

Tango/04 Computing Group Italy

Viale Garibaldi 51

13100 Vercelli VC Italy

Phone: +39 0161 56922

Fax: +39 0161 259277

[email protected]

www.tango04.it

Sales Office in Peru

Barcelona/04 Computing Group Perú

Calle Isaac Albeniz 555, Dpto 201 Urb

Las Magnolias

San Borja

L 27 Lima

Perú

Phone: +51 1 640-9168

Fax: +51 1 211-2526

[email protected]

www.barcelona04.com

Sales Office in Switzerland

Tango/04 Computing Group Switzerland

18, Avenue Louis Casaï

CH-1209 Genève

Switzerland

Phone: +41 (0)22 747 7866

Fax: +41 (0)22 747 7999

[email protected]

www.tango04.fr



www.tango04.it


www.tango04.fr


www.barcelona04.com


www.tango04.fr

About Tango/04 Computing Group

Tango/04 Computing Group is one of the leading developers of systems management and automation

software. Tango/04 software helps companies maintain the operating health of all their business

processes, improve service levels, increase productivity, and reduce costs through intelligent

management of their IT infrastructure.

Founded in 1991 in Barcelona, Spain, Tango/04 is an IBM Business Partner and a key member of IBM's

Autonomic Computing initiative. Tango/04 has more than a thousand customers who are served by over

35 authorized Business Partners around the world.

Alliances

Awards

Partnerships IBM Business Partner

IBM Autonomic Computing Business Partner

IBM PartnerWorld for Developers Advanced Membership

IBM ISV Advantage Agreement

IBM Early code release

IBM Direct Technical Liaison

Microsoft Developer Network

Microsoft Early Code Release


Legal Notice

The information in this document was created using certain specific equipment and environments, and it is limited in

application to those specific hardware and software products and version and releases levels.

Any references in this document regarding Tango/04 Computing Group products, software or services do not mean

that Tango/04 Computing Group intends to make these available in all countries in which Tango/04 Computing Group

operates. Any reference to a Tango/04 Computing Group product, software, or service may be used. Any functionally

equivalent product that does not infringe any of Tango/04 Computing Group's intellectual property rights may be used

instead of the Tango/04 Computing Group product, software or service

Tango/04 Computing Group may have patents or pending patent applications covering subject matter in this

document. The furnishing of this document does not give you any license to these patents.

The information contained in this document has not been submitted to any formal Tango/04 Computing Group test

and is distributed AS IS. The use of this information or the implementation of any of these techniques is a customer

responsibility, and depends on the customer's ability to evaluate and integrate them into the customer's operational

environment. Despite the fact that Tango/04 Computing Group could have reviewed each item for accurateness in a

specific situation, there is no guarantee that the same or similar results will be obtained somewhere else. Customers

attempting to adapt these techniques to their own environments do so at their own risk. Tango/04 Computing Group

shall not be liable for any damages arising out of your use of the techniques depicted on this document, even if they

have been advised of the possibility of such damages. This document could contain technical inaccuracies or

typographical errors.

Any pointers in this publication to external web sites are provided for your convenience only and do not, in any

manner, serve as an endorsement of these web sites.

The following terms are trademarks of the International Business Machines Corporation in the United States and/or

other countries: iSeries, iSeriese, iSeries, i5, DB2, e (logo)®Server IBM ®, Operating System/400, OS/400, i5/OS.

Microsoft, SQL Server, Windows, Windows NT, Windows XP and the Windows logo are trademarks of Microsoft

Corporation in the United States and/or other countries. Java and all Java-based trademarks and logos are

trademarks or registered trademarks of Sun Microsystems, Inc. in the United States and/or other countries. UNIX is a

registered trademark in the United States and other countries licensed exclusively through The Open Group. Oracle

is a registered trade mark of Oracle Corporation.

Other company, product, and service names may be trademarks or service marks of other companies.


visual message center dashboard server installation guide · step 1. download microsoft .net...

Documents