Hello,

I am really looking for feedback on my first document in a series of three [ Architecture, Migration and Checklist] to see what I am missing and if I could hand this over to any consultant to do a simple install of BI4.x and Migration. I would like to find a way to place my word document into this site cleanly but the outcome below is not so nice.

There are many reference documents not included, and they will be included after receiving comments on this document.

Also;

Thanks,

Jim

BI 4.1 Architecture Design

Table of Contents                                             

BI 4.1 Architecture Design.. 1

Architecture Design.. 3

1. Introduction. 3

Run books. 3

Pre-Install. 4

1. Investigation. 4
2. Inventory. 4
3. Components. 4

Architecture Diagram Support 4

1. Platform.. 5
2. Diagrams. 5
3. Sizing. 5
4. RAM.. 5
5. APS. 5
6. JAVA. 5
7. Recommendation. 5

Type of Install 5

1. Communication. 5

Gather information.. 6

Install BI4.x. 8

Download software. 8

Sever Install 8

1. Sequence. 8

Uninstall the Server Software. 8

Desktop Install 9

Authentication Setup. 9

Audit Universe Install 9

Other Support Install 9

Flash Player 9

1. JAVA. 9

POST Install. 10

Validate the Install 10

Unwanted files. 10

1. Security. 10
2. Logs. 10

User Groups – Authentication. 10

Support tools. 10

SAP Platform tool 10

GLF viewer 10

1. DELIVERABLES. 11

Document 11

Run Books. 11

1. REFERENCE. 12

BI4.1 Platform.. 12

SAP PAM... 12

1. Sizing. 12

SAPBO APS. 12

SAP Platform Installation. 12

SAP Audit Install 12

1. Authentication. 12

Uninstall 12

1. APS. 12

EXCEL project plan. 12

Platform Support Tool 12

GLF Viewer 12

1. Flash. 12

Architecture Design

Introduction

The first step in installing any version of Business Objects is in understanding the existing (Source) environment [include Service Pack and any Patch update] and the Target environment. Use this document as a template; since every SAP Business Objects install is unique, they all come with their own set of issues and bugs. This document is intended as a starting point and not an all-inclusive list of activities to complete for your client. Throughout this document the use of “Refer to …” will be found in the section called REFERENCE for supporting information.

The BI 4.x Install with a Migration is a demanding project. Prepare to deliver a well thought out Plan: Milestones, Test Strategies, Content Inventory, Cleanup (before and/or after) – just to name a few.A good beginning to start this project is to review the “Business Intelligence Platform Upgrade Guide”. This guide explains every way to install BI 4.x. Refer to SAP Platform

Run books

Each segment, of the install, requires a document be created for knowledge transfer to the client. This should include screen shots of each step with an explanation of what is going on at that step or group of steps. Run Book creation should never be looked at as time consuming, they serve a purpose for referring back to how something was done.

Once the Run Book is complete, go back over it a few times before presenting it to your client. Yes this is time consuming, but it will help in finding those misdirected words or unwanted screen shots and it will make the Run Book a better document to be presented to your client.

A typical layout of all the BI components and all could be found on one server or on separate servers

Pre-Install

Investigation

Create a list of what is on the Source, what will be on the Target, and all components in-between such as the Network, Authentication server and the [CMS/AUD] database. This will be the foundation of the Run Book and Diagrams.

Inventory

Create a complete list of all types of objects and how many of each. Determine which (object’s) will be moved and if there is a need to do a cleanup in the Source or Target environment. Are there any objects that need to be converted (Desktop Intelligence reports)?  Here are a few items that could be at your client, include all that you find.

• Report
  • Scheduled / Paused / Fail [what to do with them?]
• Universe
• Business Views
• Dashboards
• Calendars
• Server Groups
• Data Connections
• Access Level

Components

This will include all items that make up the Target environment. Possible list of items to include are:

• Server specification [Disk space, RAM, Drives…]
• JAVA [Server and Client desktop]
• Firewall
• Authentication Server [AD, LDAP or SAP]
• Load Balancer
• Database [CMS / AUD]
• Input / Output server [FRS]
• All BO servers
• Web
• CMS
• Processing
• APS (split them up? – How)
• Data Connections

Architecture Diagram Support

Create a high level Architectural diagram for both the Source and Target environments. Be as detailed as possible and if needed drill into areas of importance. Use what you found from the Investigation above to design the Target environment.

Platform

Cross check what the client has (for all hardware) will be sufficient with SAP PAM document. Refer to SAP PAM

Diagrams

Create both the Source and Target diagrams and be as specific as possible. This will be used through-out the project and the foundation of all communication.

Sizing

Each BI4.x install is different and underestimating the complexity of the whole environment will become the success of the project. The sizing guide is just a starting point and not an exact account of how the system should be designed. Not using it will surely be a downfall of the project. Refer to Sizing

RAM

There is a minimum number for the BI4.x environment, be generous with RAM:

• Java allocates memory in “heaps” which can quickly grab large amounts of RAM
• Java garbage collection happens more frequently under memory pressure
• Heavy memory pressure can cause swapping at the OS level

APS

Break down what components that will be on each BO server and which APS will be used on which server. How much RAM is available on each server depends on where each APS will be located. Review all the different APS that can be used. Refer to SAPBO APS

JAVA

Which version will be installed will depend on reviewing the SAP PAM document. Once installed on the Desktop, testing will be a key to having the correct JAVA installed. Test everything from running / scheduling and creating a report at a minimum. Refer to SAP PAM

Recommendation

This will be a document based on all the information gathered from the Investigation and the Diagram support.

Type of Install

The questions that will be answered are: Single vs. Clustered, Vertical vs. Horizontal, and to identify all server components and on which server. This may have been determined already by the Client otherwise the recommendation document may help determine the direction.

Communication

Whether the recommendation document is explained by you or the client, [to the Client’s management] a confirmation is required to move forward and install the software by design or with modifications. This is the beginning of all communication with the client that will continue to the end of the project. A daily recap with your client and a weekly update with your manager are required at the very least. The document to use (or start with) should be as a Project Plan and this can be in any format, an example of this document, Refer to Excel Project plan

Gather information

BI4.x Administrator – Password

BI4.x Logon to Server – ID & Password

Database

Authentication 

License Keys 

Cluster Keys – Production 

Cluster Keys – Test (QA)

Cluster Keys – Development

Cluster Keys – Sandbox 

Install BI4.x

Download software

After downloading [ALL] the SAP BI4.x software, the location (at the client site) of the install software should be accessible to all BI4.x environments. And the disk space should be enough to support the unzipping of the file. It is very large when unzipped. Can this be located on a SAN server away from and off the BI4.x server? Yes it should, and shall be removed once the project is complete. The software should include the Server, Client, and application software (Audit Universe, Crystal Report and Dashboard).

Sever Install

With the design of the entire BI4.x environment known from the ‘Recommendation’ document and ‘Communication’ (above), the path to install can now be laid out. Refer to SAP Platform Installation

There are a few scenarios to choose from:

1. Single server – everything on one server
2. CMS server, Processing server
3. Web server, CMS/ Processing server
4. Web server, CMS server, Processing server

Sequence

After gathering all the ID’s and Keys required to complete the install, you can now begin. Logon to the first server and start the install. It is best to wait until the competition of one install before beginning the next server. Request that (each) server be bounced before starting the install; a clean CACHE is best.

Repeat for each server to install the required components

1. Start the install
2. Enter information required
3. Wait until completed
4. Verify components installed
5. Test logon
6. Reboot server – cleanup process

Uninstall the Server Software

Sometimes the install does go the way it was supposed to and the best solution is to start over. This document explains the process to have a clean start all over again. Refer to Uninstall

Desktop Install

This will be the most simplest to install …Logon to the [Server and/or Desktop], go to the install folder of the desktop executable, click to install…done. For the applications (Crystal Report and Dashboard) just click on the install and enter the License key. Now to use any of the tools may require a data connection, or permission. Setup maybe needed.

Authentication Setup

For any type of authentication [SAP, AD, LDAP] the set-up is required since we want the groups created from a third party and not just the Enterprise. Refer to Authentication

Audit Universe Install

To install the Audit universe and audit reports, first locate the site to download the zip file. Unzip the file and follow the readme document included in the files. The reports can be installed by the Promotion Manager. Refer to SAP Audit Install

A new Audit database, Universe, and Reports are used in BI4.x but the BO 3.x can still be used in the new environment to modify the new reports.

• Keep existing XI 3.x audit database for historical data
• Move the XI 3.x audit application (universe + reports) into the new system
• Start BI 4.0 with a fresh BI 4.0 audit database
• Install the BI 4.0 sample audit universe and reports (found on the web site)
• Customize the samples or re-develop reports to match XI 3.x and BI 4.0 needs
• If continuity is needed: Create a multi-source universe and appropriate reports to get audit continuity before and after the upgrade

Other Support Install

Flash Player

Flash Player is required to execute a few applications such as; Web Intelligence Reports and Dashboards. The Install of the Flash Player will be for Desktops. The concern is that some versions of Flash player may cause problems for SWF files. Refer to Flash

JAVA

When running a Web Intelligence Report (first time) on the desktop, a JAVA request pop up will appear and the choice to install the selection available (normally the latest version) and should be determined by the PAM document (see JAVA above). The most important take away from this install is that a TEST (using the JAVA install) is mandatory. Do not wait until you turn over the system for testing to the client. If the current version is NOT acceptable, get the version that is and request that that version be the one installed on all Desktops.

POST Install

A few items that need attention before the install will be complete.

Validate the Install

Identify what needs to tested and execute a relevant testing plan

Unwanted files

Remove the install files, they are no longer needed.

Security

Specify rights with new products (WRC, IDT, LCM, etc)

Logs

Check the log file for errors.

• Are there any? – Major or Minor; in either case a follow up of what happened is required. Research the error on the SAP site; send an email to your co-workers, reach out to your favorite Business Object site or do a search on the Internet.  When all else fails, create a SAP ticket.

User Groups – Authentication

In the Authentication tab, you placed the “Do not update AD Groups and Aliases now’, change this option back or keep it this way if the Source has it this way.

Support tools

Here are few tools to help through-out the life of the BI4.x.

SAP Platform tool

              Refer to Support Platform Tool

GLF viewer

                Refer to GLF Viewer

DELIVERABLES

What will be presented to your client? Here is a list of a few items, and more is acceptable.

Document

• Inventory of BO3.x environment components
• Diagrams of Source and Target environments
• Sizing documentation of the new BI4.x environment
• Schedule (dates) of Migration
• List of questions (and answers)
• Security issues with solutions <if required>
• Project Plan
• Server install
• Applications Install [Crystal Report, Dashboard, Live Office …]
• Desktop install

Run Books

REFERENCE

For all references for each topic below can be found in the accompany documentation or web site.

BI4.1 Platform

SAP4.1 Migrate Platforms.pdf

SAP PAM

SAP BI 4.1 Supported Platforms PAM.pdf

Sizing

Http://sap.com/bisizing

This site is full of information that will help ensure good system performance and stability.

SAPBO APS

Best Practices for SAPBO BI 4.0 Adaptive Processing Servers.pdf

SAP Platform Installation

sbo41sp2_bip_inst_win_en.pdf

SAP Audit Install

http://scn.sap.com/docs/DOC-6175

Authentication

             See Chapter 7 - Authentication for all types

xi4sp5-Authentication.pdf

Uninstall

1691555 - How to completely remove _ uninstall SAP BO BI 4.0 from the system

APS

Best Practices for SAPBO BI 4.0 Adaptive Processing Servers.pdf

EXCEL project plan

Business Objects 4.1 Upgrade - Project Plan_V5.xls

Platform Support Tool

http://wiki.scn.sap.com/wiki/display/BOBJ/SAP+BI+Platform+Support+Tool

GLF Viewer

1909467 - Where can I download the GLF Viewer for BI Platform 4.0 and BI Platform 4.1?

Flash

1767674 - Browser crashes when running nested dashboards using swf loader with Flash Player 11