Professional Documents
Culture Documents
1
Pattern Book for Windows
Copyright
Contents
Chapter 1
Preface
Introduction to patterns
11
Decommissioning XI R2
21
25
Overview....................................................................................................26
Configuring firewalls..................................................................................28
Resetting the firewall to all ports closed ..............................................29
Configuring Firewall1............................................................................30
Configuring Firewall2............................................................................34
Contents
Configuring Firewall3............................................................................46
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
Chapter 6
147
Contents
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
System specifications
253
Chapter 10
261
Chapter 11
Acceptance testing
269
285
Preface
Preface
About this book
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
Introduction to patterns
Introduction to patterns
Windows pattern overview
12
Introduction to patterns
Windows pattern overview
13
Introduction to patterns
Windows pattern overview
External 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
14
Introduction to patterns
Windows pattern security
Data layer
The data layer includes the Oracle database server that hosts the corporate
database.
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
Introduction to patterns
Windows pattern security
16
Introduction to patterns
Windows pattern security
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.
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.
17
Introduction to patterns
Windows pattern security
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
Introduction to patterns
Redundancy
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
Introduction to patterns
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
Decommissioning XI R2
Decommissioning XI R2
Uninstalling XI R2 from the cluster machines
22
Decommissioning XI R2
Uninstalling XI R2 from the cluster machines
23
Decommissioning XI R2
Uninstalling XI R2 from the cluster machines
24
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 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
26
27
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
Configuring firewalls
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 Firewall2
Configuring Firewall3
Configuring iptables
Configuring the database server to static port 1521
Registering fixed port numbers for BusinessObjects servers
28
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
29
-A FORWARD -j REJECT
COMMIT
firewall_mod
References:
BusinessObjects product guides.
Linux iptables
Linux questions
Kbase.redhat
Configuring Firewall1
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
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
--dport 1024:65535 -j ACCEPT
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
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
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
Configuring Firewall2
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.
Requirements for communication
34
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 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
1024-65535*
35
Computer Browser
Protocol
Ports
138
137
139
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
Application Protocol
36
Protocol
Ports
138
139
LDAP Server
TCP
389
LDAP Server
UDP
389
SMB
TCP
445
Application Protocol
Protocol
Ports
RPC
TCP
135
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
Application Protocol
Protocol
Ports
DNS
UDP
53
DNS
TCP
53
File Replication
Protocol
Ports
RPC
TCP
135
37
Application Protocol
Protocol
Ports
random port number between 1024 - 65535*
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
Application Protocol
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
Application Protocol
Protocol
Ports
138
137
139
SMB
TCP
445
RPC
TCP
Protocol
Ports
RPC
TCP
135
138
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
Application Protocol
Protocol
Ports
138
137
139
SMB
445
TCP
40
Application Protocol
Protocol
Ports
LDAP
TCP
20000
Application Protocol
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
Application Protocol
Protocol
Ports
Cluster Services
UDP
3343
RPC
TCP
135
Cluster Administrator
UDP
137
41
42
#LOGGING
-A CDR2 -m limit --limit 60/sec -j LOG --log-level 1
--log-prefix '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 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 CDR2 -m state --state RELATED,ESTABLISHED -m limit --limit
60/sec -j LOG --log-level 1 --log-prefix
'CDR3_RELATED_ESTABLISHED:'
-A CDR2 -m state --state RELATED,ESTABLISHED -j ACCEPT
#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
-A CDR2 -p tcp -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
#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
44
Routing table:
[root@firewall2 ~]route -n
Kernel IP 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:
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
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:
Microsoft support
ch routing
routing-tables
Configuring Firewall3
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.
Requirements for communication
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
:PREROUTING ACCEPT [0:0]
:POSTROUTING ACCEPT [0:0]
:OUTPUT ACCEPT [0:0]
-A POSTROUTING -o eth0
-A POSTROUTING -o eth1
COMMIT
*filter
:INPUT DROP [0:0]
:FORWARD DROP [0:0]
:OUTPUT ACCEPT [0:0]
#Alias CDR3 chain for INPUT & FORWARD
:CDR3 - [0:0]
-A INPUT -j CDR3
-A FORWARD -j CDR3
#Allow in local loop 127.0.0.1
-A CDR3 -p ALL -i lo -j ACCEPT
#LOGGING
-A CDR3 -m limit --limit 60/sec -j LOG --log-level 1
--log-prefix 'CDR3_INPUT_FORWARD:'
-A OUTPUT -m limit --limit 60/sec -j LOG --log-level 1
--log-prefix 'CDR3_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
47
Routing table:
[root@firewall3 ~]route -n
Kernel IP 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
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
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:
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
50
ED_ESTABLISHED:'
-A CDR2 -m state --state RELATED,ESTABLISHED -j ACCEPT
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
firewall_new
10. Save the new rule set to the current instance of iptables by typing the
following command:
[root@firewall2 ~]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
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
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:
(Oracle_Port_configuration3.JPG)
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:
(Oracle_Port_configuration5.JPG)
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
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
54
create session
create table
create procedure
55
4.
5.
6.
7.
56
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.
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.
58
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
60
61
62
63
3. Click Yes.
Note:
64
During the uninstallation process, some files, such as the registry files,
are not deleted from the system. These files must be removed manually.
65
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
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.
67
68
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
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.
The "Net Service Name Configuration Done" page appears, indicating
that the Naming Methods Configuration is completed.
The "Net Service Name Configuration Done" page appears, indicating
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.
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
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.
74
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.
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
81
82
6. Click Add.
7. Click Next. For the LDAP Server type, select Microsoft Active Directory
Application Server from the drop-down list.
83
11. Select Basic (no SSO) from the authentication drop-down list.
We selected Basic because we did not use single sign-on authentication.
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.
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
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
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
88
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.
91
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
92
3. Click Modify.
The "Select Features" page appears.
4. In the "Select Features" page, selectServer Components -> Central
Management Server.
93
94
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
96
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
97
98
99
100
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
102
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.
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.
104
Machine Name
User Name
Password
Appserv1
appserv1_user1
vanpassword
Appserv2
appserv2_user1
vanpassword
105
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
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
109
After you have installed the WCA on both the application server machines,
you must enable the AJP 1.3 Connector in Tomcat.
110
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.
Quick start
Running the session replication in your Tomcat 5.5 container involves the
following tasks:
111
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.
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">
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>
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-name>cms.clusters.MIRA1</param-name>
<param-value>CLUSTER1:7400, CLUSTER2:7400, CLUS
TER3:7400</param-value>
</context-param>
114
115
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.
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.
The installation begins.
9. Click Finish to complete the installation.
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.
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
119
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.
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:
121
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>.
/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
ProxyPassReverseCookiePath
/CmcAppActions /CmcAppActions
ProxyPass
/AnalyticalReporting
http://192.168.1.13/AnalyticalReporting
ProxyPassReverse
/AnalyticalReporting
http://192.168.1.13/AnalyticalReporting
ProxyPassReverseCookiePath
/AnalyticalReporting /Analytical
122
Reporting
ProxyPass
/CrystalReports
http://192.168.1.13/CrystalReports
ProxyPassReverse
/CrystalReports
http://192.168.1.13/CrystalReports
ProxyPassReverseCookiePath
/CrystalReports /CrystalReports
ProxyPass
/VoyagerClient
http://192.168.1.13/VoyagerClient
ProxyPassReverse
/VoyagerClient
http://192.168.1.13/VoyagerClient
ProxyPassReverseCookiePath
/VoyagerClient /VoyagerClient
ProxyPass
/InfoViewApp
http://192.168.1.13/InfoViewApp
ProxyPassReverse
/InfoViewApp
http://192.168.1.13/InfoViewApp
ProxyPassReverseCookiePath
/InfoViewApp /InfoViewApp
ProxyPass
/InfoViewAppActions
http://192.168.1.13/InfoViewAppActions
ProxyPassReverse
/InfoViewAppActions
http://192.168.1.13/InfoViewAppActions
ProxyPassReverseCookiePath
/InfoViewAppActions /InfoViewAp
pActions
ProxyPass
/OpenDocument
http://192.168.1.13/OpenDocument
ProxyPassReverse
/OpenDocument
http://192.168.1.13/OpenDocument
ProxyPassReverseCookiePath
/OpenDocument /OpenDocument
ProxyPass
/PerformanceManagement
http://192.168.1.13/PerformanceManagement
ProxyPassReverse
/PerformanceManagement
http://192.168.1.13/PerformanceManagement
ProxyPassReverseCookiePath
/PerformanceManagement /Perfor
manceManagement
ProxyPass
/dswsbobje
http://192.168.1.13/dswsbobje
ProxyPassReverse
/dswsbobje
http://192.168.1.13/dswsbobje
ProxyPassReverseCookiePath
/dswsbobje /dswsbobje
ProxyPass
/PMC_Help
http://192.168.1.13/PMC_Help
ProxyPassReverse
/PMC_Help
123
http://192.168.1.13/PMC_Help
ProxyPassReverseCookiePath
/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
http://192.168.1.13/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
http://192.168.1.13/InfoViewApp
References:
Proxy
ProxyPass
ProxyPassReverse
ProxyPassReverseCookiePath
124
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
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:
2. When prompted, enter the administrative user name and password for
the CSS machine.
125
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
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
Note:
126
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
127
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.
128
!*************************** 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#
129
130
Overview
This chapter describes how to install and deploy Performance Management
components. Installing and deploying Performance Management components
involves the following tasks:
References:
Getting Started with Performance Manager
BusinessObjects Performance Manager XI 3.1 Administrator's Guide
BusinessObjects Enterprise XI 3.1 Installation Guide for Windows
132
133
134
135
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
138
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
141
142
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
144
145
146
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:
Checklist
Ensure that the following are in place before you set up Microsoft clustering
for FRS failover:
148
Pre-clustering tasks
Before you configure the Clustering Service software, verify the following:
Microsoft recommends that you configure two networks; one for public
communication and the other for private communication.
Shared disk setup
References:
Microsoft iSCSI Software Target Q and A
Checklist: Installing a Physical Disk resource
Planning Your Server Cluster
149
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.
151
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
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.
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
156
5. In the "Specify Partition Size" window, select the default values and click
Next.
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
159
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.
160
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.
11. Click Finish to complete the installation.
161
Configuring StarWind
To configure StarWind, complete the following steps:
1. Select Start -> All Programs -> Rocket Division Software -> StarWind
-> StarWind.
The "StarWind" window appears.
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.
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.
The installation begins.
10. In the "Completing the StarPort Setup Wizard" window, click Finish to
complete the installation.
167
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
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.
170
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:
We are using the following setup for Quorum and FRS filestore for purposes
of testing:
171
172
5. When prompted, type the system name of the first machine (CLUSTER1),
and click Advanced. The "Advanced Configuration Options" screen
appears.
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.
174
175
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
178
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.
180
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.
182
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.
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.
186
3. In the "Possible Owners" window, ensure that all machines in the cluster
are identified as "Possible Owners", and click Next.
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
3. In the "Possible Owners" window, ensure that all machine in the cluster
are identified as "Possible Owners", and click Next.
4. Create a dependency on the IP address resource, and click Next.
189
190
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
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
195
196
197
198
Overview
The following options are available for migrating contents from XI R2 to XI
3.1:
200
201
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 Universes
203
Note:
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
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.
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.
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.
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
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
228
Users
Groups
Folders
Categories
Documents
Connections
Events
Repository objects
Universes
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
Functional investigation
Functional investigation
Issue faced while importing users
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
Functional investigation
Issue faced while importing users
233
Functional investigation
Issue faced while importing users
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
Functional investigation
Issue faced while importing users
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
Functional investigation
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.
236
Functional investigation
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
Functional investigation
LDAP users and groups migration failed
238
Functional investigation
LDAP users and groups migration failed
The Summary page displays that one LDAP group and 5004 users are ready
for migration.
239
Functional investigation
LDAP users and groups migration failed
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
Functional investigation
Issues faced while configuring the AD domain
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.
241
Functional investigation
Issues faced while configuring the AD domain
The following sections describe these issues and the methods we used to
resolve them:
Unable to ping Cluster1, Cluster2, Cluster3 and BOEDB
242
Functional investigation
Issues faced while configuring the AD domain
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
192.168.3.12 CLUSTER2.EDI.COM
192.168.3.13 CLUSTER3.EDI.COM
243
Functional investigation
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
244
Functional investigation
Appserv2 failed to start and stop properly
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"
245
Functional investigation
ClusterName issue faced while configuring the AD domain
initialization.Authentication=secEnterprise
initialization.CMSClusterName=MIRA1:7400
Functional investigation
ClusterName issue faced while configuring the AD domain
247
Functional investigation
Unwanted folder BOEXIR3_1 was created in Cluster2 and Cluster3
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
Functional investigation
Sessions page in CMC displays HTTP Status 500
249
Functional investigation
Sessions page in CMC displays HTTP Status 500
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
plicationDispatcher.java:398)
at org.apache.catalina.core.ApplicationDispatcher.forward(Ap
plicationDispatcher.java:301)
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 org.apache.catalina.core.ApplicationFilterChain.internalD
oFilter(ApplicationFilterChain.java:252)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(Ap
plicationFilterChain.java:173)
at com.businessobjects.webutil.boetrustguard.BOETruste
dRequestCreator.doFilter(BOETrustedRequestCreator.java:97)
at org.apache.catalina.core.ApplicationFilterChain.internalD
oFilter(ApplicationFilterChain.java:202)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(Ap
plicationFilterChain.java:173)
at com.businessobjects.webutil.boetrustguard.BOETrustFil
ter.doFilter(BOETrustFilter.java:83)
at org.apache.catalina.core.ApplicationFilterChain.internalD
oFilter(ApplicationFilterChain.java:202)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(Ap
plicationFilterChain.java:173)
at com.businessobjects.webutil.TimeoutCheckerFilter.doFil
250
Functional investigation
Sessions page in CMC displays HTTP Status 500
ter(TimeoutCheckerFilter.java:99)
at org.apache.catalina.core.ApplicationFilterChain.internalD
oFilter(ApplicationFilterChain.java:202)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(Ap
plicationFilterChain.java:173)
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)
What is Installed?
BNG-VM2-VRAJU
BNG-VM3-VRAJU
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
Functional investigation
Sessions page in CMC displays HTTP Status 500
252
System specifications
System specifications
BusinessObjects client
Operating system
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
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
CPU
System specifications
Memory
2 GB
Disk space
Software
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
Authentication server
Machine name
authentic.edi.com
IP address
192.168.2.13
255
System specifications
Memory
2 GB
Disk space
Software
Application server 1
Machine name
appserv1
IP address
192.168.2.11
Operating system Windows Server 2003 SP2 Standard Edition with critical
updates
CPU
Memory
2 GB
Disk space
Software
Tomcat 5.0.27
Application server 2
Machine name
appserv2
IP address
192.168.2.12
Operating system Windows Server 2003 SP2 Standard Edition with critical
updates
CPU
256
System specifications
Memory
2 GB
Disk space
Software
Tomcat 5.0.27
cluster1.edi.com
IP address
192.168.3.11
Operating system
CPU
Memory
2 GB
Disk space
Software
cluster2.edi.com
IP address
192.168.3.12
Operating system
CPU
257
System specifications
Memory
2 GB
Disk space
Software
cluster3.edi.com
IP address
192.168.3.13
Operating system
CPU
Memory
2 GB
Disk space
Software
boedb.edi.com
IP address
192.168.3.14
Operating system Windows Server 2003 SP2 Standard Edition with mandatory
updates
CPU
258
System specifications
Memory
2 GB
Disk space
Software
Oracle 9.2
corpdata
IP address
192.168.4.2
Operating system Windows Server 2003 SP2 Standard Edition with mandatory
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
259
System specifications
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
10
10
Purpose
Name
Cisco
CSS
11501
ccss01
Load Balancer
262
IP Eth0
IP Eth1
10.6.124.1 192.168.1.13
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
HTTP
Server
HTTP1
192.168.1.11
HTTP
Server
HTTP2
192.168.1.12
Firewall
FIRE
WALL1
qaunix/qaunixe
di
Firewall
FIRE
WALL2
qaunix/qaunixe
di
Firewall
FIRE
WALL3
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
Administra
tor/ediedi
APPSERV1_Us
er1/vanpass
word
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
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
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
CORP
DATA
Authentication Type
AUTHEN
LDAP/ADAM
TIC
Administrator User
Name/Password
Normal User
Name/Password
Auth_User1/vanpassword TestUser1/vanpassword
TestUser2/vanpassword
TestUser3/vanpassword
TestUser4/vanpassword
TestUser5/vanpassword
AUTHEN
LDAP/ADAM
TIC
266
n/a
Note:
267
10
10
268
Acceptance testing
11
11
Acceptance testing
Acceptance testing workflow
Result
Installation
Installing with EPM
Passed
Passed
Passed
Passed
Passed
Test cases
Result Comments
Designer
Create a universe
Passed
Test cases
Result
Comments
A Desktop Intelligence document with
prompt was created.
270
Acceptance testing
Acceptance testing workflow
Test cases
Result
Comments
Passed
Import a universe in
Desktop Intelligence
Passed
View/schedule a document
Passed
271
11
11
Acceptance testing
Acceptance testing workflow
Test cases
Result
Comments
Passed
Passed
Schedule a document
and open the same in the Passed
InfoView portal
272
Acceptance testing
Acceptance testing workflow
Test cases
Result Comments
Test cases
Result
Comments
Passed
Central Management
Console (CMC)
Create a new user
273
11
11
Acceptance testing
Acceptance testing workflow
Test cases
Result
Passed
Passed
Passed
Passed
Passed
Delete a user
Passed
Add a server
Passed
Enable/disable a server
Passed
Delete a server
Passed
Passed
Passed
274
Comments
Acceptance testing
Acceptance testing workflow
Test cases
Result
Comments
Passed
Passed
Passed
All Folders --> Folder_1 --> Folder_1_1 -> Folder_1_1_1 --> CR_CRPE Performance Suite - Crosstab document was
used
Passed
All Folders --> Folder_4 --> Folder_4_1 -> CR_Feature Mixture Benchmark_3754Rows document was used
Passed
All Folders --> Folder_4 --> Folder_4_1 -> CR_Feature Mixture Benchmark_3754Rows document was used
Passed
Create a folder
Passed
Delete a folder
Passed
Passed
275
11
11
Acceptance testing
Acceptance testing workflow
Test cases
Result
Comments
Passed
Test cases
Result
Comments
Passed
Passed
InfoView
Passed
Passed
276
Passed
Acceptance testing
Acceptance testing workflow
Test cases
Result
Comments
A Desktop Intelligence Report with
Prompt Refresh on Open was scheduled
using user U3_1.
Passed
_CDZ_FComplex_Medium_D1000 was
scheduled using user U3_1.
Schedule a publication
Passed
View a publication
Passed
Passed
Passed
Passed
Passed
277
11
11
Acceptance testing
Acceptance testing workflow
Test cases
Result
Test cases
Comments
CR_Feature Mixture Benchmark_10000Rows was viewed.
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
278
Acceptance testing
Acceptance testing workflow
Test cases
Result Comments
Publish/schedule a WID
Passed
document
Test cases
Result
Passed
Add a calendar
Passed
Passed
Passed
Create a set
Test cases
Result
Comments
Create a metric
Passed
Create an analytic
Passed
Passed
Passed
Metrics
279
11
11
Acceptance testing
Acceptance testing workflow
Test cases
Results
Comments
Create a goal
Passed
Save a goal
Passed
Passed
Passed
Test cases
Result
Comments
Create a strategy
Passed
Create a role
Passed
Passed
Create a ControlChart
through SPC
Passed
Create a rule
Passed
Goals
StrategyBuilder
Test cases
Web Intelligence Rich Client-3 tier mode
280
Result
Acceptance testing
Acceptance testing workflow
Test cases
Result
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
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
Passed
Passed
Passed
Passed
Passed
Passed
Save
Passed
Test cases
Result
QaaWS
281
11
11
Acceptance testing
Acceptance testing workflow
Test cases
Result
Edit a query
Copy a query
Delete a query
Test cases
Re
sult
Comments
Passed
282
Acceptance testing
Acceptance testing workflow
Test cases
Re
sult
Comments
Passed
283
11
11
Acceptance testing
Acceptance testing workflow
284
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?
286
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/.
For information about the full range of Business Objects products, visit:
http://www.businessobjects.com.
287
288