Installation Config

Installation and Configuration
Guide
Version: 8.0.1
Document Number: 09300801
First Edition, July 2005, version 8.0.1
To ensure that you are using the documentation that corresponds to the software you are licensed to use, compare this version number
with the software version shown in About MicroStrategy... in the Help menu of your software.
Document number: 09300801
Copyright 2005 by MicroStrategy Incorporated. All rights reserved.
If you have not executed a written or electronic agreement with MicroStrategy or any authorized MicroStrategy distributor, the following
terms apply:
This software and documentation are the proprietary and confidential information of MicroStrategy Incorporated and may not be
provided to any other person. Copyright 2001-2005 by MicroStrategy Incorporated. All rights reserved.
THIS SOFTWARE AND DOCUMENTATION ARE PROVIDED AS IS AND WITHOUT EXPRESS OR LIMITED WARRANTY OF ANY
KIND BY EITHER MICROSTRATEGY INCORPORATED OR ANYONE WHO HAS BEEN INVOLVED IN THE CREATION,
PRODUCTION, OR DISTRIBUTION OF THE SOFTWARE OR DOCUMENTATION, INCLUDING, BUT NOT LIMITED TO, THE
IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, GOOD TITLE AND
NONINFRINGMENT, QUALITY OR ACCURACY. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE
SOFTWARE AND DOCUMENTATION IS WITH YOU. SHOULD THE SOFTWARE OR DOCUMENTATION PROVE DEFECTIVE,
YOU (AND NOT MICROSTRATEGY, INC. OR ANYONE ELSE WHO HAS BEEN INVOLVED WITH THE CREATION, PRODUCTION,
OR DISTRIBUTION OF THE SOFTWARE OR DOCUMENTATION) ASSUME THE ENTIRE COST OF ALL NECESSARY
SERVICING, REPAIR, OR CORRECTION. SOME STATES DO NOT ALLOW THE EXCLUSION OF IMPLIED WARRANTIES, SO THE
ABOVE EXCLUSION MAY NOT APPLY TO YOU.
In no event will MicroStrategy, Inc. or any other person involved with the creation, production, or distribution of the Software be liable
to you on account of any claim for damage, including any lost profits, lost savings, or other special, incidental, consequential, or
exemplary damages, including but not limited to any damages assessed against or paid by you to any third party, arising from the use,
inability to use, quality, or performance of such Software and Documentation, even if MicroStrategy, Inc. or any such other person or
entity has been advised of the possibility of such damages, or for the claim by any other party. In addition, MicroStrategy, Inc. or any
other person involved in the creation, production, or distribution of the Software shall not be liable for any claim by you or any other
party for damages arising from the use, inability to use, quality, or performance of such Software and Documentation, based upon
principles of contract warranty, negligence, strict liability for the negligence of indemnity or contribution, the failure of any remedy to
achieve its essential purpose, or otherwise. The entire liability of MicroStrategy, Inc. and your exclusive remedy shall not exceed, at
the option of MicroStrategy, Inc., either a full refund of the price paid, or replacement of the Software. No oral or written information
given out expands the liability of MicroStrategy, Inc. beyond that specified in the above limitation of liability. Some states do not allow
the limitation or exclusion of liability for incidental or consequential damages, so the above limitation may not apply to you.
The information contained in this manual (the Documentation) and the Software are copyrighted and all rights are reserved by
MicroStrategy, Inc. MicroStrategy, Inc. reserves the right to make periodic modifications to the Software or the Documentation without
obligation to notify any person or entity of such revision. Copying, duplicating, selling, or otherwise distributing any part of the Software
or Documentation without prior written consent of an authorized representative of MicroStrategy, Inc. are prohibited. U.S. Government
Restricted Rights. It is acknowledged that the Software and Documentation were developed at private expense, that no part is public
domain, and that the Software and Documentation are Commercial Computer Software provided with RESTRICTED RIGHTS under
Federal Acquisition Regulations and agency supplements to them. Use, duplication, or disclosure by the U.S. Government is subject
to restrictions as set forth in subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer Software clause at DFAR
252.227-7013 et. seq. or subparagraphs (c)(1) and (2) of the Commercial Computer SoftwareRestricted Rights at FAR 52.227-19,
as applicable. Contractor is MicroStrategy, Inc., 1861 International Drive, McLean, Virginia 22102. Rights are reserved under copyright
laws of the United States with respect to unpublished portions of the Software.
The following are either trademarks or registered trademarks of MicroStrategy Incorporated in the United States and certain other
countries:
MicroStrategy, MicroStrategy 6, MicroStrategy 7, MicroStrategy 7i, MicroStrategy 7i Evaluation Edition, MicroStrategy 7i Olap Services,
MicroStrategy 8, MicroStrategy Evaluation Edition, MicroStrategy Administrator, MicroStrategy Agent, MicroStrategy Architect,
MicroStrategy Bi Developer Kit, MicroStrategy Broadcast Server, MicroStrategy Broadcaster, MicroStrategy Broadcaster Server,
MicroStrategy Business Intelligence Platform, MicroStrategy Consulting, MicroStrategy CRM Applications, MicroStrategy Customer
Analyzer, MicroStrategy Desktop, MicroStrategy Desktop Analyst, MicroStrategy Desktop Designer, MicroStrategy eCRM 7,
MicroStrategy Education, MicroStrategy eTrainer, MicroStrategy Executive, MicroStrategy Infocenter, MicroStrategy Intelligence
Server, MicroStrategy Intelligence Server Universal Edition, MicroStrategy MDX Adapter, MicroStrategy Narrowcast Server,
MicroStrategy Objects, MicroStrategy OLAP Provider, MicroStrategy SDK, MicroStrategy Support, MicroStrategy Telecaster,
MicroStrategy Transactor, MicroStrategy Web, MicroStrategy Web Business Analyzer, MicroStrategy World, Alarm, Alarm.com,
Alert.com, Angel, Angel.com, Application Development and Sophisticated Analysis, Best In Business Intelligence, Centralized
Application Management, Changing The Way Government Looks At Information, DSS Agent, DSS Architect, DSS Broadcaster, DSS
Broadcaster Server, DSS Office, DSS Server, DSS Subscriber, DSS Telecaster, DSS Web, eBroadcaster, eCaster, eStrategy,
eTelecaster, Information Like Water, Insight Is Everything, Intelligence Through Every Phone, Intelligence To Every Decision Maker,
Intelligent E-Business, IWAPU, Personal Intelligence Network, Personalized Intelligence Portal, Query Tone, Quickstrike, Rapid
Application Development, Strategy.com, Telepath, Telepath Intelligence, Telepath Intelligence (and Design), The E-Business
Intelligence Platform, The Foundation For Intelligent E-Business, The Integrated Business Intelligence Platform Built For The
Enterprise, The Intelligence Company, The Platform For Intelligent E-Business, The Power Of Intelligent eBusiness, The Power Of
Intelligent E-Business, and The Scalable Business Intelligence Platform Built For The Internet are all registered trademarks or
trademarks of MicroStrategy Incorporated.
All other products are trademarks of their respective holders. Specifications subject to change without notice. MicroStrategy is not
responsible for errors or omissions. MicroStrategy makes no warranties or commitments concerning the availability of future products
or versions that may be planned or under development.
This product is patented. One or more of the following patents may apply to the product sold herein: U.S. Patent Nos. 6,154,766,
6,173,310, 6,260,050, 6,263,051, 6,269,393, 6,279,033, 6,501,832, 6,567,796, 6,587,547, 6,606,596, 6,658,093, 6,658,432,
6,662,195, 6,671,715, 6,691,100, 6,694,316, 6,697,808, 6,704,723, 6,707,889, 6,741,980, 6,765,997, 6,768,788, 6,772,137,
6,788,768, 6,792,086, 6,798,867, 6,801,910, 6,820,073, 6,829,334, 6,836,537, 6,850,603, 6,859,798, 6,873,693 and 6,885,734.
Other patent applications are pending.
Various MicroStrategy products contain the copyrighted technology of third parties. This product may contain one or more of the
following copyrighted technologies:
Graph Generation Engine Copyright 1998-2004. Three D Graphics, Inc. All rights reserved.
Actuate Formula One. Copyright 1993-2004 Actuate Corporation. All rights reserved.
XML parser Copyright 2003 Microsoft Corporation. All rights reserved.
Xalan XSLT processor. Copyright 1999-2004. The Apache Software Foundation. All rights reserved.
Xerces XML parser. Copyright 1999-2004. The Apache Software Foundation. All rights reserved.
FOP XSL formatting objects. Copyright 2004. The Apache Software Foundation. All rights reserved.
Portions of Intelligence Server memory management Copyright 1991-2004 Compuware Corporation. All rights reserved.
International Components for Unicode
Copyright 1999-2004 Compaq Computer Corporation
Copyright 1999-2004 Hewlett-Packard Company
Copyright 1999-2004 IBM Corporation
Copyright 1999-2004 Hummingbird Communications Ltd.
Copyright 1999-2004 Silicon Graphics, Inc.
Copyright 1999-2004 Sun Microsystems, Inc.
Copyright 1999-2004 The Open Group
All rights reserved.
Real Player and RealJukebox are included under license from Real Networks, Inc. Copyright 1999-2004. All rights reserved.
CONTENTS
Document description.............................................................. xiii

Who should use this guide..................................................... xiv
Prerequisites .......................................................................... xiv
Objectives .............................................................................. xiv
About this book .............................................................................xv
Typographical standards ..............................................................xv
For online and printed documentation ....................................xv
For printed documentation only ............................................ xvii
Resources.................................................................................... xix
Product documentation .......................................................... xix
Online documentation ............................................................ xix
International support ................................................................... xxii
User assistance ......................................................................... xxiii
Online help........................................................................... xxiii
Technical Support ................................................................ xxiii
Feedback ................................................................................... xxix
1. Introduction to Introduction.................................................................................. 1
MicroStrategy
MicroStrategy components ............................................................ 2
Common Setups for MicroStrategy.......................................... 2
How to use this book ................................................................... 14
Installing MicroStrategy on Windows ..................................... 14
Installing MicroStrategy on UNIX and Linux .......................... 16
2005 MicroStrategy, Inc. v

Contents Installation and Configuration Guide
2. Planning Your Introduction................................................................................ 19

Installation
Upgrade considerations............................................................... 20
Installation prerequisites .............................................................. 20
Recommended installation location ....................................... 21
Hardware recommendations.................................................. 21
Software recommendations ................................................... 28
Installation considerations ........................................................... 35
System sizing guidelines........................................................ 35
MicroStrategy Web Universal and Intelligence Server
compatibility ........................................................................... 42
Certified ODBC drivers for MicroStrategy Intelligence Server
Universal Edition .................................................................... 42
Methods of installation ................................................................. 43
GUI ........................................................................................ 43
Command line........................................................................ 44
Silent installation .................................................................... 45
Licensing information................................................................... 46
Types of licenses ................................................................... 47
Next steps.................................................................................... 48
3. Installing Introduction................................................................................ 49
MicroStrategy on
Installation procedure .................................................................. 50
Windows
InstallShield Wizard ............................................................... 51
Installation verification ........................................................... 67
Next steps.............................................................................. 68
4. Installing Introduction................................................................................ 71
MicroStrategy on
Installation procedures on UNIX or Linux .................................... 72
UNIX and Linux
Different methods of installation............................................. 72
Installing MicroStrategy using InstallShield Wizard ............... 73
Verifying installation ............................................................... 82
Directory structure.................................................................. 83
Next steps.................................................................................... 85
5. Configuring Introduction................................................................................ 87
MicroStrategy
Configuration prerequisites.......................................................... 88
Intelligence Server
Using the MicroStrategy Configuration Wizard............................ 89
Overview of the MicroStrategy Configuration Wizard ............ 89
Creating a metadata repository and statistics tables ............. 95
vi 2005 MicroStrategy, Inc.

Installation and Configuration Guide Contents
Setting up the MicroStrategy Intelligence Server................. 102

Project Sources ................................................................... 108
Next steps.................................................................................. 110
6. Creating a Project Introduction.............................................................................. 111

MicroStrategy Desktop definitions ............................................. 112
MicroStrategy metadata....................................................... 112
Metadata shell ..................................................................... 112
MicroStrategy objects .......................................................... 113
Project source ...................................................................... 113
Database instance ............................................................... 114
Project.................................................................................. 114
Creating a project using Project Builder .................................... 118
Using Project Builder ........................................................... 118
Creating a project using MicroStrategy Desktop ....................... 120
Creating a new project ......................................................... 120
Adding tables using the Warehouse Catalog....................... 122
Creating facts....................................................................... 124
Creating attributes ............................................................... 126
Creating shortcut objects ..................................................... 130
MicroStrategy project schema ................................................... 132
Next steps.................................................................................. 133
7. Deploying Your Introduction.............................................................................. 135

Project with
Connecting MicroStrategy Web to the Intelligence Server ........ 136
MicroStrategy Web
8. Configuring and Introduction.............................................................................. 139

Deploying
Deploying with WebLogic and Apache ...................................... 140
MicroStrategy Web
Universal WebLogic paths and folder locations ................................... 141
Preconfiguration information ................................................ 142
Deploying MicroStrategy Web Universal ............................. 146
Re-deploy the application .................................................... 157
Performance-based setup information................................. 158
Deploying with WebSphere 5.x and IBM HTTP Server ............. 165
Deploying with Sun ONE (iPlanet) 8.0....................................... 179
2005 MicroStrategy, Inc. vii


Deploying with Tomcat (Linux) .................................................. 191
Deploying with Oracle 10g......................................................... 199
Using the MicroStrategy Web Administrator Console................ 205
Intelligence Servers page .................................................... 206
Narrowcast Server Integration page .................................... 211
Diagnostics page ................................................................. 211
Security ................................................................................ 218
9. Setting up Documents Introduction.............................................................................. 221

and HTML Documents
Before you start ......................................................................... 222
Overview.................................................................................... 223
Setup for creating and executing HTML documents.................. 224
Setup for executing existing HTML documents ......................... 227
Setup for executing Report Services documents....................... 228
10. Automated Introduction.............................................................................. 229

Installation and
Methods of installation ............................................................... 231
Configuration on
Windows Response.ini file installation................................................. 231
Silent installation .................................................................. 231
Installation log file ...................................................................... 232
Installing and configuring with a response.ini file....................... 233
Configuring a response.ini file for installation ...................... 233
Configuring a response.ini file for the Configuration Wizard 257
Uninstalling using a response.ini file.......................................... 263
Example of a response.ini file .............................................. 263
Silent installation........................................................................ 265
Silent installation of a hotfix ................................................. 271
11. Automated Introduction.............................................................................. 273

Installation and
Silent installation........................................................................ 274
Configuration on UNIX
viii 2005 MicroStrategy, Inc.

Creating an options file ........................................................ 274

Settings that can be changed .............................................. 275
Silent installation output ....................................................... 279
Configuring through command line mode.................................. 279
Creating a response.ini file for the Configuration Wizard..... 280
Using the response.ini file through the Configuration Wizard ....
288
Configuring MicroStrategy using the command line mode .. 289
Configuring metadata and statistics tables .......................... 291
Setting up MicroStrategy Intelligence Server....................... 298
Creating a project source..................................................... 304
12. Adding or Removing Introduction.............................................................................. 307

MicroStrategy
Adding or removing MicroStrategy components on Windows ... 308
Components
Reinstalling MicroStrategy components on Windows................ 310
Reinstalling MicroStrategy Office......................................... 311
Uninstalling MicroStrategy components on Windows................ 312
Uninstalling MicroStrategy Office......................................... 313
Uninstalling MicroStrategy components on UNIX and Linux ..... 314
Uninstalling MicroStrategy Intelligence Server on UNIX and
Linux .................................................................................... 314
Uninstalling MicroStrategy Web Universal on UNIX and Linux..
315
A. Managing Licenses Introduction.............................................................................. 317

Verifying Named user licenses .................................................. 318
Verifying CPU licenses .............................................................. 319
MicroStrategy License Manager ................................................ 321
Determining the number of licenses in use................................ 321
Upgrading a license ................................................................... 322
B. ODBC and DSNs Introduction.............................................................................. 325

Setting up ODBC ....................................................................... 326
Configuring ODBC with MicroStrategy for Windows............ 328
Configuring ODBC with MicroStrategy for UNIX.................. 328
Creating DSNs........................................................................... 330
Using the MicroStrategy Connectivity Configuration Wizard 331
Using the MicroStrategy Configuration Wizard .................... 334
2005 MicroStrategy, Inc. ix

Using the Microsoft ODBC Administrator............................. 336

Creating DSNs for individual ODBC drivers......................... 338
Testing the ODBC connectivity .................................................. 357
Parameters from ODBC.ini ........................................................ 359
Oracle Wire Protocol............................................................ 361
DB2 Wire Protocol ............................................................... 362
Informix Wire Protocol.......................................................... 366
Sybase Wire Protocol .......................................................... 367
SQL Server Wire Protocol.................................................... 368
ODBC .................................................................................. 369
Red Brick 6.x ....................................................................... 369
SybaseIQ ............................................................................. 370
Teradata-Server................................................................... 370
Informix XPS ........................................................................ 372
C. Advanced Warehouse Introduction.............................................................................. 375

Catalog Usage
Warehouse Catalog usage ........................................................ 376
What should I know before I use the Warehouse Catalog?. 376
Accessing Warehouse Catalog............................................ 377
Warehouse Catalog layout .................................................. 377
Warehouse Catalog settings................................................ 381
Ignore table name space settings ........................................ 385
Troubleshooting Warehouse Catalog .................................. 386
D. Advanced Hardware Introduction.............................................................................. 389

Considerations
Small MicroStrategy production system configuration............... 389
Medium MicroStrategy production system configuration ........... 393
Large MicroStrategy production system configuration............... 396
E. Troubleshooting Introduction.............................................................................. 399

Installing MicroStrategy for UNIX............................................... 399
Mounting CD-ROMs............................................................. 400
General installation errors.................................................... 403
Server port number errors.................................................... 403
DSN connection errors......................................................... 404
Permission errors................................................................. 404
Troubleshooting LDAP authentication ....................................... 405
LDAP authentication mode problems .................................. 406
LDAP functionality problems................................................ 407
x 2005 MicroStrategy, Inc.

LDAP frequently asked questions........................................ 409
F. Example of a Modified Introduction.............................................................................. 411

web.xml File
Example of modified web.xml file .............................................. 411
Glossary ................................................................................... 421
Index ......................................................................................... 427
2005 MicroStrategy, Inc. xi

xii 2005 MicroStrategy, Inc.

PREFACE
Document description
The MicroStrategy Installation and Configuration Guide

provides comprehensive information on how to install and
configure MicroStrategy software, as well as basic
maintenance guidelines. This guide gets you started using the
UNIX, Linux, and Windows version of the MicroStrategy
platform.
It assumes a basic understanding of how to use UNIX either

from a UNIX server or by using a viewer on a PC. For tasks
that require advanced System Administration commands,
this document assumes you are either familiar with those
commands or can contact your System Administrator.
The appendixes contain the following additional reference

information, which you may require depending on your
specific needs:
managing MicroStrategy licenses
configuring ODBC and DSNs
warehouse catalog usage and settings
hardware related configuration information
modified web.xml file example
troubleshooting
2005 MicroStrategy, Inc. xiii

Preface Installation and Configuration Guide
Technical terms that need more clarification are defined in

the glossary section of this guide.
Who should use this guide

This document is designed for System Administrators who
install, configure, and maintain MicroStrategy software on
the UNIX, Linux, and Windows operating system.
Prerequisites
Before working with this document, you should be familiar
with
the nature and structure of the data to use for your

business intelligence application
the basics of the UNIX operating system
Objectives
After reading this manual, you will be able to
install MicroStrategy software on a UNIX, Linux, and
Windows system
configure Intelligence Server and Web Universal for use

by clients
provide maintenance support for MicroStrategy on a
UNIX, Linux, and Windows operating system
xiv Who should use this guide 2005 MicroStrategy, Inc.

Installation and Configuration Guide Preface
About this book

This book is divided into chapters and reference appendices.
The chapters provide conceptual information about
all MicroStrategy components
installation and configuration procedures
troubleshooting and maintenance guidelines
Each chapter begins with a brief overview of the content

within that chapter. The chapter is then divided into
subsections organized in the best method to promote
learning. If applicable, a series of steps may be provided to
carry out tasks and to facilitate the learning process.
The appendixes contain additional reference information,

which you may or may not require depending on your specific
needs.
When you are looking for specific information, you can use
the table of contents or index to quickly locate the
information.
Typographical standards
There are different typographical standards for the online
and printed documentation, and only for printed
documentation.
For online and printed documentation

MicroStrategy online and hard copy documentation follows
presentation conventions and cues to help you locate,
identify, and understand important concepts and procedures.
The following table lists these conventions.
2005 MicroStrategy, Inc. About this book xv

Type Indicates
bold button names, check boxes, dialog boxes,

options, lists, and menus that are the focus of
actions or part of a list of such GUI elements and
their definitions
text to be entered by the user
italic new terms defined within the text and in the

glossary
names of other product manuals
when part of a command syntax, indicates
variable information to be replaced by the user
Courier calculations
font code samples
registry keys
path and file names
URLs
messages displayed in the screen
UPPERCASE keyboard command key (such as ENTER)

shortcut key (such as CTRL+V)
+ A keyboard command that calls for the use of more

than one key (for example, SHIFT+F1)
xvi Typographical standards 2005 MicroStrategy, Inc.

For printed documentation only

The following are explanations of the font style changes,
icons, and different types of notes that you may see in this
user guide.
Actions
References to screen elements and keys that are the focus of

actions are in bold Arial font style. Following is an example:
1 Click Select Warehouse.
Code
References to code, formulas, or calculations within

paragraphs are formatted in regular Courier New font style.
Following is an example:
Sum(sales)/number of months
Data entry
References to literal data you must type in an exercise or

procedure are in bold Arial font style. References to data you
type in that could vary from user to user or system to system
are in bold italic Arial font style. Following is an example:
Type cmdmgr -f scriptfile.scp and press ENTER.
Type cp /path/to/file /path/to/newfile
Keyboard keys
References to a keyboard key or shortcut keys are in

uppercase letters. Following is an example:
To bold the selected text, press CTRL+B.
2005 MicroStrategy, Inc. Typographical standards xvii

New terms
New terms to note are in regular italic font style. These terms
are defined when they are first encountered in the course
material. Following is an example:
The aggregation level is the level of calculation for the
metric.
Notes and warnings
This note icon indicates helpful information.

This warning icon calls your attention to very
important information that should be read before
continuing.
Heading icons
The following heading icons are used to indicate specific

practice and review sections:

Precedes a Case Study. Cases Studies are real-life examples
from companies that are using MicroStrategy products.

Precedes a Business Scenario. Business Scenarios are
examples from the MicroStrategy Tutorial. They explain how
to accomplish complex tasks using MicroStrategy.
xviii Typographical standards 2005 MicroStrategy, Inc.

Resources
Product documentation
MicroStrategy includes a full set of product manuals,
designed to help you find the information you require to
install, configure, design, and administer your business
intelligence and narrowcast systems, as well as full SDK
documentation to help you extend and customize
MicroStrategy and integrate it with your existing
applications.
A list of documentation links is available to access all

documentation installed from your CD-ROM. Most of these
documents have been provided in Acrobat Portable
Document format (PDF).
Adobe Acrobat Reader is required to view these

documents. If you do not have Acrobat Reader
installed on your computer, you can download it from
http://www.adobe.com.
Online documentation
To access an online manual
1 From the UNIX File Manager, navigate to the

MicroStrategy directory, then to the Documentation
directory.
2 Double-click the Product_Manuals.htm file to see the list

of available manuals in PDF format.
3 Click the link for the desired manual.
4 Some information is provided in HTML help format.

When you select one of these guides, the Download file
dialog box will open. Select the Open this file from its
current location option and click OK.
2005 MicroStrategy, Inc. Resources xix

IfAcrobat
bookmarks are not visible on the left side of an
document, select Bookmarks and Page from
the View menu, then select the topic and section you
want to see. You can also scroll from the title page of
the guide to its table of contents, and select from there
the topic you want to read.
The following documents are provided on your CD-ROM in

Acrobat Portable Document format (PDF):
MicroStrategy Overview
Introduction to MicroStrategy: Evaluation Guide
MicroStrategy Quick Start Guide
Manuals for Query, Reporting, and Analysis

Products
MicroStrategy Installation and Configuration Guide
MicroStrategy Upgrade Guide
MicroStrategy Basic Reporting Guide
MicroStrategy Advanced Reporting Guide
MicroStrategy Document Creation Guide

MicroStrategy System Administration Guide
MicroStrategy Analytical Functions Reference
MicroStrategy Web SDK
The Web SDK is available in the MicroStrategy

Developer Library, which is sold as part of the
MicroStrategy SDK.
Manuals for Information Delivery and Alerting

Products
MicroStrategy Narrowcast Server Getting Started Guide
xx Resources 2005 MicroStrategy, Inc.

MicroStrategy Narrowcast Server Installation and

Configuration Guide
MicroStrategy Narrowcast Server Application Designer

Guide
MicroStrategy Narrowcast Server System

Administrator Guide
MicroStrategy Narrowcast Server Upgrade Guide
Manuals for Analytics Modules

Business Intelligence Developer Kit (BIDK) Installation
and Porting Guide
Customer Analysis Module Reference
Sales Force Analysis Module Reference
Web Traffic Analysis Module Reference
Financial Reporting Analysis Module Reference
Sales and Distribution Analysis Module Reference
Human Resources Analysis Module Reference
Software Development Kits

MicroStrategy Developer Library
MicroStrategy Web SDK
The Web SDK is available in the MicroStrategy

Developer Library, which is sold as part of the
MicroStrategy SDK.
Narrowcast Server SDK Guide
2005 MicroStrategy, Inc. Resources xxi

International support
MicroStrategy supports several locales. Support for a locale
typically includes native database and operating system
support, support for date formats, decimal formats, currency
symbols etc. and availability of translated interfaces and
documentation. The level of support is defined in terms of the
components of a MicroStrategy Business Intelligence
environment. A MicroStrategy Business Intelligence
environment consists of the following components,
collectively known as a configuration:
warehouse, metadata, and statistics databases
MicroStrategy Intelligence Server
MicroStrategy Web Server
MicroStrategy Desktop client
Web browser
MicroStrategy is certified in homogeneous configurations

(where all the components lie in the same locale) in the
following languagesEnglish (US), French, German, Italian,
Japanese, Korean, Portuguese (Brazilian), Spanish, Chinese
(simplified) and Swedish.
For information on the exact languages, see the

Readme file.
MicroStrategy also provides limited support for

heterogeneous configurations (where some of the
components may lie in different locales). Please contact
MicroStrategy Technical Support for more details.
A translated user interface is available in each of the above

languages. In addition, translated versions of the online help
files and product documentation are available in several of
the above languages.
xxii International support 2005 MicroStrategy, Inc.

User assistance
The following paragraphs describe the types of assistance
available to answer questions you may have regarding
MicroStrategy products.
Online help
MicroStrategy provides several modes of access to online
help:
From the Help menu, by selecting Contents and Index to

see the main table of contents for the help system
By pressing F1 to see context-sensitive help addressing

the function or task you are currently performing
Netscape
help.
browser is required for viewing the online
Technical Support
If you have questions about a specific MicroStrategy product,
you should:
1 Consult the product guides, online help, readme files, and

release notes
2 Consult the online knowledge base at

http://www.microstrategy.com/support/
k_base/index.asp
Aprobably
technical administrator in your organization can
help you resolve some of your issues
immediately.
2005 MicroStrategy, Inc. User assistance xxiii

3 If the resources listed in steps 1 and 2 do not provide you

with a solution, contact MicroStrategy Technical Support
directly. To ensure the most effective and productive
relationship with MicroStrategy Technical Support,
review the Policies and Procedures document posted at
http://www.microstrategy.com/Support/
Policies. Please refer to the terms of your purchase
agreement to determine the type of support available to
you.
The table on the following page shows where, when, and how
to contact MicroStrategy Technical Support. If you are unable
to reach MicroStrategy Technical Support by phone during
the hours of operation, you have the option to leave a
voicemail message or send electronic mail.
xxiv User assistance 2005 MicroStrategy, Inc.

North E-mail: support@microstrategy.com

America Web: https://support.microstrategy.com
Fax: (703) 8488710
Phone: (703) 8488700
Message: (703) 848-8709
Hours:
9:00 A.M.7:00 P.M. Eastern Time (14000000 GMT),
MondayFriday except holidays
Europe, the E-mail: eurosupp@microstrategy.com

Middle East, Web: https://support.microstrategy.com
and Africa Fax: +44 (0) 208 396 0001
(EMEA) The European Technical Support Centre is closed on certain
public holidays. These holidays reflect the national public
holidays in each country.
Phone:
United Kingdom: +44 (0) 208 396 0085
Benelux: +31 20 346 9210
Finland: +35 8 9 6937 9620
France: +33 1 41 91 86 49
Germany: +49 69 95096206
Ireland: +35 3 1242 1522
Italy: +39 02696 33 456
Spain: +34 91 406 90 10
International distributors: +44 (0) 208 396 0080
Hours:
United Kingdom: 9:00 A.M.6:00 P.M. GMT, Monday-Friday
except holidays
Mainland Europe: 9:00 A.M.6:00 P.M. CET, Monday-Friday
except holidays
Asia Pacific E-mail: apsupport@microstrategy.com

Web: https://support.microstrategy.com
Fax: +81 3 5456 5464
Phone:
APAC (except Korea): +81 3 5456 5618
Korea: +82 2 565 2525
Hours:
9:00 A.M.6:00 P.M. JST (Tokyo), Monday-Friday except
holidays
Latin America E-mail: latamsupport@microstrategy.com

Web: https://support.microstrategy.com
Fax: +55 11 3044 4088
Phone: LATAM (except Argentina): +55 11 3054 1010
Argentina: 0 800 444 MSTR
Hours:
9:00 A.M.6:00 P.M. (San Paulo), MondayFriday except
holidays
2005 MicroStrategy, Inc. User assistance xxv

Technical Support may be obtained by a Customers Support

Liaisons. A "Support Liaison" is defined as a person whom
the customer has designated as a point-of-contact with
MicroStrategys support personnel. All customer inquiries
and case communications must come through these named
individuals. The customer may designate two employees to
serve as their Support Liaisons. Customers may change their
Support Liaisons two times per year, if necessary, so long as
they provide written notice to MicroStrategy Technical
Support of such change.
During the course of troubleshooting and researching issues,

MicroStrategy Technical Support personnel may make
recommendations that require administrative privileges on
the MicroStrategy projects or that assume that the designated
liaison has a security level that permits them to fully
manipulate the MicroStrategy projects and has access to
potentially sensitive project data such as security filter
definitions. Although not a requirement, we recommend that
customers only designate Support Liaisons who have
permissions to be MicroStrategy project administrators. This
will eliminate security conflicts and improve case resolution
time.
When contacting MicroStrategy Technical Support, please

provide the following information:
name (first and last)

company
customer site (if different from company)
phone and fax numbers
e-mail address
MicroStrategy software product(s) being used, including

version nubmer(s)
error message(s)
brief description of the case
priority of the case
steps taken to troubleshoot the case thus far
xxvi User assistance 2005 MicroStrategy, Inc.

If the Support Liason is unable to reach MicroStrategy

Technical Support, the Support Liason can leave a voice mail
message or contact Technical Support via e-mail. The
Support Liason should include the following information in
his/her message:
name
company
brief description of the case
preferred contact method and contact information
If this is your first call, you should also be prepared to provide

the following:
street address
phone number
fax number
e-mail address
To help your Technical Support representative work with you

to resolve the problem promptly and effectively, be prepared
to provide the following additional information:
issue numberplease keep a record of the number

assigned to each problem logged with MicroStrategy
Technical Support, and be ready to provide it when
inquiring about an existing issue
software version and product registration numbers of the
MicroStrategy software products you are using
2005 MicroStrategy, Inc. User assistance xxvii

problem description:
What causes the condition to occur?
Does the condition occur sporadically or each time a

certain action is performed?
Does the condition occur on all machines or just on

one?
When did the condition first occur?
What events took place immediately prior to the first

occurrence of the condition (for example, a major
database load, a database move, a software upgrade)?
If there was an error message, what was its exact
wording?
What steps have you taken to isolate and resolve the

issue? What were the results?
system configuration (the information needed for this

purpose depends on the nature of the problem; not all
items listed may be necessary):
computer hardware specifications (processor speed,

RAM, disk space, and so on)
network protocol used
ODBC driver manufacturer and version
database gateway software version

(for MicroStrategy Web-related problems) browser
manufacturer and version
(for MicroStrategy Web-related problems) Web server
manufacturer and version
If the issue requires additional investigation or testing, you

and the MicroStrategy Technical Support representative
should agree on certain action items to be performed. You
should perform any agreed-upon actions before contacting
Technical Support again regarding the issue. If the Technical
Support representative is responsible for an action item, you
may call Technical Support at any time to inquire about the
status of the issue.
xxviii User assistance 2005 MicroStrategy, Inc.

Feedback
Please send any comments or suggestions about user
documentation for MicroStrategy 7 products to:
documents@microstrategy.com
Send suggestions for product enhancements to:
support@microstrategy.com
When you provide feedback to us, please include the name

and version of the products you are currently using. Your
feedback is important to us as we prepare for future releases.
2005 MicroStrategy, Inc. Feedback xxix

xxx Feedback 2005 MicroStrategy, Inc.

1
1. INTRODUCTION TO
MICROSTRATEGY
Introduction
MicroStrategy business intelligence tools help organizations

to monitor, report, and analyze all of their enterprise data. It
helps you make decisions based upon the data within your
organizations enterprise data warehouse.
This chapter provides an overview of the different

MicroStrategy components and products so you can decide
what you need to install. It also provides details on supported
functionality. It gives you a road map to using this guide for
installing MicroStrategy on Windows, UNIX, and Linux.
This chapter includes the following sections:
MicroStrategy components
How to use this book
2005 MicroStrategy, Inc. 1

1 Introduction to MicroStrategy Installation and Configuration Guide
MicroStrategy has a range of products that you can install on
different operating systems. Depending on the type of setup
you have, you can install various combinations of
MicroStrategy components. The components described in
this section offer a complete set of tools for creating,
deploying, supporting, and maintaining the business
intelligence applications. This section briefly describes the
most common setups and the components required for each.
Ifandyousubarecomponents,
familiar with MicroStrategy components
you can skip this section and go
to How to use this book, page 14.
Common Setups for MicroStrategy

The following are the common MicroStrategy configuration
and the components required for the setups:
Common configurations: This setup includes

MicroStrategy Desktop Products, MicroStrategy
Administrator, MicroStrategy Intelligence Server,
MicroStrategy Web Services, and MicroStrategy
Tutorial-Reporting.
MicroStrategy Web Universal configuration: In addition
to the components required for the common
configuration, you also need to install MicroStrategy Web
Universal components.
MicroStrategy NCS: In addition to the components
required for the common configuration, you also need to
install MicroStrategy Narrowcast Server components.
MicroStrategy SDK: In addition to the components

required for the common configuration, you also need to
install MicroStrategy SDK component.
2 MicroStrategy components 2005 MicroStrategy, Inc.

Installation and Configuration Guide Introduction to MicroStrategy 1
Note the following:

Apart from the components listed above, you can also
install MicroStrategy Office and MicroStrategy
eTrainer for Web.
The details regarding each component and their sub

components is described in the sections that follow.
MicroStrategy Desktop Products
MicroStrategy Desktop provides analytical features designed

to facilitate and perform the deployment of reports. It
governs application objects such as reports, filters, and
metrics.
MicroStrategy Desktop also enables you to create application

objects. The application objects are built on the schema
objects that are created in Architect. These application
objects are used to analyze and provide insight into relevant
data. The following sections provide a brief description of the
sub-components for these products.
MicroStrategy Desktop Products sub-components
MicroStrategy Desktop Analyst is a simplified version of

MicroStrategy Desktop, providing the basic interactive
reporting functionality required by managers.
MicroStrategy Desktop Designer is a full-featured version

for power analysts and application developers. With a full
range of analytical functionality, a rich library of
functions, and intelligent workflow, Desktop Designer is
well suited for demanding users.
MicroStrategy Architect provides Project Designer
functionality such as attribute, fact, hierarchy, and project
creation and modification. Another sub-component of
Architect is MicroStrategy Project Builder, which allows
quick creation of simple projects. These projects can be
used for easy creation of prototypes for proof-of-concept
purposes.
MicroStrategy Server Administrator provides

administrative functionality such as system monitoring,
cache management, and user and group management.
2005 MicroStrategy, Inc. MicroStrategy components 3

For details about the specific features that the different

Desktop versions include, review the feature comparison
chart at the following website:
http://www.microstrategy.com/Software/
Products/Desktop/feature_comparison.asp
For information on various options present in MicroStrategy

Desktop to create and run reports, refer to the MicroStrategy
Basic Reporting Guide. After you are familiar with basic
Desktop concepts, refer to the MicroStrategy Advanced
Reporting Guide for information on advanced Desktop
functionality.
MicroStrategy Administrator
The sub components of MicroStrategy Administrators are as

follows:
MicroStrategy Command Manager is an application

designed to simplify and automate administration tasks,
such as add, delete, or update enterprise-level data
associated with large numbers of users and user groups.
Additionally, Command Manager allows you to manage
various configuration settings within the MicroStrategy
platform.
MicroStrategy Object Manager provides complete life

cycle management capabilities for MicroStrategy
environments.
MicroStrategy Enterprise Manager allows viewing and
analysis of MicroStrategy product usage and system
performance.
IfWindows
you install MicroStrategy Administrator on
XP, the option to install Enterprise
Manager is not displayed.
For more information about MicroStrategy Administrator

and its components, see the MicroStrategy System
Administration Guide.

The important functions of the MicroStrategy Intelligence

Server are
sharing data
protecting the information in the metadata
sharing objects
The MicroStrategy Intelligence Server also provides a library

of over 150 different sophisticated mathematical and
statistical functions, and more can be added. See the
MicroStrategy Analytical Functions Reference for details
about these functions.
All other products in the platform work in conjunction with

the MicroStrategy Intelligence Server and benefit from its
broad functionality.
MicroStrategy has different editions of Intelligence Server,

which are
Standard edition
Enterprise edition
Universal edition
The Standard edition and Enterprise edition are Windows

versions of MicroStrategy Intelligence Server, whereas the
Universal edition is platform-independent. It can be installed
on various operating systems such as Windows, UNIX, Linux,
and so on. The Standard, Enterprise, and Universal editions
of MicroStrategy Intelligence Server share a common code
base and run reports identically. However, there are a few
functionality differences. The following table highlights the
major differences between them.

Intelligence Server
Intelligence Server
Functionality Standard and
Universal Edition
Enterprise Editions
Windows Not supported as Supported

Authentication single sign-on, but
Active Directory
Services are
supported
Custom Function Not supported Supported

Plug-in
Performance MicroStrategy Microsoft Windows

Monitoring Java-based Control MMC Performance
Center Counters
Diagnostics Debug Not supported Supported

Monitor
ETL Support Informatica MX2 not Informatica MX2

supported supported
ODBC DSN Creation MicroStrategy ODBC Microsoft Windows

Administrator ODBC Data Source
Administrator
Intelligence Server MicroStrategy SDK Supported

SDK applications can be
run against
Intelligence Server
Universal Edition, but
they need to be
executed from a
Windows machine
Microsoft Access Not supported Supported
For a detailed description of all the features of MicroStrategy

Intelligence Server, refer to the MicroStrategy System

MicroStrategy Web and Web Universal

components
MicroStrategy Web provides users with a highly interactive

environment and a low-maintenance interface for reporting
and analysis. Using the Web interface, users can access,
analyze, and share corporate data through any Web browser
on any operating system. MicroStrategy Web provides ad hoc
querying, industry-leading analysis, quick deployment, and
rapid customizability, making it even easier for users to make
informed business decisions.
In addition to the powerful functionality that MicroStrategy

Web offers, MicroStrategy Web Universal provides the added
benefit of working with
operating systems, such as Sun Solaris and IBM AIX.
application servers, such as BEA WebLogic and IBM

WebSphere.
Web servers and Web browsers.
MicroStrategy Web and Web Universal are available in the

following versions:
The full-featured version contains all the powerful

features that let report designers create Intelligent Cubes
reports for their users. Full reporting, ad hoc reporting,
and OLAP capabilities are integrated with seamless
ROLAP analysis.
The simplified version provides ad hoc analysis from
Intelligent Cubes with interactive slice-and-dice OLAP.
The Enterprise Reporting version enables viewing of
scheduled reports and interactive slice-and-dice, with
printing and e-mail subscription to reports.

MicroStrategy Web products include Web Professional, Web

Analyst, and Web Reporter. The following table lists the
versions that the various MicroStrategy Web products
support.
Enterprise
MicroStrategy Full-featured Simplified
Reporting
Products version version
version
Web Professional or Supported Supported Supported

Web Universal
Professional
Web Analyst or Web Not Supported Supported Supported

Universal Analyst
Web Reporter or Not Supported Not Supported Supported

Web Universal
Reporter
For detailed information about using the MicroStrategy Web

reporting environment, refer to the online help provided on
the MicroStrategy Web interface.
For information about configuring and tuning MicroStrategy

Web, refer to the MicroStrategy System Administration
Guide.
MicroStrategy Web Services
MicroStrategy Web Services is a self-contained business

function that operates over the Internet. It is based on
industry standards and is designed to work together with
similar components. It provides an alternative way to access
the MicroStrategy business intelligence platform using the
latest technologies such as ASP.NET, JNI, Java and Web
protocols, such as Apache Axis. MicroStrategy Web Services
is an easy-to-deploy service that is accessible through
MicroStrategy Office. It also implements an open API that

allows customers to quickly develop Web reporting

applications accessing MicroStrategy Intelligence Server. It is
a discrete business process that
exposes and describes itself
Other applications can understand and use this

functionality.
easily allows other services to locate it on the Web
It can be easily located through a type of yellow pages.
can be invoked
After it is located and examined, other services can invoke

it using an Internet standard protocol.
returns a response
When service is provided, the results are passed back to

the requesting application using the same Internet
standard protocol.
For more information on MicroStrategy Web Services, refer

to the MicroStrategy Web Services Administration Guide.
MicroStrategy SDK
The MicroStrategy SDK allows you to easily adapt and

integrate MicroStrategy functionality into your application or
modify the standard interface or functionality. It provides
access to the entire platform and includes the necessary
services and utilities for building a business
intelligence-enabled application.

The MicroStrategy SDK consists of the following

components:
A comprehensive set of open Application Programming

Interfaces (APIs) that include
the COM-based client-server API
the XML-based Web API with support for Java/COM
the Narrowcast Server API
the Office API
Complete SDK documentation for all the MicroStrategy

products and reference guides, such as Javadocs for the
APIs.
Development tools that contain the source code and
sample application code for typical customization tasks.
The SDK also provides development tools and
production-ready utilities that reduce code creation and
maintenance and help you build customized applications.
MicroStrategy Office
MicroStrategy Office lets every Microsoft Office user run,

edit, and format any MicroStrategy report directly from
within Microsoft applications such as Excel, PowerPoint,
and Word. MicroStrategy Office is designed using Microsoft
.NET technology and accesses the MicroStrategy business
intelligence platform using XML and Web Services.
MicroStrategy Office gives business users open and

straightforward access to the full functionality of the
MicroStrategy platform from familiar Microsoft Office
applications. MicroStrategy Office serves as a Microsoft
add-in, with MicroStrategy functionality exposed as a single
toolbar in Microsoft Office applications.
To learn how to use other Microsoft Office tools, refer to the

MicroStrategy Office online help.

MicroStrategy Narrowcast Server
MicroStrategy Narrowcast Server proactively distributes

personalized information to employees, business partners,
and customers through a variety of devices, including mobile
phones, PDAs, e-mail, Web pages, and pagers. The
distribution of personalized messages and targeted offers is
triggered according to predefined schedules and exception
criteria, delivering information in a timely and convenient
manner. MicroStrategy Narrowcast Server also provides a
self-subscription portal, easing administrative
responsibilities and empowering information consumers to
choose the information they receive. Narrowcast Server can
draw information from relational or non-relational sources.
For information on Narrowcast Server sub-components, refer

to the MicroStrategy Narrowcast Server Installation and
Configuration Guide.
MicroStrategy eTrainer for Web
MicroStrategy eTrainer is a Web-based training module that

gives you the in-depth knowledge and hands-on experience
you require to work with MicroStrategy Web or Web
Universal.
Each lesson of the MicroStrategy eTrainer course describes a

function of MicroStrategy Web and breaks it into a
combination of informational screens and task-based tests.
Each lesson has an appropriate and graded activity. This
training gives you the option to pick and choose topics that
enhance your performance, ultimately leading to the success
of the business intelligence or e-business project. With the
included database feature, managers can control access to the
training and monitor progress and achievement of users
going through the eTrainer module to learn about
MicroStrategy Web or Web Universal.
For more information, refer to the MicroStrategy ReadMe

files.

MicroStrategy Analytics Modules
MicroStrategy Analytics Modules are a set of packaged

analytic components built using the MicroStrategy platform.
The modules can be mapped to a different warehouse or used
as starter kits to develop custom applications. Each module
consists of a MicroStrategy project in a metadata, a reference
guide, and a default data model. Examples of the Analytics
Modules are as follows:
Customer Analysis Module focuses on customer-centric

information
Sales Analysis Module focuses on information captured

during the sales process
Web Traffic Analysis Module provides in-depth analysis

of website information captured in Web logs
Financial Reporting Analysis Module provides in-depth

analysis of financial information captured by general
ledgers, forecasting systems, and data on actual amounts,
payables, and receivables
MicroStrategy Tutorial Reporting
MicroStrategy Tutorial is a sample MicroStrategy project

with a metadata and warehouse, and a set of demonstration
applications designed to illustrate the platform's rich
functionality.
The theme of the MicroStrategy Tutorial project is a retail

store for the years 2003 - 2004 that sells electronics, books,
movies, and music. The key features include:
Five hierarchies: Customer, Geography, Products,

Promotions, and Time. Each hierarchy can be viewed
graphically through MicroStrategy Desktop and Web
(through documents).
A large number of customers and items purchased.
Five reporting areas: Human Resources, Inventory,

Financial, Product Sales, and Supplier.

Options to create reports from MicroStrategy Web or

Desktop focusing on a particular analysis area, such as
Customer, Inventory, Time, Products, Category,
Employee, or Call Center.
For more information on the MicroStrategy Tutorial, refer to

the MicroStrategy Advanced Reporting Guide.
SequeLink ODBC Socket Server
SequeLink is a complete, end-to-end solution for configuring

and managing data access across virtually any number of
data stores, operating systems, and deployment options. It
provides a universal client for ODBC and JDBC, and a
centralized console for configuring and managing data access
from a single point of control. SequeLink creates two NT
services: SLAgent 54, which is the Administrator, and
SLSocket54, which is the Server.
SequeLink ODBC Socket Server is installed

automatically if you install MicroStrategy Narrowcast
Server. You do not need to install this if you are not
installing MicroStrategy Narrowcast Server.

How to use this book

This guide provides information on how to install and
configure MicroStrategy products on Windows UNIX, and
Linux. To help you navigate through this guide, the following
section lists down the chapters that you should refer to
depending on the platform on which you are installing the
products. It also provides a brief overview of each chapter. It
is recommended that you read this section before performing
an installation.
You must read Chapter 2, Planning Your Installation,

whether you are installing MicroStrategy on Windows or any
other operating system. It provides details on things to
consider before performing an installation, such as hardware
and software recommendations and system sizing guidelines.
Installing MicroStrategy on Windows

If you are installing MicroStrategy on Windows, you should
refer to the following chapters sequentially.
Chapter 3, Installing MicroStrategy on Windows: This
chapter describes the procedures for installing the
MicroStrategy products necessary to get your business
intelligence application running in Windows
environment.
Asautomated
an alternative, you can perform a fully
installation and configuration. For
more information refer to Chapter 10, Automated
Installation and Configuration on Windows.
Chapter 5, Configuring MicroStrategy Intelligence Server:
After installing MicroStrategy products, you must use the
MicroStrategy Configuration Wizard to configure the
MicroStrategy metadata repository and statistics tables,
Intelligence Server, and project sources. This chapter
describes the steps used to configure an installed
MicroStrategy suite of products using the MicroStrategy
Configuration Wizard.
14 How to use this book 2005 MicroStrategy, Inc.

Chapter 6, Creating a Project: After installing and

configuring MicroStrategy products, you must create your
own projects to start using the product with your own
data. This chapter tells you what a project is and how you
can create a project using MicroStrategy Desktop and
Project Builder.
Chapter 7, Deploying Your Project with MicroStrategy

Web: You can deploy the project that you have created to
your user community using MicroStrategy Web. This
chapter describes the steps to connect the ASP.NET
version of MicroStrategy Web with MicroStrategy
Intelligence Server on Windows.
You can deploy your project with either

MicroStrategy Web or Web Universal.
MicroStrategy Web Universal is platform-
independent, whereas MicroStrategy Web can be
installed only on Windows.
Chapter 8, Configuring and Deploying MicroStrategy Web

Universal: You can deploy your project to your user
community using MicroStrategy Web Universal. This
chapter provides information on how to deploy and
configure MicroStrategy Web Universal on Windows and
other operating systems with various Web and application
servers. If you are installing on Windows, refer to the
following sections:
Deploying with Tomcat (Linux)
Deploying with Oracle 10g

Using the MicroStrategy Web Administrator Console
Chapter 10, Automated Installation and Configuration on

Windows: As an alternative to the regular installation
described in Chapter 3, Installing MicroStrategy on
Windows, you can perform a fully automated and
unattended installation including customization and
configuration routines available with the product. This
chapter describes different types of unattended and
automated installations and provides steps to perform
these installations on Windows.
2005 MicroStrategy, Inc. How to use this book 15

Chapter 12, Adding or Removing MicroStrategy

Components: This chapter describes the steps to add and
remove MicroStrategy components on Windows, as well
as other operating systems. If you are performing an
installation on Windows, refer to the following sections:
Adding or removing MicroStrategy components on

Windows.
Reinstalling MicroStrategy components on Windows.
Uninstalling MicroStrategy components on Windows.
Installing MicroStrategy on UNIX and Linux

If you are installing MicroStrategy on UNIX or Linux
operating systems, you should refer to the following chapters
sequentially.
Chapter 4, Installing MicroStrategy on UNIX and Linux:

This chapter describes the procedures for installing the
MicroStrategy products necessary to get your business
intelligence application running on a UNIX or Linux
environment.
Chapter 5, Configuring MicroStrategy Intelligence Server:

After installing MicroStrategy products, you must use the
MicroStrategy Configuration Wizard to configure the
MicroStrategy metadata repository and statistics tables,
Intelligence Server, and project sources. This chapter
addresses the processes necessary to configure an
installed MicroStrategy suite of products using the
MicroStrategy Configuration Wizard.

Universal: This chapter provides information on how to
deploy and configure MicroStrategy Web Universal on the
UNIX and Linux platform with various Web and
application servers. If you are installing on UNIX or Linux
platform, refer to the following sections:
Deploying with WebLogic and Apache.
Deploying with WebSphere 5.x and IBM HTTP Server.

Deploying with Sun ONE (iPlanet) 8.0.
Using the MicroStrategy Web Administrator Console.
Chapter 9, Setting up Documents and HTML Documents:

This chapter explains the setup required for the
Intelligence Server to create and execute HTML
documents and documents. It also describes the steps to
create this setup.
Chapter 11, Automated Installation and Configuration on

UNIX: As an alternative to the normal installation
described in Chapter 4, Installing MicroStrategy on
UNIX and Linux on other operating systems, you can
perform a fully automated and unattended installation
without using the graphical user interface. This chapter
describes different types of unattended and automated
installations and steps to perform these installations on
UNIX.
Chapter 12, Adding or Removing MicroStrategy

Components: This chapter describes the steps to add and
remove MicroStrategy components on all supported
operating systems. For UNIX and Linux platforms, refer
to the following section:
Uninstalling MicroStrategy components on UNIX and
Linux
2005 MicroStrategy, Inc. How to use this book 17


2
2. PLANNING YOUR
INSTALLATION
Introduction
This chapter describes important information regarding

MicroStrategy installation that should be taken into
consideration before you start installing MicroStrategy
products.
This chapter has the following sections:
Upgrade considerations
Installation prerequisites
Installation considerations
Methods of installation
Licensing information
Next steps

2 Planning Your Installation Installation and Configuration Guide
Upgrade considerations
If you have MicroStrategy products installed and want to
upgrade them, refer to the MicroStrategy Upgrade Guide.
The upgrade procedures on Windows and UNIX are covered
in this guide. It is recommended that you read this guide
before deciding to upgrade an existing database.
Installation prerequisites
Before you install MicroStrategy, you must have the
following:
MicroStrategy Intelligence Server installation files
You can access the installation files from the

MicroStrategy CD-ROM or you can ask your system
administrator to share the files on a network location.
For information on mounting or unmounting
CD-ROMs, see Mounting CD-ROMs, page 400, in
Appendix E, Troubleshooting.
License key from MicroStrategy
Installation location for your MicroStrategy products
Write permissions in the installation directory to

complete the installation; otherwise the installation fails
Apart from the information provided above, review the

following sections before you start the installation:
Recommended installation location
Hardware recommendations
Software recommendations
20 Upgrade considerations 2005 MicroStrategy, Inc.

Installation and Configuration Guide Planning Your Installation 2
Recommended installation location

There are hundreds of possible arrangements for all the
products available on MicroStrategy platform, and what you
decide to do depends largely on your installation
environment and requirements. In general, though, the
following recommendations are usually true for a typical
business intelligence system:
MicroStrategy Intelligence Server should be installed on

its own dedicated server machine.
MicroStrategy Web should be installed on its own

dedicated Web server machine.
The rest of the products can be installed in varying

combinations depending on who intends to use them and
on what machines.
These are just suggestions to help you get started.

Read the rest of this chapter for more detailed
guidelines.
Hardware recommendations
MicroStrategy acknowledges that variables, such as CPU
speed, CPU type, OS version, and service upgrades, File
Space, Physical and Swap Memory, are factors that play an
important role in making your deployment of MicroStrategy
Intelligence Server Universal a successful one. This section
lists the hardware recommendations for Windows, UNIX,
and Linux platforms.
The following information is intended to give the

reader a general guidance for hardware requirements.
For more details and exact information regarding
supported and certified versions of the OS for a
particular MicroStrategy release, see the Readme files
or contact Technical Support.
2005 MicroStrategy, Inc. Installation prerequisites 21

System hardware recommendations for

Windows
The following table shows the recommended and minimum

hardware requirements for MicroStrategy products. See the
products readme files for the updated requirements.
MicroStrategy
Processor Memory Storage
Product
Administrator 1 GHz or higher 1 GB (minimum 500 MB

Pentium compatible 256 MB)
(minimum 450MHz)
Desktop 1 GHz or higher 1 GB (minimum 500 MB

Products Pentium compatible 256 MB)
(minimum 450MHz)
Intelligence 1 GHz or higher 2 GB (minimum 2 GB

Server Pentium compatible 512 MB) (minimum
(minimum 600 MHz) 512 MB)
MicroStrategy 1 GHz or higher 512 MB 100 MB

Office Pentium compatible (minimum 256
(minimum 400 MHz) MB)
Narrowcast 1 GHz Pentium or 1 GB 2 GB

Server equivalent (minimum 512 (minimum 1
(minimum 600 MHz) MB) GB)
SDK no additional requirements
MicroStrategy 400 MHz or higher 512 MB 1 GB

Tutorial Pentium compatible
MicroStrategy N.A. N.A. N.A.

BI Developer Kit
MicroStrategy
Web
Web server 1 GHz or higher 1 GB (minimum 1 GB

Pentium compatible 512MB) (minimum
(minimum 450 MHz) 500 MB)
Web client 1 GHz or higher 512 MB or Additional

Pentium compatible higher space not
(minimum 450 MHz) (minimum 128 required
MB)
22 Installation prerequisites 2005 MicroStrategy, Inc.

MicroStrategy
Processor Memory Storage
Product
MicroStrategy
Web Universal
Web Server 1 GHz or higher 1 GB or higher 1 GB or

Web Client (minimum 450 MHz) (minimum higher
512MB) (minimum
500 MB)
1 GHz or higher 128MB or Additional

(minimum 450 MHz) higher space not
(minimum required
512MB)
In addition to the MicroStrategy products listed above, the

database server on which your MicroStrategy metadata is
hosted should run on a computer with the following
minimum configuration:
Processor: 400 MHz or higher Pentium compatible
Memory: 256 MB
Storage: 200 MB
Note the following:

Depending on the MicroStrategy products you intend
to install, you must have at least 170 MB to 300 MB of
free space on your C: drive for a set of system files that
MicroStrategy installs. If you only install
MicroStrategy Web, you need 170 MB of free space.
However, for other products besides MicroStrategy
Web, you need 300 MB of free space. For example,
even if you perform an advanced installation and
choose to install every MicroStrategy product on your
D: drive, you still have 300 MB of system files installed
on your C: drive. This storage requirement is in
addition to the storage requirement discussed in the
above list.
Intelligence Server is licensed based on CPU number
and clock speed. Thus, Intelligence Server can only be
installed on machines with a maximum clock speed
that equals the licensed clock speed. If you try to
install the product on a machine faster than what is

licensed, installation fails. For example, if you are

licensed only for 750 MHz clock speed, you cannot
install the software on a 1 GHz machine. See the
MicroStrategy System Administration Guide for
more information about licensing.
MicroStrategy Intelligence Server hardware

recommendations on UNIX
For the exact information, such as version numbers and

space requirements, see the Readme file.
Sun Solaris
Hardware File CD-ROM

CPU Memory Swap
Configuration Space Drive
Minimum 1 x 450 MHZ 1 GB 2 GB 2 GB Yes

UltraSparc II
and III
Space requirements on Sun Solaris
Common Files referred to in this table are installed no matter

which MicroStrategy products are selected.
Common Intelligence Web

Directory SDK
Files Server Universal
Home Directory 427 KB 107 KB 0 0
Install Directory 260 MB 340 MB 0 0
Log Directory 2 KB 0 0 0
Web Universal N/A N/A 26.4 MB N/A
Deploy Directory
SDK Install N/A N/A N/A 281 MB

Directory

In addition to the space requirements listed above, you also

need 75 MB of free space in the temporary directory. The
default location of the temporary directory is /var/tmp. If
the space in the default temporary directory is inadequate,
you can use the is:tempdir command to change the
location of the temporary directory. This directory must
already exist and it must be specified using its absolute path,
for example:
./setupsol.bin is:tempdir /home/user/tmp
IBM AIX

CPU Memory Swap
Minimum 1 x 450 MHZ 1 GB 2 GB 2 GB Yes

PowerPC 4
and
PowerPC 5
The AIX kernel should be running only in 64-bit mode. You

can determine the mode by logging in as the root user and
entering bootinfo -K at the command prompt. The output
displays the mode.
Space requirements on IBM AIX


Directory SDK
Install Directory 342 MB 1009 MB 0 0

Web Universal N/A N/A 26.4 MB N/A

Deploy Directory
SDK Install N/A N/A N/A 281 MB

Directory


default location of the temporary directory is /tmp. If the
space in the default temporary directory is inadequate, you
can use the is:tempdir command to change the location of
the temporary directory. This directory must already exist
and it must be specified using its absolute path, for example:
./setupAIX.bin is:tempdir /home/user/tmp
RedHat Linux

CPU Memory Swap
Minimum for 1 x 1.8 GHz 1 GB 4 GB 2 GB Yes

AMD Opteron Opteron
Minimum for 1 x 2.8 GHz 1 GB 4 GB 2 GB Yes

Intel Xeon Xeon EM64T
Space requirements for RedHat Linux


Directory SDK
Install Directory 314.8 MB 465.2 MB 0 0
Web Universal N/A N/A 27.2 KB N/A

Deploy Directory
SDK Install N/A N/A N/A 243.9 MB

Directory


default location of the temporary directory is /tmp. If the
space in the default temporary directory is inadequate, you
can use the is:tempdir command to change the location of
the temporary directory. This directory must already exist
and it must be specified using its absolute path, for example:
./setupLinux.bin is:tempdir /home/user/tmp
MicroStrategy Web Universal hardware

For exact information, see the MicroStrategy Readme file.
Web server
Requirement Minimum Recommended
Processor 450 Mhz 1 Ghz or higher
RAM 512 MB 1 GB or higher
Hard disk space 500 MB 1 GB or higher
Web client
Processor 450 Mhz 1 Ghz or higher

RAM 128 MB 512 MB or higher

MicroStrategy Web Universal hardware

recommendations on Linux
Web server
Processor 1 GHz Opteron -OR- 1 GHz Opteron -OR-

2.8GHz Xeon 2.8GHz Xeon
RAM 512 MB 1 GB or higher
Hard disk space 500 MB 1 GB or higher
Software recommendations
This section lists the software recommendations for the
Windows and UNIX platforms.
The following information is intended to give the

reader a general guidance for software requirements.
For more details and exact information regarding
supported versions of the operating system for a
particular MicroStrategy release, see the Readme files
or contact Technical Support.

System software recommendations on Windows
For a successful installation of MicroStrategy products, the

following product-specific software requirements must be
satisfied.
MicroStrategy Product Software Requirements
Administrator At a minimum, you should have one of the

following for a Windows operating system:
Microsoft Windows 2000 SP1 or higher
Microsoft Windows 2003 Server
Standard Edition or Enterprise Edition
Microsoft Windows XP Professional
Edition SP1 (not valid for Enterprise
Manager)
Desktop Products Internet Explorer 4.01 or higher. Note

that to use the Document Editor with
double-byte languages you need
Internet Explorer 5.01.
Intelligence Server For Windows 2000:

Windows 2000 Server SP3 or SP4
Windows 2000 Advanced Server SP3 or
SP4
Internet Explorer 5.01 or higher
For Windows Server 2003:
Windows Server 2003 Enterprise Edition
Windows Server 2003 Standard Edition
Internet Explorer 6.01 or higher
MicroStrategy Office Microsoft Internet Information Services

5.0 or higher
Microsoft .NET Framework 1.1 build
v1.1.4322 or higher
Microsoft Excel, Microsoft
PowerPoint, or Microsoft Word, all
version 2000 or higher
MicroStrategy Web Services configured
and running

MicroStrategy Product Software Requirements
MicroStrategy Web
Web server Microsoft Internet Information Services 5.0

or higher
Web client Minimum resolution for the monitor is
800 x 600 or higher with 256 color
palette minimum, but the recommended
resolution is 1024 x 768 or higher
Any spreadsheet application that
supports the CSV file type can be used
as an export alternative to Microsoft
Excel
MicroStrategy Web
Universal
Web server Certified combination of Web server,

application server and operating system
Recommended resolution for the

Web client monitor is 800x600 or higher with 256
color palette minimum
Any spreadsheet application that
supports the CSV file type can be used
as an export alternative to Microsoft
Excel
SDK No additional requirements
MicroStrategy Tutorial See the Introduction to MicroStrategy:

Evaluation Guide for complete details
MicroStrategy BI MicroStrategy Desktop Designer or

Developer Kit MicroStrategy Architect version 7.5.0 or
higher
Narrowcast Server Microsoft Internet Information Services

4.0 or higher
Internet Explorer 5.01 Service Pack 2 or
higher
ODBC and JDBC connectivity
For more detailed information on product-specific

requirements, see the products readme files.

MicroStrategy Intelligence Server software

For the exact information such as version numbers and space

requirements, see the Readme file.
Sun Solaris
Sun Solaris 8 Operating System for SPARC Platforms
Patch requirements:
Patch clusters: Sun-recommended patch clusters dated

05/31/05 or later.
Sun Solaris 9 Operating System for SPARC Platforms
Patch requirements:
111712-05 or higher
Patch clusters: Sun-recommended patch clusters dated

5/27/05 or later
For details and installation information for each of the

patches, refer to the Patch Finder section of the Sun
Microsystems Web site, which can be found at
http://sunsolve.sun.com/pub-cgi/show.pl?
target=patches/patch-access.
Other requirements:
A Web browser (for example, Netscape 4.78 and

above) is required for viewing readme, release notes,
and online help.
Windows Services For UNIX or Samba
(http://www.samba.org)
(http://www.microsoft.com/windows/sfu/
downloads/default.asp) is required for HTML
documents support. Samba 3.0 is required for the
support of HTML documents with alphanumeric
names.
On UltraSparc II-based systems that support both 32

and 64-bit modes, the kernel must be booted in 32-bit
mode.

IBM AIX
IBM AIX 5L UNIX Operating System, version 5.2
Patch requirements:
AIX: 5.2 maintenance level 6
IBM AIX 5L UNIX Operating System, version 5.3
AIX: 5.2 maintenance level 2
Other requirements:
A X-windows-enabled environment is required for both

the GUI-based MicroStrategy Installation Wizard and
MicroStrategy Control Center.
A Web browser (for example, Netscape 4.78 and above) is

required for viewing readme files, release notes, and
online help.
Samba (http://www.samba.org) or Windows Services

For UNIX
documents support. Samba 3.0 is required for the support
of HTML documents with alphanumeric names.
RedHat Linux
RedHat Enterprise Linux AS Version 3 (64-bit) update 3
RedHat Enterprise Linux AS Version 4 (64-bit)

Other requirements:
A X-windows-enabled environment is required for both
the GUI-based MicroStrategy Installation Wizard and
MicroStrategy Control Center.
A Web browser (for example, Netscape 4.78 and above) is

required for viewing readme files, release notes, and
online help.

Samba (http://www.samba.org) or Windows Services

For UNIX
documents support. Samba 3.0 is required for the support
of HTML documents with alphanumeric names.
MicroStrategy Web Universal software

Web client software
Requirement Recommended
Web browser At a minimum, you should have one of the

following for a Windows operating system:
Microsoft Internet Explorer version 6.0
SP1
Mozilla Firefox 1.0
Netscape Navigator 6.2 (HTML mode
only)
However, MicroStrategy recommends the
following browsers for a Windows operating
system:
Microsoft Internet Explorer 6.0 SP1
Mozilla Firefox 1.0
For the UNIX operating systems:
Netscape 7.0 on Solaris
Netscape 7.0 on AIX
Firefox 1.0 on Linux
Browser resolution 800 x 600 or higher with 256 color palette

minimum
Spreadsheet application Microsoft Excel or other spreadsheet

(for exporting) application that supports the CSV file type
PDF viewer (for viewing Adobe Acrobat Reader versions 5 or 6

and exporting PDF
documents)

Web server operating systems
MicroStrategy Web Universal supports these operating

systems:
Microsoft Windows 2000/2003
IBM AIX 5.2 or 5.3
Sun Solaris 8 or 9 for SPARC
RedHat Enterprise Linux AS Version 3 or 4 for

ADM64/EM64T
Application servers
MicroStrategy Web Universal supports the following

application servers:
BEA WebLogic version 7.x or 8.x
IBM WebSphere version 5.x or 6.x
Apache Tomcat versions 4.x or 5.x
Oracle 10g (also known as Oracle application server 9.x)
Sun ONE (iPlanet) Application Server version 8.x
Throughout this guide iPlanet is referred to as Sun

ONE (iPlanet). Sun Microsystems purchased iPlanet
and renamed it Sun ONE Application Server.
Web servers
MicroStrategy Web Universal supports the following Web

servers:
Apache version 1.3 and 2.0
IBM HTTP Server version 1.3 or 2.0
Microsoft Internet Information Server version 5.0 or 6.0
Sun ONE (iPlanet) Web Server 6.x (previously known as

iPlanet Web Server, Enterprise Edition version 6.0 SP5)
This guide uses Sun ONE (iPlanet) Web Server to

refer to what was previously known as iPlanet.

Java development kits
MicroStrategy Web Universal supports the following Java

development kits:
IBM JDK 1.3.x, and 1.4.x
Sun JDK 1.3.x, and 1.4.x
For information on the exact version numbers, see the

Readme file.
Installation considerations
The following section contains guidelines and considerations
you must keep in mind during MicroStrategy installation.
System sizing guidelines

The following topics describe things to consider when you
initially set up your system. You should periodically
reevaluate the system and update it based on actual system
performance and use.
This section describes only the most basic guidelines.

For detailed information refer to the MicroStrategy
System Administration Guide.
Number of users
The number of users can be measured in the following ways:
Total users: Users that are registered in the system. For

example, if a corporate website is available to be viewed
by 950 individuals, the site has 950 total users.
Active users: Users that are logged into the system. If a
site is available to be viewed by 950 total users and 30 of
them are logged in to the site, there are 30 active users.
2005 MicroStrategy, Inc. Installation considerations 35

Concurrent users: Users that have jobs being processed by

a server (MicroStrategy Web, Intelligence Server, and so
on) at the same time. For example, a site is available to
950 total users, and 30 people are logged in. Of 30 active
users, 10 have jobs being processed by the server
simultaneously, hence there are 10 concurrent users.
Of these measures, the number of concurrent users is

important to consider. Your system must support the
maximum number of concurrent users you expect at any
given time.
Report complexity
The more complex a report, the more Intelligence Server

resources are required. In this context, a complex report is
one that requires a lot of analytical processing. While reports
with long, complicated SQL are certainly complex in nature,
they do not necessarily require additional Intelligence Server
resources to execute. It is the analytical processing in a report
that creates additional stress on an Intelligence Server.
Since analytically complex reports create a heavier load on

the Intelligence Server than simpler reports, you should have
a general idea of what the average report complexity is for
your system. Knowing this can help you decide on a caching
strategy. For example, you may decide to pre-cache complex
reports and determine the processing power your Intelligence
Server needs.
The database server processes the SQL that

Intelligence Server generates, so reports with
extremely complex SQL can place additional stress on
the database server. You should take this into account
when sizing your database server machine.
36 Installation considerations 2005 MicroStrategy, Inc.

Ad hoc reports versus caches
Report caches store the results of previously executed

reports. If a client (MicroStrategy Web, Desktop, and so on)
requests a report that is cached, Intelligence Server simply
returns the cached report results to the client. For any ad hoc
reports that are not cached, Intelligence Server must go
through the entire report execution cycle before it can return
the results. For this reason, report caching allows better
response time while minimizing the load on the Intelligence
Server.
The benefits of caching are more apparent for complex

reports than for simple reports. While caching a complex
report may significantly improve execution time, a report
cache for a simple report may not make much difference in
this regard.
Therefore, the more complex the ad hoc reporting is in your

system, the greater the overall load on the Intelligence Server.
Be sure to take this into account when sizing your Intelligence
Server machine.
The process for element browsing is similar to ad hoc

reporting. Element browsing takes place when you
navigate through hierarchies of attribute elements, for
example, viewing the list of months in the year
attribute. By default, caching is enabled for element
browsing. In addition, you can limit the number of
elements to be retrieved at a time.
Report Services document
Report Services documents utilize MicroStrategy objects to

run complex and sophisticated reports. The datasets available
to a document determine its content. Each dataset represents
a report and its component objects, such as attributes,
metrics, custom groups, and consolidations. When a dataset
is available to a document, the entire report or any
component object from that dataset can be included in the
document output.

When creating a document, refer to the following guidelines

to avoid an increase in the Intelligence Server execution time
and the overall CPU usage:
The datasets should be few in number, but large in size.
The number of grids in the output document should be

less in number. Consolidate the data to fit into less grids
in the output document, where possible.
Use of complex elements, such as consolidations, custom
groups, and smart metrics can increase the Intelligence
Server usage, especially if arithmetic operators are used in
element definitions.
Use Custom formatting only when required.
OLAP Services
OLAP Services store reports as cubes in the physical memory

of the Intelligence Server. When these cubes are cached in
memory, report manipulations, such as adding derived
metrics, formatting, and drilling within the cube, take
considerably less time. This is the case because the new SQL
is not run against the database.
OLAP Services provide enhanced report manipulation

functionality at the cost of Intelligence Server resources, as
the cubes are stored in the memory of the Intelligence Server.
Consider the following factors to determine the size of the
Intelligent cubes:
Intelligence Server resources
expected response time
user concurrency
You must monitor Intelligence Server CPU utilization and

memory usage closely as OLAP Services might have an
impact on the performance of the platform, particularly the
memory and report response time.

Additional considerations
Numerous factors can affect system performance, most of

them related to system specifics, which makes them difficult
to predict. Listed below are items you might want to consider
when determining the requirements for your system:
MicroStrategy Desktop versus MicroStrategy Web

usageMicroStrategy products are designed with the
assumption that the majority of users access the system
through MicroStrategy Web while a smaller percentage
use the Desktop products.
Statistics loggingStatistics logging is very useful for

analyzing and further refining the system configuration
based on actual usage. However, logging all statistics all
the time can create a noticeable increase in system
response time. For this reason, you might choose to log
only a subset of the statistics generated or only log
statistics periodically.
Backup frequencyCaches can be stored in memory and

on disk. When you enable backup, you allow the
Intelligence Server to write all cache files to disk. If the
backup frequency is set to the default of zero, backup files
are written to disk as soon as they are created. However,
writing all cache files to disk all the time can cause a
noticeable reduction in system performance.
Set the backup frequency to a value that minimizes disk

writes and optimizes memory usage for your system.
Ratio of Web servers to Intelligence ServersIn a typical
system you should have a 1:1 ratio of Intelligence Servers
to Web servers. This ensures that resources on both sides
are optimized. However, you might find it useful to add
Intelligence Servers or Web servers depending on your
particular requirements.
Report StylesMicroStrategy Web provides a set of

different XSL report styles. These styles provide an easy
way for you to customize how reports look. Due to the
varying complexity of these styles, some might require
more processing than others.

Common questions about sizing
Why should I increase the processor speed of

MicroStrategy Intelligence Server?
Increasing the processor speed of MicroStrategy Intelligence

Server enhances performance and reduces execution time for
all analytical tasks and for requests from the Extensible
Markup Language (XML) and Component Object Model
(COM) application programming interfaces (APIs).
Why should I add more processors to MicroStrategy

Intelligence Server?
Adding more processors to the MicroStrategy Intelligence

Server allows for a better load distribution among the
processors. This provides an overall performance gain.
Why should I increase disk speed?
Increasing disk speed allows MicroStrategy Intelligence

Server to store and retrieve caches faster, resulting in quicker
response time.
What would more network bandwidth do for me?
For very large result sets, increasing network bandwidth

reduces bottlenecks created by network congestion. The
result is larger data flow and faster query response time.
How many CPUs can a user fully utilize?
One user can fully utilize up to one CPU, regardless of the

number of CPUs available in the server. The load is split
across multiple CPUs in multi-processor servers.
What is the advantage of using hyper-threading for a

dual processor?
The advantage of using hyper-threading with a dual

processor is that it decreases the overall CPU usage. The use
of hyper-threading is recommended if you have large number
of users.

What is the disadvantage of using hyper-threading for a

dual processor?
The disadvantage of using hyper-threading is that it increases

the Intelligence Server execution time slightly. Therefore, for
faster processing, the use of hyper-threading is not
recommended.
How will I determine the size of the Intelligent Cube

reports?
To determine the size of Intelligent Cube reports, view the

cache size of the Intelligent Cubes and Report Views. The
cache size reported in the Cache Monitor is generally 30-50%
smaller than the in-memory version because it is stored in a
compressed format.
What is the maximum Intelligent Cube cache size that I

can store in an Intelligence Server?
The Intelligence Server can support a single Intelligent Cube

with a cache size up to 400MB. A cache of this size would be
created with a report of approximately 40 million data cells.
However, with an Intelligent Cube of this size, the
Intelligence Servers memory resources will be limited for
other types of operations.
What is the recommended Intelligent Cube cache size?
It is recommend that an Intelligent Cube cache should not be

greater than 1MB in high concurrent environments. A cache
of this size would be created with a report of approximately
110,000 data cells.


compatibility
MicroStrategy Web Universal 8.0 can only connect to
MicroStrategy Intelligence Server version 8.0. or later.
Refer to the MicroStrategy 8 General Information

readme for the complete MicroStrategy platform
compatibility and interoperability specification. In
addition, you can contact MicroStrategy Technical
Support for the latest information and updates.
Certified ODBC drivers for MicroStrategy Intelligence Server

Universal Edition
The following table identifies the ODBC drivers that are
certified for MicroStrategy Intelligence Server on Solaris and
AIX.
RDBMS Driver
Informix MicroStrategy Informix Wire Protocol
Oracle MicroStrategy Oracle Wire Protocol
Sybase MicroStrategy Sybase Wire Protocol
DB2 MicroStrategy DB2 Wire Protocol
DB2 iSeries (formerly MicroStrategy DB2 Wire Protocol

known as AS400)
SQL Server MicroStrategy SQL Server Wire Protocol

Informix XPS MicroStrategy Informix Driver
Teradata NCR Teradata ODBC Driver
Red Brick Red Brick Driver

Sybase IQ Sybase IQ ODBC Driver
For information on the exact version numbers, see the

Readme file.

MicroStrategy-branded 32-bit ODBC drivers are installed

with the MicroStrategy products.
The MicroStrategy Connectivity Configuration Wizard

exposes only the MicroStrategy-branded ODBC
drivers. However, this guide also provides instructions
for drivers from other vendors, that you can install
separately and use with MicroStrategy. For more
information, refer to Appendix B, ODBC and DSNs.
The methods of MicroStrategy installation are:
GUI (Graphical User Interface)
Command line
Silent installation
GUI
The GUI mode presents a user interface for each page in the
InstallShield Wizard. You click the mouse to place the cursor
on the desired object, then proceed as appropriate to
complete the task. The following navigational buttons are
also displayed:
Next: Click to proceed to the next page.
Back: Click to return to the previous page.
Cancel: Click to cancel the installation and close the

MicroStrategy InstallShield Wizard.
Finish (only on the MicroStrategy InstallShield Wizard
Complete page): Click to complete the setup and close the
wizard.
2005 MicroStrategy, Inc. Methods of installation 43

MicroStrategy provides the following types of GUI

installation:
Typical
Advanced
For information on how to perform these installations, refer

to Chapter 3, Installing MicroStrategy on Windows and
Chapter 4, Installing MicroStrategy on UNIX and Linux.
Typical installation
This installation is interactive and prompts you for a License

Key, the products to be installed, the location for the
MicroStrategy home directory, and the name of the program
folder where the application shortcuts reside.
Advanced installation
This is similar to the Typical installation, except that you have

more control over the individual directories in which each
component is installed. The Advanced installation prompts
you for the target directory for each component being
installed.
Command line
In command line mode, you type the appropriate information
at the prompt and press ENTER. Instructions are included on
each page of the InstallShield Wizard.
In some cases, you are asked to make a selection by pressing 1

or 2, and ENTER. You then press 0 and ENTER to continue.
Defaults appear next to each prompt and are enclosed in

square brackets, for example, [1]. Press ENTER to use the
default, or type a different response to the prompt to override
the default.
44 Methods of installation 2005 MicroStrategy, Inc.

In addition, on the command line wizard pages, the following

options are available:
Press 1 and then press ENTER to proceed to the next

page.
Press 2 and then press ENTER to return to the

previous page.
Press 3 and then press ENTER to cancel the

installation and close the MicroStrategy InstallShield
Wizard.
On the last page, which is MicroStrategy InstallShield

Wizard Complete, press 3 and then press ENTER to
complete the setup and close the wizard.
For information on command line installation, refer to

Silent installation
A silent, or unattended, installation is one that presents no
graphical user interface (GUI). Silent installations are useful
for system administrators who do not want users to run the
installation themselves. It allows you to automate the
installation, so it can be called from a script and executed
without user interaction.
For information on silent installation, refer to Silent

installation, page 265, in Chapter 10, Automated
Installation and Configuration on Windows and Silent
installation, page 274, in Chapter 11, Automated Installation
and Configuration on UNIX.

Licensing information
If you have installed the Evaluation version of MicroStrategy,
you cannot use its CD Key with a Generally Available (GA) CD
Key in the same environment. Hence, the Evaluation version
of MicroStrategy cannot be used for your production
environment.
For example, an organization that has MicroStrategy 7.5.0

installed does not support MicroStrategy Office as its CD Key
does not contain the license for MicroStrategy Office. If they
want to test the capabilities of MicroStrategy Office, they can
run the evaluation CD Key on their client computers, after
downloading MicroStrategy Office, to test it in their
environment. They then configure MicroStrategy Office to
connect to their Development Intelligence Server, which was
installed by the permanent GA CD key, on the MicroStrategy
Server computer. However, after attempting to run
MicroStrategy Office, the following error message appears:
The selected Login ID does not have privilege

to use MicroStrategy Office.
This message appears as the CD keys on the client machine

and on the MicroStrategy Intelligence Server are different.
Therefore, the same CD key must be used on both the
MicroStrategy Intelligence Server and on the Client machine
for the client to connect to the MicroStrategy Intelligence
Server.
Aenvironment,
workaround for this scenario is to create a testing
built entirely on the Evaluation CD key.
This enables customers to test any products they want
to evaluate.
46 Licensing information 2005 MicroStrategy, Inc.

Types of licenses
The types of MicroStrategy licenses are
Named User licenses
CPU licenses
Named User licenses
When you purchase licenses in the Named User format, the

system monitors the number of users in your implementation
and compares it to the number of licenses. It can be
considered out of compliance if too many users are in the
metadata or more users are assigned higher-level privileges
than are licensed. For example, if you have licenses for 10
Web Professional users and 12 users have the privileges
associated with Web Professional, the system considers that
as noncompliance.
For more information, refer to Verifying Named user

licenses, page 318, in Appendix A, Managing Licenses.
CPU licenses
When you purchase licenses in the CPU format, the

Intelligence Server governs its processes to operate only on
the first "n" CPUs you specify during installation. The ability
to deploy MicroStrategy Intelligence Server only on a subset
of the total number of physical CPUs on a given machine is
called Processor Affinity. To learn more about Processor
Affinity, refer to MicroStrategy System Administration
Guide.
For more information on CPU licenses, refer to Verifying

CPU licenses, page 319, in Appendix A, Managing Licenses.
2005 MicroStrategy, Inc. Licensing information 47

Next steps
After planning your installation, you are now ready to install
the MicroStrategy components you need. The following
chapters instruct you on installing and configuring
MicroStrategy components. If you are installing
MicroStrategy on Windows, then see Chapter 3, Installing
MicroStrategy on Windows. If you are installing
MicroStrategy components on any other operating system,
then see Chapter 4, Installing MicroStrategy on UNIX and
Linux.
48 Next steps 2005 MicroStrategy, Inc.

3
3. INSTALLING MICROSTRATEGY
ON WINDOWS
Introduction
This chapter describes the procedures for installing the

MicroStrategy products that are necessary to run your
business intelligence application on a Windows environment.
IfMicroStrategy
you have used the Evaluation Edition of the
platform, you may have installed most
of these products already. However, additional
considerations are important when you are setting up
a production business intelligence system as opposed
to running the evaluation software. You should read
this chapter carefully, even if you already have a
working system from your Evaluation Edition.
Installation procedure
If you are installing MicroStrategy on UNIX or Linux, refer to

Installation procedures on UNIX or Linux, page 72 in

3 Installing MicroStrategy on Windows Installation and Configuration Guide
Installation procedure
The MicroStrategy InstallShield Wizard provides
step-by-step instructions to guide you through installing one
or more MicroStrategy products in a Windows environment.
The following sections can assist you in installing one or more
MicroStrategy products:
InstallShield Wizard
Installation verification
For information on installation prerequisites, see Installation

prerequisites, page 20 in Chapter 2, Planning Your
Installation.
For information about advanced installation functionality,

such as installing in an SMS environment or using
installation response files, see Chapter 10, Automated
For information about installing and deploying

MicroStrategy Web Universal on other operating systems or
with other Web and application servers, see Chapter 8,
Configuring and Deploying MicroStrategy Web Universal.
Note the following:

If you have not uninstalled previous versions of
MicroStrategy products, you are prompted to
overwrite them. Click Yes to ensure that all products
are installed properly. To retain the existing Tutorial
metadata repository and warehouse, rename it or
move it to another location before you start the
installation process.
Though MicroStrategy supports Windows Terminal
Services, using Windows Terminal Services is not
recommended for installation. It can affect the
functionality of some MicroStrategy components.
50 Installation procedure 2005 MicroStrategy, Inc.

Installation and Configuration Guide Installing MicroStrategy on Windows 3
InstallShield Wizard
To install MicroStrategy products, you must log on to your
machine using a domain account with Windows
administrative privileges for the domain or target machine.
The domain must include your database servers.
To exit the installation process at any time, click Cancel.
To access the InstallShield Wizard
1 Log on to the machine where you are installing one or

more MicroStrategy products.
2 Exit all Windows applications before beginning the

installation process.
3 Insert the CD into the CD-ROM drive and wait for the
MicroStrategy Main Menu window to display
automatically.
Iflocate
the MicroStrategy Main Menu does not display,
and run Setup.exe on the CD.
4 If this is the first time you have installed MicroStrategy,

you are prompted to choose the language for the wizard.
Select the appropriate language from the drop-down list
and click OK.
The InstallShield Wizard opens and leads you through the

rest of the installation process. The following sections
describe the actions you must take for each page in the
wizard.
If any Windows services are running for previously installed

MicroStrategy products, you are prompted to stop them.
Click Yes to proceed. If you click No, you cannot install
MicroStrategy products until you stop all MicroStrategy
services.
2005 MicroStrategy, Inc. Installation procedure 51

Welcome
Page Content Options
Welcome statement. Read the information on the

Welcome screen. Click Next to
proceed.
IfMicrosoft
you opened the InstallShield Wizard through the
Control Panel using the Add/Remove
Programs option, the wizard opens the Welcome page
in maintenance mode. The table below describes this
window.
Welcome statement. Click Modify to add new

program components or to
remove currently installed
components. The remaining
pages are the same as for a
first-time installation.
Click Repair to reinstall all
installed by the previous setup.
You do not have to select the
again.
Click Remove to remove all
installed MicroStrategy
components without accessing
all the InstallShield Wizard
pages.
Click Next to proceed.
Ifyouyouneedinstall the MicroStrategy products using a CD,

your original installation CD to modify or
repair the software.

License Agreement
License-related terms and Read the license agreement,

conditions. and select to accept or decline
the agreement. If you choose to
decline, you cannot install
Click Back to return to the
previous page.
Customer Information
Boxes for name, company name, Enter your name.

and product license key. Enter the name of your
company.
Enter the license key.
previous page.
Setup Type
Options to select the type of Select Typical to place all products

installation: Typical or in a given root directory.
advanced. Select Advanced to specify a
different directory for each
MicroStrategy product you install.
Click Back to return to the previous
page.
The significant differences between a Typical setup and an

Advanced setup are as follows:
With the Advanced setup option, you can select a different

location for each product selected in the Select
Components window; with the Typical option, all
products selected are placed in the same location.

With the Advanced setup option, you can select a location

for the common files; with the Typical setup option, the
system assigns the common file location (C:\Program
Files\Common Files\MicroStrategy).
Choose Destination Location
Location where the MicroStrategy Click Browse to select a

products are installed. location different from the
default value; see the following
note.
previous page.
Note the following:

While this setting determines the default root
directory for the MicroStrategy products you install,
you can change the destination of a product later if you
choose an Advanced setup.
With both Typical and Advanced setup types, you can

choose the directory for a product only if that product
is not already installed on the server machine.
Otherwise, the product can only be installed in the
same directory in which it already exists. In that case
this page is not displayed.
Select Components
A list of MicroStrategy products. Select or clear the appropriate

Space Required: Space check boxes.
needed for the MicroStrategy Click Next to proceed.
products selected; the count Click Back to return to the
changes dynamically as check previous page.
boxes are selected and
cleared.
Description: Details about
each MicroStrategy product.

Click Yes if you are prompted to stop your Web server. If you
click No, you cannot continue with the installation until you
stop your Web server.
The installation screens you see from here depend on the

products you choose to install. These instructions describe all
possible screens, but to perform the functions described in
this book, you must install the following components along
with all their sub-components:
MicroStrategy Desktop Products
MicroStrategy Web ASP.NET version, or Web

Universal, depending on your license key
MicroStrategy Web Services required for

MicroStrategy Tutorial - Reporting
You do not have to install all of these products on

the same machine. In fact, this is strongly
discouraged in a production environment. For
basic guidelines about product placement, see
Installation prerequisites, page 20 in Chapter 2,
Planning Your Installation.
Many of the platform components have sub-components. If

you expand MicroStrategy Desktop Products, MicroStrategy
Administrator, MicroStrategy Web, MicroStrategy Web
Services, or MicroStrategy Narrowcast Server, you can select
or clear the appropriate check boxes to specify the
components and sub-components to install. For information
on MicroStrategy components and sub-components, see
MicroStrategy components, page 2 in Chapter 1,
Introduction to MicroStrategy.

CPU License Information
You see this page only if
you are installing MicroStrategy Intelligence Server on a

multi-processor machine
your license is based on CPU and allows for more than

one CPU
Box to specify the number of Type the number of CPUs

CPUs Intelligence Server is to Intelligence Server is to use.
use on this machine. Click Next to proceed.
Information about the minimum Click Back to return to the
and maximum allowed number previous page.
of CPUs based on your license.
Select multiple target directories (Advanced

setup option only)
If you did not choose the Advanced Setup option, you skip
this page and its series of dialog boxes. If you select the
Advanced Setup option, you must specify the installation
location for each component you choose to install.
This step consists of multiple Click Browse to select a target

sub-steps that open one dialog destination for each
box for each component.You can component.
select multiple target directories Click Next to proceed.
only if you choose an advanced Click Back to return to the
install. previous page.
The system validates the space available for each destination

selected. This processing is transparent. You are notified of
the status only if the space available is insufficient.

MicroStrategy Web (ASP.NET) setting
You see this page only if you choose to install MicroStrategy

Web (ASP.NET) and only if you do not have a previous
version of MicroStrategy Web installed.
Box to specify the name of the Specify the name of the IIS
Microsoft IIS virtual directory to be virtual directory to be created
created. for MicroStrategy Web.
previous page.
In IIS, a virtual directory is the home location for a set of Web

pages that the Web server hosts. In this case, you must
specify the home location for the MicroStrategy Web ASP
pages. The default is MicroStrategy.
Note the following:

If you have a previous version of MicroStrategy Web
installed on the machine, the new version you install
uses the same virtual directory the previous version is
using, and you are not prompted to specify the name
of the virtual directory.
The name provided for a virtual directory must be
unique. You cannot use the same name as the default
for other MicroStrategy products.

MicroStrategy Web (ASP.NET) CPU Affinity

setting

Web (ASP.NET) and if the MicroStrategy Web installation
detects that the license key entered by the administrator
corresponds to a CPU-based license.
Box to specify the number of CPUs Specify the number of CPUs

that MicroStrategy Web should use that Web should use on the
on the machine. machine.
This page is not displayed on Click Next to proceed.
single-processor machines. Click Back to return to the
previous page.
You can specify only the number of CPUs that are allowed by
the license. If MicroStrategy Web is installed on more than
one machine, the total number of CPUs should not exceed the
maximum number of CPUs specified by the license. For
machines that support hyperthreading technology, the CPU
counts correspond to physical CPUs, not logical CPUs.
Note the following:

To allow the setting to take effect, the installation
stops Internet Information Services (IIS). After IIS has
been restarted, the MicroStrategy Web application
uses the specified number of CPUs.
If a CPU-based license key is specified for a machine
running IIS 5.0, a warning is displayed before the CPU
affinity selection dialog.
For more information on the MicroStrategy Web CPU affinity

feature, refer to the MicroStrategy System Administration
Guide.

MicroStrategy Subscription Portal setting

Subscription Portal, which is a component of Narrowcast
Server, and only if you do not have a previous version of
Subscription Portal installed.
created. for MicroStrategy Subscription
Portal.
previous page.

specify the home location for the Subscription Portal pages.
The default is NarrowcastServer.
Note the following:

Subscription Portal offers you the ability to subscribe
to and view Narrowcast Server services, service
descriptions, and their most recent modification dates
on the Web. For complete information about
Subscription Portal and other components of
Narrowcast Server, refer to the MicroStrategy
Narrowcast Server documentation.
The name provided for a virtual directory must be
unique. You cannot use the same name as the default
for other MicroStrategy products.

MicroStrategy Web Services setting

Web Services, which is required to run MicroStrategy Office,
and only if you do not have a previous version of Web
Services installed.
created. for MicroStrategy Web
Services.
previous page.

pages that the Web server will host. In this case, you must
specify the home location for the Web Services pages. The
default is MicroStrategyWS.
To learn more about MicroStrategy Web Services, refer to the

MicroStrategy Web Services Administration Guide.
MicroStrategy eTrainer for Web setting

eTrainer for Web and if you do not have a previous version of
eTrainer installed.
created. for MicroStrategy Web
Services.
previous page.


specify the home location for the eTrainer pages. The default
is eTrainer.
Select Program Folder
Box to specify the name of the Perform one of the following

program folder in your Windows actions:
Start menu from which type a folder name different
MicroStrategy products will be from the default
accessed. select an existing folder
List of the existing program accept the default. It is
folders found under the recommended to accept to
Windows Start menu. default.
previous page.
MicroStrategy Intelligence Server setting
You see this page if you choose to install MicroStrategy

Intelligence Server and if you do not have a previous version
of Intelligence Server installed.
Check box: Option to not set Enter the necessary data and
the service account. click Next to establish the
Login: Windows login with account.
administrative privileges in the Select the check box to bypass
format Domain\User. account initiation.
Password: Valid password for
the login entered in the Login
box.
Confirmation: Retype the
password to confirm.
The MicroStrategy Intelligence Server service requires a

Windows account with administrative privileges under which
to run. If you click Cancel, the service runs under the local
system account.

Note the following:

If you have a previous version of Intelligence Server
installed on your machine, the new version you install
uses the same account that the previous version is
using and you are not prompted for this information.
If the password you supply ever changes, you must

reconfigure the Windows service to use the new
password, otherwise Intelligence Server does not
work.
For information on installing MicroStrategy Intelligence

Server on UNIX or Linux, see Chapter 4, Installing
MicroStrategy on UNIX and Linux.
MicroStrategy Narrowcast Server Setting
You see this page if you choose to install MicroStrategy

Narrowcast Server.
Check box: Option to not set Enter the necessary data and
the service account. click Next to establish the
Login: Windows login with account. It is recommended to
administrative privileges in the create the account.
format Domain\User. Select the check box to bypass
Password: Valid password for account initiation.
the login entered in the Login
box.
Confirmation: Retype the
password to confirm.
The MicroStrategy Narrowcast Server service requires a

Windows account on the machine with administrative
privileges. Enter the necessary information and click Next.
Refer to the MicroStrategy Narrowcast Server Installation

and Configuration Guide for additional details about this
setting.

Note the following:

If you have a previous version of Narrowcast Server
installed on the machine, the new version you install
uses the same account the previous version is using
and you are not prompted for this information.
If you change the password, you must reconfigure the

Narrowcast Server Windows services to use the new
password at any time.
MicroStrategy Web Universal Application

Deployment
This page is displayed only when the MicroStrategy Web

Universal option is selected in the Select Components page.
If you are not deploying with WebLogic Application Server,

skip this step and click Next to proceed.
Information about the location By default, the Do not

where MicroStrategy Web configure Web Universal
Universal is deployed by the deployment location check
WebLogic Application Server. box is selected. If you are
deploying with WebLogic
Application Server, clear this
check box to enable the
Browse button.
Click Browse to specify the
MicroStrategy Web Universal
deployment location.
Click Next to proceed to the
next page.
previous page.

If you are deploying with WebLogic Application Server, the

Web deployment descriptor file (web.xml) for the Web
Universal WAR file has to be modified to allow certain
configuration files used by MicroStrategy Web Universal to
be created under an absolute path. When the MicroStrategy
Web Universal application is started, several configuration
files used by the application are saved under this path. You
can specify this path under the MicroStrategy Web Universal
Deployment location.
For information on installing MicroStrategy Web Universal

on UNIX or Linux, see Chapter 4, Installing MicroStrategy
on UNIX and Linux.
MicroStrategy Office URL setting
You see this page if you choose to install MicroStrategy Office

and if you do not have a previous version of MicroStrategy
Office installed.
Text box to specify the Specify the URL for

MicroStrategy Web Services URL MicroStrategy Web Services.
for MicroStrategy Office. Click Next to proceed.
previous page.
The MicroStrategy Office client requires the Web Services

URL to access MicroStrategy projects. The URL depends on
the name of the IIS virtual directory that you specified on the
MicroStrategy Web Services Setting page. Assuming that you
kept the default value on the MicroStrategy Web Services
Setting page and you are installing on the same Web server
machine that is hosting MicroStrategy Web, you should use
the default URL provided:
http://localhost/MicroStrategyWS/MSTRWS.asmx

MicroStrategy Office configuration
You see this page if you choose to install MicroStrategy Office

and if you do not have a previous version of MicroStrategy
Office installed.
Check boxes to specify the Select the check box next to the
Microsoft Office applications to applications to be used.
integrate with MicroStrategy Office. Click Next to proceed.
previous page.
This setting adds the MicroStrategy Office tool bar to the

Microsoft Office applications that you select. You can
configure MicroStrategy Office to integrate with Microsoft
Excel, PowerPoint, or Word. You can choose any of the
applications, but this chapter only shows you how to use
Excel.
Start Copying Files
Page content Options
Current Settings (depending Click Next to proceed.

upon the products you install): Click Back to return to the
Products that will be installed or previous page.
updated.
The target directories in which
the products are installed.
Name of the Windows Start
menu program folder.
Virtual directories for Web
(ASP.NET), Subscription
Portal, Web Services, and
eTrainer.
URL for MicroStrategy Web
Services.
Service accounts for
MicroStrategy Narrowcast
Server and Intelligence Server.
Location of the installation log
file.
License details.

Click Install to continue with the installation process, which

can take several minutes depending on your computers
hardware configuration.
Software Activation
Before the installation process ends the Software Activation

window opens.
Option to automatically activate Select Yes to activate the

MicroStrategy installation via installation.
internet. Select No to activate the
installation at a later date.
This page gives you the option to activate your MicroStrategy

product installation automatically through the Internet, or
activate it at a later date by visiting the activation web site,
https://support.microstrategy.com/activation.
If you choose to activate your installation later, you have a
grace period of thirty calendar days. If you do not complete
the activation before the grace period expires, your
MicroStrategy product stops functioning until you activate it.
If you wait to activate your installation, you receive periodic
reminders.
When the activation process is finished, you are prompted to

either view the ReadMe file, or go directly to the InstallShield
Wizard Complete page. Click Yes to read the ReadMe file and
No to go to the InstallShield Wizard Complete page.
During installation, the following folders are created

with special privileges that are required for
MicroStrategy Web users. Changes made to these
default access privileges can create problems for
MicroStrategy Web users:
Common files\MicroStrategy\Web-INF\log.
This folder stores the Web log files, including all
errors. All Web users can write to this location.

Common files\MicroStrategy\Web-INF\xml.
This folder stores some of the configuration XML files,
such as AdminServers.xml and
AdminOptions.xml. The Web administrator can
add, remove, and modify the list of Intelligence
Servers to which the Web server is connected. The
Web administrator can also modify the Administrator
Preferences shared by all users.
InstallShield Wizard Complete
Message confirming Select Yes to restart the

installation. computer. It is recommended to
Options Yes/No to restart the restart your computer.
computer if required. Select No to continue without
Check box to open the ReadMe restarting.
file, if restarting is not required. Select the check box to open
Instructions to empty drives and the ReadMe file, if restarting is
click Finish. not required.
Click Finish to complete the
setup.
Ifensure
the option to restart your machine appears, to
that the installation process finishes correctly,
you should select Yes I want to restart my computer
now.
Installation verification
During the installation routine, the InstallShield Wizard
gathers and records information about your system and your
installation selections. Verify installation setup information
through the installation log file (install.log), located by
default in C:\Program Files\Common
Files\MicroStrategy.
The installation log file includes the following information:
Installation date
Target directories

Program folder name
Operating system identification
Hardware specifications
Selected installation options
Registry paths
List of registered files
The installation log file can be helpful if you encounter

errors during the installation process. For example,
the log can tell you if a registry key or path was not
added or if a critical file was not registered
successfully.
Next steps
If you encounter errors while installing MicroStrategy, refer
to Appendix E, Troubleshooting.
After installation is complete, you are ready to configure the

MicroStrategy components you have installed. This ensures
the software can be used immediately. Configuration is
performed with the Configuration Wizard. To learn about the
Configuration Wizard, see Using the MicroStrategy
Configuration Wizard, page 89 in Chapter 5, Configuring
MicroStrategy Intelligence Server.
After you have installed MicroStrategy Web Universal, you

can deploy and configure it for your specific environment.
The configuration and deployment steps are provided in
Universal. The table below lists the steps for all
environments.

High-Level Deployment Steps
1 Log on to the application server by using the proper user name and
password.
2 Locate the MicroStrategy.war file. It is located in the Web
Universal Deployment Directory you specified during installation.
3 To increase the performance of the application and before
proceeding with the deployment, see the Performance-based setup
information section, if available, for your environment and configure
as necessary. Also, after deploying Web Universal on your
machine, there may be a few performance-based setup steps that
you should complete.
4 Choose the desired deployment method.
5 Follow the deployment procedure.
6 Log on to the MicroStrategy Web Administrator Page.
7 Launch MicroStrategy Web.
8 Start working with the application.
For details on deploying MicroStrategy Web Universal with

different application and web servers on Windows, see the
following sections:
To deploy with Tomcat Application Server, see Deploying

with Tomcat (Linux), page 191 in Chapter 8, Configuring
and Deploying MicroStrategy Web Universal.
To deploy with Oracle Application Server, see Deploying

with Oracle 10g, page 199 in Chapter 8, Configuring and
Deploying MicroStrategy Web Universal.
The MicroStrategy platform comes with a Tutoriala sample

data warehouse and demonstration project you can use to
learn about the various features that MicroStrategy offers. It
is ready to be used and requires no additional configuration
tasks. If you have used the Evaluation Edition, you should
already be familiar with the Tutorial. To use the Tutorial,
refer to the Reporting Essentails chapter in the Basic
Reporting Guide. When you are ready to set up a new system
to be used with your own data, see Chapter 5, Configuring
MicroStrategy Intelligence Server and perform the tasks
described here.


4
4. INSTALLING MICROSTRATEGY
ON UNIX AND LINUX
Introduction
This chapter describes the procedure for installing

MicroStrategy on UNIX or Linux platforms. MicroStrategy
products are compatible with Solaris, AIX, and RedHat. The
installation procedure described in this chapter refer to
installing MicroStrategy on Solaris, AIX, and RedHat. This
chapter covers the following section:
Installation procedures on UNIX or Linux
If you are installing MicroStrategy on Windows, refer to

Chapter 3, Installing MicroStrategy on Windows.

4 Installing MicroStrategy on UNIX and Linux Installation and Configuration Guide
Installation procedures on UNIX or Linux

This section describes installing MicroStrategy on UNIX or
Linux. The MicroStrategy products that you can install on
UNIX or Linux environment are:
MicroStrategy SDK
For more information about these products, see

MicroStrategy components, page 2 in Chapter 1,
Introduction to MicroStrategy.
Different methods of installation

MicroStrategy products can be installed on UNIX or Linux,
either in graphical user interface (GUI) mode or in command
line mode, using the MicroStrategy InstallShield Wizard. In
both cases, the MicroStrategy InstallShield Wizard runs,
displaying the same pages and requesting the same
information. The main differences are in how you provide the
information and navigate through the wizard.
Using GUI mode
The GUI (graphical user interface) mode presents a user

interface for each page in the InstallShield Wizard. You click
the mouse to place the cursor on the desired object, and then
proceed as appropriate to complete the task. The following
navigational buttons are also displayed:
Next proceed to the next page
Backreturn to the previous page
Cancelcancel the installation and close the

MicroStrategy InstallShield Wizard
Finishcomplete the setup and close the wizard
72 Installation procedures on UNIX or Linux 2005 MicroStrategy, Inc.

Installation and Configuration Guide Installing MicroStrategy on UNIX and Linux 4
Using command line mode
In command line mode, you type the appropriate information

at the prompt and press ENTER. Instructions are included on
each page of the InstallShield Wizard.
In some cases, you are asked to make a selection by pressing

1 or 2, and ENTER. You then press 0 and ENTER to continue.
Defaults appear next to each prompt and are enclosed in

square brackets, for example, [1]. Press ENTER to use the
default, or type a different response to the prompt to override
the default.
In addition, on the command line wizard pages, the following

options are available:
Press 1 and then press ENTER to proceed to the next

page.
Press 2 and then press ENTER to return to the
previous page.
Press 3 and then press ENTER to cancel the

installation and close the MicroStrategy InstallShield
Wizard.
On the last page, which is MicroStrategy InstallShield

Wizard Complete, press 3 and then press ENTER to
complete the setup and close the wizard.
Installing MicroStrategy using InstallShield Wizard

To install MicroStrategy products, you must log on to your
machine using a valid UNIX or Linux account. For ease of
management and maintenance, it is recommended that you
create a dedicated user account.
You need root access permissions for installation if

you have purchased the CPU-based MicroStrategy
license.
To exit the installation process at any time, click Cancel.
2005 MicroStrategy, Inc. Installation procedures on UNIX or Linux 73

To access the MicroStrategy InstallShield Wizard
1 Log on to the machine on which you are installing one or

2 Browse to the MicroStrategyInstallation/

QueryReportingAnalysis_UNIX directory.
You can access the installation files from a

CD-ROM or ask your system administrator to
share the files on a network location. There are
different CDs for installing MicroStrategy products
on different platforms; Windows, UNIX, and
Linux. For information on mounting or
unmounting CD-ROMs, refer to Mounting
CD-ROMs, page 400 in Appendix E,
Troubleshooting.
3 Type one of the following, depending on the installation

mode you chose and your operating system:
To run the wizard in GUI mode
for Solaris: ./setupsol.bin
for AIX: ./setupAIX.bin
For Linux: ./setupLinux.bin
To run the wizard in command line mode

for Solaris: ./setupsol.bin -console
for AIX: ./setupAIX.bin -console
For Linux: ./setupLinux.bin console
For more information on these modes of installation,

refer to Different methods of installation, page 72.
4 The MicroStrategy InstallShield Wizard opens and leads

you through the rest of the installation process. The
following sections describe the actions you need to take
for each page in the wizard.

Note the following:

To complete the installation, you must have write
permissions in the installation directory; otherwise the
installation fails.
At any time during the setup, click Cancel, or press 3

and then press ENTER, to quit the installation.
Language Setup
Language selection. Enter the number associated

with the language to be used
for the installation from the
available list. If you do not
select any language, by default
English is selected.
Proceed to the next page.
Welcome
Welcome statement. Proceed to the next page in the

wizard.
License Agreement
License-related terms and Read the license agreement.

conditions. Select to accept or to decline
the agreement. If you choose to
decline, you cannot install
next page.
previous page.

Customer Information
Prompts to specify the user name, Specify your user name,

company name, and license key. company name, and license
key.
Proceed to the next page.
Return to the previous page.
Home Directory
Location where the MicroStrategy If required, specify a location

configuration files and application different from the default value.
launchers will be installed. See the following Note.
next page.
previous page.
Note the following:

The default location is /var/opt/MicroStrategy,
or $HOME/MicroStrategy if you do not have write
access to /var/opt/MicroStrategy.
The path specified for the Home Directory is referred

to as <HOME_PATH> in this guide.
Do not change the names of folders in the product
destination, installation path, after
installing the Intelligence Server.

Install Directory
Location where the MicroStrategy If required, specify a location

products will be installed. different from the default value.
See the following Note.
next page.
previous page.
Note the following:



Log Directory
Location where the application If required, specify a location

logs will be created. different from the default value.
See the following Note.
next page.
previous page.
Note the following:




Select Components
A list of MicroStrategy products: Select the products you want to

Intelligence Server install. By default, all are
Web Universal selected.
MicroStrategy SDK Click Next to proceed to the
next page.
previous page.
MicroStrategy Web Universal has sub components. To learn

more about them, refer to MicroStrategy Web and Web
Universal components, page 7 in Chapter 1, Introduction to
MicroStrategy.
CPU License Information
This page is displayed only if the Intelligence Server license

has a CPU number limitation.
Prompt for the number of CPUs to Specify the number of CPUs to

be deployed on this computer. be deployed on this computer
or accept the default.
next page.
previous page.

MicroStrategy Web Universal Install Location

Information about the Click Browse to change the

destination directory where the directory.
WAR file is placed. The default Click Next to proceed.
is /opt/MicroStrategy. Click Back to return to the
Browse button. previous page.
MicroStrategy Web Universal Application

Deployment

If you are not deploying with WebLogic Application Server,

skip this step and click Next to proceed.
Information about the location By default, the Do not

where MicroStrategy Web configure Web Universal
Universal is deployed by the deployment location check
WebLogic Application Server. box is selected. If you are
deploying with WebLogic
Application Server, clear this
check box to enable the
Browse button.
Click Browse to specify the
deployment location.
next page.
previous page.

If you are deploying with WebLogic Application Server, the

Web deployment descriptor file (web.xml) for the Web
Universal WAR file has to be modified, to allow certain
configuration files used by MicroStrategy Web Universal to
be created under an absolute path. When the MicroStrategy
Web Universal application is started, several configuration
files used by the application are saved under this path. You
can specify this path under the MicroStrategy Web Universal
Deployment location.
MicroStrategy SDK Installation Location
This page is displayed only when the MicroStrategy SDK

option is selected in the Select Components page.
Location of the destination Specify the path to the folder or

directory where MicroStrategy accept the default.
SDK Universal files will be Click Next to proceed to the
installed. next page.
previous page.
Start Copying Files
Current settings: Verify the information and

Products that are installed or proceed to the next page.
updated. Return to the previous page.
Directories in which the
products are installed.
Location of the installation log
file.
License details.

File Transfer Complete
Information about any Review the information and

problems that occurred during proceed to the next page.
installation. Return to the previous page.
Software Activation
Before the installation process ends the Software Activation

window opens.
Option to automatically activate Select Yes to activate the

MicroStrategy installation via the installation.
internet. Select No to activate the
installation at a later date.
This page gives you the option to activate your MicroStrategy

product installation automatically through the Internet, or
activate it at a later date by visiting the activation web site,
https://support.microstrategy.com/activation.
If you choose to activate your installation later, you have a
grace period of thirty calendar days. If you do not complete
the activation before the grace period expires, your
MicroStrategy product stops functioning until you activate it.
If you wait to activate your installation, you receive periodic
reminders.
When the activation process is finished, you are prompted to

either view the ReadMe file, or go directly to the InstallShield
Wizard Complete page. Click Yes to read the ReadMe file and
No to go to the InstallShield Wizard Complete page.
During installation, the following folders are created

with special privileges that are required for
MicroStrategy Web users. Changes made to these
default access privileges can create problems for
MicroStrategy Web users:
Common files\MicroStrategy\Web-INF\log.
This folder stores the Web log files, including all
errors. All Web users can write to this location.

Common files\MicroStrategy\Web-INF\xml.
This folder stores some of the configuration XML files,
such as AdminServers.xml and
AdminOptions.xml. The Web administrator can
add, remove, and modify the list of Intelligence
Servers to which the Web server is connected. The
Web administrator can also modify the Administrator
Preferences shared by all users.
MicroStrategy Install Wizard Complete
Message confirming Select the check box to open

completion of installation. the ReadMe file in GUI mode
Check box to open the ReadMe only.
file, in GUI mode only. Select the check box to run
Check box to launch MicroStrategy Control Center in
MicroStrategy Control Center. GUI mode only.
Click Finish or press 3 to
complete the setup.
Ifshould
the option to restart your machine appears, you
select Yes I want to restart my computer now
to restart your computer at this time to ensure that the
installation process finishes correctly.
Verifying installation
During the installation routine, the InstallShield Wizard
gathers and records information about your system and your
installation selections. You can verify the setup information
through the installation log file (install.log).
By default, the log file is located in <INSTALL_PATH> where,

<INSTALL_PATH> is the directory you specified as the install
directory in the InstallShield Wizard.
The log file includes information about the following:
Installation date
Target directory

Operating system identification
Selected installation options
Selected licensing details
This log file can be helpful if you encounter errors

during the installation process. The log file records the
reasons due to which the errors occurred.
Directory structure
The following table describes the directories in which
MicroStrategy files are installed.
PATH/Directory Contents
<HOME_PATH> Configuration files that can be modified after installation.
<HOME_PATH>/env Scripts to set up the proper environment for the

MicroStrategy applications.
<HOME_PATH>/bin Scripts to launch the MicroStrategy applications.
<INSTALL_PATH> Files that are not supposed to change after the

installation is complete.
<INSTALL_PATH>/Documentation Documentation for MicroStrategy products.
<INSTALL_PATH>/IntelligenceServer/bin Intelligence Server-specific binary files.
<INSTALL_PATH>/PDFGeneratorFiles Support files (fonts) for the PDF generation feature of

Intelligence Server.
<INSTALL_PATH>/ReleaseNotes Release notes and readme files for this release of

<INSTALL_PATH>/SDK Software Development Kit files. This is the default

directory for the SDK but another location can be selected
during installation.
<INSTALL_PATH>/WebUniversal Web Universal deployment path. This is the default

directory for Web Universal, but it can be changed during
installation.
<INSTALL_PATH>/_jvm The Java Runtime Environment (JRE) to be used by the

Java applications. It provides the requirements for
executing a Java application, a Java Virtual Machine,
core classes, and supporting files.
<INSTALL_PATH>/_uninst Launch files for uninstalling MicroStrategy Universal.
<INSTALL_PATH>/bin 64-bit binary files.

PATH/Directory Contents
<INSTALL_PATH>/bin32 32-bit binary files.
<INSTALL_PATH>/help Online help files.
<INSTALL_PATH>/jar Java libraries.

<INSTALL_PATH>/lib 64-bit binary libraries.
<INSTALL_PATH>/lib32 32-bit binary libraries.
<INSTALL_PATH>/locale ODBC support messages. The ODBC drivers are copied

to /lib32.
<LOG_PATH> MicroStrategy application log files.
<LOG_PATH>/IntelligenceServer Intelligence Server log files.
Directory structure after deploying the WAR file
The following table shows the default directory structure

after deploying the WAR file in your application server.
Directory Contents
\help Help and descriptor

files.
\images All image files.
\javascript Interface JavaScript

files.
\jsp Interface JSP code

files.
\style Interface style files.

\WEB-INF Configuration
information for
MicroStrategy Web.
\WEB-INF\classes All resource files.
\WEB-INF\lib All library files.

\WEB-INF\log All log files, except for
ncsportal.log files.
They are created in
the application server
root folder.

Directory Contents
\WEB-INF\tlds All Tag Library

Descriptor files.
\WEB-INF\xml All Web xml and xsl

files.
Next steps
After the installation is complete, you are ready to configure
the MicroStrategy components you have installed. This
ensures that the software can be used immediately.
If there are no project sources defined, then MicroStrategy

Control Center opens the Configuration Wizard. To learn
about the Configuration Wizard, see Using the
MicroStrategy Configuration Wizard, page 89 in Chapter 5,
Configuring MicroStrategy Intelligence Server in this guide.
After you have installed MicroStrategy Web Universal, you

can deploy and configure it for your specific environment.
The configuration and deployment steps are provided in
Universal. The table below lists the steps for all
environments.
High-Level Deployment Steps
1 Log on to the application server by using the proper user name and
password.
2 Locate the MicroStrategy.war file. It is located in the Web
Universal Deployment Directory you specified during installation.
3 To increase the performance of the application and before
proceeding with the deployment, see the Performance-based setup
information section, if available, for your environment and configure
as necessary. Also, after deploying Web Universal on your
machine, there may be a few performance-based setup steps that
you should complete.
4 Choose the desired deployment method.
5 Follow the deployment procedure.
6 Log on to the MicroStrategy Web Administrator Page.
7 Launch MicroStrategy Web.
8 Start working with the application.
2005 MicroStrategy, Inc. Next steps 85

For details on deploying MicroStartegy Web Universal with

different application and web servers on UNIX, see the
following sections:
To deploy with WebLogic and Apache, see Deploying with

WebLogic and Apache, page 140 in Chapter 8,
Configuring and Deploying MicroStrategy Web
Universal.
To deploy with WebSphere and IBM HTTP Server, see

Deploying with WebSphere 5.x and IBM HTTP Server,
page 165 in Chapter 8, Configuring and Deploying
MicroStrategy Web Universal.
To deploy with Sun ONE (iPlanet), see Deploying with

Sun ONE (iPlanet) 8.0, page 179 in Chapter 8,
Configuring and Deploying MicroStrategy Web
Universal.

5
5. CONFIGURING
MICROSTRATEGY
INTELLIGENCE SERVER
Introduction
After installing MicroStrategy, you must complete a few

configuration tasks. This chapter addresses the processes
used to configure an installed MicroStrategy suite of products
using the MicroStrategy Configuration Wizard.
The MicroStrategy platform includes a Tutorial

project, which is a sample data warehouse and a
demonstration project you can use to learn about the
various features that MicroStrategy offers. It is ready
to be used and requires no additional configuration
tasks. If you want to set up a new system using your
own data, you must read this chapter and perform the
tasks it describes.
Configuration prerequisites
Using the MicroStrategy Configuration Wizard

5 Configuring MicroStrategy Intelligence Server Installation and Configuration Guide
Configuration prerequisites
Before you begin using the Configuration Wizard you should
satisfy the following requirements:
Install the necessary MicroStrategy products. You should

have at least MicroStrategy Desktop and MicroStrategy
Intelligence Server installed. For information on how to
install MicroStrategy on Windows, see Chapter 3,
Installing MicroStrategy on Windows. For information
on how to install MicroStrategy on other operating
systems, see Chapter 4, Installing MicroStrategy on
UNIX and Linux.
Have access to an empty database location certified to

house the metadata. For a list of certified metadata
platforms, see the MicroStrategy platform readme file.
MicroStrategy products must be configured on the

machine on which they are installed. You cannot
configure them remotely.
88 Configuration prerequisites 2005 MicroStrategy, Inc.

Installation and Configuration Guide Configuring MicroStrategy Intelligence Server 5

The MicroStrategy Configuration Wizard automates much of
the configuration process, prompting you only when critical
information is required. With this tool, you can configure
metadata repository and statistics tables, MicroStrategy
Intelligence Server, and multiple project sources.
If you are configuring using the Windows operating system,

you must have administrative privileges on the computer in
which the Intelligence Server is installed, so that you can set
the parameters necessary to start the Intelligence Server and
invoke server-definition objects.
You can set up the MicroStrategy Configuration Wizard to

work in silent or unattended mode, by clicking Advanced on
the Welcome page. This opens the Advanced Options page. It
uses a response file to run automated installations from local
or remote locations. For more information, refer to
Configuring a response.ini file for the Configuration
Wizard, page 257, in Chapter 10, Automated Installation
and Configuration on Windows, or refer to Configuring
through command line mode, page 279, in Chapter 11,
Automated Installation and Configuration on UNIX.
After completing any of the three main configuration

tasks, Metadata Repository and Statistics Tables,
MicroStrategy Intelligence Server, and Project
Sources, a check mark appears besides the option and
the next option is selected.
Overview of the MicroStrategy Configuration Wizard

The MicroStrategy Configuration Wizard opens
automatically after you install MicroStrategy products and
restart your machine. The MicroStrategy Configuration
Wizard allows you to configure
Metadata repository and statistics tables
Intelligence Server
Project Sources
2005 MicroStrategy, Inc. Using the MicroStrategy Configuration Wizard 89

The metadata consists of tables that contain the definitions

for nearly all MicroStrategy objects, including database
logins, server definitions, database instances and
connections, reports, metrics, facts, and so on. The metadata
repository or database contains information that facilitates
the transfer of data among MicroStrategy applications and
between MicroStrategy applications and the data warehouse.
MicroStrategy applications use the metadata database to
transform user requests into SQL queries and translate the
results of those queries back into MicroStrategy objects, such
as reports and documents. It is mandatory to have a metadata
repository to which an Intelligence Server can connect.
Statistics tables are used to record a variety of statistical

information about the usage and performance of a
MicroStrategy system. You can set which statistics are
recorded in the statistics tables and use MicroStrategy
Enterprise Manager, which is a part of the MicroStrategy
Administrator product, to analyze the data and locate
opportunities for system performance tuning. For more
information about the statistics tables and Enterprise
Manager, refer to the MicroStrategy System Administration
Guide.
The MicroStrategy Intelligence Server requires a server

definition to run. A server definition is a MicroStrategy
object stored in the metadata repository. It contains
information about the configuration of Intelligence Server,
such as governing settings, which projects should be loaded,
which communication protocols should be used, and so on.
Before you can use the MicroStrategy Intelligence Server, you

must determine from the MicroStrategy Configuration
Wizard the server definition that the Intelligence Server
should use.
Many server definitions can exist in the metadata, but

you can install only one Intelligence Server on one
server machine and MicroStrategy Intelligence Server
uses only one server definition at a time.
90 Using the MicroStrategy Configuration Wizard 2005 MicroStrategy, Inc.

Project Sources
The highest level icon in the Folder List of MicroStrategy

Desktop is the project source. Project sources are the highest
level objects in the MicroStrategy environment and represent
a connection to a metadata database or a MicroStrategy
Intelligence Server. The project source stores the location of
the metadata repository or the MicroStrategy Intelligence
Server definition that is used to run the project. Through a
project source you can create, manipulate, and administer
MicroStrategy projects.
Note the following:

For WindowsProject Source is available only if the
Desktop product is installed on the machine.
For UNIXProject Source is available only if

MicroStrategy Control Center exists. Control Center
allows you to configure project sources.
Configuring MicroStrategy software
You can configure a 3-tier or a 2-tier setup for MicroStrategy.

The following figure describes how to configure
MicroStrategy to suit a 3-tier environment. It also shows how
the various components of the MicroStrategy Configuration
Wizard, the Metadata Repository, the Intelligence Server,
and the Project Source interact with each other.

The following figure describes how to configure

MicroStrategy to suit a 2-tier environment. It also shows how
the various components of the MicroStrategy Configuration
Wizard, the Metadata Repository and the Project Source
interact with each other.
Itproduction
is not recommended to use a 2-tier setup for the
environment.
The following are the high-level steps to configure

MicroStrategy software through the Configuration Wizard.

To configure MicroStrategy through the Configuration Wizard
1 If you are installing MicroStrategy on Windows:
On the Windows Start menu, point to Programs, then

to MicroStrategy, and then choose Configuration
Wizard. The Configuration Wizard opens with the
Welcome page displayed.
If you are installing MicroStrategy on UNIX:
In a UNIX console window, browse to <HOME_PATH>

where <HOME_PATH> is the directory you specified as
the home directory during installation. Browse to the
folder bin and type ./mstrcfgwiz, then press
ENTER. The MicroStrategy Configuration Wizard
opens with the Welcome page displayed.
2 Choose from the following configuration tasks and click

Next to begin the selected task.
Metadata Repository and Statistics Tables: runs the
SQL scripts necessary to create and initialize the
metadata and statistics tables in the database location
you select.
When you create a metadata repository, a 3-tier

project source is automatically created.
Set up MicroStrategy Intelligence Server: allows

you to create a new server definition object in the
metadata repository you select. This setup provides
3-tier access to all projects that are stored in the
repository. This option also lets you link to or delete an
existing server definition. You must specify a port
number to be used by the Intelligence Server.

Project Sources: A project source contains the

configuration information that each client requires to
access an existing project. It stores the location of the
metadata repository and MicroStrategy Intelligence
Server that is used to run the project. Hence, a project
source determines how the Desktop product accesses
the metadata.


When you create a metadata repository, a 3-tier

project source is automatically created. You can
use this option, Project Sources, to create multiple
project sources for your project, or to create a 2-tier
project source.
The remainder of this chapter describes each configuration

option in detail.
After completing these steps, an empty metadata repository

is created. To learn how to add projects to your metadata
repository, refer to Creating a project using MicroStrategy
Desktop, page 120 in Chapter 6, Creating a Project.
For information about advanced configuration functionality

on Windows, such as configuring in an SMS environment or
using configuration response files, see Chapter 10,
Automated Installation and Configuration on Windows.
For information about advanced configuration functionality

on UNIX, such as using configuration response files for
automated configuration, see Configuring through
command line mode, page 279 in Chapter 11, Automated
Installation and Configuration on UNIX.

Creating a metadata repository and statistics tables

The general configuration process for creating a metadata
repository and statistics tables is as follows:
Itrepository
is recommended that you create the metadata
and the statistics tables in different
databases to ensure enhanced performance.
To create metadata repository and statistics table
1 Select a data source name (DSN) that points to the

database in which to create the metadata repository or
statistics tables.
2 Verify that the ODBC driver used to connect to the

database is MicroStrategy certified.
For information on ODBC, Appendix B, ODBC and

DSNs.
3 Select the SQL scripts to use for creating your metadata

repository or statistics tables.
ODBC drivers and validation
The validation process verifies the selected database driver

used by the DSN you chose in the first step.
MicroStrategy software ships with a current list of

MicroStrategy-branded ODBC drivers, that is, drivers that
are certified to work with MicroStrategy products. If the
driver you are using is found to be invalid, the system returns
a message that the driver is invalid and a comparison of the
selected driver and a certified driver is displayed.
See the MicroStrategy readme file for details about supported

and certified ODBC drivers. To access the MicroStrategy
readme files:
On Windows: Go to the Start menu, point to Programs,

then to MicroStrategy, and then choose ReadMe.

On UNIX: In the UNIX File Manager, browse to

<INSTALL_PATH>, where <INSTALL_PATH> is the
directory you specified as the install directory during
installation, and double-click the ReadMe.htm file.
Note the following:

Although it is possible to use a non-certified driver, it
is strongly recommended that you contact your
database vendor to obtain a certified driver if the
selected driver is not certified as valid.
MicroStrategy products include certified ODBC

drivers for you to use. The MicroStrategy General
Information Readme lists these MicroStrategy ODBC
drivers and recommended database connection
settings for them. MicroStrategy ODBC drivers only
work with MicroStrategy products.
SQL scripts
MicroStrategy has database-specific SQL scripts for creating

metadata and statistics tables. The scripts for each certified
database platform are shipped with the product. The
MicroStrategy Configuration Wizard automatically selects a
default script based on your ODBC drivers database
platform.
You must change from the default script only if a

double-byte script or a custom script is required.
By default, all the scripts reside in the directory where you

installed MicroStrategy and are identified by the .sql
extension. It is highly recommended that no edits be
performed on these scripts, except on rare occasions and only
by skilled database personnel.

The Metadata Repository and Statistics Tables option on

the Configuration Wizard provides the following selections to
start configuring a metadata repository:
Create Metadata Tables
Create Default Configuration
Create Statistics Tables
Create Default Project Source (2 Tier with Standard

Authentication)
The following sections provide details about each of these

options.
Create metadata tables
The Create Metadata Tables option lets you create

MicroStrategy metadata tables. If you choose this option, you
can create the metadata repository in the database location of
your choice. Additionally, a default configuration is created in
the tables. This populates the tables with the basic data
required for the MicroStrategy metadata, such as the default
project folder structure and some basic connection
information.
To create metadata tables
1 Select Metadata Repository and Statistics Tables and

click Next.
2 Select the Create Metadata Tables check box and click

Next.
3 Select to configure the repository in either an ODBC

database or in a Microsoft Access database.

Although it is possible to use the Microsoft Access

database for the metadata repository, it is not a
suitable metadata repository for a production project.
You should not use Microsoft Access for anything
other than a proof-of-concept or demonstration type
of application.
Creating repository in an ODBC database
4 Select an existing ODBC DSN from the drop-down list and

specify a user name and password. You can also click New
to create a new DSN, and MD Prefix if you want to specify
a metadata table prefix.
5 If you click New, choose the SQL script for creating the
metadata by accepting the default, or browse to select the
SQL script and click Finish. It is recommended that you
select the default SQL script.
6 Click Next, review the summary information, and click

Finish to create the metadata repository.
For more information on creating DSNs, Appendix B, ODBC

and DSNs.
Create default configuration
This option lets you create the default configuration for the
MicroStrategy metadata. It is disabled if Create Metadata
Tables is selected because the process of creating the default
configuration occurs automatically when the Create
Metadata Tables check box is selected.
The default configuration populates the metadata tables with

the basic necessities required for the MicroStrategy
metadata, such as the default project folder structure and
some basic connection information.
You must select the Create Default Configuration check box

if you have created empty metadata tables outside the
Configuration Wizard using a custom SQL script. You must
do this to initialize the metadata with a default configuration.
It is not recommended to create empty metadata tables
outside the Configuration Wizard.

To create a default configuration

click Next.
2 Select the Create Default Configuration check box and

click Next.
You must clear the Create Metadata Tables check

box to enable this check box.

database or a Microsoft Access database.

of application.
Creating a repository in an ODBC database
4 Choose an ODBC DSN and provide a user name and

password.
To specify a metadata table prefix, you can click New to
create a new DSN and MD prefix.

Finish to create the default configuration.
Note the following:

If MicroStrategy metadata tables are not present in the
database location you specified, you are prompted to
create them. Click Yes to create the metadata tables,
or click No to cancel.
If a configuration is already present in the database

location you specified, you are prompted to overwrite
it. Click Yes to overwrite the existing configuration or
click No to cancel.

Create statistics tables
The Create Statistics Tables option lets you create

MicroStrategy statistics tables in the database of your choice.
These tables are used to maintain and monitor system
activity. You can run MicroStrategy Enterprise Manager
against the statistical information to analyze and interpret
the statistics.
To create statistics tables

click Next.
2 Select the Create Statistics Tables check box, and click

Next.

database or in a Microsoft Access database.

database for the statistics tables, it is not suitable for a
production project. You should not use Microsoft
Access for anything other than a proof-of-concept or
demonstration type of application.
Creating repository in an ODBC database
4 Select an ODBC DSN from the drop-down list, and

provide a user name and password.
You can click New to create a new DSN.
5 If you click New, choose the SQL script for creating the
statistics tables by accepting the default, or browse to
select the SQL script and click Finish. It is recommended
that you select the default SQL script.

Finish to create the default configuration.

Create default project source (2-tier with

standard authentication)
When you create a metadata repository a 3-tier project source

is automatically created. To create a 2-tier project use the
option, default project source (2-tier with standard
authentication), to access your MicroStrategy metadata.
Enter the name of the project source to be created in the
Project Source Name box, or use the default name of New
Project Source.
Note the following:

This option is intended to be used in conjunction with
one or more of the other available options. If you want
to simply create a new project source, use the Project
Sources option on the Welcome page of the
Configuration Wizard. For information on project
sources, see Project Sources, page 108.
For more information about authentication modes,

refer to the MicroStrategy System Administration
Guide.
Configuration messages
Depending on the selected ODBC database, different

messages might be displayed prompting you to complete the
configuration successfully. Two examples of messages that
require action are as follows:
An existing Metadata Repository
configuration was found at this location.
Continuing will remove all existing
metadata objects. Are you sure you want to
continue?
This message is displayed if the Configuration Wizard

detects an existing metadata repository in the database
location you specified.
Ifmetadata
you continue, all information in the existing
repository is overwritten.

No Metadata Tables are defined, would you

like to create them?
This message is displayed if there is no existing metadata

repository and you have not chosen to create one.
The messages are displayed if there are conflicts or some

requirements are not met. These messages help you resolve
the conflicts and lead you through the configuration process.
Setting up the MicroStrategy Intelligence Server

You use the Configuration Wizard to create, link, or delete
server definitions that are stored in the metadata repository.
The following list describes these options in detail:
Create: When you create a new server definition in the

metadata repository of your choice, all its parameters are
set as default. Creating a new server definition creates an
entry in the machines configuration file that points to the
metadata. This is used by MicroStrategy Intelligence
Server at startup. You can modify a server definition using
MicroStrategy Intelligence Server Administrator. For
information on MicroStrategy Intelligence Server
Administrator, refer to the MicroStrategy System
Link: You link a server definition of your choice to

MicroStrategy Intelligence Server. When you use the
MicroStrategy Configuration Wizard to link to a server
definition different from the existing one, you are
changing the machines configuration information to
point to a different server definition, which can be in an
entirely different metadata.
Delete: When you delete a server definition, you are
deleting the server definition object from the metadata
repository, but not from the MicroStrategy Intelligence
Server software that you installed.
You must run the Configuration Wizard locally on the

Intelligence Server machine. You cannot create, link,
or delete server definitions remotely.

If you create a new server definition or link to an existing one,

you can load the projects to use with the server definition
from within the Configuration Wizard.
If the password to the metadata has changed in the database,

use the Connect to Metadata Repository page in the
MicroStrategy Configuration Wizard to update your
password.
The MicroStrategy Configuration Wizard provides the

following pages to manage server definitions:
Connect to metadata repository

User authentication
Create, link, or delete a server definition
Specify a port number
Select projects
The following sections provide details about each of these

options.
Connect to metadata repository
On the MicroStrategy Configuration Wizard, click Setup

MicroStrategy Intelligence Server to access the Connect to
Metadata Repository page. On this page, select the ODBC
Data Source Name (DSN) to use when connecting to the
metadata repository.
Selecting the ODBC DSN Driver execution mode
1 Select MicroStrategy Intelligence Server and click Next.
2 Select an ODBC DSN from the drop-down list and specify

a user name and password.
You can click the following:
New to create a new DSN

MD Prefix if you want to specify a metadata table

prefix
Temp Table Prefix to specify a prefix for the

temporary tables used by the server definition

of application.
You can only configure your database instance to be in

multiprocess mode as all available ODBC drivers are 32-bit
and Intelligence Server processes are 64-bit. Multithreaded
mode is not available. The following note provides a short
explanation of multiprocess execution mode.
Amemory
process is a running executable that resides in a
space and uses operating system resources.
An application can consist of one or several processes.
Each process owns an address space which is not
shared with other processes. If one process fails, the
others are not affected. This tends to make
multiprocess applications more robust and stable than
single process applications at the expense of overhead
in memory space and increased resources.
User authentication
After you connect to a metadata repository, click Next in the

Configuration Wizard to access the User Authentication page.
In this page you specify the username and password for the
MicroStrategy user to access the metadata to create, link, or
delete server definitions. By default, the username is
Administrator and it has no password. If you are setting up
the MicroStrategy Intelligence Server for the first time, use
the default username and password.

For security reasons, you should change the

Administrator username and password as soon as
possible after you initially configure the system. Refer
to the MicroStrategy System Administration Guide
for details about passwords and other user
management information.
To authenticate a user
1 Accept the default user name and password, if you are

setting up MicroStrategy Intelligence Server for the first
time. For subsequent uses specify an appropriate
administrative user name and password.
2 Click Next to perform the authentication and access the

Create, Link, or Delete a Server Definition page.
Create, link, or delete a server definition
After you specify the user name and password for the user,
click Next to access Create, Link, or Delete a Server
Definition page. From this page, you can create a new server
definition, link to an existing server definition, or delete a
current server definition. The steps to create, link, or delete a
server definition are as follows.
To create a new server definition
1 Select Create New Server Definition.
2 Specify a name in the Server Definition Name text box,

which defaults to the name of the machine, and click
Next.
3 Click Yes or No to accept or reject the new server

definition as the default server definition. If you click Yes,
this server definition is used by MicroStrategy
Intelligence Server when it starts. If you click No, this
server definition is not used by MicroStrategy Intelligence
Server when it starts.

To link to an existing server definition
1 Select Use Selected Server Definition.
2 Select an appropriate server definition from the list of

existing server definitions and click Next.
To delete a server definition
1 Select Delete Selected Server Definition.
2 Select the server definition to delete from the list of

existing server definitions, and click Next.
3 Read the summary information and click Yes to confirm

the deletion.
Specify a port number
After you create or link to an existing server definition, click

Next to access the Port Number page. In this page you can
use the default port number or specify another port number.
If the port number is used by another process, for example in
a shared environment, specify a free port number. For
instructions on how to find an available port number, see
Port number is in use, page 403 in Appendix E,
Troubleshooting, Troubleshooting.
To specify a port number
1 Specify a port number if required, or use the default port

number of MicroStrategy Intelligence Server, which is
34952.
2 Click Next to continue.

Select projects
After you specify a port number, click Next to access the

Select Projects page. This page displays all the projects that
are in the metadata repository. You can select projects to use
with the server definition you have chosen. The projects you
select are loaded on the server at startup.
To select projects
1 Select or clear the check boxes for each project to use with
this server definition and click Next.
2 Read the summary information and click Finish to create

the new server definition or to assign the selected server
definition to the Intelligence Server. You are prompted to
stop the Intelligence Server service.
3 When the new server definition is created, you are

prompted to restart the Intelligence Server service.
If you create a new server definition, it is displayed in the

list of existing server definitions for that metadata.
If you assigned an existing server definition to the

Intelligence Server and the existing project source uses
this server, a related message is displayed.
Starting, stopping, and restarting the server
The primary function of the Service Manager is to provide a

way to start and stop Intelligence Server. For additional
information, refer to the MicroStrategy System

Project Sources
When you create a metadata repository, by default it creates a
3-tier project source. Hence use the option, Project Sources,
if you need to create multiple project sources or a 2-tier
project source.
The different types of project sources are:
Direct project sources that connect directly to the

metadata through ODBC.
Server project sources that connect to the metadata

through an Intelligence Server.
Note the following:


Direct (2-tier)
A 2-tier project source is used to connect directly to the

metadata repository using ODBC DSN.
Connecting to a Direct (2-tier) project source
1 Select Project Sources on the Configuration Wizard, and

click Next.
2 Type a Project Source Name. Select Direct (2-tier) as the

Connection Type, and click Next.
3 Choose the ODBC DSN that points to the metadata

containing the MicroStrategy projects to access. Specify a
user name and password, and click Next.
You can also click New to create a new DSN and click MD
Prefix to specify a metadata table prefix if necessary.

4 Select the authentication mode for the project source and

click Next. For more information about authentication
modes, refer to the MicroStrategy System
5 Review the summary information and click Finish to

create the project source.
MicroStrategy Intelligence Server (3-tier)
A 3-tier project source is used to connect to the metadata

using the MicroStrategy Intelligence Server.
Connecting to a MicroStrategy Intelligence Server (3-tier)

project source
1 Select Project Sources and click Next.
2 Type a Project Source Name. Choose the MicroStrategy

Intelligence Server (3-tier) option and click Next.
3 Specify the name and port number for the Intelligence

Server to which to connect the project source, and click
Next. See the following note regarding the port number.
The port number is how the Intelligence Server

process identifies itself on the server on which it is
running. When the Intelligence Server receives a
network call from a client, that is, Desktop, Web, and
so on, it forwards those calls to the Intelligence Server
port number that is specified in the call.
The default port number for MicroStrategy
Intelligence Server is 34952. When it is set to 0, it
takes the default value of 34952. However, if you use a
non-default port number, this number must be
provided while connecting through MicroStrategy
Desktop.
4 Select the authentication mode to be used for the project

source and click Next. For more information about
authentication modes, see the MicroStrategy System

5 Review the summary information and click Finish to

create the project source.
Next steps
Now you have configured MicroStrategy and are ready to
create a project. There are various ways to create a project to
get your MicroStrategy project started. The different methods
to create a project are described in Chapter 6, Creating a
Project.
The MicroStrategy platform provides a Tutorial

project, which is a sample data warehouse and
demonstration project you can use to learn about the
various features that MicroStrategy offers. It is ready
to be used and requires no additional configuration
tasks. To use the MicroStrategy Tutorial, refer to the
MicroStrategy Basic Reporting Guide for more
information. However, if you want to create a new
project using your own data, you must read Chapter 6,
Creating a Project in detail and perform the tasks it
describes.

6
6. CREATING A PROJECT
Introduction
There are several methods for creating a project and editing a

project. This chapter introduces you to the overall process of
building a MicroStrategy project. It also provides definitions
for the MicroStrategy Desktop components that are essential
for creating a project.
You may choose not to create your own project at this

stage but use the MicroStrategy Tutorial for learning
purposes. The Tutorial has already been created and
configured for you.
MicroStrategy Desktop definitions
Creating a project using Project Builder
Creating a project using MicroStrategy Desktop
MicroStrategy project schema

6 Creating a Project Installation and Configuration Guide
MicroStrategy Desktop definitions

This section defines some of the basic terminology used in
project creation in MicroStrategy Desktop.
MicroStrategy metadata
MicroStrategy metadata is stored in a relational database
with a predefined structure, which MicroStrategy has
designed. The RDBMS for the metadata and warehouse do
not need to be the same. All schema objects, application
objects, configuration objects, and project settings are stored
in the metadata.
You can find the list of supported RDBMS platforms in

the Readme file that installs with MicroStrategy
products. By default, the Readme file can be found in
C:\Program Files\Common
Files\MicroStrategy\readme.htm.
Metadata shell
Before you can populate the metadata database with data, the
necessary tables must be present. The metadata shell refers
to the set of blank tables that are created when you initially
implement a MicroStrategy business intelligence
environment.
You create the metadata shell with the MicroStrategy

Configuration Wizard, which creates the necessary tables and
also populates some tables with basic initialization data.
112 MicroStrategy Desktop definitions 2005 MicroStrategy, Inc.

Installation and Configuration Guide Creating a Project 6
MicroStrategy objects
Project creation and navigation in MicroStrategy is generally
handled through the creation and use of various types of
objects. You can build and manipulate three fundamentally
different kinds of objects in MicroStrategy:
Configuration objectsObjects built by a project architect

or administrator. These objects are not used directly for
reporting, but rather they serve to provide important
information or governing parameters for connectivity,
user privileges, and project administration. As a general
rule, configuration objects are built and manipulated with
MicroStrategy Desktop or the managers that are
accessible from within the Administration icon in
MicroStrategy Desktop. A database instance or user are
examples of configuration objects.
Schema objectsObjects that are built in the application

to correspond to database objects, such as tables, views,
and columns. MicroStrategy Desktop is used to build and
manipulate schema objects such as facts, attributes,
hierarchies, and other objects in the Schema Objects
folder in MicroStrategy Desktops folder list.
Application objectsObjects built or manipulated using

MicroStrategy Desktop. The definition of application
objects such as reports, filters, metrics, and prompts are
derived from schema objects.
Project source
The project source configuration object is the highest-level
MicroStrategy object that exists. It appears in the folder list
and represents a connection to a metadata database. This
connection is achieved in one of two ways:
Direct or 2-tier modeConnects to the metadata by

specifying a DSN, login, and password to a metadata
database.
Itproduction
is not recommended to use a 2-tier setup for the
environment.
2005 MicroStrategy, Inc. MicroStrategy Desktop definitions 113

Server or 3-tier mode Connects to the metadata by

pointing to an Intelligence Server definition, which in
turn governs and validates the connection to the
metadata.
After the connection to the metadata is established, every

object definition you create within this project source is
stored in this metadata. This includes application objects,
schema objects, and configuration objects from any number
of projects defined within this project source.
Database instance
The database instance is a configuration object that
represents a connection to a data warehouse. When you
define a project, you specify the data warehouse location by
selecting a database instance with the appropriate connection
parameters.
Project
A project is the intersection of a data warehouse, metadata
repository, and the user community. It is the highest-level
object in the MicroStrategy reporting environment. A project
is where you build and store all schema objects and
information you require to create an application, which
together provide for a flexible reporting environment. A
project
Determines the set of warehouse tables to be used, and
therefore the set of data available to be analyzed.
Contains all schema objects used to interpret the data in

those tables. Schema objects include facts, attributes,
hierarchies, and so on.
Contains all reporting objects used to create reports and

analyze the data. Reporting objects include metrics,
filters, reports, and so on.

defines the security scheme for the user community that

accesses these objects to operate. Security objects include
security filters, security roles, privileges, access control,
and so on.
Many of the schema objects and reporting objects are

discussed in the MicroStrategy Basic Reporting
Guide and in the MicroStrategy Advanced Reporting
Guide. Security and other project-level administrative
features are discussed in the MicroStrategy System
A project can contain any number of reports in addition to a

number of other objects that support simple and advanced
reporting requirements. The objects include filters, prompts,
and metrics. Conceptually, the project is simply the
environment in which all related reporting is done.
For information on database instances, see the

MicroStrategy System Administration Guide.
Some key concepts to understand before you begin creating a

project are as follows:
A project is created within a specified metadata

repository, determined by the project source through
which you create the project.
The projects warehouse location is specified by

associating it with the appropriate database instance.
For information on project sources, see Project Sources,

page 108.
With MicroStrategy 8.0, you can create OLAP cube

reports using data from SAP BW. For detailed
information on how to set up the SAP BW project,
refer to Creating OLAP cube reports in the
MicroStrategy Advanced Reporting Guide and the
MicroStrategy online help.
For information on how to use your own customized

SQL statements to create reports, see the Creating
Freeform SQL reports chapter in the MicroStrategy
Advanced Reporting Guide.

Now that you understand the MicroStrategy metadata, the

project source, the database instance, and the project, you
can begin to build an understanding of how these various
pieces work together to provide an integrated business
intelligence environment as shown in the following diagram:
Language display of a project
Projects that use single-byte interfaces create autostyles with

fonts that are incompatible with double-byte characters.
Autostyles are predefined formatting styles that allow you to
standardize formatting among reports. For example, you
create a project in MicroStrategy Desktop using the English
interface, which is a single-byte language, and then you use a
Chinese interface that is a double-byte language, you can see
Chinese characters on the MicroStrategy Desktop. However,
if you export a report to PDF, the PDF uses autostyle fonts
that are in English and loses the Chinese characters.
For more information on autostyles refer to Report

Manipulation Essentials in the Basic Reporting Guide.

When you create a new project or update the metadata, a

language check ensures that the language settings in the
CURRENT_USER registry key, the LOCAL_MACHINE
registry key, and the Project locale property match before an
update takes place. The system performs the following
checks:
In a 2-tier configuration, it checks that the language under

the LOCAL_MACHINE registry key matches the language
under the CURRENT_USER registry key.
In a 3-tier configuration, it checks that the language under
the CURRENT_USER registry key on the client machine
matches the language under the LOCAL_MACHINE
registry key on the server machine.
The MicroStrategy interface obtains the language

information from the CURRENT_USER registry key and the
server obtains the language information from the
LOCAL_MACHINE registry key. This can lead to
inconsistencies in the language display. The language check
prevents these inconsistencies and ensures that the language
display is consistent across the interface.

Creating a project using Project Builder

Project Builder is a wizard that allows you create simple
MicroStrategy projects quickly and efficiently. With Project
Builder, you can build project prototypes rapidly for
proof-of-concept tests with your own data. Project Builder
was created with speed in mind and hence it provides only a
subset of the features and functionality of MicroStrategy. To
create a project for your production setup, other methods can
be used to add greater functionality and complexity to your
project in the production setup. For more information on
other methods refer to Creating a project using
MicroStrategy Desktop, page 120. For more information on
Project Builder, refer to the MicroStrategy online help.
Using Project Builder

By default, Project Builder uses a Microsoft Access database
for the metadata repository. You can use the Microsoft Access
database for creating the metadata repository as the project
you are creating is only a prototype project.
While it is possible to use an Access database for the

metadata repository, it is not a suitable metadata
repository for a production project. You should not use
Microsoft Access for anything other than a
proof-of-concept or demonstration type of application.
If you intend to create a production project, refer to Creating

a project using MicroStrategy Desktop, page 120.
The Project Builder contains the following options that assist

you in creating a prototype project:
My Database: allows you to name the project and select

the database that contains the business information you
want to analyze with the project you create.
My Business Model: allows you to identify relationships

that define the business information in your database.
Project Builder uses this structure to help you analyze the
data.
118 Creating a project using Project Builder 2005 MicroStrategy, Inc.

My Reports: allows you to use the attributes and metrics

you defined using My Business Model, to create a variety
of reports. These reports are based on pre-defined
templates. You can also preview and run the reports.
You can learn about creating and manipulating reports

in more detail in the MicroStrategy Basic Reporting
Guide.
After you create a project using the Project Builder you can
add more tables, facts, attributes, and hierarchies to the
project. The following sections describe the MicroStrategy
tools you can use to add additional objects to your project:
Warehouse Catalog allows you to add more warehouse
tables to your project. You can add tables in bulk using the
Warehouse Catalog, unlike Project Builder that requires
you to add just a few tables at a time.
Fact Creation Wizard allows you to add more facts to

your project. You can create facts in bulk using the Fact
Creation Wizard, unlike Project Builder that requires you
to create one at a time.
Attribute Creation Wizard allows you to add more

attributes to your project. You can create attributes in
bulk using the Attribute Creation Wizard, unlike Project
Builder which requires you to create one at a time.
Hierarchy Editor allows you to add more hierarchies to

your project. The Hierarchy Editor provides an intuitive
graphical interface for creating hierarchies.
Click MicroStrategy Desktop to open MicroStrategy

Desktop, explore your project, and access the tools described
above. You can close Project Builder now. The following
section, Creating a project using MicroStrategy Desktop,
page 120 describes how to access and use these tools.
Note the following:

When MicroStrategy Desktop opens, you might be
prompted to log in to an existing project source,
especially if you have installed MicroStrategy Tutorial.
If you are prompted, click Cancel and then choose
which project source to use.
2005 MicroStrategy, Inc. Creating a project using Project Builder 119

You can view your project even if you have installed

MicroStrategy Web or MicroStrategy Office. If you are
creating a new system, they are most likely not
properly configured yet and may not work as expected.
For information about how to configure and use these
products, see Connecting MicroStrategy Web to the
Intelligence Server, page 136 in Chapter 7, Deploying
Your Project with MicroStrategy Web.
Creating a project using MicroStrategy Desktop

This section describes how to create a project for your
production setup using MicroStrategy Desktop. It provides
advanced functionalities and greater complexity to your
project. It allows you to create a new project and add the
following objects to it or to an existing project:
tables
facts
attributes
shortcut objects
Creating a new project

Use the Project Creation Assistant wizard to create a new
project.
To create a new project
1 Log in to MicroStrategy Desktop.
2 From the Schema menu, select Create New Project. The

Project Creation Assistant opens.
3 Click Create project. The New Project page opens.
120 Creating a project using MicroStrategy Desktop 2005 MicroStrategy, Inc.

4 Specify the name, description, and default directory

location for the project.
5 Select a project source from the drop-down list, or click

New to create a new project source for your project.
The project source should point to the metadata

repository in which to create the project.
6 Click OK. The Login dialog box opens.
Ifdatayousource
are not authorized to create projects in the
you have selected, you cannot proceed
to the next step.
7 Specify a valid login ID and password and click OK. The

Project Creation Assistant creates an empty project in the
metadata database and redisplays the Project Creation
Assistant.
You can add the following through the Project Creation

Assistant wizard:
tables from the Warehouse Catalog
facts
attributes
Alternatively, you can use the various editors available

through the schema menu to create these schema objects at a
later stage.
For information on how to add tables using the Warehouse

Catalog, see Adding tables using the Warehouse Catalog,
page 122. For information on how to add facts, see Creating
facts, page 124. For information on how to add attributes, see
Creating attributes, page 126. You can also create shortcut
objects for your project. For more information on shortcut
objects and how to create them, see Creating shortcut
objects, page 130.
2005 MicroStrategy, Inc. Creating a project using MicroStrategy Desktop 121

Adding tables using the Warehouse Catalog

The Warehouse Catalog queries the data warehouse and lists
the tables and columns that exist in it. From this list, you can
choose the tables to add to your project. Every project can
have a unique set of warehouse tables.
The Warehouse Catalog lists the tables present in the

database that connect to your projects database
instance. The database login you use must have read
privileges at least. Database instances and database
logins are MicroStrategy objects that determine the
warehouse to which a project connects. If you want to
learn more about these objects, refer to the
MicroStrategy System Administration Guide.
You might want more MicroStrategy objects, such as large

number of lookup tables or relate tables that can be provided
efficiently by the Warehouse Catalog.
To open the catalog
1 Log in to the project source that contains your project in

MicroStrategy Desktop, and expand your project.
You must use a login that has Architect privileges. For

more information about privileges see Appendix B of
the MicroStrategy System Administration Guide.
2 Select the project from the folder list on MicroStrategy

Desktop.
3 From the Schema menu, choose Warehouse Catalog.

The Warehouse Catalog opens.
The left side of the Warehouse Catalog lists all available

tables and the number of rows each table contains. The list on
the right shows all tables already being used in the project.

From here you can add additional tables to the project or you
can remove tables you no longer require from the project.
Right-clicking any table provides you with additional
Warehouse Catalog functionality:
Table Structure allows you to view the columns that

make up the table and their data type.
Update Structure is similar to refreshing a display. If the

structure of the table has changed, use this option to see
the most recent version.
Show Sample Data displays the first 100 rows of data in

the table.
Table Prefix allows you to specify a table prefix to
differentiate the tables that belong to different to projects.
You can also create copies of the same table by providing a
different prefix to it.
Table Database Instance allows you to specify a

secondary database instance used to support database
gateways. For example, in your environment you might
have a gateway between two databases, perhaps an Oracle
database and a DB2 database. One of them is the primary
database and the other is the secondary database. The
primary database receives all SQL and passes it to the
correct database. From the perspective of MicroStrategy
products, you need to define two database instances, one
for the primary database and another for the secondary
database. The default database instance for the project is
set to be the primary database. In the Warehouse Catalog,
you must set the secondary database instance for any
tables that are found in the secondary database. This way,
MicroStrategy products know how to generate SQL for
each one.
Additionally, you can click Options on the Warehouse

Catalog tool bar to set advanced options. For more
information on using the Warehouse Catalog, see Appendix
C, Advanced Warehouse Catalog Usage.

To add and remove tables
1 Select the tables to add or remove. You can highlight

multiple tables using the CTRL+click or SHIFT+click
standard selection method.
2 To add tables to your project, click > to add the selected

tables. Click >> to add all the listed tables.
3 To remove tables from your project, click < to move them

to the left side. Click << to remove all the selected tables.
4 Click Save and Close to save your changes.
Creating facts
Facts are MicroStrategy objects that relate numeric data
values from the data warehouse to the project
creation/reporting environment. Relate is a key term here.
The facts correspond to physical columns in the data
warehouse. When you create facts, you are essentially
mapping column names in the warehouse to facts in the
MicroStrategy environment.
Facts are used to create metrics, which perform calculations

on the actual fact data.
For information on metrics, refer to the

MicroStrategy Basic Reporting Guide. To learn more
about facts and fact columns, refer to Data Modeling
in the MicroStrategy Basic Reporting Guide. For
more detailed discussions of both facts and metrics,
see the MicroStrategy Advanced Reporting Guide.

Project Builder guides you through the project creation

process, including the creation of facts. The Fact Creation
Wizard allows you to create multiple facts quickly and easily.
However it limits you to creating simple facts and does not
allow you to edit existing facts. Typically, you only use the
Fact Creation Wizard as part of the initial project creation, for
creating most of the facts for the project. You can use the Fact
Editor to add complexity to existing facts as your project
evolves.
The Fact Editor and the fact definitions you can create
with it are discussed in detail in the Facts chapter of
the MicroStrategy Advanced Reporting Guide.
To create facts
1 Log in to the project source that contains your project in

MicroStrategy Desktop and expand your project.

more information about privileges see Permissions
and Privileges of the MicroStrategy System
2 From the folder list on MicroStrategy Desktop, select the

project to add additional facts.
3 From the Schema menu, choose Fact Creation Wizard.

The Introduction page opens.
4 Review the Introduction page.
5 Click Define Rules. The Fact Creation Rules page opens,

which allows you to set basic fact creation rules. These
rules can make the process of choosing fact columns and
naming your facts considerably easier, especially if you
use consistent naming conventions and data types in your
data warehouse.
6 Select the rules for the Column data type and Fact name.
7 Click OK. The Introduction page opens.

8 Click Next. The Column Selection page opens. Columns

that are not currently being used in the project are listed
as available on the left side of the Column Selection page
whereas the fact columns available in the project are
placed on the right.
9 Choose the fact columns to use for your facts and click > to
add them to your project. Click >> to add all the listed
columns.
10 To remove fact columns from your project, click < to move

them to the left side. Click << to remove all the selected
columns.
11 Click Next. The Finish page opens.
12 Review the summary information in the Finish page and

click Finish to create the facts.
Creating attributes
Attributes are additional information that provides context
for facts. For example, assume Sales is a fact. If you know that
the sales figure for your company is $25,000, this
information is meaningless unless you have the context for
the sales figure, such as:
When were the sales made? Does the total represent sales
for a day, week, or year? Which day, week, or year?
Where were the sales made? Is that a company-wide total
or is it just for a particular region or store?
What products were sold and from what departments?

Who sold them?
Attributes allow you to answer these types of questions about

a fact. They provide context, categories, and levels for
convenient summarization and qualification of data.
The Attribute Creation Wizard guides you through creating

new attributes to use in your project.

Parent and child attributes
An attribute can have two parts, a parent and child. This

helps to define the relationship that one attribute has with
another attribute. A child attribute can have only parent,
whereas a parent attribute can have multiple children. For
example, a store may split the United States into different
regions such as Northeast and Southwest. The regions are the
children of the parent attribute, which is United States. For
more information on attribute relationship, refer to the
Attributes chapter in the MicroStrategy Advanced
Reporting guide.
Compound attributes
A compound attribute is any attribute with more than one

column specified as the ID column. For example, in the
MicroStrategy Tutorial, the Distribution Center attribute is a
compound attribute. To uniquely identify a distribution
center, you have to know both the distribution center ID and
the country ID. This is because the distribution center ID can
be reused in different countries. See the note at the end of
this table.
Attribute elements are the unique values of an attribute. For

example, 2002 and 2003 might be elements of the Year
attribute. Reykjavik, Jakarta, and Brussels might be elements
of the International Capital attribute.
To create attributes using the Attribute Creation Wizard
1 In MicroStrategy Desktop, log in to the project source that

contains your project and expand your project.

more information see Privileges of the MicroStrategy
System Administration Guide for more information
about privileges.
2 From the folder list, select the project to which to add new
attributes.

3 From the Schema menu, choose Attribute Creation

Wizard. The Introduction page opens.
4 Review the Introduction page.
5 Click Define Rules to set some basic attribute creation

rules. The Attribute Creation Rules page opens. These
rules can make the process of choosing attribute columns
and naming your attributes considerably easier, especially
if you use consistent naming conventions and data types
in your data warehouse.
Notice that some columns are already highlighted

based on the rules you defined. Only columns that are
not currently being used in the project are listed as
available on the left side of the ID Column Selection
page, whereas, the fact columns available in the
project, are placed on the right.
6 Select the check boxes as needed for Column data type

and Attribute name to define basic attribute creation
rules. Enter search criteria for the identifier column,
description column, and lookup tables in the Warehouse
search section. Click OK. The Introduction page opens.
7 Click Next. The ID Column Selection page opens.
An ID column is a column or group of columns that

uniquely identifies each element of an attribute. When
choosing the ID column for an attribute, make sure
that all values in the column are unique and that it
does not contain NULL values. Although
MicroStrategy Desktop allows it, you should never use
a column that has NULL or repeated values as the ID
column for an attribute. Doing so results in
unexpected behavior and errors.
8 Choose the columns to use for your attribute IDs and click
> to add them to your project. Click >> to add all the
attribute IDs.
9 To remove attribute ID columns from your project, click <

to move them to the left side. Click << to remove the
entire listed columns.

10 To create a compound attribute, complete the following

steps:
Click Compound Attributes and then click Add. The

New Compound Attribute dialog box opens.
Type a name for the attribute.
Select the columns that make up the key for the

compound attribute and click OK.
11 Click Next after adding all your attribute ID columns. The

Description Column Selection page opens.
12 Choose the default description column for each attribute.

In some cases, it may make sense to use the ID column as
the description column.
13 Click Next when you are finished. The Lookup Table

Selection page opens.
14 Choose the default lookup table for each attribute and

click Next.
If you have created a compound attribute, the
Compound Attribute Definition page opens. Specify
the lookup table and description column for the
selected compound attribute and click Next. The
Relationship Definition page opens.
If you have not created a compound attribute, the

Relationship Definition page opens.
15 To define children for each attribute follow the steps

below:
Select an attribute and click Add. The Select Children

Attributes dialog box opens.
Select the child attribute from the list of available child
attributes.
16 When you have defined children for all the attributes that
need them, click OK. The Finish page opens.
17 Review the summary information in the Finish window

and click Finish to create the attributes.

Creating shortcut objects

Shortcut objects are stand-alone objects in MicroStrategy
that represent links to other objects, such as reports, filters,
metrics, and so on. The shortcut objects are easy pointers for
navigation. Creating shortcuts to original objects in different
locations facilitates access to these objects without
duplicating them.
The shortcuts allow for easy maintenance by eliminating the

requirement to change numerous duplicate copies of the
original object. To change any parameters of an object, you
have to modify only the original object and these changes are
reflected in all locations where the shortcuts for this object
exist. To access the editor for the object, right-click the
original object or its shortcut, and select Edit. The original
object is displayed in the editor.
You can create shortcut objects either from the original object
or from the Shortcut Editor.
To create a shortcut object from the original object
1 Right-click the object for which to create a shortcut and

select Create Shortcut. The Browse for Folder dialog box
opens.
2 Navigate to the folder in which to save the shortcut and

click OK. The shortcut object is created in the destination
folder.
For example, you want to create a shortcut to the Units Sold

metric and save it in the Templates folder. Expand the
Metrics folder, then expand the Sales Metrics folder.
Right-click the Units Sold metric and choose Create
Shortcut. On the Browse to Folder dialog box, navigate to the
Templates folder and click OK. The Units Sold shortcut
object is created in the Templates folder.

To create a shortcut object using the Shortcut Editor
1 Open the folder in which to create a new shortcut object.
2 From the File menu, point to New, and then choose

Shortcut. The Open dialog box is displayed.
3 Navigate to the object for which to create a shortcut.

Select the object and click Open. Make sure the object
name is displayed in the Object name text field. The
shortcut object is created in the folder that you opened in
step 1.
For example, you want to create a new shortcut object to the

filter Year 2003 in the Templates folder. First, open the
Templates folder. From the File menu point to New, and then
choose Shortcut. On the Open dialog box navigate to the
filter Year 2003 and click Open. The shortcut to Year 2003 is
created in the Templates folder.

MicroStrategy project schema

All of the schema objects come together to form a projects
schema.
Though the concepts are related, this schema is not the

same as the physical warehouse schema. Rather, this
schema refers to an internal map that MicroStrategy
uses to keep track of attribute relationships, fact levels,
table sizes, and so on.
Whenever you make any changes to a schema objectfacts,

attributes, hierarchies, transformations, and so onyou must
indicate to MicroStrategy that new schema object definitions
have been included and that these definitions need to be
loaded into memory. You can do any of the following to
update a schema
Stop and restart MicroStrategy Intelligence Server, if in

three-tier mode.
Disconnect and reconnect to the project or the project

source, if in direct mode.
Manually update the schema.
Manually updating the schema is most effective.
To manually update the schema
1 In MicroStrategy Desktop, from the Schema menu, select

Update Schema.
2 In the Schema Update dialog box, select or clear the

following check boxes:
Update schema logical informationUse this option

if you added, modified, or deleted a schema object.
Recalculate table keys and fact entry levelsUse

this option if you changed the key structure of a table
or if you changed the level at which a fact is stored.
132 MicroStrategy project schema 2005 MicroStrategy, Inc.

Recalculate table logical sizesUse this option to

use MicroStrategy Desktops algorithm to recalculate
logical table sizes and override any modifications that
you have made to logical table sizes.
Logical table sizes are significant in how the

MicroStrategy SQL Engine determines the tables to
use in a query.
Recalculate project client object cache size Use

this option to update the object cache size for the
project.
3 Click Update.
You can also update the schema with the last saved settings
by clicking the Update Schema icon in the toolbar.
Next steps
Now you have learned how to create a new project and how to
enhance it by adding additional facts and attributes to it. To
learn how you can use these objects to create metrics, filters,
reports, documents, and so on, refer to the MicroStrategy
Advanced Reporting Guide.
After creating your project, you can deploy it to your user

community using MicroStrategy Web. To learn more about
how to deploy your project using MicroStrategy Web, refer to
Chapter 7, Deploying Your Project with MicroStrategy Web.
2005 MicroStrategy, Inc. Next steps 133


7
7. DEPLOYING YOUR PROJECT
WITH MICROSTRATEGY WEB
Introduction
This chapter describes the procedure to deploy a project to

your user community using MicroStrategy Web. The process
of deploying the ASP.NET version of MicroStrategy Web on
Windows with Microsoft Internet Information Services (IIS)
is explained in detail.
MicroStrategy Web simplifies the job of deploying to large

user groups because there is no need to install anything on
the end users machines. MicroStrategy Web can be accessed
from any supported browser because there is no code to
download. It provides the functionality that end users and
power users require to take full advantage of the
MicroStrategy product suite.
MicroStrategy Web Universal is platform-independent and

can be deployed using different combinations of operating
systems, Web servers, and application servers. If you are
deploying MicroStrategy Web Universal, Chapter 8,

7 Deploying Your Project with MicroStrategy Web Installation and Configuration Guide
Connecting MicroStrategy Web to the

Intelligence Server
You must have administrative privileges to deploy
MicroStrategy Web for your project. If this is the first time
you are logging in and you have not changed the default
MicroStrategy administrative login, you can use
Administrator as the login with no password. After the first
time, the user name and password should be changed for
security purposes.
To connect MicroStrategy Web to your Intelligence Server
1 On the Windows Start menu, point to Programs, then to

MicroStrategy, then to Web, and then choose Web
Administrator. The Web Administrator page opens. This
is the page where you connect MicroStrategy Web to the
2 Type the name of your Intelligence Server in the Add a

server manually box on the Web Administrator page.
3 Click Connect. All projects loaded on the Intelligence

Server are now available from MicroStrategy Web. Click
the Home icon to see the list of projects loaded on the
Intelligence Server you specified.
4 Send your users the URL:
http://webservername/microstrategy/asp/
where webservername is the name of the computer
hosting your Web server. For example, if the name of your
Web server machine is Web_Srv1, then the URL your
users would use to access MicroStrategy Web would be
http://Web_Srv1/microstrategy/asp
See the MicroStrategy System Administration

Guide for more information.
You have manually connected MicroStrategy Web to the

136 Connecting MicroStrategy Web to the Intelligence Server 2005 MicroStrategy, Inc.
Installation and Configuration Guide Deploying Your Project with MicroStrategy Web 7
You can also connect automatically whenever MicroStrategy

Web Server or Intelligence Server starts.
To make MicroStrategy Web connect to the Intelligence Server

automatically
1 On the MicroStrategy Web Administrator page, click

Modify in the Properties column of the Intelligence
Server.
2 Select the Automatically connect to Intelligence Server

when Web Server or Intelligence Server is restarted
option and click Save.
2005 MicroStrategy, Inc. Connecting MicroStrategy Web to the Intelligence Server 137
7 Deploying Your Project with MicroStrategy Web Installation and Configuration Guide
138 Connecting MicroStrategy Web to the Intelligence Server 2005 MicroStrategy, Inc.
8
8. CONFIGURING AND DEPLOYING
MICROSTRATEGY WEB
UNIVERSAL
Introduction
This chapter provides information on how to deploy and

configure MicroStrategy Web Universal in a UNIX/Linux
environment with various Web and application servers.
Web application servers are not MicroStrategy

products, so detailed steps cannot be provided for
every combination of application server and operating
system. This chapter supplies instructions for a few of
the most common combinations. The procedures for
different operating systems are similar, but please
refer to the vendor-provided user information for
details.
Deploying with WebLogic and Apache (Solaris)
Deploying with WebSphere 5.x and IBM HTTP Server

(AIX)
Deploying with Sun ONE (iPlanet) 8.0

8 Configuring and Deploying MicroStrategy Web Universal Installation and Configuration Guide
Using the MicroStrategy Web Administrator Console
Deploying with WebLogic and Apache

This section provides information used to deploy and
configure MicroStrategy Web Universal on the Sun Solaris 8
operating system, using Apache as the Web server and
WebLogic Server as the application server. It provides
information for WebLogic 7.x and 8.x.
This section includes the following information:
WebLogic paths and folder locations: Default folder

structure for each version of WebLogic.
Preconfiguration information: Configuration that must

occur before you begin deploying MicroStrategy Web
Universal.
Deploying MicroStrategy Web Universal: Instructions for

deploying the application.
Re-deploy the application: Instructions for re-deploying

the application.
Performance-based setup information: Optional
configuration settings to increase the applications
performance.
The additional configuration steps are not required

for MicroStrategy Web Universal to run, but these
settings can increase its performance. Review the
performance-based setup information prior to
deploying the system to see if these changes are of
interest to you.
140 Deploying with WebLogic and Apache 2005 MicroStrategy, Inc.

Installation and Configuration Guide Configuring and Deploying MicroStrategy Web Universal 8
WebLogic paths and folder locations

This section presents the default folder structure for each
version of WebLogic, and provides the variable used
throughout the rest of this chapter to represent the WebLogic
mydomain folder path.
Each version of WebLogic is installed with a different default

path to the WebLogic mydomain folder. When deploying
MicroStrategy Web Universal, you must make some changes
within the WebLogic folders. Thus, it is important to
understand the WebLogic folder structure for the version of
WebLogic you are using. The following paths reflect the
default folder structure for each WebLogic version:
WebLogic 7.x:
<WEBLOGIC_HOME>/user_projects/mydomain/
WebLogic 8.x:
<WEBLOGIC_HOME>/user_projects/domains/
mydomain/
Note the following:

<WEBLOGIC_HOME> is the WebLogic Server home
path.
The folder structures are configurable and your

organization may have changed the default names or
path.
Throughout this chapter, the WebLogic mydomain folder is

referred to as <WEBLOGIC_MYDOMAIN_FOLDER>. This
variable refers to the WebLogic mydomain folder in whatever
location it resides on your system. The location of this
variable is based on the version of WebLogic and whether
your organization has changed the versions default name or
path.
2005 MicroStrategy, Inc. Deploying with WebLogic and Apache 141

Preconfiguration information
This section provides the preconfiguration information
necessary to deploy MicroStrategy Web Universal on your
machine. This includes the following sections:
Locating the WAR file
Configuring the web.xml file
Setting up Apache Web server to proxy requests to

WebLogic
This section uses the configuration outlined in the following

table. While your setup may vary slightly, for example, you
may have different versions of these applications, the overall
process remains the same.
Operating system Sun Solaris 8
Web server Apache 1.3x, Apache 2.0.x
Application server WebLogic 7.x, WebLogic 8.x
JRE Sun JRE 1.3.1, Sun JRE 1.4.1
Note the following:

WebLogic 7.x uses Sun JDK 1.3.x whereas WebLogic
8.x uses Sun JDK 1.4.x.
For information on the version numbers supported or
certified by MicroStrategy, see the MicroStrategy
Readme file.
For information on installing these products, see

http://edocs.bea.com/
Before you start the deployment process, locate the

machine name and IP address.

The MicroStrategy Web Universal application is packaged

within a single file, called a WAR (Web ARchive) file,
following J2EE specifications. You must deploy the WAR file
to run the application in your application server
environment.
The WAR file is placed in the folder you specified when

installing MicroStrategy Web Universal. Copy the WAR file to
the <WEBLOGIC_MYDOMAIN_FOLDER>. See WebLogic paths
and folder locations, page 141 for information on the default
folder structure.
Tothatdeploy the WAR file, you must follow a set of steps

are specific to the application server you are
using. For more details, see the application server
vendor documentation or follow the instructions
within this guide. You should also follow any relevant
preconfiguration instructions within this chapter.
After deploying the MicroStrategy.war file, you can view

the WEB-INF folder, which contains a sub folder named log.
The log folder retains all the log files, except for the
ncsportal.log files. They are created in the Application
server root folder. For more information on the directory
structure after deploying the WAR file, see Directory structure
after deploying the WAR file, page 84 in Chapter 8,
Configuring the web.xml file
This procedure is required if you deploy MicroStrategy

Web Universal as a duplicate WAR file on WebLogic.
It is not necessary if you deploy the application as an
exploded directory.
By default, the paths of the configuration and log files are

saved as relative paths in the web.xml file. Before deploying
MicroStrategy Web Universal, you may need to modify these
paths to absolute paths.
A sample of modified web.xml file is available for your

reference; see Appendix F, Example of modified web.xml file.

To configure the web.xml file
1 Open the web.xml file located in the /WEB-INF

directory.
The web.xml file is inside the

MicroStrategy.war file so you must expand or
unzip that WAR file first. For details on expanding
or unzipping the file, see Deploying MicroStrategy
Web Universal, page 146.
2 The following table lists the parameters to be modified in

the web.xml file. For each parameter, replace the string
listed in the Old Value column with the string in the New
Value column. Change the parameter value from relative
to an absolute path pointing to a physical folder in your
machine. However, set the values for pageConfig.xml
and styleCatalog.xml parameters to be relative.
For example, if the directory where you store the

MicroStrategy Web Universal configuration files is
<WEBLOGIC_HOME>/NewFolder
where <WEBLOGIC_HOME> is the path to the WebLogic
Server, change the
serverConfigFilesDefaultLocation parameter
value to
<param-value>ABSOLUTE:<WEBLOGIC_HOME>/
NewFolder/ </param-value>
If you are running WebLogic Server in Windows,

make sure that you specify only forward slashes in
the absolute path. For example, <par
am-value>ABSOLUTE:C:/MyFolder
</param-value> is a valid path, but
<param-value>ABSOLUTE:C:\MyFolder</pa
ram-value> is not valid.

Parameter Old Value New Value
styleCatalogFile styleCatalog.xml /WEB-INF/xml/styleCatalog.xml

configFile pageConfig.xml /WEB-INF/xml/pageConfig.xml
serverConfigFilesDefaul <param-value>/WEB-INF/xml/ <param-value>ABSOLUTE:<WEBLOG

tLocation </param-value> IC_HOME>/NewFolder/
</param-value>
serverLogFilesDefaultL <param-value>/WEB-INF/log/ <param-value>ABSOLUTE:<WEBLOG

ocation </param-value> IC_HOME>/NewFolder/log/
</param-value>
3 Save the web.xml file and compress the WAR file.
Ifwasyoualready
modify the web.xml file for an application that
deployed, you must re-deploy the
application for the changes to take effect. For details,
see Re-deploy the application, page 157.
Setting up Apache Web server to proxy requests

to WebLogic
You can have the Apache Web server and WebLogic Server
running independently on the same machine, but to
configure Apache to proxy the desired requests to the
WebLogic Server, you must install a plug-in provided by
WebLogic. Complete the instructions at the following URLs
to install and configure the plug-in.
For WebLogic 7.x, the URL is
http://e-docs.bea.com/wls/docs70/plugins/
apache.html
Install the plug-in with the WebLogic installation in the

following location:
<WEBLOGIC_HOME>/Server/lib/solaris/
mod_wl_ssl.so

Server.

For WebLogic 8.x, the URL is
http://e-docs.bea.com/wls/docs81/plugins/
apache.html
Install the plug-in with the WebLogic installation in the

following location:
<WEBLOGIC_HOME>/Server/lib/solaris/
mod_wl_ssl.so

Server.
Tocanincrease the performance of Web Universal, you

complete additional setup configurations before
the deployment. For more information, see
Performance-based setup information, page 158.
Deploying MicroStrategy Web Universal

When your machine has been configured with the necessary
settings, you can deploy MicroStrategy Web Universal with
Apache and WebLogic. This involves the following steps:
1 Deploying automatically (development mode).
- or -
Deploying manually (production mode).
2 Accessing the MicroStrategy Web Administrator page.
3 Launching the project.
The Performance-based setup information section

provides information on additional settings to increase
application performance. These additional settings are
not required but can increase the performance of Web
Universal. Review this information prior to
deployment to see if these options are of interest to
you.

You can deploy MicroStrategy Web Universal using one of the

following deployment methods:
The automatic deployment feature is the easiest and

fastest way. See Deploying automatically (development
mode), page 147. Choose the development mode in the
/<WEBLOGIC_MYDOMAIN_FOLDER>/
startWebLogic.sh file, within the WebLogic Server
folder structure.
The manual deployment feature can be used for

environments where the server is running in production
mode and the automatic deployment is turned OFF. For
more information, see Deploying manually (production
mode), page 150.
Deploying automatically (development mode)
When automatic deployment is set to ON, as soon as you

place a WAR file in the
/<WEBLOGIC_MYDOMAIN_FOLDER>/applications folder,
the application is automatically deployed.
With this method you can deploy from either of the following:
a duplicate WAR file
an exploded directory where all the files contained in the

WAR file were extracted
To automatically deploy MicroStrategy Web Universal from a

duplicate WAR file
1 Locate the MicroStrategy.war file in the Web

Universal Deployment Directory you specified during
installation. For more information, see Installation
procedures on UNIX or Linux, page 72 in Chapter 4,
Installing MicroStrategy on UNIX and Linux.
2 Rename the WAR file to a name you can easily identify

and remember. This name is the context_name used in
the uniform resource locator (URL) to access the file. This
step is optional.

Ifremember
you do not change the name of the file,
to replace context_name with
MicroStrategy when accessing the application
from the URL.
3 Unzip the WAR file using the following command:

#jar -xvf MicroStrategy.war
4 Configure the web.xml file. For information on
configuration, see Configuring the web.xml file, page 143.
Ifmake
you are running WebLogic Server in Windows,
sure that you specify only forward slashes in
the absolute path. For example, <par
<param-value>ABSOLUTE:C:\MyFolder</pa
ram-value> is not valid.
5 Zip the WAR file with the following command:

#jar -cvf MicroStrategy.war *
6 Transfer the WAR file to the following application
directory:
/<WEBLOGIC_MYDOMAIN_FOLDER>/applications
The application is automatically deployed. To add and

connect to an Intelligence Server, see Accessing the
MicroStrategy Web Administrator page, page 174.
ToUniversal,
increase the performance of MicroStrategy Web
you can configure additional settings after
deployment. For more information, see
Next, access the MicroStrategy Web Administrator page to

finish configuring Web Universal.

To deploy MicroStrategy Web Universal from the exploded

directory
The WAR file must be uncompressed by the same

Solaris user who started the application.
1 Locate the MicroStrategy.war file. It is located in the

Web Universal Deployment Directory you specified
during installation. For more information, see
Installation procedures on UNIX or Linux, page 72.
2 Create the following new folder:

/home/username/context_folder
where username is your account name used to access
the Web server machine, and context_folder is the
name of the new folder.
You can create the new folder anywhere except in

the following location:
3 Copy the WAR file to the new folder.
4 To explode the WAR file inside the folder you created, run
the following command:
# jar -xvf MicroStrategy.war
5 Delete the MicroStrategy.war file by running this

command:
# rm MicroStrategy.war
6 Move the folder to the applications folder with the

following commands:
# cd..
# mv context_folder
The application is automatically deployed. To add and

connect to an Intelligence Server, see Accessing the

ToUniversal,
Deploying manually (production mode)
With manual deployment you can deploy MicroStrategy Web

Universal from either of the following:
a duplicate WAR file
an exploded directory where all the files contained in the

WAR file were extracted
Perform the deployment in the

directory.
To manually deploy MicroStrategy Web Universal from a

duplicate WAR file

2 Unzip the WAR file by running the following command:

3 Configure the web.xml file. For more information, see
Configuring the web.xml file, page 143.
Ifsureyouthat
are running WebLogic Server in Windows, make
you specify only forward slashes in the
absolute path. For example, <par
<param-value>ABSOLUTE:C:\MyFolder</param
-value> is not valid.

4 Zip the WAR file by running the following command:

5 Transfer the file to the
directory.
6 Open the WebLogic Server Administration Console (WLS

Admin Console) by typing the following address:
http://IP address:7001/console/
where IP address is the IP address of the machine.
7 Type a valid user ID and password at the prompt.
8 To complete this operation, see Configure from the WLS

Admin Console, page 152.
To manually deploy MicroStrategy Web Universal from the

exploded directory

2 Create a folder in the

directory and transfer the WAR file to this directory.
3 Unzip the WAR file using the following command:
4 Open the WLS Admin Console by accessing the following

address:
http://IP address:7001/console/
5 Type a valid user ID and password at the prompt. The

user ID and password are the ones you specified when
installing the WebLogic Server on your machine.

6 To complete this operation, see Configure from the WLS

Admin Console.
Configure from the WLS Admin Console
To configure from the WLS admin console, refer to the

appropriate procedure below depending on your version of
WebLogic:
To configure from the WLS Admin Console with
WebLogic 7.x, page 152
To configure from the WLS Admin Console with

WebLogic 8.x, page 153
To configure from the WLS Admin Console with WebLogic 7.x
1 Select mydomain, point to Deployments, and then

choose Web Applications. The Web Application table
opens.
2 Select Configure a New Web Application.
3 Locate and select the WAR file to configure and deploy. If

you are deploying from the exploded directory, select the
root of the exploded directory.
4 Select the server on which you want to deploy the

application. From the Available list of servers box, select
myserver and click the > arrow to move it to the Chosen
Servers box. Click Apply.
5 Type the name of the application you want to create. This

name is used in the URL to access the MicroStrategy Web
Administrator page.
6 Click Configure and Deploy, then wait for the

application to activate.
You have completed the steps required to deploy

To launch MicroStrategy Web Administrator and to configure

MicroStrategy Intelligence Server, see Accessing the

ToUniversal,
you can complete additional setup
configurations that occur after the deployment. For
more information, see Performance-based setup
information, page 158.
To configure from the WLS Admin Console with WebLogic 8.x

choose Web Application Modules. The Web Application
table opens.
2 Select Deploy a New Web Application Module.
3 Locate and select the WAR file to configure and deploy. If

you are deploying from the exploded directory, select the
root of the exploded directory.
4 Click the Target Module button.
5 Select the server on which you want to deploy the

application and click Continue.
6 Select how you want the source files to be made accessible

and type the name for the new Web Application module.
This name is used in the URL to access the MicroStrategy
Web Administrator page.
7 Click Deploy, then wait for the application to activate.
You have completed the steps required to deploy

To launch MicroStrategy Web Administrator and to configure

MicroStrategy Intelligence Server, see Accessing the
ToUniversal,

Configuring the MicroStrategy Web

Administrator page
Before starting MicroStrategy Web Universal, you must

configure the Web Administrator page; the mstrWebAdmin
servlet.
To access the MicroStrategy Web Administrator page
1 The address to launch MicroStrategy Web is different for

each deployment method. The following table lists the
URL to access MicroStrategy Web Administrator.
The servlet names are case-sensitive. Make sure to use

the correct case when typing the mstrWebAdmin
name. If the application server is enabled with
security, a dialog box related to the administrator
authentication opens.
Deployment Method Address
Automatic
deployment:
When deployed Access the Administrator page from a browser

from a duplicate using either of the following addresses:
WAR file. http://IPaddress:7001/context_na
me/servlet/mstrWebAdmin
http://IPaddress/context_name/se
rvlet/mstrWebAdmin
The first URL accesses the Web Administrator
through port 7001, which is the default port for
the application server. The second URL uses
the Apache Web server.
The context_name is the name you gave to
the WAR file and IPaddress is the IP address
of your machine.

When deployed Access the Administrator page from a browser

from an exploded at this address:
directory. http://IPaddress:7001/context_
folder/servlet/mstrWebAdmin
where context_folder is the name of the
folder where the application was exploded and
IPaddress is the IP address of your machine.
Manual deployment Access the Administrator page from a browser

using this address:
http://IPaddress:7001/name/servlet
/mstrWebAdmin
where IPaddress is the IP address of your
machine. Replace the name variable with the
name you specified in the Name field when
configuring from WLS Admin console, for
example, MyWebApp.
2 Type the same user ID and password that was used to

start the WebLogic Server on your machine.
In WebLogic, the deployment of Web Universal

automatically associates the WebLogic administrative
user with the MicroStrategy Web Universal administrator.
The WebLogic administrative user is the user who has
permissions to start the WebLogic Server on a given
machine. By default, when WebLogic is installed, the
administrative user is called system.
3 After you are authenticated, the MicroStrategy Web

Administrator page appears. Add and connect to an
Launch the Web Universal project, as described below.

Launching the project
The address to launch MicroStrategy Web Universal is

different for each deployment method. The table below lists
the URL you can use to access MicroStrategy Web Universal.
Automatic
deployment:
When deployed Access Web Universal from a browser using

from a duplicate either of the following addresses:
WAR file. http://IPaddress:7001/context_
name/servlet/mstrWeb
http://IPaddress/context_name/
servlet/mstrWeb
The first URL accesses the Web application
through port 7001, which is the default port for
the application server. The second URL goes
through the Apache Web server.
The context_name is the name you gave to
the WAR file and IPaddress is the IP address
of your machine.
When deployed Access Web Universal from a browser using

from an exploded the address:
directory. http://IPaddress:7001/
context_folder/servlet/mstrWeb
where the context_folder is the name of
the folder where the application was exploded
and IPaddress is the IP address of your
machine.
Manual deployment Access Web Universal from a browser using

the address:
http://IPaddress/name/servlet/mstr
Web
where IPaddress is the IP address of your
machine. Replace the name variable with the
name you specified in the Name field when
configuring from WLS Admin console, for
example, MyWebApp.

Re-deploy the application

If you have already deployed MicroStrategy Web Universal
with WebLogic and you change any parameters in the
web.xml file, you must re-deploy the application using the
WLS Admin Console. This allows the changes to take effect in
the deployed application.
To re-deploy the application from the WLS Admin console

address:
http://IP address:port/console/
3 In the left frame, select mydomain, point to

Deployments, and then choose Web Applications. The
Web Application table opens, which lists the
MicroStrategy Web Universal applications that have been
deployed.
4 Click the application to re-deploy, such as

MicroStrategy. The information for the application
appears.
5 Perform the appropriate steps for your version of

WebLogic, as follows:
In the right frame, select the Deploy tab.
Click Redeploy. The application is re-deployed.

Performance-based setup information

The performance of MicroStrategy Web Universal can be
increased by configuring it on various component levels.
These additional setup settings are not required, but if you
want to increase the performance of MicroStrategy Web
Universal, some changes must be done before or after the
deployment procedure. This section provides the following
configurations:
Setting the Java heap size
Precompiling JSP files
Disable/relax auto-reload parameters
Configuring Apache Web server to serve static files
The Java heap size for the WebLogic Server can be increased
by modifying the JAVA_OPTIONS variable in the
startWebLogic.sh script.
To increase the Java heap size
1 Open the startWebLogic.sh script from

/<WEBLOGIC_MYDOMAIN_FOLDER>/startWebLogic.
sh.
2 Look for the following line in the script:
JAVA_OPTIONS=-ms128m -mx128m
This line reflects a Java heap size of 128 MB. Set the
appropriate size. MicroStrategy recommends the initial
java heap size be set at a minimum of 500MB, assuming
the machine has enough memory space.
3 Stop and start the application server.

To avoid the time taken to load the Web pages in the

application server when you access it for the first time, you
must precompile the Java Server Pages (JSP) files before
deploying the application. Do this by setting the application
server to load all the pages in the application before
deployment. Thus, when you connect for the first time, the
pages are already loaded and the performance is better.
To precompile the JSP files
1 Open the weblogic.xml file located in the /WEB-INF

directory.
The weblogic.xml file is located in the

MicroStrategy.war file so you must expand or
unzip the WAR file first. You can expand the WAR
file by typing jar -xvf MicroStrategy.war.
2 In the jsp-descriptor section, set the

keepgenerated and the precompile parameters to
TRUE, as follows:
<jsp-descriptor>
:
:
<jsp-param>
<param-name>keepgenerated</param-name>
<param-value>TRUE</param-value>
</jsp-param>
<jsp-param>
<param-name>precompile</param-name>
<param-value>TRUE</param-value>
</jsp-param>
:
:
</jsp-descriptor>
3 Save the file and compress the WAR file again by typing

Disable/relax auto-reload parameters
To disable/relax auto-reload parameters, complete the

following:
Set the pageCheckSeconds parameter
Set the WebLogic Reload Period parameter
Each parameter is explained below.
Set the pageCheckSeconds parameter
The pageCheckSeconds parameter sets the interval, in

seconds, at which the WebLogic Server checks to see if JSP
files have changed and need recompiling. Dependencies are
also checked and recursively reloaded if changed.
You can set the following values:
Value Description
0 Pages are checked on every request.
-1 The page is not checked until the server is restarted. Any

classes used by the JSP page that live in the servlet
classpath are also reloaded.
n Interval (in seconds) in which WebLogic Server checks if

JSP files have changed. For example, if this is set to 1,
WebLogic checks the pages every second to see if the
JSP has changed and needs recompiling.
To set the pageCheckSeconds parameter

directory.

MicroStrategy.war file. You must first expand
or unzip the WAR file. You can expand the WAR
file by typing jar -xvf MicroStrategy.war.

2 In the jsp-descriptor section, set the

pageCheckSeconds parameter value. For example, the
following code sets the value to -1:
<jsp-descriptor>
:
:
<jsp-param>
<param-name>pageCheckSeconds
</param-name>
<param-value>-1</param-value>
</jsp-param>
:
:
</jsp-descriptor>
Set the WebLogic Reload Period parameter
In WebLogic, the Reload Period parameter sets how often

WebLogic checks whether a servlet has been modified. If the
servlet has been modified, WebLogic reloads it. As the Web
Universal servlets do not change after they have been
deployed, MicroStrategy recommends that you disable the
reload period by setting it to -1. A value of -1 means never
reload, and a value of 0 means always reload.
Use the appropriate procedure below, depending on whether

or not you are using WebLogic 8.x and have Web Universal
deployed as a duplicate WAR file.
To set the WebLogic Reload Period

address:
http://IP address:port/console/


choose Web Applications. The Web Application table
opens, which lists the MicroStrategy Web Universal
applications that have been deployed.
4 Click the application to configure, such as

MicroStrategy. The information for the application
appears.
5 Select the Configuration tab.
For WebLogic 7.x select the Files tab.
For WebLogic 8.x select the Descriptor tab.
6 Type the new value. The values are:
-1 to never reload
0 to always reload
Depending on your version of WebLogic, type the value in

the following location:
For WebLogic 7.x type the new value for the Reload
Period.
For WebLogic 8.x type the new value for Servlet
Reload Check Secs.
7 Click Apply.
8 For WebLogic 7.x only, stop and start the application

server.
To set the WebLogic Reload Period in WebLogic 8.x when

MicroStrategy Web Universal is deployed as a duplicate WAR
file

directory.

MicroStrategy.war file. You must expand or unzip
the WAR file first. You can expand the WAR file by
typing jar -xvf MicroStrategy.war.

2 In the container-descriptor section, set the

servlet-reload-check-secs parameter value. For
example, the following code sets the value to -1:
<container-descriptor>
<servlet-reload-check-secs>-1</servlet-rel
oad-check-secs>
</container-descriptor>
Configuring Apache Web server to serve static

files
Because Web servers are tuned to effectively serve static files,

the perceived performance of MicroStrategy Web Universal is
significantly enhanced if image, style sheet, and JavaScript
files are served via the Apache Web server, and the WebLogic
Server handles only the servlet requests. Do this by editing
two main parameters, Alias and MatchExpression, in the
Apache configuration file httpd.conf.
The Alias parameter is used to create a virtual directory

in the Apache Web server. The virtual directory is needed
to serve static files such as images, style sheets, and
JavaScript.
The MatchExpression parameter is used to configure
the Apache plug-in so that the WebLogic Server handles
only the servlet requests.

To configure the Apache Web server to serve static files
1 To change the Alias parameter, add the following lines

in the httpd.conf file:
Alias
/MSTRWeb/images/"/<WEBLOGIC_MYDOMAIN_
FOLDER>/applications/MSTRWeb/images/"
<Directory
"/<WEBLOGIC_MYDOMAIN_FOLDER>/
applications/MSTRWeb/images">
Options Indexes MultiViews
AllowOverride None
Order allow, deny
Allow from all
</Directory>
These code excerpts assume the application name

is MSTRWeb. See Deploying with WebLogic and
Apache for information on default folder structure.
2 Repeat the previous step for the JavaScript and style sheet
folders, replacing the word images in the previous code
with the folder name where the JavaScript and style sheet
files are located.
3 Change the MatchExpression parameter by typing

*/servlet/* in the MatchExpression parameter. For
example,
<IfModule mod_weblogic.c>
WebLogicHost 10.15.133.56
WebLogicPort 7001
MatchExpression */servlet/*
</IfModule>
4 Stop and start the Apache Web server using the
commands apachectl start and apachectl stop.

The Web server now serves image (GIF), style sheet (CSS),
JavaScript, and all other static files, thus reducing the load on
the application server and increasing the applications
performance.
Deploying with WebSphere 5.x and IBM HTTP

Server
configure MicroStrategy Web Universal on an AIX machine
using the WebSphere 5.x Server and the IBM HTTP Web
Server.
This section includes the following information:

occur before you begin deploying Web Universal.
Deploying MicroStrategy Web Universal: Instructions

for deploying the application.
settings to increase the applications performance.
These additional settings are not required, but can

increase the performance of Web Universal.
Review this information prior to deployment to see
if any of these options are of interest to you.
machine. Preconfiguration includes the following step:
This section also provides additional setup information for

the machine where the application server and Web server are
already installed.
2005 MicroStrategy, Inc. Deploying with WebSphere 5.x and IBM HTTP Server 165
This section uses the following configuration. While your

configuration may vary slightly, for example, you may have
different versions of these applications, the overall process
remains the same.
Operating system AIX 5.2

Repository None
Web server IBM HTTP Server 2.0.47
Application server IBM WebSphere V5.x
JRE IBM JRE 1.3.1
Note the following:

WebSphere 5.0.x uses IBM JDK 1.3.1 whereas
WebSphere 5.1.x uses IBM JDK 1.4.1.
For information on the version numbers certified and
supported by MicroStrategy, see the MicroStrategy
Readme file.

within a single file, called a WAR (Web ARchive) file,
following the J2EE specifications. You must deploy this file to
run the application in your application server environment.
To locate the WAR file
1 Locate the MicroStrategy.war file in the Web

Universal Deployment Directory you specified during
installation. For more information, see Installation
procedures on UNIX or Linux, page 72 in Chapter 4,
Installing MicroStrategy on UNIX and Linux.
2 Copy the WAR file to the

<WAS5_HOME>/installableApps directory, where
<WAS5_HOME> is the WebSphere 5.x application server
home path.
166 Deploying with WebSphere 5.x and IBM HTTP Server 2005 MicroStrategy, Inc.
The deployment process in this chapter assumes that

MicroStrategy.war file is stored in this directory.
After deploying MicroStrategy.war file, you can

view the WEB-INF folder, which contains a subfolder
named log. The log folder retains all the log files,
except for the ncsportal.log files. They are created
in the Application server root folder. For more
information on the directory structure after deploying
the WAR file, see Directory structure after deploying
the WAR file, page 84 in Chapter 4, Installing

Once your machine has the necessary settings configured,
you can deploy MicroStrategy Web Universal on the
WebSphere-AIX machine. Deployment involves the following
steps:
1 Launching the WebSphere Administrative Console
2 Starting the WebSphere default application server
3 Installing the Enterprise Application
4 Regenerating plugin-cfg.xml
5 Restarting the application server
6 Accessing the MicroStrategy Web Administrator page
7 Launching the project

provides information on additional settings to increase
application performance. These additional settings are
not required, but can increase the performance of Web
Universal. Review this information prior to
deployment to see if any of these options are of
interest to you.
Launching the WebSphere Administrative

Console
The WebSphere Administrative Console can be accessed only

if the WebSphere server is started on the machine.
To start the Websphere Application Server
1 Execute the startServer script as follows:
cd <WAS5_HOME>/bin
# ./startServer.sh <SERVER_NAME>
Typically, server1 is the default server name in

WebSphere 5.x.
2 Ensure that the Administrative Server has started

successfully. Execute the following commands:
cd <WAS5_HOME>/bin
# ./serverStatus.sh -all
To launch the WebSphere Administrative Console
In a Web browser, type the URL for the administrative

console.
The default port in WebSphere 5.0.x is 9090 for HTTP
and 9043 for HTTPS.
http://<hostname>:9090/admin
https://<hostname>:9043/admin
The default port in WebSphere 5.1.x is 7090 for HTTP and

7043 for HTTPS.
http://<hostname>:7090/admin
https://<hostname>:7043/admin
Starting the WebSphere default application

server
After you launch the WebSphere Administrative Console, you

can deploy MicroStrategy Web Universal by starting the
default application server.
This is applicable for Websphere Network Deployment

Edition or Websphere Enterprise Edition. For
Websphere Express or Websphere Base Editions,
there is no distinction between an administrative
server and a default server. The StartServer.sh
command starts the default application server
automatically.
To start the default application server
When the WebSphere Administrative Console opens, a tree

view is displayed.
1 Expand the Servers node, or click the link to expand the

view.
2 Click the Applications Servers link. A table listing the

application servers displays to the right of the navigation
tree. This area is the Workspace.
3 Select the box next to the application server to start.
4 Click Start above the table.
Installing the Enterprise Application
To install the Enterprise Application
1 Expand Applications, and then Enterprise Applications

to display a list of installed applications.
2 Click Install.
Preparing for the application installation
The following steps describe the settings that must be

specified for the installation.
To specify settings for the installation
1 Specify the path to the WAR file by selecting the Server

Path option and then typing in the full path for the
location of the MicroStrategy.war file. Type a suitable
name for ContextRoot, which is case-sensitive.
The URL to access MicroStrategy Web Universal

(http://machine-name/ContextRoot/serv
let/mstrWeb) contains ContextRoot, which
should be replaced by any name of your choice. For
example, you can use the default name of the WAR
file, which is MicroStrategy.
2 Click Next.
3 Select Do not override existing bindings.
4 For the Default virtual host name for Web modules, select
default host.
5 Click Next. The Provide options to perform the

installation page opens. In the screens that follow, you are
selecting settings that are used during the installation.
6 Click Next.
7 Make the following changes:
Select Enable pre-compile of JSPs.
Specify the value for the Directory to Install

Application as
${APP_INSTALL_ROOT}/DefaultNode
Specify an Application Name of your choice.
Enter the value of -1 as the Reload Interval.
8 Click Next. The Map virtual hosts for web modules page
opens.
9 Select Web Tier (default host) and click Next. The Map
modules to application servers page opens.
10 Select the application server and click Apply.
11 Select Web Tier (selected application server) and click

Next.
12 Map the admin role to the users or groups that will be

given the MicroStrategy Web Administrator privileges.
Role mapping enables the mapped users to access the
MicroStrategy Web Administrator page.
Security must be enabled for the WebSphere

Server for this feature to work.
13 Click Next. The Summary Page opens.
14 Review the summary and click Finish. A message appears

stating that the installation and precompilation of JSPs
was successful. Save the changes to the master repository.
Regenerating plugin-cfg.xml
To regenerate plugin-cfg.xml
1 Select Environment, and then click Update WebServer

Plugin.
2 Click OK, and then click Save to master configuration.
Restarting the application server
This section explains how to stop and start the application

server. Performing these steps stops and starts all the
applications running on the application server. To stop and
start only the application in which you are working, see To
start the Web module, page 173.
To restart the application server
The option to stop and start the application server

through the administrative console is available only
for the Websphere Network Deployment and
Websphere Enterprise Editions. To stop and start the
application server in Websphere Express and
Websphere Base editions, see below.
1 Expand the Servers node.
2 Click the Application Servers link. A table listing the

application servers and an icon indicating their status
appears:
red: stopped
green: started
3 Select the box next to the application server you want to

stop, and click Stop. The status icon changes from green
to red.
4 Select the application server you want to start and click

Start. The application server starts and the status icon
changes to green.
To stop and start the application server in Websphere

Express and Websphere Base editions, use the following
commands:
stopServer.sh server1 to stop the application
server
startServer.sh server1 to start the application

server.
Starting the Web module
This process starts only the Web application, rather than all
the applications running on the application server. To stop
and start all applications, see Restarting the application
server, above.
To start the Web module
1 Expand Applications.
2 Click the Enterprise Applications link. A list of installed

applications are displayed in the table to the right, along
with icons indicating their status:
red: stopped
green: started
3 Select the box next to the application to start and click

Start.
Controlling access to the MicroStrategy Web

Administrator page
The Web Administrator page (mstrWebAdmin servlet) is

accessible only to users with an administrator role. To create
the set of users and passwords that are authorized to access
the administrator page, you must create the necessary role
mapping between these users and the admin role for the
MicroStrategy Web Universal application. Refer to your IBM
documentation for more information, or contact
MicroStrategy Technical Support.
Accessing the MicroStrategy Web Administrator

page
Before you start MicroStrategy Web Universal, you must

configure the Web Administrator page, which is the
mstrWebAdmin servlet.
1 Access the mstrWebAdmin servlet by typing the following

URL in a Web browser:
http://IPAddress/context_root/servlet/
mstrWebAdmin
where context_root is the name you provided for the

Context root for Web Module box in the Preparing for
the application installation page. For example, the default
name of the WAR file, which is MicroStrategy. For
more information, refer to Preparing for the application
installation, page 170.
The servlet names are case-sensitive. Use the

correct case when typing the mstrWebAdmin
name. If the application server is enabled with
security, a dialog box related to the administrator
authentication opens.
2 Type the user ID and password assigned with the

administrator role.
3 After you are authenticated, the MicroStrategy Web

Administrator page opens. Use it to add and connect to an
Proceed to launch the MicroStrategy Web Universal project.

For more information, see Launching the project
immediately below.
After configuring the Web Administrator page, you must

follow the steps described in this section to launch your
project.
To launch the project
1 Start the Apache Web server by using the following

command:
# /usr/<HTTPServer>/bin/apachectl start
For example, if the IBM HTTP server is installed in the

default location /usr/IBMIHS, then use the following
command:
/usr/IBMIHS/bin/apachect1
2 In a Web browser, specify the following URL:
http://<machine-name>/<context_root>/
servlet/ mstrWeb
Alternatively, you can use the IP address of your machine

for remote access, as shown below:
http://<IPaddress>/<context_root>/servlet/
mstrWeb
provided
In these addresses, context_root is the name you
for the Context root for Web Module box
on Preparing for the application installation page. For
example, the default name of the WAR file, which is
MicroStrategy. For more information, refer to
Preparing for the application installation, page 170.
You can now access the MicroStrategy Web Universal

application.
Uninstalling MicroStrategy Web application
You can uninstall the MicroStrategy Web Universal

application through the WebSphere Administrative console.
To uninstall MicroStrategy Web application
1 Expand Applications.
2 Click Enterprise Applications. A list of installed

applications are displayed in the table to the right.
3 Select the desired MicroStrategy Web application.
4 Click Uninstall.
5 Save the configuration in the master repository.

increased by configuring it on various component levels.
These additional settings are not necessary, but can increase
the performance of MicroStrategy Web Universal. This
section explains the following changes:

Disable/relax auto-load parameters
Configuring the IBM HTTP Server to serve static files
You can increase the Java heap size for a given application
server by configuring the WebSphere Administrative
Console.
To increase the Java heap size
1 Access the Administrative Console.
2 Expand the Servers node.
3 Click the Application Servers link to view the list of

application servers.
4 Click the application server name, scroll to Additional

Properties and click Process Definition.
5 Click JVM Settings to set the Java heap size settings.

MicroStrategy recommends that you initially set the java
heap size to a minimum of 500MB, assuming the machine
has enough memory space.
6 Click Apply and save your changes.
7 Stop and start the application server.
To avoid the time taken to load the Web pages in the

application server when you access it for the first time, you
must precompile the Java Server Pages (JSP) files.
Precompilation can be done during deployment by selecting
the Enable pre-compile of JSPs setting. Otherwise, it can
be done after deploying the application.
To precompile the JSPs after deployment, set the application

server to load all the pages in the application. Then when you
connect for the first time, the pages are already loaded and
performance is improved.
Before you precompile the JSP files, make sure that:
The MicroStrategy Web Universal application is deployed

in the WebSphere environment.
You know the defined application name and the Web

Modules name. You can retrieve these names from the
Administrative Console. Locate the application name
under the Enterprise Applications node. Locate the Web
Module name by expanding the application and clicking
Web Modules. The default name is Web Tier.
To precompile the JSP files
1 Change the directory to <WAS_ROOT>/bin.
2 Run the following command:

./JspBatchCompiler.sh -enterpriseapp.name
ApplicationName -webmodule.name webModule
-cell.name cellName -node.name nodeName
-server.name serverName -keepgenerated
TRUE
If the administrative server is running in a security
enabled mode, you are prompted for the user ID and
password to connect to the Admin server.
username userID
password password
3 For each JSP file compiled without error, the following

message appears: Code generation successful.
Disable/relax auto-load parameters
Application servers typically reload certain resources more

often than necessary in a production environment. To disable
or relax such parameters to improve system performance, see
the application servers documentation.
Configuring the IBM HTTP Server to serve static

files
The IBM HTTP Server (Web server) is tuned to effectively

serve static files. As a result, perceived performance is greatly
enhanced if you configure the IBM HTTP Server to serve
image, style sheet, and JavaScript files. This also reduces the
load on the WebSphere Server so that it can handle only
dynamic files while IBM HTTP Server handles static files.
This requires that you do the following:
Configure the application server level to serve the Java

Server Pages (JSPs) and servlets, which are dynamic files
and handled by WebSphere.
Configure the Web server level to serve the images,

JavaScripts, and style sheets, which are static files and
handled by the IBM HTTP Server.
For more information, see the IBM WebSphere Application

Server V5.0 redbook covering System Management and
Configuration. This book discusses separating static content
from dynamic content.
Deploying with Sun ONE (iPlanet) 8.0

configure MicroStrategy Web Universal on a Sun ONE
application server (previously known as iPlanet) in a
UNIX/Linux environment. It includes the following
information:

Deploying MicroStrategy Web Universal: Instructions
for deploying.

settings to increase the applications performance.
2005 MicroStrategy, Inc. Deploying with Sun ONE (iPlanet) 8.0 179
These additional settings are not required, but can

increase the performance of Web Universal. Review
this information prior to deployment to see if any of
these options are of interest to you.
Undeploying MicroStrategy Web Universal using the

command line utility: Instructions for undeploying Web
Universal.
Throughout this guide iPlanet is referred to as Sun

ONE (iPlanet). Sun Microsystems purchased iPlanet
and renamed it Sun ONE Application Server.
necessary for deploying MicroStrategy Web Universal on
your machine. This includes:
It also provides additional setup information that needs to be

done on the machine on which the application server and
Web server are already installed.
UNIX/Linux environment
The following table shows the recommended machine

configuration to deploy MicroStrategy Web Universal with
Sun ONE (iPlanet) 8.0 in a UNIX/Linux environment:
Operating system Solaris 8

Web server iPlanet Web Server 6.x
Application server Sun ONE (iPlanet) Application Server 8.0
JRE SUN JRE 1.3.1

supported by MicroStrategy, see the MicroStrategy Readme
file.
180 Deploying with Sun ONE (iPlanet) 8.0 2005 MicroStrategy, Inc.
Windows environment
The following table shows the recommended machine

configuration for deploying MicroStrategy Web Universal in
a Windows environment:
Operating system Windows 2000/2003 Server
Web server iPlanet Web Server Enterprise Edition 6.0 SP5
Application server Sun ONE (iPlanet) Application Server 8.0
JRE and JDK Java 2 Platform, Standard Edition (J2SE) for

Windows
Make sure you install both the JRE and JDK for
running Sun ONE (iPlanet) on the Windows
environment.

supported by MicroStrategy, see the MicroStrategy Readme
file.

within a single file, called a WAR file (Web ARchive),
following the J2EE specifications. You must deploy this WAR
file to run the application in your application server
environment.
The Web Universal WAR file (MicroStrategy.war)is

located in the Web Universal deployment directory you
specified during installation. For more information, see
Installation procedure, page 50.
After deploying the MicroStrategy.war file, you

can view the WEB-INF/log folder. The log folder
retains all the log files except for the ncsportal.log
files, which are created in the application server root
folder. For more information on the directory
structure after deploying the WAR file, see Directory
structure after deploying the WAR file, page 84 in
Chapter 4, Installing MicroStrategy on UNIX and
Linux.

Once your machine has been configured, you can deploy
MicroStrategy Web Universal with Sun ONE (iPlanet) 8.0.

provides information on additional settings that can
increase application performance. These additional
settings are not required but can increase the
performance of Web Universal. Review this
information prior to deployment to see if any of these
settings are of interest to you.
The deployment involves the steps below, which are

explained in detail in the following sections:
1 Launching the Sun One Application Server Admin

Console
2 Deploying MicroStrategy Web Universal
4 Connecting to the project page
The administration and deployment tools in Sun ONE

(iPlanet) 8.0 have the same interface regardless of the
operating system on which they run. Therefore, the
deployment process is the same for all operating
systems, and is described below. There are some
minor changes in the Windows environment, which
are highlighted where necessary.
Launching the Sun One Application Server

Admin Console
This procedure describes the steps to launch the Sun One

Application Server.
To launch the Sun One Application Server Admin Console
1 Access the Sun One Application Server Admin Console by

typing the following URL:
http://<machine_name>:<admin_port>
where machine_name is the IP address or the name of

the machine where you installed Sun One, and
admin_port is the administration server port you
provided during the installation. By default, the
admin_port is 4848.
Inpointa Windows environment, from the Start menu,

to Programs, then Sun MicroSystems, then
Application Server 8.0, and then choose Admin
Console.
2 Enter the user name and password that you provided

during the installation.
Bypassword
default, the user name is admin. There is no
set by default. It is mandatory for you to
assign a password during the installation.
3 If the Administration Server is not running, an error

message appears. To start the Administration Server,
navigate to the following directory in the command
prompt:
<install-dir>/bin
and type the following command:
>asadmin start-domain domain1
where domain1 is the default domain server, or the

server you are currently working on.
Once the Administration Server starts, type the URL to

access Administration Server.
4 If the Administration Server is running, the following

messages appear:
>asadmin start-domain domain1
Starting Domain domain1, please wait.
Log redirected to
C:\Sun\AppServer8\domains\domain1\logs\ser
ver.log.
Domain domain1 is ready to receive client

requests. Additional services are being
started in background
After launching the Sun One Application Server Admin

Console, follow the steps below to deploy MicroStrategy Web
Universal as a WAR file.
To deploy MicroStrategy Web Universal as a WAR file
1 Access the Admin Console.
2 Enter the user name and password that you assigned

during the installation. By default, the user name is
admin.
3 Expand the Application Server tree view.
4 Expand Applications under the server you are using. By

default, the application server created is server1.
5 Select Web Applications and click Deploy. Deploy Web

Module opens in the right pane.
6 Type the full path or browse to the location where you

want to deploy the WAR file.
7 Select or clear the following check boxes according to your

requirements:
Redeploy if already exists
Run Verifier
Precompile JSPs
Itcheck
is recommended you select the Precompile JSPs
box to quickly load the Web pages in the
application server when you access it for the first
time.
Virtual Servers
8 Click OK.

Administrator page
For security purposes, you must only assign certain users the
authorization to access the MicroStrategy Web Administrator
page. To do this, map the Admin security role to only those
users for whom you want to grant permission to work in the
Sun ONE (iPlanet) 8.0 supports the following authentication

realms:
file
admin-realm
certificate
Asecurity
realm, also called a security policy domain or
domain, is a scope over which a common
security policy is defined and enforced by the security
administrator of the security service. For more
information, see the following resource:
http://docs.sun.com/db/prod/s1.asse#hic
In Sun One (iPlanet) 8.0, the file realm is selected by default.

To create users in the default realm, click File, then click
Manage Users to start creating users authorized to access
the MicroStrategy Web Administrator page.
Mapping security role
A descriptor file, sun-web.xml, enables Sun One to map the

existing users or groups to different security roles. This file is
located in the <webapplication_root_dir>/WEB-INF
folder. You can modify this file if you want to change the
default values for security roles.
The contents of this file are as follows:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE sun-web-app PUBLIC "-//Sun

Microsystems, Inc.//DTD Application Server
8.1 Servlet 2.4//EN"
"http://www.sun.com/software/appserver/dtds/s
un-web-app_2_4-1.dtd">
<sun-web-app
xmlns="http://java.sun.com/xml/ns/j2ee">
<context-root>/MicroStrategy</context-root>
<security-role-mapping>
<role-name>admin</role-name>
<principal-name>admin</principal-name>
</security-role-mapping>
</sun-web-app>
For mapping security roles to users and user groups, the

sun-web.xml file assumes the default values that are
provided during installation of Sun One 8.0 (iPlanet) and
deployment of MicroStrategy Web Universal. The following
are the values taken for context-root, role mapping, and the
user or principal user:
Context-root is set to MicroStrategy. This is the default

value for the context name when deploying MicroStrategy
Web Universal.
Role mapping is set to admin. This is the default value
specified in the web.xml file.
The user or principle name is also set to admin. This is the

default name assigned to the user when installing Sun
One 8.0 (iPlanet).
Ifrole,youormake changes to the default values of context,

user name while installing Sun One 8.0
(iPlanet) or deploying MicroStrategy Web Universal,
be sure that you update the sun-web.xml file before
you deploy MicroStrategy Web Universal.

page
When installing Sun One 8.0 (iPlanet), the user that you
create is saved in the admin realm. By default, the user name
is admin. You must enable this admin user to access the
To access the admin user, you must change the default realm,
file, to the admin realm.
1 Expand Configuration from the tree view, and select

Security. Security features are displayed on the right
pane.
2 Select the admin realm from the Default Realm

drop-down list.
3 Click Save to change the default realm.
4 Stop and restart the application server. For more

information, see Restarting the application server,
page 188.
Restarting the application server
You must stop and restart the application server instance to

apply changes. This is necessary after most changes to the
application server configuration, such as creating a user.
To restart the application server
After changing the application server configuration or

creating a user, a message Apply Changes Required is
displayed.
1 Click on the message Apply Changes Required.
If the server must be restarted, the Restart Required

message is displayed.
2 Click Restart.
You can also restart the application server by navigating

through the left menu, as follows:
1 Expand Application Server.
2 Select the server instance you are currently working on

and click the Stop Instance button displayed on the right
panel. The Sun Java System Application Server
Administration Console window opens.
3 Follow the instructions given in the Sun Java System

Application Server Administration Console window to
stop and restart the application server.
After restarting the application server, follow the procedure

below to connect to the project page.
Connecting to the project page
After restarting the application server, follow the steps

described here to connect to the project page.
To connect to the Project page
In a Web browser, type the following URL:
http://machine_name:HTTP_port/context
If you have used all the default variables, you can access
the following URLs:
http://localhost:80/MicroStrategy/
or
http://localhost:80/MicroStrategy/servlet/
mstrWeb
You are now ready to use MicroStrategy Web Universal.

increased by configuring various components. These
additional settings are not necessary, but they can improve
the performance of Web Universal. This section provides the
following configurations:
Undeploying MicroStrategy Web Universal using the

command line utility, after deployment
The maximum Java heap size, which handles all the Java
requests, is set to 512MB by default.
To set the Java heap size
1 Navigate to Application server.
2 Click JVM Settings and select JVM Options. You can

view the argument -Xmx512. This is the default value for
the maximum heap size.
3 Click Add JVM Options to include additional arguments

using -Xmx -Xms. For example, if you want to set the
maximum heap size to 1GB and minimum heap size to
512MB, then the argument you provide is -Xmx1024m
and -Xms512m.
Undeploying MicroStrategy Web Universal using

the command line utility
Sun recommends undeploying an application before

deploying a newer version. To undeploy an existing
MicroStrategy Web Universal application, use the following
command:
-undeploy -user admin-user -password password

-port4849 MicroStrategy
You are not required to provide the path to the WAR file.
When an application is deployed, Sun ONE (iPlanet) saves a
copy of the WAR file under the <install-dir>/ias/JARS
folder and looks for that copy when undeploying.
After the undeployment is finished, stop and restart the

application server for the changes to take effect.

This section provides information on how to deploy and
configure MicroStrategy Web Universal with Tomcat in a
Linux environment.

occur before you begin deploying Web Universal

deploying, including detailed steps
necessary to deploy MicroStrategy Web Universal with
Tomcat on your Windows machine.
Installing the JDK
Configuring the JDK
Installing Tomcat
Configuring Tomcat
This section uses the following setup. While your setup may
vary slightly, for example, you may have different versions of
these applications, the overall process remains the same.
Operating system RedHat Enterprise Linux AS Version 3 (64-bit)

update 3 -OR- Version 4 (64-bit)
Application server Tomcat 5.x
JDK SUN JDK 1.3.1 -OR- 1.4.2
2005 MicroStrategy, Inc. Deploying with Tomcat (Linux) 191

Installing the JDK
If you have not installed SUN JDK 1.3.1 or 1.4.2 yet,

download it from the
http://java.sun.com/j2se/<version>/
download.html website, where <version> is 1.3 or 1.4.
Be sure to install the JDK, not the JRE.
From the location in which to install the JDK, run the

following shell file:
j2sdk-<version>_08-linux-i586.bin
For example, to install version 1.4.2, type the following:
j2sdk-1_4_2_08-linux-i586.bin
Configuring the JDK
After you install the Sun JDK, you must configure it.
To configure the JDK
1 Open the /etc/profile file using a program that allows

you to edit the file.
2 Add the following line:

JAVA_HOME=/<path_name>/j2sdk<version>_08;
export JAVA_HOME
where <path_name> is the destination folder where you

installed the JDK and <version> is the version, such as
1.4.2, of JDK.
Ifxalan.jar
you are using Sun JDK 1.4.x, you must remove the
and xerces.jar files once you have
deployed MicroStrategy Web Universal because they
conflict with the JRE parser. The files are located by
default in the following location:
<tomcat_home>\webapps\MicroStrategy
<version>\WEB-INF\lib
192 Deploying with Tomcat (Linux) 2005 MicroStrategy, Inc.

Installing Tomcat
If you have not installed Tomcat 4.0 yet, download it from the
http://jakarta.apache.org/site/downloads/down
loads_tomcat-5.cgi website. For Linux, you need the
jakarta-tomcat-Y.M.D.zip file, for example,
jakarta-tomcat-4.1.29.zip.
From the location in which to install Tomcat, uncompress the

file with the following command:
untar jakarta-tomcat-Y.M.D.zip
Instructions for downloading and installing Tomcat are also

available on the Apache website.
Configuring Tomcat
After you install Tomcat, you must configure it by editing the

following files in the <Tomcat directory>/bin directory,
where <Tomcat directory> is the directory in which
Tomcat is installed:
startup.sh
shutdown.sh
setclasspath.sh
To edit the startup.sh file
1 Type the following command to edit the startup.sh

file:
dtpad startup.sh
2 Set the JAVA_HOME variable to the location where JDK is

installed.
3 Save and close the file.

To edit the shutdown.sh file
1 Type the following command to edit the shutdown.sh

file:
dtpad shutdown.sh
2 Set the JAVA_HOME variable to the location where JDK is

installed.
To edit the setclasspath.sh file
1 Type the following command to edit the

setclasspath.sh file:
dtpad setclasspath.sh
2 Set the CLASSPATH variable to the following:
<tomcat-directory>/server/lib
where <tomcat-directory> is the location where

Tomcat is installed.

following the J2EE specifications. You must deploy the WAR
file to run the application in your application server
environment.
The Web Universal WAR file (MicroStrategy.war) is

located in the path you specified when installing Web
Universal. The default location is
/<Install_directory>/MicroStrategy/Web JSP/.

To deploy the MicroStrategy.war file, you must follow a

set of steps that are specific to the application server you are
using. For more details, see your application server vendor
documentation or follow the instructions within this guide.
You should also follow any relevant preconfiguration
instructions within this chapter.

can view the WEB-INF folder, which contains a
subfolder named log. The log folder retains all the
log files except for the ncsportal.log files. They are
created in the Application server root folder. For more
the WAR file, page 84 in Chapter 8, Configuring and
Deploying MicroStrategy Web Universal.

After you have performed the configurations described
above, you can begin deploying MicroStrategy Web Universal
with Tomcat. This involves the following steps:
1 Deploying using Tomcat as a standalone Web container

Deploying using Tomcat as a standalone Web

container
To deploy MicroStrategy Web Universal using Tomcat as a

standalone Web container
1 Copy the MicroStrategy.war file to the

<tomcat-directory>\webapps directory.
2 In the <tomcat-directory>/bin, type startup.sh

to start Tomcat, which deploys automatically. There is
now a MicroStrategy folder under the
<tomcat-directory>\webapps directory.

Administrator page
The Web Administrator page, mstrWebAdmin servlet, is

accessible only to users with an admin role. To create a user
and password set that is authorized to access the
Administrator page, you must create the users and assign
them the admin role under the Tomcat user configuration
file.
To control access to the MicroStrategy Web Administrator

page
1 In the <tomcat-directory>/conf directory, open the

tomcat-users.xml file using a program that allows you
to edit the file.
2 Add the following tags and save the file:
<role rolename=admin/>
<user username=admin password=admin

roles=admin/>
<user username=system
password=goldengate roles=admin/>

password
You can specify any value in the user name and
fields. These are used to log in to the
MicroStrategy Web Administrator page. The
roles field must be admin.
3 Stop and restart Tomcat.
Now you can start Web Administrator to add and connect to

an Intelligence Server. To configure MicroStrategy Web
Administrator, see Accessing the MicroStrategy Web
Administrator page, page 197.

page
Before you begin this procedure, be sure you have

removed the xalan.jar and xerces.jar files, as
directed in the warning in the Configure the JDK
section, above.
To configure the MicroStrategy Web Administrator page
1 In a Web browser, access the MicroStrategy Web

Administrator page by specifying the following URL:
http://localhost:8080/MicroStrategy/
servlet/mstrWebAdmin
The servlet names are case-sensitive. Be sure to use the

correct case when typing the mstrWebAdmin name. If
the application server is enabled with security, a dialog
box related to the administrator authentication opens.
2 When prompted for a user name and password, use the

same values you specified in the tomcat-users.xml
file.
3 When you log in, the MicroStrategy Web Administrator

page is displayed.
4 Add and connect to an Intelligence Server.

Proceed to launch the Web Universal project. For more

information, see Launching the project, page 198.
In a Web browser, access MicroStrategy Web Universal using

the following URL:
http://localhost:8080/MicroStrategy/servlet/
mstrWeb
MicroStrategy Web Universal is ready to use.


This chapter provides information used to deploy and
configure MicroStrategy Web Universal on the Windows
2000 operating system with Apache as the Web server and
Oracle 10g as the application server.


deploying, including detailed steps.
machine. The following are covered in this section:
Modifying the XML parser used by the application server
This section uses the following setup. While your setup may
vary slightly, for example, you may have different versions of
these applications, the overall process remains the same.
Operating system Windows 2000
Application server Oracle 10g 9.0.x

Web server Apache
JRE SUN JRE 1.4.x
2005 MicroStrategy, Inc. Deploying with Oracle 10g 199


following the J2EE specifications, which you must deploy to
run the application in your application server environment.
The Web Universal WAR file (MicroStrategy.war) is

located in the path you specified when installing Web
Universal. The default location is C:\Program
Files\MicroStrategy\WebUniversal\ServerApps.
To deploy the MicroStrategy.war file, you must follow a

set of steps that are specific to the application server you are
using. For more details, see your application server vendor
documentation or follow the instructions within this guide.

can view the WEB-INF folder, which contains a
subfolder named log. The log folder retains all the
log files except for the ncsportal.log files. They are
created in the application server root folder. For more
the WAR file, page 84 in Chapter 4, Installing
Modifying the XML parser used by the

application server
The Web application class loader in Oracle 10g by default

looks for a class under the Oracle common library before the
individual Web application library. This creates some parsing
issues when using MicroStrategy Web Universal without
further configuration. To ensure that the Oracle application
server uses the XML/XSL parser distributed in MicroStrategy
Web Universal, follow the steps below.
200 Deploying with Oracle 10g 2005 MicroStrategy, Inc.

To use the correct XML parser in Oracle 10g
1 Unzip the MicroStrategy.war file and copy the

xerces.jar and xalan.jar files in the
MicroStrategy/WEB-INF/lib directory.
2 Paste the xerces.jar and xalan.jar files to the

following directory:
<ORACLE_10g_HOME>\jdk\jre\lib\ext
3 Keep a copy of the MicroStrategy.war file. You will

need it later when deploying Web Universal on the Oracle
application server.

After your machine is configured, you can start the
deployment of MicroStrategy Web Universal with Oracle 10g.
To deploy Web Universal, perform the following procedures:
1 Deploying using the Oracle Enterprise Manager
Deploying using the Oracle Enterprise Manager
You can access Oracle Enterprise Manager from the following

url:
http://machine_name:1810

To deploy with the Oracle Enterprise Manager
1 Start the Apache Web Server. From the Start menu, point
to OracleAS 10g - DEFAULT_HOME1, and then choose
Start
<application_server_name>.<machine_name>.<doma
in>.
2 To verify that the Apache Web Server has started, access

the Oracle Enterprise Manager, select HTTP Server and
click Start.
3 Select the OC4J instance where you want to deploy

4 Click Deploy WAR file. The Deploy Web Application page

opens.
You can deploy the WAR file or the EAR file. The
procedure for deploying the WAR file and EAR file
is the same.
5 For the Web Applications field, click Browse, then locate

and select the MicroStrategy.war file.
6 Type the Application name, such as MicroStrategy.
7 In the Map to URL box, type / before the name you

specified in Application name, such as
/MicroStrategy.
8 Click Deploy.

Administrator page
The Web Administrator page (mstrWebAdmin servlet) is

accessible only to users with an admin role. To control access
to it, map the admin security role to only those users for
whom you want to grant permission to work in the Web
Administrator page. In Oracle 10g, the security users and
groups are defined in the Oracle Enterprise Manager.

To map a security role in Oracle 10g
1 Access the Oracle Enterprise Manager.
2 Click the OC4J instance where you have deployed Web

Universal.
3 Click the application name, such as MicroStrategy. A

page displaying the Web Module opens.
4 Under Administration, click Security.
5 Click Add Group. Type the group name to which you

want to assign the admin role, for example Group1. Save
the group.
6 Click Add User. Type the user name and assign the
password. Make sure that the user is a member of the
group you created in the previous step. Save the user(s).
7 In the <ORACLE 10g_HOME>\j2ee\<OC4J instance

name>\application-deployments\MicroStrateg
y directory, edit the oracle
orion-application.xml file.
8 At the bottom of the file just before the </

orion-application> tag, add the following:
<security-role-mapping name=admin>
<group name=group1 />
</security-role-mapping>
The group name must match the name of the

group you created above. The
security-role-mapping name must be
admin.
9 Save the file.
10 Stop and restart the Apache server.
Now you can access MicroStrategy Web Administrator page

to add and connect to an Intelligence Server. For information
about this, see Accessing the MicroStrategy Web
Administrator page, page 197.


page
To configure the MicroStrategy Web Administrator page
1 In a Web browser, access the MicroStrategy Web

Administrator page by specifying the following URL:
http://IP_address/MicroStrategy/servlet/ms
trWebAdmin
where IP address is the IP address of the Oracle

machine. The servlet name is case-sensitive. Be sure to
use the correct case when typing the mstrWebAdmin
name. If the application server is enabled with Security, a
dialog box related to the administrator authentication
opens.
2 When prompted for a user name and password, specify

the values you used earlier when creating the user
mapped to the security role. For more information, refer
to the steps described in Controlling access to the
3 After you log in, the MicroStrategy Web Administrator

page appears.
4 Add and connect to an Intelligence Server.
You can now launch the MicroStrategy Web Universal

project. For details, see Launching the project, page 198.
In a Web browser, access MicroStrategy Web Universal using

this URL:
http://IP address/MicroStrategy/servlet/
mstrWeb
where IP address is the IP address of the Oracle machine.
The projects on the Intelligence Server appear, and you are

ready to use MicroStrategy Web Universal.

Using the MicroStrategy Web Administrator

Console
The MicroStrategy Web Administrator page allows you to
configure and manage MicroStrategy Web Universal
connections to MicroStrategy Intelligence Servers.
Specifically, you can do the following:
Connect or disconnect MicroStrategy Web Universal from

MicroStrategy Intelligence Servers
Modify MicroStrategy Intelligence Server property

settings
Configure MicroStrategy Web Universal to recognize

MicroStrategy Narrowcast Server and enable the
Scheduled E-mail and Send Now options
Configure MicroStrategy Web Universal logging and

statistics information, and view log files
Configure security options for MicroStrategy Web

Universal
After you deploy MicroStrategy Web Universal and log on to

the mstrWebAdmin servlet, the MicroStrategy Web
Administrator Page opens.
The four main options you use to configure MicroStrategy

Web Universal appear under the heading Web Server. You
can expand the links on the left to display sub-options. Under
Need help? is a link for the online help. The page displays the
following four settings:
Intelligence Servers page
Narrowcast Server Integration page
Diagnostics page
Security
2005 MicroStrategy, Inc. Using the MicroStrategy Web Administrator Console 205
Intelligence Servers page

The Intelligence Servers page is the default page you see
when you log in to the Administrator Page. It displays
information in the following sections:
Connected servers: Displays the list of connected

Intelligence Servers. Click Disconnect to disconnect a
server.
Unconnected servers: Displays the list of disconnected
Intelligence Servers. Click Connect to connect a server.
Add a server manually: Allows you to add and connect

to a new Intelligence Server.
Ifaccessed,
this is the first time the Administrator Page has been
the first two sections do not have any
Intelligence Servers listed.
When you disconnect a server from the connected list, or if

the server is stopped, all configuration information about the
server is saved and you can connect again. The Administrator
Page displays configuration settings for all connected and
disconnected servers.
You can perform the following tasks from the Intelligence

Servers page:
Add and connect to an Intelligence Server
Configure or modify server properties
Add and connect to an Intelligence Server
To work with the Administrator Page, you must add and

connect to an Intelligence Server.
To add and connect to an Intelligence Server
1 In the Add a server manually box, type the name of the

Intelligence Server to add.
206 Using the MicroStrategy Web Administrator Console 2005 MicroStrategy, Inc.
2 To configure advanced options for the specified

Intelligence Server connection, click Add. The Server
Properties page appears. Change settings as necessary.
For a description of the settings, see Configure or modify
server properties, page 207.
3 Click Connect. This saves any changes you may have

made and connects to the Intelligence Server. The server
is added and is displayed in the Connected Servers list.
Clicking Save only saves the connection settings you
specify in the page.
ToModify
change the server properties at a later time, click
in the Connected Servers section. You can also
click Disconnect to disconnect the server.
Configure or modify server properties
The Default Server Properties page and Server Properties

page allow you to configure advanced options for the
Intelligence Server being added. In both these pages you can
update the server properties such as connection mode, pool
size, login modes, and so on.
The difference between the Default Server Properties page

and Server Properties page is that, in the Server Properties
page the Project List, Server busy timeout, and Request
timeout options are not displayed. The Delete button, which
is used to delete the Intelligence Server and remove it from
the Connected or Unconnected servers list is also not
available.
These pages can be accessed using the following procedures:
To access the Default Server Properties page
Click Default properties, the Default Server Properties page

opens.
To access the Server Properties page
Do one of the following:
In the Connected Servers or Unconnected Servers list,

click Modify next to any of the servers. The Server
Properties page opens, providing additional details and
parameters for that server.
When you add an Intelligence Server for the first time,

you can click Add to open the Server properties page. This
page displays the following options:
Options Description
Connection
Properties:
Server name: This Displays the name of the MicroStrategy Intelligence

is not displayed in Server for which you are configuring the connection
the Server properties.
Properties page.
Connected Indicates whether the Intelligence Server is currently

connected.
Connect mode Determines whether an Intelligence Server connects

automatically or manually. The options for the connect
mode of Intelligence Server are:
Automatically connect to Intelligence Server
when Web Server or Intelligence Server is
restarted: Specifies that the Web server reconnects
to the Intelligence Server when the Web server is
started or restarted, or when the Intelligence Server
is restarted. By default, this check box is cleared.
MicroStrategy recommends using this setting for
production environments.
User manually connects Web to Intelligence
Server: Specifies that the administrator must actively
create the connection by clicking the Connect button
in the interface. By default, this check box is
selected.
Port Specifies the port number through which the Web

Server communicates with the Intelligence Server. If the
server is already connected, you cannot change this
option. The default is 0.
Options Description
Initial pool size Specifies the initial pool size for the server cluster if the
server is not connected. The pool is the number of
connections between the Web and the Intelligence
Server. This is defined at the Intelligence Server level,
not at the cluster level. You must define the pool size for
each Intelligence Server, which allows you to grant
more or fewer initial connections depending on the size
of the Intelligence Server machine. If the server is
already connected, you cannot change this option. The
default is 5.
Maximum pool size Specifies the maximum pool size for the server cluster if
the server is not connected. If the server is already
connected, you cannot change this option. The default
is 50.
Load balance Specifies the division of jobs between Intelligence

factor Servers in a cluster. You can specify the load balance
factor if the server is not connected. If the server is
already connected, you cannot change this option. The
default value is 1. This value can be increased for more
powerful servers in a cluster to provide an appropriate
balance. A larger load balance factor means the server
supports a greater load in the server cluster in which it
resides.
For example, if two servers make up a cluster, one
server with a balance factor of 3 and the other with a
balance factor of 2, and there are 20 logins, 12 logins
are supported by the first server and 8 by the second.
Server busy Length of time, in minutes, that a Web request waits for
timeout: This is not a connection from the connection pool, if the maximum
displayed in the number of connections are all busy. The default value is
Server Properties 10.
page.
Request timeout: Length of time, in minutes that Web Universal waits to

This is not receive a response from Intelligence Server. The default
displayed in the value is 40.
Server Properties
page.
Keep the Used when there is a firewall between the Web Server
connection alive and the Intelligence Server. This setting ensures that
between Web the firewall does not remove connections between the
Server and Web Server and Intelligence Server.
Intelligence Server
Options Description
Login Provides information about the login mode, whether that

mode is enabled or disabled, and which mode is the
default. The login modes include the following:
Standard (user name & password): default mode for
login
LDAP Authentication
Database Authentication
Guest
Windows Authentication: enabled only on
Windows-based Web Servers
By default all of the modes are enabled and the default
login mode is set to Standard.
Refer to Chapter 3, Deploying the System, in the
System Administration Guide for details about the
different modes. You can enable or disable these modes
and also make any of the modes the default login mode.
Project List: This is This allows you to specify whether the user must log in
not displayed in the before or after the projects are shown. You can choose
Server Properties the following options:
page. Show all the projects connected to the Web Server
before the user logs in. This option is selected by
default.
Log in, then show the projects accessible by the
supplied login.
If users log in after the projects are shown, then all
projects from all Intelligence Servers are presented to
the users. This is the default behavior.
If they log in before the projects are shown, then the
users should only see projects available to them.
Save Allows you to save the changes you made on this page.
Cancel Allows you to cancel the operation. It resets the page to

the previously saved settings.
Connect Allows you to make a connection to the Intelligence

Server. This button is displayed when you add a server
for the first time.
Delete: This is not Allows you to remove the Intelligence Server from the
displayed in the list. This button is displayed when the server is
Default Server disconnected.
Properties page.
Narrowcast Server Integration page

Use the Narrowcast Server link at the top of the
Administrator Page to access the Narrowcast Server
Integration page. This page allows you to configure
MicroStrategy Web Universal to enable the Scheduled E-mail
and Send Now features in MicroStrategy Web Universal.
The Scheduled E-mail feature allows users to have a report or

document sent to a specified e-mail address on a certain
schedule. These schedules are defined in MicroStrategy
Narrowcast Server and are separate from the schedules
maintained in MicroStrategy Intelligence Server. The Send
Now feature allows users to send a report or document
immediately to an e-mail address that they specify.
You must already have MicroStrategy Narrowcast

Server installed and configured before the Scheduled
E-mail and Send Now options work. For more
information, see the MicroStrategy Narrowcast
Server Application Designer Guide.
Diagnostics page
Diagnostics allows you to define what information is logged
by the Web and SDK, as well as where it is logged. It also
provides an interface to view these messages.
The diagnostics settings are stored in the

logger.properties file, which is saved by default
in the
CATALINA_HOME\webapps\MicroStrategy\
WEB-INF\log folder.
Click the Diagnostics link on the Administrator Page. The

Diagnostics page allows you to do the following:
Configure internal or custom log file settings
Configure how logs are displayed
Configure and view statistics
Configure internal or custom log file settings
Logs are records of all low-level activity, which can be

aggregated and used for troubleshooting a specific problem
or for server and system analysis. When you run the
MicroStrategy Web Universal application, the operations
performed by the user can generate errors, warnings, or
messages. This information can be stored and you can specify
how much of this content is written to the log file. For
example, to write only the errors generated by MicroStrategy
Web Universal, select Errors in the Diagnostics
Configuration page.
To open the Diagnostics Configuration page, click

Diagnostics on the Administrator Page. It has these options:
Options Description
Internal diagnostics This is the default option and is used to set the
setup type of information logged in the log file. The
settings defined here are written in the
logger.properties file.
Level Allows you to select the level at which the

information is written in the log file. You can
choose from the following levels:
OFF: This is the default option. Nothing is
written in the log file.
Errors: Errors generated by MicroStrategy
Web Universal are written in the log file.
Warnings: Errors and warnings generated by
MicroStrategy Web Universal are written in
the log file.
Messages: Messages, errors, and warnings
generated by MicroStrategy Web Universal
are written in the log file.
Log files directory Displays the default path where the log files are
saved; use / as the directory delimiter in the path.
You can also specify a different path. The log file
is generated in the specified path in the
MSTRmmddyyyy.log_num format. Naming of
the log file is handled by the
logger.properties file. For example, the first
log file created on 01/02/2003 appears as
MSTR01022003.log_1.
Options Description
Custom diagnostics A typical use of this setting is to load a

setup logger.properties file provided by Technical
Support. You can load those diagnostics settings
and send the output to Technical Support. When
Technical Support is finished, they can reset it to
your original settings. This allows a detailed level
of logging without requiring you to write the
logger.properties file.
Save Saves the settings.
Load default values Allows you to set the options to the default values
shipped with MicroStrategy Web Universal. This
option deletes settings that you have previously
configured.
Configure how logs are displayed
When you start working with MicroStrategy Web Universal,

the log file can record errors, warnings, or messages,
depending on how you Configure internal or custom log file
settings, page 212. This information can be difficult to
understand if you read it directly from the log file.
MicroStrategy Web Universal provides a way to view this
information in a Web page. This helps you troubleshoot and
diagnose application errors and the system.
You can view the log file information in the Administrator

Page by configuring the View Logs page. It displays the data
from the log file at a level of detail up to the level set in the
Diagnostics Configuration page. The View Logs page can be
customized to display warnings, messages, and errors at the
bottom of the page.
To view logs, you can filter the type of information to display

depending on the date period. The View Logs page requires
the following information:
Options Description
Display Provides the following choices:

Errors (default)
Warnings
Messages
Used to filter the displaying of logs on the screen.
Depending on what option you choose and on the
date setting, the Web page displays the information at
the bottom of the page. The logs that are displayed
depend on the level you choose in the Diagnostics
Configuration page. If you do not choose to record the
information, you are not able to see any logs on the
screen.
From The first date to display log file information for. By

default it displays the current date. Together the From
and To date settings specify the range of log
information to be displayed. If these settings are
equal, logs are viewed for that day only.
To The last date to display log file information for. By

default it displays the current date. Together the From
and To date settings specify the range of log
information to be displayed. If these settings are
equal, logs are viewed for that day only.
Refresh After you specify the log display options, click

Refresh to execute the new settings. The log file
information includes the following:
The time and date when the event log was created
The name of the user who logged in
The IP address of the user
The level of the information log
The class
The method related to this log
The entire message
Load Default Values Allows you to return to the default values in the Web
page.
The following conditions determine which logs are displayed:
The information recorded in the log file: If on a specific

date you turned the level OFF in the Diagnostics
Configuration page, the log file is empty for that date and
you do not see any information for it in the View Logs
page. Alternatively, it cannot display messages if you did
not select Messages to be recorded.
The levels you choose to display on the View Logs page: If

you select the check box for each of the levels, the page
displays all levels, assuming that all levels were saved in
the log file.
The date period: You can specify one or more days to

display using the From and To settings.
To configure how logs are displayed
1 In the Administrator Page, click View logs under the

Diagnostics section. A new View Logs Web page opens.
2 From the Display section, select the type of log, Error,

Messages, or Warning, to display in the log file.
3 Specify the date range to see the data available for that
period using the From and To options. This setting is
optional. If you do not specify the date range, the data for
the current date displays.
4 Click Refresh to execute your new settings.
Configure and view statistics
The statistics in the Administrator Page provide information

about the time taken by the Web Server and Intelligence
Server to complete an operation, how much data is received
and sent, the waiting time to receive some data from the
Intelligence Server, and so on. The Statistics section gives you
the option to turn the logging mode on or off, and to specify
whether the logs should be displayed on individual pages or
stored in a text file. You can enable this option to interpret
and analyze the system and server performance. The

information can be used as a source for analyzing statistical
information about MicroStrategy Web Universal. If multiple
users work on the same server, displaying statistics to each of
them is not recommended as it can have an impact on the
system and server performance.
Ifgrows
the statistics are being saved in a file, the file size
quickly. For this reason, this feature should not
be used under normal circumstances. It is useful only
when the system is not working properly and you want
to analyze the data for system tuning or
troubleshooting.
To access the Statistics page, select Statistics on the

Administrator Page, under Diagnostics.
The following table provides information about the options

available on the Statistics page.
Options Description
Mode Sets the show statistics mode to one of the

following options:
OFF: The statistics are not displayed on the
screen nor saved in a file. This is the default
setting.
Screen: The application statistics are
displayed in the lower left corner of all Web
pages.
File: The statistics are saved in the specified
file and you can open the file to see them.
Specify the absolute file path with / as a
directory delimiter in the Statistics File box.
Screen and File: The statistics are displayed
on the screen and written in the file you
specify. Specify the absolute file path with /
as a directory delimiter in the Statistics File
box.
Statistics File If you select File or File and Screen mode, you
must specify an absolute path in this box. Use /
as the directory delimiter in the path.
Save Allows you to save the settings.
Load Default Values Allows you to revert to the default settings.
For this page, the absolute path is the path where the
Web Server is installed.
When you set the mode to show statistics on the screen, the
following information is displayed on the left side of all the
Web pages:
Total Web Server + IServer processing time: Total

time, in milliseconds, taken by Web Server and
Intelligence Server to process a request.
Web Server processing time: Total time, in
milliseconds, taken by the Web Server to process the
request.
IServer processing time: Total time, in milliseconds,

taken by Intelligence Server to process the request.
IServer API time: Time, in milliseconds, spent by
Intelligence Server to process the XML API calls and to
execute and retrieve results. A percentage is displayed
after the unit and corresponds to the percent of time spent
processing the Intelligence Server API calls versus the
total time.
IServer polling time: Total time, in milliseconds, spent

waiting for results to come back from Intelligence Server
in milliseconds. MicroStrategy Web Universal is polling
Intelligence Server during that time. A percentage is
displayed after the unit and corresponds to the percent of
time spent polling Intelligence Server before it comes
back.
The polling interval is 110 milliseconds.

Number of Web API calls: Total number of API calls,
some to Intelligence Server, some made locally on the
Web Server, to access privileges, which are cached on the
Web server for each user.
Number of Web API polling calls: Number of calls made

to Intelligence Server for that request until the results are
ready.
Bytes sent and bytes received: Number of bytes
exchanged and received between the Web Server and
Intelligence Server throughout the request.
Security
MicroStrategy provides various security features to make
your application more secure and reliable. The Web
Administrators Security Web page allows you to enable or
disable various security options for users working with
To access the Security page, click Security on the

Administrator Page. The Security Web page allows you to
configure the following:
Encryption: This section determines whether or not to

encrypt the following information:
Traffic between the Web and IServer machines is

encrypted: The data transferred between
is not encrypted by default because it increases the
load on Intelligence Server. As a result, the application
can become slow. If the data is valuable and sensitive,
you can encrypt it by selecting this option.
Cookies security level: You can choose to:
Disable cookies: By default all cookies are disabled in

the application. This means that no settings are saved
in a session or in the metadata when using the
application. Select this option to make your
application highly secure.
Allow temporary cookies (deleted when the
session is closed): When you enable this option,
temporary information is saved within a session.
While you browse through the application and view
Web pages, information such as the last page visited,
filter or template definitions for execution, shared
report location, and so on is saved in the cookies. The
information is lost when the session is closed, or when
you close the browser.
Allow temporary and permanent cookies

(maintained across sessions): When you enable this
option, permanent information such as editor status
settings is saved in the metadata and can be used in
another session. This occurs if you close the browser
and open a new session. Enabling this option also sets
the application to save temporary information within a
session. This option is selected by default.
For more information about cookies, see the related appendix

in the MicroStrategy System Administration Guide.
You also have an option to enable or disable the following:

Store Intelligence Server information in temporary
cookies instead of on the Web Server: This option
specifies whether Intelligence Server session
information should be saved in cookies. It is not secure
to turn on this option in most cases as the Intelligence
Server information is sensitive. This option checks in
the cases when a cluster is set up and does not
automatically handle session replication. The session
replication is the distribution of the session
information on the client instead of on the Web server
so that the user can connect seamlessly to any of the
Intelligence Server machines.
When you enable this, temporary information such as

the Session ID of the Intelligence Server sessions is
saved.
Ifinformation
the Disable cookies option is selected, no
is saved in the cookies.
URL: You can enable or disable the following setting:
Session information is included in the URL: By

default, the application allows you to bookmark the
page you are in by adding it in your Favorites list. This
option specifies whether you want to bookmark the
page you are browsing and pass the information as
part of the URL. If you do not want to allow the user to
bookmark the page visited, turn off this option.
Even with the session information in the URL,

bookmarks only support basic pages that
correspond to saved objects or static links. This
means you cannot bookmark a report page after
you have applied manipulations.
User input filtering: You can enable or disable the

following setting:
Allow use of HTML in the print header and footer.

This setting will allow users to execute script in
the browser: This setting allows you to write HTML
code, including script, only in the print header and
footer dialog box. This allows you to include your own
images in the header and footer layout. If the check
box is cleared, the HTML text or script specified in the
print header and footer dialog box is encoded and not
interpreted, and it is printed as it appears in the dialog
box.
Login: You can enable or disable the following login

properties for MicroStrategy Web Universal users:
Allow automatic login if session is lost: This setting

allows Windows authentication users to automatically
reconnect to the MicroStrategy Web Universal
application if the session is lost. Others who are not
Windows authentication users must log in manually
again if the session is lost. By default this option is
selected.
Allow users to change expired password:

Passwords can be expired after a certain period of time
that you can set when creating a user in MicroStrategy
Desktop. A reminder is sent to the user to change the
password before it expires. If the password is not
changed within the specified time period, it is expired.
By default users cannot change the expired password.
However, if you enable this option, users have the
permission to change their expired password, except
those users who do not have privileges to change their
passwords. The change password privilege is assigned
to a user by the administrator in the User Editor of
MicroStrategy Desktop.
Save: Click to save the configuration settings in this page.
Cancel: Click to cancel the operation.
9
9. SETTING UP DOCUMENTS AND
HTML DOCUMENTS
Introduction
This chapter explains the setup required for the Intelligence

Server to execute HTML documents and Report Services
documents on UNIX or Linux platforms.

Before you start
Overview
Setup for creating and executing HTML documents
Setup for executing existing HTML documents
Setup for executing Report Services documents

9 Setting up Documents and HTML Documents Installation and Configuration Guide
Before you start

This chapter assumes the following:
You are familiar with UNIX or Linux.
You are familiar with MicroStrategy Desktop and

You are familiar with MicroStrategy HTML documents

and Report Services documents.
You have installed MicroStrategy Desktop as well as

Some of the steps described in this document may

require root access permissions.
222 Before you start 2005 MicroStrategy, Inc.

Installation and Configuration Guide Setting up Documents and HTML Documents 9
Overview
An HTML document is a container for formatting, displaying,
and distributing multiple reports on the same page, or at the
same time within a project. An HTML document object is the
standard container for creating dashboards and scorecards to
display a group of reports within the MicroStrategy platform.
HTML documents are created using MicroStrategy Desktop.

Before creating or executing HTML documents, you must
specify the HTML document directory using the Project
Configuration Editor in MicroStrategy Desktop. The HTML
document directory stores HTML templates that are required
by the MicroStrategy Intelligence Server for executing HTML
documents.
A MicroStrategy Report Services document contains objects

representing data coming from one or more reports, as well
as positioning and formatting information. It is used to
format data from multiple reports in a single display that can
be used for presentations. When you create a document, you
can specify the data that appears, control the layout,
formatting, grouping, and subtotaling of data and specify the
position of page breaks. In addition, you can insert pictures
and draw borders in the document.
InServices
this chapter, the term document signifies a Report
document.
For additional information on HTML documents, see the

HTML Documents chapter in the MicroStrategy Advanced
Reporting Guide.
For additional information on Report Services documents,

refer to the MicroStrategy Document Creation Guide.
2005 MicroStrategy, Inc. Overview 223

Setup for creating and executing HTML

documents
Using the Project Configuration Editor in MicroStrategy
Desktop, you must specify the location of the HTML
document directory as an absolute path. This document
directory can be on a local machine or on a remote machine.
Users require appropriate read and write permissions to
access this directory. When MicroStrategy Intelligence Server
executes HTML documents, it uses the same HTML files and
requires read permission to this document directory.
For the procedure below, the following assumptions are

made:
You have installed MicroStrategy Desktop as well as

The HTML document directory is stored on a UNIX or

Linux machine.
The location of the HTML document directory is

/machine-name/share/htmldocuments.
MicroStrategy Desktop users have at least read
permissions to the HTML document directory for
executing existing HTML documents. Write permissions
are required for MicroStrategy Desktop users to create
new HTML documents.
To set up HTML document creation
1 Share the HTML documents directory with MicroStrategy

Desktop installed on the Microsoft Windows platform. If
the HTML documents are not stored on the computer that
has Intelligence Server installed, then store them on a
computer that has Intelligence Server installed.
224 Setup for creating and executing HTML documents 2005 MicroStrategy, Inc.
2 Install Samba software on the UNIX computer that has

the HTML documents directory. With this software, the
HTML documents directory becomes accessible to
MicroStrategy Desktop installed on Microsoft Windows.
You can get the latest version of Samba at
http://www.samba.org.
3 Share the top-level directory that includes the HTML

documents directory as NFS shared directory, as well as
a Samba shared. For example, you must share
/machine-name/share.
4 From the Microsoft Windows computer that has

MicroStrategy Desktop installed, click Start, select Run,
and open the top-level shared documents directory. For
example, \\machine-name\share. This caches the
connection so that MicroStrategy Desktop users are not
prompted for authentication each time the shared
directory is accessed.
This must be performed every time you restart the

computer.
5 Using the Project Configuration Editor in MicroStrategy

Desktop, set the HTML document directory as an absolute
path, such as
\\machine-name\share\htmldocuments.
6 Perform one of the following, depending on whether the

HTML Document is on the same computer as the
Intelligence Server:
If the HTML documents directory is not on the same
computer as the Intelligence Server, place the HTML
documents directory on the computer that has the
Intelligence Server installed in it. Root privileges are
required for this. Type the command su and the root
password at the command prompt to log in as a
superuser, or log in as root. The command prompt
changes to the pound sign (#). Type the following:
mkdir / machine-name/share/htmldocuments
cd /
mount machine-name:/share /machine-name
2005 MicroStrategy, Inc. Setup for creating and executing HTML documents 225
If the HTML documents directory is on the same

computer as the Intelligence Server, you can store it in
the user space for root, or create a link such that it can
be accessed.
An example of the command follows:
# cd /
# mkdir <machine-name>
# cd <machine-name>
# mkdir share
# cd share
# mkdir myhtmldocuments
# ln -s /home/install/myhtmldocuments
myhtmldocuments
7 Create a directory named xsls under the HTML

document directory and copy the XSL files you require for
creating HTML documents to the xsls directory,
/machine-name/share/htmldocuments/xsls.
8 If you want to insert images into the HTML document,

create a directory named images under the HTML
document directory, and copy the images to the directory
/machine-name/share/htmldocuments/images.
9 Create your HTML documents in the HTML document

directory.
You are now ready to create and execute your HTML

documents.
226 Setup for creating and executing HTML documents 2005 MicroStrategy, Inc.
Setup for executing existing HTML documents

If you already have existing HTML documents, follow the
steps in this section to execute the HTML documents using
the MicroStrategy Intelligence Server.
For the procedure of setting up HTML document execution,

the following assumptions are made:
You have completed all the steps listed in the section,

Setup for creating and executing HTML documents,
page 224.
The location of the HTML document directory is

To set up HTML document execution
1 Copy the HTML file for any existing HTML document to

2 View the source code of each HTML file and copy the XSL
file used by each HTML document in an appropriate
directory under
For example, if the location of the XSL file in the source

code is xsl="\xsls\myxsl.xsl, then copy myxsl.xsl
to /machine-name/share/htmldocuments/xsls. If
the location of the XSL file in the source code is
xsl="\myxsl.xsl, then copy myxsl.xsl to
3 View the source code for the images used and follow the
instructions provided in the step above for XSLs.
You are now ready to execute your HTML documents.
2005 MicroStrategy, Inc. Setup for executing existing HTML documents 227
Setup for executing Report Services documents

A MicroStrategy Report Services document contains objects
representing data from one or more reports, and also
contains positioning and formatting information. A
MicroStrategy Report Services document is used to format
data from multiple reports. The formatted data can be used to
create presentations. A Report Services document can be
exported in a PDF format.
Follow the steps in this section to execute documents.
To set up document execution
1 In a UNIX console, browse to <INSTALL_PATH>, where

<INSTALL_PATH> is the directory you specified as the
install directory during installation. Browse to the folder
PDFGeneratorFiles.
2 To export documents to PDF, make sure that the

appropriate TrueType fonts (.ttf files) or the TrueType
Collection files (.ttc files) are in the PDFGeneratorFiles
folder.
For more information on documents, see the Document

Basics chapter in the MicroStrategy Document Creation
Guide.
228 Setup for executing Report Services documents 2005 MicroStrategy, Inc.
10
AUTOMATED INSTALLATION
10.
AND CONFIGURATION ON
WINDOWS
Introduction
This chapter explains the various possibilities for performing

fully automated and unattended installations within the
MicroStrategy platform. This includes customizations to the
installation and configuration routines available with the
product. It explains the different resources you can use to
deploy MicroStrategy products through various scenarios
including
deploying the MicroStrategy platform across the network
through the Microsoft System Management Server (SMS)
or its equivalent (for example, IBM Tivoli)
embedding the MicroStrategy platform within third party

custom applications and other installation routines
customizing the MicroStrategy installation to meet the

various environment-specific requirements for a given
site

10 Automated Installation and Configuration on Windows Installation and Configuration Guide
This chapter covers the following topics:
The different types of installations that can be performed

with MicroStrategy products.
How to perform a fully automated MicroStrategy

installation and configuration by modifying various
installation parameters in Windows ini-like response
files.
How to perform a partial, factory-like installation that can

be further completed by a customer. This particular set of
features enables any Original Equipment Manufacturer
(OEM) to easily embed the MicroStrategy platform within
another application.
How to customize certain aspects of the MicroStrategy

installation to meet various site-specific requirements for
multi-user environments, such as strict standards for
software deployment to user communities and so on.
230 2005 MicroStrategy, Inc.

Installation and Configuration Guide Automated Installation and Configuration on Windows 10
The methods of installations discussed in this chapter are
response.ini file installation
Silent installation
Response.ini file installation

The response.ini file installation allows you to automate
certain aspects of the installation by modifying a Windows
ini-like response file. This option is typically implemented by
OEM applications that embed MicroStrategy installations
within other products. It can also be implemented by IT
departments who want to have more control over Desktop
installations.
Silent installation
Silent installations do not present any graphical user
interface (GUI) and are typically implemented by IT
departments that perform package-based installations across
the network (SMS, for example). Although not as commonly
used as the response file installations, this scenario can also
be used for OEM installations.

Installation log file

Before you begin to learn about automated installation
options, it is important to know about the installation log file.
The setup program generates a log file in text format. This log
file contains records of all actions performed by the setup
program and by other executable files related to installation.
The installation log file can be particularly helpful if you
encounter errors during the installation process. For
example, the log can tell you if a registry key or path was not
added or if a critical file was not registered successfully. The
setup.exe file writes to this log file. The log file data
includes
update dates
machine specifications
user selections
list of files to be registered
list of files that do not require registration
list of registry entries
identification of files that fail during registration
installation activity such as performance counter loading

and DSN creation
reboot time file registration results
The default location for the install.log file is in the

Program Files\Common Files\MicroStrategy folder,
but both the location and the name can be changed. You can
specify the log file name and location in the following places:
command line, reading the parameter LogFile. For

example:
setup.exe --LogFile=C:\install.log
response file in [LogFile]. See Configuring a response.ini

file for installation, page 233 for more information.
232 Installation log file 2005 MicroStrategy, Inc.

Installing and configuring with a response.ini

file
The response.ini file can facilitate the installation and
setup of MicroStrategy products by allowing you to progress
through the installation and project creation processes with a
single keystroke. A response.ini file is an initialization file
that is used to send parameters or selections to the
InstallShield Wizard. This allows you to run it silently as all
the options are pre-selected in that file. The following types of
response.ini files are described:
installation
Configuration Wizard
Configuring a response.ini file for installation

The response.ini file for installation allows you to
automate certain aspects of the installation by modifying a
Windows ini-like response file. This option is typically
implemented by
OEM applications that embed MicroStrategy installations

within other products
IT departments who want to have more control over

desktop installations
The response.ini file specifies all the selections you want

to make during the installation in the InstallShield Wizard.
You can either run it with all the InstallShield Wizard options
that are pre-selected, or run it without having to use the
wizard at all.
The response.ini file should not be confused with

the setup.iss file, which is used by the InstallShield
to perform silent installation. When both
response.ini and setup.iss are included in the
setup, response.ini overrides setup.iss. For
details on the setup.iss file, see Silent installation,
page 265.
2005 MicroStrategy, Inc. Installing and configuring with a response.ini file 233
Creating a response.ini file
You can create a response.ini file in any text editor and

save the file as response.ini in the desired folder. You
must save the file as ANSI encoding. The following tables
describe the parameters and options for the all the sections,
such as Installer, Paths, and so on in the response.ini file.
It is followed by a sample response.ini file for your
reference.
The options are case sensitive, therefore they must

be entered as indicated in the tables below.
Installer
Options Description
[Installer] Section that begins the installation.
HideAllDialogs = TRUE or FALSE. Indicates whether the

installation uses all default values.
FALSE displays all the dialog boxes and
you must browse using the Next buttons.
The default is FALSE.
LogFile = Location where the install.log file is

generated. If left empty, it takes the
default location and file name of
Files\MicroStrategy\
install.log.
CreateShortcuts = TRUE or FALSE. TRUE creates a shortcut

called MicroStrategy in the Windows
Start menu. The default is TRUE.
PreventReboot = TRUE or FALSE. TRUE prevents the

machine from rebooting after installation
is done. Note the following conditions:
If both ForceReboot = TRUE and
PreventReboot = TRUE, then
PreventReboot applies first.
If both ForceReboot and
PreventReboot are FALSE and
HideDialog for [Finish] is set to
TRUE, then the machine reboots only
if it is required.
ForceReboot = TRUE or FALSE. TRUE reboots the

machine after the installation is done.
234 Installing and configuring with a response.ini file 2005 MicroStrategy, Inc.
Options Description
EnterpriseManagerOve TRUE or FALSE. If you select FALSE, the

rwrite = warehouse and metadata files are not
updated but the rest of the files for
Enterprise Manager are updated. This
prompt only impacts the files in the
Microsoft Access database. The default
is FALSE.
ShowConfigWizard = TRUE or FALSE. When using silent

install, set to FALSE to prevent the
Configuration Wizard from coming up
after reboot. The default is TRUE.
RunConfigWizard = TRUE or FALSE. Set this option to

specify whether to run the Configuration
Wizard. The default is FALSE.
ConfigWizardResponse Specify the name of the response file for

File = the Configuration Wizard; otherwise, it
takes the default name of
response.ini.
For more details on configuring the
response.ini file for the
Configuration Wizard, see Configuring a
response.ini file for the Configuration
Wizard, page 257.
BackupFiles = TRUE or FALSE. If you set the value to

TRUE, it creates a backup of the
following files:
*.pds
*.xsl
*.asp
*.css
*.js
*.sql
StopAllServices = TRUE or FALSE. Set this option to stop

all MicroStrategy services that are
running on the machine during
installation. The default is FALSE.
StopIIS = TRUE or FALSE. Set this option to stop

Internet Information Services (IIS) during
AnalyticsOverwrite = TRUE or FALSE. This option overwrites

the Analytics Modules from a previous
install. The default is FALSE.
Options Description
TutReportingOverwrit TRUE or FALSE. Set this option to

e = overwrite the Reporting Tutorial from a
previous installation. The default is
FALSE.
eTrainerForWebOverwr TRUE or FALSE. Set this option to

ite = overwrite the MicroStrategy eTrainer for
Web database from a previous
TutDeliveryOverwrite TRUE or FALSE. Set this option to

= overwrite the Delivery Tutorial from a
previous installation. The default is
FALSE.
CheckRenameOperation TRUE or FALSE. In some instances, as a

s = result of a previous installation or an
uninstall, certain files may be missing or
irreplaceable during installation.
Therefore, you are prompted to do one
of the following:
Reboot at the beginning of
installation to replace this file. It is
recommended that you select this
option.
Continue with the installation at the
risk of the software not functioning
properly.
If you enter FALSE, the prompt does not
display. The default is TRUE.
EnableTracing = TRUE or FALSE. Set this option to trace

the setup process in a log file that is
saved in the Temp folder. The log file
records errors that are encountered
during the installation. The default is
FALSE.
EnableASPNETServices TRUE or FALSE. Set this option to

= enable the ASP.NET Web Services
extensions that IIS Admin requires. The
default is FALSE.
EnableASPServices = TRUE or FALSE. Set this option to

enable the ASP Web Services
extensions that IIS Admin requires. The
default is FALSE.
ShowWelcomeScreen = TRUE or FALSE. Set to TRUE to display

the Welcome screen after reboot. The
Welcome screen is displayed only once
after reboot. The default is TRUE.
Paths
Options Description
[InitialPaths] Section for specifying the path for the

products that you select to install.
COMMONFILES = Location where the common files like

response.ini, install.log, and
so on will be installed. If left empty, it
takes the default location of
Files\MicroStrategy.
Desktop = Location where Desktop will be

installed. If left empty, it takes the
default location of C:\Program
Files\MicroStrategy\Desktop.
ObjectManager = Location where Object Manager will be

Administrator\Object Manager.
CommandManager = Location where Command Manager will

be installed. If left empty, it takes the
Administrator\Command
Manager.
EnterpriseManager = Location where Enterprise Manager will

Administrator\Enterprise
Manager.
Server = Location where the MicroStrategy

Intelligence Server will be installed. If
left empty, it takes the default location
of C:\Program Files\
MicroStrategy\Intelligence
Server.
Web = Location where MicroStrategy Web will

Files\MicroStrategy\Web ASPx.
WebUniversal = Location where MicroStrategy Web

Universal will be installed. If left empty,
it takes the default location of
C:\Program Files\
MicroStrategy\Web JSP.
Options Description
WebServices = Location where MicroStrategy Web

Services will be installed. If left empty, it
C:\Program Files\
MicroStrategy\Web Services.
SDK = Location where the SDK will be

Files\MicroStrategy\SDK.
Office = Location where MicroStrategy Office

will be installed. If left empty, it takes the
Files\MicroStrategy\Office.
TutorialReporting = Location where MicroStrategy Tutorial -

Reporting will be installed. If left empty,
it takes the default location of
C:\Program Files\
MicroStrategy\Tutorial
Reporting.
eTrainer= Location where eTrainer for Web will be

Files\Microstrategy\eTrainer.
AnalyticsModules = Location where the Analytics Modules

Analytics Modules.
NCSAdminDeliveryEngin Location where the Narrowcast Server

e = Delivery Engine will be installed. If left
empty, it takes the default location of
C:\Program Files\
MicroStrategy\Narrowcast
Server\Delivery Engine.
SubscriptionPortal = Location where the Subscription Portal

Files\MicroStrategy\Narrowcas
t Server\Subscription Portal.
TutorialDelivery = Location where MicroStrategy Tutorial -

Delivery will be installed. If left empty, it
C:\Program
Files\MicroStrategy\Narrowcas
t Server\Tutorial
Welcome dialog box
Options Description
[Welcome] Section for configuring the Welcome

dialog box.
HideDialog = TRUE or FALSE. True displays the

dialog box. The default is FALSE.
RemoveAll = TRUE or FALSE. This option is for the

uninstall process only. Setting it to TRUE
removes all MicroStrategy products
during the uninstall process. The default
is FALSE.
Customer Information dialog box
Options Description
[UserRegistration] Section for specifying the customer

information.
HideDialog = TRUE or FALSE. True displays the dialog

box. The default is FALSE.
UserName = Indicates the user name of the currently

logged user or a user who is already
registered. If no information is provided,
you cannot proceed to the next page.
CompanyName = The name of the company for which the

software is registered. The default is the
company name in the registry.
LicenseKey = Specify the license key for the software.

If you do not specify the license key, the
Setup Wizard will ask for it when it
reaches that step. By default it is blank
for a fresh install or displays the license
key from a previous install.
Setup Type dialog box
Options Description
[SetupType] Section for setting the appropriate dialog

boxes to display for Typical or Advanced
installation. This dialog box offers the
option to select the installation type.

Type = This determines whether the installation

is Typical or Advanced.
One of the following two parameters can
be entered:
typical
advanced
Typical or Advanced. If set to
typical, the installation paths specified
in the [InstallPaths] section are
used. If set to Advanced, you are
prompted to enter the path for each
product. For more information, refer to
GUI, page 43 in Chapter 2, Planning Your
Installation. The default is Advanced.
Choose Destination Location dialog box
Options Description
[SuiteTarget] Section specifying the name of the target

directory from where you can run the

TargetDirectory = Location of the root directory for the

Program Files. The default is set to
C:\Program Files\MicroStrategy.
Select Components dialog box
In the InstallShield Wizard, the Select Components dialog

box contains check boxes to select or clear for products to be
installed. The [ComponentSelection] options specify
whether you want the following products to be visible to the
user. In addition, you can set the default selection for each
product.
Options Description
[ComponentSelection] Equivalent to the Select Components

dialog box that you see during
installation. For the Visible option,
you can either enter TRUE to show a
product or FALSE to hide it. If you do
not specify a TRUE or FALSE value for
each product, TRUE is used for all
products. For the Select option, you
can enter TRUE to select the check box
next to a product. If you enter FALSE,
the check box next to the product is not
selected.

DesktopDesignerVisible MicroStrategy Desktop Designer

=
DestopAnalystVisible = MicroStrategy Desktop Analyst
ArchitectVisible = MicroStrategy Architect
ServerAdminVisible = MicroStrategy Server Administrator
ProjectBuilderVisible MicroStrategy Project Builder

=
CommandManagerVisible MicroStrategy Command Manager

=
EnterpriseManagerVisib MicroStrategy Enterprise Manager

le =
ObjectManagerVisible = MicroStrategy Object Manager

IServerVisible = MicroStrategy Intelligence Server
WebAnalystVisible = MicroStrategy Web Analyst
WebProfessionalVisible MicroStrategy Web Professional

=
WebReporterVisible = MicroStrategy Web Reporter
Options Description
WebUniversalAnalystVis MicroStrategy Web Universal Analyst

ible =
WebUniversalProfession MicroStrategy Web Universal

alVisible = Professional
WebUniversalReporterVi MicroStrategy Web Universal Reporter

sible =
WebServicesASPNETVisib MicroStrategy Web Services

le = (ASP.NET)
SDKVisible = MicroStrategy SDK
OfficeVisible = MicroStrategy Office
TutorialReportingVisib MicroStrategy Tutorial - Reporting

le =
eTrainer for MicroStrategy eTrainer for Web

WebVisible =
AnalyticsModulesVisibl MicroStrategy Analytics Modules

e =
NCSAdminVisible = MicroStrategy Narrowcast

Administrator
DeliveryEngineVisible MicroStrategy Delivery Engine

=
SubscriptionPortalVisi MicroStrategy Subscription Portal

ble =
TutorialDeliveryInstal MicroStrategy Tutorial - Delivery

lVisible = Installation
TutorialDeliveryConfig MicroStrategy Tutorial - Delivery

ureVisible = Configuration
JMSGatewayVisible = JMS Gateway
WebGatewayVisible = Web Gateway
During the installation process in the InstallShield Wizard,

the Select Components dialog box contains check boxes to
select or clear for products to be installed. You can either
specify TRUE to install a product or FALSE to uninstall it. If
you do not specify a TRUE or FALSE value for each product,
it always uses the most recent selection from a previous
install. If you specify TRUE, the product check box is selected.
The [ComponentSelection] options specify whether the
check box for each product will be selected or cleared.
Options Description
DesktopDesignerSelect = MicroStrategy Desktop Designer
DestopAnalystSelect = MicroStrategy Desktop Analyst
ServerAdminSelect = MicroStrategy Server Administrator
ArchitectSelect = MicroStrategy Architect
ProjectBuilderSelect = MicroStrategy Project Builder
ObjectManagerSelect = MicroStrategy Object Manager
CommandManagerSelect = MicroStrategy Command Manager
EnterpriseManagerSelect MicroStrategy Enterprise Manager

=
IServerSelect = MicroStrategy Intelligence Server
WebServerASPNETSelect = MicroStrategy Web Server
WebAnalystSelect = MicroStrategy Web Analyst
WebProfessionalSelect = MicroStrategy Web Professional
WebReporterSelect = MicroStrategy Web Reporter
WebUniversalServerASPNE MicroStrategy Web Universal Server

TSelect = (ASP.NET)
WebUniversalServerJSPSe MicroStrategy Web Universal Server

lect = (JSP)
WebUniversalAnalystSele MicroStrategy Web Universal Analyst

ct =
WebUniversalProfessiona MicroStrategy Web Universal

lSelect = Professional
WebUniversalReporterSel MicroStrategy Web Universal Reporter

ect =
WebServicesASPNETSelect MicroStrategy Web Services

= (ASP.NET)
SDKSelect = MicroStrategy SDK
Options Description
OfficeSelect = MicroStrategy Office
TutorialReportingSelect MicroStrategy Tutorial - Reporting

=
eTrainer for WebSelect MicroStrategy eTrainer for Web

=
AnalyticsModulesSelect= MicroStrategy Analytics Modules
NCSAdminSelect = MicroStrategy Narrowcast

Administrator
DeliveryEngineSelect = MicroStrategy Delivery Engine
SubscriptionPortalSelec MicroStrategy Subscription Portal

t =
TutorialDeliveryInstall MicroStrategy Tutorial - Delivery

Select = Installation
TutorialDeliveryConfigu MicroStrategy Tutorial - Delivery

reSelect = Configuration
JMSGatewaySelect = JMS Gateway
WebGatewaySelect = Web Gateway
MicroStrategy Web virtual directory
Options Description
[WebVirtualDirectory] Section that specifies the virtual

directory to be used for the
MicroStrategy Web application.

VirtualDirectory = Enter a name for the virtual directory.

The default is MicroStrategy8.
RemoveVD = YES or NO. This option is for the

uninstall only. Set this option to
remove an existing MicroStrategy
Web virtual directory from a previous
installation. The default is NO.
Subscription Portal virtual directory
Options Description
[PortalVirtualDirector Section that specifies the virtual

y] directory to be used for MicroStrategy
Subscription Portal.
HideDialog = TRUE or FALSE. The default is

FALSE.

The default is NarrowcastServer8.

from a previous installation. The
default is NO.
Web Services virtual directory
Options Description
[WebServicesDirectory] Section that specifies the virtual

directory to be used for MicroStrategy
Web Services.


The default is MicroStrategyWS.

from a previous installation. The
default is NO.
eTrainerForWeb virtual directory
Options Description
[eTrainerForWebVirtual Section that specifies the virtual

Directory] directory to be used for MicroStrategy
eTrainer.
HideDialog = TRUE or FALSE. Set this option to not

display the MicroStrategy eTrainer for
Web Virtual Directory Setting dialog
box, or the prompt for removal of the
virtual directory while MicroStrategy
eTrainer for Web is being uninstalled.

If left empty, it takes the value of
eTrainer.
RemoveVD = YES or NO. Set this option to specify

whether upon uninstallation the
MicroStrategy eTrainer for Web virtual
directory should be removed. The
default value is NO.
Program folder
Options Description
[ProgramFolder] Section specifying the Windows Start

name of the folder from where you can
run the MicroStrategy products. The
folder will be created under the default
Start\Programs\.

Name = Enter the name of the folder, for

example, MicroStrategy.
Intelligence Server service account
Options Description
[IServerServiceAccount Section specifying the Windows

] account for the MicroStrategy
Intelligence Server service. You have
two options:
bypass entering the account
information
enter the account information
SkipAccountSetting = TRUE or FALSE. Set TRUE to bypass

the service account setting in the
Setting dialog box. If you bypass it,
then the service runs with the local
system account that is installing the
products. The default is FALSE.
Domain = Enter the domain where the account is

located.
Login = Enter the user name of the account to

use.
Password = Enter the password for the account.
ServiceStartup = AUTO or MANUAL. Select to set the

Intelligence Server service startup to
be automatic or manual. The default is
AUTO.
Narrowcast Server service account
Options Description
[NarrowcastServiceAcco Section specifying the Windows

unt] account from which the MicroStrategy
Narrowcast Server service will run.

Options Description
SkipAccountSetting = TRUE or FALSE.

If you specify this value as FALSE, the
service account settings are not
skipped and the MicroStrategy
Narrowcast Server setting dialog box is
displayed. Specify the details of the
Windows account that the
services will use to log on and click
Next to proceed with the installation
process.
Domain = Enter the domain where the account is

located.
Login = Enter the user name of the account to

use.
Password = Enter the password for the account.
Web Universal URL setting
Options Description
[WebUDeployment] Section specifying the URL for


SkipDeploymentSetting TRUE or FALSE. TRUE skips the

= Deployment setting. The default is
FALSE.
DeploymentDirectory = Specify a location for MicroStrategy

Web Universal installation, for
example, C:\Program
Files\MicroStrategy\Web JSP.
Web Services URL setting
Options Description
[OfficeWebServicesURL] Section specifying the URL for

MicroStrategy Web Services.

Options Description
AllowBlankURL = TRUE or FALSE. Specify whether to

allow a blank URL. The installation
routine validates the provided URL. If
no URL is provided, the user is
informed that it has been left blank and
needs to be configured with the
MicroStrategy Office Configuration
Tool. If this is set to TRUE, the user
message is not displayed if the URL is
left blank. The default is FALSE.
URL = Enter a URL pointing to a valid

MicroStrategy Web Services
installation, for example,
http://localhost/Microstrate
gyWS/MSTRWS.asmx
MicroStrategy Office setting
Options Description
[MSOfficeLoadOptions] Section specifying the options that

determine if the MicroStrategy Office
toolbar is loaded in the installed
Microsoft Office applications.

ConfigureExcel = TRUE or FALSE. Specify to load the

MicroStrategy Office toolbar by default
when the Microsoft Excel application
runs. This applies only if Excel is
installed in the target machine. The
default is TRUE.
ConfigureWord = TRUE or FALSE. Specify to load the

when the Microsoft Word application
runs. This applies only if Word is
installed on the target machine. The
default is TRUE.
ConfigurePowerpoint = TRUE or FALSE. Specify to load the

when the Microsoft PowerPoint
application runs. This applies only if
PowerPoint is installed on the target
machine. The default is TRUE.
Intelligence Server definition setting
Options Description
[ServerDefinitionSetti Section specifying whether or not the

ng] MicroStrategy Intelligence Server will
use the server definition included with
the Tutorial.

OverwriteServerDefinit TRUE or FALSE. This option relates to

ion = the Tutorial. Set this option to overwrite
existing MicroStrategy Intelligence
Server definitions from a previous
install. The default is FALSE.
Tutorial reporting setting
Options Description
[TutorialReportingSett Section that specifies the DSN used to

ing] connect to the MicroStrategy Tutorial.

OverwriteDSN = TRUE or FALSE. Set this option to

overwrite an existing DSN with the
same name. The data source names
are as follows:
MicroStrategy_Tutorial_Meta
data
MicroStrategy_Tutorial_Data
Start Copying Files dialog box
Options Description
[Summary] Section that specifies the installation

summary in the Start Copying Files
dialog box.

InstallShield Wizard Complete dialog box
Options Description
[Finish] Section that specifies the InstallShield

Wizard Complete dialog box.

Example of a response.ini file

[Installer]
PropertiesFilesOverwrite=FALSE
EnableTracing=FALSE
HideAllDialogs=TRUE
ForceReboot=TRUE
PreventReboot=FALSE
CheckTCPIP=TRUE
CheckIIS=TRUE
CheckSP=TRUE
CreateShortcuts=TRUE
CheckRenameOperations=TRUE
AnalyticsOverwrite=FALSE
TutReportingOverwrite=FALSE
TutDeliveryOverwrite=FALSE
BackupFiles=FALSE
RunConfigWizard=FALSE
StopAllServices=TRUE
StopIIS=TRUE
EnableASPServices=TRUE
EnableASPNETServices=TRUE
eTrainerForWebOverwrite=FALSE
ShowWelcomeScreen=FALSE
ShowConfigWizard=FALSE
EnterpriseManagerOverwrite=FALSE
ConfigWizardResponseFile=Response.ini
RegistrySizeReq=512
LogFile=c:\Program Files\install.log
[Welcome]
HideDialog=TRUE
RemoveAll=FALSE
[UserRegistration]
HideDialog=TRUE
UserName=<user name here>
CompanyName=<Company name here>
LicenseKey=<Customer License Key here>
[SetupType]
HideDialog=TRUE
Type=TYPICAL
[SuiteTarget]
HideDialog=TRUE
TargetDirectory=C:\Program
Files\MicroStrategy
[ComponentSelection]
HideDialog=TRUE
### Visible Components ###

DesktopAnalystVisible=TRUE
DesktopDesignerVisible=TRUE
ArchitectVisible=TRUE
ProjectBuilderVisible=TRUE
ServerAdminVisible=TRUE
CommandManagerVisible=TRUE
EnterpriseManagerVisible=TRUE
ObjectManagerVisible=TRUE
IServerVisible=TRUE
WebReporterVisible=TRUE
WebAnalystVisible=TRUE
WebProfessionalVisible=FALSE
SDKVisible=TRUE
MDXAdapterVisible=TRUE
AnalyticsModulesVisible=TRUE
NCSAdminVisible=TRUE
DeliveryEngineVisible=TRUE
SubscriptionEngineVisible=FALSE
SubscriptionPortalVisible=TRUE
TransactorVisible=TRUE
TransactorServerComponentsVisible=TRUE
TransactorAdminVisible=TRUE
JMSGatewayVisible=FALSE
WebGatewayVisible=FALSE
TransactorDemoVisible=FALSE
TutorialReportingVisible=TRUE
TutorialDeliveryInstallVisible=TRUE
TutorialDeliveryConfigureVisible=TRUE
JDataConnectVisible=FALSE
RealAudioPlayerVisible=TRUE
WebUniversalReporterVisible=FALSE
WebUniversalAnalystVisible=FALSE
WebUniversalProfessionalVisible=FALSE
WebServicesASPNETVisible=TRUE
OfficeVisible=TRUE
eTrainerForWebVisible=TRUE
FunctionPluginVisible=TRUE
SequeLinkVisible=TRUE
IServerOLAPServicesVisible=TRUE
IServerReportServicesVisible=TRUE
### Components To Install (TRUE) or Remove

(FALSE) ###
DesktopAnalystSelect=TRUE
DesktopDesignerSelect=TRUE
ArchitectSelect=TRUE
ProjectBuilderSelect=TRUE
ServerAdminSelect=TRUE
CommandManagerSelect=TRUE
EnterpriseManagerSelect=TRUE
ObjectManagerSelect=TRUE
IServerSelect=TRUE
WebReporterSelect=TRUE
WebAnalystSelect=TRUE
WebProfessionalSelect=TRUE
SDKSelect=TRUE
MDXAdapterSelect=TRUE
AnalyticsModulesSelect=FALSE
NCSAdminSelect=TRUE
DeliveryEngineSelect=TRUE
SubscriptionPortalSelect=TRUE
TransactorSelect=TRUE
TransactorServerComponentsSelect=TRUE
TransactorAdminSelect=TRUE
TutorialReportingSelect=TRUE
TutorialDeliveryInstallSelect=TRUE
TutorialDeliveryConfigureSelect=TRUE
RealAudioPlayerSelect=TRUE
WebUniversalReporterSelect=FALSE
WebUniversalAnalystSelect=FALSE
WebUniversalProfessionalSelect=FALSE
WebServicesASPNETSelect=FALSE
OfficeSelect=TRUE
WebServerASPNETSelect=TRUE
WebUniversalServerJSPSelect=TRUE
WebUniversalServerASPSelect=FALSE
eTrainerForWebSelect=TRUE
FunctionPluginSelect=FALSE
SequeLinkSelect=TRUE
IServerOLAPServicesSelect=TRUE
IServerReportServicesSelect=TRUE
[ServerDefinitionSetting]
HideDialog=TRUE
OverwriteServerDefinition=FALSE
[TutorialReportingSetting]
HideDialog=TRUE
OverwriteDSN=FALSE
[Transactor]
LoggerOutput=TRUE
LoggerDirectory=Logger
[WebVirtualDirectory]
HideDialog=TRUE
VirtualDirectory=MicroStrategy
ReconfigureVirtualDirectory=TRUE
[PortalVirtualDirectory]
HideDialog=TRUE
VirtualDirectory=NarrowcastServer
[WebServicesVirtualDirectory]
HideDialog=TRUE
VirtualDirectory=MicroStrategyWS
[eTrainerForWebVirtualDirectory]
HideDialog=TRUE
VirtualDirectory=eTrainer
[OfficeWebServicesURL]
HideDialog=TRUE
AllowBlankURL=FALSE
URL=http://localhost/MicroStrategyWS/mstrws.a
smx
[MSOfficeLoadOptions]
HideDialog=TRUE
ConfigureExcel=TRUE
ConfigurePowerpoint=TRUE
ConfigureWord=TRUE
[IServerServiceAccount]
HideDialog=TRUE
SkipAccountSetting=FALSE
Login=<NT userlogin here>
Password=<user password here>
Domain=<domain here>
ServiceStartUp=AUTO
[NarrowcastServiceAccount]
HideDialog=TRUE
[TransactorServiceAccount]
HideDialog=TRUE
[WebUDeployment]
HideDialog=TRUE
SkipDeploymentSetting=FALSE
DeploymentDirectory=C:\Program
Files\MicroStrategy\Web
JSP
[Programfolder]
HideDialog=TRUE
Name=MicroStrategy
[Summary]
HideDialog=TRUE
[Finish]
HideDialog=TRUE
Copy and paste this example to create a

response.ini file. Make sure you check for the
spaces and new lines for the file paths in the
[InitialPaths] section.
Using the response.ini file
To use the response.ini file, do one of the following:
Type the following command in the Windows command

line:
Setup.exe --ResponseFile=C:\response.ini
From the Windows Start menu, choose Run to open the

Run dialog box. Enter the same command in the box and
click OK.
The setup program supports several command-line

parameters. The following applies to this function:
Parameters using double dashes, such as --auto, are
defined by MicroStrategy. For example, you can use the
--auto parameter as follows:
setup.exe --Auto=TRUE
--LogFile=C:\install.log
The command line is not case sensitive.
The following parameters are supported by the setup

program:
Auto= instructs the setup program to use the response
file and default values to enable a one-click installation. If
a component, such as serial key or disk space has an
invalid value, the setup program automatically reverts to
multiple-click mode, and all dialog boxes are displayed.
ResponseFile= contains responses to installation

questions and redefines default parameters. The path and
file name must be in double quotes ( ). If you use this
parameter, do not use any other parameters.
ConfigFile= used by the Configuration Wizard to set

up a repository, a server, or a client. The path and file
name must be in double quotes ( ).
LogFile= used to specify an alternative location and/or

name (other than install.log) for the log file in the
Common Files directory. If only the file name is entered,
the default location remains the Common Files directory.
Once specified, the alternative file becomes the default.
Configuring a response.ini file for the Configuration Wizard

The Configuration Wizard walks you through the process of
setting up the environment for the MicroStrategy products
installed in your system. It is possible to configure server
definition, project source names, and the metadata repository
using a response.ini file.
To generate the response.ini file for the Configuration

Wizard you can use any of the following methods:
create a response.ini file in the Configuration Wizard

by clicking the Advanced button in the interface
create a response.ini file through a text editor
To create the response.ini file through the Configuration

Wizard
1 From the Windows Start menu, point to Programs then

MicroStrategy, and then choose Configuration Wizard.
The Configuration Wizard opens.
2 Click Advanced. The Advanced Options dialog box

opens.
3 Select one of the following:
Use Response File: to reuse an existing response file
Generate Response File: to create a new response

file, overwriting the existing one if there is any
Itresponse.ini
is recommended that you always generate
file and configure it through the
You can specify the location of the ini file in the

response.ini file of the installation or by adding the -r
switch when running the setup.exe from the command
line. For more information, see Using response.ini for
the Configuration Wizard, page 262 of this chapter.
The response.ini file has the following parameters and

options.
0 means FALSE and 1 means TRUE.

Options Description
[Repository] This section configures the metadata

repository and statistics tables.
Repository = 1 or 0. If this is set to 1 then the Configuration

Wizard configures the metadata repository and
statistics table.
ConnType = This sets the type of database connection.
CreateConfig = 1 or 0. If it is set to 1, then the Configure

Default Configuration option is set.
Note: If CreateMDTables option is 1, then
you cannot set this option to 0 as this task will
be performed by default.
CreateMDTables = 1 or 0. If set to 1, the Configuration Wizard

performs the Create metadata table task to
create a metadata repository in the database
location of your choice. Also, the
CreateConfig option will be automatically
configured if this value is set to 1.
CreateStatTable 1 or 0. If this is set to 1, then the Configuration

= Wizard performs the Create statistics table
task.
MetadataPath = Specifies the path to the SQL scripts for

creating the metadata tables, for example,
C:\Program Files\Common Files
\MicroStrategy\MD8SQL8.sql.
StatisticsPath = Specifies the path to the SQL scripts for

creating the statistics table, for example,
Files\MicroStrategy\statistics_SQL
Server.SQL
DSNName = Specifies the Data Source Name for

configuring a metadata repository in the ODBC
database.
Options Description
UserName = Specifies the user name to log into the

database.
UserPwd = Specifies the password to log into the

database.
DSNNameStats = Specifies the Data Source Name for

configuring a statistics table in the ODBC
database.
UserNameStats = Specifies the user name to log into the

database for configuring statistics tables.
UserPwdStats = Specifies the password to log into the database

for configuring statistics tables.
UsingMVS = 1 or 0. To create a repository in DB2 MVS, set

this option to 1.
DBName = Specifies the database name to create tables in

MVS.
TBName = Specifies the table name to be created in the

database.
EncryptPassword 1 or 0. By default it is set to 0. You can type the

= password in the response.ini file if it is set
to 1. If it is set to 0 then the value you type will
not be the same.
[Server] In this section you can configure the

Intelligence Server definition. You can have
more than one [Server] section.
Server = 1 or 0. To configure the Setup MicroStrategy

Intelligence Server option of Configuration
Wizard, set this option to 1.
Action = This option takes the following two values for

Intelligence Server configuration:
Set to 1 to create a new server definition
Set to 2 to use an existing server definition
InstanceName = Specifies the name of the Intelligence Server

instance.
DSName = Specifies the data source name, for example,

TEST.
DSNUser = Specifies the user name to log into the ODBC

database.
DSNPwd = Specifies the password to log into the ODBC

database.
Options Description
EncryptPassword 1 or 0. By default it is set to 0. You can type the

= password in the response.ini file. If it is set
to 0, the value you type is not the same.
DSSUser = Specifies the MicroStrategy user name to log

into the project.
UseMultiProcess TRUE or FALSE sets the following options:

= TRUE to use MultiProcess
FALSE to use MultiThreaded
UseAsDefault = TRUE or FALSE. Set it to TRUE to use the newly
created Intelligence Server definition as the
default.
[Client] In this section you can configure the project
source name. You can have more than one
[Client] section. Additional client sections
can be written as [Client1], [Client2]
and so on.
Client = 1 or 0. To configure project sources, set this

option to 1.
DataSource = Specifies the name of the new project source to

create.
ConnType = Specifies the connection type. The following

connection types are supported:
2 connects to the metadata using an
ODBC DSN.
3 connects to the metadata through a
MicroStrategy Intelligence Server (3-tier).
DSN = If using connection type 2, specifies the name

of the ODBC database.
UserName = If using connection type 2, specifies the user

name to connect to the ODBC database.
UserPwd = If using connection type 2, specifies the

password to log into the database.
ServerName = If using connection type 3, specifies the name

of the MicroStrategy Intelligence Server that
you would like to connect to.
Port = If using connection type 3, specifies the port

number for the Intelligence Server when
creating a project source (3-tier project
source). The default port number for
MicroStrategy Intelligence Server is 34952.
MDType= 1 or 0. Specify the metadata type. By default it

is always 0.
Options Description
Hide = TRUE or FALSE. To hide the default project

sources displayed in the MicroStrategy
Desktop environment, set this option to TRUE.
By default it is always FALSE.
Authentication = The following authentication modes are

supported:
1Standard or login ID and password
entered by the user
2Network login ID (Windows
authentication)
8Guest account (Anonymous
authentication)
16LDAP authentication
Example of a Configuration Wizard

response.ini file
#This section configures the Metadata

Repository and Statistics Tables:
[Repository]
Repository=1
ConnType=1
CreateConfig=1
CreateMDTables=1
CreateStatTables=1
MetadataPath=C:\Program Files\Common
Files\MicroStrategy\MD7SQL7.sql
StatisticsPath=C:\Program Files\Common
Files\MicroStrategy\statistics_SQLServer.SQL
DSNName=
UserName=
UserPwd=
DSNNameStats=
UserNameStats=
UserPwdStats=
EncryptPassword=1
#In this section you can configure the server
definitions:
[Server]
Server=1
Action=1
InstanceName=
DSName=TEST
DSNUser=vmall
EncryptPassword=1
DSSUser=Administrator
DSNPwd=wnnnbcmomx
UseMultiProcess=True
#In this section you can configure the
Project Source Names. You can have more than
one [Client] section.
[Client]
Client=1
DataSource=Test PSN
ConnType=3
UserName=AccessUser
ServerName=
Port=34952
DSSFile=C:\WINNT\
MDType=0
Hide=False
Authentication=1
Using response.ini for the Configuration

Wizard
To use the response.ini file, do one of the following:
Type the following command in the Windows command

line:
macfgwiz.exe -r c:\response.ini
macfgwiz.exe
executable.
is the Configuration Wizard
From the Windows Start menu, choose Run to open the

Run dialog box. Enter the same command in the box and
click OK.
For more details on configuring the Configuration

Wizard, see Chapter 5, Configuring MicroStrategy
Intelligence Server of this guide.
Uninstalling using a response.ini file

You can uninstall all MicroStrategy products at once using a
response.ini file. You must create a response file with the
RemoveAll parameter set to TRUE in the Welcome section.
This is also known as a silent uninstall.
Before uninstallation begins, the MicroStrategy application
Checks for user privileges. If they are not valid,

uninstallation stops.
Checks for running components. If one is found,

Stops and deletes the MicroStrategy Intelligence Server

service.
Deletes application created files.

You can use the following response file to remove all
[Installer]
PropertiesFilesOverwrite=FALSE
EnableTracing=FALSE
HideAllDialogs=TRUE
ForceReboot=TRUE
PreventReboot=FALSE
CheckTCPIP=TRUE
CheckIIS=TRUE
CheckSP=TRUE
CreateShortcuts=TRUE
CheckRenameOperations=TRUE
AnalyticsOverwrite=FALSE
TutReportingOverwrite=FALSE
TutDeliveryOverwrite=FALSE
BackupFiles=FALSE
RunConfigWizard=FALSE
2005 MicroStrategy, Inc. Uninstalling using a response.ini file 263

StopAllServices=TRUE
StopIIS=TRUE
EnableASPServices=FALSE
ConfigWizardResponseFile=
RegistrySizeReq=
LogFile=
[Welcome]
HideDialog=TRUE
RemoveAll=TRUE
[WebVirtualDirectory]
HideDialog=TRUE
VirtualDirectory=MicroStrategy
RemoveVD=YES
[PortalVirtualDirectory]
HideDialog=TRUE
VirtualDirectory=NarrowcastServer
RemoveVD=YES
[WebServicesDirectory]
HideDialog=TRUE
VirtualDirectory=MicroStrategyWS
RemoveVD=YES
[eTrainerForWebVirtualDirectory]
HideDialog=TRUE
VirtualDirectory=eTrainer
RemoveVD=YES
[Finish]
HideDialog=TRUE
For details on creating a response.ini file, see Creating a

response.ini file, page 234.
After you have created a response.ini file, use the

following script at the command prompt to uninstall all
<path>\setup.exe --ResponseFile=
<path>\<responsefilename>
where the path for setup.exe must be the path to the

original setup.exe used to install MicroStrategy products.
264 Uninstalling using a response.ini file 2005 MicroStrategy, Inc.

Silent installation
A silent, or unattended, installation is one that presents no
user interface. Silent installations are useful for system
administrators who do not want users to interfere with the
installation. They are typically implemented by IT
departments that perform package-based installations across
the network, such as SMS. The silent installation can be used
for
deployment with Microsoft System Management Server

(SMS)
OEM installations
Silent installation through System Management

Server (SMS) environments
Upon setup completion, the System Management Server

(SMS) generates a Management Information Format (MIF)
file. There are two ways to generate the MIF file:
using the command line with the switch
-m<filename without extension>
adding the MIF section to the setup.ini file
Uninstallation in SMS also generates a corresponding

MIF file if you use the command line with the switch
-m<filename without extension>.
OEM silent installation
You can use silent installation to easily embed MicroStrategy

products with other applications. The following sections
discuss the procedures for OEM silent installations.
All the requirements listed for standard installation must be

observed for successful silent installation. For details, see
Chapter 3, Installing MicroStrategy on Windows of this
guide.
2005 MicroStrategy, Inc. Silent installation 265

To perform an OEM silent installation
When MicroStrategy products are installed as bundled

software with another product, the following procedure is
strongly recommended:
1 Create an installation response (response.ini) file for

the MicroStrategy products to install. The table that
follows shows which sections of the file are mandatory
and which are optional.
For detailed information regarding the contents of the

response.ini file, see Configuring a response.ini file
for installation, page 233.
Response File Section Selection
[Installer] Required
HideAllDialogs = Required
PreventReboot = Optional
StopAllServices = Optional
StopIIS = Optional
CheckRenameOperations = Optional
[UserRegistration] Required
[ComponentSelection] Required
EnterpriseManagerSelect = Required
[InitialPaths] Required
EnterpriseManager = Required
for
Setting HideAllDialogs = TRUE causes the script
the response file to
use default values as specified in the response.ini

file
not require user input
keep the dialog flow consistent from one instance to

the next
266 Silent installation 2005 MicroStrategy, Inc.

Consistency in the response file script from one instance

to the next is necessary; if setup.iss detects an
inconsistency in the dialog flow, installation is terminated
and a log file for the failure is created.
The only dialog flow modifications pertinent to silent

installation are specific to file location; therefore, the only
portion of the response.ini that may need to be
modified is the [InitialPaths] section.
2 Create the setup.iss file for the silent installation using

the response file, as follows:
[InstallShield Silent]
Version=v7.00
File=ResponseFile
[File Transfer]
OverwrittenReadOnly=NoToAll
[Application]
Name=MicroStrategy
Version=x.y.z
#x.y.z represent the version of the
product#
Company=MicroStrategy
Lang=0009
[{B339F3B3-E78C-45E8-B4D2-3C46C1C13663}-Dl
gOrder]
Count=0
3 Run the silent install with the response file as follows:
<path>\setup.exe -L0009
--ResponseFile="c:\response.ini" -s
-f1c:\setup.iss -f2c:\setup.log
You can bypass the language prompt by running setup.exe

with the command line option for the language. The following
table lists the values for the different languages that
MicroStrategy supports.
Language Value
English L0009
Italian L0010
Portuguese L0016
German L0007

Language Value
Spanish L000A
Japanese L0011
Korean L0012
Chinese L0004
Swedish L001D
French L000C
For example, to select Spanish as the user language, run the

silent install with the command line option for Spanish as
follows:
<path>\setup.exe -L000A
If the silent installation is successful, the resulting code value

is zero (ResultCode=0) in the setup.log file. If the setup
program encounters an invalid value for an installation
requirement, setup terminates and silent installation ceases.
Silent installation output
The system verifies compliance with installation

prerequisites and places related messages in a file created for
that purpose. The following applies to the generation and
storage of output messages during silent installation:
The MSTRInst.log file is created and placed in the
Temp folder.
The MSTRInst.log file is maintained during the entire
setup.
All system-generated messages, including messages

containing reasons for pre-installation termination, are
stored in the MSTRInst.log file.
Ifsubsequent
there are installation termination messages in
installation instances that use the same
dialog flow, they are also stored in the
MSTRInst.log.

The table below identifies the information that the

MSTRInst.log file includes.
Line Description
Function [F] Identifies the function calls in the

setup script.
Information [I] Logs information about the setup that

is running.
Warning [W] Includes feedback that you must

verify related to the setup. For
example, in normal mode, when
MicroStrategy applications are
running on a machine where the
setup is being run, you are prompted
to close all MicroStrategy applications
before proceeding. In silent mode,
you are not prompted, and instead
the setup terminates.
Severe [S] Includes fatal problems that prevent

the setup from proceeding. For
example, the Intelligence Server
Service cannot be created and setup
fails as a result.
A typical line in the MSTRInst.log file includes source file

name, function name, source line number, and time. It would
appear as follows:
[Z:\InstallMaster\Setup\Script
Files\MALicense.rul][UseDLL][l:
28][1318179ms][W] Le file
C:\WINDOWS\TEMP\{84D0D5E2-719A-
11D7-847C-000C293B5019}\{B339F3B3-E78C-45E
8-B4D2-3C46C1C13663}\MAInst.dll couldn't
be loaded in memory.
When reviewing warning messages in the

MSTRInst.log file, look for [W] and [S] to find
related problems.

Troubleshooting silent installation
Silent installation may not work if you are installing in a

different environment than the one you recorded. This is the
case because any dialog box that was not recorded previously
is not recognized, such as if you are prompted to stop your
Intelligence Server or your IIS Web server. If this happens,
check
the version of Intelligence Server to ensure that you have
the right one for the products you are installing
you do not have any MicroStrategy applications running
the setup.log file to see if the ResultCode=0.
Check the install.log for any recorded errors during

installation and the MSTRInst.log file for any possible
errors
The most common errors are
-8, which is an invalid path to the InstallShield Silent

Response File .iss file.
-12, which is dialog boxes out of order. This occurs

because an unrecorded screen opened when playing
the silent install.
It is recommended that you create a silent install that can be

used with a response.ini file. For more information, see
OEM silent installation, page 265. This way you can change
the settings in the response.ini file without having to
generate a new .iss file.

Silent installation of a hotfix

A hotfix is a file or a collection of files that you can apply to
MicroStrategy products installed on your computer to correct
a specific problem. Hotfixes are packaged in an executable
(.exe) file, which is a self-installing format. When you install a
hotfix, files are backed up automatically so that you can
remove the hotfix later.
You can apply a hotfix to MicroStrategy products using silent

installation. MicroStrategy supports silent installation of
hotfixes only for versions 7.5.3 and later.
To perform a silent installation of a hotfix
1 Insert the CD containing the Hotfix installable in the CD

drive.
2 Access the CD-ROM drive through the command prompt.
3 Run the silent install with the following command:
setup.exe /v" /qn
You can check the status of the silent installation in Windows

Task Manager. After applying the Hotfix, you can view it in
the Add/Remove Programs window.


11
AUTOMATED INSTALLATION
11.
AND CONFIGURATION ON
UNIX
Introduction
This chapter explains the various methods of performing a

fully automated and unattended installation and
configuration within the MicroStrategy platform when you do
not have access to a UNIX graphical user interface (GUI). The
chapter includes the following sections:
Silent installation
Configuring through command line mode

11 Automated Installation and Configuration on UNIX Installation and Configuration Guide
Silent installation
A silent or unattended installation is one that presents no
graphical user interface (GUI). Silent installations allow you
to automate the installation, so it can be called from a script
and executed without user interaction. Silent installations are
useful for system administrators who do not want users to
run the installation themselves. The silent installation can be
done on one or more computers.
Creating an options file

To run silent installation, you first create an options file and
then run it with the MicroStrategy InstallShield Wizard. Save
the options file as options.txt.
This options file or response file is used with the command

line argument -options to modify the wizard settings. The
settings that can be specified for the wizard are listed in the
next section, Settings that can be changed, page 275.
To use the options file
1 Log on to the computer where you are installing one or

2 You can access the installation files and the options file
from a CD-ROM or you can ask your system
administrator to share the files in a network location. For
information on mounting or unmounting CD-ROMs, see
Mounting CD-ROMs, page 400 in Appendix E,
Troubleshooting.
3 Browse to the MicroStrategy7Installation/

QueryReportingAnalysis_UNIX directory and open
options.txt in a text editor.
4 Specify a value for a setting by replacing the characters

<value>. For information on how to specify its value, see

Installation and Configuration Guide Automated Installation and Configuration on UNIX 11
5 Save the changes to the options.txt file.
6 To use the options file on a silent installation, specify

-silent -options <file-name> as a command line
argument to the wizard, where <file-name> is the name of
this options file, for example, options.txt.
The following are examples using the native launchers:
Solaris: >setupsol.bin -silent -options

options.txt
AIX: >setupAIX.bin -silent -options

options.txt
Settings that can be changed

The following settings can be changed for a silent installation.
For details on settings, see Chapter 4, Installing
The settings follow their descriptions, in the format
-W settingname=<value>
Customer information
Your name, the name of the company for which you work,
and the license key.
User
-W userRegistration.user=<value>
Company
-W userRegistration.company=<value>

License key
-W userRegistration.cdkey=<value>
MicroStrategy install locations
The install locations of the product. Specify valid directories

where the product should be installed.
Home directory
-W silent.homeDirectory=<value>
Install directory
-W silent.installDirectory=<value>
Log directory
-W silent.logDirectory=<value>
Product features
Legal values that you provide for all the product features are
true, which indicates that the feature is selected for

installation
false, which indicates that the feature is not selected for
installation
The selection state of MicroStrategy Intelligence Server.
-P IServerFeature.active=<value>
For example, to select MicroStrategy Intelligence Server for

installation, use
-P IServerFeature.active=true

MicroStrategy Web Universal Analyst
The selection state of MicroStrategy Web Universal Analyst.
-P WebUAnalystFeature.active=<value>
For example, to select MicroStrategy Web Universal Analyst

for installation, use
-P WebUAnalystFeature.active=true
MicroStrategy Web Universal Reporter
The selection state of MicroStrategy Web Universal

Reporter.
-P WebUReporterFeature.active=<value>
For example, to select MicroStrategy Web Universal Reporter

for installation, use
-P WebUReporterFeature.active=true
MicroStrategy Web Universal Professional
-P WebUProfFeature.active=<value>
For example, to select MicroStrategy Web Universal

Professional for installation, use
-P WebUProfFeature.active=true
MicroStrategy SDK
The selection state of MicroStrategy SDK.

-P SDKFeature.active=<value>
For example, to select MicroStrategy SDK for installation, use
-P SDKFeature.active=true

CPU license information
This value should be specified when the license being used for
MicroStrategy Intelligence Server is based on CPUs. Legal
values are integers between 1 and either the number of CPUs
allowed by the license or the number of CPUs in the machine,
whichever is lower.
-W cpuCountBean.cpuNumber=<value>
For example, the value
-W cpuCountBean.cpuNumber=
$J(install.cpuCount.maximum)
sets this option to the maximum value allowed.
MicroStrategy Web Universal application

deployment location
The deployment path of the application server where

MicroStrategy Web Universal is installed.
-W silent.keepDefaultDeployPath=<value>
You can keep the default application deployment path if you

are not using a WebLogic application server. To retain the
default path, set the value to true.
If you are using a WebLogic application server, set the value

for the default path to false. Then specify the absolute path
to the MicroStrategy Web Universal deployment location.
This location is used for reading and writing configuration
and log files.
-W silent.applicationDeployPath=<value>
MicroStrategy SDK installation location
The installation location for the MicroStrategy SDK.
-W silent.sdkDirectory="<value>"

Override options
The silent installation always overrides files from previous

installations.
To preserve some files, do not use a silent installation.

Silent installation output
The installation returns 0 if the installation is successful and
any other value if it is not. The install.log file located in
the InstallPath directory provides more information on
possible errors. For more information on the install.log
file, see Installation log file, page 232 in Chapter 3, Installing
MicroStrategy on Windows.
Ifstarts
the installation fails on any of the steps before it
copying the files, it does not give any feedback
other than the return value different from 0.
Configuring through command line mode

The MicroStrategy Configuration Wizard is provided in
command line mode so that you can use the Configuration
wizard through the operating system console if you do not
have access to the GUI. The Configuration Wizard (command
line mode) provides the following options:
Client: Creates MicroStrategy data sources in a 3-tier
mode.
2-tier data sources are available only on the

Windows operating system.
Repository: Creates metadata and statistics tables.
Server: Creates new MicroStrategy Intelligence Server

definitions in the metadata, assigns an existing server
definition for the Intelligence Server, and deletes existing
server definitions.
2005 MicroStrategy, Inc. Configuring through command line mode 279

Using the Configuration Wizard in command line mode, you

can also generate a response file through the operating
system console and run it from the same console. See Using
the response.ini file through the Configuration Wizard,
page 288 for more details about this feature.
Creating a response.ini file for the Configuration Wizard

Using a response.ini file with the Configuration Wizard,
you can configure the server definition, project source names,
and the metadata repository. For more information on a
response.ini file, see Installing and configuring with a
response.ini file, page 233 in Chapter 10, Automated
To create the response.ini file for the Configuration

Wizard you can use any of the following methods:
Create a response.ini file in the GUI mode of the

Configuration Wizard by clicking the Advanced button in
the interface.
Create a response.ini file using the Configuration

Wizard in command line mode.
Itresponse.ini
is recommended that you always create the
file through the GUI mode of the
Configuration Wizard. For more information, refer to
Creating a response.ini file for the Configuration
Wizard, page 280.
280 Configuring through command line mode 2005 MicroStrategy, Inc.

To create the response.ini file through the GUI mode of the

This procedure describes how to create a response file

while you are using the GUI mode of the Configuration
Wizard. To complete the entire configuration process
with the GUI mode, see Chapter 5, Configuring
1 In a UNIX console window, browse to <HOME_PATH>,

where <HOME_PATH> is the directory you specified as the
Home Directory during installation. Browse to the folder
bin.
2 Type ./mstrcfgwiz, then press ENTER. The

Configuration Wizard opens and the Welcome Screen is
displayed.
3 Click Advanced. The Configuration Wizard displays the

Advanced Options dialog box.
4 Select the Generate Response File option. Browse to the

path where the response file is to be saved.
5 Click Next. The Welcome Screen for the Configuration

Wizard opens again.
6 You must complete the wizard to generate the response

file; see Configuring MicroStrategy using the command
line mode, page 289 for steps to complete the
configuration.
7 At the end of the configuration, the following message

appears:
A response file will be generated. Would

you like to perform the configuration as
well?
Select Yes to perform both the tasks, or select No to

generate only the response file.

To create the response.ini file through the Configuration

Wizard in command line mode
This procedure describes how to create a response file

while you are using the command line mode of the
Configuration Wizard. To complete the entire
configuration process with the command line mode,
see Configuring MicroStrategy using the command
line mode, page 289.
1 In a UNIX console window, browse to <HOME_PATH>

bin.
2 Type ./mstrcfgwiz-editor, then press ENTER. The

Configuration Wizard in command line mode opens.
3 Type 2 to select the Create Response file option, and

press ENTER. To complete the remaining steps to
generate the response file, see Configuring
MicroStrategy using the command line mode, page 289.
Itresponse.ini
is recommended that you always create the
file through the GUI mode of the
Parameters and options in the response file
The response.ini file has the following parameters and

options.
Option Description
[Repository] Configures the metadata repository and

statistics tables. You can have more than one
[Repository] section.
Repository 1 or 0.
1: TRUE. The Configuration Wizard
configures the metadata repository and
statistics table.
0: FALSE.

Option Description
CreateConfig 1 or 0.
1: TRUE. The Configure Default
Configuration option is set. This setting is
dependent on the CreateMDTables setting,
described below. If the CreateMDTables
option is set to 1, then you cannot set the
CreateConfig option to 0 because this task
is performed by default.
0: FALSE.
DSNName Specifies the Data Source Name for

configuring a metadata repository in the ODBC
database.
UserName Specifies the user name to log into the

database.
UserPwd Specifies the password to log into the

database.
ConnType Sets the type of database connection.
CreateMDTables 1 or 0.
performs the Create metadata table task to
create a metadata repository in the
database location of your choice. If this
value is set to 1, the CreateConfig option
above is automatically configured.
0: FALSE.
MetadataPath Specifies the path to the SQL scripts for

creating the metadata tables, for example,
\<INTELLIGENCE_SERVER_INSTALL_PATH
\md7sql.sql.
CreateStatTables 1 or 0.
performs the Create statistics table task.
0: FALSE.
DSNNameStats Specifies the Data Source Name for

configuring a statistics table in the ODBC
database.
UserNameStats Specifies the user name to log into the

UserPwdStats Specifies the password to log into the

StatisticsPath Specifies the path to the SQL scripts for

creating the statistics table, for example,
\<INTELLIGENCE_SERVER_INSTALL_PATH
\statistics_DB2.sql.

Option Description
MDPrefix Specifies the prefix for the metadata repository

tables.
UsingMVS 1 or 0. 1 represents TRUE and 0 FALSE.

1: TRUE. To create a repository in DB2
MVS (Multiple Virtual System), set this
option to 1.
0: FALSE.
DBName Specifies the database name to create tables

in MVS.
TBName Specifies the table name to be created in the

database.
EncryptPassword 1 or 0.
1: TRUE. Indicates that the password
indicated in the response.ini file will be
encrypted.
0: FALSE. Indicates that the password
used exactly as typed, that is, it will not be
encrypted.
[Server] Configures the Intelligence Server definition.

You can have more than one [Server]
section.
Server 1 or 0.
1: TRUE. Configures the Setup
MicroStrategy Intelligence Server option of
the Configuration Wizard.
0: FALSE.
Action 1, 2, 3, or 4.
1: Creates a new Intelligence Server
definition.
2: Uses an existing Intelligence Server
definition.
3: Removes an existing Intelligence Server
definition.
4: Creates a new Intelligence Server
definition and use that as the default.
DSName Specifies the data source name, for example

TEST.
DSNUser Specifies the user name to log into the ODBC

database.
DSNPwd Specifies the password to log into the ODBC

database.
DSSUser Specifies the MicroStrategy user name to log

into the project.

Option Description
DSSPwd Specifies the password to log into the project.
UseMultiProcess TRUE or FALSE.

TRUE: Use MultiProcess.
FALSE: Use MultiThreaded.

tables.
TempTable Specifies the prefix to be used for the

temporary tables used by the server definition.
Port Specifies the port used by the Intelligence

Server.
InstanceName Specifies the Intelligence Server server

instance name.
ProjectsToRegiste Specifies the projects to register.

r
ProjectsToUnRegis Specifies the projects to unregister.

ter
encrypted.
encrypted.
[Client] Configures the project source name. You can

have more than one [Client] section.
Additional client sections can be labeled as
[Client1], [Client2], and so on.
Client 1 or 0.
1: TRUE. Configures project sources.
0: FALSE.
DataSource Specify the name of the new project source to

create.
ConnType Specifies the connection type. The following

connection types are supported:
2: Connects to the metadata using an
ODBC DSN.
3: Connects to the metadata through a
MicroStrategy Intelligence Server 3-tier.
DSN If using connection type (ConnType) 2 above,

specifies the name of the ODBC database.

Option Description
UserName If using connection type (ConnType) 2 above,

specifies the user name to connect to the
ODBC database.
UserPwd If using connection type (ConnType) 2 above,

specifies the password to log into the
database.

tables.
ServerName If using connection type (ConnType) 3 above,
specifies the name of the MicroStrategy
Intelligence Server to connect to.
Port If using connection type (ConnType) 3 above,

specifies the port number for the Intelligence
Server when creating a 3-tier project source.
The default port number for MicroStrategy
Intelligence Server is 34952.
Hide 1 or 0.
1: Hides the default project sources
displayed in the MicroStrategy Desktop
environment.
0: Default.
Authentication The following authentication modes are

supported:
1: Standard login ID and password entered
by the user.
2: Network login ID (Windows
authentication).
8: Guest account (anonymous
authentication).
16: LDAP authentication.
encrypted.
encrypted.

#This section configures the metadata repository and

statistics tables:
[Repository]
Repository=1
CreateConfig=1
DSNName=Test DSN
UserName=svradm
UserPwd=
CreateDefaultPSN=0
DefaultPSN=
ConnType=300
CreateMDTables=1
MetadataPath=
CreateStatTables=1
DSNNameStats=Test DSN
UserNameStats=svradm
UserPwdStats=
StatisticsPath=
MDPrefix=
UsingMVS=0
DBName=
TBName=
EncryptPassword=1
#In this section you can configure the server defini-

tions:
[Server]
Server=1
Action=4
DSName=Test DSN
DSNUser=svradm
DSNPwd=
DSSUser=Administrator
DSSPwd=UseMultiProcess=1
MDPrefix=
TempTable=
Port=
InstanceName=
EncryptPassword=1

#In this section you can configure the project source

names. You can have more than one [Client] section.
[Client]
Client=1
DataSource=Test PSN
ConnType=4
DSN=
UserName=User
UserPwd=
MDPrefix=null
ServerName=
Port=33333
Hide=0
Authentication=1
EncryptPassword=1
Using the response.ini file through the Configuration Wizard

This section describes how to use the response.ini file
through the MicroStrategy Configuration Wizard. For
information on how to configure through MicroStrategy
Configuration Wizard, see Configuring MicroStrategy using
the command line mode, page 289.
To use the response.ini file through the Configuration Wizard

in command line mode

bin.
2 Type ./mstrcfgwiz, then press ENTER. The

Configuration Wizard opens with the Welcome page
displayed.
3 Click Advanced. The Configuration Wizard displays the

Advanced Options dialog box.
4 Select the Use Response File option and browse to the

location of the response.ini file.

5 Click Next. The summary information is displayed.
6 Click Finish to start the configuration.
Configuring MicroStrategy using the command line mode

This section describes how to configure MicroStrategy using
the command line mode.
To configure MicroStrategy using the command line mode

Home Directory during installation. Browse to the bin
directory.
2 At the command prompt, type ./mstrcfgwiz-editor,

then press ENTER. The Configuration Wizard in command
line mode opens.
The sections or pages of the wizard displayed depend on

your selections. All the sections are described in the
sequence in which they appear:
Welcome message
Section Content Options
Welcome statement Press any key to proceed to the

next section of the editor.
Main menu
Options to use an existing Press 1 and ENTER to use an

response file or to create a new existing response file.
response file Press 2 and ENTER to create a
new response file.

The next section that appears depends on your choice in this

step:
If you press 1, the Use response section is displayed. Refer

to Use response file, page 290.
If you press 2, the Configuration Wizard section is

displayed. Refer to Configuration Wizard main tasks,
page 290.
Use response file
Prompt for response file path to be Type a valid path for the existing
executed in an unattended mode response file.
Note the following:

If the path and the response file are valid, the
configuration is performed and the Successful
message appears. This step confirms that the
configuration was successful and the editor closes.
If an error occurs before or during the process, the Use

Response File Error message appears. This message
displays the error that occurred when executing the
response file, and the editor closes.
Configuration Wizard main tasks
Options to configure metadata Press 1 and ENTER to configure

repository or statistics tables, to set tables for metadata repository
up MicroStrategy Intelligence and statistics.
Server, or to create a project Press 2 and ENTER to set up
source your MicroStrategy Intelligence
Server.
Press 3 and ENTER to create a
project source.

The next screen that appears depends on your choice in this

step:
If you press 1, the Create metadata tables section is

displayed. For more information, see Configuring
metadata and statistics tables, page 291.
If you press 2, the ODBC data source for server section is

displayed. For more information, see Setting up
MicroStrategy Intelligence Server, page 298.
If you press 3, the Project source name section is

displayed. For more information, see Creating a project
source, page 304.
Configuring metadata and statistics tables

You access this section by selecting option 1, Configure
Metadata Repository or Statistics tables, from the
Configuration Wizard main tasks window.
Create metadata tables
Option to create metadata tables Press Y or N and ENTER. The

default answer is yes.

step:
If you choose to create metadata tables, ODBC data source

for metadata configuration section is displayed. For more
information, see ODBC data source for metadata
configuration, page 292.
If you choose not to create metadata tables, Create

metadata configuration section is displayed. For more
information, see Create metadata configuration,
page 294.

ODBC data source for metadata configuration
Option to specify name of the Type the name and press ENTER.
ODBC data source
If you specify a valid name for the ODBC data source, the
ODBC metadata login section is displayed. If you provide a
name that does not exist or the data source is not supported
for the metadata connection, an error message is displayed
along with the option to specify the correct name.
ODBC metadata login
Option to specify login for the Type the name and press ENTER.
metadata
If you specify a login, the ODBC metadata password section is

displayed. If you do not enter a login, an error message is
displayed along with the option to specify a valid login.
ODBC metadata password
Option to specify password for the Type the password and press
metadata ENTER.
After you specify a password, the Metadata prefix section is

displayed.

Metadata prefix
This step is optional.
Option to specify prefix for the Type the prefix and press ENTER.
metadata To ignore this step, press ENTER.
The next section displayed depends on your ODBC data

source details:
If the data source points to a DB2 MVS database, MVS

database section is displayed. For more information, see
MVS database name, page 293.
If the data source does not point to an MVS database,

Metadata script section is displayed. For more
information, see Metadata script, page 294.
MVS database name
Option to specify name for the Type the name and press ENTER.
MVS database To ignore this step, press ENTER.
If you do not provide a name for the MVS database, the

default database is used. The next section displayed is the
MVS table space name.
MVS table space name
Option to specify name of the table Type the name and press ENTER.
space for the MVS database To ignore this step, press ENTER.

If you do not provide a table space name for the MVS

database, the default name of the table space is used. The
next section displayed is the Metadata script section.
Metadata script
Option to specify location of the Type the path and press ENTER.
metadata script To use the default script, press
ENTER.
If you specify a valid path, the Create statistics tables section

is displayed. If the path is invalid, an error message is
displayed along with the option to specify a valid path.
Create metadata configuration
As described in the Create metadata tables section, Create

metadata configuration section is displayed if you choose not
to create metadata tables.
Option to create metadata Press Y or N and ENTER.

configuration The default answer is yes.

step:
If you choose to create a metadata configuration, ODBC
data source for metadata configuration section is
displayed. For more information, see ODBC data source
for metadata configuration, page 292.
If you choose not to create a metadata configuration,

Create statistics tables section is displayed. For more
information, see Create statistics tables, page 295.

Create statistics tables
You access this step if you specify a valid path in the Metadata
script section, or if you choose not to create metadata tables
in the Create metadata tables section.
Option to create statistics tables Press Y or N and ENTER.

The default answer is yes.

step:
If you choose to create statistics tables, the next section

that is displayed depends upon how you accessed this
Create statistics tables section:
If you answered Yes to the Create metadata tables

section above or Yes to the Create metadata
configuration section above, then you have already set
up information about ODBC. In this scenario, the Use
same ODBC info section is displayed. For more
information, see Use same ODBC info, page 296.
If you answered No to the Create metadata

configuration section, the ODBC data source for
statistics configuration section is displayed. For more
information, see ODBC data source for statistics
configuration, page 296.
If you choose not to create statistics tables, the Save
response file section is displayed. For more information,
see Save response file, page 297.

Use same ODBC info
Option to use ODBC information Press Y or N and ENTER.

provided earlier The default answer is yes.

step:
If you choose to use the ODBC information, the Statistics

script section is displayed. For more information, see
Statistics script, page 297.
If you choose not to use the same ODBC information, the

ODBC data source for statistics configuration section is
displayed. For more information, see ODBC data source
for statistics configuration, page 296.
ODBC data source for statistics configuration
ODBC data source for statistics
configuration
If you specify a valid name for the ODBC data source for
statistics configuration, the ODBC statistics login section is
displayed. If you provide a name that does not exist or the
data source uses a database that is not allowed to create
statistics, an error message is displayed along with the option
to specify the correct name.
ODBC statistics login
ODBC statistics

If you specify a login, the ODBC statistics password section is

displayed along with the option to specify the login.
ODBC statistics password
ODBC statistics ENTER.
After you specify a password, the Statistics script section is

displayed.
Statistics script
Option to specify location of the Type the path and press ENTER.
statistics script To use the default script, simply
press ENTER.
If you specify a valid path, the Save response file section is

displayed. If the path is invalid, an error message is displayed
along with the option to specify a valid path.
Save response file
You access this step by specifying the location of the statistics

script in the Statistics script section above, or by answering
No in the Create statistics tables section above.
Option to specify location where The default path is shown.

the response file will be saved To change the location, type a new
path and press ENTER.

If you specify a valid path and the response file is saved, the
Finish metadata process section is displayed. If the path is
invalid or if there is a problem saving the response file, an
error message is displayed along with the option to specify a
valid path.
Finish metadata process
Option to execute the response file Press Y or N and ENTER.

created The default answer is yes.
If you choose to execute the response file and the path is

valid, the configuration is performed and the Successful
message appears. This step confirms that the configuration
was successful and the editor closes. If you choose not to
execute the response file, the editor closes.
Setting up MicroStrategy Intelligence Server

You access this section by selecting option 2, Set Up a
MicroStrategy Intelligence Server from the Configuration
Wizard main tasks section.
ODBC data source for server
ODBC data source for Intelligence
Server
If you specify a valid name for the ODBC data source, the
ODBC server login section is displayed. If you provide a name
that does not exist or the data source is not supported for the
metadata connection, an error message is displayed along
with the option to specify the correct name.

ODBC server login
metadata
If you specify a login, the ODBC server password section is

displayed along with the option to specify a valid login.
ODBC server password
metadata ENTER.
After you specify a password, the Metadata prefix for server

section is displayed.
Metadata prefix for server
metadata To ignore this step, press ENTER.
The next section displayed is the Temp table prefix section.

Temp table prefix
temp tables To ignore this step, press ENTER.
The next section displayed is the MicroStrategy login section.
MicroStrategy login
Option to specify MicroStrategy Type the name and press ENTER.

login for the metadata
Type a valid MicroStrategy user login that has administrator

privileges. If you specify a valid login, the MicroStrategy
password section is displayed. If you do not enter any login,
an error message is displayed along with the option to specify
a valid login.
MicroStrategy password
Option to specify MicroStrategy Type the password and press

password for the metadata ENTER.
Type a valid password for the MicroStrategy user that has

administrator privileges. After you specify a password, the
Server action section is displayed.
Itcannot
is mandatory to specify the password, otherwise you
proceed to the next page.

Server action
Options to create, link, or remove a Press 1 and ENTER to create a

server definition server definition.
Press 2 and ENTER to link a server
definition.
Press 3 and ENTER to remove a
server definition.
Press 4 and ENTER to create a
server definition and use it as the
default

step:
If you select 1, 2, or 4 the Server definition name section is
displayed. For more information, see Server definition
name, page 301.
If you select 3, the Server definition names section is

displayed. For more information, see Server definition
names, page 302.
Server definition name
You access this section by selecting option 1-Create a server

definition, option 2-Link a server definition, or option 4-
Create a server definition and use it as a default from the
Server action section above.
Option to specify server definition Type the name and press ENTER.
If you specify a valid server definition, the Server port

number section is displayed. If you enter an invalid name or a
name that already exists, an error message is displayed along
with the option to specify a valid name.

Server definition names
You access this section by selecting option 3, Remove a server

definition, from the Server action section.
Option to specify server definitions Type the name and press ENTER.
to be removed To remove multiple server
definitions, separate the names
with a backslash (\).
If you specify a valid server definition, the Server port

number section is displayed. If you enter an invalid name, an
valid name.
Server port number
You access this section after completing the Server definition

name or Server definition names sections.
Option to specify port number Type the port number and press
ENTER.
The default port number is 34952.
If you specify a valid port number, the Projects to be loaded

section is displayed. If you enter an invalid input or an invalid
range, an error message is displayed along with the option to
specify a valid number.
Projects to be loaded
Option to specify projects to be Type the name and press ENTER.

loaded To load multiple projects, separate
the names with a backslash (\).

If you specify a valid project name, the Projects to be

unloaded section is displayed. If you specify an invalid
project name, an error message is displayed along with the
option to specify a valid name.
Projects to be unloaded
Option to specify projects to be Type the name and press ENTER.

unloaded To unload multiple projects,
separate the names with a
backslash (\).
If you specify a valid project name, the Save response file

section is displayed. If you enter an invalid project name, an
valid name.
Save response file
Option to specify location where The default path is shown.

the response file will be saved To change the location, type a new
path and press ENTER.
Finish server process section is displayed. If the path is
invalid or if there is a problem saving the response file, an
valid path.

Finish server process

created The default answer is Yes.

Creating a project source

You access this section by selecting option 3, Create a Project
Source, from the Configuration Wizard main tasks section.
Project source name
project source
If you specify a valid name, the Intelligence Server name

section is displayed. If you provide an invalid name or one
that already exists, an error message is displayed along with
the option to specify the correct name.
Intelligence Server name
Option to specify the name of the Type the name and press ENTER.
Intelligence Server The default is the name of the
machine on which Intelligence
Server is installed.

If you specify a valid name, the Server port number for

project source section is displayed. If you provide an invalid
name, an error message is displayed along with the option to
specify the correct name.
Server port number for project source
Option to specify the port number Type the port number and press
ENTER.
The default port number is 34952.
If you specify a valid port number, the Authentication type

section is displayed. If you enter an invalid input or an invalid
range, an error message is displayed along with the option to
specify a valid number.
Authentication type
Options to select the type of Press 1 and ENTER to use

authentication anonymous authentication.
Press 2 and ENTER to use
LDAP authentication.
database authentication.
standard authentication.
Selecting any of the authentication options, 1, 2, 3, or 4, in

this step displays the Save response file section. If you select
an invalid response, the Authentication type section is
displayed again so you can make a valid choice. To learn
about LDAP authentication, refer to the MicroStrategy
System Administration guide.

Save response file
Option to specify the location The default path is shown.

where the response file will be To change the location, type a new
saved path and press ENTER.
Finish project source process section is displayed. If the path
is invalid or if there is a problem saving the response file, an
valid path.
Finish project source process

created The default answer is Yes.


12
ADDING OR REMOVING
12.
MICROSTRATEGY
COMPONENTS
Introduction
This chapter describes how to add or remove MicroStrategy

components on different operating systems.
Adding or removing MicroStrategy components on

Windows
Reinstalling MicroStrategy components on Windows
Uninstalling MicroStrategy components on Windows
Uninstalling MicroStrategy components on UNIX and

Linux

12 Adding or Removing MicroStrategy Components Installation and Configuration Guide
Adding or removing MicroStrategy components

on Windows
You can choose to add or remove one or more MicroStrategy
components.
To add or remove MicroStrategy components
1 Close all installed MicroStrategy products.
2 On the Windows Start menu, point to Settings, and then

choose Control Panel. The Control Panel window opens.
3 Double-click Add/Remove Programs. The Add/Remove

Programs dialog box opens.
4 Select MicroStrategy and click Change/Remove. The

MicroStrategy Setup Maintenance program opens.
5 Select Modify and click Next.
6 Select to accept the license agreement and click Next.
7 Verify your customer information and click Next.
8 Verify your setup type and click Next.
9 Select the components to add by selecting their check

boxes. Clear the check boxes for the components you want
to uninstall. Click Next.
The components that are currently installed are

displayed with their check boxes selected. These
components are not reinstalled during the
modification process. If you clear any of the check
boxes, that particular component is uninstalled
during the modification process. You are advised
not to clear the check boxes of the components that
are already installed, unless you want to remove
the component.
308 Adding or removing MicroStrategy components on Windows 2005 MicroStrategy, Inc.

Installation and Configuration Guide Adding or Removing MicroStrategy Components 12
10 If you are prompted to stop your Web server, click Yes to

stop it and continue with adding or removing files.
11 Verify the settings and click Next to begin copying or

removing the files.
12 After the modification routine is complete, click Finish to

close the maintenance program.
For more details on each page of the InstallShield Wizard, see

2005 MicroStrategy, Inc. Adding or removing MicroStrategy components on Windows 309

Reinstalling MicroStrategy components on

Windows
You can reinstall MicroStrategy components if you face
problems with previously installed components. During
reinstallation the list of components previously installed are
displayed and these components are reinstalled.
The reinstallation of MicroStrategy Office must be

performed separately. The procedure for reinstalling
MicroStrategy Office is explained in the following
section.
To reinstall MicroStrategy components
2 On the Windows Start menu, select Settings, and then



5 Select Repair and click Next.
6 Accept the license agreement and click Next.
7 You are prompted to select Yes to continue with the

reinstallation procedure and overwrite the components.
To not want to overwrite the components, select No.

stop it and continue with the reinstallation.
9 After the reinstallation routine is complete, click Finish to

For details on each page of the InstallShield Wizard, see

310 Reinstalling MicroStrategy components on Windows 2005 MicroStrategy, Inc.

Reinstalling MicroStrategy Office

This section describes the reinstallation procedure for
MicroStrategy Office.
To reinstall MicroStrategy Office

3 Double-click the Add/Remove Programs icon. The

Add/Remove Programs dialog box opens.
4 Select MicroStrategy Office and click Change/Remove.

The MicroStrategy Office Setup Maintenance program
opens.
5 Select Repair and click Next.
6 Accept the license agreement and click Next.

reinstallation procedure and overwrite the components.
To not overwrite the components, select No.

stop it and continue with the reinstallation.
9 After the reinstallation routine is complete, click Finish to

For details on each page of the InstallShield Wizard, see

2005 MicroStrategy, Inc. Reinstalling MicroStrategy components on Windows 311

Uninstalling MicroStrategy components on

Windows
The uninstallation procedure performs the following
functions:
Unregisters and removes selected files, registry entries,

and shortcuts logged in the Uninst.isu log file.
Calls a custom DLL to handle unlogged items, such as

registry entries and files.
Before uninstallation begins, the DLL file performs the

following functions:
Checks for user privileges. If they are not valid,

Checks for running components. If a component is found
running, uninstallation stops.
Stops and deletes the MicroStrategy Intelligence Server

service. This occurs only when the Intelligence Server is
being uninstalled.
Deletes files created by the application, such as *.log,

*.gid, *.ldb and *.tb.
The uninstallation of MicroStrategy Office must be

performed separately. The procedure for reinstalling
MicroStrategy Office is explained in the following
sections.
To uninstall MicroStrategy components on Windows

Control Panel. The Control Panel window opens.

312 Uninstalling MicroStrategy components on Windows 2005 MicroStrategy, Inc.


5 Select Remove and click Next.
6 Click Yes to any prompts that appear.

stop it and continue with the uninstallation.
8 After the uninstall routine is complete, select Yes to

restart your computer, or No to restart it later.
9 Click Finish to close the maintenance program.
You should restart the computer for a clean uninstall.

Uninstalling MicroStrategy Office
This section describes the uninstalling procedure for
MicroStrategy Office.
To uninstall MicroStrategy Office

Control Panel. The Control Panel window opens.

4 Select MicroStrategy Office and click Change/Remove.

The MicroStrategy Office Setup Maintenance program
opens.
5 Select Remove and click Next.
2005 MicroStrategy, Inc. Uninstalling MicroStrategy components on Windows 313


uninstallation procedure. To not remove the application
with all of its components, select No.
7 After the uninstallation routine is complete, click Finish

to close the maintenance program.
Uninstalling MicroStrategy components on

UNIX and Linux
This section discusses how to uninstall MicroStrategy
Intelligence Server and Web Universal on UNIX/Linux
platform.
Uninstalling MicroStrategy Intelligence Server on UNIX and

Linux
This section includes information on steps required to
uninstall MicroStrategy Intelligence Server on UNIX/Linux
platform.
To uninstall MicroStrategy Intelligence Server
1 Browse to <INSTALL_PATH>, where <INSTALL_PATH>

is the directory you specified as the install directory
2 Browse to the ./_uninst folder and execute

uninstall.bin.
3 The InstallShield Wizard opens with the Welcome page

displayed. Click Next.
4 On the Product Uninstallation page, select the products to

uninstall. To uninstall all products, select Product
Uninstallation. Click Next.
314 Uninstalling MicroStrategy components on UNIX and Linux 2005 MicroStrategy, Inc.
5 On the Summary page, verify the information and click

Next. The products are uninstalled.
6 After uninstallation is complete, a message is displayed.

Click Finish to complete the process and exit the
InstallShield Wizard.
Uninstalling MicroStrategy Web Universal on UNIX and Linux

This section includes information on the procedure required
to uninstall MicroStrategy Web Universal on the UNIX or
Linux platform.
Depending on the operating system, the steps to

uninstall MicroStrategy Web Universal may differ
slightly.
To uninstall MicroStrategy Web Universal
1 Locate the uninstaller.bin executable under

WebUniversal/_uninst.
2 Run the uninstaller.bin with the following

command:
./uninstaller.bin
3 The InstallShield Wizard opens. Review the uninstallation
message and click Next to proceed.
4 Review the information about the directory from which

MicroStrategy Web Universal is removed and click Next
to proceed.
5 After uninstallation is complete, click Finish to close the

wizard.
2005 MicroStrategy, Inc. Uninstalling MicroStrategy components on UNIX and Linux 315
316 Uninstalling MicroStrategy components on UNIX and Linux 2005 MicroStrategy, Inc.
A
A. MANAGING LICENSES
Introduction
After you have the MicroStrategy system in place, the

Intelligence Server verifies that you have obtained the
licenses for how the system is being used. That is, do you have
more copies of a MicroStrategy product installed and being
used than the number of licenses you have? Or, are more
users using the system than the number of licenses you have?
If you are not in compliance, the system displays a message
when you start Command Manager or open the
Administration icon in MicroStrategy Desktop.

A Managing Licenses Installation and Configuration Guide
The licenses are checked according to the type of license you

have purchased:
Named user
CPU
If you are not in compliance, use the License Manager tool to

find out more detail. If you obtain additional licenses from
MicroStrategy, you can use the tool to upgrade them.
This appendix has the following topics:
Verifying Named user licenses

Verifying CPU licenses
MicroStrategy License Manager
Determining the number of licenses in use
Upgrading a license
Verifying Named user licenses

When you purchase licenses in the Named user format, the
system monitors the number of users you have implemented
and compares it to the number of licenses. It can be
considered out of compliance if too many users are in the
metadata or more users are assigned higher-level privileges
than are licensed. For example, if you have licenses for 10
Web Professional users and 12 users have the privileges
associated with Web Professional, the system considers that
noncompliance.
Ifnotyour system is out of license compliance, you may

be able to assign privileges related to licenses that
are out of compliance. To bring it back into
compliance, you can either change the user privileges
to conform to the number of licenses you have, or you
can obtain additional licenses from MicroStrategy. Use
318 Verifying Named user licenses 2005 MicroStrategy, Inc.

Basic Setup Guide Managing Licenses A
the License Manager tool to determine the users that

are causing the metadata to exceed your license and to
determine the privileges for those users that are
causing each user to be classified as a particular
license type. For more information, see MicroStrategy
License Manager, page 321.
For more information about the privileges associated with

each license type, see the MicroStrategy System
To verify the license compliance, Intelligence Server scans the

metadata repository for the number of users fitting these
license types: Web Professional, Web Analyst, Web Reporter,
Architect, Desktop Designer, Desktop Analyst, and
MicroStrategy Administrator. If the number of licenses has
been exceeded, you see a warning message when you start
Command Manager or open the Administration icon in
Additionally, Intelligence Server writes information in the log

file named DSSErrors.log detailing for each license type
the number of users licensed and the actual number of users
detected.
You can configure the time of day that Intelligence Server

verifies your Named user licenses. To do this, open the
Intelligence Server Configuration Editor, select the Server
definition: Advanced category, and specify the time in the
Time to run license check (24 hr format) box.
Verifying CPU licenses

When you purchase licenses in the CPU format, Intelligence
Server governs its processes to operate only on the first n
CPUs you specify during installation. The ability to deploy
Intelligence Server only on a subset of the total number of
physical CPUs on a given machine is called Processor
Affinity.
2005 MicroStrategy, Inc. Verifying CPU licenses 319

In AIX, Processor Affinity is implemented using resource

sets. A resource set is a logical structure that contains a list of
CPUs. Processes are bound to a resource set that defines the
specific CPUs that will be used.
In Solaris, Processor Affinity is implemented using processor

set binding. A processor set is a collection of processors.
Thus, a process that is assigned to a processor set can only
use the specified CPUs.
In Windows, Processor Affinity is implemented by using a

special tool called MAWebAff.exe. This tool is located in the
root directory of MicroStrategy Web application, which is
C:\Program Files\MicroStrategy\Web ASPx, by
default. The MAWebAff.exe tool allows the administrator to
choose the physical CPUs MicroStrategy Web can use.
The system monitors the number of CPUs being used by the

Intelligence Server in your implementation and compares it
to the number of licenses you have. Your system can be
considered out of compliance if more CPUs are being used
than are licensed. For example, this could happen if you have
Intelligence Server installed on two dual processor machines
so that all four CPUs are being used, but you have a license
for only two CPUs.
To bring the system back into compliance, you can
shut down the machine that is running the Intelligence

Server to reduce the number of CPUs being used, so that it
conforms to the number of licenses you have
obtain additional licenses from MicroStrategy.
If necessary, use the License Manager tool to help determine

the number of CPUs license. For information, see
MicroStrategy License Manager, page 321.
MicroStrategy Service Manager can be used to view and

modify the CPU utilization of the Intelligence Server. Thus, if
the installation assigns CPUs 0 and 1 on a machine with 4
CPUs and the CPU license is for 4 CPUs, the Service Manager
can be used to assign CPUs 2 and 3. You need to stop and
start the Intelligence Server for the changes to take effect. For
more information, refer to the MicroStrategy System
320 Verifying CPU licenses 2005 MicroStrategy, Inc.

To verify CPU license compliance, Intelligence Server scans

the network to count the number of CPUs in use by the
Intelligence Servers. If the number of licenses has been
exceeded, a message appears when you start Command
Manager or open the Administration icon in MicroStrategy
Desktop.
Additionally, Intelligence Server writes information in the log

file named DSSErrors.log detailing the number of CPUs
licensed and the actual number of CPUs being used. The
DSSErrors.log is located by default in the Log Path specified
MicroStrategy License Manager

MicroStrategy License Manager is a tool for performing
certain license auditing tasks. License Manager allows you to
inventory the different MicroStrategy products installed

on a given machine
audit a MicroStrategy repository based on the number of

users mapped to particular products in the MicroStrategy
price list and generate a printable HTML report
upgrade licenses of installed MicroStrategy products
review the history of installations executed in a given

machine over time
Determining the number of licenses in use

Take the following steps to view the number of licenses for
MicroStrategy products and users:
To determine the number of licenses in use
1 For Windows, perform the following step:
2005 MicroStrategy, Inc. MicroStrategy License Manager 321

From the Windows Start menu, point to Programs,

choose MicroStrategy, and then License Manager.
The License Manager window opens.
For UNIX, perform the following steps:
Connect to each of your metadatas.
From the UNIX console window, browse to

<HOME_PATH> where <HOME_PATH> is the directory
you specified as the Home Directory during
installation. Browse to the folder bin and type
./mstrlicmgr.
2 On the Audit tab, connect to the project source.
3 Select the Everyone group and click Audit. Count the

number of licenses per product for enabled users; do not
count disabled users. You can print the summary
information. If you want more information, click Report
to create and view an HTML page.
4 Total this number for all metadatas. If you did not

purchase this many licenses, contact MicroStrategy to
purchase or upgrade licenses as necessary.
The License Manager counts the number of licenses based on

the number of users with at least one privilege for a given
product. The Administrator user created by default with the
repository, or any new name given to this user, is not
considered in the count.
Upgrading a license
If you need to upgrade a license, use the License Manager to
perform the upgrade after you receive a new license key from
MicroStrategy.
To upgrade a license
1 For Windows, perform the following step:
322 Upgrading a license 2005 MicroStrategy, Inc.


choose MicroStrategy, and then License Manager.
The License Manager window opens.
For UNIX, perform the following steps:
From a UNIX console window, browse to

<HOME_PATH> where <HOME_PATH> is the directory
you specified as the home directory during
installation.
Browse to the folder bin and type ./mstrlicmgr.
2 On the Upgrade tab, type or paste the new key in the New
License Key box and click Upgrade. The results of the
upgrade appear in the Upgrade Results box.
Iflicense
you have upgraded your system to bring it back into
compliance, you should run a compliance
check after the upgrade. This allows the system to
recognize the upgrade and system behavior can return
to normal. To run a compliance check, on the Audit
tab, click the Compliance Check button. A message
appears when the compliance check is complete
For more information, refer to the MicroStrategy System

2005 MicroStrategy, Inc. Upgrading a license 323

324 Upgrading a license 2005 MicroStrategy, Inc.

B
B. ODBC AND DSNS
Introduction
This appendix describes the Open Database Connectivity

(ODBC) standard for connecting to databases and creating
data source names (DSNs) for the ODBC drivers that are
bundled with the MicroStrategy applications, including
settings and configuration options.
This appendix has the following sections:

Setting up ODBC
Creating DSNs
Testing the ODBC connectivity
Parameters from ODBC.ini

B ODBC and DSNs Installation and Configuration Guide
Setting up ODBC
The following information is intended to assist you in setting
up ODBC between the MicroStrategy Intelligence Server and
your metadata database and data warehouse.
ODBC is a standard method of communicating with database

servers. MicroStrategy Intelligence Server uses ODBC to
connect to and communicate with all database servers in the
system. Specifically, ODBC connects to and transfers data to
and from data sources within relational databases.
The ODBC interface permits maximum interoperabilityan

application can access data in diverse database management
systems (DBMSs) through a single interface. A client
application uses a database driver and a driver manager to
make a connection to the data source. A data source,
identified by a DSN, is the database or file accessed by a
driver. Data source is another term for a logical database
within a database server. A database server can comprise
multiple logical databases or data sources.
Metadata is a repository whose data associates the tables and

columns of a data warehouse with user-defined attributes
and facts to enable the mapping of business views, terms, and
needs to the underlying database structure. Metadata can
reside on the same server as the data warehouse or on a
different server. It can be stored in different relational
DBMSs.
A data warehouse stores the data that users of the system

must analyze to track and respond to business trends and
facilitate forecasting and planning efforts.
A successful ODBC connection requires the following

information:
A data source name (DSN) is the name for a pointer used

by a client application to find and connect to a data
source. A data source is the database accessed by a driver.
The information obtained through a DSN generally
includes host computer name or IP address, instance
name, and database name. However, the exact
information varies depending on the type of database
server.
326 Setting up ODBC 2005 MicroStrategy, Inc.

Installation and Configuration Guide ODBC and DSNs B
An ODBC driver is a type of software that translates

information between the client application
(MicroStrategy Intelligence Server) and the database
server API. Different database servers speak through
different APIs. For example, Informix database servers
use Informix Command Line Interface (CLI), Oracle
database servers use the Oracle API, Sybase database
servers use another API, and so on.
A connection string stores the information required to

connect to a database server. A connection string usually
includes a DSN, as well as the user ID and password
required to log in to the database server. This information
varies depending on the particular database server.
The ODBC driver manager coordinates communication

between a client application and database server. The
client application tells the driver manager that it needs to
connect using a particular connection string. The DSN
found in this connection string provides the driver
manager with the type of database server to which the
application needs access along with the driver to be used.
From this information, the driver manager initiates the
communication.
MicroStrategy Software
ODBC Driver
Manager
Database server Database server

driver 1 driver 2
Database server Database server

API 1 API 2
Database server 1 Database server 2
Database Database Database Database
2005 MicroStrategy, Inc. Setting up ODBC 327

Configuring ODBC with MicroStrategy for Windows

MicroStrategy components require 32-bit drivers to achieve
ODBC connectivity. These applications call the driver
manager, which in turn calls the drivers. Ideally, all ODBC
drivers used on machines connected to data sources should
be from the same vendor.
Default location for ODBC and driver files for

Windows
The ODBC driver manager and support libraries are usually

installed in the following default directories.
Default location for ODBC driver manager

Operating system
libraries
Windows 98 and ME C:\WINDOWS\SYSTEM
Windows 2000 C:\WINNT\SYSTEM32
Windows 2003 C:\WINDOWS\SYSTEM32
The database-specific ODBC drivers are installed in locations

as specified during the installation of the drivers.
MicroStrategy branded drivers are installed in C:\Program
Files\Common Files\MicroStrategy.
Configuring ODBC with MicroStrategy for UNIX

MicroStrategy UNIX components require 32-bit drivers to
achieve ODBC connectivity. These applications call the driver
manager, which in turn calls the drivers. Ideally, all ODBC
drivers used on machines connected to data sources should
be from the same vendor.
328 Setting up ODBC 2005 MicroStrategy, Inc.

Default location for ODBC and driver files for

UNIX and Linux
The ODBC driver manager and support libraries are usually

installed in the following default directories:
Operating
Default Location for ODBC Driver Manager Libraries
System
Solaris 8, 9 <INSTALL_PATH>/lib32
AIX 5.2 <INSTALL_PATH>/lib32
RedHat <INSTALL_PATH>/lib32
Linux
The database-specific ODBC drivers are installed in the

locations specified during the installation of the drivers.
MicroStrategy branded drivers are installed in
<INSTALL_PATH>/lib32, where <INSTALL_PATH> is the
directory you specified as the Install Directory in the Install
Wizard.

lists only the MicroStrategy branded ODBC drivers.
However, this guide also provides information on how
to install drivers from other vendors with
MicroStrategy. For more information, Creating DSNs
for individual ODBC drivers, page 338.
2005 MicroStrategy, Inc. Setting up ODBC 329

Creating DSNs
After you install an ODBC driver, you can define one or more
data sources for it. The DSN should provide a unique
description of the data, for example,
Payroll_Project_Metadata or Payroll_Warehouse.
The DSN is the name for a pointer used by a client application

to find and connect to a data source. Multiple DSNs can point
to the same data source and one DSN can be used by different
applications.
If you are using a MicroStrategy-branded ODBC, you can

create DSN by using
the MicroStrategy Connectivity Configuration Wizard
the MicroStrategy Configuration Wizard
If you are using a MicroStrategy ODBC Driver that is not

MicroStrategy-branded, then you can use the Microsoft
ODBC Administrator to create a DSN.
Note the following:

It is strongly recommended you use the MicroStrategy
Connectivity Configuration Wizard when creating a
new DSN. Use the ODBC Administrator only if you
intend to use a driver that is not
MicroStrategy-branded.

lists only the MicroStrategy-branded ODBC drivers.
However, this guide also provides information on how
to install drivers from other vendors with
MicroStrategy. For more information, Creating DSNs
for individual ODBC drivers, page 338.
If you choose to create DSNs using the Microsoft
ODBC Administrator, they must be system DSNs.
Otherwise, MicroStrategy interfaces will not recognize
them.
330 Creating DSNs 2005 MicroStrategy, Inc.

Using the MicroStrategy Connectivity Configuration Wizard

The MicroStrategy Connectivity Configuration Wizard is a
tool designed specifically to configure connectivity to data
sources using the MicroStrategy-branded drivers.
Accessing the MicroStrategy Connectivity

You can access the MicroStrategy Connectivity Configuration

Wizard in the following ways.
To access from the Procedure
Tools menu on On the Windows Start menu, point to Programs,

Windows then MicroStrategy, then Tools, and then select
Connectivity Configuration Wizard. The
MicroStrategy Connectivity Configuration Wizard
opens.
Configuration 1 On the Windows Start menu, point to

Wizard on Windows Programs, then MicroStrategy, and then
select Configuration Wizard.
2 On the Configuration Wizard Welcome page,
select the Metadata Repository and
Statistics Tables option and click Next.
3 On the Metadata Repository Configuration
Tasks page, select the Create Metadata
Tables check box and click Next.
4 On the ODBC Data Source Name for
Metadata Repository page, click New. The
MicroStrategy Connectivity Configuration
Wizard opens.
Target directory on 1 From a UNIX console window, browse to

UINX <HOME_PATH> where <HOME_PATH> is the
directory you specified as the Home
Directory during installation. Navigate to the
folder bin.
2 Type ./mstrconnectwiz, then press
ENTER. The MicroStrategy Connectivity
Configuration Wizard opens.
2005 MicroStrategy, Inc. Creating DSNs 331

To access from the Procedure
Configuration 1 From a UNIX console window, browse to

Wizard on UNIX <HOME_PATH> where <HOME_PATH> is the
directory you specified as the Home
Directory during installation. Navigate to the
folder bin.
2 Type ./mstrcfgwiz, then press ENTER.
3 On the Configuration Wizard Welcome page,
select the Metadata Repository and
Statistics Tables option and click Next.
4 On the Metadata Repository Configuration
Tasks page, select the Create Metadata
Tables check box and click Next.
5 On the ODBC Data Source Name for
Metadata Repository page, click New. The
MicroStrategy Connectivity Configuration
Wizard opens.
MicroStrategy 1 Open the MicroStrategy Control Center.

Control Center on 2 From the Tools menu, select Connectivity
UINX Configuration Wizard. The MicroStrategy
Connectivity Configuration Wizard opens.
To add a DSN using the Connectivity Configuration Wizard
1 If you are adding a DSN on Windows, perform the

following steps:
Log in to the system as an administrator.
Open the Connectivity Configuration Wizard. The

Welcome page of the MicroStrategy Connectivity
If you are adding a DSN on UNIX, perform the following
steps:

<HOME_PATH> where <HOME_PATH> is the
directory you specified as the home directory during
installation.
Browse to the folder bin and type

./mstrconnectwiz, then press ENTER. The
Welcome page of the MicroStrategy Connectivity

2 Click Next. The following list of database drivers is

displayed for Windows:
MicroStrategy ODBC driver for Oracle Wire Protocol
MicroStrategy ODBC Driver for Oracle 8
This option is only available for users who use

pre-7.1.4 versions. SQL*Net or Net*8 Oracle
connectivity software is required (this driver does
not use wire protocol technology.)
MicroStrategy ODBC Driver for Informix 7 and 8
MicroStrategy ODBC Driver for Informix 9.x

MicroStrategy ODBC Driver for Sybase Adaptive
Server 12 and above
Microsoft SQL Server
Other Relational Databases
IfNext,
you select Other Relational Databases and click
you see a list of all other drivers installed on
your machine, excluding the MicroStrategy and the
Microsoft SQL Server drivers.
The following list of database drivers is displayed for

UNIX:
MicroStrategy ODBC Driver for DB2 UDB

MicroStrategy ODBC Driver for DB2 UDB for iSeries
(formerly known as AS400)
MicroStrategy ODBC Driver for Sybase ASE 12.x
MicroStrategy ODBC Driver for Microsoft SQL Server
3 Select a database driver for which to create a data source

and click Next. The Driver Details page opens.

There are only few databases can contain metadata

repositories. For details, refer to the readme file.
Only DSNs created to connect to these databases
can be used to connect to the metadata
repositories.
4 Enter the information in the appropriate boxes for

connecting with the selected database driver.
The information to enter varies depending on the

database platform you selected. For more
information, Creating DSNs for individual ODBC
drivers, page 338.
5 Click Test to verify the connection.
6 Enter a username and password to connect to the

database. Then click Connect to verify the connection. If
the test is performed successfully, the connection with the
database is established.
7 Click Close, then Finish to create the new DSN.
Ifname
you already have an existing DSN with the same
as the one you provided, a message box
appears. Select Yes to make sure the DSN points to
the location you are expecting. This will overwrite
the existing DSN. Select No to save the DSN with a
different name.
Repeat the above steps to create as many DSNs as you

require. At a minimum, create one for your metadata (MD)
and one for your warehouse (WH).

If a DSN does not already exist in your empty metadata
repository or the repository installed with MicroStrategy, you
can add or create a new one by using the MicroStrategy

To create a DSN using the Configuration Wizard
1 If you are creating a DSN on Windows, then perform the

following step:

then MicroStrategy, and then choose Configuration
Wizard. The Configuration Wizard opens.
If you are creating a DSN on UNIX, then perform the

following steps:

<HOME_PATH>, where <HOME_PATH> is the
directory you specified as the Home Directory during
installation.
Browse to the folder bin and type ./mstrcfgwiz,

then press ENTER. The Configuration Wizard opens.
2 In the Configuration Wizard, select the Metadata

Repository and Statistics Tables option and click Next.
3 Select the Create Metadata Tables check box and click

Next.
4 On the ODBC Data Source Name for Metadata Repository

page, click New. The MicroStrategy Connectivity
Configuration Wizard page opens that lists the
MicroStrategy-supported database drivers to create
DSNs.
5 Choose a database platform for which to create a DSN and

click Next.
There are only few databases can contain metadata

repositories. For details, refer to the Readme file.
Only DSNs created to connect to these databases
can be used to connect to the metadata
repositories.
6 Enter specific server-related information into the Driver

Setup dialog box, depending on which MicroStrategy
ODBC driver you selected.

The specific information to enter varies depending

on the ODBC driver you selected. For more
information, Creating DSNs for individual ODBC
drivers, page 338.
7 Click Test to verify that the information is correct.

Provide a valid user name and password. Click Connect.
8 A message box indicating a successful connection is

displayed. Click OK, then Close.
9 Click Finish. You return to the ODBC Data Source Name

for Metadata Repository page of the Configuration
Wizard.
10 Select the DSN from the ODBC Data Source Name

drop-down list.
IfODBC
the DSN is not listed, check if the MicroStrategy
driver used to create the DSN is one of the
certified metadata repository vendors and try
creating the DSN again.
11 Enter your User Name and Password.
12 If the same database is being used for the statistics tables,

select the Use the same information for statistics check
box.
13 Click Next. The Configuration Wizard then connects to

the database.
Using the Microsoft ODBC Administrator

The Microsoft ODBC Administrator manages database
drivers and data sources. The ODBC Administrator utility is
used to create a log with which to trace calls to data sources
and to view, create, and edit DSNs. The utility is available
from Microsoft and is usually included with the purchase of
an ODBC driver. It is also available with the Windows 2000
and 2003 operating systems.
Note the following:

It is strongly recommended you use the MicroStrategy

ODBC DSN Creator when creating a new DSN. Use the
ODBC Administrator only if you intend to use a
non-MicroStrategy driver.
If you choose to create DSNs using the Microsoft

ODBC Administrator, they must be system DSNs.
Otherwise, MicroStrategy interfaces will not recognize
them.
To add a DSN using the ODBC administrator
1 Log in to the machine as an administrator. This gives you

the ability to create a system-wide DSN, rather than a
user-specific DSN.
2 Open the ODBC Data Source Administrator dialog box

in one of the following ways, depending on your operating
system.
Platform Procedure
Windows On the Windows Start menu, point to Settings, and then

98, and ME choose Control Panel. In the Control Panel dialog box,
select Data Sources (ODBC).
Windows On the Windows Start menu, point to Settings, and then

2000 and choose Control Panel. In the Control Panel dialog box,
2003 double-click Administrative Tools, and then Data
Sources (ODBC).
On computers running previous versions of Microsoft

Windows, the ODBC Administrator icon is named
32-bit ODBC or simply ODBC.
3 Click the System DSN tab. A list displays all the existing
system data sources and their associated drivers.
ToDrivers
view all the installed ODBC drivers, click the
tab.
4 Click Add to open the Create New Data Source dialog box.
5 Select the desired driver and click Finish. A driver setup

dialog box is displayed.

ItODBC
is recommended that you select a MicroStrategy
driver. Starting with MicroStrategy in their
names, these drivers were installed when you installed
the MicroStrategy application on the computer.
6 Enter the information in the appropriate boxes to create a

data source for the selected database driver.
The information to enter varies depending on the

database platform you selected. For more information,
Chapter B, Creating DSNs for individual ODBC
drivers of this appendix.
7 Click OK to create a new DSN.
Creating DSNs for individual ODBC drivers

This section provides information on creating a DSN for each
of the following MicroStrategy-branded 32-bit ODBC drivers:
MicroStrategy ODBC Driver for Oracle Wire Protocol for

Windows and UNIX
MicroStrategy ODBC Driver for Informix Wire Protocol
for Windows and UNIX
MicroStrategy ODBC Driver for Sybase ASE Wire Protocol

for Windows and UNIX
MicroStrategy ODBC Driver for SQL Server Wire Protocol

for UNIX
MicroStrategy ODBC Driver for Informix 8 for Windows
MicroStrategy ODBC Driver for DB2 Wire Protocol (DB2

UDB) for UNIX
MicroStrategy ODBC Driver for DB2 Wire Protocol

(iSeries) for UNIX

The following table lists the information required for each

type of ODBC driver when you create a new DSN using the
MicroStrategy ODBC DSN Creator.
Platform For ODBC Driver... Enter Attribute Information...
Windows and UNIX MicroStrategy ODBC driver Data source name

for Oracle Wire Protocol Host name
SID (MicroStrategy default is ORCL)
Port number (in most cases, 1521)
Windows and UNIX MicroStrategy ODBC Driver Data source name

for Informix Wire Protocol Server name
Host name
Port number (1526 in most cases)
Database name
Windows and UNIX MicroStrategy ODBC Driver Data source name

for Sybase ASE Wire Network address
Protocol Database name
Enable Unicode support
UNIX MicroStrategy ODBC Driver Data source name

for Microsoft SQL Server Server name
Wire Protocol Database name
Windows MicroStrategy ODBC Driver Data source name

for Informix 8 Database name
Server name
Host name
Service name
Protocol name

for DB2 Wire Protocol (DB2 Host name
UDB) Database name
Port number (in most cases, 50000)
for DB2 Wire Protocol IP address
(iSeries) Collection
Location
Isolation Level
Package owner
TCP port (446 in most cases)

lists only the MicroStrategy-branded ODBC drivers.
However, this section also provides information on
how to install drivers from other vendors with
MicroStrategy.

The following ODBC drivers for Windows and UNIX

from other vendors are described as well:
MicroStrategy ODBC Driver for DB2 Wire Protocol

(DB2 UDB) for UNIX
ODBC Driver for Red Brick (UNIX)
ODBC Driver for Sybase Adaptive Server IQ

(UNIX)
ODBC Driver for Teradata (UNIX)
ODBC Driver for Informix XPS (UNIX)
ODBC Driver for Netezza (UNIX)
The following subsections provide more details on the

attribute information for each individual driver.
MicroStrategy ODBC Driver for Oracle Wire

Protocol for Windows and UNIX
The following information is required for setting up the

driver connection for MicroStrategy ODBC driver for Oracle
Wire Protocol:
Data Source Name: Type a string that identifies this

Oracle data source configuration in the system
information. Examples are Accounting and Oracle-Serv1.
Host Name: Type the name of the Oracle server to be

accessed.
SID: Type the Oracle System Identifier that refers to the
instance of Oracle running on the server. In most cases,
the value of default SID is ORCL.
Port Number: Type the port number of your Oracle

listener. Check with your database administrator for the
correct number. In most cases, the default port number is
1521.

MicroStrategy ODBC Driver for Informix Wire


driver connection for the MicroStrategy ODBC Driver for
Informix Wire Protocol:

Informix data source configuration in the system
information, such as Accounting or Informix-Serv1.
Server Name: Type the client connection string
designating the server and database to be accessed. The
required information varies depending on the client
driver you are using.
Host Name: Type the name of the machine on which the

Informix server resides. This name is assigned by the
system or database administrator.
Port Number: Type the port number of the Informix

server listener. In most cases, the default port number is
1526.
Database Name: Type the name of the database to which

you want to connect by default. This is assigned by the
database administrator.
MicroStrategy ODBC Driver for Sybase ASE Wire


driver connection for the MicroStrategy ODBC driver for
Sybase ASE Wire Protocol:
Sybase ASE data source configuration in the system
information. Examples include Accounting or
Sys10-Serv1.

Network Address: Type the network address in the

format <server name or IP address>, <port
number>. For example, if your network supports named
servers, you can specify an address, such as Sybaseserver,
5000. You can also specify the IP address directly, such as
199.226.224.34, 5000. Contact your system administrator
for the server name or IP address.

Enable Unicode support (UTF8): Select this check box if

the database is Unicode. This option is only available
through the Connectivity Configuration Wizard.
MicroStrategy ODBC Driver for SQL Server Wire

Protocol for UNIX

driver connection for the Microsoft SQL Server Wire Protocol
driver:
Data Source Name: Enter the string to be used by an

ODBC application when it requests a connection to the
data source. An example is Personnel.
Server Name: Enter the name of a SQL Server on your

network in the format <server name or IP
address>, <port number>. For example, if your
network supports named servers, you can specify an
address, such as sql-server-2000, 1433. You can also
specify the IP address directly, such as 199.226.224.34,
1433. Contact your system administrator for the server
name or IP address.
to connect by default. This is assigned by the database
administrator.

MicroStrategy ODBC Driver for Informix 8 for

Windows
Note the following:

Informix Client Software (Client-SDK) must be
installed before you create a DSN. However, this
software is not included in the MicroStrategy product
suite installation. It must be obtained through the
database vendor or a third party.
MicroStrategy metadata repository does not support

this platform.

driver connection for the MicroStrategy ODBC Driver for
Informix 8:

Informix data source configuration in the system
information, for example, Accounting or Informix-Serv1.

Server Name: Select the client connection string

designating the server and database to be accessed. The
required information varies depending on the client
driver you use.
Host Name: Type the name of the machine on which the

Informix server resides.
Service Name: Type the name of the service as it appears
on the host machine. This service name is assigned by the
system administrator. The name you specify is displayed
in the Informix Server Options dialog box.
Protocol Type: Select the protocol used to communicate

with the server.

MicroStrategy ODBC Driver for DB2 Wire

Protocol (DB2 UDB) for UNIX

driver connection for MicroStrategy ODBC Driver for DB2
Wire Protocol when running against DB2 UDB:
Data Source Name: Type a string that identifies this DB2

UDB data source configuration in the system information.
Examples are Accounting and DB2-Serv1.
Host Name: Type the name of the DB2 UDB server to be
accessed.

you want to connect by default. This name is assigned by
the database administrator.
Port Number: Type the port number of your DB2 UDB

server listener. Check with your database administrator
for the correct number. In most cases, the default port
number is 50000.
MicroStrategy ODBC Driver for DB2 Wire

Protocol (iSeries) for UNIX

driver connection for MicroStrategy ODBC Driver for DB2
Wire Protocol when running against iSeries (formerly known
as AS400):
Data Source Name: Type a string that identifies this DB2
UDB iSeries data source configuration in the system
information. Examples are Accounting and DB2-Serv1.
IP Address: Type the IP Address of the machine where
the catalog tables are stored. This can be a numeric
address or a host name.
Collection: Type the name that identifies a logical group

of database objects. On AS/400, it is also the current
schema.
Location: Type the DB2 location name, which is the name

defined during the local DB2 installation.

Isolation Level: Select the method by which locks are

acquired and released by the system.
Package Owner: Type the AuthID assigned to the

package.
TCP Port: Type the port number assigned to the DB2

DRDA listener process on the server host machine. Check
with your database administrator for the correct number.
In most cases, the default port number is 446.
Other relational databases for Windows
If you use other databases, refer to the database-specific

documentation for information on required settings.
Standard settings are supported by MicroStrategy for most
relational databases. If you plan to use Teradata, some
special settings are required. See the following subsection.
Teradata
IfMicroStrategy,
you intend to use Teradata, which is supported by
you need to
pre-install the NCR ODBC Driver for Teradata
RDBMS. Otherwise, you will not see Teradata in the
drivers list for Other Relational Databases when using
the MicroStrategy ODBC DSN Creator.
ensure that Teradata DSNs are set to Run in Quiet

Mode.
If you use Teradata, the following settings are required for

setting up the driver connection.
In the Teradata ODBC Driver Options dialog box, click

Options to set the following required options:
Session Mode: Select Teradata as the session mode to

apply for the duration of the session.
Date Time Format: Set this value to AAA format so the

ODBC driver handles the Dates, Time, and Timestamps as
ANSI-compatible strings. The ANSI-compatible strings
are only available with the V2R3 or later databases.

Disable Parsing: Select this check box to disable parsing

of SQL statements by the ODBC driver.
For information on other options, refer to the online help

by clicking Help.
ODBC Driver for Red Brick (UNIX)
ODBC driver for Red Brick is not a MicroStrategy branded

driver. The following steps show how to configure ODBC
driver for Red Brick.
To create an ODBC Driver for Red Brick
1 Install ODBC Driver for Red Brick for the correct

operating system. For information on installation, refer to
the Installation and Configuration Guide for UNIX and
Linux provided by IBM.
Make sure you install the Red Brick Client

Products (version 6.2 and higher) so that they can
be accessed by the appropriate users. You need the
following components:
RISQL Entry Tool, RISQL Reporter, and Client TMU
Red Brick ODBCLib (SDK)
Red Brick ODBC Driver
The directory where Red Brick Client Products are

installed should always be accessible to
2 Configure the environment for ODBC Driver for Red

Brick.
i In a UNIX console window, browse to <HOME_PATH>,

the Home Directory during installation. Browse to the
folder env.

ii Add Write privileges to the ODBC.sh file by entering

chmod u+w ODBC.sh
iii Edit the ODBC.sh file and add the location of the
directory where the Red Brick Client Products are
installed to the RB_CONFIG environment variable.
An example of this command follows:
RB_CONFIG=<RED_BRICK_INSTALL_PATH>
iv Save the ODBC.sh file and remove Write privileges

from the file by entering the following command:
chmod a-w ODBC.sh
3 Configure a DSN for ODBC Driver for Red Brick.
i In a UNIX console window, browse to <HOME_PATH>

the Home Directory during installation.
ii Open the odbc.ini.example file and find the

section that starts with [RED_BRICK_62] if you are
using Red Brick 6.2 or [RED_BRICK_63] if you are
using Red Brick 6.3. Copy the section into the
odbc.ini file.
iii Edit the DSN parameters SERVER and DATABASE, and

modify the value of RB_CONFIG with the location of
the directory where the Red Brick Client Products are
installed.
iv Save the odbc.ini file.

For details on these DSN parameters, refer to the product
documentation provided directly by the database vendor.


(UNIX)
ODBC driver for Sybase Adaptive Server IQ is not a

MicroStrategy branded driver. The following steps show how
to configure ODBC driver for Sybase Adaptive Server IQ.
To configure ODBC Driver for Sybase Adaptive Server IQ
1 Install ODBC Driver for Sybase Adaptive Server IQ for the

correct operating system. For information on installation,
refer to the Installation and Configuration Guide
provided by Sybase.
The directory where ODBC driver for Sybase

Adaptive Server IQ is installed should always be
accessible to MicroStrategy Intelligence Server.
2 Configure the environment for ODBC Driver for Sybase

Adaptive Server IQ.

folder env.

chmod u+w ODBC.sh
directory where the ODBC Driver for Sybase Adaptive
Server IQ is installed to the ASDIR environment
variable.
ASDIR=<SYBASE_ASIQ_INSTALL_PATH>

chmod a-w ODBC.sh

3 Configure the DSN for ODBC Driver for Sybase Adaptive

Server IQ.
i In a UNIX console window, browse to

<HOME_PATH> where <HOME_PATH> is the
installation.

section that starts with [SYBASEIQ]. Copy the section
into the odbc.ini file.
iii Edit the DSN parameters EngineName,

DatabaseName and CommLinks, and modify the value
of ASDIR with the location of the directory where the
ODBC Driver for Sybase Adaptive Server IQ is
installed.
For details on these DSN parameters, refer to the

product documentation provided directly by the
database vendor.
ODBC Driver for Teradata (UNIX)
ODBC driver for Teradata is not a MicroStrategy-branded

driver. The following steps show how to configure the ODBC
driver for Teradata.
To configure the ODBC Driver for Teradata
1 Install the ODBC Driver for Teradata for the correct

the product documentation provided directly by the
database vendor.
The directory where the ODBC driver for Teradata

is installed should always be accessible to

2 Configure the environment for the ODBC driver for

Teradata.

folder env.

chmod u+w ODBC.sh
directory where the ODBC Driver for Teradata is
installed to the MSTR_TERADATA_PATH environment
variable.
MSTR_TERADATA_PATH=
<TERADATA_INSTALL_PATH>

chmod a-w ODBC.sh
v For AIX only, you need to also specify the Teradata

GSS library installation in the ODBC.sh. To do this,
make the following changes to the MicroStrategy
Teradata GSS path. Set this path, in the
MSTR_TERADATA_GSS_PATH parameter, to the
location of the local Teradata GSS library installation:
MSTR_TERADATA_GSS_PATH='<MSTR_TERADATA_G
SS_PATH>
if [ "${MSTR_TERADATA_GSS_PATH}" !=
'<MSTR_TERADATA_GSS_PATH>' ];
then mstr_append_path LIBPATH

"${MSTR_TERADATA_GSS_PATH:?}"/-- export
LIBPATH

3 Configure the DSN for ODBC driver for Teradata.

the Home Directory during installation.

section that starts with [TERADATA_SERVER]. Copy
that section into the odbc.ini file.
iii Edit the DSN parameters DBCName, DatabaseName

and DefaultDatabase, and modify the value of
MSTR_TERADATA_PATH with the location of the
directory where the ODBC Driver for Teradata is
installed.
iv In the odbc.ini file, copy the DSN to the [ODBC

Data Sources] section with the driver description.
This ensures the DSN name appears in the tools.
v Save the odbc.ini file.

database vendor.
ODBC Driver for Informix XPS (UNIX)
ODBC driver for Informix XPS is not a MicroStrategy

branded driver. The following steps show how to configure
ODBC driver for Informix XPS.
To configure ODBC Driver for Informix XPS
1 The MicroStrategy ODBC Driver for Informix XPS is

already installed in the <INSTALL_PATH>/lib32
directory.

However, the Informix Client Software Developers Kit

(CSDK) must be installed before you create a DSN. This
software is not included in the MicroStrategy product
suite installation and must be obtained through the
database vendor or a third party. For information on
installation, refer to the product documentation provided
directly by the database vendor.
The directory where CSDK is installed should always

be accessible to MicroStrategy Intelligence Server.
2 Configure the environment for ODBC Driver for Informix

XPS.

folder env.

chmod u+w ODBC.sh
iii Edit the ODBC.sh file and make the following

changes:
Add the location of the directory where the

Informix Client Software Developer's Kit (CSDK) is
installed to the INFORMIXDIR environment
variable.
INFORMIXDIR=<CSDK_INSTALL_PATH>
Add the name of the INFORMIX Server to the

INFORMIXSERVER environment variable. This
value is chosen from the list in
<INFORMIXDIR>/etc/sqlhosts.

INFORMIXSERVER=<INFORMIX_SERVER_NAME>


chmod a-w ODBC.sh
3 Configure the DSN for ODBC Driver for Informix XPS.

the home directory during installation.

section that starts with [INFORMIX_XPS]. Copy the
section into the odbc.ini file.
iii Edit the DSN parameters Database, HostName,

ServerName and Service.

database vendor.
ODBC Driver for Netezza (UNIX)
ODBC driver for Netezza is not a MicroStrategy branded

driver. The following steps show how to configure ODBC
driver for Netezza.
To configure ODBC driver for Netezza
1 Install the ODBC Driver for Netezza for the correct

the product documentation provided directly by the
database vendor.
The directory where Netezza is installed should always

be accessible to MicroStrategy Intelligence Server.
2 Configure the DSN for ODBC driver for Netezza.

You must modify odbcinst.ini file and odbc.ini

file to create the DSN for Netezza. The
odbcinst.ini file is used only by the Netezza ODBC
driver.
To modify the odbcinst.ini file

ii Edit the odbcinst.ini file and replace the three

instances of netezza_odbc_install_dir with the
location of the directory where the Netezza ODBC
Driver is installed. An example of this is as follows:
If the original path is:
Driver =
/netezza_odbc_install_dir/lib/libnzsqlod
bc3.so,
then the modified path will be:
Driver =
/usr/odbc/netezza221sp5/lib/libnzsqlodbc
3.so.
iii Save the odbcinst.ini file.
To modify the odbc.ini file
i In a UNIX console window, browse to the directory

where you installed the Netezza ODBC driver;
netezza_odbc_install_dir. Browse to lib
directory.
ii Browse to .odbc.ini.sample file to access the

example DSN provided in this file. The example DSN
provided in this file is as follows:
[NZSQL]
Driver =
/usr/local/nz/lib/libnzsqlodbc.so
Description = NetezzaSQL ODBC
Servername = 127.0.0.1

Port = 5480
Database = system
Username = admin
Password = password
CancelAsFreeStmt = false
CommLog = false
Ksqo = false
Lie = false
Optimizer = false
Parse = false
PreFetch = 256
Protocol = 7.0
ReadOnly = false
ShowSystemTables = false
Socket = 16384
DateFormat = 1
TranslationDLL =
TranslationName =
TranslationOption =
iii Copy the contents exactly as they are provided in the

.odbc.ini.sample file.
iv In a UNIX console window, browse to the

<HOME_PATH>, where <HOME_PATH> is the directory
you specified as the home directory during
installation.
v Browse to MicroStrategy odbc.ini file.

vi Paste the contents copied from the example DSN from

the Netezza .odbc.ini.example file. You should
paste the contents of the DSN exactly as they appear in
the example file.
vii Make the following changes to the copied sample file:
Modify the driver location to match the location of the

installed Netezza ODBC Driver;
netezza_odbc_install_dir.
Change the driver name from libnzsqlodbc.so to
libnzsqlodbc3.so.
Change the Database, Servername, Username, and

Password to match the information for your database.
Following is an example of an updated DSN in the

MicroStrategy odbc.ini file:
[NZSQL]
Driver =
/usr/odbc/netezza221sp5/lib/libnzsqlodbc
3.so
Description = NetezzaSQL ODBC
Servername = 10.15.225.30
Port = 5480
Database = testDB
Username = tester01
Password = tester01
CancelAsFreeStmt = false
CommLog = false
Ksqo = false
Lie = false
Optimizer = false
Parse = false
PreFetch = 256

Protocol = 7.0
ReadOnly = false
ShowSystemTables = false
Socket = 16384
DateFormat = 1
TranslationDLL =
TranslationName =
TranslationOption =
viii Save the odbc.ini file.

database vendor.
Testing the ODBC connectivity

ODBC connectivity is one of two layers of connectivity that
are listed in the next table, along with the associated
connectivity testing programs. Connectivity should be tested
from the bottom upthe network layer first and then the
ODBC layer.
Layer Test with
ODBC driver Test ODBC

mstrtestodbc
Network Simple Network Layer Testing Tool
TCP/IP Ping, PING.EXE, for TCP/IP
The test method described above reflects the situation

when the ODBC driver and the database network
software are bundled. If they are not bundled, they
must be configured and tested separately, using
database-specific tools.
2005 MicroStrategy, Inc. Testing the ODBC connectivity 357

Using the ODBC test tool
For Windows, the ODBC test utility TSTODBC2.EXE (a 32-bit

application) was created by MicroStrategy and is installed
with MicroStrategy Desktop in C:\Program
Files\Common Files\MicroStrategy.
For UNIX, the ODBC test utility mstrtestodbc was created

by MicroStrategy and is installed with MicroStrategy for
UNIX in the target directory.
Before you use the ODBC test tool, test the network layer with
the network layer utility, PING.EXE. Consult your operating
system or network system documentation for details.
To use the ODBC test tool
1 If you want to use the ODBC test tool on Windows,

perform the following step:
then MicroStrategy, then Tools, and then choose
ODBC Test Tools.
Alternatively, run TSTODBC2.EXE to open the

MicroStrategy ODBC Test Tool.
If you want to use the ODBC test tool on UNIX, perform
the following steps:
In a UNIX console window, browse to <HOME_PATH>,
Browse to the folder bin and type ./mstrtestodbc,

then press ENTER.
2 From the Session menu, select Open Connection or click

the Connect icon on the toolbar. The GetDSN dialog box
opens. The connection interface varies depending on the
destination database.
3 Select the DSN for a data source, such as data warehouse

or metadata.
358 Testing the ODBC connectivity 2005 MicroStrategy, Inc.

4 Enter the appropriate username and password.
5 Click Connect. After your connection is opened, the

connection string is displayed in the MicroStrategy ODBC
Test Tool dialog box at the bottom. Your cursor is inserted
automatically in the SQL Statement window.
6 In the SQL Statement window, type a SQL query such as
select count (*) from Table
where Table is a system-defined table, for example,

SYSOBJECTS for Microsoft SQL Server or a
MicroStrategy-created table such as DSSMDSYSPROP in
the MicroStrategy metadata.
7 From the Queries menu, select Execute Query. A table of

data from the database is displayed in the Query Result
window.
8 From the Session menu, select Close Connection to

close the database connection.
9 From the File menu, select Exit to close the MicroStrategy

TestODBC Tool dialog box.
The Test ODBC utility includes many useful features not

discussed here. Refer to the ODBC Test Tool Online Help for
details.
Parameters from ODBC.ini

The ODBC.ini file is the configuration file that stores the
definitions for all the ODBC DSNs. These ODBC DSNs are
defined by specifying values for certain DSN parameters. This
file is activated by the environment variable of ODBCINI, and
is required by all ODBC applications. By default, the
odbc.ini file is installed in <HOME_PATH>, where
<HOME_PATH> is the directory you specified as the Home
Directory during installation. It contains the definitions for
the following MicroStrategy branded ODBC drivers:
2005 MicroStrategy, Inc. Parameters from ODBC.ini 359

MicroStrategy ODBC Driver for DB2 UDB
MicroStrategy ODBC Driver for DB2 UDB for iSeries

(formerly AS400)
MicroStrategy ODBC Driver for Sybase ASE 12.x
MicroStrategy ODBC Driver for Microsoft SQL Server
This section lists the descriptions of the DSN parameters for

all MicroStrategy branded ODBC drivers.
MicroStrategy supports ODBC drivers from other

vendors that you can install separately. This involves
manually defining the DSN parameters in the
odbc.ini file.
This section also describes the DSN parameters for the

following ODBC drivers from other vendors:
ODBC Driver for Red Brick
ODBC Driver for Teradata
ODBC Driver for Informix XPS
ODBC Driver for Netezza
360 Parameters from ODBC.ini 2005 MicroStrategy, Inc.

Oracle Wire Protocol

Parameter Description
Driver Location where the ODBC driver is installed.

Description Optional long description of a data source name.
LogonID Default logon ID used to connect to your database.
Password Default password used to connect to your database.

HostName Name of IP address of the server to which you want to connect.
PortNumber Port number of your Oracle listener.
SID Oracle System Identifier that refers to the instance of Oracle running on the
server.
CatalogOptions {0 | 1}. Determines whether the result column REMARKS for the catalog
functions SQLTables and SQLColumns, and COLUMN_DEF for the catalog
function SQLColumns, have meaning for Oracle.
0: Default.
To obtain the actual default value, set CO=1.
ProcedureRetResults {0 | 1}. Determines whether the driver returns result sets from stored
procedure functions.
0: (Default) The driver does not return result sets from stored procedures.
1: The driver returns result sets from stored procedures. When set to 1
and you execute a stored procedure that does not return result sets, you
will incur a small performance penalty.
EnableDescribeParam {0 | 1}. Determines whether the ODBC API function SQLDescribeParam is

enabled, which causes all parameters to be described with a
SQL_VARCHAR data type.
Set to 1 when using Microsoft Remote Data Objects (RDO) to access
data.
EnableStaticCursorsForL {0 | 1}. Determines whether the driver supports long columns when using a
ongData static cursor. Using this parameter causes a performance penalty at the time
of execution when reading long data.
You must set this parameter to 1 if you want to persist a result set that
contains LONG data into an XML data file.
ApplicationUsingThreads {0 | 1}. Ensures that the driver works with multi-threaded applications.
1: (Default) The driver is thread-safe.
When using the driver with single-threaded applications, set this option to
0 to avoid additional processing required for ODBC thread-safety
standards.
AlternateServers A list of alternate database servers to which the driver tries to connect if the
primary database server is unavailable. Specifying a value for this option
enables connection failover for the driver.

DB2 Wire Protocol


Description Optional descriptive comment for this data source definition.
LogonID Default logon ID used to connect to your database. The LogonID value is
your UNIX user ID.
Password Password used to connect to the database.

DB2AppCodePage Setting that must be invoked if the automatic codepage conversion fails. (The
driver determines the codepage of the ODBC application and DB2 database
and converts accordingly.)
Default setting: -1, which is equivalent to disabled.
ServerCharSet Setting that must be invoked if the automatic codepage conversion fails. (The
driver determines the codepage of the DB2 database and converts
accordingly.)
Default setting: -1, which is equivalent to disabled.
IpAddress IP (Internet Protocol) address of the machine where the catalog tables are
stored. Enter the address using the machines numeric address (for example,
123.456.78.90) or type the address name.
If you enter an address name, the driver must find this name, with the
correct address assignment, in the HOSTS file on the workstation or in a
DNS server.
Database Name of the database to which you want to connect.
Collection Name that identifies a logical group of database objects. On AS/400, it is also
the current Schema. These objects include the DataDirect Connect DB2 Wire
Protocol driver for ODBC packages. This attribute is valid only if you are
connecting to DB2 on OS/390 or AS/400.
Location Path that specifies the DB2 location name. Use the name defined during the
local DB2 installation. This attribute is valid and required only if you are
connecting to DB2 on OS/390 or AS/400.
TcpPort Port number that is assigned to the DB2 DRDA listener process on the server
host machine. Specify this ports numeric address or its name.
5179 is the default port address.
If you specify a port name, the driver must find this name, with the correct
port assignment, in the SERVICES file on the workstation.
Package Name of the package that the driver uses to process dynamic SQL for
applications that use this data source definition.
Action Refers to the binding of packages. Two options can be used:

ADD: Creates a new package if one does not already exist. If one does
exist, the bind process will fail.
REPLACE: Replaces the existing package with a new package, or
creates a new package if one does not yet exist.

QueryBlockSize Number of rows the driver retrieves when fetching from the server. This is not
the number of rows returned to the user.
Default: 8 rows.
CharSubTypeType {SYSTEM_DEFAULT | DBCS | MBCS | DBCS}. Determines which character

set is specified.
SYSTEM_DEFAULT: The system default value of the DB2 location to
which you are binding is used.
SBCS: A single-byte character set is used.
MBCS: A mixed-byte character set is used.
DBCS: A double-byte character set is used.
ConversationType {SINGLE_BYTE | MIXED_BYTE}. Determines the type of system code used

by DB2. This value indicates the byte format of character data in the
command area of a DB2 packets sent from the remote host.
SINGLE_BYTE: The remote host uses a single-byte system code page
(as specified in DSNZPARMS on DB2/MVS, for example.)
MIXED_BYTE: The remote host is DB2 3.1 and DSNZPARMS specifies a
double-byte code page where single-byte and mixed-byte values are not
allowed.
CloseConversation {DEALLOC | AT_COMMIT}. Determines when the DB2 Wire Protocol driver
closes an LU 6.2 conversation.
DEALLOC: (Default) The conversation is closed when the client
application terminates. Use this value unless you are tuning the system
for OLTP applications, or you want to prevent an application from using
host resources when a client leaves it idle for an extended period of time.
AT_COMMIT: The conversation is closed after the client application
executes a COMMIT statement.
UserBufferSize The size in kilobytes of the bulk packet that the DB2 Wire Protocol driver
uses to download data from the host. Valid values are 1 to 63. For most
environments, the default value of 32 is sufficient; however, adjusting the
value can optimize some client applications as follows:
For client applications that frequently download large amounts of data, a
large buffer size can improve response time.
For client applications that perform brief online transactions, a small buffer
will maximize memory on the machine where the DB2 Wire Protocol
driver is installed.
MaximumClients An integer that specifies the maximum number of concurrent client sessions
that the DB2 Wire Protocol driver can carry. If the driver is used with an
application server, select a value that will accommodate the number of users
who will simultaneously access the host system through the DB2 Wire
Protocol driver. In a client configuration, use a small value to reduce the DB2
Wire Protocol drivers memory requirements. The default is 10.
GrantExecute {0 | 1}. Indicates whether or not to grant privileges on the package you are
creating.
0: Privileges are not granted.
1: (Default) Privileges are granted.

GrantAuthid Determines to whom Execute privileges are granted.

Default value: Grant Execute privileges on the package to PUBLIC.
OEMANSI {0 | 1}. 1 translates data from the IBM PC character set to the ANSI character
set.
DecimalDelimiter {COMMA | PERIOD}. Determines how the decimal point is represented. This
is a required field if the DBRM file contains a decimal literal that does not
match the host systems default value.
COMMA: The decimal point is represented with a comma. For example,
3,17.
PERIOD: The decimal point is represented with a period. For example,
3.17.
DecimalPrecision {15 | 31}. Determines the number of places following the decimal point that
will be calculated.
15: (Default) 15 decimal places are calculated.
31: 31 decimal places are calculated.
StringDelimiter {SINGLE_QUOTE | DOUBLE_QUOTE}. Specifies the type of quotation

marks (single or double) used to represent constant string values that are
referenced by the SQL in the DBRM. This option must match the option used
to delimit the literal strings referenced by your embedded SQL.
IsolationLevel {ALL | CHANGE | CURSOR_STABILITY | NO_COMMIT |

REPEATABLE_READ}. Method by which locks are acquired and released by
the system. Valid values are:
ALL: Prevents any other process from accessing data that your
application has read or modified. All read or modified data is locked until
the end of the transaction.
CHANGE: Allows other processes to read from the database. Only
modified data is locked until the end of the transaction.
CURSOR_STABILITY: Allows other processes to change a row that your
application read if the cursor is not on the row that you want to change.
Prevents other processes from changing records that your application has
changed until your program commits them or terminates. Prevents your
program from reading a modified record that has not been committed by
another process.
NO_COMMIT: Allows your program to read modified records even if they
have not been committed by another person. On AS/400, this is the only
isolation level that works for collections that do not have journaling
enabled.
REPEATABLE_READ: Prevents other processes from changing records
that are read or changed by your application (including phantom records)
until your program commits them or terminates. Prevents the application
from reading modified records that have not been committed by another
process. If your program opens the same query during a single unit of
work under this isolation level, the results table will be identical to the
previous table; however, it can contain updates made by your program.

ResourceRelease {DEALLOCATION | COMMIT}. Specifies the release of database resources.

DEALLOCATION: Database resources are released when the connection
is terminated.
COMMIT: Database resources are released after a commit and provide a
high level of concurrency.
DynamicSections Number of statements that the DB2 Wire Protocol driver package can
prepare for a single user.
Trace Generates a trace file in the applications directory. The trace file name is
packet.xxx, where xxx is an incremental number starting with 000.
WithHold {0 | 1}. Value that specifies the cursor behavior for the application used with
this data source.
1: (Default) DB2 leaves all cursors open after a commit or rollback.
(SQLGetInfo( ) returns SQL_CB_PRESERVE for
SQL_COMMIT_CURSOR_BEHAVIOR.)
0: DB2 closes all open cursors after a commit or rollback. (SQLGetInfo( )
returns SQL_CB_DELETE.)

Informix Wire Protocol


Database Name of the database to which you want to connect by default.

HostName Name of the machine on which the Informix server resides.
PortNumber Port number of the server listener.
ServerName Name of the Informix server as it appears in the sqlhosts file.
EnableInsertCursors {0 | 1}. Determines whether the driver can use Insert cursors during inserts
governed by parameters. Using Insert cursors improves performance during
multiple Insert operations using the same statement.
0: The driver does not use Insert cursors.
1: (Default) The driver uses Insert cursors. This option enables insert data
to be buffered in memory before being written to disk.
GetDBListFromInformix {0 | 1}. Determines whether the driver requests the database list to be
returned from the Informix server or from the database list that the user
entered at driver setup.
0: The driver uses the list that was entered by the user at driver setup.
1: (Default) The driver requests the database list from the Informix server.
CancelDetectInterval Allows long-running queries in threaded applications to be canceled if the

application issues a SQLCancel. The value you select determines how often
(in seconds) the driver checks whether a query has been canceled using
SQLCancel. If the driver determines that SQLCancel has been issued, the
query is canceled. For example, if you select 5, for every pending query the
driver checks every five seconds to see whether the application has canceled
execution of the query using SQLCancel.
The default is 0, which means that queries are not canceled even if a
SQLCancel is issued.
TrimBlankFromIndexNa Specifies whether the leading space should be trimmed from a

me system-generated index name. This option is provided to address problems
with applications that cannot process a leading space in index names.
ApplicationUsingThreads Determines whether the driver works with single-threaded or multi-threaded

applications.

Sybase Wire Protocol


Database Default database to use.

NetworkAddress Specifies which network protocol is chosen under Network Library Name and
the Sybase server.
EnableDescribeParam Specifies whether to enable the SQLDescribeParam function, which allows

an application to describe parameters in SQL statements and in stored
procedure calls.
EnableQuotedIdentifiers Specifies whether to allow support of quoted identifiers.
OptimizePrepare {0 | 1 | 2 | 3}. Determines whether stored procedures are created on the

server for calls to SQLPrepare.
0: Stored procedures are created for every call to SQLPrepare. This
setting can result in decreased performance when processing statements
that do not contain parameters.
1: (Default) The driver creates stored procedures only if the statement
contains parameters. Otherwise, the statement is cached and run directly
at the time of SQLExecute.
2: Stored procedures are never created. The driver caches the statement,
executes it directly at the time of SQLExecute, and reports any syntax or
similar errors at the time of SQLExecute.
3: Stored procedures are never created. This is identical to value 2 except
that any syntax or similar errors are returned at the time of SQLPrepare
instead of SQLExecute. Use this setting only if you must have syntax
errors reported at the time of SQLPrepare.
RaiseErrorPositionBehav {0 | 1}. Specifies when the error is returned and where the cursor is
ior positioned when RaiseError is encountered.
0: (Default) RaiseError is handled separately from surrounding
statements. The error is returned when RaiseError is processed via
SQLExecute, SQLExecDirect, or SQLMoreResults. The result set is
empty.
1: (MS-compatible) RaiseError is handled with the next statement. The
error is returned when the next statement is processed; the cursor is
positioned on the first row of the subsequent result set. This may result in
multiple RaiseErrors being returned on a single Execute.

SelectMethod {0 | 1}. Determines whether database cursors are used for Select statements.
0: (Default) Database cursors are used. In some cases, performance
degradation can occur when performing large numbers of sequential
Select statements because of the amount of overhead associated with
creating database cursors.
1: Select statements are run directly without using database cursors, and
the data source is limited to one active statement.
ApplicationUsingThreads Determines whether the driver works with single-threaded or multi-threaded

applications.
SQL Server Wire Protocol

Description Optional description of the data source.
Database Default database to use.
Address The network address of the server running SQL Server. Used only if the
Server keyword does not specify the network name of a server running SQL
Server. Address is usually the network name of the server, but can be other
names such as a pipe, or a TCP/IP port and socket address. For example, on
TCP/IP: 199.199.199.5, 1433 or MYSVR, 1433.
QuotedId {yes | no}. Determines whether QUOTED_IDENTIFIERS is set ON or OFF for

the connection.
Yes: QUOTED_IDENTIFIERS is set ON for the connection, and SQL
Server uses the SQL-92 rules regarding the use of quotation marks in
SQL statements.
No: QUOTED_IDENTIFIERS is set OFF for the connection, and SQL
Server uses the legacy Transact_SQL rules regarding the use of
quotation marks in SQL statements.
AnsiNPW {yes | no}. Determines whether ANSI-defined behaviors are exposed.

Yes: The driver uses ANSI-defined behaviors for handling NULL
comparisons, character data padding, warnings, and NULL
concatenation. If the driver appears to be truncating trailing blank spaces,
this parameter should be set to No.
No: ANSI-defined behaviors are not exposed.

ODBC
Trace Specifies whether tracing is on or off.

TraceFile File where tracing is logged.
TraceDll Location of the ODBC trace shared lib\dll.
InstallDir Location where ODBC drivers are installed.

IANAAppCodePage Used with the transliteration system. The code page that you specify must be
the same as the code page used by your application. The driver on UNIX
determines the value of the applications code page by checking for an
IANAAppCodePage value, in the following order:
In the connection string.
In the DataSource section of the system file (odbc.ini).
In the ODBC section of the system file (odbc.ini).
If no IANAAppCodePage value is found, the driver uses the default value of 4
(ISO 8859-1 Latin-1.)
Note: The IANAAppCodePage connection string parameter replaces the
AppCodePage connection string parameter in earlier versions of Connect for
ODBC. The drivers are backwardly compatible with the AppCodePage
parameter, but you must now use the IANAAppCodePage parameter. In this
case, option three would be used. If the driver cannot find the setting in the
two previous places, it uses the one in the ODBC section.
UseCursorLib This setting is not used in UNIX. It specifies which CursorLibrary is used, the
one in the driver or the one that comes with the ODBC components. On the
UNIX platform, there is no ODBC Manager CursorLibrary available, which
means that the driver CursorLibrary is always used.
Red Brick 6.x

SERVER Host name and port number of the server that runs the database.
RB_CONFIG Location where the ODBC driver is installed.
DATABASE Name of the database to connect
UID Default logon ID used to connect to your database.
PWD Default password used to connect to your database.

SybaseIQ

UID Default logon ID used to connect to your database.
PWD Default password used to connect to your database.

EngineName Name of the database Server to connect.
DatabaseName Name of the database to connect.
CommLinks Host name and port number of the server that runs the database. The value
should be as follows: tcpip(host=X.X.X.X;port=x)
AutoStop Specifies whether the database should continue running after connections
are disconnected.
Teradata-Server
DBCName Identifies the host by name (alias) or IP Address.
SessionMode Specifies the mode for sessions. Values can be Teradata, ANSI, or System
Default.
NoScan {Yes | No}. Specifies whether parsing of SQL statements is enabled or

disabled for the driver.
Yes: The parser in the driver is bypassed and the SQL statement is sent
directly to Teradata. This option should not be set when the SQL
statement contains ODBC-specific syntax. Setting this option while using
ODBC-specific syntax in the SQL statement results in Teradata Database
reporting errors.
No: The parser in the driver is not bypassed and SQL statements are sent
to the parser.
RunInQuietMode Specifies whether the driver should display standard message boxes on the
screen.

StCheckLevel Provides enhanced ODBC state checking to detect SQLState 24000 (invalid
cursor state error) according to the requirements from the ODBC SDK.
0: (Default) No additional state checking is performed. Provides backward
compatibility. The ODBC driver will not generate error 24000 when an
ODBC function such as SQLExecute, SQLExecDirect, or an ODBC
catalog function generates a result set (open cursor state) and another
function that generates a result set is called before the first results were
fetched or freed.
1: Driver generates SQLState 24000 error if an application is in an open
cursor state and one of the following functions is called: SQLColumns,
SQLColumnPrivileges, SQLExecDirect, SQLExecute, SQLForeignKeys,
SQLGetTypeInfo, SQLPrepare, SQLPrimaryKeys,
SQLProcedureColumns, SQLProcedures, SQLSpecialColumns,
SQLStatistics, SQLTablePrivileges, or SQLTables.
2: Driver generates SQLSTate 24000 error if an application is not in an
open cursor state and SQLColAttributes, SQLDescribeCol, or SQLFetch
is called.
CharacterSet Specifies the default character set for the session. The default character set
for Single Byte Character Sets (SBCS) is ASCII. For DBCS character sets,
the value in the KanjiFormat option should match the character set name
specified for this option. Entries for this option include:
blank (default for KanjiFormat)
ASCII (for SBCS)
UTF8
SCHEBCDIC935_2IJ, TCHEBCKIC937_3IB
TCHBIG5_1RO, SDTCHBIG5_3RO
SCHEGB2312_1TO, SDSCHGB2312_2TO
SDSCHEBCDIC935_6IJ, SDTCHEBCDIC937_7IB
SDKANJIEBCDIC5026_4IG, SDKANJIEBCDIC5035_4IH
SDKANJIEUC_1U3, SDKANJISJIS_1S3
HANGULEBCKIC933_1II, HANGULKSC5601_2R4
SDHANGULEBCKIC933_5II, SDHANGULKSC5601_4R4
KANJISJIS_OS, KANJIEUC_OU
DateTimeFormat Specifies whether the ODBC driver should handle DATEs, TIMEs, and
TIMESTAMPs as integer values or ANSI-compatible strings.
III specifies that all three should be handled as integer values.
AAA specifies that they should be handled as ANSI-compatible strings.
LastUser Remembers the connection for the last user.

Username Default logon ID used to connect to your database.
Database Name of the database to connect.
DefaultDatabase Name of the default database.

Informix XPS

ApplicationUsingThreads {0 | 1}. Ensures that the driver works with multi-threaded applications.
(AUT) 1: (Default) The driver is thread-safe.
0: Use this setting when using the driver with single-threaded applications,
to avoid additional processing required for ODBC thread-safety
standards.
CancelDetectInterval Value in seconds that determines how often the driver checks whether a
(CDI) query has been canceled using SQLCancel. If the driver determines that
SQLCancel has been issued, the query is canceled. This parameter
determines whether long-running queries in threaded applications are
canceled if the application issues a SQLCancel. For example, if
CancelDetectInterval is set to 5, then for every pending request the driver
checks every five seconds to see whether the application has canceled
execution of the query using SQLCancel.
0: (Default) Queries are not canceled even if SQLCancel is issued.
CursorBehavior (CB) {0 | 1}. Determines whether cursors will be preserved or closed at the end of
each transaction.
0: (Default) Cursors are closed at the end of each transaction.
1: Cursors are held at the current position when the transaction ends. This
value may impact the performance of your database operations.
Database (DB) Name of the database to which you want to connect.
EnableInsertCursors {0 | 1}. Determines whether the driver can use Insert cursors during inserts
(EIC) governed by parameters.
0: The driver does not use Insert cursors.
1: (Default) The drier uses Insert cursors. Using Insert cursors improves
performance during multiple Insert operations using the same statement.
This option enables insert data to be buffered in memory before being
written to disk.
Note: The driver does not currently support SQLDescribeParam so there is
no support for parameterized queries.
GetDBListFromInformix {0 | 1}. Determines whether the driver requests the database list to be
(GDBLFI) returned from the Informix server or from the database list that the user
entered at driver setup.
0: The driver uses the list that was entered by the user at driver setup.
1: (Default) The driver requests the database list from the Informix server.
HostName (HOST) Name of the machine on which the Informix server resides.
LogonID (UID) Default logon ID used to connect to your database.
Password (PWD) Default password used to connect to your database.

Protocol (PRO) {olsocspx | olsoctcp | onsocspx | onsoctcp | seipcpip | sesocspx | sesoctcp |

ontlitcp}. Specifies the protocol used to communicate with the server. You can
specify one or more values; separate the names with commas.
Note: For Solaris, this value must be ontlitcp.
ServerName (SRVR) Name of the server running the Informix database.
Service (SERV) Name of the service as it appears on the host machine. This service is
assigned by the system administrator.
TrimBlankFromIndexNa {0 | 1}. Determines whether the leading space should be trimmed from a
me (TBFIN) system-generated index name. This option is provided to address problems
with applications that cannot process a leading space in index names.
0: The driver does not trim the space.
1: (Default) The driver trims the leading space.
UseDefaultLogin (UDL) {0 | 1}. Determines from where the logon information is read.
0: (Default) Logon information is read from the system information, the
connection string, or the Logon to Informix dialog box.
1: The Logon ID and Password are read directly from the Informix registry.


C
ADVANCED WAREHOUSE
C.
CATALOG USAGE
Introduction
This appendix discusses the Warehouse Catalog usage and

settings. The Warehouse Catalog queries the data warehouse
and lists the tables and columns that exist in it. From this list,
you can select the tables to add to your project. Every project
can have a unique set of warehouse tables. Adding tables
through MicroStrategy Project Builder is useful only when
you are creating a project for the first time, as later, adding
tables in the project through Project Builder can become a
cumbersome process. Warehouse Catalog is good for bulk
addition and for maintaining an existing project.
You can do the following in the Warehouse Catalog:
add, change, or remove tables to and from a project
see the table structure
see the row count of a single or multiple tables
see the sample records of a table
specify table prefix to a table

C Advanced Warehouse Catalog Usage Basic Setup Guide
specify a secondary database instance
name space settings
For information about adding and removing tables in

a project, see Adding tables using the Warehouse
Catalog, page 122 in Chapter 6, Creating a Project.
Warehouse Catalog usage

This section covers the following topics:
What should I know before I use the Warehouse Catalog?
Accessing Warehouse Catalog
Warehouse Catalog layout
Warehouse Catalog settings
Ignore table name space settings
Troubleshooting Warehouse Catalog
What should I know before I use the Warehouse Catalog?

Before you begin using the Warehouse catalog, you need to be
familiar with
your schema, so you know what columns are facts and
what information is in each table
how to create a project
376 Warehouse Catalog usage 2005 MicroStrategy, Inc.

Basic Setup Guide Advanced Warehouse Catalog Usage C
Accessing Warehouse Catalog
To access the Warehouse Catalog
1 On the Windows Start menu, point to Programs, then to

MicroStrategy, then Desktop, and then choose Desktop.
2 Connect to a project source using your user ID and

password.
3 Select a project and then from the Schema menu, choose

Warehouse Catalog. The Warehouse Catalog opens after
it retrieves the table information from the warehouse
database.
Warehouse Catalog layout

The Warehouse Catalog allows you to view tables that have
been included in the project, as well as those that are still
available in the warehouse.
As you make changes to the tables in the warehouse, you need

to periodically load the updates into the Warehouse Catalog.
You can update it by selecting Read the Warehouse Catalog
from the Actions menu.
The Warehouse Catalog has the following sections:

Tables available in the warehouse: Displays tables that
are located in the warehouse, but have not been included
in the project. You can add tables to the project by
double-clicking the tables or by selecting the tables and
then clicking >.
Tables being used in the project: Displays tables that

have been selected to be part of the project. You can
remove tables from the project by double-clicking the
tables or by selecting the tables and then clicking <.
You can add or remove all the tables from one section
to the other by clicking << and >> buttons.
2005 MicroStrategy, Inc. Warehouse Catalog usage 377

Warehouse Catalog has the following menu options.
Menu Description
File
Save Saves the current settings and status of the
Warehouse Catalog.
Exit Exits the Warehouse Catalog.
Tools
View Partitions Displays the list of tables referred to by the
selected partition mapping table in the Table
Partitions dialog box. This option is enabled
when a partition mapping table is selected.
Table Structure Displays the structure of a table selected in

the Warehouse Catalog.
Calculate Table Row Calculates the number of rows in the

Count selected tables.
Table Prefix Allows you to add or remove a table prefix for

the selected table.
Table Database Allows you to assign or update a database

Instances instance for the project. For more
information, see Catalog tab, page 381 of
this appendix.
Import Prefix Allows you to import the prefixes from the

warehouse table name space.
Options Allows you to specify various settings for the

Warehouse Catalog such as changing the
database instance, changing or assigning
default table prefixes and structures,
automatic mapping, row calculation, and so
on.
Actions
Read the Warehouse Allows you to update and reflect the changes
Catalog done to tables in the warehouse.
Help Displays MicroStrategy help options
Some of these options are also available through toolbar

buttons and through right-click menus for quick access.

Viewing table structure
The steps to view the table structure are as follows:
To view the structure of a table
1 Right-click any table and choose Table Structure from

the shortcut menu. You can also select Table Structure
from the Tools menu. The table structure of the selected
table is displayed in the dialog box.
The dialog box displays the columns available in the selected

table and the data type of each column. You can also click
Update Structure to reflect any recent changes done to that
table.
When the data type of one or more columns is modified, you

get a warning message of this change, which provides the
following options:
Click OK to apply the change to this column in all the

tables it appears.
Click Cancel to undo all data type changes. This action

results in no changes being applied to any tables or
columns.
The warning message appears only if you have selected

the Display a warning if the columns data types are
modified when updating the table structure option
in the Warehouse Catalog Options dialog box. This
option is selected by default.
Updating table structure
Whenever the structure of the warehouse table changes, for

example, when you add, delete, or rename a column in a table
associated with a project, you have to update the table
structure in the MicroStrategy Architect for the changes to
reflect in the MicroStrategy system.

To update the structure of a table
1 From the Schema menu, select Warehouse Catalog.
2 In the Tables being used in the project list, right-click the

table that has changed and select Update Structure.
3 If the data type of one or more columns is modified, you

will get a warning message of this change. Verify the
changes from the information dialog box that opens and
click OK to apply the change to this column to all the
tables in which it appears.
4 Click Save and Close to close the Warehouse Catalog

dialog box. If no object definitions have changed, the
warehouse structure gets updated completely with the
Update Structure command. For example, this would
apply if you rename a column in the table and the column
is not being used in any fact expression.
5 If any of the object definitions have changed, the table

structure is only partially updated with the Update
Structure command. Then, you have to manually update
the schema objects that depend on the outdated structure.
For example, if you rename a column in a table, you have
to manually update the facts that use this column. The
procedure for manually updating the fact is as follows:
Right-click the fact and select Edit. The Fact Editor

opens. Select the fact expression and click Modify. The
Modify Fact Expression dialog box opens. Select the
source table from which the fact has been created,
from the list of source tables. Edit the fact expression
and click OK. Click Save and Close to save the
changes and close the Fact Editor.
From the Schema menu, select Update Schema. The
Schema Update dialog box opens. Click Update.
6 Open the Warehouse Catalog dialog box again and repeat

steps 1-3 to update the table structure.
7 Click Save and Close to save the changes and close the
Warehouse Catalog dialog box.

Viewing sample data
To view sample data from a table, right-click a table and

choose Show Sample Data from the shortcut menu. You can
also select Show Sample Data from the Tools menu. The
first 100 rows of the table are returned as sample data in the
Values dialog box.
To refresh the table data, click Reload table values.
Warehouse Catalog settings

From the Warehouse Catalog, you can choose to view the
Warehouse Catalog Options dialog box. You can access the
Warehouse Catalog Options dialog box by choosing Options
from the Tools menu or by clicking Options in the toolbar.
From this dialog box you can specify various settings for the
Warehouse Catalog, such as changing the database instance,
changing or assigning default table prefixes and structures,
automatic mapping, row calculation, and so on.
The following tabs are available:
Catalog tab
View tab
Schema tab
Catalog tab
The Catalog tab is divided into the following sections:

Warehouse Database Instance for the Project: From

this section you can select the desired database instance
to use for the project. If the desired database instance
does not appear in the Database Instance box, or if it does
but needs to be modified, you can select from the
following:
Click Edit to open the General tab of the Database

Instances dialog box to modify the selected database
instance.
Click New to open the Database Instance Wizard
where you can create a new database instance.
Refer to the MicroStrategy System Administration

Guide for more information on either of these dialog
boxes.

Catalog Read Method: In this section you can customize

the SQL to read the Warehouse Catalog for every platform
except Microsoft Access. Clicking Settings allows you to
directly edit the SQL statements that are used to retrieve
the list of available tables from the Warehouse Catalog
and the columns for the selected tables. The default SQL
retrieves a DISTINCT list of tables and columns from all
users. You could restrict the information returned, for
example, by specifying certain conditions and table
owners. You can also select the following check boxes:
Count the number of rows for all tables when

reading the database catalog: Select this option if
you want to control whether or not the Warehouse
Catalog should get the number of rows each table has
when loading. This option is helpful when you want to
identify fact tables and aggregation tables. If
performance is more important than obtaining the
row count, do not select this option as it will have an
effect on performance. By default this option is
selected when you open the Warehouse Catalog for the
first time.
Ignore current table name space when reading

from the database catalog and update using new
table name space: This option allows you to switch
between warehouses found in different database name
spaces. You can also control if you wish to obtain the
size of each table in the Warehouse Catalog. For more
information, see Ignore table name space settings,
page 385 of this appendix. By default this option is
selected.
Display a warning if the column data types are

modified when updating the table structure: Select
this option if you want to be warned when the data
type for a column stored in the project is different
from the one read from the warehouse catalog. The
check for the data type change is only performed when
updating a tables structure. By default this option is
selected.
Automatically update information for all Partition
Mapping tables when reading the database
catalog: Select this option to read the latest
information for the partition mapping tables (PMTs)
currently present in the project. This setting should be

unchecked when the number of PMTs in the project is

such that reading their structure is causing
performance problems when opening Warehouse
Catalog. By default this option is selected.
Catalog Read: From this section you can select the

catalog read mode:
Automatic: The default selection, the Automatic

catalog read mode sets the catalog tables to be read as
soon as the catalog browser is loaded.
Manual: The Manual catalog read mode sets the

catalog tables to be read only when the read catalog
action is selected.
View tab
From the View tab you can choose to:
Display table prefixes in the main dialog: Select this to

display all prefixes in table names, including new tables
added to the project. By default this option is selected.
Automatically define prefixes for all tables that are

added to this project: This setting enables/disables the
following options:
Set a prefix based on the warehouse table name

space or owner (import prefix): When this option is
selected the Warehouse Catalog reads the name space
for each table being added, creates a prefix having the
same text as the name space, and associates it with the
table being added.
Set a default prefix: Select this to add a prefix to

tables when they are added to a project. This box is
only active when the database supports prefixes. You
can specify the default prefix in the Default prefix box
from the list or create a new table prefix by clicking
Modify prefix list.
Modify prefix list: Click to open the Table Prefixes
dialog box, which allows you create a new table prefix.
In the Table Prefixes dialog box, select a prefix and
click OK to create a new prefix.

Or,
Click Add to create a new prefix in the New Table

Prefix box. You can also delete table prefixes from the
Table Prefixes dialog box.
Display the number of rows per table: Select to show or

hide the values calculated for the number of rows for the
tables. Shows or hides the column where the row counts
are displayed in the Warehouse Catalog. By default, this
option is selected.
Display the name space for each table (if applicable):

Select to show or hide the owner or table name space
where the table is located in the warehouse. By default,
this option is selected.
Schema tab
From the Schema tab, you can select the options that guide
the Warehouse Catalog to map schema objects to new tables
and calculate logical sizes for new tables.
To map schema objects automatically to new tables, select

Map schema objects to new tables automatically. Objects
in the schema automatically map to tables you add to the
project. If you do not want to map the schema objects, select
Do not map schema objects to the new tables.
To calculate logical table sizes automatically, select Calculate

the logical table sizes automatically. Each time you add
new tables to the project, their logical sizes are calculated for
you. If you do not want to calculate the table logical sizes,
select Do not calculate table logical sizes.
Ignore table name space settings

This setting helps you move a project from one warehouse to
another. It is a common practice to establish a secondary
warehouse with less information than the primary warehouse
for development and testing. Before going into production,
you change the project to point to the primary warehouse.

Most database management systems (Oracle, DB2, and

others) support the concept of a table name space, which is a
way of organizing database tables into different storage
spaces. This method allows you to repeat the same table
name in different table name spaces. For instance, you can
have LU_STORE in table name space dbo and another table
LU_STORE in another table name space called admin. You
now have two tables dbo.LU_STORE and admin.LU_STORE.
The table name space provides an extra piece of information
that uniquely identifies the table.
When you add tables to a project, the Warehouse Catalog

saves information to the appropriate table name space. This
may cause a problem when you migrate from a warehouse
that resides in a certain table name space to another
warehouse in a different table name space. The problem is
that the Warehouse Catalog interprets the table as already in
the project and not found in the new warehouse. This is
because the Warehouse Catalog is looking for a table named
dbo.LU_STORE, and in the new production warehouse the
table is actually stored as admin.LU_STORE. This is a
common occurrence.
To solve this problem, select the check box option Ignore

current table name space when reading from the
database catalog and update using new table name
space. You can find it in the Warehouse Catalog Options
dialog box under the Catalog Read options section. If you
select this option, the Warehouse Catalog ignores the current
table name space when it reads the catalog information.
Thus, the Warehouse Catalog recognizes the two tables as the
same table and saves the new table name space information.
This setting allows you to migrate much more easily between
warehouses. If the check box is not selected, the Warehouse
Catalog defaults to identifying the table by both table name
space and table name.
Troubleshooting Warehouse Catalog

You may encounter the following messages while using the
Warehouse Catalog:
Tables missing

Columns data type changed
Columns missing
Tables missing
This happens when one or more tables already in the project

are removed from the data warehouse. Two cases can be
seen:
When the Warehouse Catalog is starting and retrieving

the table information from the data warehouse and it
detects that one or more tables already in the project are
missing, it displays an error message which gives you the
following options:
Leave the Table in the project: This leaves

everything as is in the project metadata. However the
definition in the project may be inconsistent with the
real physical structure in the warehouse. This can
result in SQL errors when running reports that need
data from a missing table.
Remove the table from the project. In this case, the

Warehouse Catalog does not check for any
dependencies until you save the changes. If there are
any dependencies, they are presented to you, and you
have the option to proceed or cancel the operation.
When the Warehouse Catalog tries to update the structure
of a table that is missing in the warehouse, a message is
shown which explains that the table structure update
cannot proceed because the table was not found in the
warehouse. In this case, no changes occur and the original
table structure remains intact.
Columns data type changed
When the table structure is updated for one or more tables

and if the column data types are changed, you get a warning
message showing the table name, column name, the original
data type, and the new data type. You can click Cancel at any
time to undo all data type changes. This results in no changes
being applied to the tables and columns.

Columns missing
Missing columns are detected when Update Structure is

performed. If this happens, the Warehouse Catalog checks for
the following:
Column is not mapped to any schema object: If this is
the case, then no error message is shown.
Column is mapped to a schema object: If this is the

case, then a message is displayed that gives details on
objects, which are mapped to the missing column and the
update structure operation is canceled. You are asked to
remove the mapping before continuing with the update
structure and original table structure is restored.

D
ADVANCED HARDWARE
D.
CONSIDERATIONS
Introduction
This appendix provides additional hardware-related

configuration information to help you determine
requirements for a variety of production system sizes.
Small MicroStrategy production system

configuration
For small MicroStrategy platform implementations,
customer specifications usually require support for 0-150
cross-product users.
It is assumed that these users are contacting the

MicroStrategy system from their own client computers. If
these users are power users, they are most likely interacting
with the system through the MicroStrategy Desktop client.
MicroStrategy Web users interact with the system through
their Web browsers.
2005 MicroStrategy, Inc. Small MicroStrategy production system configuration

D Advanced Hardware Considerations Installation and Configuration Guide
MicroStrategy Narrowcast Server proactively monitors the

data warehouse and generates and delivers personalized
e-mail messages when required; users are not required to
interact with the Narrowcast Server to receive Narrowcast
Server messages.
For a small MicroStrategy production system, we suggest

installing the products across two separate servers with the
following characteristics.
Minimum Minimum
Minimum
Suggested Storage Space
Server # Recommended
Memory Required for
Processor
(RAM) Installation
1 512 MB 1 GB Quad Pentium 500

MHz or equivalent
2 512 MB 1 GB Dual or Quad Pentium

500 MHz
The optimal placement of the MicroStrategy products on

these two servers with regard to system performance depends
on the product usage of the particular application in question.
For instance, for production applications in which users
primarily use MicroStrategy Web during the day, and for
which Narrowcast Server is used at night to generate
personalized messages, it makes sense to place Narrowcast
Server and Web on the same computer. In this configuration,
computer processing power is used during the day for
generating Web reports and at night for generating
personalized Narrowcast Server messages.
For general cross-product usage, the following configuration

is suggested. The particular requirements for every product
with regard to product-specific software requirements and
additional product-specific requirements, for example
database requirements, can be found in later sections of this
appendix.
On server 1 install:
MicroStrategy Desktop
MicroStrategy Architect
390 Small MicroStrategy production system configuration 2005 MicroStrategy, Inc.

Basic Setup Guide Advanced Hardware Considerations D
On server 2 install:
MicroStrategy Web
As needed, install the following products on client machines:
MicroStrategy Architect
MicroStrategy platform can function with all the products on

a single computer, with products on separate computers, or
even with individual products spread across several
computers to support large numbers of users. In this manner,
you can grow and reconfigure your MicroStrategy platform
configuration as your business intelligence requirements
increase. The MicroStrategy platform allows you to start with
a small configuration and, as your production system
requirements grow, you can transition to a medium
configuration and then to a large configuration.
Product user suggestions for small

configurations
The following table shows the user breakdown for the typical
small configuration.
Suggested Number of User

MicroStrategy Product
Licenses
MicroStrategy Intelligence Server 1-150 Named Users
Architect 1-2 Named Users
Desktop 1-10 Named Users
Administrator 1-2 Named Users
SDK 1-2 Named Users
MicroStrategy Web
2005 MicroStrategy, Inc. Small MicroStrategy production system configuration


Licenses
Analyst 10-100 Named Users
Reporter 10-100 Named Users
Viewer 10-100 Named Users

MicroStrategy Narrowcast Server 10-150 Named Users
The particular breakdown of named users within your small

production configuration depends on your specific business
intelligence system requirements. Our product offerings and
named user categories are based on the analysis of customer
use case requirements at thousands of implemented business
intelligence solutions over the last ten years. Take care to
allocate appropriate user types to your users based on the
depth of functionality and information analysis they require.
MicroStrategy Architect, MicroStrategy Administrator, and

MicroStrategy SDK named users should be allocated to
system administrators and customization developers.
MicroStrategy Desktop named users should be allocated to
power users who require the ability to create MicroStrategy
business intelligence objects (such as metrics, filters,
prompts, reports, documents, and custom groups).
MicroStrategy Web named users should be designated as
analyst, reporter, or viewer users based on the level of
interactive Web-based data analysis they require.
Not all users require the ability to analyze information

interactively. In fact, the majority of users only require access
to certain information or reports on a periodic (or alert)
basis. We refer to these users as stable requirement users,
because their information requirements are predictable. For
example, a store manager would only like to receive
information on store performance in relation to other stores
in the district at the end of every week, in addition to an alert
page if any items in his store have less than the predicted
demand that week. In this example the information the store
manager would like to receive is standardized and
predictable, and the store manager would not get much use
out of the ability to interactively analyze information through
MicroStrategy Web. In static user cases, we suggest the
allocation of MicroStrategy Web Viewer named user licenses
or MicroStrategy Narrowcast Server named user licenses.
392 Small MicroStrategy production system configuration 2005 MicroStrategy, Inc.

MicroStrategy Narrowcast Server named users should be

allocated for users who require proactive information
delivery. Narrowcast Server proactively generates and
delivers personalized messages to anyone at any time,
through e-mail, enterprise Web portals, wireless devices, and
voice. You can use MicroStrategy Narrowcast Server to
monitor the database for predefined alert conditions, and
should an alert condition occur (for instance, sales down
more than 10%), it will generate messages and deliver them
to the appropriate end users. MicroStrategy Narrowcast
Server can fulfill the information requirements of large
numbers of users with relatively little impact on the
performance of the system as a whole.
Medium MicroStrategy production system

configuration
For medium MicroStrategy platform implementations,
customer specifications usually require support for 150-1000
interactive users and up to 2000 Narrowcast Server users. To
support this number of users, we suggest installing the
products across four separate servers with the characteristics
stated in the table below.
Minimum Minimum
Minimum
Memory Required for
Processor
(RAM) Installation
1 1 GB 1 GB Quad Pentium 500

MHz or equivalent

MHz or equivalent

MHz or equivalent

MHz or equivalent
2005 MicroStrategy, Inc. Medium MicroStrategy production system configuration

For the medium configuration it is suggested that each

MicroStrategy server software product be installed on a
separate computer. This allows each server product the
exclusive usage of the available CPUs.
The following diagram shows an example of a medium

MicroStrategy configuration.
While this arrangement allows for high system performance

for 150-2000 users, it does not make use of MicroStrategy's
dynamic clustering and failover capabilities. All of the
components of the MicroStrategy platform have been
designed to function in a clustered environment. This allows
single products to use more than one computer to process job
requests. This also allows for failover, so that if a computer
fails, the system automatically recognizes this computer
failure and reallocates current and future jobs to other
computers. This functionality allows your organization to
depend on your MicroStrategy business intelligence system
for mission critical applications that must be available at all
times.
394 Medium MicroStrategy production system configuration 2005 MicroStrategy, Inc.

There are several ways to implement clustering and failover

features within a medium-sized MicroStrategy configuration.
Instead of running on four quad computers, you could use
eight dual computers, with two computers designated for
each server product shown in the diagram above. You could
also have a situation where MicroStrategy Intelligence Server
and MicroStrategy Web each are installed on two quad
processor computers, and MicroStrategy Narrowcast Server
is installed on another quad processor computer. In this
configuration the system is then configured to cluster across
the three quad processor computers.
Named product user suggestions for medium

configuration
A medium MicroStrategy production configuration typically

exhibits a user breakdown as shown in the following table.

Licenses
MicroStrategy Intelligence Server 150-2000 Named Users
Architect 2-10 Named Users
Desktop 2-100 Named Users
Administrator 2-10 Named Users
SDK 2-10 Named Users
MicroStrategy Web
Analyst 100-1000 Named Users
Reporter 100-1000 Named Users
Viewer 100-1000 Named Users

MicroStrategy Narrowcast Server 150-2000 Named Users
It is important to note that MicroStrategy Narrowcast Server

individually running on a quad processor computer should be
able to support substantially more than 2000 users. For
instance, MicroStrategy Narrowcast Server can generate and
deliver 2500 messages in less than 10 minutes.
2005 MicroStrategy, Inc. Medium MicroStrategy production system configuration

Large MicroStrategy production system

configuration
For large MicroStrategy platform implementations, customer
specifications usually require support for substantially more
than 2000 cross-product users. To support this number of
users, we suggest installing the MicroStrategy server
products across multiple clustered computers.
Minimum Minimum
Minimum
Memory Required for
Processor
(RAM) Installation
All servers in a 2 GB 2 GB Quad Pentium 650

large MHz or equivalent
MicroStrategy
production
system
For a large configuration, it is suggested that each

MicroStrategy server software product be installed on a
cluster of server computers. In this configuration each of the
MicroStrategy server products balances the load of jobs to be
processed across the servers that compose the cluster. Each
of the MicroStrategy server products also dynamically
reallocates on-going jobs if a computer in the cluster goes
down.
The following diagram depicts one example of a large

MicroStrategy production configuration. The specific
configuration of your large production MicroStrategy system
depends on your business intelligence system requirements.
By the time your requirements grow to where a large-scale
configuration is necessary, your organization should be able
to determine exactly how many computers are required to
support your system needs.
396 Large MicroStrategy production system configuration 2005 MicroStrategy, Inc.

The following diagram shows an example of a large

MicroStrategy system.
As business intelligence solutions grow to meet the

information needs of large numbers of users, the proportion
of users that can be supported through MicroStrategy Web
Viewer and MicroStrategy Narrowcast Server increases
dramatically. This is because the ratio of stable requirement
users to ad-hoc or interactive information users increases as
the number of end users goes up, and the ratio of concurrent
users to total users goes down as the number of total users
goes up. In other words, the CPU resources required per user
go down as the total number of users goes up. This
phenomenon benefits your organization since it dramatically
decreases the average cost per user of your business
intelligence system.
2005 MicroStrategy, Inc. Large MicroStrategy production system configuration

398 Large MicroStrategy production system configuration 2005 MicroStrategy, Inc.

E
E. TROUBLESHOOTING
Introduction
This appendix provides information on common problems

that you might encounter while installing and configuring
MicroStrategy for UNIX, Linux, and Windows Operating
System.
Installing MicroStrategy for UNIX

Some of the problems you can encounter while installing
MicroStrategy for UNIX are listed below with steps to resolve
them.
For information on application server-specific issues

and general troubleshooting for MicroStrategy Web
Universal, refer to the MicroStrategy Web Universal
release notes.
2005 MicroStrategy, Inc. Installing MicroStrategy for UNIX 399

E Troubleshooting Installation and Configuration Guide
Mounting CD-ROMs
Before you can install MicroStrategy on either the Solaris or
AIX operating system, you need to mount the CD-ROM. The
procedure for each is included below, along with instructions
to unmount the CD-ROM
Mounting and unmounting the CD-ROM on

Solaris
Follow the steps below to mount the CD-ROM on UNIX.
To mount the CD-ROM on Solaris
1 Enter the command su and the root password at the

command prompt, or log in as root to become the
superuser (su). The command prompt changes to the
pound sign (#).
2 If the /cdrom directory does not already exist, enter
# mkdir /cdrom
3 If the /cdrom/cdrom0 directory is empty because the

CD-ROM was not mounted, or if File Manager did not
open a window displaying the contents of the CD-ROM,
verify that the vold daemon is running by entering the
following:
# ps -e | grep vold | grep -v grep
The vold process manages the CD-ROM device and

performs the mounting.
4 If vold is running, the system displays the process

identification number of vold. If the system does not
display anything, stop and start the daemon by entering
# /usr/sbin/vold &
400 Installing MicroStrategy for UNIX 2005 MicroStrategy, Inc.

Basic Setup Guide Troubleshooting E
5 If the vold daemon is running but did not mount the

CD-ROM, stop the vold daemon and then stop and start
it. To stop it you need to know the identification process
number, which can be obtained by entering
# ps -ef | grep vold | grep -v grep
6 Stop the vold process by entering
# kill -15 process_ID_number
7 Stop and start the vold process by entering
# /usr/sbin/vold &
If you encounter problems using the vold daemon, enter one

of the following commands to mount the CD-ROM:
# etc/mountall
# mount -F hsfs -r ro /dev/dsk/cxtyd0sz

/cdrom/cdrom0
where x is the CD-ROM drive controller, y is the

CD-ROM drive SCSI ID number, and z is the slice of the
partition on which the CD-ROM is located.
To unmount the CD-ROM on Solaris
Type the following commands to unmount the CD-ROM on

Solaris:
1 # cd
2 # umount /cdrom/cdrom0
3 # eject
Mounting and unmounting the CD-ROM on AIX
Follow the steps below to mount the CD-ROM on the AIX

UNIX operating system.

To mount the CD-ROM on AIX
1 If necessary, use the mkdir command to create a mount

point for the CD. The following command creates a mount
point at /cdrom; you can mount the CD at any location on
the machines local file system.
# mkdir /cdrom
The commands in this procedure assume the CD is

mounted at /cdrom. If you mount the CD at a
different location, use that location when issuing
commands.
2 Mount the CD-ROM drive by entering
# mount -o ro -v cdrfs /dev/cdnumber /cdrom
In this command, number is the CD-ROM number for

your system, usually 0 (zero).
An example of the above command follows:
# mount -o ro -v cdrfs /dev/cd0 /cdrom
3 Navigate to the /cdrom directory by entering
# cd /cdrom
To unmount the CD-ROM on AIX
Type the following command to unmount the CD-ROM on

AIX:
# unmount /cdrom
This command assumes the CD is mounted at /cdrom. If you

mount the CD at a different location, use that location when
issuing commands.

General installation errors

1 Browse to <INSTALL_PATH> where <INSTALL_PATH> is
the directory you specified as the Install Directory during
installation
2 Open the install.log file. (Use an editor with a

command like dtpad install.log.)
3 Review the error messages. A common error is to run out

of space.
Server port number errors

This section provides troubleshooting information on server
port number errors.
I forgot the server port number
1 Browse to <HOME_PATH> where <HOME_PATH> is the

installation.
2 Browse to the folder bin and type mstrsvcmgr, then

press ENTER. This will launch the Service Manager.
3 Click Options. This launches the Service Options dialog

box.
4 Click Intelligence Server Options tab to view the port

number.
Port number is in use
1 Browse to your target directory. This is the path indicated

during installation as the Directory Name.
2 Browse to the folder bin and type mstrctl s

IntelligenceServer di FindingPortNumber,
then press ENTER.

3 Type mstrctl s IntelligenceServer ci

FindingPortNumber, then press ENTER.
4 Type mstrctl s IntelligenceServer gs

5 An XML file is returned. Search for the tag

<tcp_port_number>, which contains a port number
you can use. Record this number.
6 Type mstrctl s IntelligenceServer di

DSN connection errors

This section provides troubleshooting information on DSN
connection errors.
Testing the DSN connection failed in DSN

Creator
1 In the MicroStrategy Connectivity Configuration Wizard,

go to the Driver Details page and review all the
information.
2 Click each of the fields and read the comments at the

bottom of the window.
Permission errors
This section provides troubleshooting information on
permission errors.
Missing JVM file
The installation fails just before it starts transferring files,

and the following error is displayed:

JVM not found
Clear the set group ID on execution(s) bit on the permissions

of the directory where the InstallPath for the Intelligence
Server is to be placed.
1 In a console window, type
#chmod g-s directory
where directory is the InstallPath for Intelligence

Server.
2 Press ENTER.
Troubleshooting LDAP authentication

LDAP authentication problems within Intelligence Server
usually fall into one of the following categories:
LDAP authentication mode problems: Authentication

issues that include Clear Text and Secure Socket Layer
(SSL) authentication modes
LDAP functionality problems: Functionality problems

and questions regarding importing users and groups, or
synchronization of the LDAP users within MicroStrategy
metadata
Solutions appear below, organized within the categories

above. For flowcharts and more detail, see MicroStrategy
Tech Note TN5300-722-0369.
2005 MicroStrategy, Inc. Troubleshooting LDAP authentication 405

LDAP authentication mode problems

The authentication process involves an authentication user
and the actual user. The authentication user is used by
Intelligence Server to log in to the LDAP server and search for
the actual user. Therefore, the authentication user must have
the necessary Read and Search privileges within the LDAP
server and must be able to log in to a correct root. A correct
root is characterized as one that contains each of the potential
LDAP users who will be logging in to Intelligence Server in
one of its branches. If the authentication user cannot find the
actual user in one of its branches, the search for the actual
user fails.
There are two modes of authentication against LDAP: Clear

Text and SSL. Depending on which you are using, answering
the following questions can help you reach a solution:
If authentication fails in Clear Text mode:
Can the authentication user log in as an LDAP user?

The authentication user string can be tested in
Is the authentication Distinguished Name (DN) string

correct?
Is the password for the authentication user correct?
Can the LDAP user (different than the authentication

user) log in?
Are the user credentials correct?
Do the LDAP server-side logs show success messages?
406 Troubleshooting LDAP authentication 2005 MicroStrategy, Inc.

If authentication fails in SSL mode:
Does the authentication work in Clear Text mode?
Are the LDAP SDK DLLs installed on the

MicroStrategy Intelligence Server machine?
Do the LDAP SDK DLLs reside in the correct system

path?
Is the certificate obtained from the correct Certificate

Authority (CA)? For information on how to obtain the
certificate from the corresponding CA platforms, see
MicroStrategy Tech Note TN5300-722-0325.
Does the certificate reside on the MicroStrategy

Intelligence Server machine within the correct system
path? For information on how to import the certificate
to the Intelligence Server machine, see MicroStrategy
Tech Note TN5300-722-0325.
Do the LDAP server-side logs show success messages?
LDAP functionality problems

Functionality problems are most commonly issues with the
integration of Intelligence Server with the LDAP server(s).
Once the authentication is successful and Intelligence Server
has verified the existence of the LDAP user within the LDAP
server, it needs to treat the LDAP user as a MicroStrategy
user so that the user has the necessary privileges.
Intelligence Server achieves this transformation by importing

the LDAP user as a new MicroStrategy user into the
MicroStrategy metadata. (The option to not import the LDAP
user is discussed later in this chapter.) The relationship
between the LDAP user and the MicroStrategy user is
maintained by a link in the MicroStrategy metadata, which is
in the form of a Distinguished Name (DN) specified for the
user. A DN is the unique identifier of an entry in the LDAP
directory. You can choose to assign Distinguished Names to
MicroStrategy users explicitly. If none is supplied, the LDAP
users DN is assigned to the MicroStrategy user after the
LDAP user is imported.

The MicroStrategy users DN is different than the DN

assigned for the authentication under LDAP
configuration. The authentication user DN is the DN
of the account who logs in to the LDAP server and does
the authentication (search/verification) for the actual
user.
The authentication user DN is specified on the Intelligence

Server Configuration Editor, in the LDAP: Configuration
category in the User Distinguished Name (DN) box.
The users DN is specified in the User Editor, Authentication

tab in the User distinguished name (DN) box.
If no explicit link is specified, the LDAP user is imported as a

new MicroStrategy user under the LDAP Users group if the
Import Users check box is selected. The user can then be
treated as any MicroStrategy user and assigned privileges.
The user object in the metadata for the MicroStrategy user
now also contains a link to the LDAP user after the import.
Intelligence Server also allows LDAP groups to be imported.

With this option selected, all the groups to which the user
belongs are also imported under the LDAP Users group
(similar to the imported user) when an LDAP user logs in.
The hierarchical visual relationship between users and

their user group is not maintained within the LDAP
Users folder because it is maintained within the LDAP
server directory. Despite the visual link not appearing,
the actual link between the user and his or her group
does exist and is maintained.
The Synchronize at login options for both users and groups

cause the Intelligence Server to check (at the time of login)
whether:
user login ID, user name, MicroStrategy user in the

metadata, and LDAP user link information in the LDAP
server are synchronous
group name, MicroStrategy group in the metadata, and
LDAP group information in the LDAP server are
synchronous

The names and links between the two may or may not be
synchronized depending on whether the synchronize option
is selected in combination with whether the users and groups
are to be imported.
When the user is logged in as a temporary LDAP user or

group
there is no link persisted in the metadata and the user has

the privileges of a Guest user as long as the user is logged
in
the non-imported user cannot create objects and cannot

schedule reports
LDAP frequently asked questions

Do LDAP users have their own Inbox (History List) and
Personal folders?
If users are imported into the metadata, they have their own
Inbox and personal folders. If users are not imported,
regardless of whether they are part of the LDAP Users or
LDAP Public group, their Inbox is persisted only for the
current session. Users that are not imported do not have
personal folders and can only save items in public folders if
they have the correct privileges and permissions.
What is the scope value used for searching?
The scope for all searches is for all nodes in the sub-tree.
Intelligence Server does not support configuration of the
scope parameter, although the search results may be limited
using conditions in the search filter.
How can I assign security filters, security roles

(privileges), or access control (permissions) to individual
LDAP users?
Security filters, security roles, and access control may be

assigned to users after they are imported into the
MicroStrategy metadata, but this information may not be
assigned dynamically from information in the LDAP
repository.

To allow users to dynamically inherit this information, you

can assign these permissions at the group level in the
MicroStrategy metadata. Group membership information is
dynamically determined each time an LDAP user logs in to
the system, regardless of whether they are imported or not.
May two different users have different LDAP links, but

the same user name?
No. The MicroStrategy metadata may not contain two users

with the same login name or user name. If you attempt to
create a user with the same user login or user name, the
import fails. Each user object in the MicroStrategy metadata
must have a unique user login and user name.
What happens if there are two users with similar

descriptions in the LDAP directory?
If the DN descriptor that specifies a particular user is not

sufficient for Intelligence Server to identify him or her, then
the user will fail to log in. You can enhance the User search
filter and Group search filter in the LDAP configuration
category to help identify the user.
What happens if I import a group along with all its

members in the LDAP directory into MicroStrategy
metadata and then assign a connection mapping to the
imported group?
The connection mapping of the imported group to which the

user belongs will not readily apply to the user. For this to
work, you must manually assign the user as a member of the
group after he or she has been imported.

F
EXAMPLE OF A MODIFIED
F.
WEB.XML FILE
Introduction
This appendix provides an example of a modified web.xml

file in which parameters that originally had relative paths
now have absolute paths. The lines that were modified are
bolded for easy reference.
Example of modified web.xml file

The following is an example of a modified web.xml file:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE web-app PUBLIC "-//Sun
Microsystems,Inc.//DTD Web Application
2.3//EN""http://java.sun.com/dtd/web-app_2_3
.dtd">
- <web-app>
<display-name>Web Tier</display-name>
<context-param>
<param-name>adminServersFile</param-name>
<param-value>AdminServers.xml</param-value>
</context-param>
2005 MicroStrategy, Inc. Example of modified web.xml file 411

F Example of a Modified web.xml File Installation and Configuration Guide
<context-param>
<param-name>configFile</param-name>
<param-value>pageConfig.xml</param-value>
</context-param>
<context-param>
<param-name>dtdLocation</param-name>
<param-value>/WEB-INF/xml/dtds</param-value>
<description>This is the directory where the
application looks for DTDs used by Layout
Definitions</description>
</context-param>
<context-param>
<param-name>localesFile</param-name>
<param-value>/WEB-INF/xml/locales.xml
</param-value>
</context-param>
<context-param>
<param-name>preferencesGroupsFile</param-name>
<param-value>/WEB-INF/xml/
preferencesGroups.xml</param-value>
</context-param>
<context-param>
<param-name>resourcesFolderImage</param-name>
<param-value>../images</param-value>
</context-param>
<context-param>
<param-name>resourcesFolderJavaScript
</param-name>
<param-value>../javascript</param-value>
</context-param>
<context-param>
<param-name>resourcesFolderJSP</param-name>
<param-value>../jsp</param-value>
</context-param>
<context-param>
<param-name>resourcesFolderStyle</param-name>
<param-value>../style</param-value>
</context-param>
<context-param>
<param-name>resourcesFolderStyleFixedFont
</param-name>
<param-value>../style/fixed-font</param-value>
</context-param>
<context-param>
<param-name>resourcesFolderStyleFixedFontDB
</param-name>
<param-value>../style/fixed-font/db
</param-value>
</context-param>
<context-param>
<param-name>serverConfigFilesDefaultLocation
</param-name>
<param-value>ABSOLUTE:/usr/GGapps/
MicroStrategy/xml/</param-value>
</context-param>
<context-param>
<param-name>serverLogFilesDefaultLocation
</param-name>
<param-value>ABSOLUTE:/usr/GGapps/
412 Example of modified web.xml file 2005 MicroStrategy, Inc.

Installation and Configuration Guide Example of a Modified web.xml File F
MicroStrategy/xml/log/</param-value>
</context-param>
<context-param>
<param-name>serverLogPropertiesFile
</param-name>
<param-value>logger.properties</param-value>
</context-param>
<context-param>
<param-name>styleCatalogFile</param-name>
<param-value>>/WEB-INF/xml/styleCatalog.xml
</param-value>
</context-param>
<context-param>
<param-name>sysPreferenceDefinitionFile
</param-name>
<param-value>sys_definitions.xml</param-value>
</context-param>
<context-param>
<param-name>sysServerDefaultsFile</param-name>
<param-value>sys_defaults.xml</param-value>
</context-param>

- <servlet>
<servlet-name>mstrDocumentImages</servlet-name>
<servlet-class>com.microstrategy.web.servlets.
DocumentImageServlet</servlet-class>
- <init-param>
<param-name>imagesPath</param-name>
<param-value>../../images</param-value>
</init-param>
</servlet>
- <servlet>
<servlet-name>mstrWeb</servlet-name>
<display-name>Main Servlet</display-name>
MainServlet</servlet-class>
- <init-param>
<param-name>adminServletDeploymentName
</param-name>
<param-value>mstrWebAdmin</param-value>
</init-param>
- <init-param>
<param-name>blankReportId</param-name>

<param-value>05B202B9999F4C1AB960DA6208CADF3D
</param-value>
</init-param>
- <init-param>
<param-name>blankReportWritingId</param-name>
<param-value>934195564E2E58BD7CD7E4AF0423C149
</param-value>
</init-param>
- <init-param>
<param-name>clientLoggingFile</param-name>
<param-value>C:\MyTest.log</param-value>
<description>This parameter specifies the
location of the log file where the statistics
will be
saved. The full path should be included as part
of the parameter value. If the file does not
exist, the logging infrastructure will create
it (if possible). If the file already
exists,then the new information will be
appended to it.</description>
</init-param>
- <init-param>
<param-name>clientLoggingForm</param-name>
<param-value>http://localhost:8080/Microstrategy
7/jsp/ClientPerformanceForm.jsp
<description>This parameter specifies the server
and page to be used for displaying the client
performance results processing
form.</description>
</init-param>
- <init-param>
<param-name>clientLoggingLevel</param-name>
<param-value>0</param-value>
<description>This is the level of detail included
in the log. Its value is formed by the
BITWISE OR-ing of these values:
1=Analyze information at the PAGE (rendering)
level,
2=Analyze information at the DETAILED
(rendering) level,
4=Analyze information at the METHOD (client
manipulation) level,
8=Analyze information at the ACTION (client
manipulation) level.</description>
</init-param>
- <init-param>
<param-name>clientLoggingMode</param-name>
<description>This is how the logging is presented
to the user. Its value is formed by the
BITWISE OR-ing of these values:
1=Log to a file (see the value of
clientLoggingFile above for location). For this
flag to be applied, it requires the
clientLoggingType is set to LIVE.
2=Display results through an HTML page loaded

on the client's computer. For this flag

to be applied, it requires the
clientLoggingType is set to LIVE.
4=Display results through a Browser ALERT box.
</description>
</init-param>
- <init-param>
<param-name>clientLoggingPage</param-name>
<param-value>http://localhost:8080/Microstrategy
7/jsp/Client_Log.jsp</param-value>
<description>This parameter specifies what will
be the server and page to be used for
displaying client performance results.
</description>
</init-param>
- <init-param>
<param-name>clientLoggingType</param-name>
<description>This parameter specifies the type of
process that will be used for collecting the
statistics information.If the server/page to
process the statistical information is going
to be available for the client computer and
the reporting method involves log file or HTML
report, the logging type should be specified
to be LIVE (1). If the client computer where
the test is going to be performed does not have
access to this server, then the logging type
is STATIC (2). It does not matter if the pages
are being accessed live from the Web Universal
application or not.</description>
</init-param>
- <init-param>
<param-name>controllerClass</param-name>
<param-value>com.microstrategy.web.app.MSTRWeb
Controller</param-value>
</init-param>
- <init-param>
<param-name>defaultPDFImagesFolder</param-name>
<param-value>/images/</param-value>
</init-param>
- <init-param>
<param-name>excelDirectExport</param-name>
<param-value>false</param-value>
</init-param>
- <init-param>
<param-name>externalSecurityClass</param-name>
<param-value>com.microstrategy.web.app.Default
ExternalSecurity</param-value>
</init-param>
- <init-param>
<param-name>formatPropertiesMapping
</param-name>
<param-value>>/WEB-INF/xml/formattingProperties.
xml</param-value>
</init-param>

- <init-param>
<param-name>iframeJSP</param-name>
<param-value>/jsp/iframe.jsp</param-value>
</init-param>
- <init-param>
<param-name>intelligenceServerPollingFrequency
</param-name>
</init-param>
- <init-param>
<param-name>objBrowserFolderLinksConfigFile
</param-name>
<param-value>>/WEB-INF/xml/objBrowserFolderLink
.xml</param-value>
</init-param>
-<init-param>
<param-name>reloadConfigurationFiles
</param-name>
<param-value>false</param-value>
</init-param>
- <init-param>
<param-name>servletDeploymentName
</param-name>
<param-value>mstrWeb</param-value>
</init-param>
- <init-param>
<param-name>useServletForPDF</param-name>
<param-value>true</param-value>
</init-param>
</servlet>
- <servlet>
<servlet-name>mstrWeb72GraphLoader</servlet-name>
OldLinksServlet</servlet-class>
- <init-param>
<param-name>graphBeanName</param-name>
<param-value>gb</param-value>
</init-param>
<param-name>mainServletPath</param-name>
</init-param>
- <init-param>
<param-name>reportBeanPath</param-name>
<param-value>mstrWeb.report.frame.rb
</param-value>
</init-param>
- <init-param>
<param-name>resourceName</param-name>
<param-value>MSIGraphLoader.asp</param-value>
</init-param>
</servlet>
- <servlet>
<servlet-name>mstrWeb72RebuildReport
</servlet-name>

OldLinksServlet</servlet-class>
- <init-param>
<param-name>mainServletPath</param-name>
</init-param>
- <init-param>
<param-name>reportBeanPath</param-name>
<param-value>mstrWeb.report.frame.rb
</param-value>
</init-param>
- <init-param>
<param-name>resourceName</param-name>
<param-value>RebuildReport.asp</param-value>
</init-param>
</servlet>
- <servlet>
<servlet-name>mstrWebAdmin</servlet-name>
<display-name>Main Admin Servlet</display-name>
AdminServlet</servlet-class>
- <init-param>
<param-name>adminServletDeploymentName
</param-name>
</init-param>
- <init-param>
<param-name>configFile</param-name>
<param-value>/WEB-INF/xml/pageConfig.xml
</param-value>
</init-param>
- <init-param>
<param-name>controllerClass</param-name>
<param-value>com.microstrategy.web.admin.Admin
Controller</param-value>
</init-param>
- <init-param>
<param-name>diagnosticsFileMbSizeLimit
</param-name>
</init-param>
- <init-param>
<param-name>externalSecurityClass</param-name>
<param-value>com.microstrategy.web.app.
DefaultExternalSecurity</param-value>
</init-param>
- <init-param>
<param-name>servletDeploymentName</param-name>
</init-param>
- <init-param>
<param-name>webServletDeploymentName
</param-name>

</init-param>
- <security-role-ref>
<role-name>ADMIN</role-name>
<role-link>admin</role-link>
</security-role-ref>
</servlet>
- <servlet>
- <servlet-mapping>
<servlet-name>mstrDocumentImages</servlet-name>
<url-pattern>/servlet/Images/*</url-pattern>
</servlet-mapping>
- <servlet-mapping>
<servlet-name>mstrWeb72GraphLoader
</servlet-name>
<url-pattern>servlet/MSIGraphLoader.asp
</url-pattern>
</servlet-mapping>
- <servlet-mapping>
servlet-name>mstrWeb72RebuildReport
</servlet-name>
<url-pattern>/servlet/RebuildReport.asp
</url-pattern>
</servlet-mapping>
- <servlet-mapping>
servlet-name>mstrDocumentImages
</servlet-name>
<url-pattern>/servlet/images/*</url-pattern>
</servlet-mapping>
- <servlet-mapping>
servlet-name>mstrWeb</servlet-name>
<url-pattern>/servlet/mstrWeb</url-pattern>
</servlet-mapping>
- <servlet-mapping>
servlet-name>mstrWebAdmin</servlet-name>
<url-pattern>/servlet/mstrWebAdmin</url-pattern>
</servlet-mapping>
- <session-config>
<session-timeout>30</session-timeout>
</session-config>

- <mime-mapping>
<extension>css</extension>
<mime-type>text/css</mime-type>
</mime-mapping>
- <taglib>
<taglib-uri>/webUtilTL.tld</taglib-uri>
<taglib-location>/WEB-INF/tlds/webUtilTL.tld
</taglib-location></taglib>
- <security-constraint>
<web-resource-collection>
<web-resource-name>Administrator
</web-resource-name>
<url-pattern>/servlet/mstrWebAdmin
</url-pattern>
<http-method>GET</http-method>

<http-method>POST</http-method>
<http-method>PUT</http-method>
<http-method>DELETE</http-method>
</web-resource-collection>
<auth-constraint>
</auth-constraint>
<user-data-constraint>
<transport-guarantee>NONE
</transport-guarantee>
</user-data-constraint>
</security-constraint>
<login-config>
<auth-method>BASIC</auth-method>
<realm-name>Administrator Authentication
Area</realm-name>
</login-config>
<security-role>
</security-role>
</web-app>


GLOSSARY
attribute A data level defined by the system architect and associated

with one or more columns in a data warehouse lookup table.
Attributes include data classifications like Region, Order,
Customer, Age, Item, City, and Year. They provide a means
for aggregating and filtering at a given level.
attribute element A value of any of the attribute forms of an attribute. For

example, New York and Dallas are elements of the attribute
City; January, February, and March are elements of the
attribute Month.
child attribute The lower-level attribute in an attribute relationship.
compound attribute An attribute that has more than one key (ID) form.
cluster A collection of two or more machines that provide services to

a common set of users. Each machine in the cluster is called a
node.
See also clustering.
clustering A configuration strategy that provides uninterrupted access

to data, enhanced scalability, and increased performance for
users.
2005 MicroStrategy, Inc. attribute 421

Glossary Installation and Configuration Guide
connection string Stores the information required to connect to a database

server. A connection string usually includes a DSN and the
user ID and password required to log in to the database
server. This information varies depending on the particular
database server.
DAS See direct-attached storage.
data source name Provides connectivity to a database through an ODBC driver.

(DSN) A DSN generally contains host machine name or IP address,
instance name, database name, directory, database driver,
User ID, password, and other information. The exact
information included in the DSN varies by DBMS. Once you
create a DSN for a particular database, you can use it in an
application to call information from the database. There are
three types of DSNs:
1) System DSN: can be used by anyone who has access to the

machine. DSN info is stored in the registry.
2) User DSN: is created for a specific user. Also stored in the

registry.
3) File DSN: DSN information is stored in a text file with

.DSN extension.
data warehouse 1) A database, typically very large, containing the historical

data of an enterprise. Used for decision support or business
intelligence, it organizes data and allows coordinated updates
and loads.
2) A copy of transaction data specifically structured for query,

reporting, and analysis.
direct-attached storage A device such as an array of disks, a fiber channel, and the
(DAS) like that is directly connected to a machine, meaning that no
network traffic or overhead is involved.
DSN See data source name (DSN).
422 connection string 2005 MicroStrategy, Inc.

Installation and Configuration Guide Glossary
failover support Ensures that a business intelligence system remains available

for use in the event of an application or hardware failure.
Clustering provides failover support in two ways: load
distribution and request recovery.
hierarchies A set of attributes defining a meaningful path for element

browsing or drilling. The order of the attributes is
typicallythough not alwaysdefined such that a higher
attribute has a one-to-many relationship with its child
attributes.
installation log file The MicroStrategy setup program generates a log file in text
format. This log file contains records of all actions performed
by the setup program and by other executable files related to
installation.
load balancing A strategy aimed at achieving even distribution of

MicroStrategy Web Universal user sessions across
MicroStrategy Intelligence Servers. MicroStrategy achieves
four-tier load balancing by incorporating load balancers into
metadata A repository whose data associates the tables and columns of

a data warehouse with user-defined attributes and facts to
enable the mapping of the business view, terms, and needs to
the underlying database structure. Metadata can reside on
the same server as the data warehouse or on a different
database server. It can even be held in a different RDBMS.
node Each machine in a cluster.
ODBC See Open Database Connectivity.
ODBC driver A software routine that translates MicroStrategy Intelligence

Server requests into commands that the DBMS understands.
2005 MicroStrategy, Inc. failover support 423

ODBC driver manager Coordinates communication between a client application and

database server. The client application tells the driver
manager that it needs to connect using a particular
connection string. The DSN found in this connection string
provides the driver manager with the type of database server
to which the application needs access. From this information,
the driver manager decides what driver to use and initiates
the communication.
Open Database An open standard with which client computers can

Connectivity communicate with relational database servers. Client
machines make a connection to a particular logical database,
on a particular physical database server, using a particular
ODBC driver.
parent attribute The higher-level attribute in an attribute relationship with

one or more children.
port number The port number is how a server process identifies itself on
the machine on which it is running. For example, when the
Intelligence Server machine receives a network call from a
client (Desktop, Web Universal, Narrowcast Server,
Command Manager, and so on), it knows to forward those
calls to the Intelligence Server port number that is specified
in the call.
prefix A prefix is stored in the project metadata associated with a

table or tables and is used by the Engine to generate SQL.
Also, the Catalog Server uses it to obtain table sample values
and row counts. In most cases, it should match the name
space field since it is used to qualify on a specific table
belonging to a certain owner or name space. Prefixes can be
defined and modified from the Warehouse Catalog interface.
process An executing application comprising one or more threads.

Processes use temporary private address spaces and control
operating system resources such as files, dynamic memory
allocations, pipes, and synchronization objects.
424 ODBC driver manager 2005 MicroStrategy, Inc.

Installation and Configuration Guide Glossary
project 1) The highest-level intersection of a data warehouse,

metadata repository, and user community, containing
reports, filters, metrics, and functions.
2) An object containing the definition of a project, as defined

in (1). The project object is specified when requesting the
establishment of a session.
project source Defines a connection to the metadata database and is used by

various MicroStrategy products to access projects. A direct
project source is a two-tier connection directly to a metadata
repository. A server project source is a three-tier connection
to a MicroStrategy Intelligence Server. One project source
can contain many projects and the administration tools found
at the project source level are used to monitor and administer
all projects in the project source.
schema object A MicroStrategy object created, usually by a project designer,

that relates the information in the logical data model and
physical warehouse schema to the MicroStrategy
environment. These objects are developed in MicroStrategy
Architect, which can be accessed from MicroStrategy
Desktop. Schema objects directly reflect the warehouse
structure and include attributes, facts, functions, hierarchies,
operators, partition mappings, tables, and transformations.
server definition A MicroStrategy object stored in the metadata containing

information about the configuration of an Intelligence Server.
server instance The combination of an Intelligence Server running with a

particular server definition.
statistics tables Tables that are used to record a variety of statistical

information about the usage and performance of a
MicroStrategy system.
Structured Query The query language standardized in 1986 by the American

Language (SQL) National Standards Institute (ANSI) and used to request
information from tables in a relational database and to
2005 MicroStrategy, Inc. project 425

manipulate the tables structure and data.
426 Structured Query Language (SQL) 2005 MicroStrategy, Inc.

INDEX
Numerics Apache 140

Tomcat application server 34
2-tier project source 108
Web server 34
3-tier project source 109
starting 175
Apache Web server
A configuring to serve static files 161
absolute path, web.xml 411 proxy requests to WebLogic 145
access application servers
MicroStrategy Connectivity Configura- Apache Tomcat 34
tion Wizard 331 BEA WebLogic 34
accessing MicroStrategy Web Administra- IBM WebSphere 34
tor page Oracle 10g 34
Sun ONE (iPlanet) 187 supported 34
adding DSN attribute
MicroStrategy Connectivity Configura- attribute elements defined on 127
tion Wizard 332 child 127
adding/removing MicroStrategy compo- compound 127
nents (Windows) 308
parent 127
admin role
Attribute Creation Wizard 119, 126
assigning users 173, 185, 196, 202
automatic deployment
Administrative Server, starting 168
Web Universal 147
Administrator
MicroStrategy Command Manager 4
MicroStrategy Enterprise Manager 4 B
MicroStrategy Object Manager 4 backup 39
Analytics Modules 12 BEA WebLogic application servers 34

Index Installation and Configuration Guide
C accessing on Windows 93
create metadata repository 95
CD-ROMs
overview 89
mounting on AIX 402
prerequisites 88
mounting on Solaris 400
response.ini file (Windows) 257
unmounting on AIX 402
setup Intelligence server 102
unmounting on Solaris 401
configuring
certified database and drivers
Apache Web server to serve static
Intelligence Server 42 files 161
column 379 logs display 215
command line mode Tomcat 193
configuring metadata 291 configuring MicroStrategy
creating project source 304
command line mode 289
MicroStrategy Configuration configuring ODBC
Wizard 289
default directories (UNIX) 329
setting up MicroStrategy Intelligence
Server 298 default directories (Windows) 328
command line utility UNIX defined on 328
undeploying Web Universal 190 Windows defined on 328
common setups 2 configuring Sun JDK
components 2 Tomcat 192
Administrator 4 configuring through command line mode
(UNIX) 279
MicroStrategy Analytics Modules 12
connection errors, DSN 404
MicroStrategy Desktop 3
connection strings defined on 327
MicroStrategy eTrainer for Web 11
connectivity 357
MicroStrategy Intelligence Server 5
Connectivity Configuration Wizard 331
MicroStrategy Office 10
access 331
MicroStrategy SDK 9
adding DSN 332
MicroStrategy Tutorial Reporting 12
cookies, Security page 218
MicroStrategy Web and Web
Universal 7 CPU licensing 56
MicroStrategy Web Services 8 creating DSN
Narrowcast Server 11 using MicroStrategy Configuration
Wizard 334
SequeLink ODBC Socket Server 13
using MicroStrategy Connectivity Con-
configuration figuration Wizard 331
metadata repository and statistics using ODBC Administrator 336
tables 90
accessing on UNIX 93

Installation and Configuration Guide Index
D DSN Creator 404

DSNs
data source name defined on 326
connection errors 404
data warehouse
DSNs, creating 334
Warehouse Catalog 375
duplicate WAR file, deploying Web
data warehouses defined on 326 Universal 147
database instance defined on 114
database management system 386
definition E
configuration objects defined on 113 element browsing defined on 37
metadata shell defined on 112 encryption, Security page 218
MicroStrategy errors
metadata defined on 112 log file settings 212
project defined on 114 viewing 213
project source defined on 113 eTrainer for Web 11
schema objects defined on 113 example
deploy MicroStrategy Web Universal as a response.ini file for Configuration Wiz-
WAR file ard (UNIX) 287
Sun ONE (iPlanet) 184 response.ini file for Configuration Wiz-
deploying MicroStrategy Web Universal ard (Windows) 257
deploying with WebLogic response.ini file for installation
automatically 147 (Windows) 251
deploying with WebLogic response.ini file for uninstallation 263
manually 147 web.xml 411
Linux 195
Oracle 10g 201
F
Sun ONE (iPlanet) 182
Tomcat 195 Fact Creation Wizard 119
WebLogic and Apache 146 file
WebSphere 167 install.log 232
Desktop preinst.log 268
MicroStrategy Architect 3 setup.exe 232
MicroStrategy Desktop Analyst 3
MicroStrategy Desktop Designer 3 H
MicroStrategy Server Administrator 3 hardware configuration
Diagnostics Configuration page 212 for large production system 396
diagnostics, setting 211 for medium production system 393
direct project source 108 for small production system 389
directory structure for UNIX 83 hardware recommendations

Intelligence Server on UNIX 24 Command line mode 44

Web Universal on Linux 28 GUI mode 43
Web Universal on UNIX 27 silent installation 45
Windows 22 installation prerequisites 20
hierarchy hardware recommendations for Intelli-
Hierarchy Editor 119 gence Server on UNIX 24
hotfix hardware recommendations for Web
silent installation (Windows) 271 Universal on Linux 28
hardware recommendations for Web
how to use this book 14
Universal on UNIX 27
HTML documents 221
hardware recommendations for
overview defined on 223 Windows 22
Setup for document creation 224 recommended installation location 21
Setup for document execution 227 software recommendations for Intelli-
gence Server on UNIX 31
I software recommendations for Web
Universal on UNIX 33
IBM HTTP Server software recommendations for
configuring to serve static files 179 Windows 29
Web server 34 installation procedure
IBM JDK, Java development kit 35 InstallShield Wizard on UNIX 74
IBM WebSphere InstallShield Wizard on Windows 51
application servers 34 UNIX 72
Informix 8 (Windows) 343 Windows 50
Informix Wire Protocol 341 InstallShield Wizard on UNIX
install.log 232 accessing 74
installation InstallShield Wizard on Windows
creating response.ini file accessing 51
(Windows) 234 Intelligence Server
install.log file 232 certified database and drivers 42
OEM silent (Windows) 265 create server definition 105
plug-in for Apache 145 Enterprise edition 5
response.ini file (Windows) 233 setup 102
silent (UNIX) 274 Standard edition 5
silent (Windows) 265 Universal edition 5
silent installation of hotfix Intelligence Server on UNIX
(Windows) 271
hardware recommendations 24
troubleshooting silent (Windows) 270
software recommendations 31
installation log file 232
Intelligence Server, adding/connecting to
installation method

Web Administrator page 206 Linux

Intelligence Server, adding/modifying deploying MicroStrategy Web
Server Properties page 207 Universal 195
Intelligence Servers page 206 log
adding a server manually 206 installation 232
connected servers 206 statistics 39
unconnected servers 206 log files
international support xxii configuring display 213, 215
configuring internal or custom
settings 212
J logger.properties file 211
Java development kits
IBM JDK 35
Sun JDK 35
M
supported 35 manual deployment, Web Universal 147
Java heap size, setting 158, 177, 190 mapping a security role
Java Server Pages, precompiling 159 Oracle 10g 203
JSP files, precompiling 177 messages, viewing 213
metadata 90, defined on 326
configuration 98
L table 97
launch project metadata repository 89, 90, 103
WebLogic and Apache 156 create 95
launching Administrative Console metadata shell
WebSphere 168 definition defined on 112
LDAP methods of automated installation
FAQs 409 (Windows) 231
troubleshooting 406 response.ini file installation 231
licenses 46 silent installation 231
CPU 319 Microsoft IIS Web server 34
CPU licenses 47 Microsoft ODBC Administrator 336
managing 317 Microsoft SQL Server Wire Protocol
MicroStrategy License Manager 321 (UNIX) 342
named user 318 MicroStrategy Administrator
named user licenses 47 MicroStrategy Command Manager 4
number of licenses in use 321 MicroStrategy Enterprise Manager 4
Processor Affinity 319 MicroStrategy Object Manager 4
types 318 MicroStrategy Analytics Modules 12
upgrading 322 MicroStrategy common setups 2

MicroStrategy components 2 definition defined on 112

Desktop 3 MicroStrategy Narrowcast Server 11
MicroStrategy Administrator 4 MicroStrategy ODBC Driver for Informix 8
MicroStrategy Analytics Modules 12 (Windows) 343
MicroStrategy eTrainer for Web 11 MicroStrategy ODBC Driver for Informix
Wire Protocol 341
MicroStrategy Intelligence Server 5
MicroStrategy ODBC Driver for Microsoft
MicroStrategy Narrowcast Server 11
SQL Server Wire Protocol
MicroStrategy Office 10 (UNIX) 342
MicroStrategy SDK 9 MicroStrategy ODBC Driver for Sybase
MicroStrategy Tutorial Reporting 12 ASE Wire Protocol 341
MicroStrategy Web and Web MicroStrategy ODBC Oracle Wire
Universal 7 Protocol 340
MicroStrategy Web Services 8 MicroStrategy Project Builder 3, 375
SequeLink ODBC Socket Server 13 MicroStrategy project schema 132
MicroStrategy Configuration Wizard update schema 132
accessing on UNIX 93 MicroStrategy Server Properties page
accessing on Windows 93 adding/modifying 207
create metadata repository 95 MicroStrategy Tutorial Reporting 12
overview 89 MicroStrategy Web 135
prerequisites 88 MicroStrategy Web Administrator
setup Intelligence server 102 Page 205
MicroStrategy Connectivity Configuration MicroStrategy Web Administrator page
Wizard 331 adding/connecting to Intelligence
access 331 Server 206
adding DSN 332 diagnostics 211
MicroStrategy Desktop Diagnostics Configuration page 212
MicroStrategy Architect 3 Intelligence Servers page 206
MicroStrategy Desktop Analyst 3 Narrowcast Server Integration
MicroStrategy Desktop Designer 3 page 211
MicroStrategy Server Administrator 3 options 208
MicroStrategy Enterprise Manager 100 scheduled e-mail 211
MicroStrategy eTrainer for Web 11 Security page 218
MicroStrategy Intelligence Server 90 Send Now 211
Enterprise edition 5 statistics 215
Standard edition 5 View Logs page 213
uninstalling (UNIX) 314 MicroStrategy Web Administrator page
(Oracle)
Universal edition 5
accessing 204
MicroStrategy metadata
MicroStrategy Web Administrator page

(Tomcat) Microsoft SQL Server Wire Protocol

accessing 197 (UNIX) 342
controlling access to 196 Netezza (UNIX) 353
MicroStrategy Web Administrator page Oracle Wire Protocol 340
Sun One (iplanet) other relational databases for
controlling access to 185 Windows 345
MicroStrategy Web and Web Universal Red Brick (UNIX) 346
versions 7 Sybase Adaptive Server IQ
(UNIX) 348
MicroStrategy Web Universal 7
Sybase ASE Wire Protocol 341
manual deployment 147
Teradata (UNIX) 349
undeploying 190
ODBC driver manager defined on 327
uninstalling (UNIX) 315
options file 274
MicroStrategy Web Universal (Oracle 10g)
Oracle 10g
launching project 204
application server 34
MicroStrategy Web Universal (Tomcat)
deploy with the Oracle Enterprise
launching the project 198
Manager 202
MicroStrategy Web Universal deploying
deploying MicroStrategy Web
automatically 147 Universal 201
from duplicate WAR file 147 locating WAR file 200
MSTRInst.log 268 modifying XML parser 200
preconfiguration information 199
N Oracle Enterprise Manager 203
Narrowcast Server 11 Oracle Wire Protocol 340
scheduled e-mail 211
Send Now 211 P
network bandwidth 40 pageCheckSeconds parameter,
setting 160
O parameters
DB2 Wire Protocol 362
ODBC defined on 326
Informix Wire Protocol 366
default directories (UNIX) 329
Informix XPS 372
default directories (Windows) 328
ODBC 369
ODBC Administrator 336
Oracle Wire Protocol 361
ODBC connectivity 357
Red Brick 369
ODBC driver defined on 327
SQL Server Wire Protocol 368
Informix 8 (Windows) 343
SybaseIQ 370
Informix Wire Protocol 341
Teradata-Server 370
Informix XPS (UNIX) 351

partition mapping table 378 Hierarchy Editor 119

password to metadata 103 project source
PDF configuration 2-tier 108
Sun ONE (iPlanet) 182 3-tier 109
WebLogic and Apache 146 create default 101
performance-based setup direct 108
WebLogic and Apache 158 server 108
permission errors 404 project sources 94
plug-in for Apache 145
plugin-cfg.xml, regenerating 171 R
port number defined on 109
re-deploying 157
precompiling
reinstalling MicroStrategy components
JSP files in WebLogic 159
(Windows) 310
JSP files in WebSphere 177
control panel 310
preconfiguration information
reinstalling MicroStrategy Office 311
Oracle 10g 199
Report Services documents
Sun ONE (iPlanet) 180
Setup for document execution 228
Tomcat 191
response.ini file
WebLogic and Apache 142
Configuration Wizard (UNIX) 280
WebSphere 165
Configuration Wizard example 261
prefix 384
create for installation (Windows) 234
preinst.log 268
create through Configuration Wizard in
prerequisites command line mode
MicroStrategy Configuration (UNIX) 282
Wizard 88 create through GUI mode of Configura-
processes defined on 104 tion Wizard (UNIX) 281
processor speed 40 creating through Configuration Wizard
project (Windows) 257
create 120 example for Configuration Wizard
create attributes 126 (UNIX) 287
create facts 124 example for Configuration Wizard
(Windows) 261
create shortcut object 130
example for installation
data warehouse 122 (Windows) 251
lookup table 122 example for uninstall (Windows) 263
Project Assistant wizard 120 for Configuration Wizard
relate table 122 (Windows) 257
Warehouse Catalog 122 for installation (Windows) 233
Project Builder 118 parameters and options for Configura-

tion Wizard (UNIX) 282 Setup for document creation

parameters and options for Configura- HTML documents 224
tion Wizard (Windows) 258 Setup for document execution
parameters and options for installation HTML documents 227
(Windows) 234
Report Services documents 228
uninstalling (Windows) 263 setup.exe 232
using for Configuration Wizard silent installation 265
(Windows) 262
for hotfix (Windows) 271
using for installation (Windows) 256
introduction (UNIX) 274
using through Configuration Wizard
(UNIX) 288 OEM (Windows) 265
restarting options file (UNIX) 274
WebSphere application server 171 output (UNIX) 279
restarting application server output on Windows 268
Sun One (iPlanet) 188 override options 279
perform on Windows 266
settings (UNIX) 275
S System Management Server (SMS) on
scheduled e-mail 211 Windows 265
schema object 114 troubleshooting (Windows) 270
Security page using options file (UNIX) 274
cookies 218 values for different languages 267
encryption 218 sizing guidelines
MicroStrategy Web Administrator 218 caching defined on 37
options 218 number of users 35
security role, mapping OLAP Services 38
Oracle 10g 203 report complexity 36
security, access to MicroStrategy Web Ad- Report Services
ministrator page 196 document defined on 37
security, access to MicroStrategy Web Ad- SMS. See System Management Server.
ministrator page Sun One software activation
(iPlanet) 185 UNIX 81
Send Now 211 Windows 66
SequeLink ODBC Socket Server 13 software recommendations
server definition defined on 90, 105 for application servers 34
server project source 108 for Java development kits 35
Server Properties page 208 Intelligence Server on UNIX 31
setting, diagnostics 211 Web Universal on UNIX 33
setup command-line parameter Windows 29
(Windows) 256

SQL setting Java heap size 190

queries 359 undeploying Web Universal 190
scripts 96 Web server 34
starting Sun ONE Application Server Admin Con-
Administrative Server 168 sole
Apache Web Server 175 launching 183
iPlanet Application Server Administra- support
tion Tool 183 international xxii
Web module for WebSphere 173 Sybase ASE Wire Protocol 341
WebSphere Administrative System Management Server (SMS) on
Console 168 Windows
WebSphere default application silent installation 265
server 169
static files
configuring Apache Web server 161
T
configuring IBM HTTP Server 179 table name space 378, defined on 386
statistics technical support xxiii
log 39 Tomcat
tables 100 configuring 193
Statistics page, options 216 configuring Sun JDK 192
statistics tables defined on 90 deploying MicroStrategy Web
Universal 195
statistics, MicroStrategy Web Administra-
tor page 215 locating WAR file 194
Sun ONE (iPlanet) preconfiguration information 191
accessing MicroStrategy Web Adminis- troubleshooting
trator page 187 DSN connection errors 404
application server 34 LDAP 406
connecting to Project page 189 LDAP FAQs 409
deploy MicroStrategy Web Universal as permission errors 404
a WAR file 184 server port number errors 403
deploying MicroStrategy Web troubleshooting (UNIX) 399
Universal 182 troubleshooting Warehouse Catalog
locating WAR file 181 column missing 388
PDF configuration 182 columns data type changed 387
preconfiguration information 180 Tutorial Reporting 12
recommended configuration for types of GUI installation
UNIX/Linux 180
Typical and Advance 53
recommended configuration for
types of licenses
Windows 181
CPU licenses 47
restarting application server 188

named user licenses 47 View Logs page 213

Typical and Advanced viewing, errors 213
types of installation 53
W
U WAR file
unattended installation (UNIX) 274 deploying Web Universal 147
undeploying, Web Universal using com- exploding for WebLogic and
mand line 190 Apache 149
uninstalling locating 200
Control Panel (Windows) 312 locating for Oracle 10g 200
MicroStrategy Intelligence Server locating for Sun ONE (iPlanet) 181
(UNIX) 314 locating for Tomcat 194
MicroStrategy Web Universal locating for WebLogic 143
(UNIX) 315
locating for WebSphere 166
response.ini (Windows) 263
unzipping for WebLogic and
Uninstalling MicroStrategy components Apache 151
(Windows) 312
Warehouse Catalog 119
MicroStrategy Office (Windows) 313
access 377
UNIX layout 377
configuring ODBC defined on 328 update table structure 380
installation procedure 72 usage and settings 375
InstallShield Wizard 74 view table structure 379
software activation 81 warnings, viewing 213
verifying installation 82 Web and Web Universal
user versions 7
recommended setup for medium pro- Web module for WebSphere
duction system 395
starting 173
recommended setup for small produc-
tion system 391 Web servers
user objects 113 Apache 34
users IBM HTTP Server 34
assigned to admin role 173, 185, 196, Internet Information Server 34
202 Web Universal connections 205
Web Universal on Linux
V Web Universal on UNIX
verifying installation hardware recommendations 27
UNIX 82 software recommendations 33
Windows 67 web.xml

absolute path 411 installation procedures 50

configure for WebLogic 143 InstallShield Wizard 51
example 411 software activation 66
re-deploying the application 157 software recommendations 29
sample modified 411 verifying installation 67
WebLogic 140 Windows INI 233
WebLogic and Apache
configure web.xml 143 X
Universal 146 XML parser
launch project 156 Oracle 10g 200
locating WAR file 143 XSL report style 39
PDF configuration 146
performance-based setup 158
precompiling JSP files 159
preconfiguration information 142
production mode 147
setting Java heap size 158
setting pageCheckSeconds
parameter 160
WAR file 151
WAR file exploding 149
WebSphere
application installation 170
Universal 167
launching Administrative Console 168
locating WAR file 166
precompiling JSP files 177
preconfiguration 165
regenerating plugin-cfg.xml 171
restarting application server 171
setting Java heap size 177
starting default application server 169
WebSphere 5 165
Windows
configuring ODBC defined on 328

Installation Config

Enviado por

Dados do documento

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

Installation Config

Enviado por

Direitos autorais:

Formatos disponíveis

Installation and Configuration

Document number: 09300801

Copyright 2005 by MicroStrategy Incorporated. All rights reserved.

Document description.............................................................. xiii

2005 MicroStrategy, Inc. v

2. Planning Your Introduction................................................................................ 19

vi 2005 MicroStrategy, Inc.

Setting up the MicroStrategy Intelligence Server................. 102

6. Creating a Project Introduction.............................................................................. 111

7. Deploying Your Introduction.............................................................................. 135

8. Configuring and Introduction.............................................................................. 139

2005 MicroStrategy, Inc. vii

Preconfiguration information ................................................ 180

9. Setting up Documents Introduction.............................................................................. 221

10. Automated Introduction.............................................................................. 229

11. Automated Introduction.............................................................................. 273

viii 2005 MicroStrategy, Inc.

Creating an options file ........................................................ 274

12. Adding or Removing Introduction.............................................................................. 307

A. Managing Licenses Introduction.............................................................................. 317

B. ODBC and DSNs Introduction.............................................................................. 325

2005 MicroStrategy, Inc. ix

Using the Microsoft ODBC Administrator............................. 336

C. Advanced Warehouse Introduction.............................................................................. 375

D. Advanced Hardware Introduction.............................................................................. 389

E. Troubleshooting Introduction.............................................................................. 399

x 2005 MicroStrategy, Inc.

LDAP frequently asked questions........................................ 409

F. Example of a Modified Introduction.............................................................................. 411

Glossary ................................................................................... 421

Index ......................................................................................... 427

2005 MicroStrategy, Inc. xi

xii 2005 MicroStrategy, Inc.

The MicroStrategy Installation and Configuration Guide

It assumes a basic understanding of how to use UNIX either

The appendixes contain the following additional reference

configuring ODBC and DSNs

warehouse catalog usage and settings

hardware related configuration information

modified web.xml file example

2005 MicroStrategy, Inc. xiii

Technical terms that need more clarification are defined in

Who should use this guide

the nature and structure of the data to use for your

the basics of the UNIX operating system

configure Intelligence Server and Web Universal for use

xiv Who should use this guide 2005 MicroStrategy, Inc.

About this book

all MicroStrategy components

installation and configuration procedures

troubleshooting and maintenance guidelines

Each chapter begins with a brief overview of the content

The appendixes contain additional reference information,

For online and printed documentation

2005 MicroStrategy, Inc. About this book xv

bold button names, check boxes, dialog boxes,

italic new terms defined within the text and in the

UPPERCASE keyboard command key (such as ENTER)

+ A keyboard command that calls for the use of more

xvi Typographical standards 2005 MicroStrategy, Inc.

For printed documentation only

References to screen elements and keys that are the focus of

1 Click Select Warehouse.

References to code, formulas, or calculations within