The following illustration shows the technical architecture of the environment used in this pattern. Each server node is identified with the logical name corresponding to the architecture components it hosts.
This illustration provides an overview of the system landscape and shows the role of each machine, not the workflow order of tasks to complete. To follow the pattern, complete the tasks in the order listed in Pattern Overview rather than the order shown below..
Key configurations of this technical architecture
The architecture shown in the illustration highlights four key aspects of the system landscape required for deployment:
• Clustered servers.
• Load balancing.
• Support for reverse proxy.
• Secured SSL.
Web Server / Reverse Proxy (
The machines that host the web server, reverse proxy server, and load ballancer commonly reside outside your external firewall. Customers can access Business Intelligence platform web applications, such as BI Launch Pad and the Central Management Console (CMC), from the client machine.
Apache is the web server chosen for this pattern, because Apache is the most commonly used web server on the web, hosting over 60% of all websites.
The latest supported version of Reverse Proxy Server in SAP Business Intelligence (BI) platform 4.0 Service Pack 4 is Apache 2.4, the current mainstream release.
For information about setup details, see Setting up Apache 2.4.
Windows AD Domain Controller / Authentication Server (
This pattern uses Windows Active Directory and SAP BW authentication methods. However, BI 4.0 supports many authentication modes. Depending on the infrastructure of your system, you may be able to choose a preferred authentication method.
For information about setup details, see Setting up the Authentication Server.
Web Application Servers (
WIN PB02 and
The application servers host Business Intelligence Platform web applications, such as BI launch pad and the CMC. For production systems, you must deploy at least two web application servers to manage failover and load balancing. Your system may require more than two. The only way to know how many web application servers your system will need is to do a detailed sizing exercise.
This pattern uses Tomcat version 6.
For information about setup details, see Setting up the Application Server.
BI Platform Servers (
WIN PB04 and
In this pattern, two nodes are dedicated to BI platform services. Those two machines are clustered and host all the BI platform services.
BI platform web applications detect each BI platform server machine (specifically, they detect all CMS Servers in a cluster), and then automatically load balance their requests. If one machine fails, the web applications automatically send all requests to the other machine.
For production systems, you must deploy at least two BI platform server machines. If you need to increase scalability, you can deploy more BI platform server machines. To determine the exact number of servers and server instances needed, do a detailed sizing exercise.
For information about setup details, see BI platform 4.0 cluster configuration .
BI Explorer Server (
For this pattern, SAP BI Explorer is deployed on a dedicated host.
For information about how to size for BI Explorer, and how to set up and configure SAP BusinessObjects Explorer, see Adding SAP BusinessObjects Explorer .
File repository server (
The File Repository Server (FRS) contains all reports and other BI documents that have been created. When a user creates a BI document, the BI platform servers retrieve the data from your company database (Reporting DB), generates the document, and stores it in the FRS.
For production systems, it's best to host the FRS on a separate machine because the BI documents it stores can grow to a large number. Also, because BI documents often contain sensitive information, be sure to host the FRS on a secured machine.
For information about setup details, see Configuring the File Repository Server (FRS).
BI platform System & Audit Database Server
BI platform uses a database for its system data, which is referred to as the system database or "CMS database". It's called the CMS database because, when a user wants to see a report, the CMS checks the system database to obtain the location of the report.
For production systems, you can host the CMS database either on the database included with BI platform or on your existing database. Both are recommended for production systems, but often companies use their own databases to simplify administration.
This pattern uses MS SQL Server for BI platform System and Audit databases.
For information about setup details, seeDatabase Overview.
OLAP Reporting DB Server (
MS SQL OLAP server is used as one of the reporting databases in this pattern.
For information about how to set up OLAP BP, the client, and to connect to SAP BI OLAP, see the OLAP Overview .