BOE ARCHITECTURE

PROJECT IDENTIFICATION

Project Name CPI/Project Number Project Type

Customer Name Customer Number Planned Start/Finish

SAP Customer Partner Project Sponsor Program Manager

SAP Project Manager Customer Project Manager Partner Project Manager

1 Project Preparation............................................................................................................4
1.1 BOE Architecture Assessment..................................................................................................4
1.1.1 Component Description..........................................................................................................4
1.1.2 Objectives...............................................................................................................................4
1.1.3 Prerequisites...........................................................................................................................4
1.1.4 Risks.......................................................................................................................................4
1.1.5 Considerations........................................................................................................................5
2 Business Blue Print............................................................................................................6
2.1 BOE Architecture Design...........................................................................................................6
2.1.1 Component Description..........................................................................................................6
2.1.2 Objectives...............................................................................................................................6
2.1.3 Prerequisites...........................................................................................................................6
2.1.4 Risks.......................................................................................................................................6
2.1.5 Considerations........................................................................................................................6
2.2 BOE Architecture Unit Test Planning........................................................................................7
2.2.1 Component Description..........................................................................................................7
2.2.2 Objectives...............................................................................................................................8
2.2.3 Prerequisites...........................................................................................................................8
2.2.4 Risks.......................................................................................................................................8
2.2.5 Considerations........................................................................................................................8
3 Realization.............................................................................................................................9
3.1 BOE Server Install & Configure.................................................................................................9
3.1.1 Component Description..........................................................................................................9
3.1.2 Objectives...............................................................................................................................9
3.1.3 Prerequisites...........................................................................................................................9
3.1.4 Risks.......................................................................................................................................9
3.1.5 Considerations........................................................................................................................9
3.2 BOE Client Tools Install & Configure......................................................................................10
3.2.1 Component Description........................................................................................................10
3.2.2 Objectives.............................................................................................................................10
3.2.3 Prerequisites.........................................................................................................................10
3.2.4 Risks.....................................................................................................................................10
3.2.5 Considerations......................................................................................................................11
3.3 BOE Web Connector Install & Configure................................................................................11
3.3.1 Component Description........................................................................................................11
3.3.2 Objectives.............................................................................................................................11
3.3.3 Prerequisites.........................................................................................................................11
3.3.4 Risks.....................................................................................................................................11
3.3.5 Considerations......................................................................................................................11

©SAP AG 2009
Copyright © 2009 SAP AG. All rights reserved 2
3.4 BOE Architecture Testing........................................................................................................11
3.4.1 Component Description........................................................................................................11
3.4.2 Objectives.............................................................................................................................11
3.4.3 Prerequisites.........................................................................................................................12
3.4.4 Risks.....................................................................................................................................12
3.4.5 Considerations......................................................................................................................12
4 Final Preparation...............................................................................................................13
4.1 BOE Architecture Deployment.................................................................................................13
4.1.1 Component Description........................................................................................................13
4.1.2 Objectives.............................................................................................................................13
4.1.3 Prerequisites.........................................................................................................................13
4.1.4 Risks.....................................................................................................................................13
4.1.5 Considerations......................................................................................................................13
5 Go-Live and Support.........................................................................................................14
5.1 BOE Architecture Review........................................................................................................14
5.1.1 Component Description........................................................................................................14
5.1.2 Objectives.............................................................................................................................14
5.1.3 Prerequisites.........................................................................................................................14
5.1.4 Risks.....................................................................................................................................14
5.1.5 Considerations......................................................................................................................14

©SAP AG 2009
Copyright © 2009 SAP AG. All rights reserved 3
1 Project Preparation
1.1 BOE Architecture Assessment

1.1.1 Component Description

Identify, prioritize and document detailed BOE Architecture requirements to be included and excluded from project
scope. Assess the workload and resource needs associated with the in-scope requirements and gain consensus and
agreement with stakeholders for the scope. Prepare for BOE Architecture Blueprint phase activities.

1.1.2 Objectives
 Analyze, assess and audit existing Server infrastructure (if available).
 Discuss sizing alternatives as well as server functions with the project team.
 Analyze necessary storage size and location for FRS.
 Validate that target platform is supported.
 Document the requirements around architecture and determine how long will it take to design, develop, test,
and deploy the BOE architecture.
 Review, with the Requirements Definition document at hand, the potential use of the system as it pertains to
the following areas:
o Number of potential users.
o Number of concurrent users.
o Number of reports and objects.
o Geographical location of users.
o Report usage and database locations.
o Number of environments (e.g. Development, Production, QA, Training).
o User type (e.g. Power Users, report consumer, etc.).
o Type of reports required (e.g. Deski, Webi, Crystal, Dashboard).
o Report scheduling requirements.

1.1.3 Prerequisites
 A business requirements definition.
 In case of newly acquired hardware: hardware configuration documentation, operating System and applications
installed.
 In the case of existing hardware: version(s) of the applications installed, operating System configuration and
systems audit report.
 Access to customer’s System Administrators, Network Administrators, Database Administrators, Web Server
Administrators, Web Application Server Administrators and other technical resources as necessary.

1.1.4 Risks
 Existing hardware resources not capable of supporting the requirements defined in the Business Requirements
Definition.
 Server infrastructure is shared with other applications that will impact the overall performance and behavior of
Enterprise. This includes running the BOE on VMWare.
 Customer has insufficient technical knowledge of their own system (may need additional training).

©SAP AG 2009
Copyright © 2009 SAP AG. All rights reserved 4
  Not having any Business Objects Enterprise audit facility enabled; this may lead usage patterns being
subjective.

1.1.5 Considerations
 What is the expected number of users on the system? This will impact the placement of server services to
ensure the indicated number of user requests can be satisfied.
 What concurrency rate is expected? This will determine (as in the bullet point above) the sizing of server
hardware and the enabling of additional server services.
 What are the locations of the databases? This will determine if a review should be done on the geographical
separation of hardware or what implications will there be on network traffic/database loading and throughput.
 Where are the users located? This will determine how web services should be deployed and how load
balancing should be incorporated.
 How are users using reports? Scheduled – Requires Job Server processing, View on Demand – Requires
Page Server processing.
 What is the expected growth over the near term as well as long term? This will determine the scalability
requirements.
 Although not required to be part of the initial review, it is good to identify potential scenarios where changes or
additions to the server architecture might be required.
 Volume and type of reports. This will impact the possessing servers and File Repository servers.
 Customer requirements with respect to life cycle management that will determine the need and size of
development and testing environments.
 Back up, Fault Tolerance and Disaster recovery requirements of the customer.
 Type of network and firewall used.

©SAP AG 2009
Copyright © 2009 SAP AG. All rights reserved 5
2 Business Blue Print
2.1 BOE Architecture Design

2.1.1 Component Description

The BOE Architecture requirements in the Project Preparation Phase are analyzed at the most detailed level possible
and then documented in formal design specifications. Consensus and agreement is required from the stakeholders
against the design specifications, prior to commencing BOE Architecture development activities.

2.1.2 Objectives
 Design a robust BOE reporting infrastructure.
 Use the Business Objects Enterprise Sizing and Performance Best Practice to determine number of servers,
components, services, CPUs etc that are needed to meet user performance expectations
 Design, with the Requirements Definition document at hand, the potential use of the system as it pertains to
the following areas:
o Number of potential users.
o Number of concurrent users.
o Number of reports and objects.
o Type of users.
o Report usage.
o Database locations.
o Architecture diagram per environment.
o Network topology, data flow and file structure.
 Review the design with the stakeholders. Discuss scalability and growth potential of the design.
 Obtain sign-off from the stakeholder

2.1.3 Prerequisites
 A business requirements definition.
 Completion of Business Objects Enterprise Architecture Assessment activities (e.g., sizing).
 In case of newly acquired hardware: hardware configuration documentation, operating system and applications
installed
 In the case of existing hardware: version(s) of the applications installed, operating system configuration,
systems audit report

2.1.4 Risks
 Acquired hardware will not support the robust design, forcing functionality limitations.
 Usage patterns and expected volumes determine in the Project Preparation Phase do not reflect actual usage
after deployment.

2.1.5 Considerations
 Server and system availability.
 Services Level Agreements for all relevant components.
 Physical location of the Hardware components.

©SAP AG 2009
Copyright © 2009 SAP AG. All rights reserved 6
  Load balancing.
 Router Configurations.
 Web Server type, location and security requirements.
 Web Application Server (Java Servlet Engine) type.
 Database where the CMS and Audit repositories are to be stored.
 Reporting Database.
 SAN for shared storage location and availability.
 Backup and restoration procedures.
 Fault Tolerance and Disaster Recovery plan.
 Replication plan for Federation in case of distributed deployment.
 In you are planning a large deployment, consider setting up CMS cluster. For CMS clustering, make sure that:
o Each server the CMS runs on must be on the same operating system and the same patch level.
o Each server the CMS runs on must be on the same version of Business Objects XI, including any
patches.
o All CMS machines should have the same amount of memory and same type of CPU. L oad-balancing
will be based on the machines being “the same” so different server specifications would lead to an
unbalanced load: too much load for the smaller machine, too little for the bigger one.
o Each CMS machine should be configured in the same manner.
o Each CMS communicates with database on the same IP address without relying upon a WINS server
for name-to-IP resolution.
o Run each CMS under the same user account, i.e. the same domain account or both using the
LocalSystem account.
o Make sure each CMS connects to the CMS repository database in the same way using the same
database drivers, i.e. using native connectivity, or ODBC, etc. and with the same user account.
o CMS database should not be on either of the machines hosting the CMS services, again, to avoid
skewing the load-balancing between the servers.
o Current date and time is set correctly on all the servers.
o Each and every CMS cluster member should be on the same subnet.
 Keep all job servers in close proximity to (but not on the same machine as) the database server against which the
reports run to improve performance.
 Vertical Scaling (additional BOE servers on the same hardware) is more appropriate for CPU bound licenses while
Horizontal scaling (additional BOE servers on additional hardware) suits better for named user licenses.
 Multiple Crystal Reports Page sever services should not be installed on a single server unless there is a need to
serve multiple server groups.
 Keep in mind that Web Application Server clustering is not supported by Business Objects and is not a tested
configuration though it works with some limitations.

2.2 BOE Architecture Unit Test Planning

2.2.1 Component Description

Prepare and document a battery of tests to confirm the accuracy and functionality of BOE Architecture components to
specification. The BOE Architecture Unit Test Plans will ensure effective and exhaustive testing processes are
consistently documented and executed.

©SAP AG 2009
Copyright © 2009 SAP AG. All rights reserved 7
2.2.2 Objectives
 Determine the anticipated load associated with all identified usage scenarios.
 Develop a comprehensive set of infrastructure test scenarios.
 Prepare Unit Testing strategy (what will be tested and how it will be tested).
 How to validate the anticipated load associated with all identified usage scenarios falls within the acceptable
range outlined in the test plan.
 Executing a comprehensive set of infrastructure testing scenarios as defined in the test plan.
 How to validate all user type samples can perform the tasks planned.
 How to check all installed components are correctly installed, enabled, and running.
 How to test integration with other BOE components, such as security, performance tuning, backup & recovery,
customizations, scheduling, etc.
 What would constitute successful release criteria.
 How to handle the risks in testing (lack of representative data) and contingencies (if testing cannot happen).

2.2.3 Prerequisites
 Completion of the Business Objects Enterprise Architecture Assessment and Design activities
 Design of Business Objects Architecture.
 Business Requirements Definition.
 Stakeholder agreement and sign-off on Business Objects architecture design.

2.2.4 Risks
 Appropriate test scripts that capture server response errors are not developed.
 Lack of representative data.
 Goals for the performance test not realistic.
 Availability of external resources including DBA, System Admin, Developers, QA people, Network
Administrators and Business Objects Infrastructure Architect.

2.2.5 Considerations
 Ensure that the key metrics for the overall tests have been defined.
 Assemble the appropriate team to do the performance testing.

©SAP AG 2009
Copyright © 2009 SAP AG. All rights reserved 8
3 Realization
3.1 BOE Server Install & Configure

3.1.1 Component Description

Install and configure Business Objects Enterprise server components into desired environment.

3.1.2 Objectives
 Correctly install and configure Business Objects Enterprise for optimum performance and scalability.
 Obtain stakeholder sign-off.

3.1.3 Prerequisites
 Hardware is ready with installed software and patches, a standard copy of the OS, database client, and web
server as well as other required 3rd party software is available.
 If the BOE database is to be migrated to a true DBMS, the database server has to be identified and created
with a ~200 MB empty database. Additionally, a specific database username must be created with DB owner
privileges to the system.
 Have appropriate Business Objects software license certificates and media in possession.
 The system architecture has been determined by a qualified consultant and approved by the customer.
 A domain account with local administrator privileges for running the BOE services has been created (if using a
network id). Alternatively, a LocalSystem account will suffice.

3.1.4 Risks
 Hardware environment is shared with other applications that can negatively impact the performance of
Business Objects Enterprise.
 Not all database providers and connectors have been preconfigured, which makes it impossible for Business
Objects Enterprise to contact data providers and retrieve relevant data when reports are run.

3.1.5 Considerations
 Prerequisite completion by the customer is often completed however the consultant should still review the
environment prior to installation.
 The customer should designate the appropriate number of system administrators, report developers, and web
developers to work with the Business Objects Enterprise project team for knowledge transfer purposes.
 Client reporting tools i.e. Desktop Intelligence and Crystal Reports should be installed on all Page, Job, and
RAS servers to facilitate troubleshooting database connectivity issues with reports.
 Make sure that the target of TEMP (NT/WINDOWS) or TMP (UNIX) variables are large enough to handle the
number of expected users and reports.
 Set advanced settings to "Maximize throughput for network applications".
 Checklist and Best Practices for Installation and Configuration:
o Network Configuration is in place for servers to communicate over TCP/IP.
o Correct ODBC server has been configured.
o Using PING utility, verify connectivity to the CMS.
o Verify Web server has connectivity with Application Server.
o Recommended size virtual memory in the system is equivalent to 1.5 times the amount of RAM.

©SAP AG 2009
Copyright © 2009 SAP AG. All rights reserved 9
 o Windows server should have Performance Options configured to give Background services priority on
the system.
o A minimum of 700 MB of free space is recommended for TEMP directory.
o In case of a distributed installation, ensure that a printer driver is installed on Cystal Reports Job
Server, Report application Server and Crystal Reports Page Server machines.
o For production environment, it is recommended that CMS database is not placed on:
 The database against which the reports are running otherwise it will impact the CMS query
performance negatively if the server is busy processing report data.
 Crystal reports Job server or Crystal reports Page server otherwise it will also impact the CMS
query performance negatively if the servers are busy processing jobs.
 A CMS machine in a clustered environment to avoid negative impact on load balancing.
 If Input and Output FRS are pointing to a network shared file server, the services need to run under a domain
account with read and write access to the network share file structure.
 In case a higher level of fail-over or fault-tolerance is required, it is strongly recommended that the load of
application tier be distributed over multiple application servers and balanced through a hardware load balancer.
 When backing up the existing system, make sure to backup CMS system database, Input and Output FRS,
user id and password of administrator, application code residing on web application server and registry
changes if manual changes were performed.
 Input and Output File Repository Servers cannot share the same directories. In larger deployments, there may
be multiple Input and Output File Repository Servers, for redundancy. In this case, all the Output FRS must
share the same directory. The same is applied for Input File Repository Server.

3.2 BOE Client Tools Install & Configure

3.2.1 Component Description

BOE client software components are installed and configured in desired environment(s). For example, install Business
Objects Designer, Desktop Intelligence, Business Views Manager, Migration Wizard, Import Wizard, Publishing Wizard,
Report Conversion Tool, Repository Migration Wizard, and universe Builder.

3.2.2 Objectives
 Install Business Objects Desktop Intelligence, Designer, Views Manager, Migration Wizard, Import Wizard,
Publishing Wizard, Report Conversion Tool, Repository Migration Wizard and universe Builder.
 Test client tools and configuration.

3.2.3 Prerequisites
 Validation of the product installation being supported in the Business Objects Product Availability Report (PAR)
for the specific environment.
 Required Middleware is installed and configured.

3.2.4 Risks
 Differences in the upgrade steps and procedures form one version to the next.
 The required permissions have not been granted, or in the cases where they are granted, may not be sufficient
to complete the installations.

©SAP AG 2009
Copyright © 2009 SAP AG. All rights reserved 10
3.2.5 Considerations
 Reboot the BOE server after install and unistall.
 Disable Anti-virus software before install to speed up the installation process.
 Install the fonts prior to installng the language packs (in case of XI3.0).
 Service pack updates are applied to all applications.
 Varify and test installation of each client tool.

3.3 BOE Web Connector Install & Configure

3.3.1 Component Description

BOE Web Connector installation and configuration to enable the passing of BOE requests to the BOE framework.

3.3.2 Objectives
 Install Web connector on appropriate web server(s)
 Ensure connectivity from all user workstations to pass all report view requests on to BOE via web connector.
 Obtain customer sign-off.

3.3.3 Prerequisites
 The presence of a supported Web Server.
 Appropriate access has been granted to install software to the Web Server.

3.3.4 Risks
 If a web server is not installed on the server where BOE is deployed, the Web Connector will not be installed.
This will require manual installation of the connector on the Web Server.
 Access and security restrictions may prevent the installation of web connector software on an active web
server.
 IT support personnel not available to assist in the deployment of the web connector.

3.3.5 Considerations
 Follow instructions in BOE installation guide for the installation process.

3.4 BOE Architecture Testing

3.4.1 Component Description

Based on the BOE Architecture Unit Test Plan, execute an exhaustive battery of tests to ensure BOE Architecture
components are functioning correctly and are accurate to its specification. If an issue is identified during the testing,
take an appropriate action to resolve it.

3.4.2 Objectives
 Validate the anticipated load associated with all identified usage scenarios falls within the acceptable range
outlined in the test plan.
 Execute a comprehensive set of infrastructure testing scenarios as defined in the test plan.
 Maintain appropriate environmental control factors as outlined in the test plan.
 Make sure represented user type samples can perform the tasks planned.
 All installed components are correctly installed, enabled, and running.

©SAP AG 2009
Copyright © 2009 SAP AG. All rights reserved 11
  Test integration with other BOE components, such as security, performance tuning, backup & recovery,
customizations, scheduling, etc.

3.4.3 Prerequisites
 BOE Architecture Test Plan.
 Business Intelligence infrastructure diagrams.
 Network diagrams.
 The list of touch points with other applications, interface documentation to test hand-off to and from other
applications.

3.4.4 Risks
 Too many tests are being conducted in too short a timeframe.
 Platform changes might require additional testing.
 Results from testing procedures may require changes in the design that potentially could increase project cost
and time.

3.4.5 Considerations
 Before conducting unit tests, confirm that the installation was successful by verifying that you are able to:
o Open the admin launch pad.
o Log on CMS.
o Log on to CMC.
o Log on InfoView.
o Refresh a report in Deski, Webi and Crystal Reports.
o Publish, view and schedule a report.

©SAP AG 2009
Copyright © 2009 SAP AG. All rights reserved 12
4 Final Preparation
4.1 BOE Architecture Deployment

4.1.1 Component Description

Completed BOE Architecture software components are deployed to desired environment for access by end users.
Necessary activities are performed to ensure BOE Architecture components are successfully adopted by end user
community.

4.1.2 Objectives
 Update the Infrastructure Design Specification to match the actual deployment.
 Document installation notes (if necessary).
 Perform knowledge transfer to the customer IT and transfer maintenance responsibilities to the customer IT
team.

4.1.3 Prerequisites
 Business Objects Enterprise Architecture design activities completed.
 All components of Business Objects Enterprise are installed and configured.
 All testing of installed and configured software has been completed successfully.
 User population has been notified of potential downtime and changes in system when restored.

4.1.4 Risks
 Deployment to production has challenges due to inconsistencies in PROD environment compared to others.

4.1.5 Considerations
 All the design and test documentation has been updated and signed off by the customer
 A best practice methodology and strategic approach documentation to trouble shooting architecture issues are
in place and shared with the customer.
 Customer team has been trained and ready to take ownership of the system.
 UAT is done and signed off by all stake holders of customer team.

©SAP AG 2009
Copyright © 2009 SAP AG. All rights reserved 13
5 Go-Live and Support
5.1 BOE Architecture Review

5.1.1 Component Description

BOE Architecture application components are reviewed and results are documented. Also included is appropriate
recommendations to ensure BOE Architecture components are evolved and improved in subsequent project activities.
Results are presented to customer.

5.1.2 Objectives
 Interview system owners and representatives of the user population.
 Analyze system audits.
 Perform through reviews of the existing BOE architecture and infrastructure, using the following criteria:
o Ease of use and maintenance - How the BOE architecture is architected and deployed, how easy it is
to administer and maintain, integration with the customer's existing infrastructure.
o Validity - Adherence to the original business and technical requirements; review if the current
deployment meets the original requirements and current technical restrictions/requirements.
o Performance - Overall workflow and load analysis to find performance tuning and architectural
changes and/or enhancements opportunities.

5.1.3 Prerequisites
 Sufficient time between deployment of the system and the review to allow system users and owners to form an
opinion.
 System audit feature has been running since the system was deployed and is reportable.

5.1.4 Risks
 Insufficient time between deployment of the system and the review has elapsed to allow system users and
owners to form an opinion.
 System audit feature has not been running since the system was deployed and is reportable.

5.1.5 Considerations
 Take a note of the actual usage and load with respect to estimated usages and load.
 Make sure that the work-flow for system maintenance is followed as laid out in the design.
 Take a note of performance issues and suggest configuration changes for performance tuning. If configuration
changes are made, rerun specific tests and compare results to the benchmark tests.

©SAP AG 2009
Copyright © 2009 SAP AG. All rights reserved 14