Enterprise Server. Application Sentinel for SQL Server Installation and Configuration Guide. Application Sentinel 2.0 and Higher

(1)

Enterprise Server

Application Sentinel for SQL Server

Installation and Configuration Guide

(2)

(3)

Enterprise Server

Application Sentinel for SQL Server

Installation and Configuration Guide

unisys

(4)

NO WARRANTIES OF ANY NATURE ARE EXTENDED BY THIS DOCUMENT. Any product or related information described herein is only furnished pursuant and subject to the terms and conditions of a duly executed agreement to purchase or lease equipment or to license software. The only warranties made by Unisys, if any, with respect to the products described in this document are set forth in such agreement. Unisys cannot accept any financial or other responsibility that may be the result of your use of the informaion in this document or software material, including direct, special, or consequential damages.

You should be very careful to ensure that the use of this information and/or software material complies with the laws, rules, and regulations of the jurisdictions with respect to which it is used.

The information contained herein is subject to change without notice. Revisions may be issued to advise of such changes and/or additions.

Notice to U.S. Government End Users: This is commercial computer software or hardware documentation developed at private expense. Use, reproduction, or disclosure by the Government is subject to the terms of Unisys standard commercial license for the products, and where applicable, the restricted/limited rights provisions of the contract data rights clauses.

Correspondence regarding this publication can be e-mailed to [email protected].

Unisys is a registered trademark of Unisys Corporation in the United States and other countries.

(5)

Tables

3–1. Application Sentinel for SQL Server Components and Software on

Windows Partition . . . 3–2 4–1. Application Sentinel for SQL Server Components and Software on Client

(8)

(9)

Section 1 Introduction

This document provides installation instructions and configuration information for the Unisys Application Sentinel for SQL Server software. The installation topics provide information critical to installing and using the Application Sentinel for SQL Server software. For installation and operation information on Unisys Server Sentinel software and other third-party applications, refer to the documentation that accompanies those particular software products.

Preinstallation Considerations

Before installing the Application Sentinel for SQL Server software components, you should consider which components you want to use and where these components are to be installed. The components of Application Sentinel for SQL Server include:

• Optimizer for SQL Server

Optimizer for SQL Server simplifies performance analysis and tuning of one or multiple instances of SQL Server running on an ES7000 server.

• Spotlight on SQL Server

Spotlight on SQL Server is a diagnostic and problem-resolution tool for Microsoft SQL Server.

• Self-Healing for Clustered SQL Server

Self-healing for clustered SQL Server enhances the functioning of Microsoft SQL Server on Unisys enterprise server clusters.

• Launch Pad

The launch pad is a graphical user interface that provides a central location for

administering and managing the Application Sentinel software and the corresponding components. In addition, you enter your Application Sentinel license key using the licensing utility in launch pad.

When installing Application Sentinel for SQL Server software, you can install all of the preceding components by choosing Recommended Installation, or you can install individual components by choosing Custom Installation.

(10)

• All components include client workstation software.

• The client workstation software can be installed on the management server.

• Optimizer for SQL Server is the only Application Sentinel for SQL Server component that has server software to install on the management server.

• While all components manage the Windows partition, only launch pad and optimizer for SQL Server include software that is installed on the partition.

Management Server Considerations

You can use a single management server to manage multiple Windows partitions across multiple servers, within some constraints. The recommended minimum configuration for a management server is sufficient to get started managing a few database instances. If you plan to track performance very closely, manage a large number of systems, or install the Application Sentinel for SQL Server software along with other management products (such as Server Sentinel) on the same management server, you should configure a larger management server.

If you are setting up a new system and a new management server, you can simplify your environment by configuring a single management server to handle the Server Sentinel management server software, the AppManager® server and repository, and the

Application Sentinel software. However, if you are adding Application Sentinel software to a system that has been running for some time, you should consider configuring a new management server to handle the Application Sentinel software and avoid the risk of changing the existing management server.

(11)

Multiple Server Models or Different Server Sentinel Versions

If your environment includes multiple different server models or multiple different Server Sentinel versions, you might consider configuring multiple management servers to avoid mixing incompatible versions of software on a single management server.

Role-based Security

The Application Sentinel software limits access to tasks through the use of role-based security. The user roles of Administrator, Operator, and Observer are implemented using Microsoft Windows groups, and are established during installation of Server Sentinel or Application Sentinel software. For further information on assigning and managing the security roles, see “Sentinel Roles” later in this guide.

Migration Considerations

If you currently have Application Sentinel for SQL Server 1.1 installed on your system, you can migrate to Application Sentinel for SQL Server 2.0 release. Refer to “Migrating from Application Sentinel 1.1 to Application Sentinel 2.0” later in this guide for details.

Installation and Configuration Overview

Installing and configuring Application Sentinel for SQL Server includes the following steps. 1. On each applicable system (that is, Windows partition, management server, and client

workstation), perform the following steps. Details are provided for each system later in this guide.

a. Install any required software that is not available on the Application Sentinel for SQL Server installation CD-ROM.

b. Insert the Application Sentinel for SQL Server installation CD-ROM. This starts the installation assistant which guides you through meeting component installation requirements and installing the components.

c. Use the System Software Requirements area of the installation assistant screen to install any redistributable software provided on the Application Sentinel for SQL Server installation CD-ROM.

d. Install the Application Sentinel software.

2. Configure the installed Application Sentinel for SQL Server components as outlined in “Configuring Application Sentinel for SQL Server Components” later in this guide. 3. Using launch pad, install your Application Sentinel for SQL Server license. If you are

using Application Sentinel for SQL Server on an evaluation basis, the 120-day evaluation license is installed automatically when you first use the product.

4. You are now ready to use the Application Sentinel for SQL Server software. Refer to the user documentation of an individual component for detailed usage instructions.

(12)

(13)

Section 2 Management Server Installation

The management server is a small auxiliary server containing management software and databases and is used by administrators to manage the Windows partition. One

management server can manage multiple partitions and cluster nodes.

Note: Optimizer for SQL Server is the only Application Sentinel for SQL Server

component that has server software to install on the management server.

Prerequisites

The recommended minimum configuration for the management server is as follows:

• A 1-gigahertz (GHz) Intel Pentium III CPU

• 512 megabytes (MB) of RAM

• 100-megabits per second (Mbps) Ethernet LAN adapter

• CD-ROM drive

• Microsoft Windows 2000 Server Service Pack 3 or Service Pack 4; Windows 2000 Advanced Server Service Pack 3; or Windows Server 2003, Enterprise Edition, operating system

• Microsoft Internet Explorer 6.0 or later

• Microsoft SQL Server 2000 with Service Pack 3

Note: The management server cannot be installed on a domain controller.

Installation Tasks

The installation tasks must be completed on the management server in the following order:

(14)

Installing Server Sentinel Software

The scheduling and notification feature of Optimizer for SQL Server is integrated with NetIQ AppManager from Server Sentinel. If you plan to use this feature, install the Server Sentinel 2.2 or later management server software. Follow the installation instructions provided with the Server Sentinel software.

Installing Windows Components

Remote COM+ and MSMQ must be installed and enabled on the management server.

Windows 2000 Advanced Server or Windows 2000 Server

Microsoft Message Queuing (MSMQ) is included on the Windows 2000 CD-ROM. Perform the following steps to enable MSMQ on your management server: 1. Insert the Windows 2000 CD-ROM into the CD-ROM drive.

2. From the Control Panel, double-click Add/Remove Programs and then click

Add/Remove Windows Components.

3. Select the Message Queuing Services check box, and click Next.

4. If the Terminal Services Setup window appears, leave the default selection and click

Next.

The Message Queuing Type window appears.

5. Leave the default selection (Message Queuing Server) and click Next.

6. Select Message Queuing will not access a directory service and click Next. 7. Follow the screen instructions if you are asked to insert a CD-ROM or DVD or if you

are asked to provide a network server location where the required installation components can be found.

8. Click Finish to close the wizard.

Windows Server 2003, Enterprise Edition

MSMQ is included on the Windows Server 2003 CD-ROM.

Perform the following steps to enable remote COM+ and MSMQ on your management server:

1. Insert the Windows Server 2003 CD-ROM into the CD-ROM drive.

2. From the Control Panel, double-click Add/Remove Programs and then click

Add/Remove Windows Components.

3. Select Application Server and click Details.

4. Select the Enable network COM+ access check box and the Message

(15)

5. Clear the Active Directory Integration check box. 6. Select Common and then click Details.

7. Select the check boxes for Core Functionality and Local Storage. 8. Click OK in the Common dialog box.

9. Click OK in the Message Queuing dialog box. 10. Click OK in the Application Server dialog box.

11. Click Next in the Windows Component Wizard dialog box. 12. Click Finish to close the wizard.

Installing Microsoft SQL Server

The optimizer for SQL Server requires access to a SQL Server instance in which to store management data. Typically, this is a separate SQL Server instance from the ones that the product manages and optimizes. The optimizer for SQL Server creates databases named Unisys_OptFramework and System_Warehouse. It is useful to know these database names in the event you have optimizer for SQL Server share a SQL Server instance with other products.

You have the following options from which to choose for the SQL Server instance.

• Install Microsoft SQL Server 2000 Service Pack 3 on the management server. This option provides you with the best performance and scalability.

Note: If you choose this option, install the SQL Server instance now.

For information about installing Microsoft SQL Server 2000, refer to the MSDN Web site at http://www.msdn.microsoft.com.

• Use a SQL Server instance located on a remote system.

Notes:

- If you choose this option, install the SQL Server instance now.

- If you choose to use a SQL Server instance that resides on a system other than

the management server, you must perform an additional step to allow the optimizer for SQL Server to access that instance. On the machine where SQL Server is installed, create a local account called ASConfigAcct$ with the same password used on the management server. You can use the Windows Computer Management dialog box to perform this task. Then create a SQL Server log-in for this account.

• Install Microsoft SQL Server 2000 Desktop Engine (MSDE) with Service Pack 3 from the Application Sentinel installation CD-ROM. MSDE is recommended only for casual use, testing, and training.

Note: If you decide to use MSDE, then skip this step as the MSDE instance is

installed along with the Application Sentinel software.

If you choose to use MSDE from the Application Sentinel for SQL Server installation CD, a reboot of the management server might be necessary. Perform the following steps to avoid having to reboot the management server:

(16)

1. Prior to installing Applciation Sentinel for SQL Server, shut down all the services and applications on your systems that are using SQL Server components. 2. Install Application Sentinel for SQL Server (including MSDE).

3. After installing, be sure to restart any of the services or applications that you shut down before installing MSDE.

Installing Redistributables

Insert the Application Sentinel for SQL Server installation CD-ROM and select the management server installation options. Installation assistant provides a list of missing requirements. If the system requirements for MDAC, Windows Installer, and Microsoft .NET Framework have not been met, then click Install Redistributables, and installation assistant installs them for you.

Installing Windows Installer

The Application Sentinel software requires Microsoft Windows Installer 2.0 or later. If this software is not already installed, the installation assistant offers to install it from the CD-ROM. Click Yes to install Windows Installer 2.0.2600.2. Following this installation, you must restart your system. If you decline to install Windows Installer, the installation of Application Sentinel software fails.

Installing Microsoft Data Access Components (MDAC)

You must have MDAC 2.71 Service Pack 1A or later on the management server, the Windows partition, and the client workstation.

If this minimum requirement is not met, perform one of the following:

• Install 2.71.9040.2 using the Install Redistributables option on the System

Requirements menu.

Note: If your system already meets the minimum requirement, but has a version

earlier than 2.71.9040.2, you can install 2.71.9040.2 from the Custom Installation menu.

• Download MDAC from the Microsoft Universal Data Access Download page at http://www.microsoft.com/data/download.htm#26sp1info.

Installing Microsoft .NET Framework

The Microsoft .NET Framework 1.1 or later is a redistributable program. The installation assistant checks for the presence of .NET Framework on the management server, Windows partition, and client workstation. If you are asked whether you want to install Microsoft .NET Framework, click Yes and continue with the installation.

Note: This applies only to 32-bit partitions.

(17)

Installing Adobe Reader

Click Adobe Reader.

Follow the instructions provided by the installation program and accept the default values.

Note: At the end of the installation, if you receive a warning to remove all previous

versions of the software, wait approximately 15 seconds and the dialog box will disappear.

Installing Application Sentinel Software

Once all prerequisites have been met, you can install the Application Sentinel for SQL Server software. From installation assistant, choose Recommended Installation to install all components, or Custom Installation to select individual components to install. If you want to have the client workstation on the management server, you can also install client workstation software at this time.

When you start the installation, you are prompted for the following information:

Providing a Password for the Application Sentinel Account

The Application Sentinel account is a local account installed on the management server and Windows partition to provide Application Sentinel components access to Windows partition interfaces. The user name of the account is ASConfigAcct$. You need to provide a password for this account. This password must match the one created on all Windows partitions controlled by the management server. Refer to “Changing Passwords” in this guide for information on changing the password.

Specifying SQL Settings

The SQL Settings dialog box appears next. Select the option for the management server SQL Server instance that you chose earlier.

(18)

(19)

Section 3 Windows Partition Installation

The Windows partition is the partition on an ES7000 server that runs the production workload.

Prerequisites

Windows partitions can contain the following software:

• Microsoft Windows 2000 Advanced Server Service Pack 3; Windows 2000 Datacenter Server Service Pack 3; Windows Server 2003, Enterprise Edition; or Windows Server 2003, Datacenter Edition, operating system

• Unisys Server Sentinel 2.2 or later software

• Microsoft SQL Server 2000 Service Pack 3

• Additional Application Sentinel software components

Notes:

• Before you can install any of the features of Application Sentinel, you must accept the End-User License Agreement.

• The Microsoft hotfix for Knowledge Base article number 841401 must be applied to each instance of SQL Server on the Windows partition prior to running an analysis of the partition with optimizer for SQL Server. Without this hotfix, collection of run-time metrics can fail, and inaccurate analysis results can be produced. If the product version for a SQL Server instance, as displayed by the SQL Server Enterprise, is 8.00.935 or greater, then the hotfix is already installed.

(20)

Table 3–1. Application Sentinel for SQL Server Components and Software on Windows Partition Software Optimizer for SQL Server Spotlight on SQL Server Self-healing for Clustered SQL Server Launch Pad Microsoft Data Access Components (MDAC) Yes Windows

Installer Yes Yes Yes Yes Server Sentinel software Yes (Process Manager from Server Sentinel 2.2) Yes (Cluster Manager from Server Sentinel 2.2) Microsoft .NET Framework

Yes Yes Yes

Internet

Explorer 6.0 Yes

Installation Tasks

The installation tasks must be completed on the Windows partition in the following order: 1. Install Server Sentinel software.

2. Install SQL Server hotfix. 3. Install redistributable software.

4. Installing Application Sentinel software.

Installing Server Sentinel Software

Based on your CMP-based server model, install the Server Sentinel 2.2 or higher software on the Windows partition before installing the Application Sentinel software. This action ensures that various interdependencies between Server Sentinel and the Application Sentinel software are met. Follow the installation instructions provided with the Server Sentinel software.

(21)

Installing SQL Server Hotfix

Install the Microsoft hotfix for Knowledge Base article number 84101. This hotfix must be applied to each instance of SQL Server on the Windows partition before analyzing the partition with optimizer for SQL Server.

Note: If the product version for a SQL Server instance is 8.00.935 or greater, the hotfix is

already applied to the instance of SQL Server.

Installing Redistributables

Install the Application Sentinel software on the Windows partition using the installation CD-ROM, and selecting the Windows partition installation options.

Installation assistant provides a list of missing requirements. If the system requirements for MDAC, Windows Installer, and Microsoft .NET Framework have not been met, then click Install Redistributables, and installation assistant installs them for you.

Installing Microsoft Data Access Components (MDAC)

Installing Windows Installer

Installing Microsoft .NET Framework

(22)

For more information about installation requirements and download instructions for the Microsoft .NET Framework, refer to the MSDN Web site at

http://www.msdn.microsoft.com/.

Installing Adobe Reader

Click Adobe Reader.

Follow the instructions provided by the installation program and accept the default values.

Note: At the end of the installation, if you receive a warning to remove all previous

versions of the software, wait approximately 15 seconds and the dialog box will disappear.

Installing Application Sentinel Software

Once all prerequisites have been met, you can install the Application Sentinel for SQL Server software. From installation assistant, choose Recommended Installation to install all components, or Custom Installation to select individual components to install.

When you start the installation, you are prompted for the following information:

Providing a Password for the Application Sentinel Account

If you are installing optimizer for SQL Server, you are asked to provide a password for the Application Sentinel account. The user name for the Application Sentinel account is ASConfigAcct$. The password you provide must match the password created on the management server. Refer to “Changing Passwords” in this guide for information on changing the password.

(23)

Section 4 Client Workstation Installation

Prerequisites

The client workstation software can also be installed on the management server. The following software can run on the client workstation:

• Microsoft Windows 2000 Professional Service Pack 3 or Windows XP Professional Service Pack 1

• Macromedia Flash 7.0

• Client interfaces for Application Sentinel software components

The following table lists the software that can be installed for the Application Sentinel for SQL Server components on the client workstation.

Table 4–1. Application Sentinel for SQL Server Components and Software on Client Workstation

Software Optimizer forSQL Server Spotlight onSQL Server

Self-healing for Clustered SQL Server Launch Pad Windows Installer

Yes Yes Yes Yes Microsoft .NET Framework Yes Yes Internet Explorer 6.0 Yes

Installation Tasks

The installation tasks must be completed on the client workstation in the following order. 1. Install redistributable software.

2. Install Application Sentinel software.

(24)

Installing Redistributables

Install the Application Sentinel software on the client workstation using the installation CD-ROM, and selecting the client workstation installation options.

The Macromedia Flash 7.0 player is automatically installed by the installation assistant on the client workstation.

Installation assistant provides a list of missing requirements. If the system requirements for MDAC, Windows Installer, and Microsoft .NET Framework have not been met, then click Install Redistributables, and installation assistant installs them for you.

Installing Microsoft Data Access Components (MDAC)

Installing Windows Installer

Installing Microsoft .NET Framework

For more information about installation requirements and download instructions for the Microsoft .NET Framework, refer to the MSDN Web site at

http://www.msdn.microsoft.com/.

(25)

Installing Application Sentinel Software

Once all prerequisites have been met, you can install the Application Sentinel for SQL Server software. From installation assistant, choose Recommended Installation to install all components, or Custom Installation to select individual components to install.

Installing the Unisys Customized J2RE for Server

Sentinel

Clients that access Server Sentinel navigation require the Sun Microsystems Java 2 Runtime Environment (J2RE) 1.4.2_02 or higher and certain Unisys customized

deployment and security files. If the appropriate level of J2RE or the Unisys customized files are not installed on your system, you are prompted to install them when you first launch Server Sentinel.

If J2RE and the Unisys customized files are not installed, you can use Installation Assistant to install this software. To do so, perform the following steps from the Installation

Assistant:

1. Click Custom Installation.

2. Click Unisys Customized J2RE for Server Sentinel. 3. Follow the instructions displayed on the screen.

When the Sun Microsystems end-user license agreement is displayed, accept this license agreement. If prompted for a usercode and password, use the usercode and password required to access Server Sentinel.

Note: If your system uses J2RE 1.4.2_03 or higher, it is recommended that you do not

use Installation Assistant to install J2RE 1.4.2_02. Instead, install the appropriate version of J2RE, and then launch Server Sentinel. You are prompted to copy the Unisys

customized files.

For more information about the J2RE, refer to the Sun Microsystems Java Web site at java.sun.com.

(26)

(27)

Section 5 Configuring Application Sentinel for

SQL Server Components

This section describes how to configure the Application Sentinel for SQL Server components.

Sentinel Roles

Your user privileges are based on your assignment to one of a set of Sentinel roles. Three user roles corresponding to Windows groups are defined within Application Sentinel. Each role is allowed a specific set of functions.

Administrator

This role enables you to administer the management environment (for example, configure the management software or delete items from a log) as well as manage systems. Tasks that require Windows Administrator privilege to execute are included in this role.

Sentinel Operator

This role enables you to manage systems. Operator has read/write access to most management functions. Tasks that require Windows Administrator privilege are excluded from this role.

Sentinel Observer

This role enables you to observe systems. Observer has read access to most management functions.

Note: Refer to the System Planning Guide for your server to obtain information on creating

domain groups (Domain Sentinel Admins, Domain Sentinel Operators, Domain Sentinel Observers) and additional details on Sentinel roles.

Assigning Sentinel Roles

(28)

1. On the desktop, right-click My Computer and then click Manage. The Computer Management window appears.

2. In the left pane, expand Local Users and Groups. 3. Select the Groups folder.

4. Right-click Administrators and click Add to Group. 5. Click Add.

6. Expand the Look in list and click your domain name. Wait for the list of names to appear in the middle pane. 7. Click your Domain Sentinel Admins group name. 8. Click Add.

9. Click OK.

Verify that the Domain Sentinel Admins group appears as a member of the local Administrators group.

10. Click OK.

11. Repeat steps 4 through 10 for the roles Sentinel Operator and Sentinel Observer, adding the Domain Sentinel Operators and Domain Sentinel Observers groups to them respectively.

Optimizer for SQL Server

Caution

The Microsoft hotfix for Knowledge Base article 841401 must be applied to each instance of SQL Server on the Windows partition prior to running an analysis of the partition with the optimizer for SQL Server.

This hotfix corrects a Microsoft SQL Server metric collection issue related to the Total Active Transaction count for a SQL instance. Without this hotfix, collection of run-time metrics can fail, and inaccurate analysis results can be produced.

Sentinel Roles

The following Sentinel roles apply to optimizer for SQL Server.

• Administrator – users can use all features.

• Sentinel Operator – users can use all features.

• Sentinel Observer – users can monitor session status, view the data collected during session execution, and examine optimizer results.

(29)

Spotlight on SQL Server

After you have installed the Application Sentinel software and before you can use Spotlight on SQL Server to analyze a target system, you must first establish a connection to the system.

To establish a connection, double-click the New Connection icon on the Spotlight on SQL Server window. Follow the set-up choices to establish your new connection.

Sentinel Roles

Spotlight on SQL Server does not use Sentinel roles.

Self-Healing for Clustered SQL Server

The self-healing for clustered SQL Server software installation loads a rules importer component that allows you to import two custom SQL Server rules (Basic and Enhanced) to the cluster manager rules database on the Windows partition. You can then run the rules importer over again as necessary for additional clusters.

The self-healing for clustered SQL Server software is only for Unisys enterprise server partitions running Windows 2000 Datacenter Server or Windows 2000 Advanced Server, Microsoft SQL Server 2000 (including SQLAgent), and partitions having Server Sentinel 2.0 or higher cluster manager (including any and all applicable Interim Corrections) installed on a cluster in the domain. Microsoft Cluster Service (MSCS), is a prerequisite for Server Sentinel cluster manager operations.

If you are going to make the Enhanced SQL Server rule active on the cluster rather than using the Basic SQL Server rule, there are some file copy and customization steps that need to be followed first. These are covered in the online help for the software.

Sentinel Roles

All features are available to users assigned the Administrator role. No other Sentinel roles apply to self-healing for clustered SQL Server.

Launch Pad

The launch pad installation sequence has no dependencies. However, all other Application Sentinel components must be installed, and configured if necessary, in order for the tool invocation capabilities of the launch pad to function properly.

For the launch pad to invoke tools, Microsoft Internet Explorer 6.0 or later is required on the client workstation. In addition, the Macromedia Flash 7.0 player is automatically installed during the installation process on the client workstation.

The configuration utility enables you to configure the launch pad initialization (.ini) file. This .ini file configures the client workstation so that it can launch the Application Sentinel

(30)

components for a given list of Windows partitions that you wish to monitor. The list of partitions associated with a management server is maintained on the management server. If you use the launch pad from another client, the same list is automatically available. To configure the launch pad and create an .ini file for the first time, perform the following: 1. On the Start menu, point to Programs, then Unisys Application Sentinel, and

click LaunchPad.

The Launch Pad Configuration dialog box appears.

2. Type the names of the management server and the Server Sentinel host (the Service Processor of the ES7000 system) in the designated boxes.

Note: You must enter the names of the management server and the Server Sentinel

host in order to minimally configure the launch pad. You can use the same machine name for both fields.

3. Click OK.

4. Click Add to add Windows partitions.

5. (Optional) Select one or both of the following check boxes:

• Add LaunchPad Start menu item, which is selected by default

• Add LaunchPad desktop shortcut, which is not selected by default

6. Click Close to save your changes.

To make configuration changes later on, select Configure, then Configure Launch

Pad from the Options tab.

Refer to the Launch Pad Help for more information on the launch pad.

(31)

Section 6 Licensing Management

The features of Application Sentinel are under license management.

Entering License Keys

Use the launch pad to enter or update license information.

Note: Obtain the license key from the License Key Form document shipped with your

Application Sentinel order.

1. Start the launch pad on the client workstation.

(32)

(33)

Section 7 Application Sentinel Maintenance

Changing Passwords

During installation, a local administrative account is created on the management server and on each Windows partition. This account is called ASConfigAcct$. The optimizer for SQL Server is configured to run with this account.

During installation you are asked to define the password for this account. This password must be the same on all Windows partitions and the management server.

The Application Sentinel Maintenance Utility allows you to change the password for this account. You might want to change the password for security reasons or because you made a mistake during installation and need to correct the password on one or more machines. You do not need to know the original password in order to change it. However, you must be logged in with a user account with administrative privileges when you initiate the Application Sentinel Maintenance Utility.

The Application Sentinel Maintenance Utility must be run on each machine where the password is to be changed. To initiate the Application Sentinel Maintenance Utility, perform the following:

1. On the Start menu, point to Programs, then Unisys Application Sentinel, and click Maintenance Utility

2. On the Password tab, enter the new password twice. 3. Click Change Password.

The Application Sentinel Maintenance Utility can also be used to correct the configuration of an Application Sentinel component. This would be necessary, for example, if someone accidentally removed a required COM+ application package through the Windows Component Services dialog box.

To fix a configuration, perform the following: 1. Select the Component Configuration tab.

(34)

Maintaining the System Telemetry Warehouse

The system telemetry warehouse is a database (called System_Warehouse) in the instance of SQL Server or MSDE selected during installation on the management server. This database contains run-time metrics gathered from the Windows partition during the collection phase of optimizer for SQL Server sessions.

The system telemetry warehouse database can be maintained using the system telemetry warehouse user interface. To open the interface, perform the following steps:

1. Go to the Application Sentinel launch pad. 2. Select the Options tab.

3. Select Administer System Telemetry Warehouse.

The following selections on the first dialog box of the interface should be used for maintenance tasks:

• Back Up and Delete Data

• Restore Data

• Warehouse Options

Refer to the help text for specific instructions on using the various functions of the system telemetry warehouse interface. In addition, refer to the help text for the optimizer for SQL Server for information about the names of collections that this component adds to the warehouse.

(35)

Section 8 Migrating from Application Sentinel 1.1

to Application Sentinel 2.0

Application Sentinel for SQL Server has a three-tier architecture composed of client workstations, a management server, and one or more Windows partitions. This section explains how to migrate existing Application Sentinel systems to the Application Sentinel for SQL Server 2.0 release level.

Migration Tasks

Updating Management Servers and Client Workstations

To migrate your systems to the new release,

• Install Application Sentinel for SQL Server 2.0 on the management server.

• Install Application Sentinel for SQL Server 2.0 on the client workstation.

These steps remove the previous version of the product and replace it with Application Sentinel for SQL Server 2.0. The optimizer for SQL Server database is backed up and then migrated to the new format used by this release. Additionally, Microsoft .NET Framework 1.1 is installed if it is not present on the system. Only one release version of the product can be installed on a management server or client at a time. Management servers and clients must run the same levels of Application Sentinel for SQL server.

Updating Existing ES7000 System Partitions

(36)

Migration Considerations

Installing Other Application Sentinel Products

If you install Application Sentinel for Resource Management 2.0 or Application Sentinel for Consolidation 2.0 on your management server or system partition, then you must also upgrade existing management servers and clients to the Application Sentinel for SQL Server 2.0 release.

Changes in Dependencies

Application Sentinel for SQL Server 2.0 uses an agentless collection technique instead of agent-based collection. As a result, MSMQ is no longer required on the partition.

Persistent Storage Considerations

Application Sentinel for SQL Server automatically backs up and migrates its associated optimizer for SQL Server database as part of the upgrade installation. This persistent storage database is backed up to a file with the format <database name>_<version>.bak. For example, the backup of an optimizer for SQL Server 2.0 database using the default database name is Unisys_OptFramework_207.bak. The backup directory is named as follows:

• For SQL 2000: <installation location>\Microsoft SQL Server\MSSQL\BACKUP

• For MSDE: %windir%System32

Returning to Application Sentinel 1.1

After running Application Sentinel for SQL Server 2.0, if you decide you want to return to Application Sentinel 1.1, you can do so by performing the following procedure.

Caution

Analysis data processed under Application Sentinel 2.0 will be lost as a result of the downward migration.

1. Uninstall Application Sentinel for SQL Server 2.0.

2. Reinstall Application Sentinel for SQL Server 1.1 and apply the most recent Interim Corrections (ICs). Refer to the Unisys support site for the most recent IC versions. 3. Restore the associated optimizer for SQL Server database for the product on the

management server.

(37)

Section 9 Uninstalling Application Sentinel for

SQL Server 2.0

This section discusses uninstalling the Application Sentinel for SQL Server 2.0 software.

Removing Unisys Application Sentinel License

Control

Removing License Control through Add\Remove Programs is prohibited if any installable features for Application Sentinel for SQL Server, Application Sentinel for Consolidation, or Application Sentinel for Resource Management are listed as currently installed programs. Refer to the Application Sentinel for Consolidation Installation and Configuration Guide or the Application Sentinel for Resource Management Installation and Configuration Guide, for the installed program names for those products. The Application Sentinel for SQL Server installed program names are listed as follows:

• Unisys Application Sentinel optimizer for SQL Server

• Unisys Application Sentinel launch pad

• Application Sentinel SQL Server version

System Telemetry Warehouse Data File Folders

When the system telemetry warehouse is installed, the following file folders are created in the installation folder:

• CMInfo

• localCMInfo

• SWInfo

• Backup

• Config

(38)

(39)

Index

A

assigning Sentinel roles, 5–1

C

changing passwords, 7–1 client workstation, 4–1, 4–2 configuring, 4–1 configuring, 2–1, 3–1, 4–1, 5–2 client workstation, 4–1 launch pad, 5–3 management server, 2–1 optimizer for SQL Server, 5–2 Windows partition, 3–1 connecting, 5–3 Spotlight on SQL Server, 5–3

I

installing, 2–1, 2–2, 2–3, 2–4, 3–1, 3–2, 3–3, 4–2, 5–3

Application Sentinel for SQL Server, 5–2, 5–3

optimizer for SQL Server, 5–2

self-healing for clustered SQL Server, 5–3 Spotlight on SQL Server, 5–3 launch pad, 5–3 Microsoft SQL Server, 2–3 MSMQ, 2–2 on client workstation, 4–1 on management server, 2–1 on Windows partition, 3–1 optimizer for SQL Server, 5–2

self-healing for clustered SQL Server, 5–3 Server Sentinel software, 3–2

Spotlight on SQL Server, 5–3 SQL Server hotfix, 3–3

L

launch pad, 5–3 configuring, 5–3 installation tasks, 5–3

M

Macromedia Flash 5.0, 4–1 Maintenance Utility, 7–1 management server, 2–1 overview, 2–1

Microsoft Message Queuing (MSMQ), 2–2 Microsoft SQL Server 2000 Desktop Engine

(MSDE), 2–3 Microsoft SQL Server, 2–3

installing, 2–3

O

optimizer for SQL Server, 5–2 overview, 2–1, 3–1 client workstation, 4–1 management server, 2–1 Windows partition, 3–1

P

passwords, 2–4, 3–3, 7–1 changing, 7–1 setting up, 2–4, 3–3

S

self-healing for clustered SQL Server, 5–3 Sentinel roles, 5–1

Server Sentinel software, 3–2 installing, 3–2 setting up passwords, 2–4, 3–3 management server, 2–4 Windows partition, 3–3 Spotlight on SQL Server, 5–3 SQL Server hotfix, 3–3

(40)

U

(41)

(42)

Enterprise Server. Application Sentinel for SQL Server Installation and Configuration Guide. Application Sentinel 2.0 and Higher

Enterprise Server

Application Sentinel for SQL Server

Installation and Configuration Guide

Enterprise Server

Application Sentinel for SQL Server

Installation and Configuration Guide

unisys

Contents

Tables

Section 1

Introduction

Preinstallation Considerations

Management Server Considerations

Multiple Server Models or Different Server Sentinel Versions

Role-based Security

Migration Considerations

Installation and Configuration Overview

Section 2

Management Server Installation

Prerequisites

Installation Tasks

Installing Server Sentinel Software

Installing Windows Components

Windows 2000 Advanced Server or Windows 2000 Server

Windows Server 2003, Enterprise Edition

Installing Microsoft SQL Server

Installing Redistributables

Installing Windows Installer

Installing Microsoft Data Access Components (MDAC)

Installing Microsoft .NET Framework

Installing Adobe Reader

Installing Application Sentinel Software

Providing a Password for the Application Sentinel Account

Specifying SQL Settings

Section 3

Windows Partition Installation

Prerequisites

Installation Tasks

Installing Server Sentinel Software

Installing SQL Server Hotfix

Installing Redistributables

Installing Microsoft Data Access Components (MDAC)

Installing Windows Installer

Installing Microsoft .NET Framework

Installing Adobe Reader

Installing Application Sentinel Software

Providing a Password for the Application Sentinel Account

Section 4

Client Workstation Installation

Prerequisites

Installation Tasks

Installing Redistributables

Installing Microsoft Data Access Components (MDAC)

Installing Windows Installer

Installing Microsoft .NET Framework

Installing Application Sentinel Software

Installing the Unisys Customized J2RE for Server

Sentinel

Section 5

Configuring Application Sentinel for

SQL Server Components

Sentinel Roles

Assigning Sentinel Roles

Optimizer for SQL Server

Caution

Sentinel Roles

Spotlight on SQL Server

Sentinel Roles

Self-Healing for Clustered SQL Server

Sentinel Roles

Launch Pad

Section 6

Licensing Management

Entering License Keys

Section 7

Application Sentinel Maintenance

Changing Passwords

Maintaining the System Telemetry Warehouse

Section 8

38321097-000