Upgrade_Migrate Your Custom Development Projects to SAP NetWeaver 7.3 - Webinar Presentation

7/22/2019 Upgrade_Migrate Your Custom Development Projects to SAP NetWeaver 7.3 - Webinar Presentation

1/54

KHNC

Upgrade / Migrate your

Custom Development projects to

SAP NetWeaver 7.3

Claudia PachecoSAP Technology RIG Americas

Material Prepared by

Marc Chan, SAP Technology RIG APJ

Angel Dichev, SAP Custom Development

Makoto Sugishita, SAP Technology RIG Japan

Kenichi Unnai, SAP Technology RIG Japan


2/54

2010 SAP AG. All rights reserved. / Page 2

Disclaimer

This presentation outlines our general product direction and should not be relied on in making a

purchase decision. This presentation is not subject to your license agreement or any otheragreement with SAP. SAP has no obligation to pursue any course of business outlined in this

presentation or to develop or release any functionality mentioned in this presentation. This

presentation and SAP's strategy and possible future developments are subject to change and

may be changed by SAP at any time for any reason without notice. 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. SAPassumes no responsibility for errors or omissions in this document, except if such damages

were caused by SAP intentionally or grossly negligent.


3/54


Agenda

1. Overview2. Server Upgrade

3. Development Infrastructure

4. Web Dynpro for Java

5. Composite Application Framework (CAF)

6. Visual Composer (VC)

7. Guided Procedures (GP)

8. J2EE / Java EE 5

9. Summary


4/54


OverviewSAPs Java App. Server and Development Environment

SAP Web

Application

Server 6.40

SAP

NetWeaver

ApplicationServer 7.0x

J2EE 1.3 based J2EE 1.4 / Java EE 5 based

Java Server based on J2EE 1.3 (JDK 1.4)

NetWeaver Developer Studio (NWDS)

based on Eclipse 2.x

Java Server supports J2EE 1.4 and Java EE 5

(JDK 5 / 6)

NetWeaver Developer Studio (NWDS) based on

Eclipse 3.x

SAP

NetWeaver CE

7.1

SAPNetWeaver CE

7.1 EhP1

SAP

NetWeaver CE

7.2

SAP

NetWeaver

7.3


5/54


OverviewUpgrade / Migration paths

SAP Web

Application

Server 6.40

SAP

NetWeaver

ApplicationServer 7.0x

SAP

NetWeaver CE

7.1

SAPNetWeaver CE

7.1 EhP1

SAP

NetWeaver CE

7.2

SAP

NetWeaver

7.3

J2EE 1.3 based J2EE 1.4 / Java EE 5 based

No direct server

upgrade, migration

always required

Server upgrade available.

Project migration only

required for specific types

and maintenance

EhP installation only.

No migration required


6/54


Matrix MapFor projects from these versions to NetWeaver 7.3

WDno

foJa

C V G JE

JaE5

BM

Web AS6.40

NW 7.0x

CE 7.1CE 7.1EhP1CE 7.2

Migration is

necessary to have

the project run in

NW 7.3

Apps can run on

NW 7.3 witho ut

migrat ion

Design time

migrat ion may be

needed for project

maintenance on NW7.3

Not applicable for

th is version

This lecture

mainly focus

on this


7/54


Agenda







8. J2EE / Java EE 5

9. Summary


8/54 2010 SAP AG. All rights reserved. / Page 8

Tool for UpgradeSAPJupJava server upgrade from NetWeaver 7.0x to 7.3

SAPJup

SAP Java Upgrade Tool for users to upgrade the Java

Application Server

Is shipped to customers in a separate DVD called Upgrade

Master DVD

Upgrade Process with SAPJup1. Initialization Detects system type: ABAP + Java / Java only

2. Extraction Extract upgrade tools from Upgrade Master DVD

3. Configuration Gather info including passwords, software

units, add-ons, SP, shadow system info, etc...

4. Checks Validate OS and DB of the source release to match

the requirements of the target release5. Pre-processing Builds up the shadow sys tem

6. Downtime System down for unattended upgrade execution

7. Post-processing Remove the shadow schema created

8. Finalization Clean-up files and directories that are no longer

required after the upgrade



Standard Schema

Container Tables 7.0CM

PCD

WDP

DDIC

Application Tables 7.0

APP1 APP2 APP3DBI

nstance

Shadow Tables 7.3

SHD CM

SHD PCD

SHD WDP

SHD DDIC

Shadow Schema

Shadow Table Aliases 7.3

CM

PCD

WDP

DDIC

Shadow SystemMinimize downtime by upgrading on a mirror schema

Overview

Shadow system is created during the upgrade process

Installation and update of server components and applications are being done on the shadow

system

During the process, the Standard System is still fully operational (until reaching the downtime step)

As a result, it enables a system switch type of upgrade


APP1 APP2 APPX3

Core Layer Containers (Web, EJB, etc.)

Portal Runtime Container

WebDynpro Container

DB Schema & Content Container

J2EE Appl. Archive (.EAR)

Web Archive (.WAR)

Portal Archive (.PAR)

SDA of type JDDSCHEMA, DBSC

Shadow System 7.3SCA



Standard Schema


PCD

WDP

DDIC


APP1 APP2 APP3DBI

nstance

Shadow Tables 7.3

SHD CM

SHD PCD

SHD WDP

SHD DDIC

Shadow Schema

Shadow Table Aliases 7.3

CM

PCD

WDP

DDIC

Migration ControllerEnable custom apps to run after the upgrade

Overview

Migration Controllers migrate customer modifications from the source release tables to the shadow tables

Ensure custom applications (of supported types) continue to run on the target system after the upgrade

Service Configuration Migration Controllers

Container Data Migration Controllers

PCD Migration Controllers

UME Migration Controllers

Migration Controllers

DDIC Migration Controllers


APP1 APP2 APPX3



Standard Schema


PCD

WDP

DDIC


APP1OLD APP2 APP3DBI

nstance

Schema SwitchA post-processing and finalization process

Overview

Shadow schema is dropped. Show Tables in the Standard Schema will be renamed as the ContainerTables. System switches back to operate on the Standard Schema.

DB schemas and Content archives are redeployed to adapt to the structure in the target release.

All application tables are adapted to the target release structure, and contain the original customer data.

APPX3APP1



Agenda







8. J2EE / Java EE 5

9. Summary



Required SCs

Track for 7.0

Overview of Track migrationDifference between 7.0 and 7.3

Required SC

Track for 7.3

Inbox of the

new track

Download tothe target

track inbox

Check in after

downloading

from SAP

Service

Marketplace

CAF apps: Application Services and custom code are not migrated automatically. We recommend that you dont delete the existing

SAP NW 7.0 track before ensuring you have successfully migrated the custom code manually.



Migration ProcedureStep 1: Assemble and Export the SC from 7.0

Assemble the SCs in which your development resides in 7.0 track

Export the SCs locally to the location of the new versions inbox of CMS



Migration ProcedureStep 2: Create the track in 7.3

If you create the new track on 7.3 system, the newConfiguration Template in NWA is the easy choice

To modify SCs delivered by SAP (ex. ESS/XSS), use this wizard

You can manually create a new 730 track (in a traditional style),

but



Migration ProcedureStep 3: Configure the Build Variants for the track

7.0 (including

EHPs) 1.4.2

7.1 (including

EHPs)5 5

7.2 6 6

7.3 6 6

SAPNetWeaverRelease

SAP JVMRelease JDK version

Make sure the track is using a proper JDK

version you can configure it by ConfigTool



Migration ProcedureFinal Step

Import your SCs and required SCs in the new

track in NetWeaver 7.3

More detail availab le at SAP Note #1457908



Agenda







8. J2EE / Java EE 5

9. Summary


19/54



Migration OverviewMigrating a Web Dynpro project from NW 7.0x to NW 7.3

Overview

Complete migration of Web Dynpro Java application

written for SAP NetWeaver 7.0 is not mandatory. In SAP

NetWeaver CE 7.1 and higher there is source code

compatibility of Web Dynpro Java applications but not

binary compatibility. This means that the old source

code must be imported, re-compiled, and redeployed tothe new system.

Applications created in or migrated to NetWeaver CE 7.1

or later are binary compatible to newer versions in that

series. You can directly deploy an application built for

CE 7.1 on a 7.3 runtime.

A Migration Wizard is provided and triggered behind

the scene to adapt your projects in the new environment

during the migration process.



Migration ProcedurePrerequisites and Pre-process

Prerequisites for migration The Web Dynpro Java project to be migrated is in a

DC (either in a Development Track with NWDI or as a

Local DC)

If it is not a DC, during the import process NWDS 7.3

will prompt whether to convert it to a DC. You need to

choose yes to proceed with the migration.

If you are using NWDI

Make sure you have already migrated the Track

containing your Web Dynpro DCs from the SAP

NetWeaver 7.0x to SAP NetWeaver 7.3.

SAP NetWeaver Developer Studio for NetWeaver 7.3has been installed

SAP NetWeaver Developer Studio 7.3 has been

configured to use the Track created for NetWeaver

7.3 development.



Migration ProcedureStep 1: Importing Web Dynpro DCs

Project Import and Migration Wizard

During the import of the DCs in SAP NetWeaver Developer Studio (NWDS), a Migration Wizard istriggered behind the scene to automate the process and adapt the application to the new environment.

Below shows the importing procedures in 2 scenarios:

For DCs in NWDI

In NWDS, open Component Browser view in the

Development Infrastructure perspective Select the DCs and choose Sync / Create Project

Create Project to download the sources to you

workspace

For Local DCs

Copy the local SC folder from the 7.0 to 7.3 workspace.

In NWDS 7.3, open the Development Infrastructureperspective and refresh the local SC youve copied.

Select the DCs in the SC and choose Sync / Create

Project Create Project

After the Migration Wizard complete

A migration summary will be provided showing theoverall status of the migration as well as the detail.

You can examine each problem / warning in the

Problems view. To fix the problem / warning, right click

on the message and choose Quick Fix.



Migration ProcedureStep 2: OptionalMigrate Web Dynpro Components

Introduction

There are some architectural changes in Web Dynpro forJava starting from NetWeaver CE 7.1.

These changes are source compatible. Existing Web

Dynpro projects will run in NetWeaver 7.3 without extra

migration steps as long as it is rebuilt, re-archived and

redeployed.

All the migrations processes mentioned in this step are

therefore optional.

SAP does not recommend to migrate the Web Dynpro

Components by default. Users should consider this step

only when it is really required for the future maintenance of

the project.

Changes Overview (starting from NetWeaver CE 7.1) Interface View Controllers and Interface Controllers are no

longer used from NetWeaver CE 7.1.

A new Local Component Interface Definition is introduced.

Window Controllers replace former Component Interface

Controllers

In NetWeaver 7.0

In NetWeaver CE 7.1 or later



Migration ProcedureStep 2: OptionalMigrate Web Dynpro Components (cont)

Migration Overview

An existing Web Dynpro Component should only be

migrated to the new component model in specific

cases. Examples of these cases are shown.

A semi-automated tool called Component Migration

Tool is provided but keep in mind certain manual

processes are always required.

Migration Process

A Web Dynpro component which is not migrated is

shown in gray in NWDS.

Right click on the Web Dynpro component and choose

Migrate The Component Migration Tool opens a Cheat Sheet

which guides you through the migration with

instructions.

Mandatory Migration Cases:if your existing Web ynpro componentmust implement a new standalone CID utilizing

new functions

must use CID, which is only supported in the new

component model.

must support the generic Secondary Help service



Migration CompleteFinal Step and Noteworthy Info

Final Step: Deploy and Run

As explained, Web Dynpro for Java is sourcecompatible.

To run an existing / migrated Web Dynpro project in

NetWeaver 7.3, you will need to rebuild, re-archive and

redeploy it to the NetWeaver 7.3 server.

Noteworthy Info Be reminded of the side effects when deciding to

migrate a Web Dynpro Component

Be reminded of the behavioral differences in design time

and runtime between different versions

Examine the list of deprecated UI elements when

designing your user interface Info for the above can be found in the Online Help for

NetWeaver 7.3.

Info for deprecated APIs are shown in the corresponding

JavaDoc


26/54

DemoDEMOMigrating a Web Dynpro for Java project


27/54


Agenda







8. J2EE / Java EE 5

9. Summary


28/54


Upgrade or Migrate?For projects from these versions to NW 7.3

WDno

foJa

C V G JE

JaE5

BM

Web AS6.40

NW 7.0x


Migration is

necessary to have

the project run in

NW 7.3

Apps can run on

NW 7.3 witho ut

migrat ion

Design time

migrat ion may be

needed for project


Not applicable for

th is version


29/54


Migration OverviewMigrating a CAF Project from NW 7.0x to NW 7.3

Overview

Entity Service from NetWeaver 7.0 can be migrated with

a Migration Wizard in NWDS 7.3.

The rest of the CAF objects need to be migrated

manually.

Some objects / features are not available in NetWeaver

7.3

Runtime migration for the business entity service

(business data) is provided as part of Java Upgrade

Process (JUP).


30/54


Migration ProcedureImporting CAF DCs

Project Import and Migration Wizard

During the import of the DCs in SAP NetWeaver Developer Studio (NWDS), a Migration Wizard istriggered behind the scene to automate the process and adapt the application to the new environment.

Below shows the importing procedures in 2 scenarios:

For DCs in NWDI

In NWDS, open Component Browser view in the

Development Infrastructure perspective

Select the DCs and choose Sync / Create Project

Create Project to download the sources to you

workspace

Choose cancel if you are asked to migrate EJB/EAR/WD

project,

Create project for metadata and migrate after the other

projects are created.

For Local DCs

In NWDS, copy files from .dtc\LocalDevelopment\DCs\

To \workspace.jdi\LocalDevelopment\DCs\

In Development Infrastructure perspective, refresh and

choose Sync/Create Project -> Create Project

Choose cancel if you are asked to migrate EJB/EAR/WD

project,

Create project for metadata and migrate after the other

projects are created.

After the Migration Wizard complete

A migration summary will be provided showing the overall

status of the migration as well as the detail.


31/54


Migration ProcessWith Migration WizardEntity Service to Business Object Node

Reminder: Runtime Configuration

SAP NetWeaver 7.3 does not have a concept

analogous to the runtime configuration like

Business rule, Dynamic Attribute, Custom

Type Enumerations.

NetWeaver 7.0

/caf->Administrative Tools

Design Time objects

Entity Services are automatically converted tobusiness object nodes after design time

migration.

Each multiple attribute is converted to a new

business object node with a multiple association

to it.

The mappings to external services is not migrated

and needs to be mapped again manually.

NetWeaver 7.0

NetWeaver 7.3

Reminder: Runtime Data

Runtime data of Entity Services (Business

Object Node in 7.3) are migrated through

Upgrade process from 7.0 to 7.3 server.


32/54


Migration ProcessManual ProcessApplication Service, External Service and other objects

Application Services

They have to be modeled manually from scratch and the custom codere-implemented using the CAF tools provided by NWDS 7.3.

External Services

They have to be re-imported manually in the migrated project.

Both ways of using imported external services are possible

using mappings

direct invocation

The direct invocation in SAP NetWeaver 7.3 is implemented using the

automatic mappings (as opposed to generated proxies).

Other CAF Objects

In NW 7.3, there is no equivalent objects / features for the itemsbelow from NW 7.0. You need to implement the features in different

ways

Classifications can be re-implemented on the application side

Use EJB/Web service model for Web Dynpro Model

Guided Procedures Integration through web service

TREX Integration can be implemented by using TREX API directly


33/54

DemoDEMOMigrating a CAF project

A d


34/54


Agenda







8. J2EE / Java EE 5

9. Summary

U d Mi t ?


35/54



WDno

foJa

C V G JE

JaE5

BM

Web AS6.40

NW 7.0x


Migration is

necessary to have

the project run in

NW 7.3

Apps can run on

NW 7.3 witho ut

migrat ion

Design time

migrat ion may be

needed for project


Not applicable for

th is version

O i


36/54


OverviewMoving a VC project from NW 7.0x to NW 7.3

Upgrade Option

If you are only interested in running your VC project

developed in NetWeaver 7.0x on NetWeaver 7.3, you do

not need migration.

The standard upgrade procedure will automatically move

your VC application at runtime and do not require manual

migration of the application source code.

Migration Option Design time migration is required if:

You will continue the development / maintenance of

your VC projects on NetWeaver 7.3.

A Migration Wizard is provided to help you with the project

migration.

Remarks

VC on NWDI is available from CE 7.1 and up. VC 7.0x

does not use DC structure

Once the models were migrated in the browser based VC

on 7.3, the models can be exported and imported into the

NWDS

Mi ti P d


37/54


Migration ProcedureStep 1: Export VC models from 7.0

In your 7.0x system, export VC models

in GML format using the Export to File

Documentation Wizard is

useful to generate a report

Top-level Design-board diagrams

only and Model elements and

properties contains the list of UIs,

these info would be useful formigration

Mi ti P d


38/54


Migration Procedure

Step 2: Import the VC model in 7.3 with Migration Wizard

In your 7.3 system, choose Migration

Wizard for import & convert

Select the GML file exported

from 7.0 system

Mi ti P d


39/54


Migration ProcedureStep 3: Convert the model with Migration Wizard

Now choose Convert!

Migration report is generated

Agenda


40/54


Agenda







8. J2EE / Java EE 5

9. Summary

Upgrade or Migrate?


41/54



WDno

foJa

C V G JE

JaE5

BM

Web AS6.40

NW 7.0x


Migration is

necessary to have

the project run in

NW 7.3

Apps can run on

NW 7.3 witho ut

migrat ion

Design time

migrat ion may be

needed for project

maintenance on NW

7.3

Not applicable for

th is version


42/54

Upgrade Overview


43/54


Upgrade OverviewGP upgrade from NetWeaver 7.0 to 7.3

Overview

When upgrading the NetWeaver Java Server from 7.0 to 7.3 using JUP, migration on GP is not needed.The GP process will continue to run after the server upgrade complete.

Design time Objects and Runtime Objects will both be upgraded at the same time.

NetWeaver 7.0

NetWeaver 7.3

Migration Option


44/54


Migration OptionRequired only when moving GP to another system

Migration with Standard Transport

Mechanism If you need to move GP design time objects to a

different server, you should use Export file with GP

transport in NW7.0.

The exported SCA file can be simply deployed on

a different NetWeaver 7.3 sever.

Migration and modification using GP

Content DC in NWDS

If we import the file in GP content DC, we can

modify the GP content,

For example, we can add translation files ending

with_.xlf to the imported contents

and deploy on 7.3 server.

Agenda


45/54


Agenda







8. J2EE / Java EE 5

9. Summary

Upgrade or Migrate?


46/54



WDno

foJa

C V G JE

JaE5

BM

Web AS6.40

NW 7.0x


Migration is

necessary to have

the project run in

NW 7.3

Apps can run on

NW 7.3 witho ut

migrat ion

Design time

migrat ion may be

needed for project

maintenance on NW

7.3

Not applicable for

th is version

Overview


47/54


OverviewMoving a J2EE project from NW 7.0x to NW 7.3

Upgrade Option

If you are only interested in running your J2EE 1.3

project developed in NetWeaver 7.0 on NetWeaver 7.3,

you do not need migration.

The standard upgrade procedure will automatically move

your J2EE application at runtime and do not require

manual migration of the application source code.

Migration Option

NetWeaver 7.0 supports J2EE 1.3 while NetWeaver 7.3

supports J2EE 1.4 and Java EE 5.

Design time (source code) migration is required if:

You will continue the development / maintenance

of your projects on NetWeaver 7.3. You need the new features / standards provided in

J2EE 1.4 or Java EE 5.

A tool is provided in NetWeaver Developer Studio to

help you with the project migration.

Migration Procedure


48/54


Migration ProcedureStep 1: Prepare your J2EE modules in NetWeaver 7.0

If they are non-DC projects

In your NetWeaver Developer Studio (NWDS), export

all the J2EE projects (i.e. Web module project, EJB

module project, Enterprise Application project)

Right click on each project and choose File Export

File System

If they are Local DCs In your NetWeaver Developer Studio (NWDS), export

all the J2EE projects (i.e. Web DC, EJB DC,

Enterprise Application DC)

Right click on each project and choose File Export

File System

If they are DCs on NWDI

Make sure you have already migrated the Track

containing your J2EE DCs from the SAP NetWeaver

7.0x to SAP NetWeaver 7.3.

Migration Procedure


49/54


Migration ProcedureStep 2: Import projects to NWDS 7.3 to start migration

Importing the projects

For local projects or DCs, click on File

Import to import the modules to NWDS 7.3

If the project is a DC, it will be detected and

prompt to migrate it to an existing

development configuration

For DCs on NWDI, select the DCs and choose

sync / create project.

Migration Wizard

After the project import or project sync, a

migration wizard is triggered automatically

The migration wizard can detect the original

project base (J2EE 1.3) and asks to migrate it

to J2EE 1.4 A migration report will be generated at the end

of the process.

Errors / Warnings found are shown on the

Markers view. Quick Fix is available to guide

you on the fixes.

Migration Procedure


50/54


Migration ProcedureStep 3: (Optional) Move to Java EE 5

J2EE 1.4 vs Java EE 5 By default, the migration wizard migrate your

project to J2EE 1.4

Moving to Java EE 5 is optional as

NetWeaver 7.3 supports both J2EE 1.4 and

Java EE 5

Consider to further migrate the project to

Java EE 5 if:

Future enhancement on the projects will be

based on Java EE 5

You need to use the new features provided in

Java EE 5 (e.g. annotation, injection, etc)

Keep in mind the migration wizard does notchange your codes to use annotation. It just

enables your project to be Java EE 5 based.


51/54

Agenda


52/54


Agenda







8. J2EE / Java EE 5

9. Summary

Summary


53/54


Summary

Server upgrade is provided in NetWeaver

7.3 for direct upgrade from NetWeaver 7.0x.

NetWeaver 7.3 upgrade provides runtime

compatibility for most custom development

project types. Some exceptions are projects

with Web Dynpro for Java or CAF.

In case of projects with Web Dynpro for

Java or CAF, design time migration

procedure and tools are provided.

For other custom development project typeslike VC, GP or J2EE, migration is only

necessary if you need to have the design time

migrated to NetWeaver 7.3 for future

development.

Further Information


54/54

Further Information

SAP Public Web:

Attend bi-weekly webinars on differing SAP NetWeaver and SAP BOBJ topicswhich support successful implementations. Please visit

http://www.sdn.sap.com/irj/scn/ipnw-khnc for more information and be sure to

register to receive notifications of future events.

Refer to How-to-Guides which contain important, up-to-date information aboutsuch topics as technical infrastructure, performance issues and hardwarerequirements. Please visit http://www.sdn.sap.com/irj/scn/howtoguides.

Listen to podcasts designed to enhance your skills through deep divesessions which contain learning scenarios and how-to exercises. Visit

http://www.sdn.sap.com/irj/scn/sap-how-it-works-elearning.

You can also follow SAP Technology RIG on Facebook and Twitter

http://www.facebook.com/pages/SAP-RIG/119256894764191?ref=ts

http://twitter.com/saprig
http://www.sdn.sap.com/irj/scn/ipnw-khnchttp://www.sdn.sap.com/irj/scn/howtoguideshttp://www.sdn.sap.com/irj/scn/sap-how-it-works-elearninghttp://www.sdn.sap.com/irj/scn/sap-how-it-works-elearninghttp://www.sdn.sap.com/irj/scn/sap-how-it-works-elearninghttp://www.sdn.sap.com/irj/scn/sap-how-it-works-elearninghttp://www.sdn.sap.com/irj/scn/sap-how-it-works-elearninghttp://www.sdn.sap.com/irj/scn/sap-how-it-works-elearninghttp://www.sdn.sap.com/irj/scn/sap-how-it-works-elearninghttp://www.sdn.sap.com/irj/scn/sap-how-it-works-elearninghttp://www.sdn.sap.com/irj/scn/sap-how-it-works-elearninghttp://www.sdn.sap.com/irj/scn/sap-how-it-works-elearninghttp://www.sdn.sap.com/irj/scn/howtoguideshttp://www.sdn.sap.com/irj/scn/ipnw-khnchttp://www.sdn.sap.com/irj/scn/ipnw-khnchttp://www.sdn.sap.com/irj/scn/ipnw-khnc

Upgrade_Migrate Your Custom Development Projects to SAP NetWeaver 7.3 - Webinar Presentation

Documents

Transcript of Upgrade_Migrate Your Custom Development Projects to SAP NetWeaver 7.3 - Webinar Presentation