+ All Categories
Home > Documents > SAP First Guidance - BW on HANA 1 · SAP HANA comprises a system copy of your SAP NetWeaver BW...

SAP First Guidance - BW on HANA 1 · SAP HANA comprises a system copy of your SAP NetWeaver BW...

Date post: 30-Jun-2018
Category:
Upload: vokiet
View: 256 times
Download: 2 times
Share this document with a friend
34
SAP First Guidance SAP BW 7.3x/7.4 SAP Realtime Database Platform Applicable Releases: SAP NetWeaver BW 7.0x SP27/SP10 SAP NetWeaver BW 7.3x SP07/SP03 SAP NetWeaver BW 7.4 SP02 and higher External Use To reduce downtime in your production landscape, one of the recommended migration paths from SAP NetWeaver Business Warehouse (SAP NetWeaver BW) to SAP NetWeaver BW on SAP HANA comprises a system copy of your SAP NetWeaver BW system. The system copy procedure of SAP NetWeaver BW systems and landscapes is complex for a number of reasons however. There are a large number of configuration settings (such as connections and delta queue handling for data loading) and system copy scenarios of SAP NetWeaver BW (each with different landscape aspects) for example that have to be handled as part of every system copy, regardless of whether the system copy is part of the migration to SAP HANA or if you want to perform regular system copies of your SAP NetWeaver BW landscape. For more Information see Doc - http://scn.sap.com/docs/DOC-32414 SAP First Guidance - BW-PCA and BW Housekeeping usage
Transcript

SAP First Guidance

SAP BW 7.3x/7.4

SAP Realtime Database Platform

Applicable Releases:

SAP NetWeaver BW 7.0x SP27/SP10

SAP NetWeaver BW 7.3x SP07/SP03

SAP NetWeaver BW 7.4 SP02 and higher

External Use

To reduce downtime in your production landscape, one of the recommended migration paths from SAP NetWeaver Business Warehouse (SAP NetWeaver BW) to SAP NetWeaver BW on SAP HANA comprises a system copy of your SAP NetWeaver BW system. The system copy procedure of SAP NetWeaver BW systems and landscapes is complex for a number of reasons however. There are a large number of configuration settings (such as connections and delta queue handling for data loading) and system copy scenarios of SAP NetWeaver BW (each with different landscape aspects) for example that have to be handled as part of every system copy, regardless of whether the system copy is part of the migration to SAP HANA or if you want to perform regular system copies of your SAP NetWeaver BW landscape.

For more Information see Doc - http://scn.sap.com/docs/DOC-32414

SAP First Guidance - BW-PCA and BW Housekeeping usage

SAP First Guidance

SAP BW 7.3x/7.4

SAP Realtime Database Platform

Version 1.31

June 2014

© Copyright 2014 SAP AG. All 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 changed without prior notice.

Some software products marketed by SAP AG and its distributors

contain proprietary software components of other software vendors.

Microsoft, Windows, Excel, Outlook, and PowerPoint are registered

trademarks of Microsoft Corporation.

IBM, DB2, DB2 Universal Database, System i, System i5, System p,

System p5, System x, System z, System z10, System z9, z10, z9, iSeries,

pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390,

OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power

Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER,

OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS,

HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex,

MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and

Informix are trademarks or registered trademarks of IBM Corporation.

Linux is the registered trademark of Linus Torvalds in the U.S. and other

countries.

Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either

trademarks or registered trademarks of Adobe Systems Incorporated in

the United States and/or other countries.

Oracle is a registered trademark of Oracle Corporation.

UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open

Group.

Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame,

and MultiWin are trademarks or registered trademarks of Citrix Systems,

Inc.

HTML, XML, XHTML and W3C are trademarks or registered trademarks

of W3C®, World Wide Web Consortium, Massachusetts Institute of

Technology.

Java is a registered trademark of Sun Microsystems, Inc.

JavaScript is a registered trademark of Sun Microsystems, Inc., used

under license for technology invented and implemented by Netscape.

SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP

BusinessObjects Explorer, StreamWork, 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.

Business Objects and the Business Objects logo, BusinessObjects,

Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other

Business Objects products and services mentioned herein as well as their

respective logos are trademarks or registered trademarks of Business

Objects Software Ltd. Business Objects is an SAP company.

Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL Anywhere,

and other Sybase products and services mentioned herein as well as their

respective logos are trademarks or registered trademarks of Sybase, Inc.

Sybase is an SAP company.

All other product and service names mentioned are 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. No part of this

document may be reproduced, copied, or transmitted in any form or for

any purpose without the express prior written permission of SAP AG.

This document is a preliminary version and not subject to your license

agreement or any other agreement with SAP. This document contains

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. Please note

that this document is subject to change and may be changed by SAP at

any time without notice.

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, or other 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 of

merchantability, 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 limitation shall 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 these materials and does not

endorse your use of third-party Web pages nor provide any warranty

whatsoever relating to third-party Web pages.

SAP “How-to” Guides are intended to simplify the product implement-

tation. While specific product features and procedures typically are

explained in a practical business context, it is not implied that those

features and procedures are the only approach in solving a specific

business problem using SAP NetWeaver. Should you wish to receive

additional information, clarification or support, please refer to SAP

Consulting.

Any software coding and/or code lines / strings (“Code”) included in this

documentation are only examples and are not intended to be used in a

productive system environment. The Code is only intended better explain

and visualize the syntax and phrasing rules of certain coding. SAP does

not warrant the correctness and completeness of the Code given herein,

and SAP shall not be liable for errors or damages caused by the usage of

the Code, except if such damages were caused by SAP intentionally or

grossly negligent.

Disclaimer

Some components of this product are based on Java™. Any code change

in these components may cause unpredictable and severe malfunctions

and is therefore expressively prohibited, as is any decompilation of these

components.

Any Java™ Source Code delivered with this product is only to be used by

SAP’s Support Services and may not be modified or altered in any way.

Document History

Document Version Description

1.00 First external release initial/refresh use case

1.10 Corrections/additions, BW Housekeeping SPAU/SPDD

1.20 New Note Analyzer, BW-PCA updates/corrections

1.30 Adding BI-JAVA PCA usage

1.31 Corrections from workshop WDEUMH 06.2014

Typographic Conventions

Type Style Description

Example Text Words or characters quoted

from the screen. These

include field names, screen

titles, pushbuttons labels,

menu names, menu paths,

and menu options.

Cross-references to other

documentation

Example text Emphasized words or

phrases in body text, graphic

titles, and table titles

Example text File and directory names and

their paths, messages,

names of variables and

parameters, source text, and

names of installation,

upgrade and database tools.

Example text User entry texts. These are

words or characters that you

enter in the system exactly

as they appear in the

documentation.

<Example

text>

Variable user entry. Angle

brackets indicate that you

replace these words and

characters with appropriate

entries to make entries in the

system.

EXAMPLE TEXT Keys on the keyboard, for

example, F2 or ENTER.

Icons

Icon Description

Caution

Note or Important

Example

Recommendation or Tip

SAP First Guidance … database migration option (DMO) – BW on HANA

August 2014 3

Table of Contents

1. BW - Post Copy Automation use cases ............................................................................ 4

1.1 Application Preparation Steps ........................................................................................ 4

1.1.1 Note 1909597 (ZBW_HANA_MIGRATION_COCKPIT) .................................... 4

1.1.2 Note 1729988 (ZBW_HANA_CHECKLIST) ....................................................... 5

1.1.3 Check the Sizing of the HANA Database .......................................................... 6

1.1.4 Interaction of Housekeeping Tasks with BW-PCA ........................................... 7

1.1.4.1 Additional Housekeeping Tasks ................................... 8

1.2 New Note Analyzer for BW-PCA and Housekeeping .................................................... 9

1.3 Install the LVM Enterprise License for BW-PCA .......................................................... 12

1.3.1 Using BW-PCA for the initial copy case........................................................... 14

1.3.1.1 Preparation of the Initial Copy of BW ......................... 15

1.3.1.2 Post-Configuration of the Initial Copy of BW ............ 16

1.3.2 Using BW-PCA including delta queue cloning ................................................ 17

1.3.3 Using BW-PCA including a connected BI-JAVA system................................ 17

1.3.3.1 Check/Modify the existing ABAP UME ...................... 18

1.3.3.2 Preparing LM Automation Standalone 1.0 ............... 20

1.3.3.3 Using the JAVA-PCA tool for BI-JAVA ...................... 24

1.3.4 Using BW-PCA for the refresh copy case ...................................................... 29

SAP First Guidance … database migration option (DMO) – BW on HANA

August 2014 4

1. BW - Post Copy Automation use cases

1.1 Application Preparation Steps

For further information please visit the BW Application Lifecycle Management (ALM) Page

http://scn.sap.com/docs/DOC-7856#section14 and the Standard Guides located here:

http://help.sap.com/nwlvm#section3

1.1.1 Note 1909597 (ZBW_HANA_MIGRATION_COCKPIT)

Note 1909597 - SAP NetWeaver BW Migration Cockpit for SAP HANA

The ZBW_HANA_MIGRATION_COCKPIT UI consolidates several tools and programs for checking the

existing BW system prior to the migration to BW on HANA.

It will not automatically import the following programs; it is a UI which combines the functionality on one

screen.

SAP First Guidance … database migration option (DMO) – BW on HANA

August 2014 5

1.1.2 Note 1729988 (ZBW_HANA_CHECKLIST)

Note 1729988 - SAP NetWeaver BW powered by SAP HANA - Checklist Tool

Note 1729988 contain a comprehensive report which checks several system settings and objects to

ensure a smooth system migration.

However, as this Report is “read only”, it is only a check of certain areas in your existing BW System to

ensure the feasibility to migrate the Objects to BW on HANA.

Furthermore not all checks might be compatible with the descriptions of the following sections.

For Details see also the SCN Document - https://scn.sap.com/docs/DOC-40984

SAP First Guidance … database migration option (DMO) – BW on HANA

August 2014 6

1.1.3 Check the Sizing of the HANA Database

Note 1736976 - Sizing Report for BW on HANA

Run report /SDF/HANA_BW_SIZING to make sure that your available HANA appliance matches the

source system export.

This is only the case, if you use the BW-PCA option together with a Migration to BW on HANA

SAP First Guidance … database migration option (DMO) – BW on HANA

August 2014 7

1.1.4 Interaction of Housekeeping Tasks with BW-PCA

Note 1829728 - BW Housekeeping Task List

(contains manual steps ZNOTE_1829728_PRE_70x/ZNOTE_1829728_PRE_73x, and automated steps

applied with SNOTE)

The newly released Housekeeping Task List (Pre/Post Steps) allows you to automate mandatory tasks

prior to upgrade/migration with DMO to ensure the quality of the migration process.

Apply the Note and run the tasks in advance to ensure smooth implementation of the BW Housekeeping

Task List.

Note 1710719 - Corrections on SAPI-Tasks for System Copy Automation

Note 1767420 - Task Manager for Technical Configuration (6. Improvements)

Note 1810570 - Task Manager for Technical Configuration (7. Improvements)

If you are using the BW Housekeeping Task List SAP_BW_HOUSEKEEPING already before you start a

migration to BW on HANA or another BW system copy use case, you can work on the BW Housekeeping until the (e.g. with the DMO option) phase MAIN_INIT/REPACK_CLONE is reached.

To solve the problem with the endless loop on the last task and background scheduling, apply the

following Notes:

Note 1880465 - SAP_BW_HOUSEKEEPING not terminating

Note 1845061 - Background user has no authorization for scheduling

Note 1935301 - SNOTE tries to download SAP note 0000000000

SAP First Guidance … database migration option (DMO) – BW on HANA

August 2014 8

After an Upgrade to a higher release of the BW system follow the guide attached to the following Note:

Note 1928090 - Handle PCA SAP Notes for SPDD/SPAU comparison

1.1.4.1 Additional Housekeeping Tasks

These reports have not yet been added to the Task List, but as well essential reducing the size of the DB.

Note 706478 - Preventing Basis tables from increasing considerably

Delete Error Log: RSB_ANALYZE_ERRORLOG (check) and RSBM_ERRORLOG_DELETE (delete)

Delete Application Log: SLG1 (check) and SLG2 (delete)

Delete old Job Logs: Report RSBTCDEL2

Delete old Bookmarks: Report RSRD_BOOKMARK_REORGANISATION

Clean existing Roles: Report RSWB_ROLES_REORG

Clean Inconsistencies in RSZ* tables: Report ANALYZE_RSZ_TABLES

Synch entries in the nametab tables: Report RS_NAMT_CLEAR

Clean single runtime objects in nametab: FuBa DD_SHOW_NAMETAB/DD_NAMETAB_DELETE

Clean database entries and entries which are not in nametab: FuBa DDIF_OBJECT_DELETE

Repair secondary InfoCube Indexes: Report SAP_INFOCUBE_INDEXES_REPAIR

Check inconsistencies with shadow indexes from table partitions: Report RSDU_REPART_UI

On MSSQL check with Report RSDD_MSSQL_CUBEANALYZE any InfoCube Inconsistencies

Reorganize Table OCSCMPLOBJ (activate with delete data in SE14)

Note 889596 - UNICODE conversion: Deleting contents of OCSCMPLOBJ

Check Tables DWINACTIV_A and DWINACTIV for inactive customer objects

Transaction RSRT and RSTT delete old ABAPs and Traces

Transaction RSSGPCLA delete program class for

Template = RSRDUMMY, RSTMPLIR, RSTMPLDTPERR, RSTMPL81, RSTMPLDS

Transaction RSDDSTAT delete old statistical data

Transaction RSECADMIN delete old authorization logs

Note 1682783 - Generated programs are not deleted

Note 1634681 - Database migration: Report to find large row store tables (not available for 7.0x)

SAP First Guidance … database migration option (DMO) – BW on HANA

August 2014 9

In addition to the SAP_BW_HOUSEKEEPING task list, you can also implement the following Note for the

pre/post Upgrade and Migration task lists (up to NetWeaver 7.40)

Note 1905137 - FAQ: SAP HANA - Obsolete tables

Note 1734333 - BW Pre and Post Upgrade and Migration Tasks

Note 1786506 - Safe & fast Reset of OLAP Cache content

Note 1925451 - STC: Long Secure Content not usable in Task Manager

1.2 New Note Analyzer for BW-PCA and Housekeeping

Note 1614266 - System Copy: Post Copy Automation (PCA) / LVM

Contains the Program Code (Attachment) Z_SAP_NOTE_ANALYZER and the BASIS XML file

Note 1707321 - BW System Copy: Note analyzer Post Copy Automation (BW-PCA)

Contains the BW and SAPI XML file as Attachment

The higher the SP Level of the source system, the fewer the number of Notes that have to be

implemented during the preparation of the new Note Analyzer.

After the start of the program, there are two XML files to load depending on the BW-PCA scenario:

Basis and BW (which are also attached to the Note).

After you uploaded the two XML files additional options are visible in the New Note Analyzer.

SAP First Guidance … database migration option (DMO) – BW on HANA

August 2014 10

Loading “in dialog” allows you to see the detailed list of SAP Notes to implement prior to the usage of the

BW-PCA task list.

You have to implement/confirm the import of these SAP Notes before the Job SAP_PCA_NOTES_DOWNLAOD will come to an end.

Implement the latest version of the following collective SAP Notes for transaction SNOTE:

Note 875986 - Note Assistant: Important notes for SAP_BASIS up to 702

for SAP NetWeaver 7.00, 7.01, and 7.02

Note 1668882 - Note Assistant: Important notes for SAP_BASIS 730,731,740

for SAP NetWeaver 7.30, 7.31, and 7.40

SAP First Guidance … database migration option (DMO) – BW on HANA

August 2014 11

See the Result of the SAP Note Analyzer and proceed accordantly.

SAP First Guidance … database migration option (DMO) – BW on HANA

August 2014 12

1.3 Install the LVM Enterprise License for BW-PCA

Go to http://service.sap.com/installations and navigate to the Installation Package

The BW-PCA Installation Guide can be found here:

Note 1621867 - Installation of PCAI_ENT 100 and http://help.sap.com/nwlvm#section3

https://service.sap.com/~sapidb/011000358700000175442014E

For an initial system copy, install add-on PCAI_ENT 1.0 before the system copy on your production

system. For a system refresh, install add-on PCAI_ENT 1.0 before the system copy on your quality and

production system.

For the following SAP NetWeaver releases, use the archive K-100AGINPCAIENT:

SAP NetWeaver 7.00

SAP NetWeaver 7.01

For the following SAP NetWeaver releases, use the archive K-100BGINPCAIENT:

SAP NetWeaver 7.30

SAP NetWeaver 7.31

The Add-on PCAI_ENT 2.0 de-installs add-on PCAI_ENT 1.0 (all versions).

SAP First Guidance … database migration option (DMO) – BW on HANA

August 2014 13

Call the transaction SAINT in your ABAP system and follow the instructions on the screen to apply the

PCAI_ENT Rel. 100 Add-On.

Deinstallation of PCAI_ENT 100

The following packages have to be downloaded to perform a deinstallation with transaction SAINT:

SAPK-200AGINPCAIENTD for SAP_BASIS releases 700, 701, 702, 731, 740

o SAPK-200BGINPCAIENTD for SAP_BASIS releases 710, 711, 730

You need at least SPAM/SAINT version 0046.

Technically, both packages belong to software component version "PCAI_ENT 200"

SAP First Guidance … database migration option (DMO) – BW on HANA

August 2014 14

1.3.1 Using BW-PCA for the initial copy case

If you plan to copy your existing BW system first, to enable the (almost) continuous production

availability, the BW-PCA (post copy automation) is a required additional step.

The BW-PCA (for ABAP Basis and BW) Configuration Guide can be found here:

https://service.sap.com/~sapidb/011000358700000368892013E

http://help.sap.com/nwlvm#section3

https://service.sap.com/~sapidb/011000358700000368552013E

SAP offers the following predefined task lists for BW PCA using the task manager for technical configuration as standalone tool:

Preparation for Initial Copy of a BW System (SAP_BW_COPY_INITIAL_PREPARE)

Configuration for Initial Copy of BW/BW Source Systems (SAP_BW_BASIS_COPY_INITIAL_CONFIG)

Task lists are proprietary to SAP and can be overwritten during an upgrade. As with ABAP programs for

example, this will affect future executions of the task list only, It will not affect executions that were

started before the upgrade of the task list. If you want to preserve the current state of the task list, we

recommend saving SAP task lists as a copy prior to execution.

This graphic illustrates the overall process. The two main task lists will be explained as follows.

Step 1 runs in the system where the export of the system copy is started (see Chapter 1.3.2.1).

Task List - SAP_BW_COPY_INITIAL_PREPARE

Step 3 runs in the system which was created with SWPM in the target system (see Chapter 1.3.2.2) Task List - SAP_BW_BASIS_COPY_INITIAL_CONFIG If the BW-PCA task lists are used for the initial system copy, no additional preparation has to be made in the target system, such as manually stopping batch processes, killing reports and the like. Simply run the task list via transaction STC01

SAP First Guidance … database migration option (DMO) – BW on HANA

August 2014 15

1.3.1.1 Preparation of the Initial Copy of BW

The new task list - SAP_BW_BEFORE_MIGRATION also checks several areas and runs report

SMIGR_CREATE_DDL for the BW-specific objects prior to the export. You can then run the task list -

SAP_BW_COPY_INITIAL_PREPARE. After this, you can export the system with the SWPM.

SAP First Guidance … database migration option (DMO) – BW on HANA

August 2014 16

1.3.1.2 Post-Configuration of the Initial Copy of BW

Go to transaction STC01 and proceed with the task list - SAP_BW_BASIS_COPY_INITIAL_CONFIG

It is suitable, that you run the task list with transaction STC02 to avoid several restarts of the same run.

SAP First Guidance … database migration option (DMO) – BW on HANA

August 2014 17

1.3.2 Using BW-PCA including delta queue cloning If you also want to clone the delta queues from the connected source systems the automated scenario looks as follows:

The mentioned tasks lists are reflecting this case as well.

1.3.3 Using BW-PCA including a connected BI-JAVA system Also the case with a connected BI-JAVA system is supported as well with the JAVA-PCA tool.

SAP First Guidance … database migration option (DMO) – BW on HANA

August 2014 18

1.3.3.1 Check/Modify the existing ABAP UME

When you import a SAP JAVA system copy which was connected to a BW Backend before, which was not

the same source, you must correct the ABAP UME Provider to enable the correct start of the BI-JAVA

system prior to the usage of the LM Automation Landscape Automation.

Start the offline configtool on the BI-JAVA server where your copy is installed with SWPM.

Accept the default DB settings …

Switch to the configuration editor mode …

SAP First Guidance … database migration option (DMO) – BW on HANA

August 2014 19

Drill down to the PropertySheet „UMEBackendConnection“

Change the needed system settings to the correct ABAP UME of your used system now.

SAP First Guidance … database migration option (DMO) – BW on HANA

August 2014 20

Nevertheless you will need the existing BI-JAVA users with the correct passwords (from previous system)

created and working in your ABAP UME source.

J2EE_ADM_<SID>

SAPJSF

J2EE_GUEST

1.3.3.2 Preparing LM Automation Standalone 1.0

Note 1891353 - Standalone Task Manager for LM Automation 1.0

Note 1568545 - SAP Release Note for SL Toolset 1.0 SPS02

The LM Automation Standalone 1.0 Infrastructure executes configuration tasks in an automated way and

guides you through configuration processes, e.g. the post copy steps for a BI-JAVA system copy

connected to your NetWeaver BW System.

It does not require an SAP NetWeaver Java Engine as runtime - instead, the tool comprises an SAP JRE,

so you can completely run it self-contained.

Download the necessary software components beforehand (for Version Win64):

A (SAP) JAVA Virtual Machine, e.g. SAPJVM7_18-10010941.SAR

SAP JCo 3.0 Drivers for WinX64, e.g. sapjco30P_10-10005326.zip

The LM Standalone Automation 1.0 Kit, e.g. TMLMAUTO00P_3-10013151.ZIP

The Adobe Flash Player for IE, e.g. install_flash_player_12_active_x.exe

Optional: The updated JAVA-PCA content, e.g. JAVAPCA_1-20011792.zip

Optional: the vcredist_x64.msi Package (included in the SAPJVM7 SAR file)

SAP First Guidance … database migration option (DMO) – BW on HANA

August 2014 21

SAP First Guidance … database migration option (DMO) – BW on HANA

August 2014 22

The JAVA-PCA Guide can be found here:

https://service.sap.com/~sapidb/011000358700000364502013E

Now you can setup/build the LM Automation Landscape with these components on a Windows x64

Server. If the SAP JAVA Instance is running on Windows x64, you can directly build the JAVA-PCA here.

Create a directory of your choice, e.g. D:\usr\sap\JAVA-PCA and unpack the SAR/ZIP files here.

Create a “kind of Directory Structure” like (the components must reside in its own directory):

D:\usr\sap\JAVA-PCA\SAPJVM7

D:\usr\sap\JAVA-PCA\sapjco

D:\usr\sap\JAVA-PCA\TMLMAUTO

SAP First Guidance … database migration option (DMO) – BW on HANA

August 2014 23

sapcar.exe -xvf R:\JAVA-PCA\SAPJVM7_18-10010941.SAR

Set the JAVA_HOME Variable (for SAPJVM7) to D:\usr\sap\JAVA-PCA\sapjvm_7

Set the PATH Variable (for SAP SAPJVM7/JCo 3.0) to

D:\usr\sap\JAVA-PCA\sapjco; D:\usr\sap\JAVA-PCA\sapjvm_7\bin

Set the CLASSPATH Variable (for SAP JCo 3.0) to D:\usr\sap\JAVA-PCA\sapjco\sapjco3.jar

Apply the ADOBE Flash Player for MS IE

Start the file lmauto.bat

SAP First Guidance … database migration option (DMO) – BW on HANA

August 2014 24

Provide a password for the user lmauser

1.3.3.3 Using the JAVA-PCA tool for BI-JAVA

Import the latest LM Automation Content as follows:

Use the path D:\usr\sap\JAVA-PCA\TMLMAUTO\content\plugins

were you copied the patches for JAVA-PCA 2.0 coming from the file JAVAPCA_1-20011792.zip

SAP First Guidance … database migration option (DMO) – BW on HANA

August 2014 25

Start the JAVA post copy automation via the “Start” Button

Select the necessary post automation steps

SAP First Guidance … database migration option (DMO) – BW on HANA

August 2014 26

Continue with instructions on the screen.

SAP First Guidance … database migration option (DMO) – BW on HANA

August 2014 27

Example Input and Feedback as follows:

SAP First Guidance … database migration option (DMO) – BW on HANA

August 2014 28

SAP First Guidance … database migration option (DMO) – BW on HANA

August 2014 29

1.3.4 Using BW-PCA for the refresh copy case

If you plan to refresh one of your existing BW systems, you can use the refresh copy case from the BW-

PCA option.

The BW-PCA (for ABAP Basis and BW) Configuration Guide can be found here:

https://service.sap.com/~sapidb/011000358700000368892013E

http://help.sap.com/nwlvm#section3

https://service.sap.com/~sapidb/011000358700000368552013E

SAP offers the following predefined task lists for BW PCA using the task manager for technical configuration as standalone tool:

Preparation for Initial Copy of a BW System (SAP_BW_COPY_INITIAL_PREPARE)

Configuration of the refresh Copy of BW/BW Source Systems (SAP_BW_BASIS_COPY_REFRESH_CONFIG)

Note 1780190 - SAPI Corrections for System Copy Automation- Refresh Usecase

(contains manual report ZSAP_BW_BASIS_COPY_REFRESH_CONFIG, and automated steps applied with

SNOTE)

To keep the settings for the connected Enterprise Portal (BI-JAVA) apply the Note in advance

Note 1840800 - Retain connected Portal settings in BW system after refresh

Note 1837094 - Task list with CL_RSO_DELTA_QUEUE_CLONE hangs up in STC02

Note 1894679 - Avoiding the conversion of BW DataStores by BDLS

SAP First Guidance … database migration option (DMO) – BW on HANA

August 2014 30

Also the complex use case with connected source systems and BI-JAVA is supported.

Finally five automated task lists for system copy of BW landscape are available to fulfill the use cases.

www.sap.com/contactsap

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


Recommended