Xi31 Bip Pattern Win en

BusinessObjects Enterprise XI 3.
1
Pattern Book for Windows
BusinessObjects Enterprise XI 3.0
Copyright
2009 SAP BusinessObjects. All rights reserved. SAP BusinessObjects owns

the following United States patents, which may cover products that are offered and
licensed by SAP BusinessObjects and/or affiliated companies: 5,295,243;
5,339,390; 5,555,403; 5,590,250; 5,619,632; 5,632,009; 5,857,205; 5,880,742;
5,883,635; 6,085,202; 6,108,698; 6,247,008; 6,289,352; 6,300,957; 6,377,259;
6,490,593; 6,578,027; 6,581,068; 6,628,312; 6,654,761; 6,768,986; 6,772,409;
6,831,668; 6,882,998; 6,892,189; 6,901,555; 7,089,238; 7,107,266; 7,139,766;
7,178,099; 7,181,435; 7,181,440; 7,194,465; 7,222,130; 7,299,419; 7,320,122 and
7,356,779. SAP BusinessObjects and its logos, BusinessObjects, Crystal Reports,
Rapid Mart, Data Insight, Desktop Intelligence, Rapid Marts, Watchlist
Security, Web Intelligence, and Xcelsius are trademarks or registered
trademarks of Business Objects, an SAP company and/or affiliated companies in
the United States and/or other countries. SAP is a registered trademark of SAP
AG in Germany and/or other countries. All other names mentioned herein may be
trademarks of their respective owners.
2009-01-23
Contents
Chapter 1
Preface
About this book............................................................................................8

Comments welcome....................................................................................9
Chapter 2
Introduction to patterns
11
Windows pattern overview.........................................................................12

Windows pattern security...........................................................................15
Central Management Server................................................................15
Security plug-ins...................................................................................15
User authentication and authorization..................................................16
Network security...................................................................................17
Auditing................................................................................................18
Additional security measures...............................................................19
Redundancy...............................................................................................19
Scalability...................................................................................................20
Chapter 3
Decommissioning XI R2
21
Uninstalling XI R2 from the cluster machines............................................22

Chapter 4
Deploying the Windows pattern
25
Overview....................................................................................................26
Configuring firewalls..................................................................................28
Resetting the firewall to all ports closed ..............................................29
Configuring Firewall1............................................................................30
BusinessObjects Enterprise XI 3.1 Pattern Book for Windows
Contents
Configuring iptables..............................................................................49
Configuring the database server to static port 1521............................52
Registering fixed port numbers for BusinessObjects servers..............53
Setting up the CMS database....................................................................54
Creating a new user account for the XI 3.1 repository on BOEDB......54
Setting up the database client...................................................................61
Uninstalling the Oracle 9.2 client..........................................................62
Setting up the Oracle 10.2 client..........................................................68
Setting up the BusinessObjects server cluster .........................................71
Preinstallation ......................................................................................72
Installing and configuring BusinessObjects Enterprise servers as
cluster...................................................................................................73
Configuring XI 3.1 with LDAP...............................................................81
Adding a new BusinessObjects server.................................................88
Setting up the File Repository Server........................................................89
Setting up the auditing database...............................................................92
Configuring auditing on the cluster machines......................................93
Enabling auditing..................................................................................95
Enabling auditing on the application....................................................97
Enabling auditing on the servers..........................................................99
Importing sample audit reports and universes...................................102
Setting up the application server.............................................................103
Uninstalling the older version of Tomcat............................................103
lnstalling the Web Component Adapter (WCA)..................................105
Enabling the AJP 1.3 Connector in Tomcat........................................110
Introduction to application server clustering.......................................111
Configuring the application servers to use the CMS cluster..............113
Setting up the web servers......................................................................115
Uninstalling Apache version 2.0.59....................................................115
Installing and configuring Apache version 2.2.9.................................117
Contents
Configuring each of the Apache HTTP servers, http1 and http2, with
Tomcat................................................................................................118
Failover...............................................................................................121
Configuring the reverse proxy.................................................................122
Load balancer setup................................................................................124
Creating HTTP services on the load balancer...................................125
Sticky cookie configuration.................................................................127
Verifying the load balancer configuration...........................................128
Chapter 5
Installing and deploying Performance Management components 131

Overview..................................................................................................132
Installing Performance Management components..................................132
Configuring Performance Manager.........................................................135
Creating a target database connection..............................................136
Setting up the Performance Manager repository...............................138
Adding a universe to the Performance Manager repository...............142
Creating a calendar............................................................................143
Chapter 6
Microsoft clustering for FRS failover
147
Microsoft clustering for FRS failover........................................................148

Adding and configuring the systems to work in the domain...............150
Configuring the disks..........................................................................156
Installing StarWind.............................................................................160
Configuring StarWind.........................................................................162
Installing StarPort...............................................................................164
Configuring StarPort...........................................................................168
Windows clustering............................................................................171
Adding nodes to the cluster................................................................176
Configuring FRS to work with Windows cluster - Changing cluster
Quorum..............................................................................................181
Configuring the FRS Filestore disk by using the Windows cluster.....182
Contents
Updating the Filestore directory for Input and Output FRS................196

Chapter 7
Deployment and migration planning
199
Overview..................................................................................................200
CMS to CMS upgrade by using Import Wizard........................................201
Migrating content from XI R2 to XI 3.1 by using Import Wizard:
CMS-To-CMS method........................................................................201
First phase - Migrating 10 percent of the applications.......................201
Second phase - Migrating 90 percent of the applications .................216
Chapter 8
Functional investigation
231
Issue faced while importing users...........................................................232

Issue faced while mapping FRS for the clusters.....................................236
LDAP users and groups migration failed.................................................238
Issues faced while configuring the AD domain .......................................241
Appserv2 failed to start and stop properly...............................................244
ClusterName issue faced while configuring the AD domain....................246
Unwanted folder BOEXIR3_1 was created in Cluster2 and Cluster3......248
Sessions page in CMC displays HTTP Status 500.................................249
Chapter 9
System specifications
253
Chapter 10
List of machines and access information
261
Chapter 11
Acceptance testing
269
Acceptance testing workflow...................................................................270

Appendix A
Get More Help
285
Preface
Preface
About this book
About this book

The BusinessObjects XI 3.1 Pattern Book for Windows is intended to provide
Business Objects customers with enhanced documentation to aid in planning,
deployment, and upgrading of BusinessObjects Enterprise systems.
This book documents a specific end-to-end BusinessObjects Enterprise
deployment that runs in a Windows server environment. It includes
Infrastructure topology, setup instructions, configuration, migration,
performance tuning steps, and troubleshooting information.
The deployment scenario we followed in this Pattern is a migration of
applications from BusinessObjects XI Release 2 environment to
BusinessObjects XI 3.1 environment.
We re- used the existing infrastructure on which the BusinessObjects
XI Release 2 Windows Pattern Book
deployment is setup. We
removed the existing database client software and installed the
latest supported database client software . We performed a new
installation of BusinessObjects XI 3.1 on the existing
systems
where the BusinessObjects XI
Release 2 deployment is running
and
then migrated the data
in 2
stages
from
BusinessObjects XI Release 2 environment to
BusinessObjects XI 3.1 environment.
Once the migration of applications is complete, we
uninstalled the BusinessObjects XI Release 2
deployment.
It can be used as a guide for planning and deployment of BusinessObjects
Enterprise systems, or as a reference for setup and configuration of individual
system components. It is best used in conjunction with BusinessObjects XI
Release 2 installation, deployment, and administration documentation.
Functional and performance results reported in this book are dependant
upon full deployment of the Windows pattern, as documented.
Preface
Comments welcome
Related Links:
Introduction to patterns on page 11
Comments welcome
Your feedback is important to us. You can send your comments about this
book to: jc.raveneau@sap.com
Preface
Comments welcome
10
Windows pattern overview
In the context of Business Objects products, a pattern refers to the system

topology that represents a typical deployment of a BusinessObjects Enterprise
system. It also includes various components that integrate with the
BusinessObjects Enterprise system.
In this document, a pattern refers to a BusinessObjects Enterprise system
that runs on a Windows server environment. It is integrated with a content
switch, a reverse proxy server, an authentication server, two web servers,
two application servers, and two database servers.
The Windows pattern provides insight into system architecture and component
integration.
Note:
The use of a particular vendor's products in the Windows pattern

documentation is not intended as an endorsement. BusinessObjects
Enterprise supports a variety of vendor applications. Future pattern
documentation will mention other commonly used components from different
vendors.

This section provides a high-level overview of the Windows pattern.
The following diagram depicts a typical BusinessObjects Enterprise
deployment:
12
A typical BusinessObjects Enterprise deployment comprises the following

layers:
13
External layer
The external layer comprises a BusinessObjects client, a reverse proxy

server that is located outside the corporate firewall, and a load balancer that
distributes requests received from end-user systems.
The BusinessObjects client is a Windows desktop machine that accesses
BusinessObjects applications by using a web browser. Owing to security
constraints, only Web Intelligence applications are available from the
browser-based client, which is represented in the Windows pattern diagram.
The BusinessObjects client products are installed only on the Cluster3
machine.
The reverse proxy machine runs Apache HTTP Server 2.2. This machine
includes two network cards (NICs). One network card is used to communicate
with clients, and the other is used for internal communication. The two
network-card configuration conceals internal IP addresses.
The load balancer is a Cisco Content Services Switch. It distributes client
requests between the two web servers.
Web server layer
The web server layer consists of two systems and both these systems run
Apache HTTP Server 2.2.
Application server layer
The application server layer includes two application server machines and
an authentication server. The application server machines, which are
clustered together, run Tomcat 5.5. The authentication server runs Active
Directory Application Mode (ADAM).
BusinessObjects Enterprise layer
The BusinessObjects Enterprise layer includes a three-server cluster that

runs BusinessObjects Enterprise XI 3.1, and a separate server that hosts
the BusinessObjects Central Management Server (CMS) repository, the
auditing repository, and the File Repository Server (FRS) share.
An Oracle 10g R2 client is installed on each of the BusinessObjects servers.
The Oracle client allows the BusinessObjects servers to access databases
and repositories.
14
Windows pattern security
Data layer
The data layer includes the Oracle database server that hosts the corporate
database.

Basic security measures for a BusinessObjects Enterprise system typically
include managing user access, user rights, network security, and auditing.
The following sections discuss the security features supported in the Windows
pattern.
Central Management Server

The Central Management Server (CMS) performs a number of important
tasks related to the management of security, objects, servers, and auditing.
Many of these tasks depend on the repository that the CMS uses to store
BusinessObjects Enterprise system data. This data includes security
information, such as user accounts, group memberships, and object rights
that define user and group privileges.
When you set up your BusinessObjects Enterprise XI 3.1 system, the CMS
allows you to create user accounts and groups within BusinessObjects
Enterprise. The CMS also allows you to use the existing user accounts and
groups that are stored in third-party systems, such as Windows NT user
databases, LDAP directory servers, or Windows AD servers. The Windows
pattern uses an LDAP-based authentication server.
Security plug-ins
Security plug-ins expand and customize the ways in which BusinessObjects
Enterprise authenticates users. In addition to the default system authentication
BusinessObjects Enterprise security plug-in, additional security plug-ins are
provided that allow you to map Business Objects Enterprise user accounts
and groups to the list of users and groups present in other authentication
servers. These additional security plug-ins are managed by using Windows
NT, Windows Active Directory servers, and LDAP directory servers.
15
Each security plug-in acts as an authentication provider, which verifies user

credentials against the appropriate database. When users log into XI 3.1
InfoView, they choose from the available authentication types that you have
enabled. As part of this Windows pattern deployment, we will configure
BusinessObjects to use the LDAP authentication type.
For more information about security plug-ins, see the BusinessObjects
Enterprise XI 3.1 Administrator's Guide.
User authentication and authorization

Authentication refers to the process of verifying the identity of a user who
attempts to access the system, and authorization refers to the process of
verifying whether the user has sufficient rights to perform an action on a
specified object.
Authentication
BusinessObjects Enterprise supports the following authentication methods:

BusinessObjects Enterprise authentication (default)
Windows NT authentication
LDAP authentication
Windows AD authentication
BusinessObjects Enterprise, Windows NT, Windows AD, and LDAP
authentication methods are supported through security plug-ins.
Authorization
In BusinessObjects Enterprise, authorization is managed through a system

of user rights. Rights are the base units for controlling access to objects,
users, applications, servers, and other features in BusinessObjects Enterprise.
Rights play an important role in securing the system by specifying the
individual actions that users can perform on objects.
This document does not discuss how to define user rights. For information
about defining user rights, see the BusinessObjects Enterprise XI 3.1
Administrator's Guide.
16
Network security
Ensuring the integrity of the network within which your BusinessObjects
Enterprise system operates is a critical part of the overall system security.
The Windows pattern implements a number of network security measures,
including a reverse proxy server and a set of firewalls.
Reverse proxy server

A reverse proxy is typically deployed in front of the web server layer. Incoming
connections addressed to a web server are routed through the proxy server,
which may either respond to the request directly, or forward the request
completely or partially to the other web server.
Firewalls
A firewall is used to regulate the communication between computer networks
of different trust levels by containing or delaying a security breach. For
example, firewalls are used to regulate communication between external
networks such as the Internet (no trust), and a trusted internal computing
network.
The Windows pattern uses three internal firewalls, which filter communication
at different system layers, to provide a multi-layered defense.
BusinessObjects server communication and firewalls

The CMS is a key component in the BusinessObjects Enterprise architecture.
The directory listing service provided by the CMS is of particular importance
to firewall integration.
When a BusinessObjects Enterprise server starts, a port number is
dynamically assigned to it, and when the server connects to the
BusinessObjects Enterprise framework, it registers its IP address and port
number with the CMS. When one BusinessObjects Enterprise server needs
to communicate with another, it first contacts the directory listing service on
the CMS to obtain connection information. The first server then uses this
information to communicate directly with the second server.
17
The default behavior of BusinessObjects Enterprise is to dynamically assign

port numbers for its servers. However, in a distributed environment that
employs firewalls, you must modify this default behavior.
Note:
In a BusinessObjects Enterprise environment, the CMS and the remaining

BusinessObjects Enterprise server components must not be separated by
firewalls. You must ensure that the CMS and other BusinessObjects
Enterprise server components share the same tier. The Windows pattern
respects this requirement with the exception of the BusinessObjects Web
Component Adapter (WCA), which is installed in the application server layer.
Windows pattern firewall implementation

In the Windows pattern, firewalls regulate the transmission of data between
the application server layer, the BusinessObjects Enterprise layer, and the
data layer.
BusinessObjects Enterprise supports packet filtering firewalls, Network
Address Translation (NAT) firewalls, and SOCKS proxy firewalls. The
Windows pattern deployment uses only the packet filtering firewalls.
Packet filtering firewalls function by accepting or rejecting data transmissions
based on information included in the TCP/IP data packets. This information
may include the following types of data:
the address the data is coming from
the address the data is going to
the session and application ports being used to transfer the data
Auditing
BusinessObjects Enterprise provides insight into your system by recording
web activity and by allowing you to monitor its details. You can select web
attributes, such as time, date, IP address, and port number, that you want
to record. The audit data is logged to auditing disks and stored in
comma-delimited text files, so that you can easily report off the data or import
it other applications. The Windows pattern deployment includes an auditing
database.
18
Redundancy
Additional security measures

BusinessObjects Enterprise provides a number of additional security
capabilities, apart from those discussed in this chapter. For more information
about the BusinessObjects Enterprise security framework, see the
BusinessObjects Enterprise XI 3.1 Administrator's Guide and the
BusinessObjects Enterprise XI 3.1 Deployment and Configuration Guide.
Redundancy
Building redundancy into your BusinessObjects Enterprise System requires
the elimination of single points of failure.
Redundancy for BusinessObjects Enterprise servers is provided by a cluster
of three machines. The server cluster includes at least two of each
BusinessObjects service running on more than one machine. With this
configuration, BusinessObjects services remain available even if any one of
the three servers fails.
For a truly fault-tolerant BusinessObjects Enterprise system, the resources
that BusinessObjects Enterprise depends on must also support redundancy.
The Windows pattern uses two web servers and two application servers.
Each web server is configured to an application server. If one web server
fails, the load balancer is configured to route the requests to the functioning
web server.
The Windows pattern uses two application servers that are clustered together
and configured for load balancing. If one of the clustered application servers
fails, the load balancer routes the requests to the functioning application
server.
Other critical resources that must support redundancy measures include the
CMS database server, the File Repository Server (FRS) share, and the
corporate data server.
As part of the typical system operations, the CMS servers on the
BusinessObjects cluster send thousands of small queries to the CMS
repository. If an issue occurs in the CMS repository, then the performance
impact becomes visible to all system users, and if the CMS repository is
offline, the entire BusinessObjects system becomes unavailable. Clustering
19
Scalability
the database server that hosts the CMS repository will help you ensure
system availability.
It is also recommended that a Storage Area Network (SAN) be used for the
FRS share. A cluster of Windows file servers is an alternative if a SAN is not
available.
Scalability
There are many factors that can impact system scalability, including system
design, hardware, configuration, and tuning.
Scalability can also be achieved by improving the efficiency of reports,
increasing reporting capacity, enhancing web applications, and optimizing
the database and network.
From a system design perspective, the Windows pattern includes:
A BusinessObjects server cluster
A Cisco load balancer
Two web servers
Two application servers
Microsoft clustering for high availability of FRS
Tomcat Application Server clustering
Hardware resources used in the Windows pattern include a dual processor,
3.2 GHz server machines with 2 to 4 GB of memory, and 75 GB of disk
space.
20
Uninstalling XI R2 from the cluster machines
Uninstalling XI R2 from the cluster

machines
This section describes how to uninstall BusinessObjects Enterprise XI R2
from the cluster machines.
We decided to uninstall XI R2, starting with the Cluster 3 machine. The XI
R2 installation is at the SP3 FP3.2 level. To uninstall XI R2 completely we
first uninstalled the FP, the the SP and lastly the XI R2 base installation.
To uninstall XI R2 from a cluster machine, complete the following steps:
1. Log into the Cluster3 machine, and open the "Add or Remove Programs"
page by selecting Start > Control Panel.
The "Add or Remove Programs" page displays all the installed programs
on the machine.
2. Select Business Objects FP3.2, and click Remove.
A warning message appears asking you whether you are certain that you
want to remove the component.
3. Click Yes.
The progress bar displays the time required to uninstall the FixPack.
4. After the uninstallation of FP3.2 is complete, uninstall XI R2 SP3.
NOTE: The servers automatically restarts after the FP or SP is uninstalled.
5. Uninstall XI R2 (our Windows pattern is an SP2 Full build setup).
After some time, a dialog box appears prompting for the restart of the
system for the complete uninstallation of XI R2.
6. Click Yes.
After the system restarts, the XI R2 icons are removed from the Start
menu.
7. Manually delete the BusinessObjects install folder, because the uninstaller
does not delete all the files from the operating system. Hence, we deleted
the XI R2 install folder, BOEXIR2_SP2 from C:\.
8. By default the installer should delete all the "Business Objects" keys in
the Registry Editor. The remaining keys can be deleted by going to
Registry Editor.
22
In Registry Editor, navigate to My Computer ->

HKEY_LOCAL_MACHINE -> SOFTWARE and delete the key "Business
Objects".
We performed the same steps on machines, Cluster2 and Cluster3, to
complete the uninstallation of XI R2 on all the machines.
References:
Page 65 of BusinessObjects Enterprise Upgrade Guide xi3-1_bip_upgrade_en.pdf
23
24
Deploying the Windows

pattern

Overview
Overview
This section provides an overview of the tasks involved in deploying the
Windows pattern.
Firewall setup
The Windows pattern includes three firewalls. Setting up the firewalls involves
defining fixed port numbers for BusinessObjects Enterprise servers and
configuring firewalls to allow BusinessObjects Enterprise servers and other
system components to communicate.
Configuring firewalls on page 28
CMS database setup
In a typical BusinessObjects Enterprise installation, you provide connectivity

and credentials for an existing database server when you install
BusinessObjects Enterprise. The CMS server then creates a CMS database
on the database server. The CMS database is populated over time.
For the Windows pattern, a CMS database is set up manually, to provide a
populated CMS database for testing-related activities.
Setting up the CMS database on page 54
File Repository Server (FRS) setup
In the Windows pattern, the FRS shares the same Windows server machine
as the BusinessObjects CMS database (BOEDB). This configuration is for
testing-related activities only. In a real-time deployment, a Storage Area
Network (SAN) is recommended for the FRS. A cluster of Windows machines
set up as file servers is also an option if a SAN is not available.
Setting up the File Repository Server on page 89
Corporate database setup
In a real-time deployment, database administrators provide access to an

existing corporate database. To provide a corporate database for the
Windows pattern, a database server is installed and populated with data.
26

Overview
BusinessObjects Enterprise server cluster setup
Setting up the BusinessObjects Enterprise server cluster involves installing

BusinessObjects Enterprise on each of the three machines in the cluster and
configuring BusinessObjects Enterprise XI 3.1 with LDAP.
Setting up the BusinessObjects server cluster on page 71
Auditing database setup
A typical auditing database setup requires providing database connectivity

and credentials for an existing database during the BusinessObjects
Enterprise installation.
For the Windows pattern, an auditing database is set up manually, to provide
a populated auditing database for testing-related activities.
Setting up the auditing database on page 92
Oracle 10.2 client setup
The Oracle 10.2 client allows BusinessObjects servers to access system

databases. Setting up an Oracle 10.2 client involves uninstalling Oracle 9.2
client and installing the Oracle 10.2 client on each machine in the
BusinessObjects Enterprise server cluster.
Setting up the database client on page 61
Application server setup
Setting up the application servers involves installing the Web Component

Adapter (WCA), installing the Tomcat 5.5 application server on both the
application server machines, and configuring the AJP connector in Tomcat
5.5 to allow the application servers to communicate with the web servers.
Setting up the application server on page 103
Web server setup
Setting up the web servers includes uninstalling Apache version 2.0.59,

installing Apache 2.2.9 on both web server machines, configuring Apache
HTTP server with Tomcat, and configuring the web servers to communicate
with the application servers.
Setting up the web servers on page 115
27

Configuring firewalls
Reverse proxy configuration setup
The reverse proxy server provides system security by hiding internal IP

addresses. The reverse proxy has two network cards, one is configured for
internal communication and the other is configured for external
communication.
Configuring the reverse proxy on page 122
Load balancer setup
The Windows pattern uses a Cisco Content Services Switch (CSS) to provide
load balancing. Setting up the load balancer involves creating services on
the CSS machine for the Web servers, and configuring a sticky cookie to
ensure that clients connect to only one server during a session.
Load balancer setup on page 124
In the Windows pattern, three firewalls are used at different system layers.
Firewall configuration includes defining iptable rule sets that allow components
of the BusinessObjects Enterprise system to communicate. The iptable rule
sets defined in this section are basic examples.
In a real-time deployment, a BusinessObjects Enterprise system is typically
installed in a computing environment with existing firewalls and iptable rule
sets.
You can use the information discussed in this example during planning stages
of your deployment, to understand the firewall integration requirements for
BusinessObjects Enterprise and related components.
Setting up the firewalls involves the following tasks:
Resetting the firewall to all ports closed
Configuring Firewall1
Configuring iptables
Configuring the database server to static port 1521
Registering fixed port numbers for BusinessObjects servers
28

Resetting the firewall to all ports closed

To reset the firewall to all ports closed, complete the following steps:
1. Log into the firewall machine as the root user.
2. Verify the current firewall rule set by exporting the iptables rule set to a
flat script file. To export the default rule set, type the following command:
#Iptables-save > firewall_org
3. Verify the current configuration for IP tables in the iptables-config file. The
iptables-config file is located in /etc/sysconfig.
#cd /etc/sysconfig
#cat iptables-config
4. Flush all firewall rules. The policy of all configured tables is set to DROP.
To flush all firewall rules, type the following command:
#/sbin/service iptables panic
5. Create a new file firewall_mod by using a vi editor, as follows:

#vi firewall_mod
6. Add the following lines to the firewall_mod file:

*filter
-F
-X
-A INPUT -j REJECT
29

-A FORWARD -j REJECT
COMMIT
7. Save and exit the firewall_mod file.

8. Activate the new rule set by typing the following command:
#iptables-restore
firewall_mod
References:
BusinessObjects product guides.
Linux iptables
Linux questions
Kbase.redhat
In our pattern, Firewall1 is placed between Ethernet bus in the web server
layer and the Ethernet bus in the application server layer. The traffic in
Firewall1 consists of requests from and to the HTTP servers and the
application servers. We need to configure Firewall1 to allow this traffic.
Requirements for communication
HTTP servers are bridged with the application servers so that the HTTP
servers can communicate with the application servers.
An Apache web server is often used in front of an application server to
improve performance in high-load environments. Mod_jk allows request
forwarding to an application through a protocol called AJP. This involves
enabling mod_jk in Apache, configuring an AJP connector in your application
server, and directing Apache to forward certain paths to the application server
through mod_jk. Mod_jk is sometimes preferred to mod_proxy because AJP
is a binary protocol, and mod_jk supports both fallback and load balancing.
8009 is the default AJP connector port.
We opened port 8009 in Firewall1 because, when Tomcat or HTTP server
restarts, it tries to access the port 8009 through Firewall1.
We added the following lines in Firewall1 to open port 8009 :
30

# firewall1.txt created for FIREWALL1 on 24th November 2008

6:28 PM IST
*nat
:PREROUTING ACCEPT [5432:264153]
:POSTROUTING ACCEPT [5397:259128]
:OUTPUT ACCEPT [0:0]
COMMIT
*mangle
:INPUT ACCEPT [35:5025]
:FORWARD ACCEPT [10895:481749]
-A PREROUTING -p tcp -m tcp --tcp-flags FIN,SYN,RST,PSH,ACK,URG
FIN,PSH,URG -j DROP
NONE -j DROP
-A PREROUTING -p tcp -m tcp --tcp-flags SYN,RST SYN,RST -j DROP
-A PREROUTING -p tcp -m tcp --tcp-flags FIN,SYN FIN,SYN -j DROP
FIN,PSH,URG -j DROP
NONE -j DROP
FIN,PSH,URG -j DROP
NONE -j DROP
FIN,PSH,URG -j DROP
NONE -j DROP
COMMIT
*filter
:INPUT DROP [0:0]
:FORWARD DROP [0:0]
#Alias CDR1 chain for INPUT & FORWARD
31

:CDR1 - [0:0]
-A INPUT -j CDR1
-A FORWARD -j CDR1
#Allow in local loop 127.0.0.1
-A CDR1 -p ALL -i lo -j ACCEPT
#LOGGING
-A CDR1 -m limit --limit 60/sec -j LOG --log-level 1
--log-prefix 'CDR1_INPUT_FORWARD:'
-A OUTPUT -m limit --limit 60/sec -j LOG --log-level 1
--log-prefix 'CDR1_OUTPUT:'
#NEW means that the packet has or will start a new connection,
or that it is associated with a connection that has not seen
packets in both directions.
#RELATED means that the packet is starting a new connection
and is associated with an already established connection.
#ESTABLISHED means that the packet is part of an already
established connection that has seen packets in both directions
and is fully valid.
#ACCEPT all INPUT and FORWARD for RELATED & ESTABLISHED ports
#-A CDR1 -m state --state RELATED,ESTABLISHED -m limit --limit
60/sec -j LOG --log-level 1 --log-prefix
'CDR3_RELATED_ESTABLISHED:'
-A CDR1 -m state --state RELATED,ESTABLISHED -j ACCEPT
# HTTP1 to APPSERVERS AJP13 connector.
when Tomcat/HTTP restarts
-A CDR1 -p tcp -s 192.168.1.11 --sport
192.168.2.11 --dport 8009 -j ACCEPT
-A CDR1 -p tcp -s 192.168.1.11 --sport
192.168.2.12 --dport 8009 -j ACCEPT
-A CDR1 -p tcp -s 192.168.2.11 --sport
--dport 1024:65535 -j ACCEPT
-A CDR1 -p tcp -s 192.168.2.12 --sport
Searches for the port
# HTTP2 to APPSERVERS AJP13 connector.

when Tomcat/HTTP restarts
-A CDR1 -p tcp -s 192.168.1.12 --sport
192.168.2.11 --dport 8009 -j ACCEPT
-A CDR1 -p tcp -s 192.168.1.12 --sport
192.168.2.12 --dport 8009 -j ACCEPT
-A CDR1 -p tcp -s 192.168.2.11 --sport
-A CDR1 -p tcp -s 192.168.2.12 --sport
Searches for the port
1024:65535 -d
1024:65535 -d
8009 -d 192.168.1.11
8009 -d 192.168.1.11
1024:65535 -d
1024:65535 -d
8009 -d 192.168.1.12
8009 -d 192.168.1.12
#From here do not allow any INPUT/FORWARD port to pass through

which does not meet the above conditions
--log-prefix 'CDR1_DROPPED:'
32

-A CDR1 -j DROP
COMMIT
#Some Commands
#Logging to be viewed as [root@firewall1 ~]tail -f
/var/log/messages | grep "CDR1_OUTPUT:"
#iptables-restore < firewall1.txt
#iptables-save
#service iptables save
#iptables -L -nvx
#iptables -L
Routing:
[root@firewall1 ~]route -n
Kernel IP routing table
Destination
Gateway
Ref
Use Iface
192.168.4.0
192.168.2.254
0
0 eth1
192.168.3.0
192.168.2.254
0
0 eth1
192.168.2.0
0.0.0.0
0
0 eth1
192.168.1.0
0.0.0.0
0
0 eth0
169.254.0.0
0.0.0.0
0
0 eth1
0.0.0.0
192.168.2.254
0
0 eth1
Genmask
Flags Metric
255.255.255.0
UG
255.255.255.0
UG
255.255.255.0
255.255.255.0
255.255.0.0
0.0.0.0
UG
[root@firewall1 ~]route add -net 192.168.4.0/24 gw 192.168.2.254

dev eth1
[root@firewall1 ~]route del -net 192.168.2.0/24
[root@firewall1 ~]ip address show dev eth1
[root@firewall1 ~]ip route show dev eth1 table local
[root@firewall1 ~]route -v
[root@firewall1 ~]ip route
[root@firewall1 ~]netstat -r
A routing table contains three types of entries: entries for a specific host,
entries for all hosts on a specific network, and entries for any destination not
matched by entries of the first two types (a wildcard route). The various types
of routes are determined by the flags field of the display from netstat. The
flags field is either U, UG, UH, or UGH. The U flag is always present. The G
flag indicates a route that uses a gateway and is accompanied by a hop
count. If a route is defined through a remote gateway, the hop count must
be greater than zero. If no G flag is present, it indicates a route that does
33

not use a remote gateway. The H flag indicates a route to a host. If the H
flag is absent, it indicates a route to a network.
References:
ch-routing
routing tables
In our pattern network topology, Firewall2 is placed between the Ethernet
bus in the application server layer and the Ethernet bus in the BOE layer.
The traffic in Firewall2 consists mostly of requests from and to the application
servers, the authentic server, the BOE servers, BOEDB, and the FRS server.
We need to configure Firewall2 to allow this traffic.
Authentic.EDI.COM is the domain controller. Cluster1, Cluster2, Cluster3,

and BOEDB are in the EDI.COM domain. The machines Cluster1, Cluster2,
and Cluster3 are components of a cluster. Firewall2 must transmit all the
necessary communication for this AD domain and Microsoft cluster to work.
The CMS uses two ports, namely, the Name Server Port and the Request
Port. The web application servers that host the BusinessObjects Enterprise
SDK must be able to initiate communication with the Central Management
Server (CMS) on both the ports.
The web application server that hosts the BusinessObjects Enterprise SDK
must be able to initiate communication with the Request Port of each
BusinessObjects Enterprise server.
Ports for Windows AD Domain and MSFT Clustering Functionality
Client computers and domain controllers that are located in common or

external forests have service dependencies, so that user-initiated and
computer-initiated operations, such as domain join, logon authentication,
remote administration, and Active Directory replication, work correctly. Such
services and operations require network connectivity over specific port and
networking protocols.
34

A summarized list of services, ports, and protocols required for member

computers and domain controllers to interoperate with each other to access
Active Directory include, but are not limited to, the following:
Active Directory/LSA
Computer Browser
Distributed File System
DNS
File Replication Service
Kerberos Key Distribution Center
Net Logon
Remote Procedure Call (RPC)
Server
Active Directory (Local Security Authority)
Active Directory runs under the LSASS process and includes the
authentication and replication engines for Windows 2000 and Windows
Server 2003 domain controllers. Domain controllers, client computers, and
application servers require network connectivity to Active Directory over
specific hard-coded ports, in addition to a range of ephemeral TCP ports
between 1024 and 65535, unless a tunneling protocol is used to encapsulate
such traffic. An encapsulated solution can consist of a VPN gateway located
behind a filtering router that uses Layer 2 Tunneling Protocol (L2TP) together
with IPSec.
System service name: LSASS
Application Protocol
Protocol
Ports
LDAP Server
TCP
389
LDAP Server
UDP
389
RPC
TCP
135
RPC randomly allocated

TCP
high TCP ports
1024-65535*
35

Computer Browser
The Computer Browser system service maintains an up-to-date list of

computers on your network and supplies the list to programs that request it.
This service is used by Windows-based computers to view network domains
and resources. Computers that are designated as browsers maintain browse
lists that contain all shared resources that are used on the network.
System service name: Browser
Protocol
Ports
NetBIOS Datagram SerUDP

vice
138
NetBIOS Name ResoluUDP

tion
137
NetBIOS Session Service TCP
139
Distributed File System
The Distributed File System (DFS) integrates disparate file shares that are
located across a local area network (LAN) or a wide area network (WAN)
into a single logical namespace. The DFS service is required for Active
Directory domain controllers to advertise the SYSVOL shared folder.
System service name: Dfs
36
Protocol
Ports

vice
138
139
LDAP Server
TCP
389
LDAP Server
UDP
389
SMB
TCP
445

Protocol
Ports
RPC
TCP
135
Randomly allocated high

TCP
TCP ports
random port number between 1024 - 65535*
DNS Server
The DNS Server service enables DNS name resolution by answering queries
and updating requests for DNS names. DNS servers are required to locate
devices and services that are identified by using DNS names and also locate
the domain controllers in the Active Directory.
System service name: DNS
Protocol
Ports
DNS
UDP
53
DNS
TCP
53
File Replication
The File Replication service (FRS) is a file-based replication engine that

automatically copies updates to files and folders between computers that
are participating in a common FRS replica set. FRS is the default replication
engine that is used to replicate the contents of the SYSVOL folder between
Windows 2000-based domain controllers and Windows Server 2003-based
domain controllers that are located in a common domain. FRS may be
configured to replicate files and folders between targets of a DFS root or link
by using the DFS Administration tool.
System service name: NtFrs
Protocol
Ports
RPC
TCP
135
37

Protocol

TCP
TCP ports
Ports
Kerberos Key Distribution Center
When you use the Kerberos Key Distribution Center (KDC) system service,
users can log into the network by using the Kerberos version 5 authentication
protocol. The KDC is a single process that provides two services: the
Authentication Service and the Ticket-Granting Service. The Authentication
Service issues Ticket-Granting Tickets, and the Ticket-Granting Service
issues tickets to connect to computers in its own domain.
System service name: kdc
Protocol
Ports
Kerberos
TCP
88
Kerberos
UDP
88
Net Logon
The Net Logon system service maintains a security channel between your
computer and the domain controller, to authenticate users and services. This
service sends the user's credentials to a domain controller and returns the
domain security identifiers and user rights to the user. This is typically referred
to as pass-through authentication. Net Logon is configured to start
automatically only when a member computer or domain controller is joined
to a domain. In the Windows 2000 Server and Windows Server 2003 families,
Net Logon publishes service resource locator records in the DNS. When this
service runs, it relies on the Server service and the Local Security Authority
service to listen for incoming requests. On domain member computers, Net
Logon uses RPC over named pipes. On domain controllers, it uses RPC
over named pipes, RPC over TCP/IP, mailslots, and Lightweight Directory
Access Protocol (LDAP).
System service name: Netlogon
38

Protocol
Ports

vice
138

tion
137
139
SMB
TCP
445
RPC
TCP
135, random port number

between 1024 - 65535*
Remote Procedure Call (RPC)
The Remote Procedure Call (RPC) system service is an interprocess

communication (IPC) mechanism that enables data exchange and invocation
of functionality that resides in a different process. The different processes
can be on the same computer, on the LAN, or in a remote location, and can
be accessed over a WAN connection or over a VPN connection. The RPC
service functions as the RPC endpoint mapper and Component Object Model
(COM) Service Control Manager. Many services depend on the RPC service
to start successfully.
System service name: RpcSs
Protocol
Ports
RPC
TCP
135

vice
138

tion
137
139
SMB
445
TCP
39

Server
The Server system service provides RPC support and file, print, and named
pipe sharing over the network. This service allows the sharing of local
resources, such as disks and printers, so that other users on the network
can access them. It also allows named pipe communication between
programs that are running on the local computer and on other computers.
Named pipe communication refers to memory that is reserved for the output
of one process to be used as input for another process. The input-accepting
process does not have to be local to the computer.
System service name: lanmanserver
Protocol
Ports

vice
138

tion
137
139
SMB
445
TCP
Active Directory Application Mode (ADAM)
Active Directory Application Mode (ADAM) is a new mode of Active Directory.

It is designed specifically for directory-enabled applications. ADAM is a
Lightweight Directory Access Protocol (LDAP) directory service that runs as
a user service, rather than as a system service. You can run ADAM on
servers and domain controllers running operating systems in the Windows
Server 2003 family (except for Windows Server 2003, Web Edition) and also
on client computers running Windows XP Professional.
We are using ADAM with BusinessObjects for LDAP authentication. We
have configured port 20000 for ADAM.
40
Protocol
Ports
LDAP
TCP
20000

Protocol
Ports
LDAP
UDP
20000
Cluster Service
The Cluster Service controls server cluster operations and manages the
cluster database. A cluster is a collection of independent computers that act
as a single computer. Managers, programmers, and users view the cluster
as a single system. The software distributes data among the nodes of the
cluster. If a node in a cluster fails, other nodes provide the services and data
that was formerly provided by the missing node. When a node is added or
repaired, the cluster software migrates some data to that node.
System service name: ClusSvc
Protocol
Ports
Cluster Services
UDP
3343
RPC
TCP
135
Cluster Administrator
UDP
137

TCP
TCP ports
Ports for communication between CMS and application servers
The Central Management Server (CMS) maintains a database of information

about your BusinessObjects Enterprise system. This is known as the CMS
database. All platform services are managed and controlled by the CMS.
The CMS also manages access to the system file store where the physical
documents are managed.
The CMS uses two ports, namely, the Request Port and the Name Server
Port. The Request Port is selected dynamically by default. The Name Server
Port is 6400 by default. We set the Name Server Port to 7400.
We need to configure the Request Port to a static port. For information on
configuring the Request port, see Resetting the firewall to all ports closed
41

on page 29, Registering fixed port numbers for BusinessObjects servers on

page 53, and Adding a new BusinessObjects server on page 88. We have
configured the ports as follows:
CMS Name Server Port: 7400
CMS Request Port: 7413
We must allow the traffic between the application servers and the BOE
servers at ports 7400 and 7413.
Ports for communication between BusinessObjects servers and application
servers
When started and enabled, each BusinessObjects Enterprise server

dynamically binds to an available port (higher than 1024), registers with this
port on the CMS, and then listens for BusinessObjects Enterprise requests.
A specific Request Port number must be configured for servers that
communicate with other BusinessObjects Enterprise components across a
firewall.
BusinessObjects Enterprise servers initially contact the CMS on its Name
Server port. The CMS responds to this initial contact by returning the value
of its Request Port. The Business Objects servers use this Request Port
number for subsequent communication with the CMS.
Firewall2 configuration file:
# firewall2.txt Created for FIREWALL2 iptables-restore v1.2.11
on Mon Nov 24 6:16 PM IST 2008
*nat
COMMIT
*filter
:INPUT DROP [0:0]
:FORWARD DROP [0:0]
:CDR2 - [0:0]
-A INPUT -j CDR2
-A FORWARD -j CDR2
42

#LOGGING
and is fully valid.
#For Mircrosoft Domain and clustering. A maximum of 15 separate
ports may be specified. Port Range 1024:65535 cannot be defined
along multiport match
#Client Port(s) -- Server Port
-- Service
#1024-65535/TCP
-- 135/TCP
-- RPC
#1024-65535/TCP
-- 1024-65535/TCP
-- LSA RPC
Services (*)
#1024-65535/TCP/UDP -- 389/TCP/UDP -- LDAP
#1024-65535/TCP/UDP -- 20000/TCP/UDP
-- LDAP (ADAMS)
#53,1024-65535/TCP/UDP -- 53/TCP/UDP
-- DNS
#1024-65535/TCP/UDP -- 88/TCP/UDP
-- Kerberos
#1024-65535/TCP
-- 445/TCP
-- SMB
#TCP
-A CDR2 -p tcp -m iprange --src-range 192.168.3.11-192.168.3.14
-d 192.168.2.13 -m multiport --dport
53,389,20000,139,445,135,88 -j ACCEPT
-A CDR2 -p tcp -s 192.168.2.13 -m multiport --sport
53,389,20000,139,445,135,88 -m iprange --dst-range
192.168.3.11-192.168.3.14 -j ACCEPT
--sport 1024:65535 -d 192.168.2.13 --dport 1024:65535 -j ACCEPT
#UDP
-A CDR2 -p udp -s 192.168.2.13 -m multiport --sport
53,389,20000,137,138,3343,88 -m iprange --dst-range
192.168.3.11-192.168.3.14 -j ACCEPT
-A CDR2 -p udp -m iprange --src-range 192.168.3.11-192.168.3.14
-d 192.168.2.13 -m multiport --dport
53,389,20000,137,138,3343,88 -j ACCEPT
-A CDR2 -p udp -m iprange --src-range 192.168.3.11-192.168.3.14
--sport 1024:65535 -d 192.168.2.13 --dport 1024:65535 -j ACCEPT
43

#BOBJE multiple destination ports from APPSERVER1. A maximum

of 15 separate ports may be specified.
-A CDR2 -p tcp -m multiport --dport
7400,7401,7402,7403,7404,7405,7406,7407,7408,7409,7410,7411,7412,7413,7414
-m iprange --dst-range 192.168.3.11-192.168.3.13 -s
192.168.2.11 -j ACCEPT
7415,7416,7417,7418,7419,7420,7421,7422,7423,7424,7425,7426,7427,7428,7429
192.168.2.11 -j ACCEPT
-A CDR2 -p tcp -m multiport --dport 7430,7431,7432,7433 -m
iprange --dst-range 192.168.3.11-192.168.3.13 -s 192.168.2.11
-j ACCEPT
#BOBJE multiple destination ports from APPSERVER2.
7400,7401,7402,7403,7404,7405,7406,7407,7408,7409,7410,7411,7412,7413,7414
192.168.2.12 -j ACCEPT
7415,7416,7417,7418,7419,7420,7421,7422,7423,7424,7425,7426,7427,7428,7429
192.168.2.12 -j ACCEPT
-A CDR2 -p tcp -m multiport --dport 7430,7431,7432,7433 -m
iprange --dst-range 192.168.3.11-192.168.3.13 -s 192.168.2.12
-j ACCEPT
#BOBJE multiple BOBJE source ports towards APPSERVER1
-m multiport --sport
7400,7401,7402,7403,7404,7405,7406,7407,7408,7409,7410,7411,7412,7413,7414
-d 192.168.2.11 -j ACCEPT
7415,7416,7417,7418,7419,7420,7421,7422,7423,7424,7425,7426,7427,7428,7429
-d 192.168.2.11 -j ACCEPT
-m multiport --sport 7430,7431,7432,7433 -d 192.168.2.11 -j
ACCEPT
#BOBJE multiple BOBJE source ports towards APPSERVER2
7400,7401,7402,7403,7404,7405,7406,7407,7408,7409,7410,7411,7412,7413,7414
-d 192.168.2.12 -j ACCEPT
7415,7416,7417,7418,7419,7420,7421,7422,7423,7424,7425,7426,7427,7428,7429
-d 192.168.2.12 -j ACCEPT
-m multiport --sport 7430,7431,7432,7433 -d 192.168.2.12 -j
ACCEPT
#For Active Directory to function correctly through a firewall,
the Internet Control Message Protocol (ICMP) protocol must be
44

allowed through the firewall from the clients to the domain

controllers so that the clients can receive Group Policy
information.
#ICMP is used to determine whether the link is a slow link or
a fast link. ICMP is a legitimate protocol that Active
Directory uses for Group Policy detection and for Maximum
Transfer Unit (MTU) detection. The Windows Redirector also uses
ICMP to verify that a server IP is resolved by the DNS service
before a connection is made.
-A CDR2 -p icmp -m iprange --src-range 192.168.3.11-192.168.3.14
-d 192.168.2.13 -j ACCEPT
-A CDR2 -p icmp -m iprange --dst-range 192.168.3.11-192.168.3.14
-s 192.168.2.13 -j ACCEPT
-A CDR2 -j DROP
COMMIT
#Some Commands
#iptables-save
#iptables -L -nvx
#iptables -L
Routing table:
Destination
Gateway
Ref
Use Iface
192.168.4.0
192.168.3.254
0
0 eth1
192.168.3.0
0.0.0.0
0
0 eth1
192.168.2.0
0.0.0.0
0
0 eth0
192.168.1.0
192.168.2.1
0
0 eth0
169.254.0.0
0.0.0.0
0
0 eth0
0.0.0.0
192.168.2.1
0
0 eth0
Genmask
Flags Metric
255.255.255.0
UG
255.255.255.0
255.255.255.0
255.255.255.0
UG
255.255.0.0
0.0.0.0
UG
45

Sample commands:
[root@firewall2 ~]route add -net 192.168.4.0/24 gw 192.168.3.254
dev eth1
[root@firewall2 ~]route del -net 192.168.2.0/24
[root@firewall2 ~]ip address show dev eth1
[root@firewall2 ~]ip route show dev eth1 table local
[root@firewall2 ~]route -v
[root@firewall2 ~]ip route
[root@firewall2 ~]netstat -r
Note:
References:
Microsoft support
ch routing
routing-tables
In our pattern network topology, Firewall3 is placed between the Ethernet
bus in the BOE layer and Ethernet bus in the data layer. As a result, traffic
in Firewall3 consists mostly of requests from and to the BOE servers and
the corporate database server. We need to configure Firewall3 to allow this
traffic.
The BOE servers and the Oracle 10g corporate database server must be
able to communicate with each other to generate and refresh reports.
46

Ports for communication between the BOE servers and the corporate
database server
CORPDATA is the Oracle database server. This server contains the data
that we need to create reports and analytics. For tnsping and initial
communication, Oracle uses 1521. However, after the connection is
established, it uses any random port from 1024 to 65535. We modified the
Oracle database to use only 1521 for communication. For information on
configuring the Oracle database server, see Setting up the database client
on page 61
Firewall3 configuration file:
# firewall3.txt Created for FIREWALL3 iptables-restore v1.2.11
on Mon Nov 24 6:16 PM IST 2008
*nat
-A POSTROUTING -o eth0
-A POSTROUTING -o eth1
COMMIT
*filter
:INPUT DROP [0:0]
:FORWARD DROP [0:0]
:CDR3 - [0:0]
-A INPUT -j CDR3
-A FORWARD -j CDR3
#LOGGING
and is fully valid.
47


#Below are the restriction for access to Oracle 9i database
CORPDATA
--sport 1024:65535 -d 192.168.4.2 --dport 1521 -j ACCEPT
-A CDR3 -p tcp -s 192.168.4.2 --sport 1521 -m iprange
--dst-range 192.168.3.11-192.168.3.13 --dport 1024:65535 -j
ACCEPT
-A CDR3 -j DROP
COMMIT
#Some Commands
#iptables-save
#iptables -L -nvx
#iptables -L
Routing table:
Destination
Gateway
Ref
Use Iface
192.168.4.0
0.0.0.0
0
0 eth1
192.168.3.0
0.0.0.0
0
0 eth0
192.168.2.0
192.168.3.1
0
0 eth0
192.168.1.0
192.168.3.1
0
0 eth0
169.254.0.0
0.0.0.0
0
0 eth1
0.0.0.0
192.168.3.1
0
0 eth0
48
Genmask
Flags Metric
255.255.255.0
255.255.255.0
255.255.255.0
UG
255.255.255.0
UG
255.255.0.0
0.0.0.0
UG

Sample code:
[root@firewall3
dev eth0
[root@firewall3
[root@firewall3
[root@firewall3
[root@firewall3
[root@firewall3
[root@firewall3
~]route add -net 192.168.2.0/24 gw 192.168.3.1

~]route del -net 192.168.2.0/24
~]ip address show dev eth1
~]ip route show dev eth1 table local
~]route -v
~]ip route
~]netstat -r
References:
Microsoft support
ch routing
routing-tables
Configuring iptables
To configure iptables, complete the following steps:
1. Log into the firewall machine as a root user, and type the following
commands to view the current configuration:
[root@firewall2 ~]iptables -L -nvx
[root@firewall2 ~]iptables -L
2. Save the default firewall rule set by exporting the IPTABLES rule set to
a flat script file. In this example, the default iptables rule set is saved to
49

a file named firewall_org. To export the default rule set, type the following
command:
[root@firewall2 ~]iptables-save > firewall_org
3. Flush and delete the existing firewall rules by typing the following
commands:
[root@firewall2 ~]iptables -F
[root@firewall2 ~]iptables -X
4. Create a file to contain a new iptables rule set. In this example, the
following command is used to create a new file named firewall_new:
[root@firewall2 ~]vi firewall_new
5. Add the following lines at the start of the file:

*filter
#Default policy is set to drop all INPUT/FORWARD packets and
accept all OUTPUT data packets
:INPUT DROP [0:0]
:FORWARD DROP [0:0]
#Alias CDR2 chain created for INPUT & FORWARD
:CDR2 - [0:0]
-A INPUT -j CDR2
-A FORWARD -j CDR2
-A CDR2 -p ALL -I lo -j ACCEPT
#LOGGING
-A CDR2 -m limit --limit 60/sec -j LOG --log-level 1 --logprefix 'CDR2_INPUT_FORWARD:'
-A OUTPUT -m limit --limit 60/sec -j LOG --log-level 1 -log-prefix 'CDR2_OUTPUT:'
#NEW means that the packet has or will start a new connec
tion, or that it is associated with a connection that has
not seen packets in both directions.
established connection that has seen packets in both direc
tions and is fully valid.
-A CDR2 -m state --state RELATED,ESTABLISHED -m limit -limit 60/sec -j LOG --log-level 1 --log-prefix 'CDR3_RELAT
50

ED_ESTABLISHED:'
6. Logging to be viewed as:

[root@firewall2 ~]tail -f /var/log/messages | grep
"CDR2_INPUT_FORWARD:"
7. Add the following sample lines to the next section of the firewall_new file:
-A INPUT -I lo -j ACCEPT
-A FORWARD -I lo -j ACCEPT
-A INPUT -m state --state RELATED,ESTABLISHED -j ACCEPT
-A INPUT -p tcp -m tcp --dport 8009 -j ACCEPT
-A INPUT -p tcp -m tcp --sport 8009 -j ACCEPT
COMMIT
8. Save and exit the firewall_new file.

9. Activate the new rule set by typing the following command:
[root@firewall2 ~]iptables-restore
firewall_new
10. Save the new rule set to the current instance of iptables by typing the
following command:
[root@firewall2 ~]iptables-save
11. Save the configuration to be persistent by typing the following command:

[root@firewall2 ~]service iptables save
12. You can use the portqry command on DOS to verify the port state, as
follows:
To obtain these tools, you need to install the Support Tools from your
Windows 2003 Installation CD by running SUPTOOLS.MSI. However,
we did not install these tools on any of the machines.
Displays the state of TCP and UDP ports.
PortQry Usage:
portqry -n server [-p protocol] [-e || -r || -o endpoint(s)]
[-l logfile] [-s] [-I] [-q]
Where:
-n [server] IP address or name of server to query
-p [protocol] TCP or UDP or BOTH (default is TCP)
-e [endpoint] single port to query (valid range: 1-65535)
51

-r [end point range] range of ports to query (start:end)

-o [end point order] range of ports to query in an order
(x,y,z)
-l [logfile] name of log file to create
-s 'slow link delay' waits longer for UDP replies from re
mote systems
-I by-passes default IP address-to-name lookup
ignored unless an IP address is specified after
-n
-q 'quiet' operation runs with no output
returns 0 if port is listening
returns 1 if port is not listening
returns 2 if port is listening or filtered
Notes:
PortQry runs on Windows 2000 and later
Defaults: TCP, port 80, no log file, slow link delay
off
Hit Ctrl-c to terminate prematurely
examples:
portqry -n
portqry -n
portqry -n
portqry -n
myserver.com -e 25
10.0.0.1 -e 53 -p UDP -I
host1.dev.reskit.com -r 21:445
10.0.0.1 -o 25,445,1024 -p both
References:
Netfilter
ch-iptables
iptables-tutorials
Configuring the database server to static port 1521

This section describes how to set the Oracle registry key to force the Oracle
server to use the 1521 port only for queries that pass between the client and
server through Firewall3. We found that, when a client initially establishes a
connection with the listener on the server, it uses port 1521. For every
subsequent communication with the client, a different port number that ranges
from 1024 to 65535 is used, and the 1521 port is closed.
It was difficult to block the ports in Firewall3 because we did not know which
ports needed to be opened and which needed to be closed. This is because
the server was using ports randomly for the following actions:
52

We found that the server entry for the server is DEDICATED. If the server
is not created in DEDICATED mode, the particular phrase (Server =
DEDICATED) will not be present in the tnsnames.ora file. We confirmed
this by creating a database in SHARED mode locally on a Windows machine.
(Oracle_Port_configuration2.JPG)
1. After we confirmed that the DB is running in Dedicated mode, we set the
USE_SHARED_SOCKET registry key in HOME0, as shown below:
2. We logged into the Oracle Enterprise Manager Console with
SYS/PASSWORD credentials and restarted (Shutdown and Open) the
Oracle server. (Oracle_Port_configuration4.JPG)
3. After the Oracle server started, we logged into the Cluster3 machine and
connected to the Oracle server by using sqlplus with the Scott/tiger
account. We ran some basic queries and we found that the 1521 port
was used for all the queries, as shown below:
Registering fixed port numbers for BusinessObjects

servers
When started and enabled, each of the other BusinessObjects Enterprise
servers dynamically binds to an available port (higher than 1024), registers
with this port on the CMS, and then listens for BusinessObjects Enterprise
requests. A specific Request Port number must be configured for servers
that communicate with other BusinessObjects Enterprise components across
a firewall.
BusinessObjects Enterprise servers register with the CMS when they start.
When a server registers with the CMS, the CMS records:
The hostname (or IP address) of the server's host machine.

The server's Request Port number.
The CMS uses two ports: the Request Port and the Name Server Port. By
default, the Request Port is selected dynamically. The Name Server Port is
6400 by default. We set the Request Port to 7400.
Other BusinessObjects Enterprise servers will initially contact the CMS on
its Name Server port. The CMS will respond to this initial contact by returning
53

Setting up the CMS database
the value of its Request Port. The Business Objects servers will use this
Request Port for subsequent communication with the CMS.
To register fixed port numbers, complete the following steps:
1. Log into Central Management Console (CMC).
2. In "Central Management Console" home page, navigate to the "Servers"
management area of the CMC.
3. Select the server, and then select Stop Server from the "Actions" menu.
4. Select the server, and select Properties from the "Manage" menu.
5. In the "Properties" window, under "Common Settings", clear the
Auto-Assign check box for Request Port.
6. Under "Common Settings", type the port number you want the server to
listen on. Click Save & Close.
7. Start the server for the changes to take effect.
The server is registered with the CMS with the specified port numbers.
Registering fixed port numbers for BusinessObjects servers is complete.
References:
BusinessObjects Enterprise Administrator's Guide

The CMS database contains information about the BusinessObjects
Enterprise system, which the BusinessObjects components can access when
required. The data stored in the CMS includes information about users and
groups, security levels, Business Enterprise content, and servers.
Setting up a CMS database involves creating a permanent tablespace,
creating a temporary tablespace, and creating a new user.
Creating a new user account for the XI 3.1 repository

on BOEDB
This section describes how to create a new user account. For the purpose
of illustration, we will use the Oracle 10g account for setting up the repository.
This user account has the following privileges:
54

create session
create table
create procedure
Creating a permanent tablespace
To create a permanent tablespace, complete the following steps:

1. In the "Oracle Program Group" window, click Database Control - O101.
The "Login" screen appears.
2. Type the built-in user account SYS in the "User name" text box and
vanpassword in the "Password" text box. Select SYSDBA from the
Connect as drop-down list box.
3. Navigate to the "Administration" tab, and click the Tablespaces link. The
Tablespaces link is located in the "Database Administration" section.
55

4.
5.
6.
7.
56
In the "Tablespaces" page, click Create.

In the "Create Tablespace" page, type "XIR3_1" in the "name" text box.
Scroll down to the datafiles section, and click Add.
In the "Add Datafile" page, type XIR3_1 in the "File Name" text box, and
set the tablespace file size to 2 GB. In the "Storage" section, enable
Automatically extend datafile when full (AUTOEXTEND).

This allows the datafile to continue to expand if its size exceeds 3 GB.
Click OK to accept the change.
A permanent tablespace is created.
Repeat steps 1 to 7 to create XIR3_1_EPM and XIR3_1_AUDIT tablespaces
for the Performance Management repository and the Audit repository,
respectively.
Creating a temporary tablespace

To create a temporary tablespace, complete the following steps:
1. In the "Oracle Program Group" window, click Database Control - O101.
The "Login" screen appears.
2. Type the built-in user account SYS in the "User name" text box and
vanpassword in the "Password" text box. Select SYSDBA from the
Connect as drop-down list box.
3. Navigate to the "Administration" tab, and click the Tablespaces link. The
Tablespaces link is located in the "Database Administration" section.
57

4. Type XIR3_1_Temp in the "name" text box, and set the datafile size to 1
GB. Click OK to accept the change.
5. Repeat steps 1 and 2 to create XIR3_1_EPM_TEMP and

XIR3_1_AUDIT_TEMP temporary tablespaces for the Performance
Management repository and the Audit repository, respectively.
Creating a new user

To create a new user, complete the following steps:
1. Navigate to the Administration tab.
2. In the Administration tab, click the Users link. The Users link is located
in the "Users & Privileges" section
3. In the "Users" page, click the Create button.
The "Create User" page appears.
4. In the "Create User" page, type XIR3_1 in the "Name" text box, and type
XIR3_1 in the "Enter Password" and "Confirm Password" text boxes.
58

Select XIR3_1 for Default Tablespace and XIR3_1_Temp for Temporary

Tablespace, respectively.
5. In the Quotas tab, select Unlimited in XIR3_1 Tablespace, and save the
settings. Make sure the following System privileges and quotas are
assigned to the user.
59

6. For a user XIR3_1_EPM with password XIR3_1_EPM to be used for EPM

repository, repeat steps 1 to 4. This user is assigned to XIR3_1_EPM
and XIR3_1_EPM_TEMP tablespaces. Make sure the appropriate System
privileges and quotas are assigned to the user.
7. In the "Create User" page, type XIR3_1_Audit in the "Name" text box,
and type XIR3_1_Audit in the "Enter Password" and "Confirm Password"
text boxes. Select XIR3_1_AUDIT for Default Tablespace, and select
XIR3_1_AUDIT_Temp for Temporary Tablespace. Make sure the
appropriate System Privileges are assigned to this user.
60

Setting up the database client
A new user is created.

This section describes how to install the Oracle 10.2 client software on the
systems in the cluster. After you install the Oracle 10.2 client, you can use
the Oracle native client to connect to your Oracle database server. This
section also describes the tasks that you must complete before you can
install the Oracle database client products. For information about hardware,
software, and other requirements, see the Oracle Client Installation Guide.
Setting up the database client involves the following tasks:
Uninstalling the Oracle 9.2 client
Installing the Oracle 10.2 client
61

Uninstalling the Oracle 9.2 client

This section describes how to uninstall the Oracle 9.2 client. To uninstall the
Oracle 9.2 client, you must log into your system by using an account that
belongs to the local administrator's group.
In the Windows pattern, the Oracle client is installed on three machines.
These three machines are Cluster1, Cluster2, and Cluster3. The Oracle client
is used by the CMS to connect to the CMS databases and the corporate
database.
You can use the existing Windows users (Cluster1_User1, Cluster2_User1,
and Cluster3_User1) to uninstall the Oracle client from the CMS cluster
machines.
Stopping the Oracle services on Windows

This section describes how to stop the Oracle services on Windows. The
Oracle services must be stopped before you remove the Oracle components
and registry entries.
To stop the Oracle services on Windows, complete the following steps:
1. SelectStart menu -> Programs -> Administrative Tools -> Services.
2. Select the Oracle services (names begin with Oracle or Ora) that are
running, and click Stop.
3. Exit the "Services" window.
62

Removing the Oracle database client by using Oracle Universal Installer

This section describes how to remove the Oracle database client by using
Oracle Universal Installer.
Note:
Before starting with the uninstallation procedure, back up your existing

tnsnames.ora and sqlnet.ora from c:\oracle\ora92\network\ADMIN
To remove the Oracle database client by using Oracle Universal Installer,
complete the following steps:
1. Run the Oracle Universal Installer from theStart menu, and select Pro
grams > Oracle Installation Products > Universal Installer.
The "Oracle Welcome" screen appears.
2. Click Installed Products, to view the existing installation features of the

client.
The installer prompts for confirmation about removing the components.
63

3. Click Yes.
Note:
A message may appear indicating that removing some components can

affect the performance of other components. The "Install" page displays
the list of components that are being uninstalled and their status. After
the uninstallation process is completed, the "Inventory" page appears,
indicating that the client is uninstalled successfully.
4. Click Close, and then click OK.
64

During the uninstallation process, some files, such as the registry files,
are not deleted from the system. These files must be removed manually.
Manually deleting the remaining Oracle database client components

During the uninstallation of the Oracle client, the Oracle Universal Installer
does not remove Oracle components such as registry keys, environment
variables, Start menu options, and directories. This section describes how
to remove these Oracle components.
Deleting the Oracle components that are not removed during the uninstallation
of the Oracle client involves the following tasks:
This section discusses the following topics:
Deleting Oracle keys from the Registry Editor on Windows

Updating the PATH environment vaviable
Deleting the Oracle database client from the Start menu
Deleting the Oracle database client directories
65

Deleting Oracle keys from the Registry Editor on Windows

The uninstallation of the Oracle client using Oracle Universal Installer does
not remove some of the registry keys and all the services created by the
Oracle Net Configuration Assistant. To complete the uninstallation of the
Oracle client, you must manually remove these services and registry keys.
Deleting the registry keys manually involves the following tasks:
Deleting only the Oracle Net Service Registry key

Deleting all Oracle Registry keys
Deleting only the Oracle Net Service Registry key

To delete only the Oracle Net Service registry key, complete the following
steps:
1. Log into the system by using an account that belongs to the administrator's
group.
2. Stop the Oracle services on Windows. For information on stopping the
Oracle services on Windows, see Stopping the Oracle services on
Windows on page 62.
3. Select Start -> Run, and type the following command: regedt32
4. Navigate to the HKEY_LOCAL_MACHINE\SYSTEM\CurrentCon
trolSet\Services folder, and delete the Oracle HOME_NAME TNSListener
registry entry. All other Oracle Net services are deleted automatically by
the Oracle Universal Installer.
The Oracle Net Service Registry key is deleted.
5. Exit the Registry Editor.
6. Restart the system.
The Oracle Net Service Registry key is deleted.
Deleting all the Oracle Registry keys

This section describes how to delete all the Oracle Registry keys from the
system.
Note:
You must exercise extreme caution while deleting the registry entries. Deleting
incorrect entries can affect your system. Make sure that you remove the files
under ORACLE_BASE\ORACLE_HOME\DB_NAME only after you have
removed the registry keys, which is described in this section
66

To delete all Oracle Registry keys, complete the following steps:

1. Log into the system by using an account that belongs to the administrator's
group.
2. Stop the Oracle services on Windows. For information on stopping the
Oracle services on Windows, see Stopping the Oracle services on
Windows on page 62.
3. Select Start -> Run , and type the following command: regedt32
4. Navigate to "HKEY_CLASSES_ROOT".
5. Delete the keys that begin with the following:
ORAMMCPMON10
ORCLSSO
OraOLEDB.ErrorLookup
OraOLEDB.Oracle
OracleInProcServer.XOraServer
In our case, the installer deleted the specified registry key.
6. Navigate to "HKEY_LOCAL_MACHINE\SOFTWARE" and delete the
ORACLE Group key.
7. If you installed Oracle Services for Microsoft Transaction Server, navigate
to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Event
log\Application and delete the Oracle Services for Microsoft Transac
tion Server key.
8. Navigate to "HKEY_CURRENT_USER\Software" and delete all Oracle
keys, including the Oracle HOME_NAME entries under Microsoft\Win
dows\CurrentVersion\Explorer\MenuOrder\StartMenu\Programs.
9. Exit "Registry Editor".

10. Restart your system.
All Oracle Registry keys are deleted.
Updating the PATH environment variable

This section describes how to update the PATH environment variable path.
To update the PATH environment variable path, complete the following steps:
1. Select Start -> Control Panel , and click System.
2. Click Advanced and then click Environment Variables.
67

3. Select PATH, and edit it to remove all Oracle entries.

In our case, the installer had already removed the Oracle entries.
4. Save the changes you made, and exit System.
Updating the PATH environment variable is complete.
Deleting the Oracle database client from the Start menu

This section describes how to delete the Oracle database client from the
Start menu.
To delete the Oracle Database client from the Start menu, complete the
following steps:
1. SelectStart > Programs > Oracle HOME_NAME.
2. Right-click Oracle - HOME_NAME, and click Delete.
The Oracle database client is deleted from the Start menu.
Deleting the Oracle database client directories

This section describes how to delete the Oracle database client directories.
After deleting all Oracle Database Client registry keys and restarting the
computer, you must delete any existing Oracle database client directories
and files.
To delete the Oracle database client directories, complete the following steps:
1. Using My Computer or Windows Explorer, delete the
SYSTEM_DRIVE:\program files\oracle directory.
2. Using My Computer or Windows Explorer, delete all ORACLE_BASE
directories from the hard drive.
The Oracle database client directories are deleted.
Setting up the Oracle 10.2 client

This section describes how to install the Oracle 10.2 client software on the
systems in the cluster. After you install the Oracle 10.2 client, you can use
the Oracle native client to connect to your Oracle database server. For
information about the tasks you must complete before installing the Oracle
client and the prerequisites your systems must meet, see the Oracle Client
Installation Guide.
68

Installing the Oracle 10.2 client

To install Oracle 10.2 client, you must log into your system by using an
account that belongs to the local administrator group.
The Oracle client must be installed on three machines. These three machines
are Cluster1, Cluster2, and Cluster3.
You can use the existing Windows users (Cluster1_User1, Cluster2_User1,
and Cluster3_User1) to install the Oracle client on the CMS cluster machines.
To install the Oracle 10.2 client, complete the following steps:
1. Run the Oracle installation package from \\vanpgsoftware\software\Or
acle\DB-Clients\Database_10.2.0.1Client\win
dows\10201_client_win32\client.
The "Oracle welcome" screen appears.

2. Click Installed Products to verify whether Oracle clients already exist in
the system.
3. Click Close to go back to the main menu.
4. Click Next. The installer displays a list of installation types.
5. Select Administrator as the installation type. Selecting this installation
type enables you to install management console, management tools,
networking services, utilities, and basic client software. This is the only
installation type that includes the Oracle native driver. This installation
type also provides tools that enable you to administer an Oracle database
remotely.
6. Click Next. The screen for specifying the installation location appears.
Type BOE_OraHome10 in the Name field. You can either accept the default
installation path (\oracle\product\10.2.0\client_1) or specify another
path in the Destination Path field, if disk space is available on the drive
you select. For purposes of illustration, this document uses the following
destination path: C:\oracle\product\10.2.0\boe_ora10g.
The installer checks for prerequisites such as operating system, service
pack requirements, and so on. If the prerequisites are not present, the
list of missing components is displayed.
7. Click Next.
The "Summary" page appears, displaying your installation selections. To
revise the selections, click Previous and make the necessary changes.
69

After you click Install, the Oracle Setup Wizard begins copying files and
setting up the Oracle client on your system.
8. Click Install.
The "Install" page appears, displaying the components that are being
installed and their status.
9. Once all the files are installed, Oracle will launch the Oracle Net
Configuration Assistant wizard to help you with the various configuration
tasks.
Naming Methods Configuration: To connect to a service, clients use a
connect identifier in the connect string. The connect identifier can be
either a connect descriptor or a simple name that maps to a connect
descriptor. The connect descriptor contains:
a. Network route to the service, including the location of the listener,
through a protocol address
b. An Oracle8i or later database service name or Oracle 8.0 database
Oracle System Identifier (SID). A simple name is resolved to a connect
descriptor by a naming method. Naming method configuration consists
of the following steps:
c. Selecting a naming method.
d. Mapping the connect descriptors to simple names.
e. Configuring clients to use the naming method. For our configuration,
we will perform a typical configuration to set up a connection with the
database server.
10. For our Windows pattern, we will select Local Naming.
11. In the next page, type BOE11 as "Service Name", because we are
connecting to the BOE11 database.
12. In the "Net Service Name Configuration, TCP/IP Protocol" page, specify
the machine where the database is located and the TCP/IP port number.
For this configuration, enter the BOEDB as the "host name" and 1521 as
the port number, and click Next.
13. In the" Net Service Name Configuration, Select Protocols" page, the list
of available network protocols is displayed. Select TCP as the protocol
to be used for communication across the network.
14. In the "Net Service Name Configuration, Test" page, select Yes, perform
a test if you want to perform a connectivity test, or No, do not test if you
do not want to perform a connectivity test. By default, this option is set to
"No, do not test"
70

Setting up the BusinessObjects server cluster
15. In the "Net Service Name Configuration, Net Service Name" page, specify
a name for your net service configuration. We used the default net service
name because we wanted the hostname to be the same as the service
name.
16. In the "Net Service Name Configuration, Another Net Service Name?"
page, select Yes if you want to configure another net service name, or
No to finish the installation. We selected "No" because we did not want
to create another net service name.
The following results are displayed:
The "Net Service Name Configuration Done" page appears, indicating
that the Net Service Configuration is complete.
that the Naming Methods Configuration is completed.
that the Net Service Name Configuration is complete.
The "Configuration Assistants" page appears, indicating that net service,
naming service configuration, and net service name creation are complete.
The installation of the client is complete.
17. Click EXIT.
18. Log into the database with any user account to verify the installation. In
our case, we used the scott/tiger@boe11 account to verify the installation.
19. After you verify the contents, copy the contents of the backed up
tnsnames.ora and sqlnet.ora to the existing files.
Setting up the BusinessObjects server

cluster
A BusinessObjects server cluster provides scalability and redundancy. There
are three machines in the BusinessObjects server cluster.
Setting up the BusinessObjects server cluster involves the following tasks:
Installing and configuring BusinessObjects Enterprise servers as clusters
Configuring XI 3.1 with LDAP
71

Preinstallation
The BusinessObjects servers are first installed on Cluster1, followed by
Cluster2 and Cluster3. The following ports are planned for: CMS: 7400 and
SIA: 7410
These ports were selected because they were free. We used 'netstat -a' at
the DOS command prompt to verify the available ports. We also used an
internal software called Port Reporter & Port Query to verify the available
ports.
Before we install BusinessObjects Enterprise, we reviewed the following
installation checklist.
1. Did we verified the network connectivity between machines that will be
part of your deployment?
2. For own database server:
a. Have we created a database for the CMS?
b. Have we created an auditing database, if required?
c. Have we created a user ID and password with the necessary
permissions to access your existing database (if you are integrating
your existing database server software), so that the installation can
access your database to configure the CMS database?
d. Have me made sure you can log into the database with your login ID
and password?
e. Have we tested the database connection between the machine hosting
the database servers and the Central Management Server (CMS)?
f. For using DB2 or Sybase, we verified that our database was created
with the correct settings? (Some settings can't be modified after the
database has been created.)
g. Has the database client software been properly configured?
3. We consulted the BusinessObjects Enterprise Planning Guide to gain a
general understanding of the installation process and the different options
available.
4. We reviewed our systems to ensure they meet the basic requirements
for a BusinessObjects Enterprise installation. We refered to the System
requirements on the Products Availability Report (PAR) document
boe_xi_31_sp_windows.pdf found at BOSAP Support Site. Even refer
the guides: xi3-1_whats_new_en.pdf, xi3-1_release_notes_en.pdf,
72

xi3-1_bip_install_win_en.pdf & xi3-1_bip_admin_en.pdf. You can
find the guides here: BusinessObjects Product Guides.

5. We ensured that all machines that will be part of our BusinessObjects
Enterprise deployment can communicate across the network.
6. We decided which BusinessObjects Enterprise components to install,
and which of our own components to integrate.
7. We determined the location of the components to be installed. This
included the specific subnet, machine, database, security, or cluster
systems that will be used to run our system.
8. We decided which installation method to use.
9. We ensured that we have a Windows user account that belongs to the
local administrator's group. The local administrator's group must have
system default security rights.
Installing and configuring BusinessObjects

Enterprise servers as cluster
This section describes the installation steps for installing BusinessObjects
Enterprise on each of the three cluster machines(Cluster1, Cluster2, and
Cluster3).
To install and configure BusinessObjects Enterprise servers as cluster,
1. Log into the system with the user account you created for the
BusinessObjects Enterprise server installation.
2. We copied the installable locally, and double-click the setup.exe. The
Installation Wizard appears. Click Run.
73

3. We selected the setup language and then selected the check box to
create the installation log. The log file is created as:
<INSTALLDIR>\BusinessObjects Enterprise
12.0\Logging\BOEInstall_X.log.
The Windows installer appeared.
4. In the"Welcome to BusinessObjects Enterprise XI Release 2 Installation

Wizard" dialog box, we clicked Next.
The following error message appears if Microsoft .NET Framework 2.0
is not detected:
74

Microsoft .NET Framework 2.0 can be downloaded from the following

link: MS.NET Framework
5. Since we did not have Microsoft .NET Framework 2.0 installed we exit
the setup. We installed .NET Framework and restarted the setup, We
repeat steps 1 to 7.
6. In the License Agreement dialog box, we read the license terms and to
continue with the installation accepted the terms of the agreement, and
clicked Next.
7. We entered the product keycode, and clicked Next.
8. We selected English for the language packs we wanted to install.
9. We select "Custom or Expand" option. We do not select "New" as we
don't want to install all the components. We do not select the "Web Tier"
option as we do not only want to install components used by a web
application server to run a web application. Hence we choose "Custom
or Expand" so we can select the components we want to install and
perform a distributed deployment. As per plan we selected C:\BOEXI3_1\
for the installation.
75

Click Next.
10. We installed the following components: On Cluster1 and Cluster2:
76

Server components
Database Access: To access the database.
Export Support
We selected the following components because we did not want the client
components to be installed on this system, cluster1 and cluster2. We only
wanted the server components.
On Cluster3:
77

Server components
Database Access
Export Support
Client components: Only on cluster 3.
We installed all the client components on Cluster3 because we wanted

some client tools as backup. The client tools will not be used regularly.
We have installed client components on Cluster3 because of hardware
constraints. It is advisable for the customers to install client components
is some client machine which is outside the corporate network.
11. In the CMS Clustering dialog box, we select "Yes" when the first CMS
in the cluster, and enter the port number and the administrator password.
In our case, the administrator password is 'vanpassword'. The first time
we do not select "No" as this is the first CMS in our deployment. The next
two times as we already have a CMS in our deployment we will select
"No". Click Next.
78

12. In the Server Intelligent Agent dialog box, we entered MIRA1 in "node
name" and 7410 in "port information" for Cluster1. For Cluster2 we entered
MIRA2 and Cluster3 we entered MIRA3. The port information is the same
for each of the cluster machines, 7410. Once done we clicked Next.
13. In the CMS Database Information dialog box, select an appropriate
database and type the credentials. We used an Oracle 10g database.
79

14. In the Start installation dialog box, we can click Back to review the
installation information. We clicked Next to start the installation.
The installation begins.
80

15. Once the installation is complete, we clicked Finish.
Configuring XI 3.1 with LDAP

This section describes how to set up the LDAP authentication on the XI 3.1
system.
Please refer to Using LDAP authentication section of xi3-1_bip_ad
min_en.pdf (257) for details. This guide is available at: BusinessObjects
Product Guides.
To configure XI 3.1 with LDAP, complete the following steps:
1. Log into the Central Management Console (CMC) by using a Enterprise
user account that is part of the BOE administrator's group. We used the
default BOE administrator user ID to log into CMC.
2. In the Manage section, click Authentication.
81

The "Authentication" page appears.

3. Double-click LDAP.
The "LDAP Configuration Wizard" page appears.
4. Click Start LDAP Configuration Wizard.

5. Navigate to the "LDAP" tab. Enter the name of the LDAP server and the
port number. We entered Authentic as the name of the LDAP server
and 20000 as the port number. This information can be garthered from
the administrator of the security team.
82

6. Click Add.
7. Click Next. For the LDAP Server type, select Microsoft Active Directory
Application Server from the drop-down list.
8. Type O=BusinessObjects,C=US as the distinguished name of a partition

to which you want to connect. This information can be garthered from the
administrator of the security team.
9. For the LDAP Server Administration Credentials, type the distinguished
name, CN=Auth_User1,OU=BOBJ Users,O=BusinessObjects,C=US.
This user account is used to connect to the LDAP server. This information
can be garthered from the administrator of the security team.
10. Select Basic (no SSL) from the authentication drop-down list.
We selected Basic because we did not use SSL authentication.
83

11. Select Basic (no SSO) from the authentication drop-down list.
We selected Basic because we did not use single sign-on authentication.
12. Specify how aliases must be mapped to BusinessObjects Enterprise

accounts.
a. In "New Alias" option, select how new aliases are mapped to Enterprise
accounts. Select one of the following:
Assign each added LDAP alias to an account with the same name
84

Use this option if you know that users have an Enterprise account with
the same name; that is, LDAP aliases will be assigned to existing
users (auto alias creation is enabled). If users do not have an
Enterprise account, or if their name in Enterprise is different from that
in the LDAP account, then they are added as new users.
Create a new account for each LDAP alias that is added. Use this
option if you want to create a new account for each user.
a. In "Alias Update Options", select how to manage alias updates for the
Enterprise accounts. Select one of the following:
Create new aliases when the Alias Update occurs
Use this option to create a new alias automatically for every LDAP
user mapped to BusinessObjects Enterprise. New LDAP accounts are
added for users who do not have BusinessObjects Enterprise accounts,
or for all users if you selected the Create a new account for every
added LDAP alias option.
Create new aliases only when the user logs in

Use this option if the LDAP directory you are mapping contains many
users, but only a few of them are likely to use BusinessObjects
Enterprise. BusinessObjects Enterprise does not automatically create
aliases and Enterprise accounts for all users. Instead, it creates aliases
(and accounts, if required) only for users who log into BusinessObjects
Enterprise.
a. In "New User Options", specify how new users are created by selecting
one of the following:
New users are created as named users
New user accounts are configured to use named user licenses. Named
user licenses are associated with specific users and allow users to
access the system based on their user name and password. This
provides named users with access to the system regardless of how
many other users are connected. You must ensure that a named user
license is available for each user account created by using this option
New users are created as concurrent users

New user accounts are configured to use concurrent user licenses.
Concurrent licenses specify the number of users who can connect to
BusinessObjects Enterprise at the same time. This licensing type is
highly flexible because a small concurrent license can support a large
85

user base. For example, depending on how often and how long users
access BusinessObjects Enterprise, a 100 concurrent users license
can support 250, 500, or 700 users. We have the same user ID in the
CMS database and LDAP server because we are upgrading an existing
platform. If we were deploying a new platform we would have nothing
in our CMS database.
For New Alias Options, we selected Assign each added LDAP alias to
an account with the same name because we have the same user ID
in the CMS database and LDAP server database. For Update Options,
we selected the Create new aliases when the Alias Update occurs
option. For New User Options, we selected the New users are created
as concurrent users option because we are using a concurrent user
license in our configuration.
The following screen appears after you enter the required information:
86

13. Click Finish.

The information you entered is verified and the LDAP main page appears.
You must not add the LDAP Group in a real-time scenario. We found that
if the LDAP Group is mapped at this stage, the LDAP users are mapped
in XI 3.1 and their respective aliases are created. Hence, attempts to
import the LDAP users from XIR2 to XI 3.1 fails. In our case, we had to
delete all the LDAP aliases mapped in XI 3.1 and then unmap the LDAP
group before continuing with the migration of users.
14. In the Mapped LDAP Member Groups section, type the distinguished
group name:CN=BOE Testers,OU=BOBJ
Users,O=BusinessObjects,C=US, and click Add. This group contains all
the LDAP user members.
15. Click Update.
After you configure LDAP, you can test it by logging into the InfoView
desktop or CMC by using the LDAP user ID.
16. By default, the Authentication option in the InfoView login page is disabled.
Modify the Web.xml file under the C:\Tomcat55\webapps\In
foViewApp\WEB-INF folder, to view the tab.
Note:
We noticed that the LDAP users are not mapped immediately though
LDAP Group is created and is visible in the CMC. This is because a large
number of users were present in the LDAP Server (4999). However, when
we restarted the SIA and remapped the LDAP users, the list of users was
displayed immediately in the CMC.
87

Adding a new BusinessObjects server

This section describes how to add a new BusinessObjects server.
In the MIRA1 and MIRA 3 machine we added CrystalReportsCacheServer1,
ReportApplicationServer1, and WebIntelligenceProcessing Server1. In the
MIRA2 machine we added 2 WebIntelligenceProcessing Server1. We added
these servers so reports can be processed faster and the load is balanced
over the servers.
To add a new BusinessObjects server, complete the following steps:
1. Log into the CMC with a user account that has administrative rights.
2. In the CMC home page, click Servers.
3. In the "Servers" window, selectManage > New > New Server.
The "Create New Server" dialog box appears.
4. Select Service Category. Select a server type from the "Select Service"
list, and then click Next.
5. To add an additional service to the server, select the service from the
Available Additional Services list, and click >, and click Next.
Note: Additional services are not available for all server types.
6. If your BusinessObjects Enterprise architecture consists of multiple nodes,
from the Node list, select the node where you want to add the new server.
7. Type a name for the server in the Server Name text box.
Each server on the system must have a unique name. The default naming
convention is NODENAME.servertype (a number is appended if there is
more than one server of the same type on the same host machine).
8. Type a description in the Description text box, and click Create.
The new server appears in the list of servers in the Servers area of the
CMC.
9. Enable and start the server.
A new BusinessObjects server is added.
88

Setting up the File Repository Server

An Input and Output File Repository Server (FRS) is a part of every
BusinessObjects Enterprise system. The FRS manages report objects and
program objects that administrators and end users publish, by using the
Publishing Wizard, the CMC, the Import Wizard, or a Business Objects
designer component, such as Crystal Reports, or the Web Intelligence Java
or HTML Report Panels.
In the Windows pattern, the File Repository Server (FRS) shares the same
Windows server machine as the BusinessObjects CMS database (BOEDB).
In a real-time deployment, a Storage Area Network (SAN) is recommended.
A cluster of Windows machines as file servers is also an option if a SAN is
not available.
This section describes how to map the FRS for the clusters on the BOEDB
machine. To map the FRS for the clusters on the BOEDB machine, complete
the following steps:
1. Create a folder and name it MIRA FRS.
You must share this folder and grant full control to administrator on this
folder and all the subfolders under it.
89

2. Create Input and Output folders under the MIRA FRS folder. You must
also create a folder called temp under each Input and Output folder.
3. Map the directories to the IFRS and OFRS of all the clusters.
4. Log into the CMC as administrator.
5. Navigate to the "Servers" section, right-click
Mira1.InputFileRepositoryServer, and select Properties.
90

6. Navigate to the "File Store Directory" option, and change the path to
\\boedb\MIRA FRS\Input. For the Temporary Directory, use
\\boedb\MIRA FRS\Input\temp. Click Save & Close.
The server page appears. This page displays a red flag against the server
in the Stale column. This implies that you must restart the server for the
changes to take effect.
The FRS is mapped for the clusters on the BOEDB machine.

Repeat the same steps to map the Output File Repository Server for the
cluster machines on the BOEDB.
91

Setting up the auditing database
After you restart the server, you can view the Input.Mira1, Input.Mira2, and
Input Mira3 folders in the \\boedb\MIRA FRS\Input\temp folder. These
folders represent the cluster.
You can also view the Output.Mira1, Output.Mira2, and Output.Mira3 folders
in the \\boedb\MIRA FRS\Output\temp folder. These folders represent the
cluster.
References:
Issue faced while mapping FRS for the clusters on page 236

In the Windows pattern, the auditing database uses the same database
server as the CMS database.
Setting up the auditing database involves providing connectivity and
credentials for an existing database server when you install BusinessObjects
Enterprise. The CMS server then creates the auditing database on a database
server that the administrator specifies. The database is populated over time
as the system is used.
This section describes how to enable auditing on the cluster machines. For
the Windows pattern, a populated auditing database is required for
performance testing. Hence, the database is set up manually. Setting up the
database manually involves the following tasks:
Configuring auditing on cluster machines
Enabling auditing on the applications
Enabling auditing on servers
92

Importing sample audit reports and universes
Configuring auditing on the cluster machines

This section describes how to configure auditing on the cluster machines.
To configure auditing on the cluster machines, complete the following steps:
1. Log into Cluster1, and select Start -> Settings -> Control Panel -> Add
or Remove Programs.
The "BusinessObjects Enterprise XI 3.1 setup" page appears
2. Click Change.
3. Click Modify.
The "Select Features" page appears.
4. In the "Select Features" page, selectServer Components -> Central
Management Server.
93

5. Click Auditor, and select the entire feature.

6. Click Next to start the installation.
94

Auditing is configured on Cluster1.

To configure auditing on Cluster2 and Cluster 3, repeat steps 1 to 5 on each
one of them.
Enabling auditing
After you configure auditing on the cluster machines, you must enable auditing
from the Central Configuration Manager (CCM).
To enable auditing, complete the following steps:
1. Log into a cluster machine, and stop SIA from the CCM console.
After the SIA stops, the Auditor icon appears.
95

2. Click the Auditor icon.

The "Database Driver" dialog box appears.
3. Select a connection method. We selected Oracle native driver.
4. Enter the user name and password for the Oracle database, and click
OK.
96

The "Central Configuration Manager" dialog box appears, indicating that

auditing is set up successfully.
5. Start the SIA. The following tables are created under the XIR3_1_AUDIT
schema:
INCOMPLETE_EVENT
AUDIT_DETAIL
AUDIT_EVENT
APPLICATION_TYPE
EVENT_TYPE
SERVER_PROCESS
DETAIL_TYPE
Enabling auditing on the application

This section describes how to enable auditing on the application
To enable auditing on the application, complete the following steps:
1. Log into the CMC, and navigate to the "Applications" section.
2. Right-click Web Intelligence, and select Audit Events.
97

You can select both Web Intelligence and Desktop Intelligence

applications. However, this document discusses only Web Intelligence
applications.
3. In the "Audit Events for Web Intelligence" page, select the events you
want to audit.
4. Select the Auditing Status option.
5. Click Update to save the settings.
98

Auditing is enabled on the application.
Enabling auditing on the servers

This section describes how to enable auditing on servers. To verify if auditing
is working properly, you must enable auditing on
WebIntelligenceProcessingServer. To enable auditing on the
WebIntelligenceProcessingServer, complete the following steps:
1. Right-click theMIRA1.WebIntelligenceProcessingServer -> Audit
Events option.
2. In the Audit Events: "MIRA1. WebIntelligenceProcessingServer" page,
select all the events you want to audit by clicking All option under Select
Events to Audit. You must also select Auditing is Enabled option.
99

The auditing information is logged in the Audit_Event and Audit_Detail

tables.
3. Log into the Oracle user account (XIR3_1_Audit) and query against the
Audit_Event and Audit_Detail tables, to confirm that no are events
recorded.
4. Open and refresh the test Web Intelligence document from the InfoView
by logging in as the administrator.
5. Log into the Oracle Database Enterprise Manager or SQL Plus, to verify
whether the Open/Refresh activity is audited.
100

6. Navigate to the "Tables" section, and open the Audit_Detail table.

The Open and Refresh Activity of the Test Document is logged in the
table.
Note:
You can view the detailed action type by comparing the value of
Detail_Type_Id column in the Audit_Detail table with that of
Detail_Type_Description column in the Detail_Type table. You can also
view other details in the Audit_Event table for the Open/Refresh activity.
101

Auditing is enabled on the servers.
Importing sample audit reports and universes

After you install the Auditor on the cluster machines, you must manually
import the sample audit reports and universes from the BIAR file. This section
describes how to import sample audit reports and universes.
To import sample audit reports and universes, complete the following steps:
1. Run the "Import Wizard" from the Cluster3 machine.
2. Select the BIAR file, and navigate to the "Samples" folder. (add image)
3. Select the auditing_rpt_en.biar file in the Samples folder, and click
OK. (add image)
4. Select the Cluster3 machine as the destination. Type the login credentials
for "the administrator", and click Next. (add image)
The Import Wizard starts to scan the BIAR file.
5. Select the following options:
Users and groups
Folder & Objects
Universes
Repository Objects
6. In the "Import Scenario" page, select the first option to update and rename
the import scenario if another object with the same name and unique ID
exists.
7. Select Overwrite to overwrite the contents.
The Users and Groups list is empty. This indicates that there are no new
users associated with the sample reports and universes. The Folder
structure displays all the default reports in the BIAR file. (add image)
8. In the "Import options for universes and connections" page, select the
third option to import universes and connections. (add image)
The Activity Universe is automatically migrated.
9. In the "Import options for publications" page, select Do not Import
recipients.
The"Summary" page displays the list of selected objects and universes.
The Import Wizard displays the progress of the import process.
102

Setting up the application server
10. Click View Detail Log to view the details of the imported documents and
universes. (add image)
11. Log into CMC.
You can view the Auditor folder in the list of folders.
Importing sample audit reports and universes is complete.

BusinessObjects Enterprise XI 3.1 supports Tomcat 5.5 and later with JDK
1.5.0_xx. For more information, see the Product Availability Report (PAR).
The Windows pattern includes two application servers for scalability and
redundancy.
Setting up the application server involves the following tasks:
Installing the Web Component Adapter (WCA)
Enabling the AJP 1.3 Connector in Tomcat
Configuring the Tomcat cluster
Configuring the application servers to use the BusinessObjects CMS

cluster
Uninstalling the older version of Tomcat

The Tomcat server installed with BusinessObjects Enterprise XI Release 2
must be uninstalled before installing and deploying the Tomcat server shipped
with XI 3.1.
To uninstall Tomcat, complete the following steps:
1. SelectStart -> Control Panel -> Add or Remove Programs.
2. In the "Add or Remove Programs" window, select BusinessObjects
Enterprise XI Release 2, and click Remove.
The following dialog box appears. Click Yes
103

3. Click Yes.
The uninstallation of BusinessObjects Enterprise XI Release 2 begins.
After the uninstallation is complete, BusinessObjects Enterprise XI Release
2 is removed from the list of installed programs.
4. Close the "Add or Remove Programs" window.

The older version of Tomcat is uninstalled.
104

lnstalling the Web Component Adapter (WCA)

Prerequisites for installing the Web Component Adapter (WCA) include:

A Windows operating system supported by BusinessObjects Enterprise
XI 3.1. For the list of supported platforms, see the Platform.txt file included
in your product distribution. The operating system used in our setup is
Windows 2003 Standard Edition SP2.
2 GB of RAM
A Windows user account that belongs to the local Windows administrator's
group. The local administrator's group must have system default security
rights. The following user accounts are used in this setup:
Machine Name
User Name
Password
Appserv1
appserv1_user1
vanpassword
Appserv2
appserv2_user1
vanpassword
The WCA must be installed on both the application server machines. To

install the WCA, complete the following steps:
1. Log into the computer with the user account that you created for installing
the application server.
2. Insert the installation CD-ROM, and double-click the setup.exe program.
3. Click Run.
4. Select the setup language.
The Windows installer appears.
5. In the "Welcome to BusinessObjects Enterprise XI Release 2 Installation

Wizard" dialog box, click Next.
105

The following error message appears if Microsoft .NET Framework 2.0

is not detected.
You can download Microsoft .NET Framework 2.0 from the following
location: Microsoft .NET Framework 2.0
6. In the "License Agreement" dialog box, read the license terms. To continue
with the installation, accept the terms of the agreement, and click Next.
7. Type the product keycode, and click Next.
8. Select the language packs you want to install.
9. If a previous version of BusinessObjects Enterprise is already installed
on the system, then an option is displayed that you can use to upgrade.
We selected No because this is fresh/new installation.
10. Select Custom or Expand, and click Next.
106

We selected this option because we wanted to install only WCA.

11. Select the following Web Tier components to configure Tomcat:
BI Platform Java Web Components
BusinessObjects Enterprise Web Services
Tomcat
12. In the"CMS Clustering" dialog box, enter the CMS existing hostname,
port number, and CMS administrator password, and then click Next.
107

13. In the "Web Application Server" dialog box, select Java Web Application
Server, and click Next.
108

14. In the"Configure Tomcat" dialog box, specify the connection port,

shutdown port, and the redirect port. Click Next.
We used the default ports. Before specifying the ports, you must ensure
that the ports are available for use.
The installation starts.
15. Click Finish to complete the installation.
109

After you have installed the WCA on both the application server machines,
you must enable the AJP 1.3 Connector in Tomcat.
Enabling the AJP 1.3 Connector in Tomcat

Enabling the AJP connector allows Tomcat to work with your Apache HTTP
web servers.
To enable the AJP 1.3 Connector for Tomcat, you must edit the server.xml
file that is located in C:\Tomcat55\conf directory, as follows:
1. Open the server.xml file in a text editor.
2. Locate the entry for the AJP 1.3 Connector. The entry appears as follows:
<--<Connector debug="0" enableLookups="false" port="8009"
protocol="AJP/1.3" redirectPort="8443"/>-->
3. By default, the AJP 1.3 Connector is commented out. To enable the

connector, remove the comment tags. The entry appears as follows after
the comment tags are removed: <Connector debug="0" en
110

ableLookups="false" port="8009" protocol="AJP/1.3" redirect

Port="8443"/>
4. Save the server.xml file, and restart the Tomcat server.

If the Tomcat server does not start, check if the values in the AJP 1.3
Connector section are separated with a single space. If not, provide a
space between the values. For example, replace the following entry:
<Connector enableLookups="false"port="8009"proto
col="AJP/1.3"redirectPort="8443"/>-->
with
<Connector enableLookups="false" port="8009" proto
col="AJP/1.3" redirectPort="8443"/>
The AJP connector is now enabled, allowing Tomcat to work with the web
servers.
Introduction to application server clustering

A cluster is a group of application servers that transparently run a J2EE
application as if it were a single entity. There are two methods of clustering:
vertical scaling and horizontal scaling. Vertical scaling is achieved by
increasing the number of servers running on a single machine, whereas
horizontal scaling is achieved by increasing the number of machines in the
cluster. Horizontal scaling is more reliable than vertical scaling, because
there are multiple machines involved in the cluster environment, as compared
to only one machine. In vertical scaling, the machine's processing power,
CPU usage, and JVM heap memory configurations are the main factors in
deciding how many server instances must be run on one machine (also
known as the server-to-CPU ratio).
To make Tomcat clustering and failover work, you need:
More than 2 Tomcat instances running on same or different machines

Deploy a web application on each Tomcat instance
A hardware or software load balancer setup.
Quick start
Running the session replication in your Tomcat 5.5 container involves the
following tasks:
111

Implementing java.io.Serializable for all session attributes

Uncommenting the Cluster element in server.xml
Uncommenting the Valve (ReplicationValve) element in server.xml
Ensuring that the tcpListenPort attribute is unique for each instance, if
your Tomcat instances are running on the same machine
Ensuring that your web.xml includes the <distributable/> element or setting
this element at <Context distributable="true" />
Ensuring that jvmRoute attribute is set at your Engine <Engine
name="Catalina" jvmRoute="node01" >
Ensuring that all nodes display the same time and that they are
synchronized with the NTP service
Ensuring that your load balancer is configured for the sticky session mode.
Note:
Your session state is tracked by a cookie. Hence, you must ensure that the
URL looks the same from outside. If not, a new session is created. Clustering
support currently requires JDK version 1.4 or later.
Configuring an individual Tomcat instance as a node

You must configure an individual Tomcat instance as a node to create a
Tomcat cluster. To configure an individual Tomcat instance as a node,
1. Open the server.xml file in a text editor.
2. Locate the entry for the cluster element. The entry appears as follows:
<--<Cluster className="org.apache.catalina.cluster.tcp.Sim
pleTcpCluster"
managerClassName="org.apache.catalina.clus
ter.session.DeltaManager"
---------------------------------------------------------------------------------<ClusterListener className="org.apache.catalina.cluster.ses
sion.ClusterSessionListener"/>
</Cluster>-->
3. By default, the AJP 1.3 Connector is commented out. To enable the

connector, remove the comment tags. The entry appears as follows after
the comment tags are removed:
<Cluster className="org.apache.catalina.cluster.tcp.SimpleTcp
Cluster"
112

managerClassName="org.apache.catalina.clus
ter.session.DeltaManager"
---------------------------------------------------------------------------------<ClusterListener className="org.apache.catalina.cluster.ses
sion.ClusterSessionListener"/>
</Cluster>
4. Locate the Engine element. An Engine represents the entry point (within
Catalina) that processes every request. The Engine implementation for
Tomcat standalone analyzes the HTTP headers included in the request,
and passes them to the appropriate host (virtual host).The entry appears
as follows:
<Engine defaultHost="localhost" name="Catalina">
5. Set jvmRoute to support load balancing through AJP, as follows:

<Engine defaultHost="localhost" name="Catalina" jvm
Route="appserv1">
6. Save the server.xml file, and restart the Tomcat server.

7. Add the <distributable/> tag to the web.xml of InfoView applications
deployed with APPSERV1 and APPSERV2. The <distributable/> tag must
be inside the <web-app> tag. For example, the web.xml entry for InfoView
must be as follows:
<distributable/>
<display-name>Business Objects Central Management Con
sole</display-name>
<description>
Business Objects Central Management Console applica
tion
</description>
The application servers are clustered.
Configuring the application servers to use the CMS

cluster
The BusinessObjects Enterprise server cluster includes three Central
Management Servers (CMSs). If you have more than one CMS, and if you
are using a Java application server, you must modify the web.xml files in the
PlatformServices\WEB-INF\ directory of your web application deployment.
113

To configure the application servers to use the CMS cluster, complete the
following steps on both the application servers:
1. Open web.xml. In our setup, the file is located in the following directory:
C:\Tomcat\Tomcat55\webapps\PlatformServices\WEB-INF.
2. Locate the following section in the file:
<! -- EXAMPLE: <context-param> <param-name>cms.clus
ters</param-name>
3. Remove the comment tags from this section of the file.

4. For the param-name tag cms.clusters, enter the cluster name for
param-value. Begin each cluster name with a "@", and separate each
cluster name with a comma. The configuration must appear as follows:
<context-param>
<param-name>cms.clusters</param-name>
<param-value>@MIRA1</param-value>
</context-param>
5. In the second param-name tag, add the name of the first cluster. Do not
start the cluster name with the "@" symbol. The configuration must appear
as follows:
<context-param>
<param-name>cms.clusters.MIRA1</param-name>
6. In the second param-value tag, type the name of each CMS in that cluster
and enter the port number of the CMSs, if required. Separate each CMS
name with a comma. The port number is separated from the CMS name
with a colon (:) The port number is assumed to be 6400 unless it is
specified. The configuration must appear as follows:
<context-param>
<param-value>CLUSTER1:7400, CLUSTER2:7400, CLUS
TER3:7400</param-value>
</context-param>
7. Save your changes and close web.xml.

8. Restart Tomcat.
9. Verify the settings by logging into InfoView and the CMC.
The application servers are now configured to use the CMS cluster.
References:
114

Setting up the web servers
Clustering/Session Replication - HOW TO

Load Balancer - HOW TO
redhat - Failover support

The Windows pattern includes two web servers for scalability and redundancy.
Before we install the web servers we will be remove the existing, lower level
version web servers.
Setting up the web servers involves the following tasks:
Installing the HTTP servers
Configuring a connection from the HTTP servers to the application servers.
Uninstalling Apache version 2.0.59

Before uninstalling Apache HTTP Server, take a back up of the configuration
files. For more information, see Uninstallation of Apache 2.0
To uninstall Apache version 2.0.59, complete the following steps:
1. Log into Apache by using the local system account.
115

2. SelectStart -> Control Panel -> Administrative Tools -> Services.

Select Apache2, and click Stop.
116

3. SelectStart -> Control Panel -> Add Remove Programs. Select Apache
HTTP Server 2.0.59, and click Remove. (add image)
4. Click Yes.
5. Navigate to the Program Files folder and delete the Apache Group
folder.
Apache version 2.0.59 is uninstalled.
Installing and configuring Apache version 2.2.9

We will install and configure Apache version 2.2.9 on both web server
machines, http1 and http2.
To install and configure Apache HTTP Server 2.2.9, complete the following
steps:
1. Download and then double-click apache_2.2.9-win32-x86-no_sslr2.msi.
2. Click Run.
3. Click Next. Read and accept the license agreement to proceed with the
installation.
4. Click Next.
5. Type the following information:
Network Domain: Enter the name of the DNS domain in which your
server will be registered.
Server Name: Enter the full DNS name of your server.
Administrator's Email Address: Enter the server administrator's or
webmaster's email address. By default, this email address is displayed
to the client along with error messages.
117

For whom to install Apache: Select All Users, on Port 80, as a Service
- This is recommended if you want your new Apache server to listen
at port 80 for the incoming traffic. It will run as a service (that is, Apache
will run even if no one is logged in on the server at the moment). Select
Current User, on Port 8080, when started Manually if you'd like to
install Apache as an experiment or if you already have another WWW
server running on port 80.
6. Select Custom as the installation type. This installation type allows you
to specify what you want to install. A full install will require about 13 Mb
of free disk space. This does not include the size of your websites.
7. Select the features of the Apache HTTP server, and click Next. We
selected all the features.
To modify your selections, click Back and make the necessary changes.
8. Click Install.
10. To check the status of Apache, select Start -> Administrative Tools ->
Services.
11. Launch Internet Explorer, and type http://localhost:80 or
http://http1.
Apache version 2.2.9 is installed and configured.
Configuring each of the Apache HTTP servers, http1

and http2, with Tomcat
We need to configure the Apache HTTP server to connect to Tomcat. The
mod_jk connecter is used to connect the Tomcat JSP container with web
servers, such as Apache, Netscape, iPlanet, SunOne, and even IIS by using
the AJP protocol.
You can download mod_jk connecter from the following link: Download
mod_jk connecter.
From the above given link we need to download mod_jk-1.2.26-httpd-2.2.4.so
(for Apache 2.2, and works with Apache 2.2.4 and later). Rename to
mod_jk.so before putting it in your Apache2.2/modules directory.
118

You can configure Apache by inserting the necessary directives within the
configuration files (in plain text format). The location of the main configuration
file, which is called httpd.conf, is specified while compiling the file. However,
you can change the location of this file with the -f command line flag. Though,
for historical reasons, some sites include srm.conf and access.conf files,
you can also add other files with the help of the Include directive. You can
place any directive in the configuration files. Apache takes note of the
changes you have made to the configuration files only when you start or
restart the server.
The httpd.conf file is located in the \Program Files\Apache Software
Foundation\Apache2.2\conf folder. Add the following lines to the
httpd.conf file to configure it to work with Tomcat. Take a backup of
httpd.conf before modifying it.
LoadModule jk_module modules/mod_jk.so"
JkWorkersFile conf/workers.properties"
JkLogFile logs/mod_jk.log
JkLogLevel info
JkLogStampFormat "[%a %b %d %H:%M:%S %Y] "
JkOptions +ForwardKeySize +ForwardURICompat -ForwardDirectories
JkRequestLogFormat "%w %V %T"
JkMount /jsp-examples/* loadbalancer
JkMount /servlets-examples/* loadbalancer
JkMount /clusterjsp/* loadbalancer
JkMount /* loadbalancer
JkMount /*.jsp loadbalancer
LoadModule jk_module modules/mod_jk.so - Informs the Apache server

about the location of the mod_jk libray and prompts the server to load the
library.
JkWorkersFile conf/worker.properties - Informs mod_jk about the location
of the worker.properties file.
JkLogFile logs/mod_jk.log - Instructs mod_jk where to write the logs that are
related to mod_jk.
The JkLogLevel directive enables you to specify the level of logging that
must occur to the log file that was defined by using JkLogFile.
The JkMount directive indicates the URI contexts that are sent to an ASF
Tomcat worker.
We need to configure workers.properties file that is located in the
\Program Files\Apache Software Foundation\Apache2.2\conf folder.
119

A Tomcat worker may be defined as a Tomcat instance that awaits

instructions, on behalf of a web server, to execute servlets or other content.
For instance, an Apache web server may forward servlet requests to a Tomcat
process (the worker) that runs behind it.
We need to add the following lines and save the file to create workers.prop
erties:
workers.java_home="C:\Program Files\Java\ jre1.5.0_09"
worker.list= appserv1, appserv2, loadbalancer
#define appserv1 instance TomCat worker
worker. appserv1.port=8009
worker. appserv1.host=192.168.2.11
worker. appserv1.type=ajp13
worker. appserv1.lbfactor=1
worker. appserv1.cache_timeout=600
worker. appserv1.socket_keepalive=1
worker. appserv1.socket_timeout=300
#failover node for appserv1
worker. appserv1.redirect= appserv2
#define appserv2instance TomCat worker
worker. appserv2.port=8009
worker. appserv2.host=192.168.2.12
worker. appserv2.type=ajp13
worker. appserv2.lbfactor=1
worker. appserv2.cache_timeout=600
worker. appserv2.socket_keepalive=1
worker. appserv2.socket_timeout=300
#failover node for appserv2
worker. appserv2.redirect= appserv1
#define load balancer
worker.loadbalancer.type=lb
worker.loadbalancer.balanced_workers= appserv1, appserv2
worker.loadbalancer.sticky_session=true
When starting up, the web server plug-in instantiates the workers whose
names appear in the worker.list property. You can map requests to these
workers.
The values appserv1 and appserv2 are specified in the <Engine> element
of the Tomcat instances.
The meanings for the worker property name are:
120
Port: The port where the Tomcat worker is listening for ajp13 requests.
Host: The host where the Tomcat worker is listening for ajp13 requests.
Type: The ajp13 type workers forward requests to out-of-process Tomcat
workers by using the ajpv13 protocol over TCP/IP sockets.
Lbfactor: The load-balancing factor for the worker.

Redirect: In case of a failover, the requests are forwarded to the other

Tomcat server.
At the command line, type the following syntax to check the config files:
c:\Program Files\Apache Software Foundation\Apache2.2\bin>httpd
-t
Syntax OK
Restart your Apache server. Changes to the main configuration files are
recognized by Apache only when it is started or restarted. If the configuration
is successful, you can view the Tomcat homepage when you type
http://http1:80.
Failover
Tomcat does not provide a built-in failover mechanism to detect when a
cluster member crashes. Hopefully, a future version of Tomcat will provide
the failover feature that can be used to find the availability of a specific cluster
member, to ensure that it's ready to service incoming web requests. Clustering
solutions typically provide the following levels of failover capabilities:
1. Request-level fail over: If one of the servers in the cluster goes down, all
subsequent requests must be redirected to the remaining servers in the
cluster. This involves using a heartbeat mechanism to keep track of the
server status and to avoid sending requests to the servers that are not
responding. In our cluster setup, a Tomcat instance acting as a load
balancer takes care of request-level failover by forwarding web requests
to another node in the cluster.
2. Session-level fail over: The HTTP server maintains and manages sessions
of the web client. In session-level failover, if one of the servers in the
cluster goes down, another server in the cluster must be able to carry on
with the sessions that were being handled by the first server, with minimal
loss of continuity. This involves replicating the session data across the
cluster. A Tomcat cluster with session replication capability takes care of
session-level fail over.
Note:
The installation process will register Apache as a Windows service. The

registration of Apache as a Windows service fails if port 80 is preoccupied
with some other server on the machine. To resolve this issue, open the
httpd.conf file available in the conf folder of the Apache installation, and
121

Configuring the reverse proxy
Change the port value specified after Listen (Listen 80) to that of some other
free port. For example, Listen 81.
Search for ServerName (ServerName http1:80) and change the port value
to the value provided at Listen (http1:81)
Manually register Apache as a Windows service.
At the Windows command line, type httpd -k install. This command will
install Apache as a Windows service with the default name Apache2. If a
different version of the Apache server with the same default service name
already exists, then specify a different name for the service. For example,
httpd -k install -n <ServiceName>.

The reverse proxy server machine has two network cards; one for external
communication and the other for internal communication. This allows the
reverse proxy to mask IP addresses of internal systems.
Open the httpd.conf file available in the \Program Files\Apache
Software Foundation\Apache2.2\conf directory, and add the following
lines:
ProxyPass
http://192.168.1.13/CmcApp
ProxyPassReverse
http://192.168.1.13/CmcApp
ProxyPassReverseCookiePath
/CmcApp
/CmcApp
/CmcApp
/CmcApp
ProxyPass
/PlatformServices
http://192.168.1.13/PlatformServices
ProxyPassReverse
/PlatformServices
http://192.168.1.13/PlatformServices
ProxyPassReverseCookiePath /PlatformServices /PlatformServices
ProxyPass
/CmcAppActions
http://192.168.1.13/CmcAppActions
ProxyPassReverse
/CmcAppActions
http://192.168.1.13/CmcAppActions
/CmcAppActions /CmcAppActions
ProxyPass
/AnalyticalReporting
http://192.168.1.13/AnalyticalReporting
ProxyPassReverse
/AnalyticalReporting
http://192.168.1.13/AnalyticalReporting
/AnalyticalReporting /Analytical
122

Reporting
ProxyPass
/CrystalReports
http://192.168.1.13/CrystalReports
ProxyPassReverse
/CrystalReports
http://192.168.1.13/CrystalReports
/CrystalReports /CrystalReports
ProxyPass
/VoyagerClient
http://192.168.1.13/VoyagerClient
ProxyPassReverse
/VoyagerClient
http://192.168.1.13/VoyagerClient
/VoyagerClient /VoyagerClient
ProxyPass
/InfoViewApp
http://192.168.1.13/InfoViewApp
ProxyPassReverse
/InfoViewApp
/InfoViewApp /InfoViewApp
ProxyPass
/InfoViewAppActions
http://192.168.1.13/InfoViewAppActions
ProxyPassReverse
/InfoViewAppActions
http://192.168.1.13/InfoViewAppActions
/InfoViewAppActions /InfoViewAp
pActions
ProxyPass
/OpenDocument
http://192.168.1.13/OpenDocument
ProxyPassReverse
/OpenDocument
http://192.168.1.13/OpenDocument
/OpenDocument /OpenDocument
ProxyPass
/PerformanceManagement
http://192.168.1.13/PerformanceManagement
ProxyPassReverse
/PerformanceManagement
http://192.168.1.13/PerformanceManagement
/PerformanceManagement /Perfor
manceManagement
ProxyPass
/dswsbobje
http://192.168.1.13/dswsbobje
ProxyPassReverse
/dswsbobje
http://192.168.1.13/dswsbobje
/dswsbobje /dswsbobje
ProxyPass
/PMC_Help
http://192.168.1.13/PMC_Help
ProxyPassReverse
/PMC_Help
123

Load balancer setup
http://192.168.1.13/PMC_Help
/PMC_Help /PMC_Help
Remote servers can be mapped into the local server by using the ProxyPass
directive. The local server functions as a mirror of the remote server and not
as a proxy in the conventional sense. The name of the local virtual path is
path, and url is a partial URL for the remote server. For example, ProxyPass
<path> <URL>
Ex.
ProxyPass
/InfoViewApp
In this example, we are mapping the /InfoViewApp path to the load balancer
device by using the URL: http://192.168.1.13/InfoViewApp.
http://192.168.1.13 is the virtual web server of our CSS 11501 device.
The ProxyPassReverse directive allows the Apache server to adjust the URL
in HTTP response headers sent from a reverse proxied server. This is
necessary if you use Apache as a reverse proxy (or gateway) to avoid
bypassing the reverse proxy because of HTTP redirects on the back-end
servers that stay behind the reverse proxy.
ProxyPassReverse <path> <URL>
Ex. ProxyPassReverse
/InfoViewApp
References:
Proxy
ProxyPass
ProxyPassReverse
Load balancer setup

The load balancer used in this deployment is a Cisco Content Services Switch
or "CSS". The following table describes the version of the Cisco Load
124

Load balancer setup
Balancer used in our Windows pattern deployment. You can use the following
command to get the version details of the Cisco Load balancer:
CSS11501# version
Version
sg0730005 (07.30.0.05)
Flash (Locked)
07.30.0.05
Flash (Operational)
07.30.0.05
Type
PRIMARY
Licensed Cmd Set(s)
Standard Feature Set
Note:
The initial configuration used a CISCO Local Director LDIR-430, but this
device was replaced due to setup problems
Load balancer setup includes the following steps:
Creating HTTP services on the load balancer

Sticky cookie configuration
Verifying the load balancer configuration
Creating HTTP services on the load balancer

A administrative user account for the CSS machine. For this setup, access
was requested for an existing CSS machine located on our internal network.
To create services on the load balancer for the two HTTP servers that
aredeployed as part of the Windows pattern, complete the following steps:
1. Telnet to the CSS machine using a command similar to the one below.
The IP address for your CCS machine is unique to your environment.
telnet 168.192.2.1
2. When prompted, enter the administrative user name and password for
the CSS machine.
125

Load balancer setup
3. After logging into the CSS machine, the next step is to find an available
CSS interface. You can view available CSS interfaces by typing the
following command:
show interface
4. Type config -t to enable configuration mode.

5. Select an available interface. In this example, we select an interface
named Ethernet_Mgmt by typing the following command:
int Ethernet_Mgmt
6. The next step is create a service on the CSS machine for each of the
HTTP Servers. The services are required by the CSS machine in order
to direct incoming requests to the HTTP servers. To create services
named web1 and web2, we enter the following commands:
service web1
ip address 168.192.6.15
string webserver1
keepalive type http
active
service web2
ip address 168.192.6.16
string webserver2
keepalive type http
active
service web1: Creates a service named web1

ip address 168.192.6.15: Specifies the IP address for the web server.
In this case, it is the IP address for the webserver1 machine.
string webserver1: webserver1 is the string that will be appended to
the incoming URL, thereby directing requests to the webserver1
machine.
keep alive type http: With keepalive type set to http, the CSS will
generate http requests and check the response to ensure that the
service is active. If the service is found to be inactive, the CSS will
remove the service from its load balancing algorithm.
active: The active command activates the service on the CSS.
Note:
The IP addresses used in your setup will be unique to your environment.

HTTP services are created on the load balancer.
126

Load balancer setup
Sticky cookie configuration

This section describes sticky cookie configuration.
The following steps assume you are already logged on to the CSS machine.
A sticky cookie allows the CSS to ensure that a client remains connected to
the same HTTP server during a session.
To configure the sticky cookie, complete the following steps:
1. Defining an owning group for the sticky cookie and specify the purpose
of the group by entering the following commands:
In this example, the owning group for the cookie is EDI. We have defined
arrowpoint_cookie as the purpose of this group using the content
command. You can specify any value for owner or content. For example,
you can specify owner Mygroup and content MyStickyCookie. The
values you specify are arbitrary.
owner EDI
content arrowpoint_cookie
2. After you have defined the sticky cookie type, type the following command
to configure the sticky cookie:
protocol tcp
port 80
add service web1
add service web2
vip address 192.168.6.17
advanced-balance arrowpoint-cookie
balance leastconn
active
protocol tcp: Indicates the communication protocol

port 80: Indicates the port number used for communication
add service: Indicates which services are available for client
connections 86
vip address 192.168.6.17: Virtual IP address of the CSS machine. All
incoming requests are directed to the virtual IP address of the CSS
machine before being routed to an HTTP server
advanced-balance arrowpoint-cookie: Indicates that an
arrowpoint-cookie is used for load balancing
127

Load balancer setup
balance leastconn: Indicates that a client connection will be routed to

an HTTP machine with the least current connections
active: Sets the services to active mode
3. After you have configured the sticky cookie, exit cookie configuration
mode.
4. Type copy run start to save your configuration.
Sticky cookie is configured.
Verifying the load balancer configuration

This section describes verifying the load balancer configuration.
The following steps assume you are logged on to the load balancer device.
After creating services for the HTTP servers and performing sticky cookie
configuration, you should verify the load balancer configuration.
To verify the configuration, complete the following steps:
Run the following command on the load balancer device:

The output should appear similar to the following:
show run
!*************************** GLOBAL
***************************
no restrict web-mgmt
!************************* INTERFACE
*************************
interface Ethernet-Mgmt
phy 10Mbits-HD
!************************** CIRCUIT
**************************
circuit VLAN1
ip address 192.168.6.250 255.255.255.0
!************************** SERVICE
**************************
service web1
ip address 192.168.6.15
string webservice1
keepalive type http
active
service web2
ip address 192.168.6.16
string webservice2
keepalive type http
active
128

Load balancer setup
!*************************** OWNER
***************************
owner EDI
content arrowpoint-cookie
protocol tcp
port 80
add service web1
add service web2
vip address 192.168.6.17
advanced-balance arrowpoint-cookie
balance leastconn
active
CSS11501#
The load balancer configuration is verified.
129

Load balancer setup
130
Installing and deploying

Performance Management
components
Installing and deploying Performance Management components

Overview
Overview
This chapter describes how to install and deploy Performance Management
components. Installing and deploying Performance Management components
involves the following tasks:
Installing Performance Management components

Configuring Performance Manager
References:
Getting Started with Performance Manager
BusinessObjects Performance Manager XI 3.1 Administrator's Guide
BusinessObjects Enterprise XI 3.1 Installation Guide for Windows
Installing Performance Management

components
This section describes how to install Performance Management components.
To install Performance Management components, complete the following
steps:
1. Log into your system by using the account you created for installing the
BusinessObjects Enterprise server.
2. Insert the installation media, and double-click the setup.exe program.
The BusinessObjects Enterprise XI 3.1 Installation Wizard appears.

3. In the "Open File - Security Warning" dialog box, click Run.
The "Application Maintenance" screen appears.
132

4. In the "Application Maintenance" screen, select Modify, and click Next.

5. In the "Select Features" dialog box, click Server Components.
The list of server components appears.
133

6. From the list of server components, select Dashboard and Analytic

Servers.
7. Select the Enable servers upon installation option.
8. Click Next.
9. In the "CMS" dialog box, type the CMS host name, CMS port number,
and the CMS administrator password.
10. Click Next. The installation process starts.
134

11. Click Finish after the installation is complete.

Performance Management components are successfully installed.
Repeat steps 1 to 11 to install Performance Management components on
all three systems in the cluster.

You must create the Performance Manager repository before you start to
work with Dashboard and Analytics.
A Dashboard and Analytics deployment includes two repositories:
The Central Management Server (CMS) database - To store user security
information, documents, dashboards, analytics, performance models,
schedules, and the semantic layer that maps to your corporate data sources
(for example, metric universes and business views).
The Performance Manager repository - To store metrics, calendars, goals,
and sets that are specific to Dashboard and Analytics.
Configuring Performance Manager involves the following tasks:
135

Creating a target database connection

Setting up the Performance Manager repository
Adding a universe to the Performance Manager repository
Creating a calendar
Creating a target database connection

To create a target database connection, complete the following steps
1. Open the Universe Designer by selecting Start -> All Programs ->
BusinessObjects XI 3.1 -> BusinessObjects Enterprise -> Designer.
The "User Identification" window appears.
2. In the "User Identification" window, type the system name, user name,
password, and the authentication type.
If required, click Cancel.
3. In the "Universe Designer" window, selectTools -> Connections.
4. In the "Wizard Connection" window, click Add

5. In the "Define a new connection" window, click Next.
6. In the "Database Middleware Selection" window, select Secured as the
Connection Type, and type the connection name, for example, PMCRepo.
136

7. Select the appropriate database node, middleware node, and data access
driver for the connection. For example, if you are using Oracle 10 database
as the repository, select Oracle -> Oracle10 -> Oracle Client.
8. Click Next
The "Login Parameters" window appears.
137

9. In the "Login Parameters" window, specify the login parameters to access

the Oracle database server. In Authentication Mode, type the user name,
password, and select the service.
10. Click Test Connection.
11. In the "Configuration Parameters" window, select the default values, and
click Next.
12. In the "Custom Parameters" window, click Finish.
The new connection is added to the Connections List.
13. Click Finish to exit Wizard Connection.
A connection to the target database is created.
Setting up the Performance Manager repository

This section describes how to set up the Performance Manager repository.
To set up the Performance Manager repository, complete the following steps:
1. Log into InfoView.
138

2. In the InfoView homepage, selectOpen -> Dashboard and Analytics

Setup.
The Setup page appears.
3. Click System Setup.

The "System Setup" page appears.
4. Click Change to configure the repository.
The "Choose repository connection" panel appears.
139

5. In the "Universe connection" dialog box, select the connection that was
created while setting up the target database connection. For example,
PMCRepo.
6. Click OK.
A warning message appears.
7. Click OK.
The "System Setup" page appears.
8. In the "boe11 System Tables Management" section, click Setup
Repository to configure the repository.
The "Setup Repository panel" appears.
140

9. In the "View Options" tab, click Next.

10. In the "View SQL" tab, click Select All, and then click Execute.
11. In the "Confirm SQL Execution" dialog box, click OK. The SQL is executed
and the repository is configured. On successful execution, the following
message is displayed: "Execution successful". Click OK.
12. Click the System User tab.
13. Under the "System User" tab, type the user name. This user name enables
the engines to create new connections when needed.
The system user must have administrator rights specified in the Central
Management Console (CMC).
141

14. Click Check, and then click Apply.

The Performance Manager repository is configured.
Adding a universe to the Performance Manager

repository
This section describes how to add a universe to the Performance Manager
repository.
To add a universe to the Performance Manager repository, complete the
following steps:
1. Select System Setup -> Universes.
2. Click Add Universe.
The "Add a Universe panel" appears. This panel displays the list of
universes.
3. Click the Refresh button to refresh the list of universes.
4. Select a universe from the list, and click OK.
A confirmation messages appears. Click OK.
142

5. Click the universe you added in step 2, and click Update.

The list of available objects is displayed.
The universe is successfully added to the Performance Manager repository.
Creating a calendar
This section describes how to create a calendar.
In the example discussed in this section, both metrics and goals are based
on a specific time period. The metrics and goals can be associated with a
calendar.
To create an appropriate calender, complete the following steps:
1. Click the Time Config tab. By default, the Calendar tab is selected.
A list of available calendars appears.
2. Click Add.
143

The "Add a Calendar" panel appears.
3. Type a name for the calendar. For example, Monthly Calendar.

4. Type a description. For example, Monthly calendar for the period Jan
2000 to Dec 2009.
5. Under "Type of Periods", select Calendar.
6. In the Interval box, select Monthly.
7. Under "Period Display", select the first day of period, and select
MM/DD/YYYY from the format list
144

8. Under "Calendar Span", select the following:

From Jan/2000
To Dec/2009
9. Click OK.
The "Monthly Calendar" appears in the list of available calendars.
The Performance Manager is successfully configured. We can now create

metrics, goals, analytics, and dashboards.
145

146
Microsoft clustering for FRS

failover


The concept of clustering
Clustering denotes the action of bringing together two or more systems to

work in tandem. Systems are brought together in order to ensure
high-availability, scalability, and reliability, compared to the benefits of using
a single system. If a system in a cluster fails, the resources are immediately
redirected and workload is shared by the other systems in the cluster. As a
result, the end users encounter only a partial failure and are not required to
do anything more than refresh the browser or connect to an application again
to resume their work.
Installation overview
Microsoft clustering is used to set up failover and LUN access for the three
Business Objects XI 3.1 servers to a SAN located within the Enterprise
environment. Clustering these three servers with the SAN provides an
active/passive FRS failover solution to the FRS directories, without using
third-party software to manage the interface.
Note:
LUN is a Logical Unit Number. It is used to refer to an entire physical disk,

or a subset of a larger physical disk or disk volume. The physical disk or disk
volume can be an entire single disk drive, a partition (subset) of a single disk
drive, or disk volume from a RAID controller comprising multiple disk drives
aggregated together for larger capacity and redundancy. LUNs represent a
logical abstraction or a virtualization layer between the physical disk
device/volume and the applications.
Checklist
Ensure that the following are in place before you set up Microsoft clustering
for FRS failover:
148
Microsoft Windows Server 2003 Enterprise Edition Service Pack 2 must

be installed on all machines
A name resolution method
An existing domain model
All nodes must be in the same domain
A domain-level account that is a member of all the nodes in the domain.

Pre-clustering tasks
Before you configure the Clustering Service software, verify the following:
Microsoft Windows Server 2003 Standard Edition Service Pack 2 has

been installed on all machines
Network setup
Shared disk setup
You must verify these on each machine in the cluster.

Network setup
Microsoft recommends that you configure two networks; one for public
communication and the other for private communication.
Shared disk setup
To provide the Business Objects File Repository with failover capability, a

SAN storage implementation is recommended.
We used iSCSI Target software called StarWind, because a SAN is not
available. The iSCSI Target software supports the implementation of an
iSCSI storage area network (SAN) solution, which provides storage
provisioning, and management. Using the iSCSI Target software, you can
create and manage iSCSI targets and iSCSI virtual disks for storage. You
can also schedule, export, and locally mount snapshots of the virtual disks
for use in backup and recovery operations.
Checklist for installing a physical disk resource
Ensure that the disk is configured as basic and not dynamic.

Ensure that all partitions on the disk are formatted using the NTFS file
system.
Ensure that all partitions have a drive letter assigned or that the partitions
are set up as a mounted drive.
Ensure that the disk has a signature.
References:
Microsoft iSCSI Software Target Q and A
Checklist: Installing a Physical Disk resource
Planning Your Server Cluster
149

Windows Server 2003 R2 Enterprise Edition Cluster Server Resource

Center
Cluster Architecture Essentials
Cluster deployment and operation options
Choosing a Cluster Model
Logical Unit Number (LUN)
Adding and configuring the systems to work in the

domain
Currently, the system is in workgroup EDI3. For configuring the MSFT cluster,
we must add the machines to the domain because the MSFT cluster needs
the machines to be in the domain. AUTHENTIC (EDI.com) is the AD Domain
Controller. We need to add Cluster1, Cluster2, Cluster3, and BOEDB to the
EDI.COM domain. Then, we need to create a domain service user. All BOE
cluster Server Intelligence Agents will run under the domain service user.
We must also configure the FRS Filestore to work with the domain service
user.
Adding a system to the domain

To add a system to the domain, complete the following steps:
1. Log into the system with a user account that belongs to the administrator's
group.
2. Specify the DNS entries in the TCP/IP properties.
Without the DNS entries, the system cannot establish contact with
controller of the domain. For information on configuring the DNS entries,
see Configuring the DNS entries on page 151.
3. Right-click My Computer, and click Properties.
4. In the "System Properties" dialog box, select the Computer Name tab,
and click Change.
5. In the "Computer Name Changes" dialog box, select Domain, enter the
domain name, edi.com, in the text box, and click OK.
150

6. In the "Computer Name Changes" dialog box, type the user name and
password of an account that is permitted to join the domain, and click
OK.
The following confirmation message appears: "Welcome to the edi.com
domain."
7. In the "Computer Name Changes" dialog box, click OK, and, in the System
Properties tab, click OK. The "System Settings Change" dialog box
appears.
8. Click Yes to restart the system.
You must restart the system for the changes to take effect.
Your system is now part of the AD domain.
Configuring the DNS entries

To configure the DNS entries, complete the following steps:
1. Select Start -> Control Panel -> Network Connections -> Local Area
Connection.
The "Local Area Connection Status" screen appears.
2. In the "Local Area Connection Status" screen, click Properties.
The "Local Area Connection Properties" screen appears.
3. In the "Local Area Connection Properties" window, select Internet
Protocol (TCP/IP), and click Properties.
The "Internet Protocol (TCP/IP) Properties" screen appears.
4. In the "Internet Protocol (TCP/IP) Properties" screen, select the " Use the
following DNS server addresses" option.
The "Preferred DNS Server" screen appears.
5. In the "Preferred DNS Server" screen, type the IP address of the server
Authentic, that is, 192.168.2.13.
6. Click OK.
The "Local Area Connection Properties" window appears.
7. Click OK.
8. Click Close.
Your machine is configured with the DNS entries.
151

Creating a cluster service account

To configure the MSFT cluster, you must create a domain account under
which the cluster service can run. This section describes how to create a
cluster service account.
To create a cluster service account, complete the following steps:
1. Select Start -> All Programs -> Administrative Tools -> Active
Directory Users and Computers.
The "Active Directory Users and Computers window" appears.
2. In the "Active Directory Users and Computers" window, click Users.
3. In the "menu bar", select Action -> New -> User.
The "New Object - User" panel appears.
4. In the "New Object - User" panel, type cluster_user in the "First name"
text box.
The "Full name" text box is automatically populated with the value of
cluster_user.
5. In the "User logon name" field, type cluster_user.
The "User logon name (pre-Windows 2000)" text box is automatically
populated with the cluster_user value.
6. Click Next.
7. Enter a suitable password for the user cluster_user.
Unselect User must change password option at next login, and select
the User cannot change password option. The password never expires.
8. Click Next.
9. Click Finish.
The cluster service account is successfully added to the list.
Setting the domain user as part of the administrator's group

You must set the domain user, cluster_user, as part of the administrator's
group in all the four systems, namely, Cluster1, Cluster2, Cluster3, and
BOEDB.
152

To set the domain user as part of the administrator's group, complete the
following steps:
1. Right-click My Computer, and click Manage.
The Computer Management window appears.
2. In the "Computer Management" window, expand Local Users and
Groups, and click Groups.
3. Right-click Administrators, and select Properties.
The "Administrative Properties" window appears.
4. In the "Administrative Properties" window, click Add.
The "Select Users, Computers, or Groups" window appears.
5. In the "Select Users, Computers, or Groups" window, type the domain
user name, and click Check Names.
The "Enter Network Password" dialog box appears.
6. In the "Enter Network Password" dialog box, type the user name and
password, and click OK.
The domain user is added to the administrator's group.
7. Click OK.
8. SelectStart > Administrative Tools > Local Security Policy.
9. In "Local Security Settings" window, selectSecurity Settings > Local
Policies > Security options. Interactive Logon: Number of previous
logons to cache (if domain controller is not available) is set to 0 logons.
The Interactive Logon option specifies the number of users who have
cached logon credentials on the local system. Logon information of all
the previous users are cached in the local system. This is to ensure that
a user can log into the local system even if a domain controller is
unavailable. As a result, when a user whose credentials have been cached
in the local system attempts to log in, and if the domain controller is
unavailable, then the following message appears:
Windows cannot connect to a server to confirm your logon
settings. You have been logged on using previously stored
account information. If you changed your account information
since you last logged on to this computer, those changes
will not be reflected in this session.
However, if a user whose credentials have not been cached in the local
system attempts to log in, and if the domain controller is not available,
then the following message appears:
153

The system cannot log you on now because the domain

<DOMAIN_NAME> is not available.
Consider the following points while setting the security policy for caching:
If you set 0 as the value, then caching is disabled
The maximum number of logon attempts cached is 50. For instance,
even if you set a value greater than 50, say 80, the local system caches
only the first 50 logon attempts.
The default value is 10.
10. In the "Local Security Settings" window, select Security Settings > Local
Policies > User Rights Assignment. The cluster_user must be granted
the following permissions:
Act as part of the operating system.
Log in as a service.
If we do not grant the these local policies, then we cannot start the cluster
service.
Domain user is now part of administrator's group.
Configuring the BOE servers to run with the domain user for
Cluster1, Cluster2, and Cluster3
To configure the BOE servers to run with the domain user, complete the
following steps:
1. SelectStart -> All Programs -> BusinessObjects Enterprise -> Central
Configuration Manager.
The "Central Configuration Manager" window appears.
2. In the "Central Configuration Manager" window, select "Server Intelligence
Agent", and click Stop.
3. Right-click "Server Intelligence Agent", and click Properties.
In the "Server Intelligence Agent Properties" window, the Server
Intelligence Agent is logged in with the administrator's account.
4. Replace the administrator account with the domain user account,
cluster_user.
5. In the "Central Configuration Manager" window, select "Server Intelligence
Agent", and click Start.
The Server Intelligence Agent is running now.
154

You have successfully configured the BOE servers to run with the domain
user account.
Configuring the FRS Filestore for the domain account

Before configuring the Microsoft cluster, we used a network share for FRS.
To access the FRS after adding the systems to the domain, we need to
configure the FRS Filestore to work with the domain account.
To configure the FRS Filestore for the domain account, complete the following
steps:
1. Navigate to the location where the FRS Filestore is located, right-click
"MIRA FRS", and select Properties.
In the BOEDB system, the FRS Filestore is located in the E:\MIRA FRS
folder.
2. In the "MIRA FRS Properties" window , click the Security tab, and click
Add.
3. In the "Select Users, Computers, or Groups" panel, type the domain user
name, cluster_user, in the Enter the object names to select text box.
4. Click Check Names.
The "Enter Network Password" panel appears.
5. In the "Enter Network Password" panel, type the user name and password
of an account that is permitted to access edi.com.
6. Click OK. The identified object is displayed, as shown in the following
figure:
7. Click OK. The domain user name appears in the Group or user names:
list.
8. Select the domain user, cluster_user, select "Allow for Full Control", and
click Apply.
9. Click the Sharing tab, and then click Permissions.
The "Permissions for MIRA FRS" window appears.
10. In the "Permissions for MIRA FRS" window, click Add.
The "Select Users, Computers, or Groups" panel appears.
11. In the "Select Users, Computers, or Groups" panel, type the domain user
name in the "Enter the object names to select" text box.
155

12. Click Check Names. The identified object is displayed as shown in the
following figure:
13. Click OK.
The domain user name appears in the Group or user names: list
14. Under Permissions for cluster_user, select domain user cluster_user,
and select Allow for Full Control.
15. Click Apply, and then click OK.
The FRS filestore is configured for the domain account.
References:
Issues faced while configuring the AD domain on page 241
Configuring the disks

To configure the disks, complete the following steps:
1. Right-click My Computer, and select Manage.
The "Computer Management" window appears.
2. In the "Computer Management" window, right-click Unallocated disk
and select New Partition.
The "New Partition Wizard" appears.
3. Click Next in the New Partition Wizard.

The "Select Partition Type" window appears.
4. In the "Select Partition Type" window, select Primary partition, and click
Next.
The "Specify Partition" window appears.
156

5. In the "Specify Partition Size" window, select the default values and click
Next.
The "Assign Drive Letter or Path" window appears.

6. In the "Assign Drive Letter or Path" window, select the Assign the
following drive letter option and select Q for the Quorum disk. For the
data disk, drive letter R or S is recommended. We are using E because
it is already configured.
157

Quorum disk is the first resource that is brought online when the cluster
service attempts to form a disk.
7. In the "Format Partition" window, select Format this partition with the
following settings.
158

a. File system: NTFS

b. Allocation unit size: Default
c. Volume label: Q
Click Next.
8. Review your settings and then click Finish. If you need to modify your
settings, you can click Back and make the necessary changes.
159

The disk configuration starts.

After you configure the disks, you must install and configure the StarWind
iSCSI Target software.
Installing StarWind
StarWind can be downloaded from: StarWind.
To install StarWind, complete the following steps:
1. Download StarWind from the following location: http://www.rocketdivi
sion.com/download_starwind.html
2. Double-click starwind.exe to start the installer. The "Setup - StarWind"
window appears.
3. In the "Setup StarWind" window, click Next.

4. In the "License Agreement" window, select I accept the agreement, and
click Next.
5. In the "Select Destination Location" window, select the default location,
and click Next.
160

6. In the "Select Components" window, select Full installation from the

drop-down list.
By default, Full installation is selected.
7. Click Next.
8. In the "Select Start Menu Folder" screen, select the default values, and
click Next.
9. In the "Select Additional Tasks" window, select the default values, and
click Next.
10. In the "Ready to Install" window, review the values you have specified,
and click Next.
If you want to modify the settings, click Back and then make the required
changes.
The installation starts. When the installation is about to complete, the
"Completing the StarWind Setup Wizard" window appears.
161

Configuring StarWind
To configure StarWind, complete the following steps:
1. Select Start -> All Programs -> Rocket Division Software -> StarWind
-> StarWind.
The "StarWind" window appears.
2. Right-click localhost:3260, and click Connect

3. In the "Login" window, type the user name and password. The default
user name is test, and the default password is test.
162

4. In the toolbar, click Add Device. "The Device type selection" window
appears.
5. Select the "Disk Bridge" device, and click Next.
We selected the Disk Bridge device because we used the physical disk
as the iSCSI target.
6. In the "Please specify Disk Bridge device parameter" window, select the
hard disk you want to set as the iSCSI target. The Asynchronous mode
option is selected by default.
7. Select the Allow multiple concurrent iSCSI connections (clustering)
option, and click Next.
8. In the"Please specify common device parameters" window, specify a
target name, and click Next. You must ensure that the target name you
set is same as the drive name.
9. In the "Completing the Add Device Wizard" window, review the settings,
and click Next. If you want to modify the settings, click Back and make
the necessary changes.
10. In the "Device was successfully added" window, click Finish.
163

Note:
To add more disks, repeat steps 1 to 10 for each disk you want to add.
You have successfully configured the iSCSI targets. These disks will be used
for Quorum and Data disks.
Installing StarPort
After you configure StarWind, you must install an iSCSI software initiator on
the systems that you want to cluster. The iSCSI software initiator enables
you to connect a Windows host to an external iSCSI storage array by using
Ethernet NICs. In this document, installing StarPort, an iSCSI software initiator
from Rocket Division Software, is used as an example.
StarPort can be downloaded from: StarPort.
To install StarPort, complete the following steps:
1. Download StarPort from the following location: http://www.rocketdivi
sion.com/download_starport.html
164

2. Double-click starport.exe.
3. In the "Open File - Security Warning" window, click Run to start the
installation.
The "Setup - StarPort" window appears.

4. In the "The Setup - StarPort" window, click Next.
5. In the "License Agreement" window, read and select I accept the
agreement, and click Next.
6. In the "Select Destination Location" window, select the default values,
and click Next.
165

7. In the "Select Start Menu" folder, select the default values, and click Next.
166

8. In the "Select Additional Tasks" window, select the default values, and
click Next.
9. In the "Ready to Install" window, review the settings, and click Next.
If you want to modify the settings, click Back and make the necessary
changes.
10. In the "Completing the StarPort Setup Wizard" window, click Finish to
complete the installation.
167

You have successfully installed StarPort.
Configuring StarPort
After you install StarPort, you must configure this software initiator. This
section describes how to configure StarPort.
To configure StarPort, complete the following steps:
1. Select Start -> All Programs -> Rocket Division Software -> StarPort
-> StarPort.
2. In the "StarPort" window, select Remote iSCSI devices, and click Add
New Device.
168

3. In the "Welcome to new device installation wizard" window, click Next.
169

4. In the "Device Type" window, select Remote iSCSI device, and click
Next.
5. In the "New Remote iSCSI device parameters" window, type the IP
address of the remote iSCSI device or the name of the machine, and click
Next.
6. In the "iSCSI target selection" window, select an iSCSI target, and click
Next.
7. In the "Completing the Add Device Wizard" window, click Finish.
170

The device is added to the list.

You have successfully added the remote iSCSI device to your system.
Windows clustering
Before setting up the cluster, we need to ensure that Quorum and FRS data
disks are formatted using NTFS, and assigned a drive letter on the first
machine to join the cluster. Following are the disk space requirements for
Quorum and FRS data disks:
500 MB for Quorum partition

100 GB for Input FRS Filestore partition
100 GB for Output FRS Filestore partition
We are using the following setup for Quorum and FRS filestore for purposes
of testing:
1095 MB for Quorum partition

137 GB for Input and Output FRS Filestore partition
To configure the first node, complete the following steps:
171

1. SelectStart > Administrative Tools, and click Cluster Administrator.

2. When prompted by the Cluster Administrator, select Create New Cluster,
and click OK. The New Server Cluster Wizard opens.
3. Click Next to continue.

The "Cluster Name and Domain" screen appears.
4. In the "Cluster Name and Domain" screen, type the domain name and
the cluster name (EDIcluster), and click Next.
The "Select Computer" screen appears.
172

5. When prompted, type the system name of the first machine (CLUSTER1),
and click Advanced. The "Advanced Configuration Options" screen
appears.
In the "Advanced Configuration Options" screen, Typical (full)

Configuration is selected by default. For complex configurations, you can
select Advanced (minimum) Configuration so that the wizard does not
173

automatically locate all the storage devices in the cluster. After you select
the configuration type, click OK and then click Next. The "Analyzing
Configuration" screen appears. The setup process will now run a check
against Cluster1 to validate the ability to place Cluster1 in the cluster.
6. Click Next when the verification is complete. The "Cluster IP Address"
window opens.
7. In the "Cluster IP Address" window, type a suitable IP address for the

cluster, and click Next.
The "Cluster Service Account" page appears.
8. In the "Cluster Service Account" page, type the user name (cluster_user)
and password (vanpassword), and click Next. The "Proposed Cluster
Configuration" page opens. Verify the information, and click Next.
9. When the cluster creation is complete, click Next.
174

The "New Server Cluster Wizard" window appears.

10. In the "Completing the New Server Cluster Wizard" window, click Finish.
EDIcluster is created and Disk Q is configured as the Quorum disk.
11. To validate the cluster, complete the following steps:
a. Select Start -> Administrative Tools, and then click Cluster
Administrator.
b. Expand Groups, and click Cluster Group.
Validation of the cluster is complete.
175

The first node is configured.
Adding nodes to the cluster

To add nodes to the cluster, complete the following steps:
1. In the "Cluster Administrator" windows, select File -> New -> Node.
The Add Node wizard appears. Click Next.
176

2. In the "Select Computers" window, type the name of the systems that
you want to add to the cluster, and click Next.
In the" Advanced Configuration Options" screen, Typical (full)
Configuration is selected by default. You can select Advanced (minimum)
Configuration for complex configurations so that the wizard does not
automatically locate all the storage devices in the cluster.
177

3. In the "Analyzing Configuration" window, click Next.

4. In the "Cluster Service Account" window, type the password
(vanpassword) for the domain user, cluster_user.
178

5. Click Next. The "Proposed Cluster Configuration" page appears.
179

6. In the "Cluster Configuration" page, review the settings, and click Next.
If you want to modify the setting, click Back and make the necessary
changes.
The "Adding Nodes to the Cluster" page appears.
The node is added to the cluster.

7. In the "Completing the New Server Cluster Wizard" window, click Finish.
8. Open "Cluster Administrator" to validate the cluster.
EDIcluster is configured successfully.
180

Configuring FRS to work with Windows cluster Changing cluster Quorum

We had to change the cluster Quorum from Drive Q to Drive P. Initially, we
had planned to use Drive E as data disk. However, because Drive E was
being used for another activity, we changed our plan as follows:
We created an image file of 2 GB by using StarWind, and this image file

was used as the Quorum disk (Disk P). An image file is a virtual hard
drive in a physical disk. This image file is added as an iSCSI disk in all
the three systems in the cluster.
The current disk Q was used as the data disk.
To change the Quorum disk, complete the following steps:

1. Add the new Disk P to the cluster in the Cluster Group. For information
about adding Drive P, see Creating the FRS physical disk resource on
page 184
2. Right-click the cluster name (EDICLUSTER), and click Properties.
3. In the "EDICluster Properties" window, select "Disk P:" as the Quorum

resource from the drop-down menu, and click OK.
181

The Quorum resource has been changed successfully. Now, Disk Q can
be taken offline. Delete it from the Cluster Group so that it can be used
as the data disk.
Configuring the FRS Filestore disk by using the

Windows cluster
For the FRS servers to access the SAN Filestore disk, you must implement
a solution that allows the nodes to communicate with the Filestore directory
through the UNC. You can use this method to incorporate a standard
Active/Passive FRS solution where FRSs can seamlessly failover to the
passive node if the active FRSs become unavailable. Configuring SAN FRS
partitions involves the following tasks:
182
Creating a cluster group

Creating the FRS physical disk resource

Creating the IP address resource

Creating the network name resource
Creating a new resource for the UNC fileshare
Creating a cluster group

To create a cluster group, complete the following steps:
1. Right-click the Groups folder, and selectNew -> Group.
2. Type the name of the group and the description, and click Next
3. In the "Preferred Owners" window, leave the preferred owners field blank,
and click Finish.
183

The cluster group is created. After creating the cluster group, the following
four resources must be added to the cluster group:
The physical disk that represents the SAN Filestore disk drive
An IP address that is dependent on the physical disk resource
A network name that is dependent on the IP address resource
A fileshare resource that represents a UNC path by using the network
name resource, and points to the physical directory location of the
FRS directory.
Creating the FRS physical disk resource

To create the FRS physical disk resource, complete the following steps:
1. Right-click the cluster group, and select New -> Resource.
2. Specify a name, description, resource type (physical disk) and group,
and click Next.
184

3. In the "Possible Owners" window, ensure that all machines in the cluster
are identified as "Possible Owners", and click Next.
185

4. Leave the Dependencies field blank for the disk resource, and click Next.
5. Select the disk associated with the SAN Filestore, and click Finish.
The physical disk resource is created.
Creating the IP address resource

To create the IP address resource, complete the following steps:
2. Specify a name, description, resource type (IP address), and the name
of the cluster group, and click Next.
186

3. In the "Possible Owners" window, ensure that all machines in the cluster
4. Do not select any resource dependencies. Click Next.
187

5. Specify an IP address and subnet mask, select the appropriate local area
connection for the network, and click Finish.
188

The IP address resource is created.
Creating the network name resource

This section describes how to create a network name resource.
To create a network name resource, complete the following steps:
2. Specify a name, description, resource type (network name), and cluster
group, and click Next.
3. In the "Possible Owners" window, ensure that all machine in the cluster
4. Create a dependency on the IP address resource, and click Next.
189

5. Specify the network name parameters, for example, XI31SANSHARE.

Click Finish.
The network name specified must be the host name that binds to the IP
address resource.
190

The network name resource is created.

Note:
After the resource has been created and the cluster group is started, the
host name specified must resolve (run ping tests from another machine to
confirm) the correct IP address the network name is dependent on. We ran
a test successfully from the Cluster2 system.
191

Creating a new resource for the UNC fileshare

After creating the network name resource, a resource must be created for
the UNC fileshare.
To create a new resource for the UNC fileshare, complete the following steps:
2. Specify "File Share" as the resource type, add it to the existing FRS cluster
group, and click Next.
192

3. Ensure that all machines in the cluster are identified as "Possible Owners",
and click Next.
4. In the "Dependencies" window, make the UNC fileshare resource
dependent on the other three resources in the cluster group, namely,
physical disk, IP address, and the network name.
193

5. In the "File Share Parameters" window, type a name for the resource that
will be used to resolve the share over UNC, and set the physical path to
the Filestore root directory, where the Input and Output FRS directories
are stored.
194

6. Click Permissions to set the permissions on the share.

Ensure that the Windows domain account controlling the Input/Output
FRS servers has read/write permissions to the share.
7. In the "Permissions" window, click OK.
8. In the "File Share" window, click Finish.
Ensure that the Fileshare resource was created properly and that it is
running in the cluster group.
9. After creating the fileshare cluster resource, ensure that the UNC path is
resolvable over the network. To do this, select Start -> Run on one of
the XI 3.1 servers in the Windows cluster that is running the FRS servers,
type \\XI31SANSHARE\FileStore, and click OK.
195

The directory opens successfully in Windows Explorer, confirming the

successful resolution of the UNC fileshare.
A new resource is created for the UNC fileshare.
Updating the Filestore directory for Input and Output

FRS
After the Filestore directory is set up, you must update the Input and Output
FRS with the UNC path information. To update the Filestore directory,
1. Log into Central Management Console.
2. In the Central Management Console home page, click Servers
management area.
3. In the "Servers List" window, right-click MIRA1.InputFileRepository
server, and select Properties.
196

4. In the "MIRA1.InputFileRepository" window, set the temporary directory

and Filestore directory values in the Input Filestore Service section. For
example, \\XI31SANSHARE\FileStore\Input\temp and \\XI31SAN
SHARE\FileStore\Input.
5. Restart the server.

The FRS is configured to work with the Windows cluster.
Repeat steps 1 to 5 for each Input and Output FRS in your setup.
197

198
Deployment and migration

planning

Overview
Overview
The following options are available for migrating contents from XI R2 to XI
3.1:
Back up the contents of XI R2 by using a BIAR file

Copy the entire XI R2 CMS to XI 3.1 CMS by using a CMS update tool
such as Central Configuration Manager
Install XI R2 and XI 3.1 side by side and then migrate the contents by
connecting to the XI R2 CMS and XI 3.1 CMS by using Import Wizard.
The first option, namely, backing up the contents of XI R2 by using a BIAR

file is not recommended because we cannot export the contents if the size
of the BIAR file is more than 25 MB. Hence, we may have to use several
BIAR files to migrate the contents. Moreover, BIAR files are used to back up
contents only in the case of small repositories.
The second option, namely, copying the contents by using the CMS update
tool, CCM, allows you to copy all the contents in one CMS database to
another CMS database. However, this option is useful only if a full migration
is being planned. Customers, on the other hand, usually prefer to upgrade
incrementally, that is, by upgrading one application at a time, than attempt
a full migration.
Using the Import Wizard to migrate contents directly from XI R2 to XI 3.1 is
the best option to migrate one application at a time and allow users to connect
to the existing XI R2 system simultaneously, so that we can reduce the
downtime. This option also allows us to monitor the progress of the migration
process and verify the integrity of the content. Given these advantages, we
selected this option.
200

CMS to CMS upgrade by using Import Wizard
CMS to CMS upgrade by using Import

Wizard
Migrating content from XI R2 to XI 3.1 by using
Import Wizard: CMS-To-CMS method
As part of this exercise, we will adopt a phased approach to migration; we
will first migrate about 10 percent of the content and then migrate the
remaining content. We know that there are about 3800 objects (including
Crystal Reports, Web Intelligence, and Desktop Intelligence documents) and
about 9209 users who belong to 59 different root groups.
In the first phase, we will migrate all the users and groups along with the
Folder_1 (Folder_1 contains about 320 Crystal Reports objects). We are
migrating all the users and groups so that security is also migrated along
with folders/groups/documents. This will ensure that there are no security
breaks and we don't have to setup the security again on the destination
system.
We will use Import Wizard of XI 3.1 to migrate the contents.
Reference Links:
BusinessObjects Product Guides
BusinessObjects Enterprise XI 3.1 Import Wizard Guide bip_ImportWiz_en.pdf
BusinessObjects Enterprise Administrator's Guide - xi3-1_bip_admin_en.pdf
First phase - Migrating 10 percent of the applications

1. Launch Import Wizard from the XI 3.1 Cluster3 machine by selecting Start
> All Programs > BusinessObjects XI 3.1 > BusinessObjects
Enterprise > Import Wizard.
The "Import Wizard" welcome screen appears. Click Next.
201

2. In the "Source environment" screen of the Import Wizard, we can select

different sources such as BusinessObjects Enterprise XI3.0,
BusinessObjects XI, XIR2 Release2, BusinessObjects 6.x, and so on.
Select BusinessObjects Enterprise XI Release2 from the drop-down
list, and enter the XI R2 login information with the port number of the
CMS. Click Next. Ensure that you have specified the correct XI R2 CMS
port number (6400) because both XI R2 and XI 3.1 installations are
running parallel on the same machine.
The "Destination environment" page appears and prompts for login

information for the XI 3.1 system.
202

3. Enter the user credentials and the cluster name with the port number
(7400), and click Next.
The "Select Objects to Import" page appears.
4. In the "Select Objects to Import" page, select the following options:
Import Users and User Groups
Import Corporate Categories
Import Folders and objects
Import Repository Objects
Import Universes
203

Note:
When we are exporting objects, it is a general practice to export users

and groups so that the rights associated with the objects are also
exported at the same time.
5. In the "Import Scenario" page, select the second option to update the
destination system by using CUID as a reference to compare source and
destination systems. Selecting this option will enable the Import Wizard
to compare identical users/groups/objects that exist in the destination
system (XI 3.1) and the source system (XI R2) based on the CUID. The
option to rename objects if they already exist on the destination system
must also be checked so that Import Wizard can rename these objects.
Click Next.
204

In the "Incremental Import" page, by default, the options are checked, as

shown below.
6. Do not modify any of the selections (because we are migrating for the
first time, the destination system is empty and nothing is overwritten),
and click Next.
205

The Import Wizard starts retrieving the users and groups. The "Users and
Groups" page displays the list of users and groups to be migrated.
206

7. Select all the users and groups by selecting Select All, and click Next.
The "Categories" page appears.
8. In the "Categories" page, select all the categories by selecting the Select
All option. In this phase, we are importing only 10 percent of the XI R2
documents, and these documents are mapped to different categories and
groups. We will import all the categories because we do not know which
documents are mapped to which categories. However, we will not select
the "Import all the objects" option because selecting this option will result
in the migration of all the documents in the repository that are mapped
to these categories.
207

9. In the "Folders and Objects" page, select Folder_1 and the "Import all
instances" option for each selected object. This option enables you to
select even the scheduled instances of the reports under the folder. Click
Next.
208

10. Leave all the fields blank. This is because we are not migrating the
application folders.
11. In the "Import options for universes and connections" page, select the
third option to migrate only the universes and connections based on which
the reports are created. The reports referred to here are those we selected
in step 9. This is to ensure that we don't migrate all the universes and
connections at once. If any of the documents based on these universes
are selected, then, by default, these universes are also imported. We will
also select the default option, "Keep universe overloads for the imported
users and groups". Selecting this option will result in the migration of
restrictions, if any. Click Next.
209

12. In the "Universe folder and universes" page, select the additional universes
to be imported. We will leave this section blank because additional
universes will be migrated only in the next stage. Click Next. We found
that no universe was selected. This implies that Crystal Reports
documents under Folder_1, which we selected in step 9, are not based
on any of the universes and that these report documents were created
by using ODBC connections.
13. In the "Import repository objects options" page, select the third option to
migrate repository objects that are being used by the reports we selected
in step 9. Click Next.
210

14. In the "Import Options for publications" page, select "Do not import
recipients" option. We selected this option because we do not have any
publications in our setup.
211

The "Ready to Import" page displays the summary of the selections made.
To change of these selections, click Back and make the necessary
changes.
15. Click Finish to start the import.
The "Import Progress " page displays the list of objects/users that are
being migrated and the overall status of the migration process. After the
import process is complete, the View Detail Log button is automatically
enabled.
212

16. Click the View Detail Log button to view the details of the import process,
such as errors and success.
213

Note:
The process of migrating 10 percent of the content took about nine hours to
complete. We observed that a number of logs (about 35 GB) was generated
on the client machine. We suspect that this is the reason why the import
process took so long to complete.
Observations on the import process

From the Detail Log, we discovered that a number of users and groups,
folders, and categories were not imported to the destination system. This is
because the LDAP users and groups failed to migrate.
The error message displayed for users and groups was similar to the
following:
"Committing the export object to the destination CMS failed. Reason: Failed
to commit objects to the server. Duplicate object name in the same folder".
The reason for the failure in the case of personal folders and categories was
displayed as follows:
"Owner of this Personal Category and Personal Folder was not found".
Rest of the users and groups and their folder/categories, selected Folder_1
with CR were migrated accurately.
214

After reviewing the logs, click Done. An Import Wizard rights verification tool
is launched. If you are importing objects from any source environment other
than BusinessObjects Enterprise XI 3.x or an XI 3.x BIAR file, the Import
Wizard displays a dialog box, informing you that it will run a rights verification
215

tool. This tool searches for child objects on the destination system with rights
that have not been granted to their parent objects. If the tool finds any such
objects, the Import Wizard removes the rights from the child objects.
Reason for failure of Business Objects NT users Group migration:
We did not had any users belonging to this group in our XIR2 setup and
hence we did not enable the NT Authentication is enabled authentication
option and other details for the same prior to the migration and hence this
group was not migrated.
Note:
After the migration is complete, we did some basic testing for viewing, refresh,
modification and scheduling of the imported reports, LDAP user/Enterprise
logins and all seemed fine.
LDAP users and groups migration failed on page 238.
Second phase - Migrating 90 percent of the

applications
This section describes the second phase of the migration process.
1. Launch the Import Wizard from the XI 3.1 Cluster3 machine by
selectingStart -> All Programs -> BusinessObjects XI 3.1 ->
BusinessObjects Enterprise -> Import Wizard. Click Next.
The "Import Wizard" welcome screen appears.
2. In the "Source environment" screen of the Import Wizard, select
BusinessObjects Enterprise XI Release2 from the drop-down list, and
type the XI R2 login information along with the port number of the CMS.
We have specified the port number of the XI R2 CMS as 6400. Click Next.
216

The "Destination environment" page prompts for the login credentials for
the XI 3.1 system.
3. Type the user credentials and the cluster name with the port number
(7400), and click Next.
217

4. In the "Select Objects to import" page, click Select All and clear the
following selections: "Users" inbox, favorite folders and so on. We cleared
these selections because we have already exported them in the first
phase of the migration. This option need not be selected if the users and
groups are already in the destination system. However, it is a general
practice to export the users and groups, to ensure that the rights
associated with the users and groups are also migrated. We did not select
server groups, calendars, and profiles because contents corresponding
to these categories are not available in the source system. Click Next.
218

5. In the "Import Scenario" page, select the second option to update the
destination system by using CUID as a reference to compare source and
destination systems. Selecting this option will enable the Import Wizard
to compare identical users/groups/objects that exist in the destination
system (XI 3.1) and the source system (XI R2) based on the CUID. The
option to rename objects if they already exist on the destination system
must also be checked so that Import Wizard can rename these objects.
Click Next
219

6. In the "Incremental Import" page, we selected all the options for the
following reasons:
Overwrite Object Contents: If you are already working with objects
(except for universe, universe connections, and groups) such as users,
Desktop Intelligence reports, Web Intelligence reports, and Crystal
reports, on the Destination XI3.1 system, and if you select this option,
the Import Wizard will overwrite objects that match with the objects in
the XI R2 system. This option is not recommended if users are using
the XI 3.1 system and are working on the objects.
220
Overwrite Universe Contents - Similar to Overwrite Object

Contents.
Overwrite Connections Contents Similar to Overwrite Object

Contents.

Overwrite Group and user membership If the Import Wizard

detects groups on the destination system that matches with groups in
the source system, then it replaces the group membership information
in the destination with the group membership information in the source
system.
If you do not select this option, then the Import Wizard adds new
members. It does not modify the existing members.
Overwrite Object Rights - If the Import Wizard detects an object

(object refers to folders and reports) in the destination environment
that matches with an object in the source system, and if the users or
groups that the object's rights pertain to are either on the destination
or are being imported, then the Import Wizard overwrites any existing
rights on the object for those users or groups.
If you do not select this option, the Import Wizard adds any new rights
to the object that aren't already specified on it. It does not add or modify
any existing rights on the object.
Import Wizard starts retrieving the users and groups, and the "Users and
groups" page displays the list of users and groups to be migrated.
221

7. Select all the users and groups by clicking Select All and click Next.
222

8. In the "Categories" page of the Import Wizard, select the "Select All"
option. In this phase, we are importing the rest of the folders and
documents that are mapped to these categories. Hence, we must import
these categories as well so that the documents are mapped to these
categories. If not, then the relation between the documents and the
categories break and we will have to map them manually in the destination
system. We will not select the "Import all the objects that belong to the
selected category" option. This is because, if we select this option, then
it will result in the migration of the documents that were imported in the
first phase.
223

9. In the "Folders and Objects" page, we will select the all the folders except
Folder_1, which was migrated in the first phase. The sample
folders/documents that are created with the installation of XIR2 are also
not selected. However, we will select the "Import all instances of each
selected object" option, which will result in the migration of the scheduled
instances of the reports under the folder. Click Next.
224

10. Do not modify any of the fields, because we are not exporting the
applications.
11. In the "Import options for universes and connections" page, we will select
the first option to migrate all the universes and connections in the
repository. In the first phase, we did not migrate any of the universes.
Hence, we will migrate all universes now.
225

12. In the "Import repository objects" options, select the first option to migrate
all the repository objects. Click Next.
226

13. In the "Import Options for publications" page, we will select the Do not
import recipients option because there are no publications in our setup.
227

The"Ready to Import" page displays the summary of the selections.

14. To modify the selections, click Back. To proceed with the import process,
click Finish.
The Import Progress page displays the list of objects and users that are
being migrated and the overall status of the migration process. When the
import process is complete, the View Detail Log button is automatically
enabled.
15. Click View Detail Log to view the details of the import process, such as
errors and success.
Observations on the import process

In this phase, we found that the following were migrated properly:
228

Users
Groups
Folders
Categories
Documents
Connections
Events
Repository objects
Universes
We also observed the following:

The BusinessObjects NT user group failed to migrate. This is because
the NT Authentication option was not configured in the XI R2 system.
Objects belonging to EPM/PMC failed to migrate. This is because
Performance Management applications were not installed in the
destination system.
After reviewing the logs, click Done. An Import Wizard rights verification tool
is launched. If you are importing objects from any source environment other
than BusinessObjects Enterprise XI 3.x or an XI 3.x BIAR file, the Import
Wizard displays a dialog box, informing you that it will run a rights verification
tool. This tool searches for child objects on the destination system with rights
that have not been granted to their parent objects. If the tool finds any such
objects, the Import Wizard removes the rights from the child objects.
Note:
After the migration was completed, we tested the imported reports and LDAP
user/Enterprise logins for the following functions: viewing, refreshing,
modifying, and scheduling. All operations were completed successfully.
This completes the migration of contents from XI R2 to XI 3.1 in two phases.
229

230
Issue faced while importing users

In the first phase, we imported all the users and the groups by manually
selecting all the groups. We also chose the Select Groups option to include
all the groups, so that when a user is selected, the group the user belongs
to is also selected automatically.
The "Import Wizard Ready to Import" page displays the summary of the
contents that will be exported to the BIAR file. If required, we can click Back
and then make the necessary changes to the settings we have specified.
After reviewing the settings, click Finish.
232
The "Import Progress" page displays the progress of the migration.
233
After the import process is complete, we can click the View Detail Log button
to view the details of the import process, such as failure and success.
Summary
Total Users in the
9209
Repository
(Enterprise +
LDAP)
4210 + 4999
Users Imported
234
Number of Users
4100
Missing
PMUser
Super
Administrator
Supervisor
Auth_User1
M*
800
D*
51
U1*
400
SD*
51
U2*
600
TestUser*
U4*
1000
U3*
4999
U0*
46
Guest
S*
51
Total number of
Users imported
5109
U5*
1200
Total number of
Users missing
4100
Note:
For example, S* refers to all user names that start with S. However. this does
not include user names that start with SD.
Conclusion: The import failed for 4100 users.
Investigation
We chose to run Import Wizard without the LDAP authentication.
We noticed that only about 5109 users and 59 groups were imported, though
the total number of users is 9209. When we checked the log file, we found
that 4100 users were not exported. Moreover, no information was available
on why these users were not exported to the BIAR file. To troubleshoot this
issue, we cleared the "LDAP Authentication is enabled" check box and
updated the setting by clicking Update.
235
Issue faced while mapping FRS for the clusters
We ran the Import Wizard again. This time, the summary page displayed the
number of users selected, which was 9209.
We suspected that this issue was caused by an error that occurred while
selecting the LDAP groups manually. To verify this, we enabled LDAP
authentication again and then ran the Import Wizard by selecting the Select
All option.
All users and groups were imported properly.
Issue faced while mapping FRS for the

clusters
We logged into the Cluster1 system with user cluster1_user1. When we
attempted to change the OFRS to \\boedb\MIRA FRS\Input and
\\boedb\MIRA FRS\Input\temp, the following error message was displayed:
236
Issue faced while mapping FRS for the clusters
"This server has configuration error." However, the Input server was able to
map to the shared folder. We initially attributed this error to the UNC mapping
of the folder, though we had given all the rights on the root folder (MIRA
FRS) for the users.
Next, we tried mapping the network drives to the MIRA Temp folder. However,
we encountered the same error. Our attempt to resolve this issue by restarting
the Server Intelligence Agent (SIA) also met with the same result. Then, we
mapped the drive by using a different user (administrator). This attempt also
failed to resolve the issue.
We observed that the SIA is running with Local System account and we
wanted to change the account to Local Administrator account. To change
the account, we opened the "Services" page (by selecting Start->Run->
type Services.msc) and stopped the SIA service. Then, we navigated to
the Log On tab, selected "This account", typed the administrator credentials
(Administrator/ediedi), clicked Apply, and started the SIA service.
After the SIA service started, we found there were no errors for all the FRS
servers in the CMC. We also found that the temp folders were updated with
237
LDAP users and groups migration failed
Input.MIRA1 folder under \\boedb\MIRA FRS\Input\temp and Output.MIRA1

folder under \\boedb\MIRA FRS\Output\temp.
Similarly, we changed the login account for other SIAs of Cluster2 and
Cluster3 machines. When we restarted the SIA, we found Input.MIRA2,
Output.MIRA2 and Input.MIRA3, Output.MIRA3 under respective Input and
Output temp folders.
Changing the login account resolved the issue because the user name
(Administrator) and its password (ediedi) is same for both the Windows
systems and this is facilitated by Microsoft Network Sharing.
Later, we used domain accounts to run the SIA service and all the systems
in that domain.

Based on the information we received from the developers, we decided not
to map the LDAP group in the destination system prior to the migration
process, because we were migrating users and groups along with the
folders/objects owned by the LDAP users.
We logged into CMC, navigated to the Authentication tab, opened LDAP,
and deleted the LDAP group CN=BOE Testers,OU=BOBJ
Users,O=BusinessObjects,C=US, and then clicked Update.
LDAP User and Group Migration
After deleting the LDAP group from the XI 3.1 system, we ran the Import
Wizard with the same options, to migrate the LDAP users from the XI R2
system to the XI 3.1 system.
We selected only the LDAP group and its corresponding users, because
only this group failed to migrate in the first attempt. We did not modify the
options we had selected earlier in the Import Wizard.
238
The Summary page displays that one LDAP group and 5004 users are ready
for migration.
239
We found that all LDAP users and groups with their personal folders and
categories were migrated properly.
Observation
Compared to the first attempt, the second was considerably faster. The entire
process did not take more than 90 minutes. This is because we had disabled
logging before starting the migration process. In the first attempt, on the other
hand, we had modified the bo_trace.ini file to log all information. As a result,
a number of logs were generated and the system ran out of space.
Issues faced while mapping LDAP users to Enterprise groups
After migrating the LDAP users, we logged into CMC and found that all the
users were migrated properly. However, these users were not mapped to
the existing Enterprise groups. In our XI R2 setup, the LDAP users belong
to different Enterprise Groups, but in XI 3.1, the LDAP users belong to LDAP
group and Everyone group.
In our previous attempt at migration, we had not selected the Select Groups
option. We did not select this option because the Enterprise groups were
already in the XI 3.1 system. Hence, we assumed that the LDAP users will
240
Issues faced while configuring the AD domain
be mapped automatically while users are migrated. However, we observed

that the LDAP users were not mapped.
Moreover, because we did not select the Select Groups option, the users'
relationship information with these groups was not migrated. Hence, the
relationship between the Enterprise groups and the LDAP users was broken
and the LDAP users were not mapped to the Enterprise groups.
For these reasons, we decided to run the Import Wizard again to migrate all
the LDAP users and their group relationship.
Note:
Ensure that you have selected the Select Groups option, which contains the
selected users, and that you have selected the LDAP group so that all the
LDAP users are selected along with the groups they belong to.
We observed that if we select this option after selecting the users and groups,
then the groups are not mapped automatically. The Import Wizard team
informed us that we must select the Select Groups option before selecting
the users and groups. This is by design.
When we selected the LDAP group, other Enterprise groups (such as G0,
G1_1, and so on) to which LDAP users belong were selected automatically.
After the LDAP users were migrated along with the LDAP group, we logged
into the CMC and observed that the LDAP users were mapped to the
Enterprise groups.
Issues faced while configuring the AD

domain
After we added Cluster1, Cluster2, Cluster3, and BOEDB in the AD domain
EDI.COM and restarted the systems, we encountered the following issues:
Note:
Microsoft recommends restarting the system after adding the machines to

the AD domain for the changes to take effect.
We were unable to ping Cluster1, Cluster2, Cluster3, and BOEDB

We were unable to log into InfoView and CMC
The CMS Name Server port was reset to 6400.
The CMS Request ports for Cluster1, Cluster2, and Cluster3 were reset
to Auto assign.
241
The following sections describe these issues and the methods we used to
resolve them:
Unable to ping Cluster1, Cluster2, Cluster3 and BOEDB
After we added Cluster1, Cluster2, Cluster3, and BOEDB in AD domain

EDI.COM and restarted the system, Cluster1 failed to ping Cluster2. We also
faced similar issues with Cluster2, Cluster3 and BOEDB.
Our attempts to ping these systems from Firewall3 failed. However, we
succeeded in pinging AUTHENTIC from Firewall3. This was unexpected
because the IP addresses were still the same.
Initially, we thought that this issue was related to the configuration of Firewall3.
Accordingly, we checked and modified the following in Firewall3:
We checked the iptables configuration, and then stopped the iptables so that
there are no rules.
We checked the : /etc/hosts; /etc/resolv.conf; /etc/host.conf;
/etc/sysconfig/network configuration files, and we added the following
entries to resolv.conf
and host.conf:
[root@firewall3 etc]# cat resolv.conf
#generated by /sbin/dhclient-script
domain edi.com
search edi.com
nameserver 192.168.2.13
[root@firewall3 etc]# cat host.conf
order hosts,bind
multi on
We also checked the IP routing table by using the netstat -r command. We

did not observe any issue in the configuration.
However, we were still unable to ping Cluster1, Cluster2, Cluster3, and
BOEDB from Firewall3. We, then, suspected that the issue was because of
the DNS entries in Cluster1, Cluster2, Cluster3, and BOEDB. To remove the
DNS entries, we navigated to Local Area Connection Status. We observed
a lock in the "Activity" area. We realized that the Windows firewall was
enabled. We disabled the firewall and the issue was resolved. This issue
occurred because the Windows firewall was enabled and it blocked the
communication.
242
Unable to log into InfoView and CMC
Our attempts to log into InfoView and CMC from REVPROXY, APPSERV1,
and APPSERV2 failed. The following error messages was displayed:
Communication Error: CLUSTER1:7400 could not be contacted.
We logged into APPSERV1 and succeeded in pinging Cluster1. However,
attempts to ping CLUSTER1.EDI.COM failed. Then, we navigated to
C:\WINDOWS\system32\drivers\etc, opened the host file, and added the
following entries:
192.168.3.11 CLUSTER1.EDI.COM
With these changes in place, we succeeded in pinging CLUSTER1.EDI.COM,

CLUSTER2.EDI.COM ,and CLUSTER3.EDI.COM.
In "APPSERV1", we navigated to C:\Tomcat\Tomcat55\webapps\In
foViewApp\WEB_INF and modified web.xml with the following information:
<context-param>
<param-name>cms.default</param-name>
<param-value>CLUSTER1.edi.com:7400</param-value>
</context-param>
In the location C:\Tomcat\Tomcat55\webapps\PlatformServices\WEBINF, modified web.xml with the following:
<context-param>
<param-name>cms.clusters</param-name>
<param-value>@MIRA1</param-value>
</context-param>
<context-param>
<param-value>CLUSTER1.edi.com:7400, CLUSTER2.edi.com:7400,
CLUSTER3.edi.com:7400</param-value>
</context-param>
We repeated the same steps in "APPSERV2", and restarted both "

APPSERV1" and "APPSERV2". We succeeded in logging into InfoView and
CMC.
The issue was resolved.
243
Appserv2 failed to start and stop properly
The CMS Name Server port was reset to 6400 and CMS Request port was
reset to Auto assign
We logged into CMC, navigated to the "Servers" management area of the

CMC, selected the CMS, and then selected Properties from the "Manage"
menu. We observed the following:
The CMS Name Server port was reset to 6400
The CMS Request port was reset to Auto assign
We reset the values as follows:
Name Server Port was reset to 7400
Request Port was reset to 7413
Disabled Auto assign.
We saved the modifications and restarted the CMS. The issue was resolved.

We observed that Appserv2 failed to start and stop properly. When we
attempted to stop Appserv2 from the services, the following error message
was displayed: "The service could not be stopped properly."
We checked the entries in the server.xml file located at C:\Tomcat\Tom
cat55\conf. We did not observe any issues in this file.
When we attempted to stop Tomcat from the command prompt, the following
error message was displayed:
java.net.ConnectException: Connection refused: connect
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketIm
pl.java:195)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
at java.net.Socket.connect(Socket.java:519)
at java.net.Socket.connect(Socket.java:469)
at java.net.Socket.(Socket.java:366)
at java.net.Socket.(Socket.java:179)
at org.apache.catalina.startup.Catalina.stopServer(Catalina.ja
va:394)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
244
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAc
cessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Delegating
MethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.apache.catalina.startup.Bootstrap.stopServer(Boot
strap.java:343)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.ja
va:434)
We also found that Tomcat failed to start properly. It waited for a long time
at "Initializing Performance Management".
We typed the following commands to check whether the Tomcat server is
accessing ports 8005 and 8009:
netstat -aon|find "8005"
netstat -aon|find "8009"
However, no output was displayed for these commands.

To find out why Tomcat waited for a long time at Initializing Performance
Management, we examined the InitConfig.Properties file located at:
C:\Tomcat\Dashboards and Analytics 12.0.
We observed that the InitConfig.Properties file contained the following
entries for Appserv2:
# Runtime configuration
# Note: When using, " -DAAHOME=<files location>" Should be in
cluded as startup parameter
initialization.CMSName=CLUSTER1.edi.com:7400;CLUS
TER2.edi.com:7400;CLUSTER3.edi.com:7400
initialization.User=Administrator
initialization.Password=
initialization.Authentication=secEnterprise
initialization.CMSClusterName=MIRA1:7400
We compared these entries with the entries in the InitConfig.Properties

file in Appserv1, which is shown below::
# Runtime configuration
# Note: When using, " -DAAHOME=<file's location>" Should be
included as startup parameter
initialization.CMSName=CLUSTER1:7400;CLUSTER2:7400;CLUSTER3:7400
initialization.User=Administrator
initialization.Password=yreq0qr1eqq1q151Gq11iq
245
ClusterName issue faced while configuring the AD domain
initialization.Authentication=secEnterprise
initialization.CMSClusterName=MIRA1:7400
We replaced the entries in Appserv2 with the entries in Appserv1, and

restarted Tomcat. The issue was resolved.
These changes in the InitConfig.Properties file may have happened while
adding the cluster machines to the AD domain.
ClusterName issue faced while

configuring the AD domain
The Cluster3 domain information is missing in SIA
We placed the Cluster1, Cluster2, and Cluster3 machines in the EDI.COM
domain. After we started re-configuring the firewalls, we closed all the ports.
The Cluster3 machine appeared in the domain when we checked the
Computer Name tab in System Properties. However, in SIA, the Cluster3
machine appears without the domain suffix, as shown below:
To fix this issue, we performed the following steps:

1.
2.
3.
4.
5.
6.
7.
246
Log into Cluster3 with an account that has administrative privileges.

Stop SIA.
Place the system in the WORKGROUP domain and restart it.
Place the system back in the EDI.COM domain and restart it.
Stop SIA.
Log into Cluster2 with an account that has administrative privileges.
Stop SIA.
ClusterName issue faced while configuring the AD domain
8. Click SIA Properties.

9. In the "Startup" tab, select Cluster3 under Remote CMS Servers, and
click Properties.
10. In the Hostname field, replace cluster3 with CLUSTER3.edi.com, and
click OK.
11. Click Apply and then OK.
12. Log into Cluster1 with an account that has administrative privileges.
13. Repeat steps 7 to 11.
14. Log into Cluster3 and start SIA.
15. Start SIA in Cluster1 and Cluster2.
The issue is fixed now.
247
Unwanted folder BOEXIR3_1 was created in Cluster2 and Cluster3
Unwanted folder BOEXIR3_1 was created

in Cluster2 and Cluster3
After the cluster systems were installed and configured, we observed that,
apart from the default installation folder C:\BOEXI3_1, a folder called
BOEXIR3_1 was created in C:\ of Cluster2 and Cluster3 systems. This folder
contained data related to search. We deleted the folder. However, it was
created again.
To troubleshoot this issue, we examined CMC > Applications > Content
Search. In the Content Search properties, we observed the following:
We modified the path as follows and then deleted the BOEXIR3_1 folder:
The folder was not created again and the issue was resolved.
248
Sessions page in CMC displays HTTP Status 500
Sessions page in CMC displays HTTP

Status 500
After Tomcat was clustered, the Sessions page in CMC Home displayed:
HTTP Status 500. The following page was displayed when we clicked
Sessions in CMC Home:
In the Tomcat log, we observed the following:

06-11-08 06:41:52:156 - {ERROR} [/CmcApp].[jsp] Thread [TPProcessor8]; Servlet.service() for servlet jsp threw exception
java.lang.IllegalArgumentException: Attribute [sessionsBean]
is not serializable
at org.apache.catalina.cluster.session.DeltaSession.setAt
tribute(DeltaSession.java:1237)
at org.apache.catalina.cluster.session.DeltaSession.setAt
tribute(DeltaSession.java:1215)
at org.apache.catalina.cluster.session.DeltaSessionFacade.se
tAttribute(DeltaSessionFacade.java:130)
at org.apache.jasper.runtime.PageContextImpl.doSetAt
tribute(PageContextImpl.java:329)
at org.apache.jasper.runtime.PageContextImpl.setAttribute(Page
ContextImpl.java:308)
at org.apache.jsp.App.Sessions.sessions_jsp._jspService(ses
sions_jsp.java:113)
249
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.ja
va:97)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at org.apache.jasper.servlet.JspServletWrapper.ser
vice(JspServletWrapper.java:334)
at org.apache.jasper.servlet.JspServlet.serviceJsp
File(JspServlet.java:314)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.ja
va:264)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at org.apache.catalina.core.ApplicationFilterChain.internalD
oFilter(ApplicationFilterChain.java:252)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(Ap
plicationFilterChain.java:173)
at org.apache.catalina.core.ApplicationDispatcher.invoke(Ap
plicationDispatcher.java:672)
at org.apache.catalina.core.ApplicationDispatcher.processRe
quest(ApplicationDispatcher.java:463)
at org.apache.catalina.core.ApplicationDispatcher.doForward(Ap
at org.apache.catalina.core.ApplicationDispatcher.forward(Ap
at com.sun.faces.context.ExternalContextImpl.dispatch(Exter
nalContextImpl.java:346)
at com.sun.faces.application.ViewHandlerImpl.renderView(ViewHan
dlerImpl.java:152)
at com.sun.faces.lifecycle.RenderResponsePhase.execute(Render
ResponsePhase.java:107)
at com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleIm
pl.java:245)
at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleIm
pl.java:137)
at javax.faces.webapp.FacesServlet.service(FacesServlet.ja
va:214)
at com.businessobjects.webutil.boetrustguard.BOETruste
dRequestCreator.doFilter(BOETrustedRequestCreator.java:97)
at com.businessobjects.webutil.boetrustguard.BOETrustFil
ter.doFilter(BOETrustFilter.java:83)
at com.businessobjects.webutil.TimeoutCheckerFilter.doFil
250
ter(TimeoutCheckerFilter.java:99)
at org.apache.catalina.core.StandardWrapperValve.invoke(Stan
dardWrapperValve.java:213)
at org.apache.catalina.core.StandardContextValve.invoke(Stan
dardContextValve.java:178)
at org.apache.catalina.core.StandardHostValve.invoke(Standard
HostValve.java:126)
at org.apache.catalina.cluster.tcp.ReplicationValve.in
voke(ReplicationValve.java:346)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorRe
portValve.java:105)
at org.apache.catalina.core.StandardEngineValve.invoke(Stan
dardEngineValve.java:107)
at org.apache.catalina.connector.CoyoteAdapter.service(Coy
oteAdapter.java:148)
at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHan
dler.java:199)
at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.ja
va:282)
at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.ja
va:767)
at org.apache.jk.common.ChannelSocket.processConnection(Chan
nelSocket.java:697)
at org.apache.jk.common.ChannelSocket$SocketConnec
tion.runIt(ChannelSocket.java:889)
at org.apache.tomcat.util.threads.ThreadPool$Control
Runnable.run(ThreadPool.java:684)
at java.lang.Thread.run(Thread.java:595)
We set up a similar environment on the local VMWARES to reproduce this

issue.
System Name
What is Installed?
BNG-VM2-VRAJU
BusinessObjects Enterprise with Tomcat1
BNG-VM3-VRAJU
Apache HTTP and Tomcat2
In this environment, Tomcat1 and Tomcat2 are clustered and bridged with
HTTP.
The issue was reproduced. When we removed the <distributable/> tag from
web.xml of CmcApp under D:\Business
251
Objects\Tomcat55\webapps\CmcApp\WEB-INF\web.xml, we observed that
the issue did not occur.

For session replication to occur in a cluster, all attributes stored in the session
object must be serializable.
The program manager has confirmed that this is a design limitation.
Note:
Program Manager's statement: We do support Tomcat clustering, but not

session replication. We also support application server clustering for load
balancing. However, we do not support session replication of application
servers. Only InfoView supports session replication. However, this does not
extend to components that integrate with the InfoView, such as Web
Intelligence, XCelsius and so on.
252
BusinessObjects client
Operating system
Windows XP Professional SP2 with mandatory updates
CPU
1 CPU
Memory
1 GB
Software
Internet Explorer 6
SUN JVM 1.5.0.x
Reverse proxy
Machine name
revproxy.product.businessobjects.com
External IP address
10.6.127.59
Internal IP address 192.168.1.1

Operating system Windows Server 2003 SP2 Standard Edition with mandatory
updates
CPU
1 CPU, 1 core, 2 threads
Memory
1 GB
Disk space
Software
Apache 2.2.x
HTTP server 1
254
Machine name
http1
IP address
192.168.1.11
Operating system
Windows Server 2003 SP2 Standard Edition with critical

updates
CPU
Memory
2 GB
Disk space
Software
Apache HTTP Server 2.0.49
HTTP server 2
Machine name
http2
IP address
192.168.1.12
Operating system Windows Server 2003 SP2 Standard Edition with critical
updates
CPU
Memory
2 GB
Disk space
Software
Apache HTTP Server 2.0.49
Authentication server
Machine name
authentic.edi.com
IP address
192.168.2.13
Operating system Windows 2003 Server Enterprise Edition with mandatory

security updates
CPU
255
Memory
2 GB
Disk space
Software
Application server 1
Machine name
appserv1
IP address
192.168.2.11
updates
CPU
Memory
2 GB
Disk space
Software
Tomcat 5.0.27
Application server 2
Machine name
appserv2
IP address
192.168.2.12
updates
CPU
256
Memory
2 GB
Disk space
Software
Tomcat 5.0.27
BusinessObjects Enterprise cluster server 1

Machine name
cluster1.edi.com
IP address
192.168.3.11
Operating system
Windows Server 2003 Enterprise Edition with critical updates
CPU
Memory
2 GB
Disk space
Software

Oracle .NET 10.2 client

Machine name
cluster2.edi.com
IP address
192.168.3.12
Operating system
CPU
257
Memory
2 GB
Disk space
Software


Machine name
cluster3.edi.com
IP address
192.168.3.13
Operating system
CPU
Memory
2 GB
Disk space
Software

BusinessObjects Enterprise database server and FRS share

Machine name
boedb.edi.com
IP address
192.168.3.14
updates
CPU
258
Memory
2 GB
Disk space
Software
Oracle 9.2
Corporate database server

Machine name
corpdata
IP address
192.168.4.2
updates
CPU
Memory
2 GB
Disk space
Software
Oracle 9.2
Firewall 1
Machine name
firewall1
IP address 1
192.168.1.254
IP address 2
192.168.2.1
Operating system
Linux Redhat Enterprise 5.0
259
CPU
Memory
1 GB
Disk space
Firewall 2
Machine name
firewall2
IP address 1
192.168.2.254
IP address 2
192.168.3.1
Operating system
CPU
Memory
1 GB
Disk space
Firewall 3
Machine name
firewall3
IP address 1
192.168.3.254
IP address 2
192.168.4.1
Operating system
CPU
Memory
1 GB
Disk space
260
List of machines and access

information
10
10
A KVM Avocent is installed on each of the machines used in our setup to

provide access to the remote console. The device is connected to the
keyboard, mouse, screen connectors and does not interfere with network
operations.
List of Machines
Purpose
Name
Cisco
CSS
11501
ccss01
Load Balancer
262
IP Eth0
IP Eth1
10.6.124.1 192.168.1.13
Local AdAdditional User

min User
Name/PassName/Password
word
ad
min/bobobo
Administra
tor/ediedi
revproxy_us
er1/vanpass
word
Media Disconnected
Administra
tor/ediedi
HTTP1_Us
er1/vanpass
word
Media Disconnected
Administra
tor/ediedi
HTTP2_Us
er1/vanpass
word
Reverse
Proxy
REVPROXY 10.6.127.59 192.168.1.1
HTTP
Server
HTTP1
192.168.1.11
HTTP
Server
HTTP2
192.168.1.12
Firewall
FIRE
WALL1
192.168.1.254 192.168.2.1 root/ediedi
qaunix/qaunixe
di
Firewall
FIRE
WALL2
192.168.2.254 192.168.3.1 root/ediedi
qaunix/qaunixe
di
Firewall
FIRE
WALL3
192.168.3.254 192.168.4.1 root/ediedi
qaunix/qaunixe
di
Authenti169.254.154.228
AUTHEN
Administra
cation
192.168.2.13 Disabled this
TIC
tor/ediedi
Server
media later
Auth_User1/vanpassword cluster_user/vanpassword
ApplicaMedia Distion serv- APPSERV1 192.168.2.11

connected
er
Administra
tor/ediedi
APPSERV1_Us
er1/vanpass
word
ApplicaMedia Distion serv- APPSERV2 192.168.2.12

connected
er
Administra
tor/ediedi
APPSERV1_Us
er1/vanpass
word
BOE
Database
BOEDB
and I/O
FRS
Media Disconnected
Administra
tor/ediedi
BOE_User1/van
password
CorpoCORPDA
Media Disrate Data
192.168.4.2
TA
connected
Server
Administra
tor/ediedi
Corpdata_Us
er1/vanpass
word
BOE
Cluster
Server
CLUS
TER1
192.168.3.11
Media Disconnected
Administra
tor/ediedi
Cluster1_Us
er1/vanpass
word
BOE
Cluster
Server
CLUS
TER2
192.168.3.12
Media Disconnected
Administra
tor/ediedi
Cluster2_Us
er1/vanpass
word
192.168.3.14
263
10
10
BOE
Cluster
Server
CLUS
TER3
192.168.3.13
Media Disconnected
Administra
tor/ediedi
Cluster3_Us
er1/vanpass
word
List of Gateways
264
Machine IP
Address
Machine
Name
Gateway IP Ad- Gateway

dress
Name
10.6.127.59
"Automatically
REVPROXYobtained from
public
DNS server"
n/a
n/a
192.168.1.1
REVPROXY192.168.1.254
private
Firewall1eth0
n/a
192.168.1.11
HTTP1
no gateway
n/a
192.168.1.12
HTTP2
no gateway
n/a
192.168.1.254
Firewall1eth0
192.168.1.1
REVPROXYn/a
private
192.168.2.1
Firewall1eth1
192.168.2.254
Firewall2eth0
192.168.2.11
APPSERV1 no gateway
n/a
192.168.2.12
APPSERV2 no gateway
n/a
192.168.2.13
AUTHEN
TIC
192.168.2.254
Firewall2eth0
n/a
192.168.2.254
Firewall2eth0
192.168.2.1
Firewall1eth1
n/a
192.168.3.1
Firewall2eth1
192.168.3.254
Firewall3eth0
n/a
Routing Information
n/a
Machine IP
Address
Machine
Name
Gateway IP Ad- Gateway

dress
Name
Routing Information
192.168.3.14
BOEDB
no gateway
n/a
192.168.3.11
CLUSTER1 no gateway
n/a
192.168.3.12
CLUSTER2 no gateway
n/a
192.168.3.13
CLUSTER3 no gateway
n/a
192.168.3.254
Firewall3eth0
192.168.3.1
Firewall2eth1
n/a
192.168.4.1
Firewall3eth1
no gateway
n/a
n/a
192.168.4.2
CORPDA
TA
192.168.4.1
Firewall3eth1
n/a
List of Databases
DB
System
VerName
sion
Service
Name
AdministraPort
tor User
NumName/Passber
word
Additional
User
Purpose
Name/Password
BOEDB
Oracle
10g
BOE11
R2
1521
For XIR2
sys/vanpass testware/test
CMS Reposiword
ware
tory
BOEDB
Oracle
10g
BOE11
R2
1521
test
For XIR2
sys/vanpass
ware_epm/test EPM Reposiword
ware_epm
tory
BOEDB
Oracle
10g
BOE11
R2
1521
For XI 3.1
sys/vanpass
xir3_1/xir3_1 CMS Reposiword
tory
265
10
10
DB
System
VerName
sion
Service
Name
AdministraPort
tor User
NumName/Passber
word
Additional
User
Purpose
Name/Password
BOEDB
Oracle
10g
BOE11
R2
1521
For XI 3.1
sys/vanpass
xri3_1_epm/xri3_1_epm EPM Reposiword
tory
BOEDB
Oracle
10g
BOE11
R2
1521
xir3_1_au
sys/vanpass
For XI 3.1 Audit/xir3_1_au
word
dit Repository
dit
Oracle CORP
9i R2 DATA
Corporate data used by

sys/vanpass
universe con1521
TPCR/TPCR
word
nections and
other connections
CORP
DATA
List of LDAP Users

System
Name
Authentication Type
AUTHEN
LDAP/ADAM
TIC
Administrator User
Name/Password
Normal User
Name/Password
Auth_User1/vanpassword TestUser1/vanpassword
TestUser2/vanpassword
AUTHEN
LDAP/ADAM
TIC
266
n/a
PASS is the password

for other LDAP users
listed in ADAM
Note:
Password expires every one month for all users.
267
10
10
268
Acceptance testing
11
11
Acceptance testing
Acceptance testing workflow

Test cases
Result
Installation
Installing with EPM
Passed
Starting/stopping all the servers by using CCM
Passed
Logging into/logging out of InfoView (Java)
Passed
Logging into/logging out of CMC (Java)
Passed
Logging into/logging out of EPM Portal
Passed
Test cases
Result Comments
Designer
Create a universe
Passed Universe Orders were created.
Export the universe to

repository
Passed
Test cases
Result
Create a Desktop Intelligence document
Universe Orders were exported to the CMS

repository successfully.
Comments
A Desktop Intelligence document with
prompt was created.
Export a document to the

A Desktop Intelligence document with
repository, with or without Passed prompt was created and exported to the
the category
location, Public Folders > Feature samples.
Save a Desktop Intelligence document as PDF, Passed
xls, htm, and txt
270
Acceptance testing
Test cases
Result
Comments
Check that the following

specific elements of documents are still in place
_FC_FComplex_Medium_1.rep was used
after migration: paginaPassed to test the elements of documents. The
tion, formulas, fonts, laydocument appeared fine.
out, breaks, sections,
colors, filters, drills, tabs,
alerts, and sorts.
Refresh a document containing prompts; test the Passed
Show Values option
Open a document that a
user is not supposed to
have access rights for:
Passed User D0_1 was used.
must be denied with a
clear message
Test drill functionality on
Used a Desktop Intelligence document with
a document that was miPassed a prompt for which the Refresh on open
grated from a previous
option was set.
version
Test cell formats: Number, %, Date, Currency
Passed
_FC_FComplex_Medium_1.rep was used

to test the cell formats.
Import a universe in
Desktop Intelligence
Passed Universe Orders were imported.
Add a new data provider Passed

Add a variable to the
document
Passed A variable for running sum was added.
Import a report from the

repository, and then refresh it
Passed
View/schedule a document
Passed
271
11
11
Acceptance testing
Test cases
Result
Comments
Export to repository and

then open in the InfoView Passed
portal
View a document (with
prompt) in HTML format
Passed
(Draft Mode) in the InfoView portal
View a document with
multiple pages (with
prompt) and navigate
Passed
page by page in the InfoView portal (Pagination
Mode)
View a document (with
prompt) in the InfoView
portal (PDF Mode)
Passed
Refresh a document (with

prompt) in the InfoView Passed
portal
Set the Refresh on open
option (with prompt) and
A Desktop Intelligence document with the
save the document with
Refresh on Open prompt was created and
another name, and then Passed
saved in the Public Folders > Feature
open the saved docusamples.
ment in the InfoView portal
Send a document to Inbox and open the same
in the InfoView portal
Passed
Schedule a document
and open the same in the Passed
InfoView portal
272
Acceptance testing
Test cases
Result Comments
Desktop Intelligence - 3tier mode

Create a document by
launching the Desktop
Intelligence client and
Passed The document was created.
then clicking on the New
document menu from the
InfoView portal
Export to repository from
the Desktop Intelligence
The document was exported and opened in
client (3-tier mode) and Passed
the portal.
open in the InfoView portal
Import a document from
the repository and then Passed The document was refreshed.
refresh the document
Edit the query in the docPassed The document was edited and refreshed.
ument and then refresh it
Modify the document
Passed The document was edited and modified.
Launch Desktop Intelligence 3-tier from the

Start Menu of the Windows System, import a
document from the
repository, and then refresh the document
Passed The document was imported and refreshed.
Test cases
Result
Comments
Passed
An Enterprise user (BATUser) with password (BATUser) was created.
Central Management
Console (CMC)
Create a new user
273
11
11
Acceptance testing
Test cases
Result
Log into the CMC with

the newly created user
BATUser
Passed
In continuation with the

previous workflow, log
out of the CMC
Passed
Create a new user group Passed
BATGroup was created
Add a user to a user

group
Passed
BATUser was added to BATGroup
Remove a user from a

user group
Passed
BATUser was removed from BATGroup
Delete a user group
Passed
BATGroup was removed from the repository
Delete a user
Passed
BATUser was removed from the repository
Add a server
Passed
Mira1.BAT Server, which is a Desktop Intelligence Job Server, is added.
Enable/disable a server
Passed
Mira1.BAT Server was enabled/disabled
Start/stop/restart a server Passed
Mira1.BAT Server was used in this workflow
Delete a server
Passed
Stopped the Mira1.BAT Server and then

removed it.
Create a server group
Passed
BAT Server Group was created
Passed
Mira1.BAT Server, Mira1.Adaptive Job

Server, Mira1.Adaptive Processing Server,
and Mira1.Connection Server were added
to Server Group
Add servers to server

groups
274
Comments
Acceptance testing
Test cases
Result
Comments
Remove servers from

server groups
Passed
Mira1.BAT Server, Mira1.Adaptive Job

Server, Mira1.Adaptive Processing Server,
and Mira1.Connection Server Servers
were removed from the Server Group
Delete a server group
Passed
BAT Server Group was deleted
Check the properties of a

Crystal Reports docuPassed
ment.
All Folders --> Folder_1 --> CR_Charting_Benchmark document was used.
Schedule a Crystal Reports document
Passed
All Folders --> Folder_1 --> Folder_1_1 -> Folder_1_1_1 --> CR_CRPE Performance Suite - Crosstab document was
used
View a Crystal Reports

document
Passed
All Folders --> Folder_4 --> Folder_4_1 -> CR_Feature Mixture Benchmark_3754Rows document was used
Refresh a Crystal Reports document
Passed
All Folders --> Folder_4 --> Folder_4_1 -> CR_Feature Mixture Benchmark_3754Rows document was used
View a Desktop Intelligence document
Passed
All Folders --> Document -->_FC_FComplex_Medium_D287 document was used
Schedule a Desktop IntelPassed

ligence document
All Folders --> Document -->_FC_FComplex_Medium_D287 document was used
Create a folder
Passed
Created under All Folders --> BAT Folder
Delete a folder
Passed
BAT Folder was deleted
View a Web Intelligence

Passed
document
All Folders --> Document -->

_CDZ_FComplex_Medium_130 document
was used
Refresh a Web Intelligence document

was used
Passed
275
11
11
Acceptance testing
Test cases
Result
Comments
Schedule a Web Intelligence document
Passed

was used
Test cases
Result
Comments
Log in by using LDAP

authentication
Passed
Successfully logged using U3_1 and

Auth_user1.
Browse categories and

document lists
Passed
InfoView
Add and delete a categoPassed

ry
Change user preferences
Passed
and control
Schedule a Crystal Report
Passed
View a Crystal Report
Passed
CR_Feature Mixture Benchmark_10000Rows was scheduled using

user U3_1.
Change view options to

test Desktop Intelligence Passed
viewer options
Send an object to the inPassed
box
CR_Feature Mixture Benchmark_3754Rows was sent to inbox.
Post a discussion note for

Passed
an object
View history
276
Passed
Acceptance testing
Test cases
Result
Schedule a Desktop IntelPassed

ligence document
Comments
A Desktop Intelligence Report with
Prompt Refresh on Open was scheduled
using user U3_1.
View a Desk Intelligence

Passed
document
Schedule a Web Intelligence document
Passed
_CDZ_FComplex_Medium_D1000 was
scheduled using user U3_1.
View a Web Intelligence

Passed
document
Add a publication to foldPassed
er
My Pub was created.
Schedule a publication
Passed
My Pub was scheduled for U3_1 and the

operation succeeded.
View a publication
Passed
My Pub was viewed.
Use the search function

to search all documents
Passed
by using keyword and title
Create and delete a foldPassed
er
Created and deleted a test folder.
Add a report to a folder
Reports were added to the BAT folder.
Passed
Access report properties Passed

Test the different view
modes for any type of
document:
Passed
View Report - DHTML

Viewer
Passed
CR_Feature Mixture Benchmark_10000Rows was viewed.
View Report - Active X

Viewer
Passed
277
11
11
Acceptance testing
Test cases
Result
View report - Java Viewer Passed
Test cases
Comments
Result Comments
Web Intelligence
Create a new Web IntelliCreated BAT Web Intelligence document
gence document with
Passed based on TPCR, TPCR_1 universes by
multiple data providers
logging in as U3_1 User
Open a Web Intelligence
All Folders --> Document --> _CDZ_FComdocument from a previ- Passed
plex_Medium_200 was opened
ous version
Used a BAT Web Intelligence document
from All Folders --> BAT Folder. While saving the document in the CSV format, we
Save a Web Intelligence
encountered the following error message:
document as PDF, xls,
Maximum binary output size has reached.
Passed
htm, or csv in the InContact Administrator. We resolved this
foView portal
issue by using the Binary Stream Max Size
option in all the Web Intelligence Processing
Servers to increase the value to 200MB from
the default value of 50 MB.
Publish/schedule a WID
Scheduled a BAT Web Intelligence report
Passed
document
from All Folders --> BAT Folder
Delete a Web Intelligence document
Passed
Deleted a BAT Web Intelligence document

from All Folders --> BAT Folder
Try to save an existing

document in a certain
category to check if the
Passed The operation is quite normal.
effect is immediate, requires time, or requires a
restart of the server
278
Acceptance testing
Test cases
Result Comments
Publish/schedule a WID
Passed
document
Test cases
Result
Performance Management Components (PMC)

Log into the InfoView portal with administrator crePassed
dentials
Configure the PMC repository
Passed
Add a calendar
Passed
View the PMC home page
Passed
Log in with PMuser
Passed
Create a set
Pending because the license has expired
Test cases
Result
Comments
Create a metric
Passed
The sum of p_Retail was created.
Create an analytic
Passed
A speedometer and IMT were

created.
Create a metric tree
Passed
View the calendar list
Passed
Metrics
279
11
11
Acceptance testing
Test cases
Results
Comments
Create a goal
Passed
Goal on Sum of P_retail was created.
Save a goal
Passed
Publish the goals
Passed
Create and view dashboard
Passed
Test cases
Result
Comments
Create a strategy
Passed
Strategy EDI was created.
Create a role
Passed
Administrator and analyst

roles were created.
Publish the goals
Passed
Create Predictive Models
Pending because the

license has expired
Create a ControlChart
through SPC
Passed
Select the Metric/Goal

and schedule
Pending because the

license has expired
Create a rule
Passed
Goals
The Parts dashboard was created.
StrategyBuilder
Test cases
Web Intelligence Rich Client-3 tier mode
280
Result
Acceptance testing
Test cases
Result
Create a document by clicking the New document menu in the InPassed

foView portal
Export to repository and open in the InfoView portal
Passed
Open a document from the InfoView portal in Rich Client and refresh
Passed
it
Edit the document query in Rich Client and refresh it
Passed
Modify the document
Passed
Launch Web Intelligence Rich Client in 3-tier mode from Start Menu
of the Windows system, and import a document from the repository Passed
and refresh it
Test cases
Result
Universal Translation Manager

Log into UTM
Passed
Import eFashion from CMS
Passed
Select English as the source language
Passed
Select French as available language
Passed
Set Publish=yes for French
Passed
Put a French string in French - column
Passed
Save
Passed
Test cases
Result
QaaWS
281
11
11
Acceptance testing
Test cases
Result
Create a query with prompt.
Edit a query
Copy a query
Delete a query
Test cases
Re
sult
Comments
Web Intelligence Rich

Client
Set the Web Intelligence
Preferences, "Select a
default creation/editing
Passed
tool" to Desktop, and validate
Create a new Web IntelliThe BAT Web Intelligence Rich Client docuPassed
gence document
ment created by User Administrator
Save the document to My
Passed
Favorites folder
Export the document to
My Favorites folder
Passed
Open the document that

was created in the previous workflow and view it Passed
in the InfoView portal
(HTML format)
282
Acceptance testing
Test cases
Re
sult
Comments
Refresh the document
Passed
A BAT Web Intelligence Rich Client Report

was refreshed
283
11
11
Acceptance testing
284
Get More Help
Get More Help
Online documentation library
Business Objects offers a full documentation set covering all products and
their deployment. The online documentation library has the most up-to-date
version of the Business Objects product documentation. You can browse
the library contents, do full-text searches, read guides on line, and download
PDF versions. The library is updated regularly with new content as it becomes
available.
To access the online documentation library, visit http://help.sap.com/ and
click Business Objects at the top of the page.
Additional developer resources
https://boc.sdn.sap.com/developer/library/
Online customer support
The Business Objects Customer Support web site contains information about
Customer Support programs and services. It also has links to a wide range
of technical information including knowledgebase articles, downloads, and
support forums.
http://www.businessobjects.com/support/
Looking for the best deployment solution for your company?
Business Objects consultants can accompany you from the initial analysis
stage to the delivery of your deployment project. Expertise is available in
relational and multidimensional databases, in connectivities, database design
tools, customized embedding technology, and more.
For more information, contact your local sales office, or contact us at:
http://www.businessobjects.com/services/consulting/
Looking for training options?
From traditional classroom learning to targeted e-learning seminars, we can

offer a training package to suit your learning needs and preferred learning
style. Find more information on the Business Objects Education web site:
http://www.businessobjects.com/services/training
286
Get More Help
Send us your feedback
Do you have a suggestion on how we can improve our documentation? Is

there something you particularly like or have found useful? Drop us a line,
and we will do our best to ensure that your suggestion is included in the next
release of our documentation:
documentation@businessobjects.com
Note:
If your issue concerns a Business Objects product and not the documentation,
please contact our Customer Support experts. For information about
Customer Support visit: http://www.businessobjects.com/support/.
Business Objects product information
For information about the full range of Business Objects products, visit:
http://www.businessobjects.com.
287
Get More Help
288

Xi31 Bip Pattern Win en

Diunggah oleh

Informasi Dokumen

Judul Asli

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

Xi31 Bip Pattern Win en

Diunggah oleh

Hak Cipta:

Format Tersedia

BusinessObjects Enterprise XI 3.

BusinessObjects Enterprise XI 3.0

2009 SAP BusinessObjects. All rights reserved. SAP BusinessObjects owns

About this book............................................................................................8

Windows pattern overview.........................................................................12

Uninstalling XI R2 from the cluster machines............................................22

Deploying the Windows pattern

BusinessObjects Enterprise XI 3.1 Pattern Book for Windows

BusinessObjects Enterprise XI 3.1 Pattern Book for Windows

Installing and deploying Performance Management components 131

Microsoft clustering for FRS failover

Microsoft clustering for FRS failover........................................................148

BusinessObjects Enterprise XI 3.1 Pattern Book for Windows

Updating the Filestore directory for Input and Output FRS................196

Deployment and migration planning

Issue faced while importing users...........................................................232

List of machines and access information

Acceptance testing workflow...................................................................270

Get More Help

BusinessObjects Enterprise XI 3.1 Pattern Book for Windows

About this book

BusinessObjects Enterprise XI 3.1 Pattern Book for Windows

BusinessObjects Enterprise XI 3.1 Pattern Book for Windows

BusinessObjects Enterprise XI 3.1 Pattern Book for Windows

In the context of Business Objects products, a pattern refers to the system

The use of a particular vendor's products in the Windows pattern

Windows pattern overview

BusinessObjects Enterprise XI 3.1 Pattern Book for Windows

A typical BusinessObjects Enterprise deployment comprises the following

BusinessObjects Enterprise XI 3.1 Pattern Book for Windows

The external layer comprises a BusinessObjects client, a reverse proxy

The BusinessObjects Enterprise layer includes a three-server cluster that

BusinessObjects Enterprise XI 3.1 Pattern Book for Windows

Windows pattern security

Central Management Server

BusinessObjects Enterprise XI 3.1 Pattern Book for Windows

Each security plug-in acts as an authentication provider, which verifies user

User authentication and authorization

BusinessObjects Enterprise supports the following authentication methods:

In BusinessObjects Enterprise, authorization is managed through a system

BusinessObjects Enterprise XI 3.1 Pattern Book for Windows

Reverse proxy server

BusinessObjects server communication and firewalls

BusinessObjects Enterprise XI 3.1 Pattern Book for Windows

The default behavior of BusinessObjects Enterprise is to dynamically assign

In a BusinessObjects Enterprise environment, the CMS and the remaining

Windows pattern firewall implementation

BusinessObjects Enterprise XI 3.1 Pattern Book for Windows

Additional security measures

BusinessObjects Enterprise XI 3.1 Pattern Book for Windows

BusinessObjects Enterprise XI 3.1 Pattern Book for Windows

Uninstalling XI R2 from the cluster

BusinessObjects Enterprise XI 3.1 Pattern Book for Windows

In Registry Editor, navigate to My Computer ->

BusinessObjects Enterprise XI 3.1 Pattern Book for Windows

BusinessObjects Enterprise XI 3.1 Pattern Book for Windows

Deploying the Windows

Deploying the Windows pattern

In a typical BusinessObjects Enterprise installation, you provide connectivity

In a real-time deployment, database administrators provide access to an

BusinessObjects Enterprise XI 3.1 Pattern Book for Windows

Deploying the Windows pattern

BusinessObjects Enterprise server cluster setup