Serco-NA Technical Architecture
Lloyd Palfrey Click to edit Master subtitle style Architect Senior Technical 01/04/2011
Copyright 2010 Bluefin Solutions
Objectives
Document Objectives The objective of this document is to define the production technical architecture for the Serco-NA BW, BPC and Business Objects project. Define the development landscape and sizing based on the architecture in this document Architectural Objectives Provide end to end high availability Saleable and flexible architecture Utilize virtual x86 guest servers to reduce TCO Align architecture with other Serco projects where possible
Copyright 2010 Bluefin Solutions
Proposed Production Architecture
Copyright 2010 Bluefin Solutions
SAP BW Central Instance Servers
1 x SAP BW (ABAP) OS Software Oracle Instances Databases SAP Instances High Availability AIX 6.1 LPAR SAP BW 7.0 EhP1 SP6 Central Instance, Oracle 11G 1 1, BWP 1, BWP High Availability is provided by HACMP
1 x SAP BW (Java) OS Software Oracle Instances Databases SAP Instances High Availability AIX 6.1 LPAR SAP BW 7.0 EhP1 SP6 Central Instance, Oracle 11G 1 1, EPP 1, EPP High Availability is provided by HACMP
Copyright 2010 Bluefin Solutions
SAP BW Application Servers
2 x ABAP Application Server OS Software Databases Connections High Availability User Connectivity AIX 6.1 LPAR SAP BW 7.0 EhP1 SP6 App Server, Oracle Client 1, BWP High Availability is provided by VMware HA clustering and the fact there are mulitple application servers. All user connectivity to go via SAP Dispatcher. This will not only load balance over the available application servers but will also provide failover in the event of an application server failure
2 x Java Application Server OS Software Databases Connections High Availability User Connectivity AIX 6.1 LPAR SAP BW 7.0 EhP1 SP6 App Server, Oracle Client 1, EPP High Availability is provided by VMware HA clustering and the fact there are mulitple application servers. All user connectivity to go via SAP Dispatcher. This will not only load balance over the available application servers but will also provide failover in the event of an application server failure
Copyright 2010 Bluefin Solutions
Web Dispatcher
2 x SAP BPC Server OS Software High Availability User Connectivity AIX 6.1 SAP Web Dispatcher 720 High Availability is provided by HACMP All SAP ABAP and Java connections to go via this dispatcher installation
SAP BPC .NET Servers
2 x SAP BPC Server OS Software High Availability User Connectivity Windows 2008 SP2 Enterprise SAP BPC 7.5 SP7 The two .NET servers to be in a windows cluster BPC rich clients and web clients point directly to the clustered hostname providing load balancing and failover.
Copyright 2010 Bluefin Solutions
SAP Business Objects Servers
1 x Business Objects Database Server OS Software Oracle Instances Databases High Availability AIX 6.1 LPAR Oracle 11G 1 2, BI4CMS & BI4AUDIT High Availability is provided by HACMP
2 x Business Objects Application/Web Servers OS Software Databases Connections High Availability Redhat Linux 5.6 Oracle Client, SAP BI4 BI4CMS & BI4AUDIT High Availability is provided by VMware HA clustering and the fact there are mulitple application servers. The two servers will be in a CMS cluster. BI4 rich clients to point to CMS cluster name. BI4 web connections to go to either of the two severs. [Risk]
User Connectivity
Copyright 2010 Bluefin Solutions
Proposed Production Architecture Summary
Key Points Highly Scalable Infrastructure All critical servers hosted on AIX Linux and virtual servers utilized where possible to reduce TCO Assumptions Solution manager and SAP router already exist Serco deploy BI4 instead of Business Objects Enterprise XI 3.1 Risks Web connections to Business Objects are not clustered. In order to do this hardware load balancing in the form of Cisco content switch or F5, or a software load balancer/cluster that supports source IP address persistence
Copyright 2010 Bluefin Solutions
Development Landscape
Copyright 2010 Bluefin Solutions
Development Sizing
OS Database ABAP/JAVA Business Objects BPC .NET IBM AIX 6.1 Red Hat Linux 5.6 Windows 2008 Server SP2 CPU 0.1 1.5 Core 2 Core 2 Core Memory 16GB 6GB 2GB Disk 300GB 20GB 10GB
Key Points Disk space is in addition that required by the OS Mount points to be defined in pre-build document Memory resources should not be contended
Copyright 2010 Bluefin Solutions
10
Next Steps
Review and discuss Technical Architecture Sign off technical architecture Prepare Development pre-build document detailing the server configuration
before they are handed over to Bluefin for installation Production Sizing Prepare QA and Production pre-build document
Copyright 2010 Bluefin Solutions
11
Thank You
Lloyd Palfrey Senior Technical Architect Click to edit Master subtitle style +44 (0)7825 021599
Copyright 2010 Bluefin Solutions
12
