Lifecycle Management in XI 3.1 Manage promotion of BI ... · Business Objects Enterprise...

Lifecycle Management in XI 3.1Manage promotion of BI content in a way that is robust,repeatable, reliable, and auditable

Rob Rohloff, Senior Sales Consultant, OEMDecember 3, 2008

© SAP 2008 /

1. What is Lifecycle Management?2. Introducing BusinessObjects Live Cycle Manager 3.13. Product Overview4. Best Practices5. Conclusion

Agenda

© SAP 2008 /

Why Is Life-Cycle ManagementImportant?

Regulations such as Sarbanes Oxley and HIPPA require a new level of rigor

Internal controls are required for:How changes are madeWho can access production systems

Reports need to be correct and on timeMinimal downtimeChanges to system, data or processes must be thoroughly tested

Sensitive data must be protected

For many, BI has become mission critical

© SAP 2008 /

Benefits of Life-Cycle Management

Reduce costsAvoid errorsAvoid reworkAvoid system downtime

Increase SecurityProtect against errors and mistakesProtect against malicious actsSafeguard information

© SAP 2008 /

Basic Principle - Separation

DevelopmentDevelop reports

TestValidate reportsTest securityTest software (fixpacks, service packs)

ProductionVerify changes

© SAP 2008 /

1. What is Lifecycle Management?2. Introducing BusinessObjects Live Cycle Manager 3.1

2.1. Improvements over Import Wizard2.2. Limitations2.3. Architecture2.4. LCM, Import Wizard, Federation Differences

3. Product Overview4. Best Practices5. Conclusion

Agenda

LifeCycle Manager Overview

Web-based tool that enables you to...Promote BI resources from one system to another system without affecting the dependenciesof these resourcesManage dependencies of BI resourcesManage different versions of BI resourcesRoll back a promoted resource to restore the destination system to its previous state

Note: The same version of BusinessObjects Enterprise must be installed on both the sourceand destination systems.

© SAP 2008 /

BusinessObjects LifeCycle Manager

Primary life-cycle management tool for XI 3.1 and later

Stand-alone web applicationWill eventually be another tab in the CMC

No additional licensing requiredAvailable now at SAP Service Marketplace (SMP)

© SAP 2008 /

Improvements over the ImportWizard

Complete granular control over objects selected

Better insight into “What will happen?”Dependency managementThe ability to test promotions before processing

Auditing – “What did happen?”

Rollback

SchedulablePromotions can be scheduledRegular build processes can be set-up

Fully handles delegated administration

Easier integration with version management systems

Database connection overrides and mapping

© SAP 2008 /

Version 1 Limitations

English-only

Java-only

Requires a Windows serverHowever, as a web application, it can be used to manage any XI

Limited to BusinessObjects Enterprise 3.1 source and destination systems

LCM jobs are not visible in the CMC therefore you must be in the LCM admin tool tocreate and schedule jobs

Cannot use events to trigger jobs

Only supports objects in CMS repository. Doesn’t support:EIM (Data Services)Performance Optimization Applications (such as GRC)Performance Manager

PM Deployment Tool (PMDT) is still required

© SAP 2008 /

What LCM is Not Designed For

Back up

Disaster Recovery

Archiving

© SAP 2008 /

Architecture

Example Architecture

© SAP 2008 /

© SAP 2008 /

1. What is Lifecycle Management?2. Introducing BusinessObjects Live Cycle Manager 3.13. Product Overview

3.1. Administration Options3.2. Promotion Jobs3.3. Manage Dependencies3.4. Promotion3.5. Air Gap3.6. Version Control3.7. Rollback3.8. Version Control

4. Best Practices5. Conclusion

Agenda

LifeCycle Manager

Primary tool for promotion

Version control

XI 3.1 and greater

© SAP 2008 /

Promotion: “Transport content from like system to like system.”Typically Dev to Test to ProductionContent is primarily document templates and metadata and schedulesNot document instances

Import Wizard

For migration

For promotion until XI 3.0

© SAP 2008 /

Migration: “Transport and transform content from previous version to newer version”Content includes all previous object types

Federation

For replication

© SAP 2008 /

Replication: “Transport content from like production system to like productionsystem.”Content should go through development life cycle and intoproduction before it is replicatedContent includes document templates, metadata, schedulesCan include document instances

Comparison Summary

© SAP 2008 /

LifeCycle ManagerPromotion (3.1 and later)Templates and metadataVersion Control

Import WizardMigrationPromotion (until XI 3.0)

FederationReplicationSubset of content types

BusinessObjects LifeCycle Manager

© SAP 2008 /

Home page providesstatus of promotion jobs

Jobs can be organized andsecured by folders. Metadata is

stored in an instance of BOE.

Administration Options

© SAP 2008 /

Before you start, setAdministration Options

Administration OptionsManage Systems

© SAP 2008 /

Enables you to add andremove host systems

Administration OptionsRollback and Job Settings

© SAP 2008 /

Enables you to configurethe rollback process

Enables you to specifythe number of job

instances that can exist inthe LCM system

Administration OptionsAudit Log

© SAP 2008 /

A variety of events canbe audited

Audit Reporting

© SAP 2008 /

Who promoted change?When did the change take effect?What objects were successfully added

or modified?Which objects failed?

Administration OptionsSubversion Settings

© SAP 2008 /

Enables you to configure theSubversion parameters

Promotion and Job Defined

Promotion enables you to create or update info-objects in the destination system.

A job is a collection of info-objects that can be moved from one BusinessObjectsEnterprise deployment to another. It can also refer to a collection of related anddependent CUIDs that need to be promoted to the destination system.

© SAP 2008 /

Creating a New Promotion Job

© SAP 2008 /

Create a New PromotionJob

Creating a New Promotion Job

© SAP 2008 /

Promotion Job Window

© SAP 2008 /

Add objects to anew job

Adding New Objects to a Job

© SAP 2008 /

Browse and select allobject types – notjust documents

Manage Dependencies

© SAP 2008 /

After selecting objects,optionally check the

dependencies

Managing Dependencies enables you to select and manage the dependents of theinfo-objects in the job that you want to promote.

Manage DependenciesFilters

© SAP 2008 /

Here, we see aconnection is a

dependent of a universe

Objects can be filteredfor better analysis

Manage DependenciesRules

© SAP 2008 /

Rules allow for groups ofdependents to be selected(Similar to Import Wizard)

Promotion

© SAP 2008 /

After selecting objects,click Promote

Promotion

© SAP 2008 /

Once the promotion job isbuilt, it is ready for promotion.A variety of options can be set

PromotionMappings

© SAP 2008 /

Use Mappings to override:Universe connectionsCrystal Reports database infoQuery as a Web Service URLs

Mapping enables you to modify a source connection or URL in the source system tomatch with a dependency type that exists in the destination system.

PromotionUniverse Connection Mappings

© SAP 2008 /

A connection can be mappedto the appropriate connection

in the next environment

PromotionUniverse Connection Overrides

© SAP 2008 /

Or, the specific properties of auniverse connection can be

updated

PromotionCrystal Reports Overrides

© SAP 2008 /

Database connectioninformation for Crystal Reports

can be updated

PromotionQuery as a Web Service Overrides

© SAP 2008 /

The URL for the WSDL can beupdated

PromotionScheduling a Promotion Job

© SAP 2008 /

The promotion job can bescheduled using all the

standard scheduling options.

Allows for deploys to bescheduled for after hours

PromotionExternal Change Management ID

© SAP 2008 /

An external ID can be enteredhere and associated with

changes in audit log

PromotionSecurity Settings

© SAP 2008 /

The security associated withobjects can optionally be

promoted.

Best practice is to onlypromote security when

changes have been made -typically with a significantrevision of the application

Air Gap

When the source and destination systems are on different networks or are notconnected, the Air Gap feature facilitates promotion by allowing the users tocreate a BIAR file. This BIAR file can be used as a source in the destinationsystem for promotion. The BIAR file can be written to DVD or tape, and thenphysically moved to the destination system where it can be imported.

Note: The file extension for the LCM BIAR file is LCMBIAR. LCM BIAR files are notcompatible with Import Wizard BIAR files.

© SAP 2008 /

Rollback

© SAP 2008 /

We decide to rollbackVersion 5 of the Expense

Reporting application

Rollback enables you to restore the destination system to its previous state, after ajob is promoted. You can roll back an entire job or part of the job.

RollbackBest Practices

When a deploy issue is identified, can either:Fix issue in dev, and promote fix through life cycle, orRollback some or all of deploy to previous state

Rollback makes sense when:Scope of changes to be rolled back is largeChange must be reversed quicklyIssue is in production

Can rollback more than one set of changes, however:Each successive rollback increases complexityLess likely that the result will be predictable to end user

Best practice:Only rollback when absolutely necessaryAvoid rolling back more than one versionEnable it only for critical systems (there is a cost: disk space)

© SAP 2008 /

Version Control

Version Management enables you to manage different version of the same document.The LCM tool enables you to manage versions of resources that exist in theBusiness Objects Enterprise repository. Subversion, an open source versioncontrol system, is used to version control the resources.

Provided out of the box by Subversion 1.4.6Popular open source version control systemSubversion is installed on same server as LifeCycle ManagerOr, can reuse an existing instance of Subversion

Use file security to lock down access to Subversion so that LifeCycle Manager is theonly access point

Ensure that Subversion files are backed up

© SAP 2008 /

Best PracticesSystems

Implement a 3 system deployment methodologyDevelopmentTestProduction

Ensure consistency in OS and patch level between environmentsFreeze Test environment when testing patches and service packsIf not possible, then test patches and services in a distinct environment

Leverage virtualization to:Keep costs downEasily build and maintain multiple environments

© SAP 2008 /

Best PracticesImportance of Mirrored Environments

All objects must have the same CUID in each environmentCUIDs are the primary method of identifying relationships and dependencies*

(*Not exclusively, but if you follow this rule you will be safe)

If Dev and Test aren’t complete mirrors of Production:Do a complete refresh from Production

Do not use one system for two environmentsCopying objects will create a new CUID and break the model

© SAP 2008 /

Best PracticesPromotion Jobs

Organize promotion jobs in folder structure that mimics production folder structureAssign delegated admins as desiredUse a consistent naming convention for promotion jobs

Do not promote security if it hasn’t changedSecurity typically changes less often that content

Do not promote dependencies if they haven’t changedExample: universes will change less often than reports

If you need to rollback security changes – do a full rollback, not partial, to be safeThen adjust job and re-promoteReuse or copy a job to ensure that all objects moved to test are then moved to production

© SAP 2008 /

Conclusion

Create a robust life-cycle management process that leverages the principle ofseparate environments

LifeCycle Manager is a new tool that allows for promotions to be reliable, automatedand repeatable

LifeCycle Manager also provides a version control solution by embedding Subversion

© SAP 2008 /

© SAP 2008 /

Copyright 2008 SAP AGAll rights reserved

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 changedwithout prior notice.

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.

SAP, R/3, xApps, xApp, SAP NetWeaver, Duet, SAP Business ByDesign, ByDesign, PartnerEdge and other SAP products and services mentioned herein as well as their respective logos aretrademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned and associated logos displayedare the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.

The information in this document is proprietary to SAP. This document is a preliminary version and not subject to your license agreement or any other agreement with SAP. This documentcontains only intended strategies, developments, and functionalities of the SAP® product and is not intended to be binding upon SAP to any particular course of business, product strategy,and/or development. SAP assumes no responsibility for errors or omissions in this document. SAP does not warrant the accuracy or completeness of the information, text, graphics, links, orother items contained within this material. This document is provided without a warranty of any kind, either express or implied, including but not limited to the implied warranties ofmerchantability, fitness for a particular purpose, or non-infringement.

SAP shall have no liability for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use of these materials. This limitationshall not apply in cases of intent or gross negligence.

The statutory liability for personal injury and defective products is not affected. SAP has no control over the information that you may access through the use of hot links contained in thesematerials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages

Weitergabe und Vervielfältigung dieser Publikation oder von Teilen daraus sind, zu welchem Zweck und in welcher Form auch immer, ohne die ausdrückliche schriftliche Genehmigung durchSAP AG nicht gestattet. In dieser Publikation enthaltene Informationen können ohne vorherige Ankündigung geändert werden.

Einige von der SAP AG und deren Vertriebspartnern vertriebene Softwareprodukte können Softwarekomponenten umfassen, die Eigentum anderer Softwarehersteller sind.

SAP, R/3, xApps, xApp, SAP NetWeaver, Duet, SAP Business ByDesign, ByDesign, PartnerEdge und andere in diesem Dokument erwähnte SAP-Produkte und Services sowie diedazugehörigen Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und in mehreren anderen Ländern weltweit. Alle anderen in diesem Dokument erwähnten Namenvon Produkten und Services sowie die damit verbundenen Firmenlogos sind Marken der jeweiligen Unternehmen. Die Angaben im Text sind unverbindlich und dienen lediglich zuInformationszwecken. Produkte können länderspezifische Unterschiede aufweisen.

Die in diesem Dokument enthaltenen Informationen sind Eigentum von SAP. Dieses Dokument ist eine Vorabversion und unterliegt nicht Ihrer Lizenzvereinbarung oder einer anderenVereinbarung mit SAP. Dieses Dokument enthält nur vorgesehene Strategien, Entwicklungen und Funktionen des SAP®-Produkts und ist für SAP nicht bindend, einen bestimmtenGeschäftsweg, eine Produktstrategie bzw. -entwicklung einzuschlagen. SAP übernimmt keine Verantwortung für Fehler oder Auslassungen in diesen Materialien. SAP garantiert nicht dieRichtigkeit oder Vollständigkeit der Informationen, Texte, Grafiken, Links oder anderer in diesen Materialien enthaltenen Elemente. Diese Publikation wird ohne jegliche Gewähr, wederausdrücklich noch stillschweigend, bereitgestellt. Dies gilt u. a., aber nicht ausschließlich, hinsichtlich der Gewährleistung der Marktgängigkeit und der Eignung für einen bestimmten Zwecksowie für die Gewährleistung der Nichtverletzung geltenden Rechts.

SAP übernimmt keine Haftung für Schäden jeglicher Art, einschließlich und ohne Einschränkung für direkte, spezielle, indirekte oder Folgeschäden im Zusammenhang mit der Verwendungdieser Unterlagen. Diese Einschränkung gilt nicht bei Vorsatz oder grober Fahrlässigkeit.

Die gesetzliche Haftung bei Personenschäden oder die Produkthaftung bleibt unberührt. Die Informationen, auf die Sie möglicherweise über die in diesem Material enthaltenen Hotlinkszugreifen, unterliegen nicht dem Einfluss von SAP, und SAP unterstützt nicht die Nutzung von Internetseiten Dritter durch Sie und gibt keinerlei Gewährleistungen oder Zusagen überInternetseiten Dritter ab.

Alle Rechte vorbehalten.

Lifecycle Management in XI 3.1 Manage promotion of BI ... · Business Objects Enterprise...

Documents

Transcript of Lifecycle Management in XI 3.1 Manage promotion of BI ... · Business Objects Enterprise...