openSAP BIFOUR1 Week 2 Installation Upgrade Promotion PDF

Week 2 Unit 1: Installation
BI 4.x Products and Components
BI 4.x Server
13+ Server products BI Servers hosting such services as WebI, Crystal Reports, Dashboards, Explorer, and Design Studio Server tools such as CCM, SIA, and WDeploy
BI 4.x Clients
BI 4 Client Tool package containing such clients as WebI Rich Client, Information Design Tool, and Report Conversion Tool Crystal Reports for Enterprise and Crystal Reports 2011/2013 MS Office based products such as Analysis for Office and Live Office
2013 SAP AG. All rights reserved.
Public
BI 4.x Server Installation Tips
Refer to the Product Availability Matrix (PAM) and Supported Platforms (PAR) to plan your installation BI 4.x Server and Web Application Server must be installed on 64-bit servers and use 64-bit JDK Minimum hardware recommendations as follows:
Public
Install and Configure database middleware if using an external database server Install all needed languages during the initial BI 4.x installation Select Full or Web Tier install types depending on requirements Determine if a side-by-side installation is required
BI 4.x and XI 3.1 servers can be installed on the same machine BI 4.x and XI 3.1 clients can be installed on the same machine
Public
Make note of CMS Cluster Key and important user passwords

You will not be able to repoint the CMS system database without the Cluster Key Administrator, System Database, and Subversion passwords are important
Ensure the installation directory meets requirements

The path cannot contain special characters Keep the path simple to prevent it from becoming too deep
Public

Windows Platform
Install Microsoft .NET Framework 3.5 SP1 or higher Disable Anti-Virus software and Windows Firewall during install
Anti-Virus can slow down an installation significantly as it scans each file Firewall can prevent servers from communicating with system database or CMS
Install user must be a member of Local Administrators Group

Ensures that installation can write to Windows system folders and create registry entries as needed
Public

Unix/Linux
Install Required Libraries

Consult Install guide for details http://help.sap.com/bobip
List of Utilities:
Install Required Utilities Set locale settings

syntax can be different on different UNIX flavors and shells; for example:
export LANG=en_US.utf8 export LC_ALL=en_US.utf8
Dont use root user for install Set ULIMIT to Unlimited

Public

Unix/Linux
BI 4.1
For BI 4.1 Sybase SQL Anywhere 12.0.1 is default db for CMS and Audit Databases
On a clustered environment
Install SQL Anywhere Database Client Create an ODBC DSN connecting to the primary node SQL Anywhere CMS DB.
Check Kernel Parameters on Suse Linux

kernel.sem = 250 32000 32 1024 kernel.msgmni = 1024 kernel.shmmax = 18446744073709551615
Public
References
Business Intelligence Pattern Books:

http://wiki.sdn.sap.com/wiki/display/BOBJ/Business+Intelligence
Business Intelligence Platform Installation Guide (UNIX):

http://service.sap.com/~sapidb/011000358700000805302013E/sbo41sp1_bip_inst_unix_en.pdf
Business Intelligence Platform Installation Guide (Windows):

http://service.sap.com/~sapidb/011000358700000805312013E/sbo41sp1_bip_inst_win_en.pdf
Public
Thank you
Contact information: open@sap.com
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. National product specifications may vary. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty. SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries. Please see http://www.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and notices.
Public
11
Week 2 Unit 2: Configuration
BI 4.x Server Configuration Tips

Web Applications Properties
Bilaunchpad.properties CrystalReports.properties
dsws.properties
Controls settings specific to the BI Launch Pad application Ensure custom changes are made to the following parameters:
authentication.visible authentication.default cms.default
Controls settings specific to the Crystal Reports application Ensure custom changes are made to the following parameter:
cms.default
Controls settings specific to the Web Services application Ensure custom changes are made to the following parameters:
domain qaaws.principal.username qaaws.principal.password
Public

Update CMC Application Parameters
Update Web Services Access URL

This value is used for Dashboards using the direct query connection It can be picked up automatically for Web Service based dashboards if you dont specify a URL
Set the Open Document Processing Settings

Certain application, like Design Studio, require this to be set for viewing applications on the BI Platform
Public

Cluster Settings
Update the cluster name using CCM or serverconfig.sh

The value defaults to the first CMS in the cluster Change this to provide a friendly name for your environment such as BI41Production
To make web applications cluster aware update the PlatformServices.properties file
Public

Update Java Settings
Update Java Options for Tomcat

<install location>/sap_bobj/tomcat/bin/setenv.sh Start > Programs > Tomcat > Configure Tomcat > Java
JAVA_OPTS="-Xms128m Xmx2048m -XX:MaxPermSize=512m
Set Tomcat Garbage Collector

Java 6: JAVA_OPTS=-XX:+UseParallelOldGC Java 7: JAVA_OPTS=-XX:+UseG1GC
Update the JDK used by Tomcat to take advantage of security and performance improvements
Public

Firewall Settings
Reserve a port range to be used for BI to communicate through the firewall

For example, reserve ports 6400-6700 for BI use and remember port 8080/8443 for Tomcat Port ranges make firewall monitoring easy Enable easy repetition in BI environment expansion
Bind each BI service to a specific port

Ports can be configured from the CMC server properties Leverage requestJSChildPorts switch on Job Server command line for Job Server Child processes Align Job Server Child ports with Job Server to minimize complexity
Public

Other
Exclude the Tomcat web application directory from AntiVirus

Scanning the directory increases Tomcat startup time Web Application Deployment time is increased exponentially if scanned by Anti-Virus
In BI 4.1, use the System Configuration Wizard to shut down unwanted products Turn off monitoring in the CMC if not needed
Public
Single Server Deployment
Best suited for small organizations Downtime can cause long periods of unavailability Proper backups are critical to recovering single server deployments Processes can be vertically scaled to increase capacity
Public
Horizontal Scaling
Also known as Scale Out

Scale out web applications by adding a web server and splitting out static content Distribute BI Platform servers on specialized nodes for Management Tier and Processing Tier
Primary use case for redundancy and fault tolerance

Distribute multiple instances of processing servers, such as Web Intelligence, to ensure availability in case of server failure
Web Connector (e.g. AJP 13)
Web Client
Web Server
Serves static content or redirect only
Web Application Server

Serves static and/or dynamic content
BI Platform Servers
Public
Horizontal and Vertical Scaling

Web Client
Hardware Load Balancer
Web Server Farm

Static content or redirector only Web Connector (e.g. AJP 13)
Application Server Cluster (Session Replication)
BI Platform Servers
Public
10
Performance Challenges
Often have slower links resulting in increased wait times Non-optimized cache settings cause additional server roundtrips to download content
Lack of Cache-control Public header prevents pervasive caching on proxies Standard proxy servers cannot cache content delivered over SSL
Increased GC from Application Server handling static content More GC cycles reduce throughput and can cause application pause times
Public
11
Apache Web Server and WDeploy
Apache is the most popular web server in the world today running an estimated 63% of all web sites.
Available branded as IBM HTTP server for use with WebSphere where it provides equivalent functionality Provides modules that extend core functionality and enable optimization of static resources
The WDeploy tool is included with SAP BI Platform to ease deployment of web applications to Java-based web application servers.
Supports auto-configuration of HTTP server connectors such as MOD_JK or IBM HTTP server plugin Separates static content and automatically deploys it to your supported web server of choice
Public
12
Apache Modules Explained

Allows forwarding of dynamic requests to Application Server for processing Enables Load Balancing and Reverse Proxy features for added performance, reliability, and scalability
MOD_JK
MOD_HEADERS
Apply Cache-Control headers such as Public and Max-Age Remove extraneous ETag or Last-Modified Headers
MOD_CACHE
Deliver in-memory or file system based caching Automated maintenance of file system cache with Htcacheclean process
MOD_DEFLATE
Simple HTTP compression for more effective static content delivery
Public
13
Web Application Deployment with WDeploy
wdeploy.bat tomcat6 deployall wdeploy.bat tomcat6

Das_mode=split Dws_type=apache deployall
wdeploy.bat tomcat6 Das_mode=split Dws_type=apache predeployall Dwork_dir=C:/temp
C:\Program Files (x86)\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\warfiles\webapps
C:\temp\tomcat6\resources
Public
14
Changes to WDeploy Split mode

WDeploy static content in XI3.1 WDeploy static content in BI 4.x
~5.5x increase to the amount of static content separated in BI 4.x
Public
15
Thank you
Public
17
Week 2 Unit 3: Upgrade
Overview
Objective: How to upgrade content from previous versions of the platform such as 3.1 and XI R2

Upgrade Manager Tool Upgrade Scenarios Upgrade Workflows Upgrade Manager Best Practices
Public
The right tool for the job in BI 4

Upgrade Upgrade Manager
Upgrade: Transport and transform content from previous version to newer version Content includes all objects. Improvement over previous releases: Now a unique and scalable tool dedicated to upgrading from previous versions. Functionality looks similar to Import Wizard from previous XI versions
Promotion LCM
Promotion: Transport content from like system to like system Systems are the same major version, e.g. Dev to Test to Production. Content is primarily document templates, metadata, and schedules. Not document instances. 100 objects or less!
Public
Upgrade Manager Live-to-Live Scenario

Optimized for a large amount of objects. No intermediate step or storage
Systems running in parallel and connected
2 ways (Incremental or Complete) Required to have source and destination systems up and running Ports must be opened between source and destination
Administrator running Upgrade Manager
Public
Upgrade Manager BIAR-to-Live Scenario

Needs to be used when the previous and new systems cannot be connected Allows to keep a snapshot of the content and possibly restart the process from it Use small BIAR (10,000 objects, 1GB max recommended)
BIAR file Previous version XI R2 or XI 3
Administrator running Upgrade Manager
Public
Basic Upgrade Workflow Full System
Replaces Database Migration in Central Configuration Manager Easily upgrade your entire repository in 4 steps
1 2 34
Available in Windows GUI and Unix command line
Get the summary Choose Upgrade Choose the of what going to scenario & is enter End Complete Upgrade be upgraded credentials
Public
Basic Upgrade Workflow Staged

To perform an Incremental Upgrade:
3 4
Choose Upgrade Choose objects objects to to Choose the Choose End scenario & enter exclude & options & options Incremental copy Upgrade credentials
Public
Upgrade Manager Best Practices
Clean-up your source system before migrating content Increase XMX setting in UMT command line Change (if necessary) temp directory to allow for more space -Djava.io.tmpdir=TEMP PATH Map AD groups and roles in the destination system prior to running the upgrade (* simplified in 4.1 )
Public
Summary
Upgrade Manager upgrades content from previous versions of the platform such as 3.1 and XI R2. You should now be able to:

Describe the function of the Upgrade Manager Tool Describe upgrade scenarios Perform upgrade workflows Describe Upgrade Manager best practices
Public
Thank you
Public
11
Week 2 Unit 4: Promotion
Why Is LifeCycle Management Important?

Setting the context
Industry regulations (such as the Sarbanes-Oxley Act and HIPPA) require new levels of rigor when moving content from between environments. Internal controls are required for:
How changes are made Who can access production systems Synchronizing changes across complex systems landscapes
Reports need to be correct and on time with:

Minimal downtime Changes to systems, data, or processes that are thoroughly tested
Sensitive data must be protected. Business intelligence has become mission critical.
Public
Why Is LifeCycle Management Important?

Basic principal, separate environments
Develop content (reports, universes, etc.)
Validate content Test security Test software (support packs, patches, etc.)
Increase security:
Verify changes
Reduce costs:
Avoid errors Avoid rework Avoid system downtime

Recover from errors and mistakes Recover from malicious acts Safeguard information
Public
3
What Is Promotion and Version Management?

What Promotion and Version Management is NOT designed for?
Promotion and Version Management is NOT designed for:
Backup Disaster Recovery Archiving
Why?
Focused on Promotion workflows Optimized for 100 objects/promotion
However, it may form part of a recover strategy since it is possible to

Re-promote content, thereby restoring lost or corrupted content Check out previously checked-in content, from Version Management, thereby restoring lost or corrupted content. Promote selected content, typically ad-hoc content, from Production into another environment such as development.
Public

Basic promotion management workflow
Content is in Development We want to promote it into Test, for testing Then we want to promote it again into production
Public

We firstly create a promotion job
Public

We then run the promotion job, so the content is promoted into Test
Public

If the test of that content was successful, we can then re-run the same promotion job, but we change the target to Production. (as per SAP TMS / CTS+ ) Promoting content from Test to Production does not follow this principal and so it is considered poor practice.
Public
What is Version Management?

Basic version management workflow
There are basically two workflows

Check-in. This creates a new revision of an object (like a document, or a universe) every time you check it in. Check-out. This overwrites the version in the BusinessObjects Repository with the revision you select.
Public
High-Level Architecture
Recommendation for a connected system
For XI3: Promotion & Version Management runs on top of the BI Platform. It comes as an addon installer. For BI4: Promotion & Version Management is fully integrated into the BI Platform. For both versions no extra licensing required for this instance.
Public
10
Recommendation for a non-connected system (airgap)
Public
11
Why a dedicated system is recommended Why a dedicated system?
Promotion Management is really a production system It stores rollback content from a production environment, which could be critical if a rollback is required in your Production system. With the Version Management System, it contains the versioning and an audit trail of your BI content allowing that content to be re-promoted or old content recovered. Could be critical to meet compliance regulations. Avoids potential issues when promoting content the Promotion job owner does not have access to. Its really like any other production environment:
Need to back up the system The rollback content is stored as instances in the output File Repository Server The versioning of content is stored in version management, so you must also back up the version management database.
Public
12
Why a dedicated system is recommended Additional benefits of a dedicated Promotion Management System
Allows for a refresh of Development and Test from Production without losing any Promotion Management-specific data. Allows for decoupling of software releases between Promotion Management and other environments.
For example, you can patch just Promotion Management without affecting Production. Allows the Promotion Management Server to be upgraded without necessarily upgrading Production. This could be important, for example, you may wish to upgrade Test before Production, but to be supported, you also need to upgrade the Promotion Management Server.
Public
13
Mappings & Overrides
Overview of Mappings When a connection is promoted from one environment to the other, then the datasource connection needs to be updated accordingly. We call this connection overrides. Connection overrides include:
Universe connections Query as Web Service connections Crystal Reports direct to data connections
Public
14
Overview of BI4 Validation

Check services
Promotion Management Role
Needs to have an Adaptive Job Server and an Adaptive Processing Server containing the services shown. Only one active Lifecycle Management Service per cluster is supported. This is because this service uses a file-based database for holding over-ride connections, and only one service can be accessing that file-based database at any one time. The location of the file-based database is specified in the CMC Applications Promotion Management.
Public
15
Lifecycle Management EGI
How to install, configure, and use Promotion and Version Management (LCM) by means of Expert Guided Implementation (EGI) http://service.sap.com/sap/support/notes/1791078 Enterprise Support Academy http://service.sap.com/esacademy
Public
16
Expert Guided Implementation Promotion and Version Management (LCM) Day 1

Empowering lesson
SAP Expert presents Why and What is Promotion and Version Management High Level architecture
(Web session, 2 h. in the morning)
Day 2
Empowering lesson
SAP expert provides overview of installation, configuration, and validation
Day 3
Empowering lesson
SAP expert explains details of How Promotion by ID operates Promotion security Best practice workflows Mappings Features by product version
Execution by customer
Check Prerequisites Decide the most appropriate architecture
Installation, configuration, and validation. Simple exercises to improve functional understanding of the product set.
(Remote support in the afternoon)
Possible synchronization of repositories Setup and testing of mappings Practice promoting content following best practice.
Goal of the day

Ready for installation and configuration
Goal of the day

Software installed and configured
Goal of the day

Further understanding in best practice Environment becoming ready for use
Public
17
Expert Guided Implementation Promotion and Version Management (LCM) Day 4

Empowering lesson
SAP Expert explains Visual difference Promotion and Version Management security Delegated administration Rollback, other best practices, SubVersion backup/upgrade and manual install Command line use of Promotion Management Troubleshooting
(Web session, 1 h-2 h. in the morning)
Visual difference testing Application and functional security setup Rollback and other settings Test of SubVersion backup
Goal of the day

Promotion and Version Management Setup complete and ready for to be used. Best Practice understood.
Public
18
Thank you
Public
20

openSAP BIFOUR1 Week 2 Installation Upgrade Promotion PDF

Hochgeladen von

Dokumentinformationen

Originalbeschreibung:

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

openSAP BIFOUR1 Week 2 Installation Upgrade Promotion PDF

Hochgeladen von

Copyright:

Verfügbare Formate

Week 2 Unit 1: Installation

BI 4.x Products and Components

2013 SAP AG. All rights reserved.

BI 4.x Server Installation Tips

2013 SAP AG. All rights reserved.

BI 4.x Server Installation Tips

2013 SAP AG. All rights reserved.

BI 4.x Server Installation Tips

Make note of CMS Cluster Key and important user passwords

Ensure the installation directory meets requirements

2013 SAP AG. All rights reserved.

BI 4.x Server Installation Tips

Install user must be a member of Local Administrators Group

2013 SAP AG. All rights reserved.

BI 4.x Server Installation Tips

Install Required Libraries

Install Required Utilities Set locale settings

Dont use root user for install Set ULIMIT to Unlimited

BI 4.x Server Installation Tips

Check Kernel Parameters on Suse Linux

2013 SAP AG. All rights reserved.

Business Intelligence Pattern Books:

Business Intelligence Platform Installation Guide (UNIX):

Business Intelligence Platform Installation Guide (Windows):

2013 SAP AG. All rights reserved.

Contact information: open@sap.com

2013 SAP AG. All rights reserved.

2013 SAP AG. All rights reserved.

Week 2 Unit 2: Configuration

BI 4.x Server Configuration Tips

2013 SAP AG. All rights reserved.

BI 4.x Server Configuration Tips

Update Web Services Access URL

Set the Open Document Processing Settings

2013 SAP AG. All rights reserved.

BI 4.x Server Configuration Tips

Update the cluster name using CCM or serverconfig.sh

To make web applications cluster aware update the PlatformServices.properties file

2013 SAP AG. All rights reserved.

BI 4.x Server Configuration Tips

Update Java Options for Tomcat

Set Tomcat Garbage Collector

2013 SAP AG. All rights reserved.

BI 4.x Server Configuration Tips

Reserve a port range to be used for BI to communicate through the firewall

Bind each BI service to a specific port

2013 SAP AG. All rights reserved.

BI 4.x Server Configuration Tips

Exclude the Tomcat web application directory from AntiVirus

2013 SAP AG. All rights reserved.

Single Server Deployment

2013 SAP AG. All rights reserved.

Also known as Scale Out

Primary use case for redundancy and fault tolerance

Web Connector (e.g. AJP 13)

Web Application Server

2013 SAP AG. All rights reserved.

Horizontal and Vertical Scaling

Hardware Load Balancer

Web Server Farm

Application Server Cluster (Session Replication)

2013 SAP AG. All rights reserved.