Blade Logic Installation

Property of BladeLogic, Inc. Strictly confidential and proprietary

BladeLogic Installation Guide

Version 7.4.3

Property of BladeLogic, Inc. BladeLogic Installation GuideStrictly confidential and proprietary

© 2008 BladeLogic, Inc.

All rights reserved. This product or document is protected by copyright and distributed under licenses restricting its use, reproduction, distribution and decompilation. No part of this product or document may be reproduced in any form by any means without prior written authorization of BladeLogic, Inc.

BladeLogic, Enabling Continuous Configuration, and Network Shell are registered trademarks or trademarks of BladeLogic, Inc., in the USA and/or other countries. All other brand names, product names, or trademarks belong to their respective holders.

BladeLogic reserves the right to alter product offerings and specifications at any time without notice, and is not responsible for typographical or graphical errors that may appear in this document.

Restricted Rights Legend: Use, duplication, or disclosure by the government is subject to restrictions asset forth in subdivision (c)(1)(ii) of the Rights in Technical Data and Computer Software Clause at FAR 52.227-7013.

BladeLogic, Inc.10 Maguire Road, Building 3Lexington, MA 02140www.bladelogic.com


Contents

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Intended Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Documentation Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Procedural Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

System Text . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Path Separators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

<external-files.zip> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Related Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Supported Operating Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Minimum System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Configuration Manager, Provisioning Manager, and Network Shell . . . . . . 16

Network Shell Only . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Application Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

RSCD Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

File Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

PXE Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Data Store Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Patch Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Reporting Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

GUI Support on UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

VMware Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Perl Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Required Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Using Databases with BladeLogic . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Database System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Setting Up a BladeLogic Database Schema . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Setting up an Oracle Database Schema . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

4


Setting up a SQL Server Database Schema . . . . . . . . . . . . . . . . . . . . . . . . 26

Setting Up the Schemas for BladeLogic Reports . . . . . . . . . . . . . . . . . . . . . . . 28

Setting Up a Reporting Data Warehouse . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Using the Database to Change File Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Changing the File Server Using Oracle . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Changing the File Server Using SQL Server . . . . . . . . . . . . . . . . . . . . . . . . 36

Optimizing an Oracle Database for BladeLogic Reports . . . . . . . . . . . . . . . . . . 39

Recommendations for Gathering Statistics . . . . . . . . . . . . . . . . . . . . . . . . . 39

Recommendations for Configuring the Database . . . . . . . . . . . . . . . . . . . . 40

Recommendations for the Physical Implementation . . . . . . . . . . . . . . . . . . 40

Upgrading BladeLogic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Using <external-files.zip> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Master Checklist for the Upgrade Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Upgrading Application Servers and Reports Servers . . . . . . . . . . . . . . . . . 43

Determining Sizing Requirements for Oracle Databases . . . . . . . . . . . . . . 44

Upgrading the Core BladeLogic Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Upgrading the BladeLogic Reports Data . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Upgrading Consoles and Agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Upgrading the Provisioning System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Upgrading Client-tier and Middle-tier Components . . . . . . . . . . . . . . . . . . . . . . 58

Upgrading Client-tier and Middle-tier Components on Windows . . . . . . . . . 58

Upgrading Client-tier and Middle-tier Components on UNIX . . . . . . . . . . . . 60

Upgrading RSCD Agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Upgrading the RSCD Agent on Windows . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Silently Upgrading Windows Agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

Upgrading the RSCD Agent on UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

Silently Upgrading UNIX Agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Upgrading BladeLogic Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

Upgrading BladeLogic Reports on Windows . . . . . . . . . . . . . . . . . . . . . . . . 68

Upgrading BladeLogic Reports on UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Upgrading the PXE Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

Upgrading a PXE Server on Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

5


Upgrading a PXE Server on UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

Using BladeLogic Data Migration Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

Validating Oracle Environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

Running Data Upgrades . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

Viewing Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

Exporting Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

Viewing Results from Previous Sessions . . . . . . . . . . . . . . . . . . . . . . . . . . 89

Installing and Uninstalling on Windows . . . . . . . . . . . . . . . . . . . . . . 91

Installing Client-tier and Middle-tier Components on Windows . . . . . . . . . . . . . 91

Performing a Typical Install (Configuration Manager and Network Shell) . . 92

Performing a Full Installation (All BladeLogic Components) . . . . . . . . . . . . 97

Performing a Custom Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

Installing Only Network Shell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113

Modifying, Repairing, or Removing Client-tier and Middle-tier Components

on Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

Modifying an Existing Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

Repairing an Existing Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120

Removing All Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121

Installing and Uninstalling RSCD Agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123

Installing the RSCD Agent on Windows . . . . . . . . . . . . . . . . . . . . . . . . . . 124

Uninstalling the RSCD Agent on Windows . . . . . . . . . . . . . . . . . . . . . . . . 130

Installing Agents in a Replicated Domain Controller Environment . . . . . . 132

Using Installation Mode Rather Than Execution Mode . . . . . . . . . . . . . . . . . . 133

Determining the Current Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134

Temporarily Invoking Installation Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . 134

Installing BladeLogic Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135

Installing BladeLogic Reports on Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . 136

Installing BladeLogic Reports on UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146

Uninstalling BladeLogic Reports on Windows . . . . . . . . . . . . . . . . . . . . . . . . . 151

Uninstalling BladeLogic Reports on UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151

Setting Up Data Collection Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152

os_config.nsh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152

6


collect_agent_logs.nsh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153

populate_reports.nsh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154

update_delete_dependencies.nsh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154

Installing and Uninstalling on Solaris, Linux, AIX, and HP-UX . . . 156

Installing All BladeLogic Components on UNIX . . . . . . . . . . . . . . . . . . . . . . . 156

Installing Client Utilities (Configuration Manager, Provisioning Manager, and

Network Shell) on UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164

Installing Only Network Shell on UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167

Installing Only an RSCD Agent on UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169

Uninstalling All BladeLogic Components on UNIX . . . . . . . . . . . . . . . . . . . . . 173

Setting Up the Provisioning System . . . . . . . . . . . . . . . . . . . . . . . . 175

PXE Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175

Configuring the DHCP Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176

Configuring a DHCP Server on Windows . . . . . . . . . . . . . . . . . . . . . . . . . 177

Configuring a DHCP Server on Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179

Installing and Uninstalling the PXE Server . . . . . . . . . . . . . . . . . . . . . . . . . . . 181

Installing the PXE Server on Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . 182

Installing the PXE Server on UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190

Uninstalling the PXE Server on Windows . . . . . . . . . . . . . . . . . . . . . . . . . 193

Configuring the TFTP Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194

Red Hat 7.3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195

Red Hat 8.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195

Red Hat AS 2.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195

Red Hat AS 3.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195

Red Hat AS 4.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195

SuSE 8.x . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196

SuSE 8.x AMD 64 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196

SuSE 9.x . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196

SuSE 9.x AMD 64 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196

SuSE 10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197

Setting Up a Data Store . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197

Stocking the Data Store . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199

7


Windows Operating Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200

Red Hat Linux Operating System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201

SuSE 8.x Operating System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201

SuSE 8.x AMD 64 Operating System . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202

SuSE 9.x Operating System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203

SuSE 9.x AMD 64 Operating System . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204

SuSE 10 Operating System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205

ESX Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206

Windows Drivers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210

All Operating Systems: fdisk.exe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213

Preparing Agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213

Setting Up a Multiple Database Provisioning Environment . . . . . . . . . . . . . . . 215

Editing the PXE Server’s config.xml . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216

Editing pxe.conf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220

Switching From Multi-Database to Single-Database Mode . . . . . . . . . . . . 221

JumpStart Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222

NIM Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224

Ignite Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225

Related Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227

Licensing Agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227

Using the Post-Install Configuration Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . 228

Starting Network Shell, Configuration Manager, and Provisioning Manager . 234

Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234

Solaris, Linux, AIX, and HP-UX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235

Starting the Application Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235

Loading Pre-packaged Content . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235

Manually Installing Perl . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236

Installing Perl on Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236

Installing Perl on UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237

Configuring an Application Server for Perl . . . . . . . . . . . . . . . . . . . . . . . . 237

Ensuring a TTY Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238

Setting up BladeLogic for Non-English Locales . . . . . . . . . . . . . . . . . . . . . . . 239

8


Configuring BladeLogic Databases for a Non-English Locale . . . . . . . . . . 239

Setting the Language for the Installers on Windows . . . . . . . . . . . . . . . . . 240

Setting the Language for the Installers on UNIX . . . . . . . . . . . . . . . . . . . . 240


Introduction

The BladeLogic Installation Guide provides installation procedures for all the components of the BladeLogic system on Windows, Solaris, Linux, AIX, and HP-UX.

A BladeLogic system consists of the following software components:• Configuration Manager—A graphical console that provides system administrators with a

point-and-click interface and many powerful utilities for automating data center management.

• Network Shell—A cross-platform shell with full scripting capability that gives seamless access to remote servers from central management workstations. Because Configuration Manager is based on Network Shell, when you install Configuration Manager, you must also install Network Shell.

• Provisioning Manager—A graphical console that lets system administrators provision operating systems onto servers, including the initial provisioning of machines (sometimes called bare metal provisioning or raw iron provisioning).

• Application Server—Software for controlling how Configuration Manager, Provisioning Manager, and Network Shell securely communicate with remote servers and databases.

• RSCD agent (short for Remote System Call Daemon)—Software that must be installed and running on each remote server that the Application Server and Network Shell access.

• BladeLogic Command Line Interface (BLCLI)—A set of utilities that allow you to perform most Configuration Manager tasks from a command line.

• BladeLogic Reports—A reporting tool that makes a variety of data center operations information available to a web-based report viewer.

Intended AudienceThis document is intended for system administrators who manage networks of remote servers.

Documentation Conventions

Procedural DescriptionsAll step-by-step procedural descriptions are flagged with a heading in the left margin that says Procedure. Within a procedure, bold text highlights actions that you should take. For example, a procedural step might read, “From the File menu, select Add.”

Introduction 10


If a procedure requires you to select a sub-option from a menu option, the description includes a > to indicate you are choosing a sub-option. For example, a description might read “select Main Option > Sub-option” rather than saying “select Main Option and then select Sub-option.”

System TextMonospace, serif fonts depict text that a user might enter at the command line or text that a system generates in response to user input. Monospace fonts also depict file system paths. The following is an example of system text:

ERROR: You must be "root" for pkgadd to execute properly.

Path SeparatorsWhen describing paths, this guide uses UNIX-style path separators (forward slashes) except in situations where Windows-style path separators (backslashes) are specifically required.

<external-files.zip>Many procedures reference a file called <external-files.zip>. This convention refers to a zip file named current_release-external-files.zip that BladeLogic customers can use for setting up databases and performing other preliminary procedures before actually installing BladeLogic products. If you do not already have access to <external-files.zip>, contact BladeLogic support.

Icons This guide sometimes describes interactions with icons that appear in the BladeLogic consoles. The following list shows and describes all icons mentioned in this guide. The BladeLogic consoles include other icons, but this user guide does not reference them.

Name Icon Description

Export Log Exports a log.

Show Task Details

Displays detailed information about a task.

Introduction 11


Related Documentation

Title Description Available Formats

BladeLogic Users Guide Documents the functionality of Configuration Manager and Provisioning Manager.

PDF and HTML

BladeLogic Administration Guide

Explains how to perform all the tasks necessary to make the components of a BladeLogic system function together smoothly.

PDF

BladeLogic Reports Users Guide

Explains how to use BladeLogic’s reporting module.

PDF and HTML

Bulk RSCD Agent Installer Guide

Explains how to use BladeLogic’s Bulk RSCD Agent Installer to install or upgrade RSCD agents on multiple servers simultaneously.

HTML and PDF (English only)

BladeLogic Network Shell Command Reference

Provides a complete description of all Network Shell commands and utilities.

PDF and man pages (English only)

BLCLI Help Documents how to use the BladeLogic Command Line Interface.

HTML (English only)


System Requirements

This chapter shows the system requirements for running BladeLogic.

Supported Operating SystemsThe following table shows operating systems that support BladeLogic system components.

OperatingSystem

Version RSCD Patch Mgmt

Configuration / Provisioning

Manager

Network Shell

App Server

Reports Server

PXE TFTP

System Package

AIX (pSeries)

4.3.3

5.1

5.2 *5.3 *6.1 *

HP-UX (PA-RISC)

10.20 *11.00 *11.11 (11i v1)

*

11.23 (11i v2)

*

11.31 (11i v3)

*

HP-UX (IA64)

11.23 (11i v2)

*

11.31 (11i v3)

** *

Novell SuSE (x86)

SLES 8.0

SLES 9.0 *SLES 10.0

*

System Requirements 13


Novell SuSE (x64)

SLES 9.0 *SLES 10.0

*

Red Hat Linux (x86)

7.1

7.2

7.3

8

9

RHEL 2.1 AS/ES

*

RHEL 3.0 AS/ES

*

RHEL 4.0 AS/ES

*

RHEL 5.0 AS/ES

*

Red Hat Linux (x64)

RHEL 3.0 AS/ES

*

RHEL 4.0 AS/ES

*

RHEL 5.0 AS/ES

*

Red Hat Linux (IA64)

RHEL 4.0 AS/ES

Red Hat Linux (pSeries)

RHEL 4.0 AS

OperatingSystem



Manager

Network Shell

App Server

Reports Server

PXE TFTP

System Package



Solaris (sun4u)

2.6

7

8 *9 *10 * *** ***

Solaris (sun4v)

10 *

Solaris (sun4us)

10

Solaris (x86)

8 *9 *10 *

Solaris (x64)

10 *

Windows (x86)

2000

XP

2003

Vista

2008

Windows (x64)

2003 R2 x64

2008

VMware ESX (x86)

2.5

3.0

3.5

OperatingSystem



Manager

Network Shell

App Server

Reports Server

PXE TFTP

System Package



VMware ESX (x64)

3.0

3.5

OperatingSystem



Manager

Network Shell

App Server

Reports Server

PXE TFTP

System Package

* Delivered as a content bundle.

** Requires PHSS_36520 patch to be applied before installing the agent on this platform.

*** You can also run these components in a Solaris Zone, but BladeLogic recommends running them on a single operating system on dedicated hardware for better scalability and performance.



Minimum System RequirementsThe following sections describe system requirements for components of a BladeLogic system. Refer to Supported Operating Systems for details on the versions of the operating systems supported.

Configuration Manager, Provisioning Manager, and Network Shell

OperatingSystems Processor/Speed Memory Available

Disk Space Screen

Novell SuSE • minimum - Intel Pentium III, 500 MHz

• recommended - Intel Pentium IV, 2 GHz or better

• minimum - 256 MB

• recommended - 512 MB or better

200 MB • 1024 x 768• minimum

256 colors

Red Hat Linux • minimum - Intel Pentium III, 500 MHz




200 MB • 1024 x 768• minimum

256 colors

Windows • minimum -Intel Pentium III, 500 MHz




200 MB • 1024 x 768• minimum

256 colors

Solaris and the Solaris J2SE recommended patch set for Java RunTime Environment (JRE) version 1.5.0_05 (included in a BladeLogic installation) Download the J2SE patch cluster from sunsolve.sun.com.

• minimum - UltraSparc II, 550 MHz

• recommended - UltraSparc III, 1 GHz or better



200 MB • 1024 x 768• minimum

256 colors

http://sunsolve.sun.com



Network Shell OnlyNetwork Shell on any platform requires a minimum of 64 MB of RAM when running —BladeLogic recommends 128 MB or better. Installation of Network Shell on any platform requires a minimum of 30 MB of available disk space — BladeLogic recommends 50 MB or better.

Application Server

RSCD AgentAn RSCD agent on any platform requires 1 MB of RAM when running. Installation of an RSCD agent on any platform requires 10 MB of available disk space.

In addition, you need to consider the amount of space needed in the future for the Transactions folder. The Transactions folder, which is within the agent install directory, contains copies of the BLPackages you deploy on the agent. BladeLogic stores these copies, by default, in case you want to roll back changes from a Deploy Job. You can change the default behavior by unchecking the Allow rollback – Leave rollback files on target for later use option for the associated Deploy Jobs (see the BladeLogic Users Guide for more information). If you uncheck this option for all Deploy Jobs targeted for the agent machine, the only file written to the directory is the deployment log. If you choose to keep the default

OperatingSystems Processor/Speed Memory Available

Disk Space

Novell SuSE • minimum - 2 Xeon, 2 GHz• recommended - 4 Xeon, 3 GHz or

better

• minimum - 2 GB• recommended - 4 GB

50 GB

Red Hat Linux • minimum - 2 Xeon, 2 GHz• recommended - 4 Xeon, 3 GHz or

better


50 GB

Solaris and the Solaris J2SE recommended patch set for Java RunTime Environment (JRE) version 1.5.0_05 (included in a BladeLogic installation) Download the J2SE patch cluster from sunsolve.sun.com.

• minimum - 2 UltraSparc III, 1.3 GHz

• recommended - 4 UltraSparc III, 1.3 GHz or better

• minimum - 1 GB• recommended - 2 GB or

better

50 GB

Windows • minimum - 2 Xeon, 2 GHz• recommended - 4 Xeon, 3 GHz or

better


50 GB




setting and leave the rollback files in the Transactions folder for your deployments, the location of the Transactions directory must have enough space to accommodate the number of BLPackages you plan to deploy multiplied by the average size of your BLPackages.

For BladeLogic’s patch analysis functionality to be operable, the Microsoft XML (MSXML) 2.5 or higher parser must be installed on the server where the RSCD agent is installed. MSXML is installed by default on Windows 2003 and XP machines but not on Windows 2000. You can install the RSCD agent on a machine where MSXML is not installed, but patch analysis will not function correctly until MSXML 2.5 or later is installed.

In order to mount an agent on a UNIX/Linux server, the showmount command must be available on the server.

File ServerA file server must have, as a minimum, 72 GB of available, non-redundant, disk space. BladeLogic recommends that the file server have 200 GB or more of available RAID 5 disk space.

DatabaseBladeLogic is compatible with the following databases:• Oracle 10g Standard or Enterprise Edition, release 2 or greater with latest patch• Oracle 9i Enterprise Edition, release 2 or greater with latest patch • SQL Server 2005 • SQL Server 2000 (Service Pack 3a or more recent)

Use vendor recommendations when sizing BladeLogic databases.

PXE ServerA PXE Server has minimal processor resources and memory requirements. Installation of a PXE Server on any platform requires 1 GB of available disk space.

Data Store ServerTypically, a PXE Server and a data store server are set up on the same machine, although that configuration is not required. The data store server holds the operating system installation files used for performing network installations of operating systems. Depending on the number of distinct operating systems you are provisioning, you may need 1 to 10 GB of disk space to hold these files. At minimum the data store server should have 256 MB of RAM. In addition, the data store server should have a fast, reliable network connection.



Additional requirements for the data store server vary, depending on whether it is set up on Windows or Linux and whether you are provisioning Windows or Linux to a bare metal server. The following table details data store server requirements for all possible provisioning scenarios:

Patch ManagementIn order to deploy all missing patches on a target server, the minimum recommended free space on the drive containing the staging directory of the target server is 3 GB. The disk space required during staging depends on the number of missing hotfixes on the server.

Reporting EnvironmentThe BladeLogic reporting environment is based on BladeLogic Configuration Manager and an Oracle or SQL Server database.

Database Server

Requirements for the database supporting the reporting environment vary, as described below.

An Oracle database installation must meet the following requirements:• Oracle 10g Standard or Enterprise Edition, release 2 or greater with latest patch; Oracle

9i Enterprise Edition, release 2 or greater with latest patch.• DBA privileges (that is, “system” account privileges) are required to create database

tables for the reporting data warehouse.

A SQL Server database must meet the following requirements:• SQL Server 2005 SQL Server 2000 (Service Pack 3a or later).• DBA privileges (that is, “System Administrator” account privileges) are required to

create database tables for the reporting data warehouse.

If Provisioning

If Data Store Server Is Running: Additional Requirements

Windows Windows None

Linux • SMB must be running on data store server

Linux Windows • IIS must be running on data store server

Linux • HTTP server must be running on data store server

• SMB must be running on data store server



BladeLogic Reports Server

The following are minimum requirements for the server where BladeLogic Reports is installed:

Reports Server Software

The reports server must have the Oracle or SQL Server client software installed. The version of the client software must correspond to the version of the database server software. The following are the specific software requirements:

OperatingSystems Processor/Speed Memory

Available Disk

Space

Windows • minimum - 1 Xeon, 1.5 GHz

• recommended - 2 Xeon, 2 GHz or better

• minimum - 1 GB• recommended - 2

GB or better

12 GB

Solaris and the Solaris J2SE recommended patch set for Java RunTime Environment (JRE) version 1.5.0. (included in a BladeLogic installation) Download the J2SE patch cluster from sunsolve.sun.com.

• minimum - 1 UltraSparc III, 900 MHz

• recommended - 2 UltraSparc III, 1 GHz or better


GB or better

12 GB

Novell SuSE • minimum - 1 Xeon, 1.5 GHz



GB or better

12 GB

Red Hat Linux • minimum - 1 Xeon, 1.5 GHz



GB or better

12 GB

Database Loader Platform Support Installation Requirements

Oracle SQL*Loader (sqlldr)

Windows and UNIX When installing the client, choose the Administrator installation type. The insta-client installation type is not sufficient.Note: The user that runs the populate_reports.nsh script must be able to run sqlldr. This user must have the Oracle environment variables set and sqlldr must be in his or her path.




Viewing Reports

To view BladeLogic Reports, use a web browser to access a URL that displays report results. BladeLogic Reports supports the following web browsers:

GUI Support on UNIXThe OS-specific xll libraries for the supported variants of UNIX are required to run the Configuration Manager and Provisioning Manager consoles and the Post-Install Configuration wizard on UNIX.

VMware SupportBladeLogic provides integrated support for VMware ESX 3.0 and VMware ESX 3.5 servers. Using the Servers workspace in Configuration Manager, you can manage the virtual infrastructure of an ESX 3.0 or ESX 3.5 server by accessing the ESX Host node. This node lets you browse, snapshot, audit, package, and deploy virtual infrastructure settings. BladeLogic also supports RSCD agents running on ESX 2.5 servers, but the ESX Host node is not available for ESX 2.5 servers.

SQL Server BCP Windows BCP is installed as part of the Client Tools installation. Running the SQL Server installer with the Connectivity Only option selected is not supported as it does not install BCP.

Browser Version

Mozilla Firefox 1.0.7

Internet Explorer 6.0

Netscape 7.2

Database Loader Platform Support Installation Requirements



Perl SupportBladeLogic provides integrated support for Perl, the script programming language. When you install Network Shell on a platform that can support a BladeLogic Application Server (see list below), BladeLogic’s Perl module is automatically installed. The BladeLogic Perl module is compatible with the versions of Perl listed below:

If you are installing Network Shell and the installer does not find a supported version of Perl on the server, the installer stores the files needed for the Perl module in the BladeLogic installation directory. You can use these files to install and configure Perl at a later time. For information on installing BladeLogic’s Perl module manually, see Manually Installing Perl.

Required PortsBladeLogic uses the ports described in the following table. Your firewall must allow communication through these ports for the associated components to function. The Authentication Service, Application Service, and SRPPort ports are set during the installation of the Application Server. The default values for the ports are listed in the table.

Operating System Version Supported Version of Perl

Windows 2000 ActiveState Perl 5.6.1

XP ActiveState Perl 5.6.1

2003 ActiveState Perl 5.6.1

Solaris 8 Perl 5.6.0

9 Perl 5.6.0

10 Perl 5.6.0

Red Hat Linux 2.1 AS/ES Perl 5.6.0

3.0 AS/ES Perl 5.6.0

4.0 AS/ES Perl 5.6.0

Novell SuSE SLES 8.x Perl 5.6.0

SLES 9.x Perl 5.8.0

SLES 10.x Perl 5.8.0



You can define different port numbers using the blasadmin utility. Setting the port for the Network Shell Proxy Service is done manually using the blasadmin utility.

The blasadmin options used to define these ports are:

appserver AppSvcPortappserver ProxySvcPortappserver SRPPortAuthServer AuthSvcPort

See the BladeLogic Administration Guide for information on using the blasadmin utility.

Functional Component Port Number(by convention) Required? Setup

Authentication Service 9840 Yes Installed by default

Application Service 9841 Yes Installed by default

Network Shell Proxy Service 9842 Required for a Network Shell Proxy Server

Must be set manually

SRPPort 9829 Required for BladeLogic Reports

Installed by default


Using Databases with BladeLogic

This chapter explains how to use a database in conjunction with a BladeLogic system. It also provides the following procedures describing how to set up and maintain an Oracle or SQL Server database:

Setting Up a BladeLogic Database SchemaSetting Up the Schemas for BladeLogic ReportsUsing the Database to Change File ServersOptimizing an Oracle Database for BladeLogic Reports

For information on BladeLogic’s database clean-up utility refer to the BladeLogic Administration Guide.

Database System Requirements BladeLogic supports the following database versions:• Oracle 10g Standard or Enterprise Edition, release 2 or greater with latest patch• Oracle 9i Enterprise Edition, release 2 or greater with latest patch.• SQL Server 2005 • SQL Server 2000 (Service Pack 3a or greater).

When configuring init.ora in Oracle, you must set the following initialization parameters:• db_block_size must be set to 8192. • processes should be set to at least 200. Ideally, the number of processes should be 30

to 40 higher than the total number of job-related and non-job-related database connections configured for the Application Server. If you are running BladeLogic Reports, the number of processes should ideally be 110 to 120 higher than the total number of job-related and non-job-related database connections. For more information on configuring the Application Server, see the BladeLogic Administration Guide.

All other configuration parameters can be set at the discretion of the database administrator.

If you need to connect to an Oracle database as a user who does not own the schema, you are required to have greater permissions than if you were the schema owner and, as such, BladeLogic recommends against it. But, if it is a requirement, the non-schema owner user making the connection must have the following grants:

SELECT ANY TABLEUPDATE ANY TABLEINSERT ANY TABLEDELETE ANY TABLE

Using Databases with BladeLogic 25


CREATE ANY TABLEALTER ANY TABLEDROP ANY TABLESELECT ANY SEQUENCEEXECUTE ANY PROCEDURECREATE VIEW

In addition, all synonyms must be public.

Setting Up a BladeLogic Database SchemaUse these procedures to set up a fresh installation of the BladeLogic database schema for an Oracle or SQL Server database.

If you are using BladeLogic to support a language other than English, refer to Configuring BladeLogic Databases for a Non-English Locale.

Setting up an Oracle Database SchemaUse this procedure to set up a schema for an Oracle database.

Procedure 1 Create the directory that will be used for the tablespace for the new schema.BladeLogic recommends creating a directory on a disk separate from the Oracle system tables, found in .../oradata/<SID>.

2 Copy install scripts from <external-files.zip> into the directory created for the tablespace. If you extract the entire contents of <external-files.zip>, you will find the relevant scripts in the /db_scripts/oracle/ and /db_scripts/oracle/schema directories.

3 Cd to /db_scripts/oracle/schema.

4 Modify the create_oracle_instance.sql script and change the path for data files so the path matches the directory you identified in the first step.

Warning: These procedures are intended for DBAs. Perform the steps in these procedures in the exact order in which they are described.

If you are not using the following scripts to create the schema, please refer to them to determine what privileges are required.

Note: Remember to change both the CREATE TABLESPACE and ALTER DATABASE commands. You must change the path in four places total.



5 Start SQL*Plus using a user name that has sysdba privileges. For example, you might enter:

sqlplus /nologSQL> connect sys/manager as sysdba

6 Run the create_oracle_instance.sql script, as shown below:SQL> @create_oracle_instance.sqlSQL> exit

7 Cd to /db_scripts/oracle.8 Log into the BladeLogic database using the following syntax:

sqlplus <bl_user>/<bl_pwd>@<bl_tns_entry>

where,<bl_user> is the login name for the BladeLogic database user. <bl_pwd> is the BladeLogic database user password.<bl_tns_entry> is the tns entry for the BladeLogic database instance.

9 Start a log and run the master script that corresponds to the character sets for which your database is configured.

SQL> spool create_bladelogic_schema.logSQL> start <master_script>.sql <BL_DATA> <BL_INDEX>SQL> spool off

where,<master_script>.sql is either oracle_master.sql if your database is configured for char/varchar character sets or oracle_nchar_master.sql if your database is configured for nchar/nvarchar character sets.<BL_DATA> is the BladeLogic data tablespace. <BL_INDEX> is the BladeLogic index tablespace.

10 After executing the master script, check the create_bladelogic_schema.log for errors.

Setting up a SQL Server Database SchemaUse this procedure to set up a schema for a SQL Server database.

Procedure 1 Copy install scripts from <external-files.zip> to a location that you can access from the SQL Server console. If you extract the entire contents of <external-files.zip>, you will find the relevant scripts in the /db_scripts/sqlserver directory.

2 Do one of the following:• If using SQL Server 2000, start SQL Server Enterprise Manager.• If using SQL Server 2005, start SQL Server Management Studio.



3 Expand the database server.4 Right-click on the Databases folder and choose New Database. 5 Provide a name for the database, such as “bladelogic.”

6 Create a login for the database and make this user the owner of all objects in the database.

7 Use SQL Server Authentication and create a password for the user you created in step 6.8 Set the default database to the database you created in step 4 and 5.9 Set the default language for the database.10 If you are setting up BladeLogic to support a language other than English, for Collation

name, select the collation for your language that is case-insensitive, accent-sensitive, and (where appropriate) kana-sensitive. For example, if you are setting up BladeLogic for French use French_Cl_AS, and if you are setting up BladeLogic for Japanese use Japanese_Cl_AS_KS.The new database appears under the Databases folder. You can set other options at this time too, but they are not required.

11 If using SQL Server 2000, you can exit SQL Server Enterprise Manager and proceed to the next step. If using SQL Server 2005, to reduce the likelihood of database deadlocks, do the following:

a Right-click on the database server node and select New Query.b Execute the following query:

ALTER DATABASE <db name> SET READ_COMMITTED_SNAPSHOT ON;c You can now exit SQL Server Management Studio.

12 Open a command prompt window.13 Cd to /db_scripts/sqlserver. 14 Run the master script that corresponds to the character sets for which your database is

configured, using the following syntax:<master_script>.bat <db_server> <db_name> <bl_user> <bl_pwd>

where,

<master_script>.bat is either sqlserver_master.bat if your database is configured for char/varchar character sets or sqlserver_nchar_master.bat if your database is configured for nchar/nvarchar character sets.<db_server> is the name of the database server.<db_name> is the name of the BladeLogic database you created in step 4 and 5.

Note: SQL Server database names are case-sensitive. You need to use the same case when specifying the JDBC connections or the load process for the Bladelogic Reports data warehouse will fail.



<bl_user> is the login name for the BladeLogic database user.<bl_pwd> is the BladeLogic database user password.

Setting Up the Schemas for BladeLogic ReportsIn BladeLogic Reports, some reports read data from BladeLogic’s core database, while others read data stored in a data warehouse for reporting. The data warehouse should be set up in a database that is separate from the core BladeLogic database.

If you are using BladeLogic Reports to support a language other than English, refer to Configuring BladeLogic Databases for a Non-English Locale.

Note: When the master script runs, the following warnings may appear:Cannot add rows to sysdepends for the current stored

procedure because it depends on the missing object

'rsave_cond_result_subtree'. The stored procedure will still

be created.

Cannot add rows to sysdepends for the current stored

procedure because it depends on the missing object

'rsave_cr_group_result_subtree'. The stored procedure will

still be created.

These warnings are expected and can be ignored.

Note: The BladeLogic core database and the data warehouse used for reporting must be of the same database type (Oracle or SQL Server). For example, you cannot have an Oracle core database and SQL Server reporting database. Since BladeLogic Reports requires the database client to be installed on the reports server and a UNIX client for SQL Server is not available, if you want to use SQL Server for the core database, the reports server must be running Windows and a SQL Server reporting data warehouse.

Warning: If you are not using the following scripts to create the schema, please refer to them to determine what privileges are required.



Setting Up a Reporting Data WarehouseUse these procedures to set up a fresh installation of the schema for a reporting data warehouse. These procedures are intended for DBAs.

Setting up a Reporting Data Warehouse Schema on Oracle

Use this procedure to set up a schema for a reporting data warehouse on Oracle.

To use the reporting data warehouse, the BladeLogic core database must exist. See Setting up an Oracle Database Schema for a description of how to use Oracle to create the BladeLogic core database.

Procedure 1 Create the directory that will be used for the tablespace for the new schema.BladeLogic recommends creating a directory on a disk separate from the Oracle system tables, found in .../oradata/<SID>.

2 Copy the install scripts from <external-files.zip> into the directory used for the tablespace. If you extract the entire contents of <external-files.zip>, you will find the scripts in the /db_scripts/oracle/schema directory. The scripts you should copy vary, depending on whether your database is configured for char/varchar or nchar/nvarchar character sets. The following table details the scripts you should copy:

Warning: Perform the steps in these procedures in the exact order in which they are described.

Note: Do not use SQL Worksheet or other Oracle GUI tools to run the scripts in the following procedure, as these can put line breaks into the SQL data and lead to a corrupted database. Instead, be sure to use the command-line version of SQL*Plus or other command-line tools.

Script Required For:

create_oracle_db_reports_warehouse.sql All character sets

create_schema_reports_warehouse_oracle.sql char/varchar

create_schema_reports_warehouse_oracle_nchar.sql nchar/nvarchar

create_additional_index_reports_warehouse_oracle.sql

All character sets

create_oracle_sequences_reports_warehouse.sql All character sets

sprocs_warehouse_oracle.sql char/varchar

sprocs_warehouse_oracle_nchar.sql nchar/nvarchar



3. Modify the create_oracle_db_reports_warehouse.sql script and change the path for data files so the path matches the directory you identified in the first step.

4 Start SQL*Plus using a user name that has sysdba privileges. For example, you might enter:

sqlplus /nologSQL> connect sys/manager as sysdba

5 Run the create_oracle_db_reports_warehouse.sql script, as shown below:SQL> @create_oracle_db_reports_warehouse.sqlSQL> quit

6 Log into the BLREPORTS database and run installation scripts in the order shown below.

sqlplus blreports/saSQL> spool create_blreports_schema.logSQL> start create_schema_reports_warehouse_oracle.sql or

create_schema_reports_warehouse_oracle_nchar.sqlSQL> start create_additional_index_reports_warehouse_oracle.sqlSQL> start create_oracle_sequences_reports_warehouse.sql SQL> start sprocs_warehouse_oracle.sql or

sprocs_warehouse_oracle_nchar.sqlSQL> start core_data_reports_warehouse_oracle.sqlSQL> start create_reports_properties_tables_and_metadata_

warehouse_oracle.sql

core_data_reports_warehouse_oracle.sql All character sets

create_reports_properties_tables_and_metadata_warehouse_oracle.sql

All character sets

create_oracle_functions_warehouse.sql All character sets

Note: Remember to change both the CREATE TABLESPACE and ALTER DATABASE commands. You must change the path in four places total.

Note: If you have changed the tablespace names from blreports and blreports_index make the following change to core_data_reports_warehouse_oracle.sql before running it:• Modify the last line of the file as follows:

exec blrpt_set_tablespace('NEW','NEW_INDEX');

where NEW is the name of the new tablespace for tables and NEW_INDEX is the name of the new tablespace for indices.




SQL> start create_oracle_functions_warehouse.sqlSQL> spool off

After executing these scripts, check the create_blreports_schema.log for errors.

Setting up a Reporting Data Warehouse Schema on SQL Server

Use this procedure to set up a schema for a reporting data warehouse on SQL Server.

Procedure 1 Copy the install scripts from <external-files.zip> to a location that you can access from the SQL Server console. If you extract the entire contents of <external-files.zip>, you will find the scripts in the /db_scripts/sqlserver/schema directory. The scripts you should copy vary, depending on whether your database is configured for char/varchar or nchar/nvarchar character sets. The following table details the scripts you should copy:

2 Do one of the following:• If using SQL Server 2000, start SQL Server Enterprise Manager.• If using SQL Server 2005, start SQL Server Management Studio.

3 Expand the database server.4 Right-click on the Databases folder and choose New Database. 5 Provide a name for the database, such as “blreports.”


create_schema_reports_warehouse_sqlserver.sql char/varchar

create_schema_reports_warehouse_sqlserver_nchar.sql

nchar/nvarchar

create_additional_index_reports_warehouse_sqlserver.sql

All character sets

sprocs_warehouse_sqlserver.sql char/varchar

sprocs_warehouse_sqlserver_nchar.sql nchar/nvarchar

core_data_reports_warehouse_sqlserver.sql All character sets

create_reports_properties_tables_and_metadata_warehouse_sqlserver.sql

All character sets

create_sqlserver_functions_warehouse.sql All character sets

Note: Hyphens are not allowed in the reporting data warehouse name. If the data load process encounters a hyphen in the reporting data warehouse name, it will fail. In addition, SQL Server database names are case-sensitive. You need to use the same case when specifying the JDBC connections or the load process will fail.



6 Create a login for the database and make this user the owner of all objects in the database.

7 Use SQL Server Authentication and create a password for the user you created in step 6.8 Set the default database to the database you created in step 4 and 5.9 Set the default language for the database.10 If you are setting up BladeLogic to support a language other than English, for Collation

name, select the collation for your language that is case-insensitive, accent-sensitive, and (where appropriate) kana-sensitive. For example, if you are setting up BladeLogic for French use French_CI_AS, and if you are setting up BladeLogic for Japanese use Japanese_CI_AS_KS.The new database appears under the Databases folder. You can set other options at this time too, but they are not required.

11 Do one of the following:• If using SQL Server 2000, click the new database and then choose SQL Query

Analyzer from the Tools menu.SQL Query Analyzer opens and defaults to the new database.

• If using SQL Server 2005, right-click on the database server node and select New Query.

12 From the File menu, select Open and then select the create_schema_reports_warehouse_sqlserver.sql file that you copied in the first step. If you need nchar/nvarchar character support, select create_schema_reports_warehouse_sqlserver_nchar.sql instead.

13 The contents of the file appear within Query Analyzer. 14 From the Query menu, do one of the following:

• If using SQL Server 2000, select Execute or press F5. After the script executes, ensure that there are no errors.

• If using SQL Server 2005, select the correct database name from the drop-down box and select Execute or press F5. After the script executes, ensure that there are no errors.

15 Repeat the previous two steps for each of the following scripts, running each script in the order listed below:

create_additional_index_reports_warehouse_sqlserver.sqlsprocs_warehouse_sqlserver.sql or sprocs_warehouse_sqlserver_nchar.sqlcore_data_reports_warehouse_sqlserver.sqlcreate_reports_properties_tables_and_metadata_

warehouse_sqlserver.sqlcreate_sqlserver_functions_warehouse.sql



Using the Database to Change File ServersUse the following procedures (one for Oracle and one for SQL Server) to change your file server, the storage location on a file server, or both. These procedures count all references to file servers and file server locations and then change those references so they point to a new file server and file server storage location.

Changing the File Server Using OracleChanging the File Server Using SQL Server

While using these procedures, you may determine that your database includes references to multiple file servers. Typically this happens when files have been stored on a new file server but that server has been “aliased” to point to the name and location of an old file server. This procedure addresses that situation by first changing current file server references to the new file server and then iteratively updating references to other file servers so they also point to the new file server.

The following procedures are based on the following scripts:• file_server_check_<database type>.sql—Identifies the current settings for your file

server and file server storage location and tells how many items in the database refer to that setting. It also tells whether there are references to other file servers and how many references there are to each.

• file_server_change_<database type>.sql (or .bat for SQL Server)—Changes all file server and file server storage location values in the database that refer to the current settings. It also sets the value of the file server and file server storage location in the system_property table to values you provide in the form of parameters.

• file_server_change_<database type>_system_property.sql (or .bat for SQL Server)—Changes the current values of the file server and file server storage location in the system_property table to the values of arguments you provide. This script is only needed if there are references to a file server and file server storage location other than the current setting.

Changing the File Server Using OracleUse this procedure to change a file server by updating file server references in an Oracle database.

Procedure 1 In the file structure extracted from <external-files.zip>, copy the following scripts from /bl_<current release>/db_scripts/oracle/utility/file_server_change to a directory from which you can access SQL*Plus.

file_server_check_oracle.sqlfile_server_change_oracle.sqlfile_server_change_oracle_system_property.sql

2 Cd to the directory where you copied the scripts.



3 Determine how many file servers your database references by using SQL*Plus to execute the following command:sqlplus <user>/<password>@<service_name> @file_server_check_oracle.sql

Output for One File ServerIf your database references only one file server, the output looks something like this:

File Server and root path current setting//devfs1/blade/corp

Counts of items at File Servers and root paths referenced in the database 4639//devfs1/blade/corp

This output tells you that the current file server and root path is //devfs1/blade/corp. It also tells you that the script has counted 4,639 references to a file server and path that matches the current setting.

Output for Multiple File Server ReferencesIf you have references to multiple file servers in the database, the output looks something like this:


Counts of items at File Servers and root paths referenced in the database 4639//devfs2/blade/corp 284//devfs1_x1/blade/first/test

This output tells you that the current file server and root path is //devfs1/blade/corp. The script has counted 4,639 references to that file server and path. It has also counted 284 references to another file server, //devfs1_x1/blade/first/test.

4 During a maintenance window or some other period of user inactivity, shut down the BladeLogic system and move all files from the current or any former file servers to a new location.

5 Back up your database.6 Change all file server references so they point to the new file server rather than the

current file server by executing the following SQL*Plus command:sqlplus <user>/<password> @file_server_change_oracle.sql <NewFS> </NewRoot>



In the command shown above, provide the following values:• <NewFS>—New file server name. Do not include a double slash.• </NewRoot>—Path to new file server storage location. Include a leading slash.

OutputRunning this command produces output similar to the following:

Old system_property parametersFileServer//devfs1FileServerStorageLocationblade/corp3 rows updated.29 rows updated.4 rows updated.4603 rows updated. . . .Commit complete.New system_property parametersFileServerNewFSFileServerStorageLocation/New/Root

The actual number of rows updated by each update statement will vary in your database.7 If your database includes references to only one file server (as determined in step 3), the

procedure is complete. If the database references other file servers that you want to make consistent with the new file server, you must change the values for the current file server so they match the settings for an older file server. To accomplish this, use SQL*Plus to execute the following command:

sqlplus <user>/<password> @file_server_change_oracle_system_property.sql

<HistoricalFS> </HistoricalRoot>

In the command shown above, <HistoricalFS> is the name of another file server (other than the current file server) and </HistoricalRoot> is the path to that other

Note: Be aware of the following:• Both the <NewFS> and </NewRoot> parameters are required, even if one

is the same as an existing value. If you forget to include one, SQL*Plus will repeatedly prompt you for the other value. In a situation like this, use Ctrl-C to exit the script and run it again.

• If a SQL error occurs, the script rolls all values back.• If you have spaces in the <NewFS> and </NewRoot> parameters, you must

enclose the parameters in quotation marks.



file server’s storage location. You can obtain these values from the output generated by the script you ran in step 3.

OutputRunning this command produces output similar to the following:

Old system_property parameters

FileServer

devfs2

FileServerStorageLocation

/blade/NewPath

1 row updated.

1 row updated.

Commit complete.

New system_property parameters

FileServer

devfs1_x1

FileServerStorageLocation

/blade/first/test

8 Repeat step 6, which changes all references pointing to the current file server so they now point to the new file server.

9 If your database includes references to additional file servers, repeat steps 7 and 8 for each file server you want to change. Step 7 changes the current settings so they are equivalent to those of an historical file server. Step 8 converts all references pointing to the current setting so they now point to the new setting.

10 To be certain that all file servers reference the new file server, repeat step 3. The output should identify only one file server, and its values should be those of the new file server and storage location.

Changing the File Server Using SQL ServerUse this procedure to change a file server by updating file server references in a SQL Server database.

Procedure 1 In the file structure extracted from <external-files.zip>, copy the following scripts from /bl_<current release>/db_scripts/sqlserver/utility/file_server_change to a directory from which you can access osql:

file_server_check_sqlserver.sql file_server_change_sqlserver.batfile_server_change_sqlserver_system_property.batfile_server_change_sqlserver_sp_create.sqlfile_server_change_sqlserver_sp_drop.sql



file_server_change_sqlserver_system_property_sp_create.sqlfile_server_change_sqlserver_system_property_sp_drop.sql

2 Cd to the directory where you copied the scripts.3 Determine how many file servers your database references by using SQL Query

Analyzer or a similar tool to execute the contents of the script file_server_check_sqlserver.sql.If you do not have access to SQL Query Analyzer, you can run this script via osql as follows:

osql –S<Server> -U<User> -d<Database> -ifile_server_check_sqlserver.sql -ofile_server_check_sqlserver.out

In the command shown above, provide the following values:• <Server>—Database server• <User>—User name• <Database>—Database nameFor example, you might run a command like the following:

osql –S<dbserver> -U<dbadmin> -d<bladelogic> -ifile_server_check_sqlserver.sql -ofile_server_check_sqlserver.out

If you run the script using osql, the output includes many headings, underscores, and blank lines. You must scroll through all of these to find the important information, near the bottom.

Output for One File ServerIf your database references only one file server, the output looks something like this:


Nbr items at File Servers and root path setting found4639 //devfs1/blade/corp

This output tells you that the current file server and root path is //devfs1/blade/corp. It also tells you that the script has counted 4,639 references to a file server and path that matches the current setting.

Output for Multiple File Server ReferencesIf you have references to multiple file servers in the database, the output looks something like this:


Nbr items at File Servers and root path setting found4639 //devfs1/blade/corp284 //devfs1_x1/blade/first/test



This output tells you that the current file server and root path is //devfs1/blade/corp. The script has counted 4,639 references to that file server and path. It has also counted 284 references to another file server, //devfs1_x1/blade/first/test.

4 During a maintenance window or some other period of user inactivity, shut down the BladeLogic system and move all files from the current or any former file servers to a new location.

5 Back up your database.6 Change all file server references so they point to the new file server rather than the

current file server by running the following command:file_server_change_sqlserver <S> <U> <d> <NewFS> </NewRoot>

In the command shown above, provide the following values:• <S>—Database server• <U>—User name• <d>—Database name• <NewFS>—New file server name. Do not include a double slash.• </NewRoot>—Path to new file server storage location. Include a leading slash.

7 If your database includes references to only one file server (as determined in step 3), the procedure is complete. If the database references other file servers that you want to make consistent with the new file server, you must change the values for the current file server so they match the settings for an older file server by running the following command:

file_server_change_sqlserver_system_property <S> <U> <d> <HistoricalFS> </HistoricalRoot>

In the command shown above, provide the following values:• <S>—Database server• <U>—User name• <d>—Database name• <HistoricalFS>—Name of another file server other than the current file server.

Do not include a double slash. You can obtain this name from the output generated by the script you ran in step 3.

Note: Be aware of the following:• The SQL Server scripts asks you for the password to the database three

times as it makes osql calls.• If you have spaces in the <NewFS> and </NewRoot> parameters, you must

enclose the parameters in quotation marks.



• </HistoricalRoot>—Path to the other file server’s storage location. Include a leading slash. You can obtain this path from the output generated by the script you ran in step 3.

8 Repeat step 6, which changes all references pointing to the current file server so they now point to the new file server.

9 If your database includes references to additional file servers, repeat steps 7 and 8 for each file server you want to change. Step 7 changes the current settings so they are equivalent to those of an historical file server. Step 8 converts all references pointing to the current setting so they now point to the new setting.

10 To be certain that all file servers reference the new file server, repeat step 3. The output should identify only one file server, and its values should be those of the new file server and storage location.

Optimizing an Oracle Database for BladeLogic ReportsBladeLogic provides the following recommendations to optimize the performance of an Oracle database serving BladeLogic Reports:

Recommendations for Gathering StatisticsRecommendations for Configuring the DatabaseRecommendations for the Physical Implementation

Recommendations for Gathering Statistics BladeLogic recommends you gather statistics for BladeLogic Reports and the core BladeLogic database after each data warehouse load.

Use the following command to gather statistics:

exec dbms_stats.gather_schema_stats( ownname => USER, cascade=>TRUE, options => 'GATHER', estimate_percent => dbms_stats.auto_sample_size);



Recommendations for Configuring the Database The following recommendations are for a 10 GB database. Scale the configuration recommendations up or down based on the relative size of your database.

Recommendations for the Physical Implementation To avoid disk contention and increase input/output throughput when accessing data, store the physical data and index datafiles in different tablespaces (that is, across multiple disks).

Configuration Parameter Recommended Value

db_cache_size 1 GB

log_buffer 512 KB

pga_aggregate_target 360 MB

undo tablespace size 2 GB


Upgrading BladeLogic

This chapter provides a detailed procedural description explaining how to upgrade a complete BladeLogic system, including step-by-step instructions for upgrading all BladeLogic databases.

Using <external-files.zip>A zip file named <current_release>-external-files.zip provides the scripts you will need to upgrade data to the current release. BladeLogic documentation refers to this zip file as <external-files.zip>.

If you do not already have access to <external-files.zip>, contact BladeLogic support. You can find <external-files.zip> by accessing the Support section of the BladeLogic web site. Go to Downloads, scroll down, and then click DB Scripts and Documentation.

Extracting the contents of <external-files.zip> creates a large directory structure, with the parent directory named bl_<current_release>. The graphic shows the portion of the directory structure that applies to a data upgrade.

bl_<current_release>

db_scripts

oracle

upgrade

sqlserver

upgrade

Upgrading BladeLogic 42


Master Checklist for the Upgrade ProcessThe following steps provide a high-level description of the upgrade process:

1 Before starting the upgrade process, refer to the “Upgrade Notes” section of the Release Notes for details for your specific upgrade path.

2 If you are upgrading from a version earlier than 7.2 and if you plan to use the legacy (pre-7.2) patch management reports, it is critical that you run one last Populate Reports data collection job to ensure that all the pre-7.2 patch analysis data is in the warehouse before upgrading to 7.4.3. All pre-7.2 patch analysis data will be removed from the core BladeLogic database during the data upgrade, so if you do not populate this data into the warehouse before upgrading to 7.4.3, you will not have the option of deciding to report on it later.

3 Upgrading Application Servers and Reports Servers (page 43)—Upgrades the application server and reports servers so that the BladeLogic Data Migration Manager can be used to upgrade the databases.

4 Determining Sizing Requirements for Oracle Databases (page 44)—Determines your database sizing requirements if you are using an Oracle database.

5 Upgrading the Core BladeLogic Data (page 49)—Validates your BladeLogic database server environment and then launches BladeLogic Data Migration Manager to upgrade the BladeLogic database to the current release.

6 Upgrading the BladeLogic Reports Data (page 52)—Validates your reports server environment and then launches BladeLogic Data Migration Manager to upgrade the BladeLogic Reports data warehouse to the current release.

7 Upgrading Consoles and Agents (page 56)—Upgrades software for the Configuration Manager and Provisioning Manager consoles and RSCD agents.

8 Upgrading the Provisioning System (page 57)—Upgrades the BladeLogic provisioning system.

Warning: These procedures must be performed in order. Many steps are prerequisites for other steps that occur later in the process.



Upgrading Application Servers and Reports ServersUse this procedure to upgrade all BladeLogic Application Servers and reports servers. Note that when you upgrade the Application Server and the BladeLogic Reports server, you are not only upgrading software, you are also generating many of the files needed to upgrade data.

Procedure 1 Shut down the BladeLogic environment by doing the following:a Stop the Application Server (refer to the BladeLogic Administration Guide for

instructions).b Stop the PXE Server (refer to the BladeLogic Users Guide for instructions).c Stop the Reports Server (refer to the BladeLogic Reports Users Guide for

instructions).2 Back up the installation directories for all Application Servers and PXE Servers, and

BladeLogic Reports. The default installation locations are as follows:

3 Upgrade all Application Servers. For a step-by-step description of this procedure, see Upgrading Client-tier and Middle-tier Components (page 58).If you have a provisioning system configured and working prior to upgrade, your Provisioning Server will be upgraded automatically when the Application Server is upgraded.

4 If you are upgrading from a version earlier than 7.4.1, you will need to set your certificate password before you can run your upgraded Application Server. The

Note: Be aware of the following compatibility requirements:• If you upgrade the Application Servers, all Configuration Manager consoles must also

be upgraded. The Application Servers and Configuration Manager consoles must be at the same revision.

• If your file server resides on a separate machine than your Application Server, you must upgrade the agent on the machine on which your file server resides. After you upgrade your data, you must upgrade the agent on your file server prior to running the product. This is because the file server and the database must be at the same revision.

ApplicationDefault Location

Windows UNIX

Application Server C:\Program Files\BladeLogic\OM /usr/nsh

PXE Server C:\Program Files\BladeLogic\PXE /usr/nsh

BladeLogic Reports C:\Program Files\BladeLogic\Reports /usr/local/bl-reports



CertPasswd parameter is set using the Application Server Administration Console (blasadmin). Prior to 7.4.1 it was optional. Starting with 7.4.1 it is required, and if not set, the Application Server will not start. To set the parameter, run the following blasadmin command:set appserver Certpasswd <password>

where password is the password supplied to generate the certificate when initially installing the Application Server.For more information on running blasadmin commands refer to the BladeLogic Administration Guide.

5 Upgrade the Reports Server. For a step-by-step description of this procedure, see Upgrading BladeLogic Reports (page 68).

6 Check that the file server agent is running.

You have completed this procedure. Proceed to the following section, Determining Sizing Requirements for Oracle Databases, if you are using an Oracle database. If you are using SQL Server, proceed to Upgrading the Core BladeLogic Data (page 49).

Determining Sizing Requirements for Oracle DatabasesPrior to running BladeLogic Data Migration Manager, it is important to meet minimum disk space requirements for the UNDO and TEMP Oracle system areas. The following section provides guidelines for determining those requirements for running BladeLogic Data Migration Manager:

Determining TEMP Disk Space RequirementsDetermining UNDO Disk Space Requirements

A script is provided in <external-files.zip> that runs the queries described in these sections. If you extract the entire contents of <external-files.zip>, you will find the script in the /db_scripts/oracle/utility/migration_sizing_7x_temp_undo directory. You can either run the individual queries described in the following sections or extract and run the script provided in <external-files.zip>. To run the script: 1 Start SQL*Plus as the bladelogic user. For example, you might enter:

sqlplus bladelogic

2 Run the sizing_7x_temp_undo.sql script, as shown below:SQL> @sizing_7x_temp_undo.sqlSQL> exit

If your environment is shared with other applications, once you have determined the TEMP and UNDO disk space requirements for updating your BladeLogic data, you need to add it to the cumulative minimum requirements for TEMP and UNDO disk space for your other applications. You need to make sure that the total TEMP disk space requirements and total



UNDO disk space requirements for BladeLogic Data Migration Manager and all other applications are available before executing the data upgrade. For example,

Determining TEMP Disk Space Requirements

The following table provides specific recommendations for determining TEMP disk space requirements. To determine the necessary TEMP disk space for a 7.x data upgrade, run the query for the version you are upgrading from and the queries for each subsequent version from your starting point to the current release and put the results in the third column of the table (you can either print the pages prior to running the queries or annotate the PDF). Take the largest value in the third column as the minimum TEMP space requirements for using the BladeLogic Data Migration Manager to automatically upgrade your data through each version to the current version.

Application TEMP Disk Space Requirement

UNDO Disk Space Requirement

BladeLogic 20 GB 18 GB

App1 15 GB 16 GB

App2 10 GB 12 GB

Total Requirement: 45 GB 46 GB

Note: these guidelines assume that you do not use archive logging while the BladeLogic Data Migration Manager is executing. If for some reason you cannot turn off archive logging in your environment, you need to allocate additional archive log space for the duration of the data upgrade.

Upgrading from version: Query to determine TEMP disk space requirements Min. Req.

7.0.2 Result pre-determined - no query needed 2 GB

7.1.1 SELECTCASE WHEN ROUND(3 *bytes / 1024 / 1024 / 1024, 4) < 2 THEN 4 ELSE ROUND(3 *bytes / 1024 / 1024 / 1024, 4)END "GB"FROM user_segmentsWHERE segment_name = 'PRIMITIVE_BL_VALUE';

(fill in result of query)



For example, if you are currently at 7.1.1, run the queries for 7.1.1, 7.2.0, and 7.3.0 and fill in the third column of the table with the results as follows.

For this example, your minimum TEMP space requirements are 30 GB (the largest value in the third column) and you need to have at least 30 GB of TEMP space prior to running BladeLogic Data Migration Manager to upgrade your data from 7.1.1 to 7.4.1.

Determining UNDO Disk Space Requirements

The following table provides specific recommendations for determining UNDO disk space requirements. To determine the necessary UNDO disk space for a 7.x data upgrade, run the query for the version you are upgrading from and the queries for each subsequent version from your starting point to the current release and put the results in the third column of the table (you can either print the pages prior to running the queries or annotate the PDF). Take

7.2.0 SELECTCASE WHEN ROUND(10 *bytes / 1024 / 1024 / 1024, 4) < 2 THEN 4 ELSE ROUND(10 *bytes / 1024 / 1024 / 1024, 4)END "GB"FROM user_segmentsWHERE segment_name = 'ENUMERATED_BL_VALUE';


7.3.0 SELECTCASE WHEN ROUND(10 *bytes / 1024 / 1024 / 1024, 4) < 2 THEN 4 ELSE ROUND(10 *bytes / 1024 / 1024 / 1024, 4) END "GB"FROM user_segmentsWHERE segment_name = 'ENUMERATED_BL_VALUE';


Upgrading from version: Query to determine TEMP disk space requirements Min.

Req.


7.1.1 (7.1.1 query) 18 GB

7.2.0 (7.2.0 query) 22 GB

7.3.0 (7.3.0 query) 30 GB

Upgrading from version: Query to determine TEMP disk space requirements Min. Req.



the largest value in the third column as the minimum UNDO space requirements for using the BladeLogic Data Migration Manager to automatically upgrade your data through each version to the current version.

Upgrading from version: Query to determine UNDO disk space requirements Min.

Req.


7.1.1 SELECT round(1.5*(bytes + .5*bytes) / 1024 / 1024 / 1024,4)FROM user_segmentsWHERE segment_name IN('JOB_RUN_EVENT', );


7.2.0 SELECT 2 *MAX(bytes) / 1024 / 1024 / 1024 "GB"

FROM user_segments

WHERE upper(segment_name) IN('BL_PATCH_ANALYSIS_RES_DATA', 'BL_PATCH', 'PROP_SET_CLASS_PROP_DEF_VAL', 'SYSTEM_PACKAGE', 'PATCH_CONFIG_FILE', 'BL_PATCH_SUBSCRIPTION', 'BL_ACE', 'BL_ACL', 'BLOPTION', 'AS_TIME_ZONE', 'AS_LOCALE', 'TIMEZONE', 'TEMPLATE_PART', 'SYSTEM_PROPERTY', 'SYSTEM_PACKAGE_TYPE_PATH', 'SYSTEM_PACKAGE_TYPE_PART', 'SYSTEM_PACKAGE_TYPE', 'SCHEDULE', 'LOCALE', 'KEYBOARD', 'HRB_PROPERTY_SET_CLASS', 'DEVICE', 'DATA_TYPE', 'CONFIG_FILE_GRAMMAR', 'SYSTEM_PACKAGE_SCRIPT', 'PROPERTY_SET_CLASS_PROPERTY', 'PROPERTY_SET_CLASS', 'PROPERTY', 'PATCH_CONFIG_FILE_TYPE', 'OS');




7.3.0 SELECT 2 *MAX(bytes) / 1024 / 1024 / 1024 "GB"

FROM user_segments

WHERE UPPER(segment_name) IN('APPLICATION_SERVER', 'ASSET_ATTRIBUTE_CONDITION', 'ASSET_ATTRIBUTE_COND_RESULT', 'BLGROUP_TYPE', 'BLOPTION', 'BL_ACE', 'BL_ACL', 'BL_ACL_AGG_AUTH', 'BL_AUTH', 'BL_AUTH_ENUM', 'BL_AUTH_OBJECT_TYPE', 'BL_VALUE', 'COMPLIANCE_REMEDIATION_OPTIONS', 'COMPLIANCE_REMEDIATION_RUN', 'COMPLIANCE_RULE', 'COMPLIANCE_RULE_RESULT', 'COMPONENT', 'COMPONENT_EXCEPTION_MAP', 'COMPONENT_EXCEPTION_RULE_SEL', 'COMP_REMEDIATION_TEMPLATE', 'CR_RULE_OVERFLOW', 'CR_RULE_RESULT_OVERFLOW', 'CR_RULE_RESULT_SELECTOR', 'DATA_TYPE', 'DEPOT_OBJECT', 'ENUMERATED_BL_VALUE', 'ENUMERATED_DATA_TYPE', 'ENUM_DATA_TYPE_LEGAL_VALUE', 'EXTENDED_OBJECT_CLASS', 'JOB', 'JOB_OPTION_VALUE', 'JOB_RESULT_DEVICE', 'JOB_RUN', 'JOB_RUN_EVENT', 'JOB_RUN_EVENT_OVERFLOW', 'LIST_BL_VALUE_ELEMENT', 'OBJECT_TYPE', 'OPERATION_TYPE', 'OS', 'OS_COMPONENT_DEPENDENCY', 'PARTITIONS', 'PARTITION_TYPE', 'PM_DEVICE', 'PRIMITIVE_BL_VALUE', 'PROPERTY', 'PROPERTY_CONDITION', 'PROPERTY_CONDITION_RESULT', 'PROPERTY_SET_CLASS_PROPERTY', 'PROPERTY_SET_INSTANCE', 'PROP_SET_CLASS_PROP_DEF_VAL', 'PROP_SET_INSTANCE_PROP_VAL', 'PXE_BOOT_IMAGE', 'RANGE_BL_VALUE', 'REPAIR_ACTION_PROPERTY_VALUE', 'ROLE_AGG_AUTH', 'ROLE_AUTH', 'SCHEDULE', 'SCHEDULE_PARAMS', 'SERVER_CONFIG_DEFINITION', 'SOFTWARE_DEFAULT_OS', 'SOFTWARE_PROPERTY', 'SYSTEM_PACKAGE', 'SYSTEM_PACKAGE_TYPE', 'SYSTEM_PACKAGE_TYPE_OS_COMP', 'SYSTEM_PACKAGE_TYPE_PART', 'SYSTEM_PROPERTY', 'SYS_PACK_PRE_INSTL_SCRIPTS', 'TEMPLATE', 'UI_CUSTOM_ICON', 'UI_EXTENDED_OBJECT_ICON');



Req.



For example, if you are currently at 7.2.0, run the queries for 7.2.0 and 7.3.0 and fill in the third column of the table with the results as follows.

For this example, your minimum UNDO space requirements are 28 GB (the largest value in the third column) and you need to have at least 28 GB of UNDO space prior to running BladeLogic Data Migration Manager to upgrade your data from 7.2.0 to 7.4.3.

Proceed to the following section, Upgrading the Core BladeLogic Data.

Upgrading the Core BladeLogic DataUse this procedure to prepare for the database upgrade and to launch BladeLogic Data Migration Manager for the core BladeLogic database. Some of these steps may require database expertise and should be performed by a DBA.

Procedure 1 Back up the BladeLogic database.

2 Backup the BladeLogic file server storage location. For example, copy the entire contents of the storage location to a directory other than the current storage location.

3 Obtain the most recent version of <external-files.zip> and extract its contents.4 Using the files extracted from <external-files.zip>, copy all files from the following

directory into a directory on your application server:/bl_<current_release>/db_scripts/<db_type>/upgrade/


Req.


7.1.1 (7.1.1 query) N/A

7.2.0 (7.2.0 query) 22 GB

7.3.0 (7.3.0 query) 28 GB

Note: This procedure is relevant for the following upgrade paths: • For Oracle environments, release 7.0.2 and above to the current release• For SQL Server environments, the previous release to the current release

For all other upgrade paths, refer to the “Upgrade Notes” section of the Release Notes for more information.

Warning: You must back up before beginning the actual data upgrade process. The data upgrade occurs in place. If, for any reason, it should become impossible to complete the upgrade, the only way to restore the database to its pre-upgrade state will be from the backups.



5 If you use BladeLogic Reports, copy the following files from the config directory in the existing BladeLogic Reports installation directory to db_scripts/<db_type>/upgrade/<upgrade_path>/OM/Migration_actions:

PatchPropertiesDataDescription.xmlPropertiesDataDescription.dtdPropertiesDataDescription.xmlPropertiesDataDescription_BLContent.xml (if present)

6 If your database is in an Oracle environment, your DBA must execute the following steps:a Make sure adequate TEMP and UNDO space is available (see Determining Sizing

Requirements for Oracle Databases (page 44) for more information). b Copy the following file extracted from <external-files.zip> to a location where you

have access to SQL*Plus:/bl_<current_release>/db_scripts/<Oracle>/upgrade/migration_setup_OM.sql

c Log into SQL*Plus as sysdba.

d Set the Bladelogic user’s roles and permissions to allow the upgrade to be carried out by entering the following: start migration_setup_OM.sql

7 Cd to <OM_install_dir>/OM/br on the Application Server.8 Launch BladeLogic Data Migration Manager to validate your environment and perform

the data upgrade by entering one of the following:• For Windows, enter

blmigration_mgr <path_to_upgrade_directory>

• For UNIX, enter./blmigration_mgr <path_to_upgrade_directory>

where <path_to_upgrade_directory> is the path to the upgrade directory you copied to the Application Server in step 4. You must use the operating system-style path

Warning: You must log in as sysdba to run the migration_setup_OM.sql script in step d.

Note: If your installation has chosen a schema owner for the core BladeLogic database other than the default schema owner BLADELOGIC, you will have to modify the migration_setup_OM.sql script run in step d to use the schema owner username for your installation. After the data upgrade has completed, the schema owner can have its additional upgrade roles and permissions returned to their normal state.



when specifying the path. For example, if you copied the contents of upgrade to \tmp\upgrade on a Windows system, you would execute the following command:

blmigration_mgr C:\tmp\upgrade.

BladeLogic Data Migration Manager creates the stored procedures needed for the data upgrade and then launches the BladeLogic Data Migration Manager console.

9 On Oracle, click Validate Environment if you choose to execute the validate step separately from the validation that is done as part of the next step. See Validating Oracle Environments (page 85) for more information.

10 Click Run Migration. For details on using BladeLogic Data Migration Manager, see Using BladeLogic Data Migration Manager (page 84).

Warning: Before executing blmigration_mgr, close all connections to the database. Open connections may cause certain database commands to fail, which will cause the upgrade to stop.



When you have successfully upgraded the BladeLogic database using BladeLogic Data Migration Manager, proceed to the following section, Upgrading the BladeLogic Reports Data.

Upgrading the BladeLogic Reports DataUse this procedure to prepare for the database upgrade and to launch BladeLogic Data Migration Manager for the BladeLogic Reports data warehouse. When you perform these steps, you should have access to a DBA who can monitor database performance.

Procedure 1 Back up the data warehouse for BladeLogic Reports.

2 Using the files extracted from <external-files.zip>, copy all files from the following directory into a directory on your reports server (this must be a different location than where you copied the files for BladeLogic in step 4 in Upgrading the Core BladeLogic Data): /bl_<current_release>/db_scripts/<db_type>/upgrade

3 If your database is in an Oracle environment, your DBA must execute the following steps:a Copy the following file extracted from <external-files.zip> to a location where you

have access to SQL*Plus:/bl_<current_release>/db_scripts/<oracle>/upgrade/migration_setup_reports.sql

b Log into SQL*Plus as sysdba.

Note: This procedure is relevant for the following upgrade paths: • For Oracle environments, release 7.1.1 and above to the current release• For SQL Server environments, the previous release to the current release

For all other upgrade paths, refer to the “Upgrade Notes” section of the Release Notes for more information.

Warning: You must back up before beginning the actual data upgrade process. The data upgrade occurs in place. If, for any reason, it should become impossible to complete the upgrade, the only way to restore the database to its pre-upgrade state will be from the backups.

Warning: You must log in as sysdba to run the script in step c.



c Set the Bladelogic user’s roles and permissions to allow the upgrade to be carried out by entering the following: start migration_setup_reports.sql

4 Cd to <reports_install_dir>/bin on the reports server.5 Launch BladeLogic Data Migration Manager to validate your environment and perform

the data upgrade by entering one of the following:• For Windows, enter

blrptmigration_mgr <path_to_upgrade_directory>

• For UNIX, enter./blrptmigration_mgr <path_to_upgrade_directory>

where <path_to_upgrade_directory> is the path to the upgrade directory you copied to the reports server in step 2. You must use the operating system-style path when specifying the path. For example, if you copied the contents of upgrade to \tmp\reports\upgrade on a Windows system, you would execute the following command:

blrptmigration_mgr C:\tmp\reports\upgrade

Note: If your installation has chosen a schema owner for the data warehouse for BladeLogic Reports other than the schema owner BLREPORTS, you will have to modify the migration_setup_reports.sql script run in step c to use the schema owner username for your installation. After the data upgrade has completed, the schema owner can have its additional upgrade roles and permissions returned to their normal state.



BladeLogic Data Migration Manager creates the stored procedures needed for the data upgrade and then launches the BladeLogic Data Migration Manager console.

6 Click Run Migration.For details on using BladeLogic Data Migration Manager, see Using BladeLogic Data Migration Manager (page 84).

7 When you have successfully upgraded the BladeLogic Reports data warehouse using BladeLogic Data Migration Manager, back up the schemas for the BladeLogic Reports data warehouse to ensure that you have preserved a clean baseline version.

8 Start the Application Server (the Application Server must be running in order to execute the script in step 12).

9 Start the reports server. 10 Cd to <reports_install_dir>/bin on the reports server.11 Create the dynamically generated portion of the reporting data warehouse schema by

doing one of the following:• For Windows, enter

load_warehouse_schema.bat



• For UNIX, entersh load_warehouse_schema.sh

12 Migrate report definition information by doing one of the following:• For Windows, enter

migr_saved_rept_defns.bat <username> <password>

• For UNIX, entersh migr_saved_rept_defns.sh <username> <password>

where <username> and <password> are the user name and password of any valid user of BladeLogic Reports.

13 Cd to <reports_install_dir>/out_of_box_reports on the reports server.14 Install the built-in reports by entering the following:

• For Windows, enter..\bin\blrptadmin -f out_of_box_import.txt

• For UNIX, enter../bin/blrptadmin -f out_of_box_import.txt

To import the legacy patch analysis reports, enter the following:• For Windows, enter

..\bin\blrptadmin -f legacy_patch_reports_import.txt

• For UNIX, enter../bin/blrptadmin -f legacy_patch_reports_import.txt

This will create a folder named Legacy Patch Analysis Reports under the All Reports folder containing the pre-7.2 patch analysis reports.

15 Upgrade the BladeLogic Reports data collection scripts by doing the following:a Log in to the Configuration Manager console.

Tip: To avoid having the username and password appear in any history lists on UNIX, you can use the -i (interactive mode) option. Simply replace the username and password on the command line with the -i option and the program will prompt you for the username and password. For example,

sh migr_saved_rept_defns.sh -i

Note: The built-in patch analysis reports report on data generated in release 7.2 and beyond. If you are upgrading from a version earlier than 7.2 and if you want to report on patch analysis data generated prior to 7.2, you can import the older patch analysis reports, called the Legacy Patch Analysis Reports.



b Replace your existing version of the following data collection scripts:os_config.nshcollect_agent_logs.nshpopulate_reports.nsh.

You must replace these scripts in Configuration Manager with the new scripts installed with this release and then recreate the associated Network Shell Script Jobs. If you do not care about retaining the history of the Network Shell Script Jobs, the easiest approach is to delete the old Network Shell Script Jobs and create new jobs associated with the new versions of these three scripts. If you want to retain job history, you must open the existing scripts and replace their contents with the contents of the new scripts. Starting in release 6.3, the collect_agent_logs.nsh script must use the runscript option. If you are upgrading from a release earlier than 6.3 and using an existing script and replacing it with the contents of the 7.4.3 version of the collect_agent_logs.nsh script, you must make sure the Script Type option is set to Execute the script separately against each host (using “runscript”).

See Setting Up Data Collection Jobs (page 152) for a complete description of how to include data collection scripts in Configuration Manager jobs.

c Run the new Network Shell Script Job for os_config.nsh to generate new data formatted for this release.

d Run the new Network Shell Script Job for populate_reports.nsh to ensure that all the data in the data warehouse is upgraded to the new release.

Proceed to the following section for the procedure for upgrading the consoles and agents, Upgrading Consoles and Agents.

Upgrading Consoles and AgentsUse this procedure to upgrade Configuration Manager and Provisioning Manager consoles and RSCD agents.

Procedure 1 Upgrade all servers running Configuration Manager consoles. For a step-by-step description of this procedure, see Upgrading Client-tier and Middle-tier Components (page 58). At this time you can also upgrade Provisioning Manager consoles, or you can perform that procedure while upgrading your provisioning system.

Note: If you have modified any of the existing data collection scripts, you must implement those same modifications in the new versions of these scripts.



2 Upgrade agents on all servers.

Refer to Upgrading RSCD Agents (page 61) for detailed instructions on how to upgrade agents interactively or by means of a silent upgrade procedure.

You have completed this procedure. Proceed to the following section, Upgrading the Provisioning System.

Upgrading the Provisioning SystemUse this procedure to upgrade the provisioning system used by Provisioning Manager. For a step-by-step description of all the software upgrades procedures mentioned in this procedure, refer to Upgrading the PXE Server (page 81).

Procedure 1 If you have not already done so, upgrade all Provisioning Manager consoles. For a step-by-step description of this procedure, refer to Upgrading Client-tier and Middle-tier Components (page 58).

2 If you have not already done so, upgrade the agent on the data store server. For a step-by-step description of this procedure, refer to Upgrading RSCD Agents (page 61).

3 If you want to use any system packages created in BladeLogic releases earlier than 7.4, make a backup copy of <tftproot>/x86pc/pxelinux/blade.img in an alternate location.

4 Upgrade the PXE and TFTP Servers. For a step-by-step description of this procedure, refer to Upgrading the PXE Server (page 81). If you do not plan to use any system packages created in BladeLogic releases earlier than 7.4, skip to step 6.

5 Copy the backup of blade.img you saved to an alternate location in step 3 back to <tftproot>/x86pc/pxelinux.

6 If you want to install the current release of the agents when provisioning bare metal machines, upgrade your agent installers in the data store.

7 Start the PXE and TFTP Servers.

Congratulations. You have completed the software and data upgrade. The remainder of this chapter contains detailed procedures referred to from the Master Checklist for the Upgrade Process (page 42) master procedure.

Note: Users should be mapped to root for the duration of the upgrade for all UNIX Application Servers.



Upgrading Client-tier and Middle-tier ComponentsUse the following procedures to upgrade client-tier and middle-tier components, such as Configuration Manager, Provisioning Manager, and Network Shell:• Upgrading Client-tier and Middle-tier Components on Windows• Upgrading Client-tier and Middle-tier Components on UNIX

Upgrading Client-tier and Middle-tier Components on WindowsUse this procedure to upgrade all client-tier and middle-tier BladeLogic components that were installed as part of the previous installation.

If the host where you are installing the Application Server has ActiveState Perl version 5.6.1 installed, this installation automatically installs the Network Shell Perl module. If you have some other version of Perl installed, the installation still installs the Perl module but it may be incompatible with your Perl executable.

Procedure 1 If you are upgrading the Application Server, stop the Application Server.2 Navigate to the directory containing installation files and invoke the installation program

for BladeLogic.

Note: Be aware of the following:• To perform this installation, you must have local Administrator privileges.• If you are using Windows Terminal Services or Citrix Presentation Server to

install or you are installing on a Windows Server 2003 machine, you must install in Installation mode rather than Execution mode, or you must install using the Windows Add or Remove Programs utility. For more information, see Using Installation Mode Rather Than Execution Mode (page 133).



The installer extracts files needed for installation and displays the Setup Type window.

3 Select Upgrade and click Next.A progress bar shows the progress of the installation. The Upgrade Complete window announces that the upgrade is complete.

4 Click Finish to complete the upgrade to your installation.See Starting Network Shell, Configuration Manager, and Provisioning Manager (page 234) for instructions on starting Configuration Manager.



Upgrading Client-tier and Middle-tier Components on UNIXUse this procedure to upgrade all client-tier and middle-tier BladeLogic components that were installed as part of the previous installation.

If the host where you are installing the Application Server has the correct version of Perl installed (refer to Perl Support (page 22) for information on what is the correct version of Perl for your operating system), this installation automatically installs the BladeLogic Network Shell Perl module. If you have some other version of Perl installed, the installation still installs the Perl module but it may be incompatible with your Perl executable.

Procedure 1 Log in as root. 2 If you are upgrading the Application Server, stop the Application Server.3 Navigate to the directory containing upgrade files and invoke the upgrade script for

BladeLogic.The following message displays:A previous installation already exists.Do you wish to continue (y/n) ?

4 Enter y.A message displays letting you choose a language for the installation program.

5 Enter the number representing the language you want.The following message displays:Welcome to the BladeLogic Operations Manager Release 7.4.3 installation script ...

A previous installation has been detected. This installation willbe upgraded to BladeLogic Operations Manager 7.4.3.

Do you wish to continue (y/n) ?

6 Enter y.Licensing text displays and concludes with the following message:Do you agree to the terms of the license agreement (y for Yes) ?

7 Read the licensing text. If you agree with its terms, enter y.A list displays the BladeLogic components that will be upgraded and asks if you want to continue.

8 Enter y.Several messages display, and then the upgrade script is complete. For information on starting client utilities, see Starting Network Shell, Configuration Manager, and Provisioning Manager (page 234).



Upgrading RSCD AgentsUse the following procedures to upgrade RSCD agents interactively or with an unattended process:• Upgrading the RSCD Agent on Windows• Silently Upgrading Windows Agents• Upgrading the RSCD Agent on UNIX• Silently Upgrading UNIX Agents

Upgrading the RSCD Agent on WindowsUse this procedure to upgrade an earlier version of the RSCD agent.

Procedure 1 Navigate to the directory containing installation files and invoke the installation program for the RSCD agent. The installer extracts files needed for installation and then displays the Setup Type window.

Note: Starting in version 7.3, the 32-bit and 64-bit agents are packaged separately. If you previously installed a 32-bit Windows agent on a 64-bit platform, you cannot simply upgrade to a 64-bit Windows agent. You have to first uninstall the old 32-bit version of the agent before being able to successfully install the new 64-bit version.

Note: To avoid problems caused by user replication in replicated domain controller environments, you should follow a recommended procedure for installing or upgrading agents, as described in Installing Agents in a Replicated Domain Controller Environment (page 132).



2 Select Upgrade and click Next. The next window announces that the upgrade is complete.

3 Click Finish to complete the upgrade to your installation.For information on restricting access to RSCD agents and the secure configuration file, see the BladeLogic Administration Guide.

Silently Upgrading Windows AgentsUse these procedures to perform an unattended (that is, a “silent”) upgrade of RSCD agents running a previous version of BladeLogic software. An unattended upgrade for Windows consists of two procedures. First you create a response file for the installation process by upgrading a server and recording your responses to the installation program’s prompts (see Creating a Response File for Windows Agents). Then you deploy the upgrade program to all servers needing an upgrade to the current release (see Deploying the Silent Upgrade to Multiple RSCD Agents). Because the second procedure is based on a Configuration Manager job, an RSCD agent must already be installed on servers where the job is run.

Note: If the Microsoft XML (MSXML) 2.5 or later parser is not installed on this server, a warning displays. MSXML is installed by default on Windows 2003 and XP machines but not on Windows 2000. For BladeLogic’s patch analysis functionality to be operable, MSXML 2.5 or later must be installed. You can cancel the installation or click OK to continue. If you continue, patch analysis will not function correctly on this server until MSXML 2.5 or later is installed.



Creating a Response File for Windows Agents

Use this procedure to record your responses to prompts from the installation program. Your responses are stored in a response file.

Procedure 1 Copy rscd<version>.exe (the RSCD agent installation program) to <WINDIR>\Temp, where <WINDIR> is typically C:\winnt or C:\Windows.

2 From the command line, connect to <WINDIR>\Temp.3 From the command line, enter

rscd<version> –a –r –f1<WINDIR>\Temp\version-install_type.iss

where version-install_type.iss is the name of response file you are creating (for example, specify 7.4.1-install.iss as the name of the response file for initial installs of 7.4.1 or 7.4.1-upgrade for upgrades to 7.4.1 from earlier versions of the agent).The installation program for the RSCD agent opens. Use the program to perform an initial install or an upgrade of the RSCD agent, selecting the options that are appropriate for your site.

Deploying the Silent Upgrade to Multiple RSCD Agents

Use this procedure to deploy the RSCD agent installation program, the response file you created in the previous procedure, and other files used for controlling agents. The deployment copies these files to any target servers you specify and then silently executes the installation program.

Procedure 1 Using the Configuration Manager console, browse to the server where you upgraded an RSCD agent in the previous procedure. Browse to the <WINDIR>\Temp directory in that server’s File System, where <WINDIR> is typically C:\winnt or C:\Windows.

2 Select the following files, right-click, and select Deploy Files from the pop-up menu:rscd<version>.exe<version>-upgrade.iss

These files should exist in the same directory where you ran the installation program in the previous procedure. The File Deploy Job wizard opens.

Note: If the Microsoft XML (MSXML) 2.5 or later parser is not installed on a server where you are installing the RSCD agent, a warning displays during the installation process. MSXML is installed by default on Windows 2003 and XP machines but not on Windows 2000. For BladeLogic’s patch analysis functionality to be operable, MSXML must be installed. When creating a response file for Windows agents, note the type of Windows operating system. If necessary, include an appropriate response for the MSXML warning. When responding to the warning, you can continue with the installation, but patch analysis will not be functional on that server until MSXML 2.5 or later is installed.



3 For Name, assign a name to this File Deploy Job. For Save in, specify the job group where you want to store this job.

4 If you are deploying the upgrade to a version 6.2 agent or a more recent agent, skip this step. If you are deploying the upgrade to an agent older than version 6.2, under Source, add the following files to the list of files included in the deployment:

agentctl.exeactl.exe

These files are typically located in C:\Program Files\BladeLogic\RSC on the server where you upgraded an RSCD agent in the previous procedure.

5 For Destination, enter /c/tmp or a directory with no spaces in its path and click Next.6 Choose the servers being upgraded and click Next twice to display the Advanced

Options panel.7 For Post-command, enter the following:

”C:\Program Files\BladeLogic\RSC\agentctl” -b exec C:\tmp\rscd<version>.exe -a -s -f1C:\tmp\<version>-upgrade.iss

If necessary, replace C:\Program Files\BladeLogic\RSC with the installation directory for the RSCD agent and C:\tmp with the destination directory you used for the installer and response files. Note, the path to the destination directory cannot contain spaces.

8 Click Finish.The files are deployed to the target servers and the installation runs silently on each machine.

Upgrading the RSCD Agent on UNIXUse this procedure to upgrade an earlier version of the RSCD agent running on Solaris, Linux, AIX, or HP-UX.

Procedure 1 Log in as root. 2 Navigate to the directory containing upgrade files and invoke the installation package for

the RSCD agent.The following message displays:A previous installation already exists. Do you wish to continue (y/n) ?

3 Enter y.A message displays letting you choose a language for the installation program.

Note: If you are upgrading a server with components installed other than the RSCD agent, you must use an installation script that includes those other components. For example, if you are upgrading the RSCD agent on a machine where Network Shell is also installed, the installation package you are using must include Network Shell.



4 Enter the number representing the language you want.The following message displays:Welcome to the BladeLogic RSCD Agent 7.4.3 installation script ...Do you wish to continue (y/n) ?

5 Enter y.A message displays, warning you that you must review text about terms and conditions for using this software.

6 Press Enter.Licensing text displays and concludes with the following message:Do you agree to the terms of the license agreement (y for Yes) ?

7 Read the licensing text. If you agree with its terms, enter y.A message shows the RSCD Agent as the one component to be upgraded and asks if you want to continue.

8 Enter y.Several messages display, and the upgrade is complete. For additional information on restricting access to RSCD agents, see the BladeLogic Administration Guide.

Silently Upgrading UNIX AgentsUse these procedures to perform an unattended (that is, a “silent”) upgrade of RSCD agents running a previous version of BladeLogic software on Solaris, Linux, AIX, and HP-UX. An unattended upgrade consists of two procedures. First you create a file that defines variables that control how a silent installation on UNIX behaves (see Creating a File of UNIX Installation Defaults). Then you deploy the installation program to all servers needing an upgrade (see Deploying the Silent Installation). Because the second procedure is based on a Configuration Manager job, an RSCD agent must already be installed on servers where the job is run.

Creating a File of UNIX Installation Defaults

Use this procedure to create a file that defines variables that control how a silent installation on UNIX behaves. To alter any of the default steps in a silent installation, include an entry in the file that sets a variable for that step in the installation. Then include another line that exports the variable. For example, a file of installation defaults might appear as follows:

NSH_INSTALL_SKEL=yexport NSH_INSTALL_SKELCOMPONENT_CHECKED=1export COMPONENT_CHECKED



Procedure 1 Using any server, create a text file called nsh-install-defaults in the /tmp directory. The file must belong to root.

2 Create an entry in the file that sets a variable, such as INSTALL_DIR=/export/home/nsh. The following table describes how to set each possible variable:

Variable Explanation

INSTALL_DIR Setting this allows you to choose an installation directory other than the default installation directory of /usr/nsh.

COMPONENT_CHECKED [1-6]

By default, running a silent installation installs all possible components in the installation. You can override that default by setting the COMPONENT_CHECKED value. The components you install can be any combination of numbers, such as COMPONENT_CHECKED=12456. The numbers have the following meanings:

1 - RSCD Agent2 - Application Server3 - Provisioning Server4 - Network Shell5 - Configuration Manager Console6 - Provisioning Manager Console

When using the file with the Bulk RSCD Agent Installer, set the value to 1.

IS_SECURE_AGENT_LOGS Setting this variable to 1 enables secure agent logging. When secure agent logging is enabled for an agent, agent logs are periodically rolled and digitally signed as they are rolled.

IS_KEYSTROKE_LOGS Setting this variable to 1 enables keystroke (nexec) logging on an agent. When keystroke logging is enabled on an agent, remote commands run against the agent using nexec are captured and logged in an encrypted manner in keystroke logs. These logs are also periodically rolled and digitally signed as they are rolled.

RND_CHOICE BladeLogic uses random data to encrypt communication securely. If a server on which you are performing a silent installation does not include a hardware device for generating random numbers, the silent installation by default installs the the Pseudo Random Number Generator Daemon (prngd). You can use this variable to override that choice. Acceptable values are:

1 - prngd (default)2 - bl_gen_rand (creates a seed file for generating random numbers)



3 Create the next entry in the file to export the variable you just created. For example, if you created a variable in the previous step that said RND_CHOICE=1, create the next entry to say export RND_CHOICE.

4 Repeat the previous two steps for every step in the silent installation that you want to modify.

5 Save /tmp/nsh-install-defaults.

Deploying the Silent Installation

Use this procedure to silently deploy the installation program for an agent upgrade.

Procedure 1 Create a file identifying default behavior for the silent installation, as described in Creating a File of UNIX Installation Defaults (page 65).

2 Using the same server, copy rscd<version>.sh (the RSCD agent installation program) to /tmp.

3 Make rscd<version>.sh executable by entering the following command:chmod 755 rscd<version>.sh

NSH_ROOT_HOST Set this value to identify a client on which users are granted root privileges for this server. This option sets the root= flag in the exports configuration file. By default no clients are specified.

NSH_USER_FROM and NSH_USER_TO

Set these values to configure a default user mapping in the users.local file. By default no users are mapped. The values set with this variable create an entry in the users.local file that says:

NSH_USER_FROM rw,map=NSH_USER_TOFor example, by defining values for these variables, you could create an entry in users.local like the following:

betty rw,map=root

NSH_INSTALL_SKEL By default a silent installation does not include the .nsh /etc/skel files. Set this variable to yes to install those files.

DEFAULT_WEBBROWSER By default the silent installation tries to find a default web browser by searching for Netscape and Mozilla in a few specific locations. Use this variable to identify the location of a default web browser.

Note: To perform this procedure you must have root privileges or be mapped to root. You must also be capable of running the at command.

Variable Explanation



4 Using the Configuration Manager console, browse to the server to which you copied the RSCD agent installation program in the first step. Browse to the /tmp directory in that server’s File System.

5 Select rscd<version>.sh. If you created an nsh-install-defaults file specifying installation defaults, select that file too. Right-click and select Deploy from the pop-up menu.

6 For Destination Directory, enter /tmp and click Next.7 Choose the servers with agents being upgraded and click Next.8 For Post-command, enter the following:

sh /tmp/rscd<version>.sh -silent

9 Click Finish.The files are deployed to the target servers and the installation runs silently on each machine. Because the installation runs silently on each machine, the deploy job will return immediately even though the silent installation can take one to two minutes to finish.

Upgrading BladeLogic ReportsUse the following procedures to upgrade BladeLogic Reports. • Upgrading BladeLogic Reports on Windows• Upgrading BladeLogic Reports on UNIX

Upgrading BladeLogic Reports on WindowsUse this procedure to upgrade a reports server running an older version of BladeLogic Reports on a Windows machine.

Note: Be aware of the following:• To complete this procedure, you must provide database connection

information. To set up a reporting database, see Setting Up the Schemas for BladeLogic Reports (page 28).

• An RSCD agent must be installed on the machine where you are installing BladeLogic Reports.

• If you are using Windows Terminal Services or Citrix Presentation Server to install or you are installing on a Windows Server 2003 machine, you must install in Installation mode rather than Execution mode, or you must install using the Windows Add or Remove Programs utility. For more information, see Using Installation Mode Rather Than Execution Mode (page 133).

• Most of the fields in the installation program are already populated with values based on your previous installation.



Procedure 1 If upgrading from 7.0.1 or a newer version, proceed to step 2. If you are upgrading from a version older than 7.0.1, run the drop_reports_repository_<databasetype>.sql script on the repository database for BladeLogic Reports. You can find this script in the file structure extracted from <external-files.zip>, in db_scripts/<databasetype>/schema.

2 Navigate to the directory containing the 7.4.3 BladeLogic installation files and double-click BladelogicReports.exe. The installer extracts the files needed for installation and displays the following window.

3 Click Next. The Acknowledgements window opens, providing license information for all third party software products included in BladeLogic Reports.



4 Click Next. The License Agreement window opens.

5 After reading the license agreement, click Yes if you agree with its terms. The Reports Server Hostname window opens.

6 Enter the name of the reports server that will be used in URLs that access BladeLogic Reports. Then click Next.



The Configure Tomcat Ports window opens.

7 For HTTP, enter the port to which the Tomcat server should listen for HTTP traffic.8 Do one of the following:

• If BladeLogic Reports should not use secure communication based on SSL, leave the HTTPS field blank.

• If BladeLogic Reports should use secure communication based on SSL certificates, enter the following information:HTTPS—The port that the Tomcat server should use to service HTTPS requests (that is, HTTP over SSL).Location—The path to the keystore where a certificate should be stored.Password—The password needed to gain access to the keystore.Confirm—Confirmation of the password.

If you perform this step, the installation program creates a self-signed certificate, which is stored in the keystore location you identify.

9 Click Next. The Operations Manager Database window opens.



This window lets you define a connection to the core BladeLogic database, which contains tables needed for BladeLogic Reports.

10 From Database Type, select the type of database you are using for the core BladeLogic database. Depending on the type you select, other options and default values change on this window.

11 Enter the following information to define a connection with the core database:Host—The name of the server running the database.Port—The port the database listens on. By default a BladeLogic installation uses the following database ports.

Database/SID—The name of the SQL Server database or the SID of the Oracle database. Typically this database is named bladelogic.User—A login ID for the BladeLogic database.Password—A password for the login ID.

Database Type Port Number

Oracle 1521

SQL Server 1433



12 Click Next. The Warehouse Database window opens. It lets you define a connection to the reporting data warehouse.

13 Enter the following information to define a connection with the reporting data warehouse:Host—The name of the server running the reporting data warehouse.Port—The port the warehouse database listens on. By default a BladeLogic installation uses the following database ports.

Database/SID—The name of the SQL Server database or the SID of the Oracle database. Typically this database is named blreports.User—A login ID for the reporting data warehouse.Password—A password for the login ID.If your database type is SQL Server, proceed to step 16. If your Warehouse database type is Oracle, proceed to the next step.

Note: The Database Type is automatically set to the same type of database chosen in the previous window.


Oracle 1521

SQL Server 1433



14 Click Next. If your Warehouse database type is Oracle, the Warehouse Oracle Net Service window opens.

15 Enter the name of the Oracle Net Service for your Warehouse database.16 Click Next. The Application Server Location window opens. BladeLogic Reports

authenticates through the Application Server.

17 Define a connection to the Application Server by providing the following information:Host—Name of the host where the Application Server is installed.Port—The port on which the Application Server should listen for communication from BladeLogic Reports. By convention, the Application Server listens for SRP traffic on port 9829. For information on configuring the Application Server port for other purposes, see the BladeLogic Administration Guide.



18 Click Next. The SMTP options window opens. BladeLogic Reports requires an email server. (SMTP stands for simple mail transfer protocol.)

19 Provide the following information:Server—Name or IP address of the host managing email.Port—Port on which an SMTP server listens for traffic.Email From—Email address from which BladeLogic-generated email is sent.

20 Click Next. The Selected Components window opens.

21 Review the current settings to confirm that you have specified the correct installation configuration and then click Next. A progress bar indicates the progress of the



installation until the following window opens and informs you that the installation is finished but you must restart your computer.

22 Do one of the following:• Select an option indicating you want to restart your computer immediately. Then

click Finish. • Select an option indicating you will restart your computer later. Then click Finish.

You must restart for the installation to be complete.23 If you have previously made any customizations to PropertiesDataDescription.xml, the

upgrade process creates a backup copy of your modified version and appends the .<version>.bak extension to it. The new, unmodified version of the file is installed to the same location. To retain your customizations, do the following:a Navigate to the <Reports install directory>/config directory. b Merge any customized changes from the .<version>.bak files to the .xml files.

To view the home page for BladeLogic Reports, use the Start menu and select Programs > BladeLogic > Reports > Reports Home Page.

Note: If you have chosen to recreate your reporting data warehouse as opposed to upgrading your data and, as such, did not follow the procedure documented in the “Upgrading the BladeLogic Reports Data” section, you need to execute the last few steps of this procedure starting at step 10.



Upgrading BladeLogic Reports on UNIXUse this procedure to upgrade a reports server running an older version of BladeLogic Reports on a UNIX machine.

Procedure 1 If upgrading from 7.0.1 or a newer version, proceed to step 2. If you are upgrading from a version older than 7.0.1, run the drop_reports_repository_<database type>.sql script on the repository database for BladeLogic Reports. You can find this script in the file structure extracted from <external-files.zip>, in db_scripts/<database type>/schema.

2 Log in as root.3 Navigate to the directory containing installation files and invoke the installation script

for BladeLogic Reports.A message like the following displays:A previous installation already exists in [/usr/local/bl-reports].Do you wish to continue?

4 Enter y.Another message displays saying a previous installation has been detected.

5 Enter y to continue.A message displays, asking you to read third party software license agreements.

Note: Be aware of the following:• An RSCD agent must be installed on the reports server.• If you are installing on Solaris, the SUNWxwrtl package must be installed.• If you are installing on Linux, the following are required:

> The /tmp directory must have at least 200 MB of available disk space.> If you are installing on Red Hat Linux, the compat-libstdc++ RPMs must

be installed. Also, the XFree86-libs or xorg-x11-libs RPMs must be installed.

> If you are installing on SuSE 8.x, the compat and xf86 RPMs must be installed.

> If you are installing on SuSE 9.x, either the compat or compat-32bit RPM must be installed and the xf86 RPM must be installed.

> If you are installing on SuSE 10.x, either the compat or compat-32bit RPM must be installed and the xorg-x11 RPM must be installed.

• To complete this procedure, you must provide database connection information. To set up a reporting database, see Setting Up the Schemas for BladeLogic Reports (page 28).

• Most of the fields in the installation program are already populated with values based on your previous installation.



6 Press Enter.An acknowledgment displays listing the third party software that BladeLogic uses. Licensing text for those third parties follows the acknowledgment.

7 When you are done reading the license agreements, press Enter.A message displays, warning that you must review text about terms and conditions for using BladeLogic software.


9 Read the licensing text. If you agree with its terms, enter y.A message displays asking you to enter the host name of the reports server.

10 Enter the name of the reports server that will be used in URLs that access BladeLogic Reports, or press Enter to accept the host name that the installation program is reading for this machine. A message prompts you to confirm your entry.

11 Enter y to confirm your entry for the host name.A message displays telling you to configure the ports that the Tomcat server should use, beginning with the HTTP port.

12 Enter the port to which the Tomcat server should listen for HTTP traffic.A message prompts you to enter an HTTPS port.

13 Do one of the following:• If BladeLogic Reports should not use secure communication based on SSL, enter 0.

A message displays showing the configuration you have specified for the HTTP port. If the configuration is correct, enter y.

• If BladeLogic Reports should use secure communication based on SSL certificates, do the following:a Enter the port that the Tomcat server should use to service HTTPS requests (that

is, HTTP over SSL).If you enter a value for HTTPS, the installation program creates a self-signed certificate, which is stored in the keystore location you identify in the next step.A message prompts you for the certificate location.

b Enter the path to the keystore where a certificate should be stored.A message prompts you for a password to the certificate.

c Enter a password and then confirm the typing for your password.A message displays showing the configuration you have specified.

d If the configuration is correct, enter y.



The following displays:Please enter the Operations Manager database connection parameters:Database Server []:

14 Provide connection parameters for the core BladeLogic database by doing the following:a Enter the name of the server running the BladeLogic core database.

The following displays:Database Port []:

b Enter the port the database listens on. By default a BladeLogic installation uses the following database port.

The following displays:SID []:

c Enter the SID of the Oracle database. Typically this name is bladelogic.The following displays:User ID []:

d Enter a login ID for the BladeLogic database.The following displays:Password []:

e Enter a password for the BladeLogic database login ID.A message displays showing the database parameters you have selected.

f If the database parameters are correct, enter y.A message displays telling you to select the type of database for the reporting data warehouse.

15 Provide database connection parameters for the reporting data warehouse, just as you did in step 14. The database name or SID for the warehouse is typically blreports. After you provide connection parameters, the following displays:Please enter your Oracle Home Directory.

Oracle Home []:

16 Enter your Oracle home directory. A message displays showing the Oracle home directory you have entered. The following displays:Please enter the Net Service name associated with the warehouse database.

Net Service []:


Oracle 1521



17 Enter the Oracle Net Service name.A message displays showing the Oracle Net Service name you have entered.

18 If the database parameters are correct, enter y.19 Configure a connection with the Application Server by doing the following:

a Enter the name of the host where the Application Server is installed.The following displays:Port [9829]:

b Enter the port on which the Application Server should listen for communication from BladeLogic Reports. By convention, the Application Server listens for SRP traffic on port 9829. For information on configuring the Application Server port for other purposes, see the BladeLogic Administration Guide.When you enter the port number, a message displays, asking you whether the Application Server parameters are correct.

c If the Application Server parameters are correct, enter y.The following displays:Configure an SMTP relay through which notifications will be sent from the BladeLogic Reporting module.

Server []:

20 Do one of the following:• If you do not want to configure an SMTP server, leave this field blank. A message

says you have chosen not to configure SMTP parameters. If that is correct, enter y.• If you want to configure an SMTP server, do the following:

a Enter the name or IP address of the host managing email. If you want to disable the SMTP Server, leave this field blank.The following displays:Port []:

b Enter the port on which an SMTP server listens for traffic.The following displays:Email From []:

c Enter the email address from which BladeLogic-generated email is sent. A message displays, asking you whether the SMTP parameters are correct.

d If the SMTP parameters are correct, enter y.A series of messages display and the installation is complete.



21 If you have previously made any customizations to PropertiesDataDescription.xml, the upgrade process creates a backup copy of your modified version and appends the .<version>.bak extension to it. The new, unmodified version of the file is installed to the same location. To retain your customizations, do the following:a Navigate to the <Reports install directory>/config directory. b Merge any customized changes from the .<version>.bak files to the .xml files.

To view the home page for BladeLogic Reports, enter the following address into a web browser:

https://reports_server:port_number/BladeLogicReports

where reports_server is the server that hosts BladeLogic Reports and port_number is the HTTPS port specified during installation. If BladeLogic Reports is not configured to use secure communication over SSL, enter the same URL but precede it with http instead of https, and specify the HTTP port instead of the HTTPS port.If the HTTPS port is 443 or the HTTP port is 80, it can be omitted from the URL.

Upgrading the PXE ServerUse the following procedures to upgrade the PXE Server.• Upgrading a PXE Server on Windows• Upgrading a PXE Server on UNIX

Upgrading a PXE Server on WindowsUse this procedure to upgrade a PXE Server on Windows.

Note: If you have chosen to recreate your reporting data warehouse as opposed to upgrading your data and, as such, did not follow the procedure documented in the “Upgrading the BladeLogic Reports Data” section, you need to execute the last few steps of this procedure starting at step 10.

Warning: If the PXE Server is installed on a machine where the Configuration Manager console is also installed, you should only perform this procedure after upgrading all other components in a BladeLogic system.



Procedure 1 Navigate to the directory containing installation files and invoke the installation program for the PXE Server. The installer extracts files needed for installation and displays the Setup Type window.

2 Select Upgrade and click Next.


install or you are installing on a Windows Server 2003 machine, you must install in Installation mode rather than Execution mode, or you must install using the Windows Add or Remove Programs utility. For more information, see Using Installation Mode Rather Than Execution Mode (page 133).



A progress bar shows the progress of the installation. The Upgrade Complete window announces that the upgrade is complete.

3 Click Finish to complete the upgrade to your installation.

Upgrading a PXE Server on UNIXUse this procedure to upgrade a PXE Server running on a UNIX machine. This procedure requires you to record the existing settings for the PXE Server, uninstall it, and then reinstall the PXE Server using the settings you have recorded.

Procedure 1 Record the following settings for the PXE Server:• Installation directory (typically usr/nsh)• Database connectivity information

The PXE Server uses the same database as the Application Server. One way to obtain this information is to start the Application Server Administration console (also known as the blasadmin utility) and enter the following command:

show database all

• Host name and IP address of the PXE Server• DHCP server location (local or remote)• TFTP root directoryYou do not have to record the name and location of the data store.

2 Uninstall the PXE Server.

Warning: If the PXE Server is installed on a machine where the BladeLogic console is also installed, you should only perform this procedure after upgrading all other components in a BladeLogic system.



Currently, on UNIX-style servers you cannot selectively uninstall one BladeLogic component. You must uninstall all BladeLogic components. For more information see Uninstalling All BladeLogic Components on UNIX (page 173).

3 Install the latest version the PXE Server. As you use the installation program, be sure to provide information that matches the settings you recorded in step 1. For more information, see Installing the PXE Server on UNIX (page 190).

Using BladeLogic Data Migration ManagerBladeLogic Data Migration Manager simplifies and automates the data upgrade process. Refer to the Release Notes for information on which upgrade paths BladeLogic Data Migration Manager supports in this release.

In addition to running the data upgrade, you can use BladeLogic Data Migration Manager to check that your environment is ready for a data upgrade without actually running the upgrade. Also, you can access logs from the current environment checks and upgrades or from the last BladeLogic Data Migration Manager session.

From the BladeLogic Data Migration Manager console, you can determine the following information:• Current version of the database.• Upgrade path to be executed.• Status of the environment check.• Status of the data upgrade.

and execute the following tasks:• Validate your environment to ensure it is ready for the database upgrade (Oracle only).

For more information, see Validating Oracle Environments.• Run the database upgrade (this automatically validates your environment before starting

the upgrade). For more information, see Running Data Upgrades.• Track the progress of the validation and upgrade tasks.• Get estimates on the amount of time the upgrade will take.• View results from verifications or upgrades launched from the current BladeLogic Data

Migration Manager session or from the previous session. For more information, see Viewing Results and Viewing Results from Previous Sessions.

• Export logs. For more information, see Exporting Logs.• Restart a data upgrade if a previous attempt did not run to completion.



Validating Oracle EnvironmentsTo validate that your Oracle environment is ready to be upgraded, do the following:

Procedure 1 Click Validate Environment. The progress of the environment check displays in the results table in the Migration progress area of the console. When the execution of the tasks completes, a message with the overall status of the validation displays, and the result of the validation check (whether it passed or failed) is shown next to the Environment check label in the Migration status area of the console.

For more information on viewing the results, see Viewing Results. If the validation completed successfully and you want to run the actual upgrade, see Running Data Upgrades.

Status of check

Results table



Running Data UpgradesTo start the upgrade or restart an upgrade that had not run to completion previously, do one of the following:

Procedure 1 Click Run Migration or Continue Migration.BladeLogic Data Migration Manager creates the stored procedures needed for the upgrade, executes the environment validation tasks, and if the validation is successful, starts running the upgrade tasks. In the case where you are continuing an upgrade that had previously not run to completion, BladeLogic Data Migration Manager continues the upgrade from the last completed step. The progress of the tasks displays in the results table in the Migration progress area of the console. If the upgrade path includes multiple versions, the version being updated is highlighted in bold in the Migration path section of the Migration status area of the console. When the upgrade for each version completes, BladeLogic Data Migration Manager moves on to the next. For each version in the upgrade path, it creates the necessary stored procedures, executes the environment validation tasks, and if the validation is successful, starts running the upgrade tasks for that version. The log is reset as each upgrade commences.



When the execution of all the tasks completes, a message with the overall status of the upgrade displays, and the result of the upgrade (whether it passed or failed) is shown next to the Migration result label in the Migration status area of the console.

For more information on viewing the results, see Viewing Results.

Viewing ResultsBladeLogic Data Migration Manager displays the results of an environment check or a database upgrade in the results table. Each row corresponds to a main task. The following information is available for each task:

Status of upgrade - in this example the upgrade is still running

Upgrade path - in this example, the version in bold is in the process of being upgraded

Results table

Column Description

Group The name of the group of which the task is a member. Task groups are groups of tasks related to the same feature or function.

Task Name of the task.

Task Entry Date

The date and time of the task started to run.



In addition, you can also access the task details (see Accessing Subtasks) or the full log including all the tasks, not just the main tasks or just a set of subtasks for a particular main task (see Viewing the Full Log for a Validation Check or Upgrade).

Accessing SubtasksProcedure To access subtasks from the results table, do any of the following:

• Double click on a main task row.• Click the Task Details icon (see list of icons).

The log for the task appears in a new window in the same format as results table described in Viewing Results.

Viewing the Full Log for a Validation Check or UpgradeProcedure To view the full log for a validation check or upgrade, do the following:

1 Click Show Log. The full log for the validation or upgrade appears in a new window in the same format as results table described in Viewing Results.

2 From the Task Log window, you can perform any of the following:• Export the log (see Exporting Logs).• Limit the information displayed as follows:

> To not include the success messages in the log, uncheck Show Information.> To not include the warning messages in the log, uncheck Show Warnings.> To not include the error messages in the log, uncheck Show Errors.

• Close the window, click Close.

Status Whether or not the task ran to successful completion.

Estimated Run Time

Original estimate of the time the task will take to run.

Current Run Time

Length of time the task has run.

Message Message generated by the task.

Column Description



Copying to the Clipboard

You can select one or more lines of text from the results table or a log window and copy it to the clipboard. Once it is copied to a clipboard, you can paste this information into a document or spreadsheet.

Procedure 1 In the results table or a log window, select one or more lines of textual information.2 Right-click and select Copy to Clipboard from the pop-up menu.

Exporting LogsProcedure To export a log, do the following:

1 From a log window, click the Export Log icon (see list of icons). The Export Results dialog displays.

2 On the dialog, for Object Name, provide a file name and location where you want to store the exported results log.

3 From File encoding, select the type of character encoding that should be used for the exported data, such as UTF8 or UTF16.

4 On the Export Results dialog, click Save.A message displays when the export is complete.

Viewing Results from Previous SessionsProcedure To view results from a previous BladeLogic Data Migration Manager session:

Launch BladeLogic Data Migration Manager by entering one of the following:• For Windows, enter

blmigration_mgr <path_to_upgrade_directory>

• For UNIX, enterblmigration_mgr <path_to_upgrade_directory>

where <path_to_upgrade_directory> is the path to the upgrade directory on the Application Server. You must use the operating system-style path when specifying the path.



For example, if you copied the contents of upgrade to \tmp\upgrade on a Windows system, you would execute the following command:

.\blmigration_mgr \tmp\upgrade

If you have already completed the data upgrade in a previous BladeLogic Data Migration Manager session, you will get a warning that there is no migration path from the current version.

The console displays with the log options enabled and the other options disabled.

For information on viewing the results, see Viewing Results.


Installing and Uninstalling on Windows

This chapter provides installation and maintenance procedures for all BladeLogic components, including Configuration Manager, Network Shell, Application Server, and the RSCD agent. This chapter organizes information into the following sections:• Installing Client-tier and Middle-tier Components on Windows• Modifying, Repairing, or Removing Client-tier and Middle-tier Components

on Windows• Installing and Uninstalling RSCD Agents

Installing Client-tier and Middle-tier Components on WindowsThis section describes how to install BladeLogic’s client-tier and middle-tier components, including Network Shell, Configuration Manager, and the Application Server. BladeLogic’s installation program allows you to choose three approaches to installing client and middle-tier components. • Typical installation—Installs BladeLogic’s client utilities, which includes Configuration

Manager, Provisioning Manager, and Network Shell, along with any associated help files and documentation. Generally organizations use a typical installation to set up consoles for monitoring a BladeLogic installation. When you use a typical installation you must also set up a middle-tier, including the Application Server and a database. For more information, see Performing a Typical Install (Configuration Manager and Network Shell).

• Full installation—Installs all BladeLogic components except RSCD agents. A full installation is useful for quickly setting up a stand-alone system that includes both client and middle-tier components. For more information, see Performing a Full Installation (All BladeLogic Components).

• Custom installation—Allows you to select the components you want to install. The installation program enforces any dependencies between programs. When you install components that rely on the presence of other components, you must also install those other components. For more information, see Performing a Custom Installation.

This section also describes how to install Network Shell by itself (see Installing Only Network Shell).

A standard installation does not set up a Network Shell Proxy Server. For detailed instructions on setting up and customizing a Network Shell Proxy Server, see the BladeLogic Administration Guide.

Installing and Uninstalling on Windows 92


Performing a Typical Install (Configuration Manager and Network Shell)Use this procedure to perform a typical BladeLogic installation, which installs Configuration Manager, Provisioning Manager, and Network Shell when no previous version of those programs exists on your system. This procedure does not include installation of an Application Server. See Performing a Custom Installation for information on installing an Application Server.

If the host where you are installing Network Shell has ActiveState Perl version 5.6.1 installed, this installation automatically installs the Network Shell Perl module. If you have some other version of Perl installed, the installation still installs the Perl module but it may be incompatible with your Perl executable.

Procedure 1 Navigate to the directory containing installation files and invoke the installation program for BladeLogic. The Choose Setup Language window opens.

2 Select a language to use for the installation. The language you choose will be the default language for the Provisioning Manager and Configuration Manager consoles, but can be changed when logging in (see Setting the Language for the Installers on Windows for more information). Click Next.


install or you are installing on a Windows Server 2003 machine, you must install in Installation mode rather than Execution mode, or you must install using the Windows Add or Remove Programs utility. For more information, see Using Installation Mode Rather Than Execution Mode.



The installer extracts the files needed for installation and displays the Welcome window.

3 Click Next. The Acknowledgments window opens, providing license information for all third-party software products included in BladeLogic.




5 If you want to print the license agreement, click Print and the license agreement is printed to your default printer.

6 After reading the license agreement, click Yes if you agree with its terms. The Customer Information window opens.



7 Enter your name and the name of your organization. Then click Next. The Setup Type window opens.

8 Select Typical and click Next. Selecting Typical instructs the installation program to install Configuration Manager, Provisioning Manager, Network Shell, and associated help files. The Choose Destination window opens.

9 Specify a directory for your installation by doing one of the following:• Accept the default location (C:\Program Files\BladeLogic\OM) by

clicking Next. • Select another location by clicking Browse. The Choose Folder dialog displays. Use

it to select a directory for the installation and click OK. Then click Next.



10 The Selected Components window opens.

11 Review the current settings to confirm that you have specified the correct installation configuration and then click Next. The InstallShield Wizard Complete window declares that the installation is complete.

12 Click Finish to complete the installation.See Starting Network Shell, Configuration Manager, and Provisioning Manager for instructions on starting Configuration Manager and Provisioning Manager.



Performing a Full Installation (All BladeLogic Components)Use this procedure to perform a full BladeLogic installation, which installs all BladeLogic components needed for a BladeLogic system except RSCD agents. The components installed in a full installation are as follows:

Network ShellConfiguration Manager ConsoleProvisioning Manager ConsoleApplication ServerProvisioning ServerOnline help and documentation

Running a full installation allows you to quickly set up a stand-alone version of the client and middle tiers of a BladeLogic system. To set up the server tier, install RSCD agents (see Installing the RSCD Agent on Windows).

If you are installing an Application Server that should cooperate with other Application Servers to balance their job processing workloads, all of the Application Servers must meet the following requirements:• Each Application Server must be installed on a separate server. • Each Application Server must be configured to access the same database. • The tpasswd.conf file from one Application Server must be copied to all cooperating

Application Servers.On UNIX-style systems, tpasswd.conf can be found in the nsh/br directory. On Windows, tpasswd.conf can be found in the OM\br directory.

• System clocks on all Application Servers must be synchronized to within a few seconds of each other.

If the host where you are installing the Application Server has ActiveState Perl version 5.6.1 installed, this installation automatically installs the Network Shell Perl module. If you have

Note: Prior to performing the full installation, your DBA must set up your database schema, see Using Databases with BladeLogic for more information.



some other version of Perl installed, the installation still installs the Perl module but it may be incompatible with your Perl executable.












5 If you want to print the license agreement, click Print and the license agreement is printed to your default printer.





8 Select Full and click Next. The Selected Components window opens.

9 Review the current settings to confirm that you have specified the correct installation configuration and then click Next. A progress bar indicates the progress of the installation until the Certificate Password window opens. The Certificate Password window prompts you for a password, which is needed to generate a self-signed X.509 certificate. Communication between Provisioning Manager and servers being provisioned and between the Application Server and the process spawner uses the TLS protocol and X.509 certificates. For more



information on certificates and the TLS protocol, see the BladeLogic Administration Guide.

10 On the Certificate Password window, enter a password for the certificate. Then, for Verify, enter the password again to confirm its accuracy.When you enter this information, the installation program runs the following command:

keytool -genkey -alias blade -keyalg RSA -keysize 1024 -dname "CN=hostname" -keypass password1 -storepass password1 -keystore "<install_dir>\br\bladelogic.keystore" -validity 1000

If you ever need to manually generate a certificate, you can use this command. In the command shown above, CN stands for Common Name. The installation program uses the host name for a Common Name, but you can set it to any value.



11 Click Next and the Post-Configuration Options window opens.

12 Check Configure the Application Server, if desired, and click Next. The Configure the Application Server option opens BladeLogic’s Post-Install Configuration wizard, which lets you rapidly make a BladeLogic system operational by configuring the Application Server and setting up administrator passwords. This option is only available if you are installing the Application Server.

13 If you checked Configure the Application Server, use the Post-Install Configuration wizard to configure the Application Server and set up administrator passwords. For information on using the wizard, see Using the Post-Install Configuration Wizard.

14 Click Finish. The installation is complete. See Starting Network Shell, Configuration Manager, and Provisioning Manager for instructions on starting the client-tier applications. See Starting the Application Server for instructions on starting the Application Server. See



the BladeLogic Administration Guide for instructions on configuring the Application Server.BladeLogic recommends that you synchronize the clock on the Application Server and all client machines. Clocks should be synchronized to the minute. For example, if an Application Server is in Boston, where the time is 7:04, the clock on client machines in San Francisco should be set to 4:04. The clocks on Application Servers that are balancing their workloads should be synchronized to within a few seconds of each other.

Performing a Custom InstallationUse this procedure to perform a custom BladeLogic installation, which allows you to choose the components you want to install. For example, you might want to install just the Application Server and Network Shell if you are setting up a machine that will function as a middle tier for a BladeLogic installation. The details of this procedure vary depending on the options you choose to install.




If the host where you are installing the Application Server has ActiveState Perl version 5.6.1 installed, this installation automatically installs the Network Shell Perl module. If you have



some other version of Perl installed, the installation still installs the Perl module but it may be incompatible with your Perl executable.



Note: Be aware of the following:• You must provide database connection information to complete this procedure.

If you want to set up the BladeLogic database before you begin to install software, see the Using Databases with BladeLogic chapter.

• To perform this installation, you must have local Administrator privileges.• If you are using Windows Terminal Services or Citrix Presentation Server to













7 Select Custom and click Next. The Choose Destination Location window opens.

8 Specify a directory for your installation by doing one of the following:• Accept the default location (C:\Program Files\BladeLogic\OM) by


it to select a directory for the installation and click OK. Then click Next.



The Select Features window opens.

9 Choose the desired components needed for an Application Server by doing the following:• To install the client utilities, check Network Shell, Configuration Manager

Console, Provisioning Manager Console, or a combination of these choices. When installing the Application Server or Configuration Manager, you must install Network Shell so the installation program automatically selects it. You cannot clear the Network Shell option until you first clear the Application Server and Configuration Manager options.

• To install the Application Server, check Server Utilities, which should automatically check Application Server as well. You can optionally check Provisioning Server to install the provisioning server, which is a component needed when you are using Provisioning Manager.

• Under Documentation, select Online Documentation to install manuals in PDF format. Select Online Help to install HTML-based help for Configuration Manager. You cannot clear the Online Help option until you first clear the Configuration Manager Console option under Client Utilities.

10 Click Next. The Application Server JVM Settings window opens, which lets you define the heap size for a Java Virtual Machine (JVM).



By default, the installer sets the minimum and maximum heap size to be half the memory of the local machine.

11 Enter the maximum value for the heap size of the Java Virtual Machine. 12 Click Next. The Selected Components window opens.

13 Review the current settings to confirm that you have specified the correct installation configuration and then click Next. A progress bar indicates the progress of the installation. If you are installing the Application Server, the Certificate Password window opens. The Certificate Password window prompts you for a password, which is needed to generate a self-signed X.509 certificate. Communication between Provisioning Manager and servers being provisioned and between the Application Server and the process spawner uses the TLS



protocol and X.509 certificates. For more information on certificates and the TLS protocol, see the BladeLogic Administration Guide.

14 On the Certificate Password window, enter a password for the certificate. Then, for Verify, enter the password again to confirm its accuracy.When you enter this information, the installation program runs the following command:

keytool -genkey -alias blade -keyalg RSA -keysize 1024 -dname "CN=hostname" -keypass password1 -storepass password1 -keystore "<install_dir>\br\bladelogic.keystore" -validity 1000




15 Click Next, and the Post-Configuration Options window opens.

16 Check Configure the Application Server, if desired, and click Next. The Configure the Application Server option opens BladeLogic’s Post-Install Configuration wizard, which lets you rapidly make a BladeLogic system operational by configuring the Application Server and setting up administrator passwords. This option is only available if you are installing the Application Server.

17 If you checked Configure the Application Server, use the Post-Install Configuration wizard to configure the Application Server and set up administrator passwords. For information on using the wizard, see Using the Post-Install Configuration Wizard. When you finish using the wizard, the InstallShield Wizard Complete window opens.

18 Click Finish. The installation is complete. See Starting Network Shell, Configuration Manager, and Provisioning Manager for instructions on starting the client-tier applications. See



Starting the Application Server for instructions on starting the Application Server. See the BladeLogic Administration Guide for instructions on configuring the Application Server.BladeLogic recommends that you synchronize the clock on the Application Server and all client machines. Clocks should be synchronized to the minute. For example, if an Application Server is in Boston, where the time is 7:04, the clock on client machines in San Francisco should be set to 4:04. The clocks on Application Servers that are balancing their workloads should be synchronized to within a few seconds of each other.

Installing Only Network ShellUse this procedure to install only Network Shell. You cannot perform this procedure if you have a previous version of Network Shell installed or any version of Configuration Manager installed.

If the host where you are installing Network Shell has ActiveState Perl version 5.6.1 installed, this installation automatically installs the Network Shell Perl module. If you have some other version of Perl installed, the installation still installs the Perl module but it may be incompatible with your Perl executable.

Procedure 1 Navigate to the directory containing installation files and invoke the installation program for Network Shell. If this is the initial installation, the Choose Setup Language window opens in the local language of the Windows operating system. All subsequent invocations of the installer (upgrades and uninstalls) will use the language selected at the initial installation. To

Note: If you want to run Network Shell so it communicates with a Network Shell Proxy Server and uses BladeLogic's single sign-on capabilities, then you need to install Configuration Manager, which automatically installs Network Shell. See Installing Client-tier and Middle-tier Components on Windows for information on installing Configuration Manager.





choose a different language after an initial installation, first uninstall the product, and then run the install program again.

2 Select a language to use for the installation. Click Next.The installer extracts the files needed for installation and displays the Welcome window.







5 Enter your name and the name of your organization. The Choose Destination Location window opens.

6 Specify a directory for your installation by doing one of the following:• Accept the default location (C:\Program Files\BladeLogic\NSH) by


it to select a directory for the installation and click OK. Then click Next.The Selected Components window opens.




installation until the InstallShield Wizard Complete window declares that the installation is complete.

8 Click Finish to complete the installation.See Starting Network Shell, Configuration Manager, and Provisioning Manager for instructions on starting the client tier applications.

Modifying, Repairing, or Removing Client-tier and Middle-tier Components on Windows

Use the procedures described in this section to perform maintenance activities on client-tier and middle-tier BladeLogic components. This section includes the following procedures:

Modifying an Existing InstallationRepairing an Existing InstallationRemoving All Components

Modifying an Existing InstallationUse this procedure to add BladeLogic components to an existing application.

Procedure 1 Navigate to the directory containing the installation program for the version of BladeLogic that is currently installed and invoke the installation program.




2 Select Modify and click Next.The Select Components window opens.

3 Choose the components you want to install by doing the following:• To install the client utilities, check Network Shell, Configuration Manager

Console, Provisioning Manager Console, or a combination of these choices. When installing the Application Server or Configuration Manager, you must install Network Shell so the installation program automatically selects it. You cannot clear the Network Shell option until you first clear the Application Server and Configuration Manager options.

• To install the Application Server, check Server Utilities, which automatically checks Application Server as well. You can optionally check Provisioning Server



to install the provisioning server, which is a component needed when you are using Provisioning Manager.

• Under Documentation, select Online Documentation to install manuals in PDF format. Select Online Help to install HTML-based help for Configuration Manager.


5 Review the current settings to confirm that you have specified the correct installation configuration and then click Next. A progress bar indicates the progress of the installation until either the Post-Configuration Options window opens or the Maintenance Complete window opens. The Post-Configuration Options window only displays if you are adding the Application Server.

6 Check Configure the Application Server, if desired, and click Next. The Configure the Application Server option opens BladeLogic’s Post-Install Configuration wizard, which



lets you rapidly make a BladeLogic system operational by configuring the Application Server and setting up administrator passwords.

7 If you checked Configure the Application Server, use the Post-Install Configuration wizard to configure the Application Server and set up administrator passwords. For information on using the wizard, see Using the Post-Install Configuration Wizard. When you finish using the wizard, the Maintenance Complete window opens.

8 Click Finish to complete the installation.See Starting Network Shell, Configuration Manager, and Provisioning Manager for instructions on starting the client tier applications. See the BladeLogic Administration Guide for instructions on configuring the Application Server.

Repairing an Existing InstallationUse this procedure to repair an existing installation by reinstalling everything that was installed during the last setup process.

Procedure 1 Navigate to the directory containing the installation program for the version of BladeLogic that is currently installed and invoke the installation program.




2 Select Repair and click Next. A progress bar indicates the progress of the installation until the Maintenance Complete window declares that the installation is complete.

Removing All ComponentsUse this procedure to remove all client-tier and middle-tier BladeLogic components from a server, including Configuration Manager, Network Shell, and the Application Server.



Before performing this procedure, you may want to save some or all of the following configuration files:• \Program Files\BladeLogic\OM\br\tpasswd.conf, which is used to

generate a one-way hash for encrypted user passwords.

• \Program Files\BladeLogic\OM\br\config.xml, which defines behavior for the Application Server and other BladeLogic components.

• <Windows_directory>\rsc, a directory that holds several important files, including the exports, users, and secure files. These files define communication and security settings for an RSCD agent. The rsc directory also contains license.dat, which holds licensing information for the RSCD agent.

Procedure 1 Do one of the following:• From the Start menu, select Programs > BladeLogic > Uninstall Operations

Manager. • From the Windows Control Panel, open the Add/Remove Programs dialog. Select

BladeLogic Operations Manager and click Change/Remove. The Confirm Uninstall dialog displays.

2 Click OK.

Warning: BladeLogic strongly recommends saving tpasswd.conf. Losing this file would require you to reset all user passwords. Because this file can be used to launch an attack on your system security, BladeLogic also recommends keeping tpasswd.conf very secure at all times.



The Uninstall Complete window announces that the uninstall is complete.

3 Click Finish to complete the uninstall.

Installing and Uninstalling RSCD AgentsUse the procedures described in this section to do any of the following:

Installing the RSCD Agent on WindowsUninstalling the RSCD Agent on Windows

Note: The uninstall does not delete some log files that Configuration Manager creates.

Note: For a server to provide information about Windows Group Policy objects, the file secedit.exe must be installed on the server and it must be included in the server’s path.



Installing the RSCD Agent on WindowsUse this procedure to install an RSCD agent when no previous version of the agent exists on your system.

Procedure 1 Navigate to the directory containing installation files and invoke the installation program for the RSCD agent. If this is the initial installation, the Choose Setup Language window opens in the local language of the Windows operating system. All subsequent invocations of the installer (upgrades and uninstalls) will use the language selected at the initial installation. To choose a different language after an initial installation, first uninstall the product, and then run the install program again.

2 Select a language to use for the installation and click Next.

Note: Be aware of the following:• If you are installing an agent on a Windows server that is a Windows domain

controller, please make sure that the Netlogon service is enabled and running before installing the agent. This ensures the agent gets installed with correct service dependencies.

• To avoid problems caused by user replication in replicated domain controller environments, you should follow a recommended procedure for installing or upgrading agents, as described in Installing Agents in a Replicated Domain Controller Environment.

• If you are using Windows Terminal Services or Citrix Presentation Server to install or you are installing on a Windows Server 2003 machine, you must install in Installation mode rather than Execution mode, or you must install using the Windows Add or Remove Programs utility. For more information, see Using Installation Mode Rather Than Execution Mode.





Note: If the Microsoft XML (MSXML) 2.5 or later parser is not installed on this server, a warning displays. MSXML is installed by default on Windows 2003 and XP machines but not on Windows 2000. For BladeLogic’s patch analysis functionality to be operable, MSXML 2.5 or later must be installed. You can cancel the installation or click OK to continue. If you continue, patch analysis will not function correctly on this server until MSXML 2.5 or later is installed.





6 Do one of the following:• To perform a typical agent installation, select Typical and click Next. • To provide information used to define user permissions, select Expert and click

Next. Performing an expert installation requires a solid understanding of how BladeLogic uses configuration files to set user permissions and allows you to set security options for logging.



The Choose Destination Location window opens.

7 Specify a directory for your installation by doing one of the following:• Leave the default location unchanged. The default location is C:\Program

Files\BladeLogic\RSC.• Select another location by clicking Browse. The Choose Folder dialog displays. Use

it to select a directory for the installation and click OK. 8 Click Next and one of the following occurs:

• If you are performing a typical installation, a window lets you review your current installation options. Proceed to step 15.

• If you are performing an expert installation, a window lets you specify clients where users should be granted Administrator privileges. By default, users with Administrator privileges on client machines are not granted Administrator privileges on servers.



9 For Host, enter the name of a client where users with Administrator privileges should be granted local Administrator privileges on this server.

10 Click Next, and a window lets you map a user on a client to a user on a server.

Typically you map user names to give Administrator privileges on the server to client users. If you do not map user privileges, BladeLogic will attempt to map a client user to an existing user on the server. If no match is found, BladeLogic maps the user to Anonymous. However, BladeLogic does not automatically map Administrator on the client to Administrator on the server unless you make that possible for a particular client by specifying its host name in the previous step. If you use this window to map a client user to a local user, the client user receives the local user’s privileges when connecting from any client machine. To implement this mapping, BladeLogic generates an entry in the users.local configuration file. For more information on user privilege mapping and the configuration files, see the BladeLogic Administration Guide.

11 To map users between clients and the server, enter a client user name in Client Name. For Local User, enter a user name on the server.

Note: NT Domain Controllers have no local users. For information on granting Administrator privileges on NT Domain Controllers, see the BladeLogic Administration Guide.



12 Click Next, and a window lets you specify logging security.

13 Do any of the following:• Check Use secure (digitally signed) agent logs to secure agent logs by assigning

message authentication codes and sequence numbers to the current log, and by digitally signing the rolled logs.

• Check Use keystroke logs for nexec commands to create keystroke logs for capturing log information for remote commands run on the agent using nexec

14 Click Next.A window lets you review your current installation options.

15 If the current installation settings are correct, click Next.



The next window declares that the installation is complete.

Agents are automatically licensed with a demonstration license valid for only two weeks. Visit www.bladelogic.com/support.jsp to obtain and install long-term licenses for one or more agents. For general information on licensing agents, see Licensing Agents.

16 Click Finish to complete the installation.

Uninstalling the RSCD Agent on WindowsUse this procedure to uninstall an RSCD agent.

Procedure 1 From the Start menu, select Settings > Control Panel. Double-click Add/Remove Programs. Select RSCD agent, and then click Change/Remove.The installer extracts files. What the installer displays next depends on which version of the RSCD agent you currently have installed.

http://www.bladelogic.com/support.jsp



2 Do one of the following:• If the installer detects an earlier version of the RSCD agent, it displays the Setup

Type window. Select Uninstall and then click Next.

• If the installer detects that the current version of the RSCD agent is installed, it displays a dialog asking if you want to uninstall the RSCD Agent. Click Yes.

After you take either of the actions described above, the Confirm Uninstall dialog displays.

3 Click OK.



The next window announces that the uninstall is complete.

4 Click Finish to complete the uninstall.

Installing Agents in a Replicated Domain Controller EnvironmentIn Windows environments where replication occurs between two or more domain controllers, the RSCD agent can sporadically fail to connect to at least one of the domain controllers. (The message “No authorization to access host” displays.) This problem occurs because replication can cause the BladeLogicRSCD user (a user who is automatically created when you install the RSCD agent) to have incorrect Local Security Policies. This procedure describes how to avoid those incorrect settings by setting Domain Controller Security Policies on one domain controller and then installing RSCD agents in the correct sequence on all domain controllers.

Procedure 1 On a domain controller, set Domain Controller Security Policies by doing the following:a Select Security Settings > Local Policies > User Rights Assignment.b Double-click Deny logon locally and check Define These Policy Settings.c Double-click Log on as a batch job and check Define These Policy Settings.

2 Install the RSCD agent on the domain controller. For more information on installing RSCD agents, see Installing and Uninstalling RSCD Agents.

3 License the agent on the domain controller. For more information on licensing agents, see Licensing Agents or visit www.bladelogic.com/support.jsp.

Note: The uninstall leaves log files that BladeLogic created in the directory where the RSCD agent was installed.




4 Using Network Shell, run the agentinfo command on the domain controller’s agent by entering the following command:

agentinfo <DC_name>

where <DC_name> is the name of the server running the domain controller.Running agentinfo (or any Network Shell command) establishes a connection to the RSCD agent on the domain controller, creates a user called BladeLogicRSCD, and creates Domain Controller Security Policies.If Domain Controller Security Policies are not set to “defined,” as described in the first step, the RSCD agent creates Local Security Policies instead. In this situation you must manually set the Domain Controller Security Policies to continue.

5 Confirm that replication has occurred to a second domain controller by checking its Local Security Policy. Both of the policies listed above (Deny logon locally and Log on as a batch job) should be set to “Effective.” Typically replication occurs between domain controllers at five minute intervals.

6 Install the RSCD agent on the second domain controller.7 License the agent on the second domain controller.8 Using Network Shell, run the agentinfo command on the second domain controller’s

agent.Because the BladeLogicRSCD user already exists (as a domain user), it is not re-created.

9 After replication occurs again, run the agentinfo command against both domain controllers. The agents on both machines should successfully return data.

10 Continue installing agents on the remaining replicated domain controllers, as described in the preceding four steps.

Using Installation Mode Rather Than Execution ModeIf you are using Windows Terminal Services or Citrix Presentation Server to install a BladeLogic component or you are installing a component on a Windows Server 2003 machine, you must install in Installation mode rather than Execution mode or you can use the Windows Add or Remove Programs utility. The following are procedures for determining your current mode and temporarily activating Installation mode:

Determining the Current ModeTemporarily Invoking Installation Mode

Note: NT Domain Controllers have no local users. To set up user privilege mapping on NT Domain Controllers, map users to Administrator or the administrator account for the domain. For more information on user privilege mapping, see the BladeLogic Administration Guide.



Determining the Current ModeUse this procedure to determine your current mode.

Procedure 1 From a command line, enter the following:change user /query

2 Use the following table to determine your response.

Temporarily Invoking Installation ModeUse this procedure to temporarily invoke Installation mode.

Procedure 1 From a command line, enter the following:change user /install

2 Install the BladeLogic component.3 From a command line, enter the following:

change user /execute

System Response Your Action

Application EXECUTE mode is enabled Invoke Installation mode or install the component using the Windows Add or Remove Programs utility.

Application INSTALL mode is enabled Do nothing

Application EXECUTE mode is enabled

Install mode does not apply to a Terminal server configured for remote administration

Do nothing

Change command not found Do nothing


Installing BladeLogic Reports

BladeLogic Reports is a reporting tool that makes a variety of data center operations information available to a web-based report viewer. System administrators and IT professionals use BladeLogic Reports to monitor and improve operations throughout the data centers they manage. BladeLogic Reports allow users to view, print, and export reports using a web browser.

To support BladeLogic’s web-based reports, you must set up a reporting environment on a web server. This guide refers to that machine as the reports server.

The following is a high-level description of the process needed to set up a reporting environment. 1 Set up the database tables, as described in Setting Up the Schemas for BladeLogic

Reports. BladeLogic Reports reads data from BladeLogic’s core database and a data warehouse that stores reporting data.

2 Install BladeLogic Reports, as described in the following procedures:• Installing BladeLogic Reports on Windows• Installing BladeLogic Reports on UNIX

3 Make sure the server where you installed BladeLogic Reports meets the following requirements:• An RSCD agent is installed and licensed.• The database client is installed. See Reports Server Software for details.

4 Make sure the logging priority is set to info level or higher on managed servers. The default logging level when you install an agent is info. The logging level is controlled using the priority option in the <category> appender in the log4crc.txt file. For more information on log4crc.txt, see the BladeLogic Administration Guide.

5 Set up data collection jobs. BladeLogic Reports provides three data collections scripts. You must use Configuration Manager to set up these scripts as Network Shell Script jobs that run on a regular basis to collect data for BladeLogic Reports. Setting Up Data Collection Jobs describes how to set up data collection jobs.

6 Set up the Configuration Manager jobs needed to support reports. Some reports are based on Configuration Manager jobs that are run while using Configuration Manager. See the BladeLogic Users Guide for information on setting up jobs in Configuration Manager.

Installing BladeLogic Reports 136


Installing BladeLogic Reports on WindowsUse this procedure to install the reporting environment needed to support BladeLogic Reports on a Windows web server. This machine is called the reports server.

Procedure 1 Navigate to the directory containing BladeLogic installation files and double-click BladelogicReports.exe. If this is the initial installation, the Choose Setup Language window opens in the local language of the Windows operating system. All subsequent invocations of the installer (upgrades and uninstalls) will use the language selected at the initial installation. To choose a different language after an initial installation, first uninstall the product, and then run the install program again.

Note: Be aware of the following:• To complete this procedure, you must provide database connection

information. To set up a reporting database, see Setting Up the Schemas for BladeLogic Reports.

• An RSCD agent must be installed on the machine where you are installing BladeLogic Reports.

• If you are using Windows Terminal Services or Citrix Presentation Server to install or you are installing on a Windows Server 2003 machine, you must install in Installation mode rather than Execution mode, or you must install using the Windows Add or Remove Programs utility. For more information, see Using Installation Mode Rather Than Execution Mode.

• The reports server must have the Oracle or SQL Server client software installed. The version of the client software must correspond to the version of the database server software (see Reports Server Software for more information).



2 Select a language to use for the installation and click Next.The installer extracts the files needed for installation and displays the Welcome window.

3 Click Next. The Acknowledgements window opens, providing license information for all third party software products included in BladeLogic Reports.







6 Enter your name and the name of your organization. Then click Next. The Choose Destination Location window opens.

7 Specify a directory for your installation by doing one of the following:• Accept the default location (C:\Program Files\BladeLogic\Reports) by


it to select a directory for the installation and click OK. Then click Next.The Reports Server Hostname window opens.

8 Enter the name of the reports server that will be used in URLs that access BladeLogic Reports. Then click Next.



The Configure Tomcat Ports window opens.

9 For HTTP, enter the port to which the Tomcat server should listen for HTTP traffic.10 Do one of the following:

• If BladeLogic Reports should not use secure communication based on SSL, leave the HTTPS field blank.

• If BladeLogic Reports should use secure communication based on SSL certificates, enter the following information:HTTPS—The port that the Tomcat server should use to service HTTPS requests (that is, HTTP over SSL).Location—The path to the keystore where a certificate should be stored.Password—The password needed to gain access to the keystore.Confirm—Confirmation of the password.

If you perform this step, the installation program creates a self-signed certificate, which is stored in the keystore location you identify.

11 Click Next. The Operations Manager Database window opens.



This window lets you define a connection to the core BladeLogic database, which contains tables needed for BladeLogic Reports.

12 From Database Type, select the type of database you are using for the core BladeLogic database. Depending on the type you select, other options and default values change on this window.

13 Enter the following information to define a connection with the core database:Host—The name of the server running the database.Port—The port the database listens on. By default a BladeLogic installation uses the following database ports.

Database/SID—The name of the SQL Server database or the SID of the Oracle database. Typically this database is named bladelogic.User—A login ID for the BladeLogic database.Password—A password for the login ID.


Oracle 1521

SQL Server 1433



14 Click Next. The Warehouse Database window opens. It lets you define a connection to the reporting data warehouse.

15 Enter the following information to define a connection with the reporting data warehouse:Host—The name of the server running the reporting data warehouse.Port—The port the warehouse database listens on. By default a BladeLogic installation uses the following database ports.

Database/SID—The name of the SQL Server database or the SID of the Oracle database. Typically this database is named blreports.User—A login ID for the reporting data warehouse.Password—A password for the login ID.If your database type is SQL Server, proceed to step 18. If your Warehouse database type is Oracle, proceed to the next step.

Note: The Database Type is automatically set to the same type of database chosen in the previous window.


Oracle 1521

SQL Server 1433



16 Click Next. If your Warehouse database type is Oracle, the Warehouse Oracle Net Service window opens.

17 Enter the name of the Oracle Net Service for your Warehouse database.18 Click Next. The Application Server Location window opens. BladeLogic Reports

authenticates through the Application Server.

19 Define a connection to the Application Server by providing the following information:Host—Name of the host where the Application Server is installed.Port—The port on which the Application Server should listen for communication from BladeLogic Reports. By convention, the Application Server listens for SRP traffic on port 9829. For information on configuring the Application Server port for other purposes, see the BladeLogic Administration Guide.



20 Click Next. The SMTP options window opens. BladeLogic Reports requires an email server. (SMTP stands for simple mail transfer protocol.)

21 Provide the following information:Server—Name or IP address of the host managing email.Port—Port on which an SMTP server listens for traffic.Email From—Email address from which BladeLogic-generated email is sent.





installation until the InstallShield Wizard Complete window opens and informs you that the installation is finished but you must restart your computer.

24 Do one of the following:• Select an option indicating you want to restart your computer immediately. Then

click Finish. • Select an option indicating you will restart your computer later. Then click Finish.

You must restart for the installation to be complete.25 If your available RAM is greater than 1.5 GB, increase the default Tomcat heap size

from 512 MB to 1/3 of your total available memory rounded up to the nearest 128 MB boundary, but no more than 1/2 of available RAM or 1024 MB maximum, as follows: Change the -Xmx and -Xms values from 512 to the increased heap size in the following registry keys under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Apache Tomcat\Parameters:

26 Navigate to the <BladeLogic_install_dir>/Reports/bin directory and enter the following script:

load_warehouse_schema.bat

The load_warehouse_schema script creates the dynamically generated portion of the reporting data warehouse schema. You must perform this step before you can run the data collection scripts. See the Setting Up Data Collection Jobs for more information.

Key Default Value

JVM Option Number 0 -Xmx512M

JVM Option Number 1 -Xms512M



27 Restart the reports server. From the Windows Start menu, select Settings > Control Panel. Double-click Administrative Tools, and double-click Services. Right-click Apache Tomcat, and select Restart from the pop-up menu.

To view the home page for BladeLogic Reports, use the Start menu and select Programs > BladeLogic > Reports > Reports Home Page.

Installing BladeLogic Reports on UNIXUse this procedure to install the reporting environment needed to support BladeLogic Reports on UNIX-style servers. This machine is called the reports server.

Procedure 1 Log in as root.2 Navigate to the directory containing installation files and invoke the installation script

for BladeLogic Reports.A message displays asking you to choose an installation directory.

3 Enter y to create a new installation directory for BladeLogic Reports in the default location of /usr/local/bl-reports. If that directory already exists, press Enter.A message displays letting you choose a language for the installation program.

Note: Be aware of the following:• An RSCD agent must be installed on the reports server.• If you are installing on Solaris, the SUNWxwrtl package must be installed.• If you are installing on Linux, the following are required:

> The /tmp directory must have at least 200 MB of available disk space.> If you are installing on Red Hat Linux, the compat-libstdc++ RPMs must





• To complete this procedure, you must provide database connection information. To set up a reporting database, see Setting Up the Schemas for BladeLogic Reports.

• The reports server must have the Oracle client software installed. The version of the client software must correspond to the version of the database server software (see Reports Server Software for more information).



4 Enter the number representing the language you want to use for the installation.The following message displays:Welcome to the BladeLogic Reports 7.3 installation script ...Do you wish to continue (y/n) ?

5 Enter y.A message displays, asking you to read third party software license agreements.


7 When you are done reading the license agreements, press Enter.A message displays, warning that you must review text about terms and conditions for using BladeLogic software.


9 Read the licensing text. If you agree with its terms, enter y.A message displays asking you to enter the host name of the reports server.

10 Enter the name of the reports server that will be used in URLs that access BladeLogic Reports, or press Enter to accept the host name that the installation program is reading for this machine. A message prompts you to confirm your entry.

11 Enter y to confirm your entry for the host name.A message displays telling you to configure the ports that the Tomcat server should use, beginning with the HTTP port.

12 Enter the port to which the Tomcat server should listen for HTTP traffic.A message prompts you to enter an HTTPS port.

13 Do one of the following:• If BladeLogic Reports should not use secure communication based on SSL, enter 0.

A message displays showing the configuration you have specified for the HTTP port. If the configuration is correct, enter y.

• If BladeLogic Reports should use secure communication based on SSL certificates, do the following:a Enter the port that the Tomcat server should use to service HTTPS requests (that

is, HTTP over SSL).If you enter a value for HTTPS, the installation program creates a self-signed certificate, which is stored in the keystore location you identify in the next step.A message prompts you for the certificate location.



b Enter the path to the keystore where a certificate should be stored.A message prompts you for a password to the certificate.

c Enter a password and then confirm the typing for your password.A message displays showing the configuration you have specified.

d If the configuration is correct, enter y.The following displays:Please enter the Operations Manager database connection parameters:Database Server []:

14 Provide connection parameters for the core BladeLogic database by doing the following:a Enter the name of the server running the BladeLogic core database.

The following displays:Database Port [1521]:

b Enter the port the database listens on. By default a BladeLogic installation uses the following database port.


Enter the name of the SID of the Oracle database. Typically this name is bladelogic.The following displays:User ID []:

c Enter a login ID for the BladeLogic database.The following displays:Password []:

d Enter a password for the BladeLogic database login ID.A message displays showing the database parameters you have selected.

e If the database parameters are correct, enter y.A message displays telling you to select the type of database for the reporting data warehouse and asking you to provide the database connection parameters for the reporting data warehouse.

15 Choose a database type and provide database connection parameters for the reporting data warehouse, just as you did in step 14. The database name or SID for the warehouse is typically blreports.


Oracle 1521



After you provide connection parameters, the following displays:Please enter your Oracle Home Directory.

Oracle Home []:

16 Enter your Oracle home directory. A message displays showing the Oracle home directory you have entered.

17 If the database parameters are correct, enter y.The following displays:Please enter the Net Service name associated with the warehouse database.

Net Service []:

18 Enter the Oracle Net Service name.A message displays showing the Oracle Net Service name you have entered.

19 If the database parameters are correct, enter y.20 Configure a connection with the Application Server by doing the following:

a Enter the name of the host where the Application Server is installed.The following displays:Port [9829]:

b Enter the port on which the Application Server should listen for communication from BladeLogic Reports. By convention, the Application Server listens for SRP traffic on port 9829. For information on configuring the Application Server port for other purposes, see the BladeLogic Administration Guide.When you enter the port number, a message displays, asking you whether the Application Server parameters are correct.

c If the Application Server parameters are correct, enter y.The following displays:Configure an SMTP relay through which notifications will be sent from the BladeLogic Reporting module.

Server []:

21 Do one of the following:• If you do not want to configure an SMTP server, leave this field blank. A message

says you have chosen not to configure SMTP parameters. If that is correct, enter y.• If you want to configure an SMTP server, do the following:

a Enter the name or IP address of the host managing email. If you want to disable the SMTP Server, leave this field blank.The following displays:Port []:



b Enter the port on which an SMTP server listens for trafficThe following displays:Email From []:

c Enter the email address from which BladeLogic-generated email is sent. A message displays, asking you whether the SMTP parameters are correct.

d If the SMTP parameters are correct, enter y.If you are performing a fresh installation, a series of messages display and the installation is complete.

22 If your available RAM is greater than 1.5 GB, increase the default Tomcat heap size from 512 MB to 1/3 of your total available memory rounded up to the nearest 128 MB boundary, but no more than 1/2 of available RAM or 1024 MB maximum, as follows: Change the value of the -Xmx and -Xms values from 512 to the increased heap size in the following section of the /etc/init.d/bltomcat file:

start)CATALINA_OPTS="-Xmx512M -Xms512M -Djava.awt.headless=true -Djavax.net.ssl.trustStore=/usr/local/bl-reports/Tomcat/webapps/BladeLogicReports/WEB-INF/conf/tomcattruststore -Djavax.net.ssl.trustStorePassword=tomcattruststore -Djava.protocol.handler.pkgs=com.sun.net.ssl.internal.www.protocol"export CATALINA_OPTS

23 Navigate to the <BladeLogic_install_dir>/Reports/bin directory and enter the following script:

load_warehouse_schema.sh

The load_warehouse_schema script creates the dynamically generated portion of the reports data warehouse schema. You must perform this step before you can run the data collection scripts. See the Setting Up Data Collection Jobs for more information.

24 Restart the reports server by entering the following:/etc/init.d/bltomcat restart

To view the home page for BladeLogic Reports, enter the following address into a web browser:

https://reports_server:port_number/BladeLogicReports

where reports_server is the server that hosts BladeLogic Reports and port_number is the HTTPS port specified during installation. If BladeLogic Reports is not configured to use secure communication over SSL, enter the same URL but precede it with http instead of https, and specify the HTTP port instead of the HTTPS port.If the HTTPS port is 443 or the HTTP port is 80, it can be omitted from the URL.



Uninstalling BladeLogic Reports on WindowsUse this procedure to uninstall the reporting environment for BladeLogic Reports on a Windows system.

Procedure 1 From the Start menu, select Program Files > BladeLogic > Reports > Uninstall Reports.The installer extracts files and displays a dialog asking you if you want to uninstall BladeLogic Reports.

2 Click OK. The Uninstall Complete window announces that the uninstall is complete.

3 Click Finish.

Uninstalling BladeLogic Reports on UNIXUse this procedure to uninstall the reporting environment for BladeLogic Reports on a UNIX-style system.

Procedure 1 Log in as root.2 Navigate to the directory where you have installed BladeLogic Reports. Typically this

directory is /usr/local/bl-reports.3 Invoke the installation script by entering the following:

#./Uninstall/Uninstall



The following displays:Are you sure you wish to continue uninstalling ?

4 When you are ready to continue uninstalling, enter y.Many messages display listing the data that is deleted.

Setting Up Data Collection JobsBladeLogic Reports provides three scripts that collect data needed for various aspects of the reporting module and a related data deletion script. The scripts are stored in <install_dir>/Scripts, where <install_dir> is the location where you have installed BladeLogic Reports. You must use Configuration Manager to add these scripts to the depot as Network Shell scripts. Then you must create Network Shell Script jobs that run these scripts on a regular basis. For more information on setting up Network Shell script jobs, see the BladeLogic Users Guide.

The following sections describe the process of adding each script to the Configuration Manager depot and then incorporating it into a job:

os_config.nshcollect_agent_logs.nshpopulate_reports.nshupdate_delete_dependencies.nsh

os_config.nshThis script collects data for inventory reports. When you create and run a Network Shell Script Job based on os_config.nsh, the script creates one XML file (known as a server data file) for every server you specify in the job. The server data file contains configuration information about that server. The script copies the server data file to a directory on the reports server.

Procedure 1 Using Configuration Manager, add the os_config.nsh script to the depot as a Network Shell script. Assign any name to the script. When specifying the Script Type, choose the option that uses the runscript command. You do not have to set up any parameters when adding this script to the depot.

2 Create one or more Network Shell script jobs based on the script you added to the depot in the previous step. Use each job to identify servers or server groups against which the script should run. Schedule the jobs to run at a frequency that you prefer. BladeLogic

Note: Each server data file created by this job is named for the target server, and the file overwrites any XML files of the same name that already exist on the server.



recommends running this job no more than once a week per server. Ideally, this job should run during off peak hours.

collect_agent_logs.nshThis script collects data for Server Usage reports. The collect_agent_logs.nsh job copies data from agent logs on the target servers you specify to files on the reports server.

Procedure 1 Using Configuration Manager, add the collect_agent_logs.nsh script to the depot as a Network Shell script. Assign any name to the script. When specifying the Script Type, choose the option that uses the runscript command. You do not have to set up any parameters when adding this script to the depot.

2 Create one or more Network Shell script jobs based on the script you added to the depot in the previous step. Each job should run against target servers or server groups. From these servers, agent logs are collected. Schedule each job to run at a frequency that you prefer. BladeLogic recommends running this job against all of your servers at least once a week. Ideally, this job should run during off-peak hours.

Note: The os_config.nsh script uses a variety of commands to collect data. While it does not make any changes to target servers, it does utilize server resources. If you are running this script on production servers, you should schedule the job so it runs at a time that does not affect business activity.

Note: Run this script before you run populate_reports.nsh for the first time. In general, it is a good practice always to run collect_agent_logs.nsh before running populate_reports.nsh to ensure you are reporting on the latest server data.



populate_reports.nshThis script performs all data aggregation and populates the reporting data warehouse.

Procedure 1 Using Configuration Manager, add the populate_reports.nsh script to the depot as a Network Shell script. Assign any name to the script. When specifying the Script Type, choose the option that uses the runscript command. You do not have to set up any parameters when adding this script to the depot.

2 Create a Network Shell script job based on the script you added to the depot in the previous step. The job should run against the reporting server—that is, the server where BladeLogic Reports is installed. Schedule the job to run as frequently as you want to populate your reporting database. BladeLogic recommends running this job once a day. Ideally, this job should run during off-peak hours.

update_delete_dependencies.nshThis script checks if deleted objects have any dependencies. If a deleted object has dependencies, the script marks the dependent objects for deletion. For example, it marks the components of a deleted template for deletion. Running this script ensures that no deleted objects will be loaded into the reporting data warehouse the next time popuplate_reports.nsh is run.

Procedure 1 Using Configuration Manager, add the update_delete_dependencies.nsh script to the Depot as a Network Shell script. Assign any name to the script. When specifying the Script Type, choose the option that uses the runscript command. You do not have to set up any parameters when adding this script to the depot.

2 Create a Network Shell script job based on the script you added to the Depot in the previous step. The job should run against the reporting server—that is, the server where BladeLogic Reports is installed. This job should be run with the same permissions as the

Note: Before you run this script for the first time, you should run collect_agent_logs.nsh. In general, it is a good practice always to run collect_agent_logs.nsh before running this script to ensure you are reporting on the latest server data.

Occasionally deleted objects are loaded into the reporting data warehouse when running populate_reports.nsh. This occurs when an object has been deleted, but it has objects that are dependent on it. Those dependent objects are not deleted automatically. For example, components of a template are loaded into the data warehouse and can appear in reports even after the template is deleted. The dependent objects get loaded into the data warehouse when you run the populate_reports.nsh script unless you first mark them for deletion by running the update_delete_dependencies.nsh script as described in the following section.



role that executes the clean-up utility. This job should be run between running the clean-up utility and a subsequent popuplate_reports.nsh script. See the BladeLogic Administration Guide for more information on running the clean-up utility.


Installing and Uninstalling on Solaris, Linux,AIX, and HP-UX

This chapter describes the most common procedures for installing major components of the BladeLogic system on UNIX-style machines. • Installing All BladeLogic Components on UNIX• Installing Client Utilities (Configuration Manager, Provisioning Manager, and Network

Shell) on UNIX• Installing Only Network Shell on UNIX• Installing Only an RSCD Agent on UNIX• Uninstalling All BladeLogic Components on UNIX

Installing All BladeLogic Components on UNIXUse this procedure to install all components of a BladeLogic system on a Solaris or Linux host, including all client and middle-tier utilities, the RSCD agent, and the PXE Server. If you prefer, you can install only some of the available BladeLogic components. For example, you may not want to install Provisioning Manager. If you perform this procedure but choose not to include all components, some steps in the procedure may differ from the procedure described here.

Performing this installation creates a user called bladmin and a group called bladmin. The BladeLogic Application Server runs as the bladmin user. If a user who does not have root privileges wants to use Configuration Manager or Provisioning Manager, he or she must first be added to the bladmin group to gain access to essential configuration files.




Installing and Uninstalling on Solaris, Linux, AIX, and HP-UX 157


A standard installation of middle tier components does not set up a Network Shell Proxy Server. For detailed instructions on setting up and customizing a Network Shell Proxy Server, see the BladeLogic Administration Guide.

If the host where you are installing the Application Server has the correct version of Perl installed (version 5.6.0 for Linux and Solaris), this installation automatically installs the BladeLogic Network Shell Perl module. If you have some other version of Perl installed, the installation still installs the Perl module but it may be incompatible with your Perl executable.


for BladeLogic.The following message displays:Please choose the installation directory. [/usr/nsh]

3 Press Enter to install Configuration Manager in /usr/nsh.A message displays letting you choose a language for the installation program.

4 Enter the number representing the language you want to use for the installation. The language you choose will be the default language for the Provisioning Manager and Configuration Manager consoles, but can be changed when logging in (see Setting the Language for the Installers on UNIX for more information). A welcoming message displays, followed by a message asking you to read the third party software license agreements.


6 When you are done reading the license agreements, press Enter.A message displays, warning you that you must review text about terms and conditions for using this software.


8 Read the licensing text. If you agree with its terms, enter y.

Note: If you are installing the Application Server, you must provide database connection information to complete this procedure. If you want to set up the BladeLogic database before you begin to install software, see the chapter on databases in the BladeLogic Administration Guide.



The following displays:============== Select Installation Components =============

Server Utilities1 - RSCD Agent2 - Application Server3 - Provisioning ServerP - PXE ServerT - TFTP Server

Client Utilities4 - Network Shell5 - Configuration Manager Console6 - Provisioning Manager Console

9 - Start the installationA - Select all components

Select component

9 Enter A. A + displays next to all installation components, indicating you have chosen to install all server, client, and database utilities.

10 Enter 9. A list shows the software you have chosen to install. The following message displays:Do you wish to continue (y/n) ?

11 Enter y.Several messages display as the installation goes through various setup stages. The following message displays:Do you wish to use secure (digitally signed) logs for the RSCD Agent (y/n)?:

12 Enter Y to secure agent logs by assigning message authentication codes and sequence numbers to the current log, and by digitally signing the rolled logs. Enter N to not enable secure logging.The following message displays:Do you wish to use keystroke logs for nexec commands (y/n)?:

13 Enter Y to create keystroke logs for capturing log information for remote commands run on the agent using nexec. Enter N to not turn on keystroke logging for nexec commands.



If the installation program detects that the machine does not include a hardware device for generating random numbers, the installation program explains why BladeLogic needs random numbers and concludes with the following message:Please choose the type of random number support you wish to use. 1 - Create a .rnd file in / 2 - Do not install anything else (Usually chosen if you will add a patch) 3 - Install the PRNGDRandom number support choice [1]:

BladeLogic uses random data to encrypt communication securely. If a server includes a hardware device for generating random numbers (usually found at /dev/random or /dev/urandom) but that device is not functioning properly, the installation program advises you to install a patch to correct the problem. This is the best approach for setting up random number support on a server. The installation program also gives you two other options. You can install an entropy gathering daemon (EGD) that performs a variety of actions to generate random data in a secure manner. The BladeLogic EGD is called the Pseudo Random Number Generator Daemon (PRNGD). Alternatively, you can generate a random number seed, which provides BladeLogic with a less secure means of generating random numbers. If you wish to generate keystroke logs for nexec commands and/or secure agent logs, you must either install a patch or use PRNGD.

14 If you are prompted to make a decision about random number support, do one of the following:• Generate a file that functions as a random number seed by doing the following:

a Enter 1.A message displays, concluding with the following:Please type randomly on your keyboard until the progress bar stops. Your keystrokes will be used to generate a seed.

b Hit random keystrokes until the progress bar stops and the following message displays:Hit Return/Enter to continue:

c Press Enter.

• Skip this option by entering 2. A message warns that you must install a patch for your random number device or configure your own random number generator before you can use secure communication based on TSL/SSL in BladeLogic.

Note: If you use this method for random number support, because this is a less secure means of creating random numbers, keystroke logs will not be generated even if you entered Y in step 13. In addition, secure agent logs will fail over to normal rolling logs. If you wish to use keystroke logs and/or secure agent logs, you must either install a random number generator patch (if available) or install PRNGD.



• Install PRNGD by entering 3.Several messages display, ending with a description of user privilege mapping and the following message:Setup an initial host with root equivalency (y/n) ?

By default, users with root privileges on client machines are not granted root privileges on servers. This option lets you specify client machines where users should be granted root privileges on this server.

15 If you want to grant root privileges on this server to users on a client machine, do the following:a Enter y. The following message displays:

Hostname which will be granted initial root equivalency:

b Enter the name of a client where users with root privileges should be granted root privileges on this server.

A message shows the host you have designated, and then the following message displays:Setup a mapping for a particular client user (y/n) ?

Typically you map user names to give root privileges on the server to client users. If you do not map user privileges, BladeLogic will attempt to map a client user to an existing user on the server. If no match is found, BladeLogic maps the client user to “nobody.” However, BladeLogic does not automatically map a root user on the client to root on the server unless you make that possible for a particular client by specifying its host name, as described in step 13. If you do map a client user to a local user, the client user receives the local user’s privileges when connecting from any client machine. To implement this mapping, BladeLogic generates an entry in the users.local configuration file. For more information on user privilege mapping and the configuration files, see the BladeLogic Administration Guide.

16 If you want to map users between clients and the server, do the following:a Enter y. The following message displays:

What client user would you like to map?

b Enter a client user, such as root. The following message displays:What local user would you like to map this user to?

c Enter a local user. A message shows the mapping you have specified and asks you to confirm your choices.

d Enter y. Several messages display, ending with the following:Please select the mechanism by which the RSCD Agent should be started in the future.1 - At system bootup through "/etc/init.d/rscd" file2 - Manually (I'll do it myself)Installation type:

17 Enter 1.



Several messages display, ending with the following:Do you wish to install the default .nsh resource files into /etc/skel (y/n)?

These files make it easier to set up Network Shell as a login shell. 18 Enter y.

Several messages display, ending with the following:Please enter the path to the default webbrowser for this machine:

A web browser is necessary to view HTML-based online help.19 Enter the path to your default web browser.

The following displays:Please specify the max heap size to use for theApplication Server JVM [512-2048] (units are MBytes)Max. Heap (512-2048) [512]:

The installer sets the maximum heap size for the Java Virtual Machine (JVM). By default, it sets the maximum size to 512 MB.

20 Enter the maximum JVM heap size. Several messages display, ending with a message asking you to enter a password so a self-signed certificate can be generated. Communication between Provisioning Manager and servers being provisioned and between the Application Server and the process spawner uses SSL and requires an X.509 certificate. For more information on certificates and SSL, see the BladeLogic Administration Guide.Using this information, the installation program runs the following command:

keytool -genkey -alias blade -keyalg RSA -keysize 1024 -dname "CN=hostname" -keypass password1 -storepass password1 -keystore "<install_dir>/br/bladelogic.keystore" -validity 1000


21 Enter a password and then confirm your entry by entering it again.The following displays:Please select the BladeLogic database type:

1) Oracle2) SQL Server

Database Type [1]:

22 Enter a number corresponding to the type of database you are using for the core BladeLogic database. The following displays:Please enter the BladeLogic database connection parameters:Database Server []:



23 Provide connection parameters for the BladeLogic database by doing the following:a Enter the name of the server running the BladeLogic database.


b Enter the port the database listens on. By default a BladeLogic installation uses the following database ports.


c Enter the name of the SID of the Oracle database. Typically this name is bladelogic.The following displays:User ID []:



f If the database parameters are correct, enter y.A message displays listing the host name and IP address of this server. This information is needed to configure a connection with the TFTP server and the data store.

24 If the information identifying this server is correct, enter y.Several messages display, ending with the following:Is your DHCP server configured to run on this server (y/n)?:

If the DHCP server is located on another server, the installation program automatically configures this server to function as a DHCP proxy.

25 Answer the question about the location of the DHCP Server.


Oracle 1521

Note: You must configure the DHCP server differently, depending on whether it is installed on the same machine as the PXE Server. For more information on configuring the DHCP server, see the BladeLogic Users Guide. BladeLogic recommends that you not install the PXE Server on the same machine as the DHCP server.



The basic installation is complete. Now the installer gives you the option of configuring the Application Server by displaying the following message:Do you wish to set your DISPLAY and configure the Application Server (y/n) ?

26 Enter y and the installer prompts you to define a display variable. Enter a variable and BladeLogic’s Java-based Post-Install Configuration wizard opens.

27 Use the wizard to make your BladeLogic system operational by configuring the Application Server and setting up administrator passwords. For information on using the wizard, see Using the Post-Install Configuration Wizard.

For information on starting client utilities, see Starting Network Shell, Configuration Manager, and Provisioning Manager. See Starting the Application Server for instructions on starting the Application Server.BladeLogic recommends that you synchronize the clock on the Application Server and all client machines. Clocks should be synchronized to the minute. For example, if an Application Server is in Boston, where the time is 7:04, the clock on client machines in San Francisco should be set to 4:04. The clocks on Application Servers that are balancing their workloads should be synchronized to within a few seconds of each other.

Note: Running the Post-Install Configuration wizard requires an Xdisplay window. If you do not have Xdisplay configured, enter n and the installation is complete. Remember to configure the Application Server manually using the Application Server Administration utility, as described in the BladeLogic Administration Guide.

Note: Be aware of the following:• Agents are automatically licensed with a demonstration license valid for

only two weeks. Visit www.bladelogic.com/support.jsp to obtain and install long-term licenses for one or more agents. For general information on licensing agents, see Licensing Agents.

• If you are setting up VMware ESX servers, you must define certain properties that allow the Application Server to communicate with a web service which accesses the ESX server’s virtual infrastructure. For more information on configuring an ESX server, see the BladeLogic Users Guide.




Installing Client Utilities (Configuration Manager, Provisioning Manager, and Network Shell) on UNIX

Use this procedure to install Configuration Manager, Provisioning Manager, and Network Shell on a Solaris or Linux host.

Performing this installation creates a group called bladmin. If a user who does not have root privileges wants to use Configuration Manager or Provisioning Manager, he or she must first be added to the bladmin group to gain access to essential configuration files.


for BladeLogic.A message displays letting you choose a language for the installation program.

3 Enter the number representing the language you want to use for the installation. The language you choose will be the default language for the Provisioning Manager and Configuration Manager consoles, but can be changed when logging in (see Setting the Language for the Installers on UNIX for more information). The following message displays:Please choose the installation directory. [/usr/nsh]

4 Press Enter to install Configuration Manager in /usr/nsh.A welcoming message displays, followed by a message asking you to read the third party software license agreements.


6 When you are done reading the license agreements, press Enter.

A message displays, warning you that you must review text about terms and conditions for using this software.


8 Read the licensing text. If you agree with its terms, enter y.The following displays:============== Select Installation Components =============Server Utilities

1 - RSCD Agent2 - Application Server3 - Provisioning ServerP - PXE ServerT - TFTP Server





9 Enter 456. A + displays next to Network Shell, Configuration Manager, and Provisioning Manager, indicating you have chosen to install them.

10 Enter 9. Network Shell, Configuration Manager, and Provisioning Manager appear in a list of the software you want to install. The following message displays:Do you wish to continue (y/n) ?

11 Enter y.Several messages display as the installation goes through various setup steps. The following message displays:Do you wish to use secure (digitally signed) logs for the RSCD Agent (y/n)?:


13 Enter Y to create keystroke logs for capturing log information for remote commands run on the agent using nexec. Enter N to not turn on keystroke logging for nexec commands.The installation program tests if the machine includes a hardware device for generating random numbers and if it is functioning properly. Additional text explains why BladeLogic needs random numbers and describes the options BladeLogic provides for immediately setting up random number support. The text concludes with the following message:Please choose the type of random number support you wish to use. 1 - Create a .rnd file in / 2 - Do not install anything else (Usually chosen if you will add a patch) 3 - Install the PRNGDRandom number support choice [1]:

BladeLogic uses random data to encrypt communication securely. If a server includes a hardware device for generating random numbers (usually found at /dev/random or /dev/urandom) but that device is not functioning properly, the installation program advises you to install a patch to correct the problem. This is the best approach for setting up random number support on a server.



The installation program also gives you two other options. You can install an entropy gathering daemon (EGD) that performs a variety of actions to generate random data in a secure manner. The BladeLogic EGD is called the Pseudo Random Number Generator Daemon (PRNGD). Alternatively, you can generate a random number seed, which provides BladeLogic with a less secure means of generating random numbers. If you wish to generate keystroke logs for nexec commands and/or secure agent logs, you must either install a patch or use PRNGD.




c Press Enter.


• Install PRNGD by entering 3.Several messages display, ending with the following:Do you wish to install the default .nsh resource files into /etc/skel (y/n)?

These files make it easier to set up Network Shell as a login shell. 15 Enter y.

Several messages display, ending with the following:Please enter the path to the default webbrowser for this machine:

A web browser is necessary to view HTML-based online help.16 Enter the path to your default web browser.




Several messages display, ending with the following:Please enter the following information pertaining to the Application Server this client will connect to.

Application Server Host [localhost]:

17 Enter the name or IP address of the server running the Application Server or press Enter to accept the default value.The installation is complete. For information on starting client utilities, see Starting Network Shell, Configuration Manager, and Provisioning Manager.

Installing Only Network Shell on UNIXThis procedure describes how to install only Network Shell on a Solaris, Linux, AIX, or HP-UX host.


for Network Shell.The following message displays:Please choose the installation directory. [/usr/nsh]

3 Press Enter to install Network Shell in /usr/nsh.A message displays letting you choose a language for the installation program.

4 Enter the number representing the language you want to use for the installation. A welcoming message displays followed by a warning you that you must review text about terms and conditions for using this software.


Note: If you want to run Network Shell so it communicates with a Network Shell Proxy Server and uses BladeLogic's single sign-on capabilities, then you need to install Configuration Manager, which automatically installs Network Shell. See Installing Client Utilities (Configuration Manager, Provisioning Manager, and Network Shell) on UNIX for information on installing Configuration Manager.




1 - RSCD AgentClient Utilities

4 - Network Shell


Select component

7 Enter 4. A + displays next to Network Shell to indicate you have chosen to install it.

8 Enter 9. The following message displays:Do you wish to continue (y/n) ?

9 Enter y.The installation program tests if the machine includes a hardware device for generating random numbers and if it is functioning properly. Additional text explains why BladeLogic needs random numbers and describes the options BladeLogic provides for immediately setting up random number support. The text concludes with the following message:Please choose the type of random number support you wish to use. 1 - Create a .rnd file in / 2 - Do not install anything else (Usually chosen if you will add a patch) 3 - Install the PRNGDRandom number support choice [1]:

BladeLogic uses random data to encrypt communication securely. If a server includes a hardware device for generating random numbers (usually found at /dev/random or /dev/urandom) but that device is not functioning properly, the installation program advises you to install a patch to correct the problem. This is the best approach for setting up random number support on a server.The installation program also gives you two other options. You can install an entropy gathering daemon (EGD) that performs a variety of actions to generate random data in a secure manner. The BladeLogic EGD is called the Pseudo Random Number Generator Daemon (PRNGD). Alternatively, you can generate a random number seed, which provides BladeLogic with a less secure means of generating random numbers.






c Press Enter.• Skip this option by entering 2. A message warns that you must install a patch for

your random number device or configure your own random number generator before you can use secure communication based on TSL/SSL in BladeLogic.

• Install PRNGD by entering 3.Several messages display, ending with the following:Do you wish to install the default .nsh resource files into /etc/skel (y/n)?

These files make it easier to set up Network Shell as a login shell. This prompt is not displayed when installing on AIX.

11 Enter y.Several messages display, and the installation is complete. For more information on starting Network Shell, see Starting Network Shell, Configuration Manager, and Provisioning Manager.

Installing Only an RSCD Agent on UNIXThis procedure describes how to install only the RSCD agent on a Solaris, Linux, AIX, or HP-UX host when BladeLogic has never been installed on this machine before.

Note: BladeLogic provides a special installer for RSCD agents on VMware ESX 3.0 servers. You must run this installer to use BladeLogic's Virtualization Manager, which lets you use the capabilities of BladeLogic to manage virtual infrastructure, including configuration information for any virtual machines on an ESX server. If you install a Linux RSCD agent on an ESX 3.0 server rather than the agent specially designed for ESX servers, you will see an ESX host node when browsing that server. However, you will not be able to use the information in the ESX Host node to manage virtual infrastructure.




for the RSCD agent.The following message displays:Please choose the installation directory. [/usr/nsh]

3 Press Enter to install the RSCD agent in /usr/nsh.A message displays letting you choose a language for the installation program.

4 Enter the number representing the language you want to use for the installation. A welcoming message displays, followed by a warning you that you must review text about terms and conditions for using this software.



1 - RSCD Agent


Select component

7 Enter 1. A + displays next to RSCD Agent to indicate you have chosen to install it.

8 Enter 9. The following message displays:Do you wish to continue (y/n) ?

9 Enter y.Several messages display as the installation goes through various setup steps. The following message displays:Do you wish to use secure (digitally signed) logs for the RSCD Agent (y/n)?:


11 Enter Y to create keystroke logs for capturing log information for remote commands run on the agent using nexec. Enter N to not turn on keystroke logging for nexec commands.



The installation program tests if the machine includes a hardware device for generating random numbers and if it is functioning properly. Additional text explains why BladeLogic needs random numbers and describes the options BladeLogic provides for immediately setting up random number support. The text concludes with the following message:Please choose the type of random number support you wish to use. 1 - Create a .rnd file in / 2 - Do not install anything else (Usually chosen if you will add a patch) 3 - Install the PRNGDRandom number support choice [1]:

BladeLogic uses random data to encrypt communication securely. If a server includes a hardware device for generating random numbers (usually found at /dev/random or /dev/urandom) but that device is not functioning properly, the installation program advises you to install a patch to correct the problem. This is the best approach for setting up random number support on a server.The installation program also gives you two other options. You can install an entropy gathering daemon (EGD) that performs a variety of actions to generate random data in a secure manner. The BladeLogic EGD is called the Pseudo Random Number Generator Daemon (PRNGD). Alternatively, you can generate a random number seed, which provides BladeLogic with a less secure means of generating random numbers. If you wish to generate keystroke logs for nexec commands and/or secure agent logs, you must either install a patch or use PRNGD.




c Press Enter.





• Install PRNGD by entering 3.Several messages display, ending with a description of user privilege mapping and the following message:Setup an initial host with root equivalency (y/n) ?

By default, users with root privileges on client machines are not granted root privileges on servers. This option lets you specify clients where users should be granted root privileges on this server.

13 If you want to grant root privileges on this server to users on a client machine, do the following:a Enter y. The following message displays:

Hostname which will be granted initial root equivalency:

b Enter the name of a client where users with root privileges should be granted root privileges on this server.

A message shows the host you have designated, and then the following message displays:Setup a mapping for a particular client user (y/n) ?

Typically you map user names to give root privileges on the server to client users. If you do not map user privileges, BladeLogic will attempt to map a client user to an existing user on the server. If no match is found, BladeLogic maps the client user to “nobody.” However, BladeLogic does not automatically map a root user on the client to root on the server unless you make that possible for a particular client by specifying its host name, as described in step 13. If you do map a client user to a local user, the client user receives the local user’s privileges when connecting from any client machine. To implement this mapping, BladeLogic generates an entry in the users.local configuration file. For more information on user privilege mapping and the configuration files, see the BladeLogic Administration Guide.

14 If you want to map users between clients and the server, do the following:a Enter y. The following message displays:

What client user would you like to map?

b Enter a client user, such as root. The following message displays:What local user would you like to map this user to?

c Enter a local user. A message shows the mapping you have specified and asks you to confirm your choices.

d Enter y.



Several messages display, ending with the following:Please select the mechanism by which the RSCD Agent should be started in the future.1 - At system bootup through "/etc/rc.tcpip" file2 - Manually (I'll do it myself)3 - At system bootup through “/etc/rc.d/init.d/rscd” fileInstallation type:

15 Enter 1.The installation is complete.

For additional information on restricting access to RSCD agents, see the BladeLogic Administration Guide.

Uninstalling All BladeLogic Components on UNIXThis procedure describes how to uninstall all components of the BladeLogic system, including Configuration Manager, Network Shell, the Application Server, and the RSCD agent. Before uninstalling you may want to back up configuration files. Otherwise, those files will be deleted, and the next time you install BladeLogic you will have to recreate them.

Procedure 1 Log in as root.2 Navigate to the directory where you have installed BladeLogic components. Typically

this directory is /usr/nsh.3 Invoke the installation script by entering the following:

#./Uninstall

Note: Be aware of the following• Agents are automatically licensed with a demonstration license valid for

only two weeks. Visit www.bladelogic.com/support.jsp to obtain and install long-term licenses for one or more agents. For general information on licensing agents, see Licensing Agents.

• If you are setting up VMware ESX servers, you must define certain properties that allow the Application Server to communicate with a web service which accesses the ESX server’s virtual infrastructure. For more information on configuring an ESX server, see the BladeLogic Users Guide.

Note: Be aware of the following:• On UNIX-style servers you cannot selectively uninstall one BladeLogic

component while leaving others installed. You must uninstall all BladeLogic components.

• This procedure does not uninstall BladeLogic Reports.




A message displays letting you choose a language for the uninstall program.4 Enter the number representing the language you want to use for the uninstall program.

A message warns about the loss of configuration files. It concludes with the following:Are you sure you wish to continue uninstalling ?

The configuration files you may want to save are as follows:• /nsh/br/tpasswd.conf, which is used to generate a one-way hash for

encrypted user passwords.

• /nsh/br/config.xml, which defines behavior for the Application Server and other BladeLogic components.

• /usr/lib/rsc, which is a directory that holds several important files, including the exports, users, and secure files. These files define communication and security settings for an RSCD agent. The /rsc directory also contains license.dat, which holds licensing information for the RSCD agent.

• /usr/lib/rsc/certificate.pem, which contains the agent's self-signed certificate and the private key, which is needed to verify the integrity of secure logs.

5 When you are ready to continue uninstalling, enter y.Many messages display listing the data that is deleted.

Warning: BladeLogic strongly recommends saving tpasswd.conf. Losing this file would require you to reset all user passwords. Because this file can be used to launch an attack on your system security, BladeLogic also recommends keeping tpasswd.conf very secure at all times.

Note: The uninstall does not delete some log files that Configuration Manager creates. If you plan to re-install a newer version of Configuration Manager in the same location, be sure to completely remove all left-over files in order to avoid conflicts. The easiest way to do this is to delete all files in the installation directory.


Setting Up the Provisioning System

Before you can use Provisioning Manager to perform unattended installations on servers, you must set up all the functional components of BladeLogic’s provisioning system. Generally, you only need to perform these tasks once unless you are changing the configuration of your provisioning system.

BladeLogic uses the following provisioning technologies:• Pre-boot Execution Environment (PXE)—for provisioning Windows and Linux servers.• Sun Microsystems JumpStart software—for provisioning Solaris SPARC servers.• IBM Network Installation Manager (NIM) software—for provisioning AIX servers.• Hewlett-Packard Ignite software—for provisioning HP-UX servers.

The setup tasks for each environment are described in the following sections:• PXE Setup• JumpStart Setup• NIM Setup• Ignite Setup

PXE SetupUse the following procedure as a process flow for setting up the BladeLogic provisioning system in a PXE environment. Use the references in this procedure to obtain additional information about a particular step.

Procedure 1 Obtain access to the DHCP server that will service requests from your provisioning targets. Then make some required configuration changes, as described in Configuring the DHCP Server.

2 Install the PXE server and TFTP server.For more information, see the Installing and Uninstalling the PXE Server.

3 Install Network Shell, if not already installed. The BladeLogic provisioning process requires Network Shell on the PXE server.

4 If you are provisioning Linux operating systems, configure the TFTP server, as described in Configuring the TFTP Server.

5 Set up data stores.In Windows installations, you have the option to set up a data store on the same machine as the PXE Server. In this case, you only need to set up the account used to access the

Setting Up the Provisioning System 176


data store. However, you can set up multiple data stores on other Windows or Linux servers. For more information, see Setting Up a Data Store.

6 Stock the data store.The data store holds all operating system installation files needed for provisioning, as well as Windows plug and play drivers and BladeLogic RSCD agents. For more information, see Stocking the Data Store.

7 Set up all necessary agent installations and add them to the data store.The BladeLogic provisioning process installs an agent on all servers so they can be managed with Configuration Manager. For more information, see Preparing Agents.

8 Create boot image files.BladeLogic uses Windows PE and Gentoo Linux as boot environments for bare metal provisioning. • If you are provisioning Windows machines, you use WinPE.• If you are provisioning Linux machines, you use Gentoo Linux. Regardless of your target environment, you need to create an appropriate bootable image file. For information on how to do this, see the BladeLogic Users Guide.

9 [Optional] Set up a multi-database provisioning environment.In a large, distributed provisioning environment, you may find it more efficient to use multiple Application Servers accessing multiple databases. For information on how to do this, see Setting Up a Multiple Database Provisioning Environment.

Configuring the DHCP ServerThe BladeLogic provisioning process requires a DHCP (Dynamic Host Configuration Protocol) server, which gives the machine being provisioned an IP address and (in a single-database environment) the location of the Application Server.

This document assumes that you understand how to install and configure a DHCP server. This section, however, describes the unique configuration needed so a DHCP server can support BladeLogic’s provisioning process. BladeLogic requires you to:• Have the TFTP server and the PXE Server reside on the same machine.• Provide the IP address of the BladeLogic provisioning server.• Define a DHCP option field, which lets the machine being provisioned differentiate

between a DHCP server and proxy DHCP servers.

The process for configuring a DHCP server differs in Windows and Linux, as described in the following procedures:

Configuring a DHCP Server on WindowsConfiguring a DHCP Server on Linux



Configuring a DHCP Server on WindowsIn addition to standard configuration of the DHCP server, which includes defining a scope, you must set some scope options. Use the following procedures to configure the DHCP server on Windows:

Adding Predefined OptionsAdding Option 60

Adding Predefined Options

A standard DHCP configuration should include the definition of a scope, which sets a start and end of the range of IP addresses being distributed. This range determines the number of servers that can simultaneously access the DHCP server.

The BladeLogic provisioning process requires the following scope options:60 211212

Use this procedure to add scope options 211 and 212. Use Adding Option 60 to add scope option 60.

Procedure 1 Install DHCP, if it is not already installed. 2 Run DHCP from the Start menu by selecting Programs > Administrative Tools >

DHCP. The default server is the server where you have installed DHCP.3 If a scope is not already defined, right click on server and select New Scope. Use the

wizard to define a new scope.4 Select the default server, right-click, and select Set Predefined Options. The Predefined

Options and Values dialog opens. 5 Click Add. The Option Type dialog opens.

Note: If you are setting up a multi-database environment, do not add scope options 211 and 212. Instead, specify the IP address/hostname of the Application Server by editing config.xml, as described in Setting DHCP Scope Options.

If you are changing from a single-database environment to a multi-database environment, you must remove scope options 211 and 212 from your DHCP configuration.



6 Provide the following information:• Name—Enter bl-server.• Data Type—Select IP Address.• Code—Enter 211.

7 Click OK.8 On the Predefined Options and Values dialog, click Add again. The Option Type dialog

opens again.9 Provide the following information:

• Name—Enter bl-port.• Data Type—Select Word.• Code—Enter 212.

10 Click OK and then click OK again.11 Provide values for 211 and 212 by selecting Scope Options, right-clicking, and selecting

Configure Options.12 Under Available Options, scroll down and select option 211. Then, for IP address enter

the IP address of the BladeLogic Application Server.13 Select option 212. For Port, enter 9831, which is the port BladeLogic uses by default for

SSL communication.14 Click OK.

Adding Option 60

If the DHCP server and the PXE Server reside on the same machine, you must use this procedure to let target machines differentiate between DHCP servers and proxy DHCP servers. You do not have to perform this procedure if the DHCP server and the PXE Server reside on separate machines.

Procedure 1 From the command line on the DHCP server, enter netsh. 2 Enter dhcp.3 Enter one of the following:

• server \\servername where servername is the name of the DHCP server.• server ip_address where ip_address is the IP address of the DHCP

server.The command prompt says dhcp server.



4 Enter the following command:add optiondef 60 PXEClient STRING 0 comment=userDefined

where userDefined is any comment you want to add. This information appears in the list of scope options for the DHCP server. If your comment includes spaces, enclose the comment in quotation marks.

5 Enter the following command:set optionvalue 60 STRING PXEClient

6 To confirm the addition of the scope option, enter the following: show optionvalue all

You should see something like the following:General Option Values:OptionId: 60Option Value:Number of Option Elements = 1Option Element Type = STRINGOption Element Value = PXEClient

Configuring a DHCP Server on LinuxBladeLogic requires a Linux-based DHCP server to be running version 3.0p2 of the Internet Software Consortium (ISC) DHCP. The ISC provides a freely re-distributable version of DHCP. Earlier versions of ISC DHCP are not compatible with BladeLogic’s provisioning system.

When you configure a DHCP server on Linux, you must configure a file called dhcpd.conf. In that file you enter values needed for standard configuration of a DHCP server, including the definition of a scope, which sets a start and end of the range of IP addresses being distributed. This range determines the number of servers that can simultaneously access the DHCP server.

In addition to all standard configuration, you must include statements that are needed for the BladeLogic provisioning process. In the following example of a dhcpd.conf file, the shaded lines highlight entries that are required or recommended for BladeLogic provisioning.

allow booting;allow bootp;allow duplicates;always-broadcast on;ddns-update-style none;option bl-server code 211 = ip-address;option bl-port code 212 = unsigned integer 16;



In the shaded lines shown above:

• The option vendor-class-identifier statement is necessary if the DHCP server and the PXE Server reside on the same machine. This statement lets target machines differentiate between the DHCP server and proxy DHCP servers. Do not include this statement in the dhcpd.conf file if the DHCP server and the PXE Server reside on separate machines.

• The option bl-server statement defines an IP address for option 211. The IP address is the IP address of the BladeLogic Application Server.

• The option bl-port statement defines a port number for option 212. Generally, you should enter a value of 9831, which is the port the BladeLogic Application Server uses by default for SSL communication.

subnet 192.168.4.0 netmask 255.255.255.0{range 192.168.4.200 192.168.4.220;option subnet-mask 255.255.255.0;option routers 192.168.4.1;option domain-name-servers 10.20.21.3;option netbios-name-servers 10.20.21.3;option domain-name "netboot.customer.com";default-lease-time 2592000;max-lease-time 5184000;option vendor-class-identifier "PXEClient";option bl-server 192.168.4.100;option bl-port 9831;}

Note: If you are setting up a multi-database environment, do not add the statements for options 211 and 212. Instead, specify the IP address/hostname of the Application Server by editing config.xml, as described in Setting DHCP Scope Options.

If you are changing from a single-database environment to a multi-database environment, you must remove the statements for options 211 and 212 from dhcpd.conf.



Installing and Uninstalling the PXE ServerThe following procedures explain how to install and uninstall the PXE Server on Windows and UNIX-style machines.

Installing the PXE Server on WindowsInstalling the PXE Server on UNIXUninstalling the PXE Server on Windows

If you want to uninstall the PXE Server on UNIX, see Uninstalling All BladeLogic Components on UNIX. Currently, on UNIX-style servers you cannot selectively uninstall one BladeLogic component. You must uninstall all BladeLogic components.

Note: The PXE Server installation procedure requires you to specify information about the database you will be using for provisioning. If you plan to set up a multi-database provisioning environment, specify one database here in the PXE installation procedure, then add additional databases as described in Setting Up a Multiple Database Provisioning Environment.



Installing the PXE Server on WindowsUse this procedure to install a PXE Server and the TFTP server, which are functional components required for the BladeLogic provisioning solution.

Procedure 1 Navigate to the directory containing installation files and invoke the installation program for the PXE Server.The installer extracts the files needed for installation and displays the Welcome window.

Note: Be aware of the following:• If the PXE and DHCP servers are running on separate physical devices, the

PXE Server must be able to receive the initial DHCP packet broadcast from the target server being provisioned. If the PXE Server is on a different subnet than the target server, an IP Helper address must be added to the network router in order to forward broadcasts from the target server to the PXE Server.

• This procedure sets up a data store server on the machine where you are installing the PXE server. If you plan to use this default configuration, you must also install and license an RSCD agent on this machine (see Installing the RSCD Agent on Windows). For successful provisioning, an RSCD agent must be running on the data store server, and this agent must be licensed for use with both NSH and Configuration Manager.

• To perform this installation, you must have local Administrator privileges.• If you are using Windows Terminal Services or Citrix Presentation Server to








4 Enter your name and the name of your organization. Then click Next. The Choose Destination Location window opens.

5 Specify a directory for your installation by doing one of the following:• Accept the default location (C:\Program Files\BladeLogic\PXE) by


it to select a directory for the installation and click OK. Then click Next.The Database Type window opens.



6 Select the type of database you are using in conjunction with BladeLogic and click Next. The Database Connection Parameters window opens. The options available on this page vary, depending on the type of database you have selected.

7 Enter the following information:Database Server—The name of the server running the database.Database Port—The port the database listens on. By default a BladeLogic installation uses the following database ports.

Database Name/SID—The name of the SQL Server database or the SID of the Oracle database.User ID—A login ID for the database that BladeLogic Configuration Manager uses.Password—A password for the BladeLogic database login ID.


Oracle 1521

SQL Server 1433



8 Click Next. The Network Configuration window opens.

9 On the Network Configuration window, confirm that the Hostname and IP address of this machine are correct; this information is needed to configure a connection with the TFTP server and the data store.

10 Click Next. The DHCP Configuration window opens.

11 Specify whether the DHCP is installed on this server or another machine. If the DHCP server is located on another server, the installation program automatically configures this server to function as a DHCP proxy.

Note: You must configure the DHCP server differently, depending on whether it is installed on the same machine as the PXE Server. For more information on configuring the DHCP server, see Configuring the DHCP Server. BladeLogic recommends that you not install the PXE Server on the same machine as the DHCP server.



12 Click Next. The Virtual Directory Creation window opens.

13 On the Virtual Directory Creation window, do one of the following:• Indicate that you plan to configure a data store manually at a later time by leaving

the Name and Location fields blank.The data store is the location where you keep operating system installation files used for provisioning operating systems. By default, a data store is set up on the same machine as the PXE Server. A virtual directory is used for provisioning Linux operating systems. The installation program also sets up a network share, using the same name as the one you assign to the virtual directory. The network share is needed during the early stages of provisioning both Windows and Linux operating systems. During those stages, the provisioning processing must be able to mount a network drive to the data store.If you have previously installed the PXE Server and you leave the Name and Location fields blank in this step, the installer uses the name and location that were stored in the database during the previous installation.

• Configure a data store by doing both of the following:> For Name, enter the name that should be given to the virtual directory that

serves as a data store. The name must be 16 characters or less. > For Location, enter the directory that should be used as the location of the

virtual directory and the network share that the data store requires.

Note: The Virtual Directory Creation window does not open in certain configurations—instead the TFTP Root window opens. If the TFTP Root window opens, proceed to step 15.



The directory you identify can be a root directory, with files arranged in sub-directories beneath the root directory.

14 Click Next. The TFTP Root window opens.

15 Enter a directory or use the Browse button to specify the root directory of the TFTP server.The TFTP server must reside on the same server as the PXE Server. The TFTP server downloads the boot image needed during the provisioning process. The TFTP root directory is the location where files are read from.

Note: If you are using WinPE, you need a password to access the data store share. (Passwords are not necessary if using Gentoo or DOS.) If you are using WinPE, the machine being provisioned will need to map a drive to the location of the installation files on the data store server. BladeLogic strongly recommends that any account used for this purpose should only be granted read access to the data store. Otherwise, you are creating the potential for a dangerous security lapse.




Review the current settings to confirm that you have specified the correct installation configuration and then click Next. A progress bar indicates the progress of the installation until the InstallShield Wizard Complete window declares that the installation is complete.

17 Click Finish to complete the installation.



Installing the PXE Server on UNIXUse this procedure to install the PXE and TFTP servers, which are functional components required for the BladeLogic provisioning solution.


for BladeLogic.The following message displays:Please choose the installation directory. [/usr/nsh]

3 Press Enter to install Configuration Manager in /usr/nsh.A welcoming message displays, followed by a message asking you to read the third party software license agreements.


5 When you are done reading the license agreements, press Enter.A message displays, warning you that you must review text about terms and conditions for using this software.

6 Press Enter.

Note: If you are installing on Linux, be aware of the following:> If you are installing on Red Hat Linux, the compat-libstdc++ RPMs must





• If the PXE and DHCP servers are running on separate physical devices, the PXE Server must be able to receive the initial DHCP packet broadcast from the target server being provisioned. If the PXE Server is on a different subnet than the target server, an IP Helper address must be added to the network router in order to forward broadcasts from the target server to the PXE Server.

• For successful provisioning, an RSCD agent must be running on the PXE server, and this agent must be licensed for use with both NSH and Configuration Manager.



Licensing text displays and concludes with the following message:Do you agree to the terms of the license agreement (y for Yes) ?


1 - RSCD Agent2 - Application Server3 - Provisioning Manager ServerP - PXE ServerT - TFTP Server



8 Enter PT. A + displays next to PXE Server and TFTP Server, indicating you have chosen to install them.

9 Enter 9. A list shows the software you have chosen to install. The following message displays:Do you wish to continue (y/n) ?

10 Enter y.

Note: If you plan to set up a data store on the same machine where you install the PXE server (see Setting Up a Data Store), you must also install an RSCD agent on that machine. Thus, in this step you would enter 1PT rather than PT. The following procedure only describes how to install the PXE and TFTP Servers. If you install the RSCD agent, additional steps are necessary, as described in Installing Only an RSCD Agent on UNIX.



Several messages display.

Finally the following displays:Please select the BladeLogic database type:

1) Oracle2) SQL Server

Database Type [1]:

11 Enter a number corresponding to the type of database you are using for the core BladeLogic database. The following displays:Please enter the BladeLogic database connection parameters:Database Server []:

12 Provide connection parameters for the BladeLogic database by doing the following:a Enter the name of the server running the BladeLogic database.


b Enter the port the database listens on. By default a BladeLogic installation uses the following database ports.

One of the following displays:> For SQL Server – Database Name [bladelogic]:> For Oracle – SID []:

Note: If you are installing on Linux and one of the following is not satisfied, the installer warns that some BladeLogic components will not function until the appropriate RPM is installed.

> If you are installing on Red Hat Linux, the compat-libstdc++ RPMs must be installed. Also, the XFree86-libs or xorg-x11-libs RPMs must be installed.





Oracle 1521

SQL Server 1433



c Enter the name of the SQL Server database or the SID of the Oracle database. Typically this name is bladelogic.The following displays:User ID []:



f If the database parameters are correct, enter y.A message lists the host name and IP address of this server. This information is needed to configure a connection with the TFTP server and the data store.

13 If the information identifying this server is correct, enter y.Several messages display, ending with the following:Is your DHCP server configured to run on this server (y/n)?:

If the DHCP server is located on another server, the installation program automatically configures this server to function as a DHCP proxy.

14 Answer the question about the location of the DHCP Server.The installation is complete.

Uninstalling the PXE Server on WindowsUse this procedure to uninstall a PXE Server.

Procedure 1 From the Start menu, select Programs > BladeLogic > PXE Server > Uninstall PXE Server. A confirmation dialog displays.

2 Click OK.

Note: You must configure the DHCP server differently, depending on whether it is installed on the same machine as the PXE Server. For more information on configuring the DHCP server, see Configuring the DHCP Server.



The Uninstall Complete window announces that the uninstall is complete.

3 Click Finish.

Configuring the TFTP ServerThe TFTP server serves the boot images that are needed for a network-based installation of an operating system. As part of your initial setup, you need to create these boot images and place them on the TFTP server, as described in the BladeLogic Users Guide.

The TFTP server is installed on the same machine as the PXE Server. The BladeLogic installation program configures the TFTP server log settings by modifying the tftp.conf file, changing two settings called file_path and log_file.

For successful provisioning, an RSCD agent must be running on the TFTP server, and this agent must be licensed for use with both NSH and Configuration Manager.

If you are provisioning Linux operating systems, you must also perform the configuration procedures described in the following sections, for each operating system you will be provisioning.

Red Hat 7.3Red Hat 8.0Red Hat AS 2.1Red Hat AS 3.0Red Hat AS 4.0SuSE 8.xSuSE 8.x AMD 64SuSE 9.xSuSE 9.x AMD 64SuSE 10



Red Hat 7.3When provisioning Red Hat 7.3, copy the files initrd-everything.img and vmlinuz from the images/pxeboot directory on disk 1 of the Red Hat installation media to the tftproot/X86PC/pxelinux directory of the TFTP server. Rename those files as follows:• initrd-everything.img should be named initrd-7.3.img• vmlinuz should be named vmlinuz-7.3

Red Hat 8.0When provisioning Red Hat 8.0, copy the files initrd-everything.img and vmlinuz from the images/pxeboot directory on disk 1 of the Red Hat installation media to the tftproot/X86PC/pxelinux directory of the TFTP server. Rename those files as follows:• initrd.img should be named initrd-8.img

• vmlinuz should be named vmlinuz-8

Red Hat AS 2.1When provisioning Red Hat AS 2.1, copy the files initrd-everything.img and vmlinuz from the images/pxeboot directory on disk 1 of the Red Hat installation media to the tftproot/X86PC/pxelinux directory of the TFTP server. Rename those files as follows:• initrd.img should be named initrd-2.1.img• vmlinuz should be named vmlinuz-2.1

Red Hat AS 3.0When provisioning Red Hat AS 3.0, copy the files initrd-everything.img and vmlinuz from the images/pxeboot directory on disk 1 of the Red Hat installation media to the tftproot/X86PC/pxelinux directory of the TFTP server. Rename those files as follows:• initrd.img should be named initrd-3.img• vmlinuz should be named vmlinuz-3

Red Hat AS 4.0When provisioning Red Hat AS 4.0, copy the files initrd-everything.img and vmlinuz from the images/pxeboot directory on disk 1 of the Red Hat installation



media to the tftproot/X86PC/pxelinux directory of the TFTP server. Rename those files as follows:• initrd.img should be named initrd-4.img• vmlinuz should be named vmlinuz-4

SuSE 8.xWhen provisioning SuSE 8.x, copy the files initrd and linux from the boot/loader directory on CD1 of the SuSE installation media to the tftproot directory of the TFTP server. Rename those files as follows:• initrd should be named initrd-suse-8.x.img• linux should be named suselinux-8.x

SuSE 8.x AMD 64When provisioning SuSE 8.x AMD 64, copy the files initrd and linux from the boot/loader directory on CD1 of the SuSE installation media to the tftproot directory of the TFTP server. Rename those files as follows:• initrd should be named initrd-suse-8.x_64.img• linux should be named suselinux-8.x_64

SuSE 9.xWhen provisioning SuSE 9.x, copy the files initrd and linux from the boot/loader directory on CD1 of the SuSE installation media to the tftproot directory of the TFTP server. Rename those files as follows:• initrd should be named initrd-suse-9.x.img• linux should be named suselinux-9.x

SuSE 9.x AMD 64When provisioning SuSE 9.x AMD 64, copy the files initrd and linux from the boot/loader directory on CD1 of the SuSE installation media to the tftproot directory of the TFTP server. Rename those files as follows:• initrd should be named initrd-suse-9.x_64.img• linux should be named suselinux-9.x_64



SuSE 10When provisioning SuSE 10, copy the files initrd and linux from the boot/loader directory on CD0 of the SuSE installation media to the tftproot directory of the TFTP server. Rename those files as follows:• initrd should be named initrd-suse-10.1.img• linux should be named suselinux-10.1

In addition, if you have set up the data store on a Windows system where IIS and .Net Framework are installed, you need to remove the file associations with .cs files in IIS as follows:

Procedure 1 From the Start menu, select Programs > Administrator Tools > IIS Manager.2 From IIS Manager, select Default Web Sites > datastore. Right click and select

Properties. The Datastore Properties window displays.

3 On the Virtual Directory tab, click Configurations. The Application Configuration window opens.

4 Remove the application mappings for .cs files.5 From Services, restart the IIS service.

Setting Up a Data StoreUse this procedure to set up a data store. It describes in general terms how to set up a data store on a Windows or Linux server. When you install the PXE Server on Windows, the installation program gives you the option to set up a default data store on the PXE Server. However, you are not limited to this approach. You can set up multiple data stores on Windows or Linux servers.

If you are provisioning many devices simultaneously, using multiple data stores can potentially reduce network traffic. During the provisioning process, most network traffic occurs between the device being provisioned and the data store. Using multiple data stores can reduce the possibility of a bottleneck. Additionally, if you are provisioning devices on different network segments, you can place a data store on each segment, thereby substantially reducing network traffic.

Typically Provisioning Manager requires two types of access to the data store: Windows directory sharing and HTTP access. However, these requirements can vary, depending on whether you are provisioning Windows or Linux to a bare metal server. In all cases the early stages of the provisioning process use an image file. To accommodate this, the installation must be able to map a drive to the data store, which requires the presence of SMB on the data store server. (SMB is native to Windows. An SMB emulator such as Samba is typically used for Linux). If you are installing the Linux operating system to a bare metal machine, you also



need to provide HTTP access to the data store (such as Apache on Linux or IIS on Windows) because the Linux installers run over HTTP.

Procedure 1 On the machine that will function as a data store server, set up a directory structure that will contain all of your operating system installers and other related files.By default, the PXE Server installation program sets up data store directory on the same machine as the PXE Server. The directory is named pxestore and it resides directly under the PXE Server’s install directory.

2 Set up directory sharing by doing one of the following:• If the data store server is a Windows machine, use Windows to set up sharing with

the data store directory. The share should allow read-only access.• If the data store server is a Linux machine, use Samba to set up sharing with the data

store directory structure. The share should allow read-only access.If you are using WinPE, you need a password to access the data store share. Passwords are not necessary if using Gentoo or DOS. If you are using WinPE, the machine being provisioned will need to map a drive to the location of the installation files on the data store server. You must enable this account. You can use properties in Provisioning Manager to provide the connection information needed to access other data stores. For more information on defining Provisioning Manager properties and assigning properties to a system package being used to provision a server, see the BladeLogic Users Guide.

3 If you are provisioning the Linux operating system, set up HTTP access by doing one of the following:• If the data store server is a Windows machine, use IIS to define a virtual directory

that corresponds to the data store directory structure. Use web sharing to grant read-only access to this virtual directory.By default the PXE Server installation program sets up web sharing with an IIS virtual directory that is assigned the same name as the network share, pxestore.

• If the data store server is a Linux machine, set up HTTP read-only access to the data store directory structure.

To facilitate troubleshooting, you can optionally set up HTTP access so it allows directory browsing. However, this makes your data store configuration less secure.

Note: ESX 2.5.x only: The data store needs to have NFS access. For this, you need to export the data store as an NFS share. This requires an NFS server on the data store server.

Warning: BladeLogic strongly recommends that any account used to share access to the data store should be limited to read-only access. Otherwise, you are creating the potential for a dangerous security lapse.



4 If the data store server is a Windows machine, and you plan to use this machine to provision Windows operating systems, configure the security settings as follows:a From the Start menu, select Settings > Control Panel. Double-click

Administrative Tools, double-click Local Security Policy. Under Security Settings, click Local Policies and double-click Security Options.

b Set the following policies as shown:

5 Install an RSCD agent on the data store server using one of the following procedures:• Installing the RSCD Agent on Windows• Installing Only an RSCD Agent on UNIXTo successfully provision servers, an RSCD agent must be running on the data store server.

6 Stock the data store with the installers and other files you expect to use.For more information see Stocking the Data Store.

Stocking the Data StoreOnce a data store server is set up, it must be stocked. A data store holds several categories of information:• Operating system installers necessary for provisioning a server. • Files needed to support Windows plug and play drivers.• Files and other information needed to install BladeLogic RSCD agents after the

operating system has been installed.

The following procedures describe how to set up access to a data store and then stock it with operating system installation files and drivers:

Windows Operating SystemsRed Hat Linux Operating SystemSuSE 8.x Operating SystemSuSE 8.x AMD 64 Operating SystemSuSE 9.x Operating SystemSuSE 9.x AMD 64 Operating SystemSuSE 10 Operating SystemESX Server

Policy Security Setting

Network security: Do not store LAN manager hash value on next password change

Disabled

Network security: LAN Manager authentication level Send LM & NTLM responses



Windows DriversAll Operating Systems: fdisk.exe

See Preparing Agents for information on setting up agents that can be installed after the operating system is provisioned.

Windows Operating SystemsUse this procedure to copy the operating system installation files for the following Windows operating systems to a data store:

Windows 2000 ServerWindows 2000 Advanced ServerWindows 2003 ServerWindows 2003 Enterprise Server

You must create separate directories for each operating system.

This procedure also includes directions for integrating a service pack into the operating system installation files. If you integrate a service pack, the operating system you provision onto servers will include all updates included in the service pack.

Procedure 1 Create a directory in a data store to hold the Windows operating system installation files. For example, if the root directory of the data store is C:\Program Files\BladeLogic\pxestore, you can use the command line to enter the following:

mkdir C:\Program Files\BladeLogic\pxestore\win2k\i386

The win2k directory can be named anything. Do not rename the i386 directory.2 Copy the contents of the i386 directory on the Windows product CD to the i386

directory you have created in the data store.3 To integrate a service pack into the operating system installation files, do the following:

a Create a directory to temporarily hold the service pack files. For example, you could create a directory called C:\ExtractedFiles.

b Using the Windows service pack CD, extract the files from the service pack by entering

D:\W2ksp2.exe /x

where D: is the drive running the service pack CD.c When prompted for a directory to place the extracted files, enter the directory you

created in step a. d After the service pack files are extracted, enter the following:

C:\ExtractedFiles\i386\Update\Update.exe-s:C:\Program Files\BladeLogic\pxestore\win2k



where C:\Program Files\BladeLogic\pxestore\win2k\i386 is the directory you created in the first step to store the i386 directory.

Red Hat Linux Operating SystemUse this procedure to copy the operating system for Red Hat Linux from installation media to a data store. The following procedure provides a generic description using the value <RHRelease>. When installing a version of Red Hat, replace <RHRelease> with the appropriate Red Hat release, such as redhat80 or rhas30.

Procedure 1 Create a directory in a data store to hold the Red Hat operating system installation files. For example, if the root directory of the data store is C:\Program Files

\BladeLogic\pxestore, use the command line to enter the following:mkdir C:\Program Files\BladeLogic\pxestore\<RHRelease>

2 Using the first disc of the Red Hat product CD, copy the RedHat directory, including all sub-directories, to the <RHRelease> directory. This creates a directory structure like the following:C:\Program Files\BladeLogic\pxestore\<RHRelease>\RedHat\RPMSC:\Program Files\BladeLogic\pxestore\<RHRelease>\RedHat\baseC:\Program Files\BladeLogic\pxestore\<RHRelease>\RedHat \TRANS.TBL

3 Insert all other discs associated with the Red Hat installation and copy the contents of the RedHat\RPMS directories on those disks to: C:\Program Files\BladeLogic\pxestore\<RHRelease>\RedHat\RPMS

SuSE 8.x Operating SystemUse this procedure to copy the operating system for SuSE 8.x from installation media to the data store.

Procedure 1 Create a directory in the data store to hold the SuSE operating system installation files. For example, if the root directory of the data store is C:\Program Files\BladeLogic\pxestore, you can use the command line to enter the following:

mkdir C:\Program Files\BladeLogic\pxestore\suse80

2 Make three subdirectories under the suse80 directory. Name the directories CD1, CD2, and CD3.

3 Copy the contents of the SuSE United Linux For SuSE Enterprise Server 8 CD1 to the suse80\CD1 directory. Copy the contents of the SuSE United Linux For SuSE

Note: To integrate service pack files into the operating system installation files using this procedure, you must be running the Windows 2000 operating system.



Enterprise Server 8 CD2 to the suse80\CD2 directory. Copy the contents of the SuSE United Linux For SuSE Enterprise Server 8 CD3 to the suse80\CD3 directory.

4 Remove the file info.txt from the directory CD1\media.1. 5 Make sure that when you use the Configurations window to identify the location of

operating system installer packages, you enter a path relative to the base directory of the data store. The path should include the directory CD1.For example, if the CD directories are located in C:\Program Files\BladeLogic\pxestore\suse80, and the base directory of the data store is C:\Program Files\BladeLogic\pxestore, you would enter suse80\CD1.See the BladeLogic Users Guide for more information on identifying the location of operating system installer packages.

SuSE 8.x AMD 64 Operating SystemUse this procedure to copy the operating system for SuSE 8.x AMD 64 from installation media to the data store.


mkdir C:\Program Files\BladeLogic\pxestore\suse80_64

2 Make three subdirectories under the suse80_64 directory. Name the directories CD1, CD2, and CD3.

3 Copy the contents of the SuSE United Linux For SuSE Enterprise Server 8 CD1 to the suse80_64\CD1 directory. Copy the contents of the SuSE United Linux For SuSE Enterprise Server 8 CD2 to the suse80_64\CD2 directory. Copy the contents of the SuSE United Linux For SuSE Enterprise Server 8 CD3 to the suse80_64\CD3 directory.

4 Copy the suse directory from the SuSE Linux Enterprise Server for AMD 64 CD 1 to the suse80_64\CD1 directory.Note that this step asks you to copy a directory from different installation media than the previous step.

5 Make sure that when you use the Configurations window to identify the location of operating system installer packages, you enter a path relative to the base directory of the data store. The path should include the directory CD1.For example, if the CD directories are located in C:\Program Files\BladeLogic\pxestore\suse80, and the base directory of the data store is C:\Program Files\BladeLogic\pxestore, you would enter suse80_64\CD1.



See the BladeLogic Users Guide for more information on identifying the location of operating system installer packages.

SuSE 9.x Operating SystemUse this procedure to copy the operating system for SuSE 9.x from installation media to the data store.


mkdir C:\Program Files\BladeLogic\pxestore\suse90

2 Make five subdirectories under the suse90 directory. Name the directories CD1, CD2, CD3, CD4, and CD5.

3 Copy the contents the SuSE product CDs to those directories as follows:• Copy the contents of disc 2 to suse90\CD1.• Copy the contents of disc 3 to suse90\CD2.• Copy the contents of disc 4 to suse90\CD3.• Copy the contents of disc 5 to suse90\CD4.• Copy the contents of disc 6 to suse90\CD5.Note that the contents of each disc are not copied to a directory of the same name.

4 Copy the boot directory from compact disc CD1 to the same location in the directory called CD1, choosing to overwrite all files.

5 Copy the yast directory from compact disc CD1 to the same location in the directory called CD1, choosing to overwrite all files.

6 Copy the suse/i586 directory from compact disc CD1 to the same location in the directory CD1, choosing to overwrite all files.

7 Copy the suse/setup/descr directory from compact disc CD1 to the same location in the directory called CD1, choosing to overwrite all files.

8 Make sure that when you use the Configurations window to identify the location of operating system installer packages, you enter a path relative to the base directory of the data store. The path should include the directory CD1.For example, if the CD directories are located in C:\Program Files\BladeLogic\pxestore\suse90, and the base directory of the data store is C:\Program Files\BladeLogic\pxestore, you would enter suse90\CD1.See the BladeLogic Users Guide for more information on identifying the location of operating system installer packages.



SuSE 9.x AMD 64 Operating SystemUse this procedure to copy the operating system for SuSE 9.x AMD 64 from installation media to the data store.



2 Make five subdirectories under the suse90 directory. Name the directories CD1, CD2, CD3, CD4, and CD5.

3 Copy the contents the SuSE product CDs to those directories as follows:• Copy the contents of disc 2 to suse90_64\CD1.• Copy the contents of disc 3 to suse90_64\CD2.• Copy the contents of disc 4 to suse90_64\CD3.• Copy the contents of disc 5 to suse90_64\CD4.• Copy the contents of disc 6 to suse90_64\CD5.Note that the contents of each disc are not copied to a directory of the same name.

4 Copy the boot directory from compact disc CD1 to the same location in the directory called CD1, choosing to overwrite all files.

5 Copy the yast directory from compact disc CD1 to the same location in the directory called CD1, choosing to overwrite all files.

6 Copy the suse/setup/descr directory from compact disc CD1 to the same location in the directory called CD1, choosing to overwrite all files.

7 Copy the suse/x86_64 directory from compact disc CD1 to the same location in the directory called CD1, choosing to overwrite all files.

8 Make sure that when you use the Configurations window to identify the location of operating system installer packages, you enter a path relative to the base directory of the data store. The path should include the directory CD1.For example, if the CD directories are located in C:\Program Files\BladeLogic\pxestore\suse90_64, and the base directory of the data store is C:\Program Files\BladeLogic\pxestore, you would enter suse90_64\CD1.See the BladeLogic Users Guide for more information on identifying the location of operating system installer packages.



SuSE 10 Operating SystemUse this procedure to copy the operating system for SuSE 10 from installation media to the data store.



2 The SuSE 10 installation media can be either a DVD or a set of CDs:> If you have a DVD, continue at Copying From a DVD.> If you have a set of CDs, continue at Copying From CDs.

3 If you are using IIS, you must delete the package.cs file as follows:a In the Provisioning Manager console, from the Tools menu, select Property

Dictionary.b In the left hand Property Class Navigation panel, open the Built-in Property

Classes folder, then open the DataStore sub-folder.

Copying From a DVD1 If you have a DVD, make one subdirectory under the suse_10 directory. Name this

directory DVD.2 Copy the contents of the SuSE product DVD into the newly created DVD directory.3 Make sure that when you use the Configurations window to identify the location of

operating system installer packages, you enter a path relative to the base directory of the data store. The path should include the DVD directory.For example, if the directories are located in C:\Program Files\BladeLogic\pxestore\suse10_1, and the base directory of the data store is C:\Program Files\BladeLogic\pxestore, you would enter suse10_1\DVD.See the BladeLogic Users Guide for more information on identifying the location of operating system installer packages.

Copying From CDs1 If you have a set of CDs, make the same number of subdirectories under the suse10_1

directory as there are CDs in the set. Name the directories CD0, CD1, CD2, CD3, CD4, and so on.



2 Cd to the suse10_1 directory.3 Copy the entire contents of each SuSE product CD to its corresponding directory.4 Make sure that when you use the Configurations window to identify the location of

operating system installer packages, you enter a path relative to the base directory of the data store. The path should include the directory CD1.For example, if the CD directories are located in C:\Program Files\BladeLogic\pxestore\suse10_1, and the base directory of the data store is C:\Program Files\BladeLogic\pxestore, you would enter suse10_1\CD1.See the BladeLogic Users Guide for more information on identifying the location of operating system installer packages.

ESX ServerUse this procedure to copy the installer files for VMware ESX Server from the ESX installation media to a data store. The following procedure provides a generic description using the value <VMRelease>. When installing a version of ESX, replace <VMRelease> with the appropriate VMware release, such as vmware2 or vmware3.

The procedure varies depending on whether your data store is on a UNIX-style system or on a Windows system:

If Data Store is on UNIX-style SystemIf Data Store is on Windows System

If Data Store is on UNIX-style SystemProcedure 1 Copy installation files to the data store, as described in Copying Installation Files to the

Data Store.

2 Copy image files to the TFTP server, as described in Copying Image Files to the TFTP Server.

3 Add wget to the RPM bundle, as described in Adding wget to the VMware RPM Bundle.

Copying Installation Files to the Data Store1 Create a directory in the data store to hold the ESX operating system installation files.

For example, if the root directory of the data store on a Linux box is:/var/installs/pxestore

use the command line to enter the following:mkdir /var/installs/pxestore/VMware/<VMRelease>



2 Copy the entire contents from the installation CD into this <VMRelease> folder. This creates a directory structure like this:/var/installs/pxestore/VMware/<VMRelease>/VMware/RPMS

/var/installs/pxestore/VMware/<VMRelease>/VMware/base

/var/installs/pxestore/VMware/<VMRelease>/VMware/TRANS.TBL

Copying Image Files to the TFTP Server1 Copy the following files from the installation CD:

/images/pxeboot/initrd.img

/images/pxeboot/vmlinuz

2 Place these files in the \x86PC\pxelinux directory under <tftproot>, for example:\\pxeserver\\BladeLogic\PXE\tftproot\X86PC\pxelinux

Adjust this location depending on the location of your <tftproot> directory.

Adding wget to the VMware RPM Bundle

The VMware RPM bundle does not install wget by default. Provisioning Manager needs wget to download the RSCD agent installer and some other supporting files, so you need to add wget to the bundle.1 Download a copy of wget-1.10.1-1.30E.1.i386.rpm and place it in the VMware/RPMS/

directory in the data store.2 Add the following <rpm> line to the file VMware/RPMS/descriptor.xml:

...

<rpmlist>

...

<rpm arch="i386" rel="1.30E.1" ver="1.10.1">wget</rpm>

</rpmlist>

3 Add the following <packagereq> line to the file VMware/base/comps.xml:...

</packagelist>

...

<packagereq type="mandatory">wget</packagereq>

</packagelist>

4 Modify the hdlist.a First, create a symbolic link in the VMware directory. To do this, run the following

commands:cd /var/installs/pxestore/VMware/<VMRelease>/

ln -s VMware RedHat

b Download and install the package anaconda-runtime-9.1-8.RHEL on the data store server.



c Run the following genhdlist command (all on one line):/usr/lib/anaconda-runtime/genhdlist /var/installs/pxestore/VMware/<VMRelease>

If Data Store is on Windows System

Before you begin: Although your data store is on a Windows system, this procedure requires access to a UNIX-style system. Therefore, make sure you have access to a UNIX-style system before you start this procedure.

Procedure 1 Copy installation files to the data store, as described in Copying Installation Files to the Data Store.

2 Copy image files to the TFTP server, as described in Copying Image Files to the TFTP Server.

3 Add wget to the RPM bundle, as described in Adding wget to the VMware RPM Bundle.

Copying Installation Files to the Data Store1 Create a directory in the data store to hold the ESX operating system installation files.

For example, if the root directory of the data store on a Windows box is:E:\pxestore

use the command line to enter the following:cd E:\pxestore

mkdir VMware

cd VMware

mkdir <VMRelease>

This creates a directory structure like this:E:\pxestore\VMware\<VMRelease>

2 Copy the entire contents from the installation CD into this <VMRelease> folder. This creates a directory structure like this:E:\pxestore\VMware\<VMRelease>\VMware\RPMS

E:\pxestore\VMware\<VMRelease>\VMware\base

E:\pxestore\VMware\<VMRelease>\VMware\TRANS.TBL

Copying Image Files to the TFTP Server1 Copy the following files from the installation CD:

/images/pxeboot/initrd.img

/images/pxeboot/vmlinuz

2 Place these files in the \x86PC\pxelinux directory under <tftproot>, for example:\\pxeserver\\BladeLogic\PXE\tftproot\X86PC\pxelinux

Adjust this location depending on the location of your <tftproot> directory.



Adding wget to the VMware RPM Bundle

The VMware RPM bundle does not install wget by default. Provisioning Manager needs wget to download the RSCD agent installer and some other supporting files, so you need to add wget to the bundle.1 Download a copy of wget-1.10.1-1.30E.1.i386.rpm and place it in the VMware\RPMS

directory in the data store.2 Add the following <rpm> line to the file VMware\RPMS\descriptor.xml:

...

<rpmlist>

...

<rpm arch="i386" rel="1.30E.1" ver="1.10.1">wget</rpm>

</rpmlist>

3 Add the following <packagereq> line to the file VMware\base\comps.xml:...

</packagelist>

...

<packagereq type="mandatory">wget</packagereq>

</packagelist>

4 Modify the hdlist.a Find a UNIX-style system.b Copy the ESX installation files to that UNIX-style system, as described in Copying

Installation Files to the Data Store.c On the UNIX-style system, create a symbolic link in the VMware directory. To do

this run the following commands:cd /var/installs/pxestore/VMware/<VMRelease>/

ln -s VMware RedHat

d On the UNIX-style system, download and install the package anaconda-runtime-9.1-8.RHEL.

e Run the following genhdlist command (all on one line):/usr/lib/anaconda-runtime/genhdlist

/var/installs/pxestore/VMware/<VMRelease>

f Now return to the Windows data store system and create a directory named RedHat, located here:E:\pxestore\VMware\<VMRelease>\RedHat

g Copy the entire contents of the /var/installs/pxestore/VMware/<VMRelease>/VMware directory on the UNIX-style system into the RedHat directory on the Windows system.



The directory structure will then look like this:E:\pxestore\VMWare\<VMRelease>\VMware\RPMS

E:\pxestore\VMWare\<VMRelease>\VMware\base

...ANDE:\pxestore\VMware\<VMRelease>\RedHat\RPMS

E:\pxestore\VMware\<VMRelease>\RedHat\base

...

Windows DriversWhile Windows installation files (that is, the contents of the i386 directory) can be used to install the Windows operating system on various types of hardware, Windows drivers are often specific to a particular hardware configuration. BladeLogic recommends you store hardware-specific drivers in unique locations under the root directory of the data store. BladeLogic also recommends that you create a different system package for each hardware configuration you want to provision.

Unattended installations for Windows use special directories called $OEM$ to access hardware-specific drivers. When setting up the data store, create a separate $OEM$ directory for each different hardware configuration you plan to provision. For example, you could set up a directory structure like the following:

When you create a system package for Windows, you should specify the path to hardware-specific drivers using the Path to $OEM$ directory field on the Computer Settings panel in Provisioning Manager. For example, if you set up a directory structure like the one shown above, you could enter the following in Path to $OEM$ directory:

drivers/Compaq

The path you enter is relative to the root directory of the data store. Do not include the $OEM$ directory in the path.

See Plug and Play Drivers for instructions on setting up a data store for Windows plug and play drivers. See SCSI and RAID Controller Drivers for instructions on setting up a data store for SCSI or RAID controller drivers.



Plug and Play Drivers

Every time the Windows operating system boots, it loads the drivers for the server’s plug and play (PnP) hardware. Windows searches for these drivers in all of the locations specified in its PnP driver path. In order for Windows to find those drivers, the provisioning process must store the correct files on the server’s file system. The provisioning process must also include the location of those files in the server’s PnP driver path.

To ensure that plug and play drivers are stored in the server’s file system during provisioning, use the $OEM$ directory and another special directory called $1. The $1 directory represents the drive and partition of the server you are provisioning. The provisioning process copies any files or directories that exist under $OEM$\$1 to the target server.

To provide drivers to the text-based section of the Windows installer, you need to create a folder called TEXTMODE below $OEM$. This new TEXTMODE folder should be set up at the same level as the $1 directory. It must contain at least one file though this file can contain anything and can be of any size.

When setting up the data store, use a directory structure similar to the one shown below for plug and play drivers:

If your directory structure is set up like the one shown above and the Path to $OEM$ directory field in the Computer Settings panel of a Windows system package is set to drivers/Compaq, the provisioning process copies the display and network directories to the C: directory of the target server.

In order for Windows to know where to look for the drivers that you have copied to the C: directory, the paths to these locations must be appended to the Windows PnP driver path. The PnP driver path is a semicolon-delimited list of paths relative to the C: directory. When defining a Windows system package, use the PnP driver path field on the Computer Settings panel to specify the paths you want appended to the Windows PnP driver path. For example, if the data store is structured like the one shown above, and the Path to $OEM$ directory field in the Computer Settings panel of a Windows system package is set to drivers/Compaq, the PnP driver path field should be:

display;network



For more information on using the Computer Settings panel when defining a Windows system package, see the BladeLogic Users Guide.

Example

Here is an example of how you might create additional folders for PnP and textmode drivers.

Assume the following:• The data store instance resides at E:\Pxestore• The drivers path on the data store is at: E:\Pxestore\drivers • The individual driver sets are broken down by manufacturer and server model type• The vendor name is Vendor1 and the server model is Model1.

In this example, the drivers for the server model “Model1” reside at:E:\Pxestore\drivers\Vendor1\Model1\

Also, the value for the Path to $OEM$ directory field in the Computer Settings panel in the Provisioning Manager console will simply be:

drivers\Vendor1\Model1

because this path is always relative to the data store being used.

For PnP drivers,

Create a folder called $1 below the $OEM$ folder and place the PnP drivers in it. You can also separate individual driver sets by placing them in their own subfolders below $1. For example,

E:\Pxestore\drivers\Vendor1\Model1\$OEM$\$1\lan

E:\Pxestore\drivers\Vendor1\Model1\$OEM$\$1\video

E:\Pxestore\drivers\Vendor1\Model1\$OEM$\$1\audio

Specify lan;video;audio in the PnP driver path field in the Computer Settings panel. This points the PnP drivers to the individual subfolders below $1. Each of these subfolders will be copied to the same drive and partition in which Windows is being installed.

For textmode drivers (typically SCSI, SATA, and RAID disk drivers),

Create a folder called textmode below the $OEM$ folder and place any driver sets required for the textmode section of the Windows installer in it. For example,

E:\Pxestore\drivers\Vendor1\Model1\$OEM$\TEXTMODE

These drivers will also need to be referenced in the [MassStorageDrivers] and [OEMBootFiles] sections of the unattend.txt file. See the BladeLogic Users Guide for more information.



SCSI and RAID Controller Drivers

During an interactive installation of the Windows operating system, a system prompt asks you to insert a floppy containing SCSI or RAID controller drivers. An unattended Windows installation, however, must provide SCSI and RAID controller drivers by storing them in a directory called TEXTMODE under the $OEM$ directory. Obtain SCSI and RAID controller drivers, along with another essential file called txtsetup.oem, from your hardware manufacturer.

If your hardware configuration requires SCSI or RAID controller drivers, create a directory structure like the one shown below. Store the SCSI and RAID controller drivers as well as the txtsetup.oem file in the TEXTMODE directory. The TEXTMODE directory should not have any subdirectories.

When defining a Windows system package that provisions a server with SCSI or RAID controller drivers, you must use the Unattended Entries shortcut in Advanced Options to provide essential driver information, as described in the BladeLogic Users Guide.

All Operating Systems: fdisk.exeFor DOS-based provisioning, you need to place a copy of the fdisk.exe program in the root directory of all your data stores.

You can download this program from:

http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/dos/fdisk/fdisk121.zip

Preparing AgentsUse this procedure to set up agents so they can be installed as part of the BladeLogic provisioning process.

The provisioning process installs an RSCD agent on each machine being provisioned. After installing the agent on a server, the provisioning process also registers the agent and adds the server to the list of managed servers under Available Servers in Configuration Manager. In this way you can seamlessly move from provisioning servers with Provisioning Manager to managing servers with Configuration Manager and Network Shell.



Procedure 1 For each platform you are provisioning (for example, Linux 7.3 or Windows 2000 servers), store the installation program for the appropriate RSCD agent in the data store. The data store is where you store sets of operating system installation files and other files used for provisioning operating systems. For example, if the root directory of the data store is C:\Program Files\BladeLogic\pxestore, then you might store agent installation programs in a directory called C:\Program Files\BladeLogic\pxestore\AgentInstalls.

2 For each platform you are provisioning, create a response file for the installation of the RSCD agent and store the response file in the data store. For Windows systems, the response file is required. For Linux systems you can optionally create the response file if you want to override the agent installation defaults.For information on how to create response files when installing agents, see Creating a Response File for Windows Agents and Creating a File of UNIX Installation Defaults.

3 Identify the location of the agent installation programs and response files using the System Packages tab on the Configurations window in Provisioning Manager.For more information on this procedure, see the BladeLogic Users Guide.

Note: The installation program for the RSCD agent must be named rscd.exe for Windows, rscd.sh for UNIX-style platforms, and the (optional) silent installation file must be named rscd.iss.



Setting Up a Multiple Database Provisioning EnvironmentIn a large, distributed provisioning environment, you may find it more efficient to use multiple Application Servers, where each Application Server connects to a different database.

For example, consider the following implementation:

Figure 1: Sample Multi-Database Implementation

Use this procedure to configure a multi-database environment for provisioning.

Procedure 1 When you installed the PXE server (Installing and Uninstalling the PXE Server), you provided information about one of the databases you are using.The database you specified during the PXE server installation process is the default database. For example, referring to the diagram in Sample Multi-Database Implementation, assume that when you installed the PXE server, you specified Database1; therefore Database1 is your default database.

Device Group 1

Application Server 1 Windows Provisioning

Database 1

Application Server 3 International (Windows

and Linux) Provisioning

Application Server 2 Linux Provisioning

Database 2 Database 3

MAC Addr #1MAC Addr #2MAC Addr #3

PXE Server

Will be provisioned by Application Server 1

Device Group 2



Device Group 3





You need to provide information about the additional, non-default databases by editing the PXE server’s config.xml file, as described in Adding Additional Databases. Again, referring to the diagram in Sample Multi-Database Implementation, you would need to add information about Database2 and Database3.

2 Associate each database with an Application Server and port. You do this by editing config.xml, as described in Setting DHCP Scope Options.If you are upgrading from a single-database environment to a multi-database environment, you need to disable DHCP options 210 and 211. For more information, see Configuring the DHCP Server.

3 Specify that you are using a multi-database provisioning environment by editing pxe.conf, as described in Specifying Multi-Database Environment.

4 For performance reasons, the PXE server maintains a cache of imported devices and their associated databases. Yo can optionally set cache options by editing pxe.conf, as described in [Optional] Modifying Cache Options.

5 Stop and restart the PXE server. For information on how to do this, see the BladeLogic Users Guide.

6 In a multi-database environment, when devices boot up and are connected to the network, they do not automatically appear as imported devices within the Provisioning Manager console. Instead, you must use the Provisioning Manager console to manually import devices before they boot up or are connected to the network.For example, using the diagram at the start of this section, you would need to use the Provisioning Manager console connected to Application Server 1 to manually add the devices in Device Group 1.Once the Provisioning Manager console(s) are up and running, manually import all the devices you want to provision.For information on manually importing devices, see the BladeLogic Users Guide.

Editing the PXE Server’s config.xmlA config.xml file resides on the PXE server. You need to edit this PXE server config.xml file to specify information about your non-default databases and about DHCP scope options.

Adding Additional DatabasesSetting DHCP Scope Options



Adding Additional Databases

Each time you install an Application Server, the installation process creates a config.xml file for that Application Server. This config.xml file contains a <Database> element that contains information about the database associated with the Application Server.

By default, the Application Server’s config.xml resides at:<install_dir>/br/config.xml

In summary, you need to:• Access the config.xml file on each Application Server associated with a non-default

database.The database you specified when you installed the PXE server is the default database. All other databases are non-default databases. Continuing with the example started earlier in this discussion, and referring to the diagram in Sample Multi-Database Implementation, the non-default databases are Database2 and Database3. Therefore, you would need to access the config.xml file on Application Server 2 and the config.xml file on Application Server 3.

• Copy each <Database> element.• Add a name attribute to your copies of each <Database> element.• Paste these <Database> elements into the config.xml file on the PXE server.

These tasks are described in detail in the following procedure.

Procedure 1 Using a text editor, open the config.xml that contains information about a non-default database. Continuing with the example above, you would open config.xml on Application Server 2.

2 Search for the <Database> element.

3 Copy the entire <Database> element and store it in a text file on a thumb drive, file server, or other convenient storage mechanism. Assume you name this temporary text file:db_info.txt

4 Open db_info.txt and edit your newly added <Database> element, so that its first line contains a name attribute whose value is any descriptive string you choose. This string should describe this particular database. Continuing with this example, where this <Database> element describes Database2, your first line might look like this:<Database name="db2">

5 Repeat the preceding steps for each non-default database—go to each Application Server, open config.xml, copy and edit each <Database> section.



When you are finished, your db_info.txt file should contain a <Database> element for each non-default database. Each of these <Database> elements should now contain a name element as well.Continuing with this example, db_info.txt would contain just two <Database> elements—one for Database2 and one for Database3. The contents of db_info.txt might look something like this:

<Database name="db2"><ConnectionString>jdbc:sqlserver://localhost:1433;DatabaseName=Database2;SelectMethod=cursor</ConnectionString> <DriverClass>com.microsoft.sqlserver.jdbc.SQLServerDriver</DriverClass> <UserId>sa</UserId><Password>XVMLXBLBEKMBPMNKTLONLLKQALQVBNKAVMQPMBWNVQOMBLBVBAMZVBWBNUQLTAQL</Password> <CommitSize>50</CommitSize> <FetchSize>100</FetchSize> <MinJobExecutionConnections>0</MinJobExecutionConnections> <MaxJobExecutionConnections>100</MaxJobExecutionConnections> <MinGeneralConnections>0</MinGeneralConnections> <MaxGeneralConnections>20</MaxGeneralConnections> <MinClientConnections>0</MinClientConnections> <MaxClientConnections>20</MaxClientConnections> <StatementCacheSize>64</StatementCacheSize> <IdleConnectionTestInterval>300</IdleConnectionTestInterval> <MaxIdleTime>1800</MaxIdleTime> </Database>

<Database name="db3"><ConnectionString>jdbc:sqlserver://localhost:1433;DatabaseName=Database3;SelectMethod=cursor</ConnectionString> <DriverClass>com.microsoft.sqlserver.jdbc.SQLServerDriver</DriverClass> <UserId>sa</UserId><Password>XVMLXBLBEKMBPMNKTLONLLKQALQVBNKAVMQPMBWNVQOMBLBVBAMZVBWBNUQLTAQL</Password> <CommitSize>50</CommitSize> <FetchSize>100</FetchSize> <MinJobExecutionConnections>0</MinJobExecutionConnections> <MaxJobExecutionConnections>100</MaxJobExecutionConnections> <MinGeneralConnections>0</MinGeneralConnections> <MaxGeneralConnections>20</MaxGeneralConnections> <MinClientConnections>0</MinClientConnections> <MaxClientConnections>20</MaxClientConnections> <StatementCacheSize>64</StatementCacheSize> <IdleConnectionTestInterval>300</IdleConnectionTestInterval> <MaxIdleTime>1800</MaxIdleTime> </Database>

6 Go to the PXE server and use a text editor to open the PXE server’s config.xml file. By default, config.xml resides at:<install_dir>/br/config.xml

7 This config.xml file already has one <Database> element—the PXE server installation process added this element, and it describes the default database.



Search for this <Database> element, and leave it as is.Right underneath this <Database> element, paste in the contents of your db_info.txt file—this file contains the <Database> elements you copied and edited from the various Application Servers associated with non-default databases.

8 Save the config.xml file on the PXE server.

Setting DHCP Scope Options

DHCP scope options associate each Application Server with the database it connects to.

You specify DHCP scope options by adding <DHCPscopeForDBInstance> elements to the config.xml file on the PXE server, using the procedure below.

Procedure 1 Using a text editor, open the config.xml file on the PXE server.2 At the bottom of the file, add a <DHCPscopeForDBInstance> element for each

database, using the syntax below:<DHCPscopeForDBInstance>

<AppserverIP>hostname1</AppserverIP>

<port>9831</port>

</DHCPscopeForDBInstance>

<DHCPscopeForDBInstance name="db2">

<AppserverIP>hostname2</AppserverIP>

<port>9831</port>

</DHCPscopeForDBInstance>

Note the following rules for <DHCPscopeForDBInstance> elements:• Default database: The <DHCPscopeForDBInstance> element that describes the

default database (the database you specified when you installed the PXE server) must NOT have a name attribute.In the example above, the element describing the default database is the first <DHCPscopeForDBInstance> element, and its first line looks like this:<DHCPscopeForDBInstance>

All subsequent <DHCPscopeForDBInstance> elements that describe non-default databases must have a name attribute, for example:<DHCPscopeForDBInstance name="db2">

• name attribute for non-default databases: The name attribute you use in the <DHCPscopeForDBInstance> element must match the name element you used in the corresponding <Database> element.



Continuing with the example started earlier in this discussion, suppose your first non-default database has a <Database> element that starts like this:<Database name="db2">

When you add a <DHCPscopeForDBInstance> element for this database, you would use the same name element you used in the <Database> element, so the first line would be:<DHCPscopeForDBInstance name="db2">

• <AppserverIP> element: Specify either the IP address or the hostname of the Application Server associated with this database.If your environment is set up for disaster recovery, use a hostname rather than an IP address, because in a disaster recovery scenario, the hostname will resolve to the failover Application Server.

• <port> element: Generally, you should enter a value of 9831, which is the port the BladeLogic Application Server uses by default for SSL communication.

Editing pxe.confThe pxe.conf file resides on the PXE server. By default, pxe.conf resides at:

<install_dir>/br

You need to edit pxe.conf to indicate that you are using a multi-database environment. In addition, you can optionally modify cache options.

Specifying Multi-Database Environment[Optional] Modifying Cache Options

Specifying Multi-Database Environment

To indicate that you are using a multi-database environment, add the following line to pxe.conf:

multi_db_mode= 1

If the multi_db_mode switch is absent or its value = 0, then the PXE server will run in single-database mode.

[Optional] Modifying Cache Options

For performance reasons, the PXE server maintains a cache of imported devices and their associated databases. • The PXE server creates this cache during initialization, then updates it every <n>

seconds, as specified by the following parameter in pxe.conf:device_cache_refresh_interval=<n>



Where <n> is the number of seconds. By default, <n> is 300.• To prevent thrashing, pxe.conf includes another parameter that controls how long the

PXE server must wait between cache refreshes. This parameter is:min_time_for_cache_refresh=<n>

Where <n> is the number of seconds to wait before doing another refresh. By default, <n> is 60.If a device comes online, and the PXE server does not find its MAC address in the cache, the PXE server does a refresh to try to find it—this parameter prevents the thrashing that might occur if too many unknown devices come online simultaneously.

Switching From Multi-Database to Single-Database ModeIf you have set up your provisioning environment for multi-database use, you can switch back to single-database mode. For example, you may have added multiple databases to config.xml, and you now want to run in single-database mode with any one of these databases.

The procedure varies slightly depending on whether or not the single database you want to use is the default database:

If the Single Database Is the Default DatabaseIf the Single Database Is Not the Default Database

If the Single Database Is the Default Database

Use the following procedure to switch back to single-database mode, if the single database you want to use is the default database.

Procedure 1 Edit pxe.conf to contain the following line:multi_db_mode=0

2 If pxe.conf has a single_mode_db_name setting, delete it.3 Edit config.xml to remove all <DHCPscopeForDBInstance> elements.4 Configure the DHCP server for 211 and 212 scope options, as described in Adding

Predefined Options.

If the Single Database Is Not the Default Database

Use the following procedure to switch back to single-database mode, if the single database you want to use is not the default database.

Procedure 1 Edit pxe.conf to contain the following lines:multi_db_mode=0

single_mode_db_name=<database_name>



2 Edit config.xml to remove all <DHCPscopeForDBInstance> elements.3 Configure the DHCP server for 211 and 212 scope options, as described in Adding

Predefined Options.

JumpStart SetupPrerequisite: You must have a working JumpStart environment, configured for and stocked with all the operating system installation files you want to use to provision target machines. Your JumpStart environment can use one, two, or three physical servers for the boot, config, and install JumpStart services.

Procedure 1 Each JumpStart server machine must be running version 7.2 or higher of the RSCD agent. For information on installing or upgrading the agent, see:Installing Only an RSCD Agent on UNIXUpgrading RSCD Agents

2 On the machine you are using for your JumpStart configuration server, create the following subdirectories under the root directory for the configuration server:/BladeLogic/rscd

For example, if you created a directory called /configserver to act as the root directory for the configuration server, your directory structure would look like this:/configserver/BladeLogic/rscd/

3 Unzip the file:external-files.zip

into a temporary directory.This file expands into a large number of files and subdirectories. Depending on which architecture(s) you plan to provision, navigate to one or both of the following files:For SPARC: bl_7.2/provisioning/jumpstart/bmisolarisFor x86: bl_7.2/provisioning/jumpstart/bmisolaris-x86

4 Copy the bmisolaris/bmisolaris-86 file to the BladeLogic/rscd/ directory you just created.

5 Obtain the Solaris agent installer file(s) for SPARC and/or x86 architectures:RSCD72-SOLSPARC.SH

RSCD72-SOLx86.SH

(You can download these files from the BladeLogic web site.)

Note: For successful provisioning, an RSCD agent must be running on each of your JumpStart infrastructure machines (the boot server, the config server, and the install server). Each agent must be licensed for use with both NSH and Configuration Manager.



These files install an RSCD agent on each target machine being provisioned. 6 Rename the RSCD72-SOLSPARC.SH file to:

rscd.sh

and copy rscd.sh to the newly created BladeLogic/rscd/ directory.7 Rename the RSCD72-SOLx86.SH file to:

rscd-sol-x86.sh

and copy rscd-sol-x86.sh to the newly created BladeLogic/rscd/ directory.8 Optional—create a response file for the installation of the RSCD agent and store the

response file in the newly created BladeLogic/rscd directory. The response file is called nsh-install-defaults.For information on how to create an nsh-install-defaults file, see Creating a File of UNIX Installation Defaults.

9 Check that the BladeLogic/rscd/directory on the configuration server now contains the following files:bmisolarisrscd.shrscd-sol-x86.shnsh-install-defaults (optional)

10 Now you need to copy the check file from the JumpStart installation server to the root directory for the JumpStart configuration server.When you set up the JumpStart installation server, the JumpStart setup process creates a file called check, and places it in a directory structure whose higher level subdirectories reflect the names of the relevant operating system.For example, here is a sample directory structure for set of Solaris 10 install files:install_root/solaris10/Solaris_10/Misc/jumpstart_sample/

Regardless of the higher level directory names (for example, for Solaris 8, Solaris 9, etc.) the lower level Misc/jumpstart_sample subdirectory contains the file that you want to copy — check.Copy this check file into the root directory for the JumpStart configuration server. In this example, you would copy the check file into the /configserver directory, as shown here:/configserver/check



NIM SetupPrerequisite: You must have a working NIM environment, configured for and stocked with all the operating system installation files you want to use to provision target machines.

Procedure 1 The NIM master machine must be running version 7.2 or higher of the RSCD agent. For information on installing or upgrading the agent, see:Installing Only an RSCD Agent on UNIXUpgrading RSCD Agents

2 On the NIM master, select or create a directory to use as a BladeLogic staging directory. This directory will be used to hold copies of the configuration files that BladeLogic generates. By convention, this directory is called:/export

Make a note of this directory because you will need it when you configure Provisioning Manager for NIM. (Specifically, you need to specify this staging directory in the STAGING_DIR_PATH property when you define your NIM data store instances.)Directly beneath this staging directory, create the following subdirectories:/BladeLogic/rscd

For example, if your staging directory is called /export, your directory structure would look like this:/export/BladeLogic/rscd/

3 Obtain the AIX agent installer file:RSCD72-AIX.SH

(You can download this file from the BladeLogic web site.)This file installs an RSCD agent on each target machine being provisioned.

4 Rename the RSCD72-AIX.SH file to:rscd.sh

and copy rscd.sh to the newly created BladeLogic/rscd/ directory.5 Optional—create a response file for the installation of the RSCD agent and store the

response file in the newly created BladeLogic/rscd directory. The response file is called nsh-install-defaults.For information on how to create an nsh-install-defaults file, see Creating a File of UNIX Installation Defaults.

Note: For successful provisioning, an RSCD agent must be running on the NIM master. This agent must be licensed for use with both NSH and Configuration Manager.



6 Check that the BladeLogic/rscd/directory on the NIM master now contains the following files:rscd.shnsh-install-defaults (optional)

Ignite SetupPrerequisite: You must have a working Ignite environment, configured for and stocked with all the operating system installation files you want to use to provision target machines.

Procedure 1 The Ignite master machine must be running version 7.3 or higher of the RSCD agent. For information on installing or upgrading the agent, see:Installing Only an RSCD Agent on UNIXUpgrading RSCD Agents

2 On the Ignite master, select or create a directory to use as a BladeLogic staging directory. This directory will be used to hold copies of the configuration files that BladeLogic generates. By convention, this directory is called:/export

Make a note of this directory because you will need it when you configure Provisioning Manager for Ignite. (Specifically, you need to specify this staging directory in the STAGING_DIR_PATH property when you define your Ignite data store instances.)Directly beneath this staging directory, create the following subdirectories:/BladeLogic/rscd

For example, if your staging directory is called /export, your directory structure would look like this:/export/BladeLogic/rscd/

3 Obtain the HPUX agent installer file:RSCD730-HPUX11.SH

(You can download this file from the BladeLogic web site.)This file installs an RSCD agent on each target machine being provisioned.

4 Rename the RSCD730-HPUX11.SH file to:rscd.sh

and copy rscd.sh to the newly created BladeLogic/rscd/ directory.5 Optional—create a response file for the installation of the RSCD agent and store the

response file in the newly created BladeLogic/rscd directory. The response file is called nsh-install-defaults.

Note: For successful provisioning, an RSCD agent must be running on the Ignite master. This agent must be licensed for use with both NSH and Configuration Manager.



For information on how to create an nsh-install-defaults file, see Creating a File of UNIX Installation Defaults.

6 Check that the BladeLogic/rscd/directory on the Ignite master now contains the following files:rscd.shnsh-install-defaults (optional)


Related Procedures

This chapter describes the following information that relates to the installation of Network Shell and Configuration Manager on all operating systems and information about installing localized versions of BladeLogic products (see Setting up BladeLogic for Non-English Locales):• Licensing Agents• Using the Post-Install Configuration Wizard• Starting Network Shell, Configuration Manager, and Provisioning Manager• Ensuring a TTY Connection

Licensing AgentsA licensed RSCD agent must be installed on every server that you plan to manage using Configuration Manager or Network Shell. When you install an agent, it is automatically granted a demonstration license valid for two weeks. After you have registered as a customer, you can log into BladeLogic’s customer support web site and use a web-based licensing mechanism at www.bladelogic.com/support.jsp to obtain long-term licenses for your RSCD agents.

BladeLogic’s web-based licensing utility asks you to provide a file with information about the hosts that should be licensed. When you install RSCD agents on any platform, the installation process lets those agents run in unlicensed mode, which gives the agents enough functionality to run a command that creates a file listing the number of processors and the host ID of each machine where the agent is installed. BladeLogic needs this information to license your RSCD agents. After you upload that file to BladeLogic, the web-based licensing utility will download a file that contains the appropriate licensing keys. You can then run another command that applies those keys to multiple agents simultaneously.

For a detailed description of the procedure for licensing agents, visit www.bladelogic.com/support.jsp.



Related Procedures 228


Using the Post-Install Configuration WizardBladeLogic’s Post-Install Configuration wizard consolidates the minimum configuration steps that must be performed to set up an Application Server. Although BladeLogic’s Application Server Administration console provides command-line mechanisms for configuring all possible Application Server options, only a few must be set to make a BladeLogic system functional. The Post-Install Configuration wizard presents those essential tasks in a graphical user interface and provides explanatory information for each step in the process.

Available for both Windows and UNIX-style installations, the configuration wizard allows you to set the following configuration options:• Database connection parameters—Configuration Manager works in conjunction with an

Oracle or SQL Server database server in its middle tier. Use the configuration wizard to configure your database connection.

• File server—Configuration Manager uses a file server to store large snapshots of files, Network Shell scripts, BLPackages, Windows installables, and other types of information that is not easily stored in a database. Use the configuration wizard to identify the file server and a directory within the file server.

• Notification servers—Configuration Manager optionally generates email and SNMP traps that send notifications when a job completes. Use the configuration wizard to identify an SMTP server, the address from which the notification emails originate, and the SNMP destination to which all SNMP traps are sent.

• Super-user passwords—Configuration Manager provides several predefined users. The RBACAdmin user has full permission to manage roles and users in the RBAC Manager workspace in Configuration Manager, where you can assign permissions for all BladeLogic users. The BLAdmin user has Read access for all system objects within Configuration Manager. Use the configuration wizard to provide SRP passwords for the RBACAdmin and BLAdmin users.

Note: Be aware of the following:• If your database is not set up or you do not currently have the information

needed to establish a connection to that database, you cannot configure the Application Server. Click Cancel to close the wizard. Obtain the necessary connection information and run the Post-Install Configuration wizard again to complete your system configuration.

• If you are running the Post-Install Configuration wizard on UNIX, the OS-specific xll libraries must be installed.



Procedure 1 To start the Post-Install Configuration wizard, do one of the following:• Perform an installation that includes installation of the Application Server. The

installation program gives you the option of launching the wizard at the end of the installation procedure.

• From the Windows Start menu, select Programs > BladeLogic > Utilities > Application Server Configuration Wizard.

• Start the wizard manually by running /br/blappconf in the directory where BladeLogic is installed, as shown below:> In Windows, enter C:\Program Files\BladeLogic\br

\blappconf -install.

> In UNIX, enter /usr/nsh/br/blappconf -install.

The configuration wizard opens.

Note: If you invoke the wizard without passing the -install flag, the wizard will display configuration settings that have already been entered for the Application Server and allow you to change those settings.



2 Read the introductory page and click Next. The Database page displays.

3 Choose a Database Type—either Oracle or SQL Server.4 Provide the following database configuration information:

Database Server—Server running the database.Database Port—Port the database listens on. By default a BladeLogic installation uses the following database ports:

Database Name—SQL Server database name. By default the database name is bladelogic. (This option is only available for SQL Server databases.)SID—System ID of the Oracle database. (This option is only available for Oracle databases.)User ID—User name that the database needs to authenticate your connection. Password—Password assigned to the user ID.


Oracle 1521

SQL Server 1433



5 Click Next. The File Server page displays.

6 Provide the following file server configuration information:File Server Name—Name of the server where data is stored. By default, the file server is created on the same machine as the Application Server. File Server Storage Location—Directory on the file server where data is stored. By default, the directory of the file server is

<appserver_install_directory>/storage.A file server should meet the following requirements:• An RSCD agent must be installed and licensed. • A file server must have, as a minimum, 72 GB of available, non-redundant, disk

space. BladeLogic recommends that the file server have 200 GB or more of available RAID 5 disk space.

• A user name must be defined on the file server, and all Configuration Manager users must be mapped to that user. Without this mapping a user may not be able to access a file that another user has stored on the file server. One way to accomplish the necessary mapping is to create an entry like the following in the exports file on the file server:<AppServer> rw,user=<username>

where <AppServer> is a comma-separated list of Application Server names or IP addresses and <username> is the name to which all users are mapped.



• The internal System:System role/user must be mapped to the user name defined on the file server. To accomplish the mapping, create an entry like the following in the users.local file on the file server: System:System rw,user=<username>

where <username> is the name to which all users are mapped, typically bladmin or administrator.

If the required directory structure does not already exist on the file server, the process will attempt to create it.

7 Click Next. The Notification Servers page displays.

8 Provide information identifying an email server by entering the following under SMTP Options:SMTP Server—Name or IP address of the host managing email. (SMTP stands for simple mail transfer protocol.)Email From—Email address from which BladeLogic-generated email is sent. BladeLogic jobs can generate email upon their completion.

9 If you are using SNMP trap notifications, provide information identifying the SNMP server by entering the following under SNMP Options:SNMP Server—Name or IP address of the host to which SNMP traps should be sent.SNMP Port—The port on the SNMP server that listens for SNMP traps. By default the port is set to the standard SNMP port of 162.



10 Click Next. The User Passwords page displays.

11 Under both RBACAdmin User and BLAdmin User, enter a password and then retype the password to confirm your entry. You will not be able to enter a password if a password has already been set. Passwords are used to authenticate the RBACAdmin and BLAdmin users via the SRP authentication protocol.The RBACAdmin user has full permission to manage roles and users in the RBAC Manager workspace in Configuration Manager, where you can assign permissions for all BladeLogic users. The BLAdmin user has Read access for all system objects within Configuration Manager. For more information on the RBACAdmin and BLAdmin users, see the BladeLogic Users Guide.

12 Click Finish.

Note: BladeLogic recommends that you synchronize the clock on the Application Server and all client machines. Clocks should be synchronized to the minute. For example, if an Application Server is in Boston, where the time is 7:04, the clock on client machines in San Francisco should be set to 4:04.



Starting Network Shell, Configuration Manager, and Provisioning Manager

Use these procedures to start Configuration Manager, Network Shell, and Provisioning Manager.

WindowsTo start Network Shell, do one of the following:• From the Start menu, select Programs > BladeLogic > Network Shell.• From a command line, enter the following (assuming you have installed Network Shell

in its default location):C:\Program Files\BladeLogic\OM\bin\nsh.exe

To start Configuration Manager, do one of the following:• From the Start menu, select Programs > BladeLogic > Configuration Manager

Console.• From a command line, enter the following (assuming you have installed Configuration

Manager in its default location):C:\Program Files\BladeLogic\OM\br\blclient.bat

To start Provisioning Manager, do one of the following:• From the Start menu, select Programs > BladeLogic > Provisioning Manager

Console.• From a command line, enter the following (assuming you have installed Configuration

Manager in its default location):C:\Program Files\BladeLogic\OM\br\blpmclient.bat

Note: To run Configuration Manager, you must first make several configuration settings to the Application Server and define passwords for predefined users. Typically these minimal settings are made using the Post-Install Configuration wizard (see Using the Post-Install Configuration Wizard). BladeLogic also provides command line utilities for configuring the Application Server and extensive support for controlling user permissions through RBAC Manager in Configuration Manager. For more information on RBAC, see the BladeLogic Users Guide.



Solaris, Linux, AIX, and HP-UXTo start Network Shell, enter the following:

$ /bin/nsh

To start Configuration Manager, you must first start Network Shell and then start Configuration Manager, as shown below:

$ /bin/nsh$ blclient

To run the blclient utility, a user must have root privileges or be a part of the bladmin group.

To start Provisioning Manager, enter the following:$ /bin/nsh$ blpmclient

Starting the Application ServerUse this procedure to start the Application Server.

Procedure Do one of the following:• On Windows, from the Start menu, select Settings > Control Panel. Double-click

Administrative Tools, double-click Services, and then double-click BladeLogic Application Server. On the properties page for the Application Server, click Start.

• On a UNIX-style system, enter the following:/etc/init.d/blappserv start

Loading Pre-packaged ContentBladeLogic provides a script that creates sample content in Configuration Manager and Provisioning Manager. The script creates groups, folders, and smart groups that are commonly used by many organizations. In the RBAC Manager workspace, the script creates sample roles, authorization profiles, and ACL templates that are defined to perform many common tasks. When you perform the following procedure, all of this pre-packaged content is loaded into the database that BladeLogic is currently accessing.

Procedure 1 Set up your database as you normally would.2 Install BladeLogic and run the Post-Install Configuration wizard.

Note: To run the Application Server, you must first configure it. Typically this initial configuration is performed using the Post-Install Configuration wizard (see Using the Post-Install Configuration Wizard). BladeLogic also provides command line utilities for configuring the Application Server. For more information, see the BladeLogic Administration Guide.



3 From the directory where BladeLogic is installed, do one of the following:• On Windows, enter the following:

br\blcontent.bat

• On a UNIX-style system, enter the following:/br/blcontent

Manually Installing PerlWhen you install client- or server-tier BladeLogic components, the Perl Module is automatically installed if the installer finds a supported version of Perl on the server. (For supported versions of Perl, see Perl Support.) If Perl is not found, the installer stores the files needed for the Perl module in the BladeLogic installation directory. You can use these files to install and configure Perl at a later time.

Use these procedures to install BladeLogic’s Perl module manually after you have installed client- or server-tier components. The procedure varies between Windows and UNIX-style machines.

Installing Perl on WindowsUse this procedure to manually install Perl on Windows.

Procedure 1 Install a client- or server-tier component. 2 Copy the NSH.pm file from <BladeLogic_install_dir>/OM/perl to

<Perl_install_dir>/lib.BladeLogic_install_dir is the directory where you have installed BladeLogic and Perl_install_dir is the root directory where Perl is installed.For example, copy C:\Program Files\BladeLogic\OM\perl\NSH.pm to C:\Perl\lib\NSH.pm.

3 Create a directory called NSH under <Perl_install_dir>/lib/auto.4 Copy the remaining files in <BladeLogic_install_dir>/OM/perl to

<Perl_install_dir>/lib/auto/NSH. The files that must be copied are:

NSH.bsNSH.dllNSH.expNSH.lib

Note: If you want to access properties defined in the pre-packaged content in reports, refer to the BladeLogic Reports Users Guide for instructions on making the properties available in the default data set for ad hoc reporting.



If you are configuring the Perl module on a client machine, the procedure is complete. If you are configuring the Perl module on an Application Server, you must configure the Application Server so it knows the path to the Perl executable, as described in Configuring an Application Server for Perl.

Installing Perl on UNIXUse this procedure to manually install Perl on UNIX-style machines.

Procedure 1 Install a client- or server-tier component. 2 Cd to <BladeLogic_install_dir>/perl.

For example, cd to usr/nsh/perl.3 Enter the following command:

./Install

If you are configuring the Perl module on a client machine, the procedure is complete. If you are configuring the Perl module on an Application Server, you must configure the Application Server so it knows the path to the Perl executable, as described in Configuring an Application Server for Perl.

Configuring an Application Server for PerlIf you are installing the Perl Module on an Application Server, you must perform this procedure so the Application Server knows the path to the Perl executable.

Procedure 1 From the <BladeLogic_install_dir>/br directory, enter the following command to start the Application Server Administration utility:

blasadmin

2 Enter the following command to specify the path to the Perl executable:set perlconfig location PATH_TO_PERL

where PATH_TO_PERL is a Network Shell-style path, such as /c/perl/bin/perl.exe.

3 To validate that you have properly configured Perl, enter the following:bladmin>show perlconfig all

You should see the following:[perlconfig] location:/c/perl/bin/perl.exe

4 Restart the Application Server.



Ensuring a TTY ConnectionBladeLogic supports TTY communication, a capability that simulates a character-based data flow between machines, allowing your computer to emulate the output of a character-based terminal such as a VT100. TTY gives you the capability to run programs that require screen control on remote machines. For example, with TTY, you can run vi, top, or smit on remote servers.

TTY only applies to programs launched with BladeLogic's nexec command on remote UNIX servers. Applications that do not require screen-oriented capabilities are not affected by TTY. In fact, TTY is not even required for those applications to run successfully. If you are not running a screen-oriented application, the information in this procedure is not relevant for you.

Although you should generally be able to use TTY communication without any extra effort on your part, in some situations you may have to adjust the terminal type and terminal setting of your machine. Before you change those terminal settings, you should know the following:• What type of terminal emulation does your screen window support? Some common

emulations types are vt100, ansi, and xterm.• How is the TERM variable set for your session? The TERM variable tells other

programs what type of terminal emulation your session is using. • Does the remote machine support your type of emulation? Not all servers are configured

to support all emulation types. For example, an AIX base installation does not typically support ansi emulation, even though ansi is the default emulation used on Windows machines.

Procedure To ensure proper terminal emulation support, do the following:1 On your machine, run a terminal emulation window that you know will be supported by

the remote server. The xterm program is widely supported. The xterm application can often be found in the following locations:

2 Ensure that your TERM variable is set. To determine the value of the TERM variable, enter the following command from Network Shell:

echo $TERM

Operating System Location

Solaris /usr/openwin/bin/xterm

Linux /usr/bin/X11/xterm

AIX /usr/bin/X11/xterm

HP-UX /usr/bin/X11/xterm



If no output (or a blank line) is output, then your TERM variable is not set. You must set it before you can run any remote, screen-oriented application. Set a TERM variable by entering the following:

export TERM=emulation_type

where emulation_type provides a value, such as ansi or xterm, that matches the terminal emulation capabilities of your window.

3 Ensure that the terminal emulation type you specify is supported on the remote server. This can be done as follows from Network Shell:• For a remote Linux server, enter the following:

echo | nexec linuxhost /usr/bin/tset -Qr

• For a remote Solaris server, enter the following:nexec solarishost /usr/ucb/tset -Qr

• For a remote AIX server, enter the following:nexec aixhost /bin/tset -Qr

• For a remote HP-UX server, enter the following:nexec hpuxhost /bin/tset -Qr

If the message that returns says something like Terminal type is ansi, then your TTY connection should work correctly. If the message returned says something like tset: unknown terminal type ansi or Type ansi unknown, then you will not be able to run remote screen-oriented applications. Applications that do not require screen capabilities are not affected.

Setting up BladeLogic for Non-English LocalesBladeLogic provides various levels of internationalization and localization support for its products. Refer to the "I18N/L10N Support" section of the Release Notes for details of the internationalization and localization support provided in this release. See the following sections for database configuration and language selection information relating to setting up BladeLogic for non-English locales:

Configuring BladeLogic Databases for a Non-English LocaleSetting the Language for the Installers on WindowsSetting the Language for the Installers on UNIX

Configuring BladeLogic Databases for a Non-English LocaleIf you are using BladeLogic in a locale other than English, please follow these recommendations:• Configure your BladeLogic databases using the settings recommended by your database

vendor for that language. Use the appropriate BladeLogic schema scripts depending on your configuration, see Determining which Schema Scripts to Use for more information.



• In order to avoid data issues, save all string data in UTF-16 format. • If you are using SQL Server, specify the appropriate collating sequence as described in

the following sections: Setting up a SQL Server Database SchemaSetting up a Reporting Data Warehouse Schema on SQL Server

Determining which Schema Scripts to Use

When setting up a database schema, the DBA typically configures a database to support char/varchar or nchar/nvarchar character sets. BladeLogic provides nchar versions of the applicable schema scripts to be used in the case where the database is configured for nchar/nvarchar character sets. This is generally the case for SQL Server databases that store double-byte data and Oracle databases that store data for multiple languages.

Setting the Language for the Installers on WindowsWhen installing BladeLogic products on Windows, the first window that displays is the Choose Setup Language window. This allows you to select the language to use for the installation program. The subsequent installer windows display in the language you choose.

If this is the initial installation, the Choose Setup Language window opens in the local language of the Windows operating system. All subsequent invocations of the installer (upgrades and uninstalls) will use the language selected at the initial installation. To choose a different language for the installer after an initial installation, first uninstall the product, and then run the install program again.

When you are installing BladeLogic, the language chosen on this screen becomes the default language used for the Configuration Manager and Provisioning Manager consoles. When a user logs in, he or she can select a different language and then that choice becomes his or her personal default for future logins. See the BladeLogic Users Guide for more information.

When you are installing BladeLogic Reports, the language chosen on this screen only applies to the Reports installer windows. The language of the web-based user interface for Reports is determined by your browser settings. See the BladeLogic Reports Users Guide for more information.

Setting the Language for the Installers on UNIXWhen installing BladeLogic products on UNIX, you are prompted to select the language to use for the installation process. The subsequent installer messages display in the language you choose.



When you are installing BladeLogic, the language chosen becomes the default language used for the Configuration Manager and Provisioning Manager consoles. When a user logs in, he or she can select a different language and then that choice becomes his or her personal default for future logins. See the BladeLogic Users Guide for more information.

When you are installing BladeLogic Reports, the language chosen only applies to the Reports installer messages. The language of the web-based user interface for Reports is determined by your browser settings. See the BladeLogic Reports Users Guide for more information.