PI 7.1 Upgrade

SAP NetWeaver Process Integration 7.1 - Upgrade 1

SAP NetWeaver Process Integration 7.1Upgrade to SAP NetWeaver PI 7.1

SAP NetWeaver Regional Implementation GroupSAP NetWeaver Product ManagementDecember 2007


Benefits

After reading this document, you will know what you will have to doto:

Upgrade your SAP Exchange Infrastructure 3.0 /SAP NetWeaver 2004

Upgrade your NetWeaver Exchange Infrastructure 7.0 To SAP NetWeaverProcess Integration 7.1


1. Upgrade Overview2. Adapters and Modules3. Java Proxies

Agenda



Agenda


Upgrade Paths toSAP NetWeaver Process Integration 7.1

Upgrade paths will be offered for

SAP NetWeaver ’04 and

SAP NetWeaver 7.0 (2004s)

to go to SAP NetWeaver Process Integration 7.1 (SAP NetWeaver PI 7.1).

SAP NetWeaver ‘04 SAP NetWeaver 7.0(2004s)

SAP NetWeaverPI 7.1

Upgrade

Upgrade Upgr

ade

Upgrade paths to SAP NetWeaver PI 7.1 will be supported by SAP NetWeaver ´04as well as SAP NetWeaver 7.0 (2004s)

Existing investments are leveraged, i.e. most of the objects stored in XI 3.0 or SAPNetWeaver PI 7.0 (2004s) will be available after an upgrade to SAP NetWeaver PI7.1. However, necessary adjustments that customers would have to do will bepublished.


Upgrade Overview

Only inplace upgrade supported

Content copy (like XI 2.0 -> 3.0 migration)not supported

32 bit OS not supported-> Migrate to 64 bit OS before upgrade

SAP JVM is installed during upgrade,(other JDK not supported)

Check the Product Availability Matrixservice.sap.com/pam (not available yet)

Upgrade is an inplace upgrade like between XI 3.0 and SAP NetWeaver 7.0

No migration is necessary

Content copy is not supported

Restrictions:– No support for 32 bit operating systems -> Before the upgrade, you have to migrate your system to

a 64 bit operating system

– SAP JVM is installed during upgrade, other JDKs are not supported

For questions concerning which hardware and databases are running with SAPNetWeaver 7.1, you have to consult the SAP Service Marketplace ->http://service.sap.com/pam (not available yet)

SAPJVM = Java Virtual Machine provided by SAP

http://service.sap.com/pam(not


High Availability Consideration

In SAP NetWeaver 6.40

ABAP: The message server and the enqueue server are integrated within the ABAPCentral Instance (CI)Java: The message server and the enqueue server are implemented as services withinthe SAP System Central Services Instance (SCS) and separated from the centralinstance (CI) this way


ABAP: The message server and the enqueue server can be separated from the centralinstance (CI) to the ABAP SAP Central Services Instance (ASCS) in the ABAP stackalso (recommended)


Only ASCS is supported

SAP NetWeaver 7.1 supports only ABAP SAP Central Service Instance (ASCS) ->You might need to change the high availability setup

The change of HA setup means: Backup and remove the system, install the newsetup.


Upgrade Steps

1. Migrate Operating System, if necessary

2. Upgrade Database, if necessary (see PAM)

3. Upgrade SAP NetWeaver to 7.1

4. New HA setup, if necessary


Upgrade of PI Objects and CustomerEnhancements

After upgrade to PI 7.1All objects in the Integration Repository (IR) are available in the Enterprise SOARepository (ESR) and can be used without changeAll objects in the Integration Directory (ID) are available and can be reusedAll mappings (graphical mapping, XSLT, Java mapping and ABAP mapping) will workwithout changeCustomer Adapters and Adapter modules have to be adjusted and redeployedJava Proxies have to be redeployed

Besides self-written adapter modules and adapters and Java proxies, the PI 7.1 willrun without changes after the upgrade.


Upgrade Documentation (Not Yet Released)

For further information, you can look at the upgrade documentation at the SAPService Marketplace


1. Upgrade Overview2. Adapters and Adapter Modules3. Java Proxies

Agenda


PI Adapter Framework API: from 3.0 to 7.1 – APIStructure

Complex, distributed class structure

High number of reference x high number ofdeployment descriptors

Partial release, but „private“ classes are visible

Inherited classes, many should not be released

Using facades for public SAP NetWeaver

Synchronization point for Java Documentation and Tests

Reduction of (parts of) packages / classes:

462 publics or 44% of the API was removed by facadefilter project technology

Reduction of references, one facade per layer

XI 3.0/ PI 7.0

NetWeaver 7.1

In SAP NetWeaver 7.1 the adapter development API was changed, as the packagenames were restructured.


Adapter Framework API Changes

Major changes:

1. Messaging System moved: com.sap.aii to com.sap.engine

2. Deletion of obsolete packages, for example: com.sap.aii.af.service.monitor,com.sap.aii.af.service.trace

3. Filtering of „internal“ parts, for example: com.sap.aii.af.service.cpa.Mapping

4. Using new JEE APIs, for example: com.sap.transaction

5. And in general: New JVM 1.5

But: These changes are incompatible!

Major changes:– Packages are moved, names changed

– Deletion of obsolete packages

– Filtered packages -> No access to them

– New JVM 1.5 had some problems in JSP

– => All your adapters and adapter modules have to be adjusted when you upgrade the system


Semantical vs. Syntactical AF API Changes

The Adapter Framework programming model has not changed!Message layer (addressing, quality of service, etc.)AF modulesCPA access

No new JCA Technology (still 1.0)

Same transactional model

Same admin model

Changes due to migration are merely syntactical!

Programming model has not changed, so the largest part of the source code doesnot need to be adjusted.

No new JCA technology -> JCA adapter connectivity has not changed

Transaction model has not changed

=> Most changes on the development are syntactical


Migrating an Adapter Module Step by StepPart 1:

Steps in the SAP NetWeaver Developer Studio:

1. Create an EJB J2EE 1.4 module project

2. Apply the libraries (at least com.sap.aii.af.lib.mod.jar andcom.sap.aii.af.ms.ifc_api.jar)

3. Create a package

4. Create a stateless session bean

5. Apply the code of the adapter module

6. Modify the Java code of the adapter module

7. Adjust the ejb-jar.xml

8. Adjust the ejb-j2ee-engine.xml

Steps to be preformed for migration to SAP NetWeaver 7.1– In principle, these are the same steps as for a new deployment

– First: Create an EJB 1.4 module project. New adapter modules are still based on EJB 2.0, not thenew EJB 3.0

– Next: Apply the new libraries

– Create a package

– Create a stateless session bean

– Apply the code of the old adapter module

– Modify the Java code of the adapter module

– You have to adjust the two library deployment descriptor files


Use the New AF 7.1 Library Files

Libraries for AF 3.0/7.0

aii_af_mp.jar

aii_af_ms_api.jar

aii_af_trace.jar

aii_af_svc.jar

aii_af_cpa.jar

Libraries for AF 7.1

com.sap.aii.af.lib.mod.jar

com.sap.aii.af.ms.ifc_api.jar

sap.com~tc~logging~java~impl.jar

com.sap.aii.af.svc_api.jar

com.sap.aii.af.cpa.svc_api.jar

For the module migration, you have to extract the newlibraries from your 7.1 PCK/AF installation.

For migrating the adapter modules, it is necessary to replace the 3.0/7.0 libraries withthe corresponding 7.1 libraries.


Use the New AF 7.1 Packages

The interface modulecom.sap.aii.af.mp.module -> com.sap.aii.af.lib.mp.module

Dealing with payload and attachmentscom.sap.aii.af.ra.ms.api -> com.sap.engine.interfaces.messaging.api

Writing in audit logcom.sap.aii.af.service.auditlog ->

com.sap.engine.interfaces.messaging.api.auditlog

Writing in J2EE server logcom.sap.aii.af.service.trace -> com.sap.tc.logging

Accessing communication channel datacom.sap.aii.af.service.cpa -> com.sap.aii.af.service.administration.api.cpa or

com.sap.aii.af.service.cpa

For the module migration, you have to adjust theimport statements in your Java code.

As the package names changed in PI 7.1, you have to adjust the import statementsin your adapter code.

A lot of class names did not change, so you have to adjust the code of adapterdevelopment only for special cases, which are described on the following slides


Example 1: Logging to Service Trace

SAP NetWeaverAdministrator provides aLog Viewer.

Trace output is configuredin the Log Configuration.

Each log destination canbe separately displayedand filtered according touser-specific needs.

The Log Viewer can be accessed in SAP NetWeaver Administrator:

Choose Availability and Performance Management -> Log Viewer


Logging: Service Trace (Code Fragment)in AF 3.0/7.0

public class CreateAttachment implements SessionBean,Module {

private static final Trace TRACE = new Trace("yourVersion");

public ModuleData process(ModuleContext moduleContext,ModuleData inputModuleData)throws ModuleException {

String SIGNATURE = "YourSignature";

TRACE.entering(SIGNATURE,new Object[] { moduleContext, inputModuleData });

try{Message messageIN =

(Message) inputModuleData.getPrincipalData();

} catch (Exception e) {TRACE.catching(SIGNATURE, e);TRACE.errorT(SIGNATURE, "Error occurred");

}

}

This code sample shows the writing of server logs in 3.0/7.0

The highlighted code has to be changed during migration.


Logging: Service Trace (Code Fragment)in AF 7.1

public class CreateAttachment implements SessionBean,Module {

private Location loc = null;


try{

String SIGNATURE = "YourSignature";loc =

Location.getLocation(CreateAttachment.class.getName();loc.entering(SIGNATURE,

new Object[] { moduleContext, inputModuleData });

Message messageIN =(Message) inputModuleData.getPrincipalData();

} catch (Exception e) {loc.catching(SIGNATURE, e);loc.errorT(SIGNATURE, "Error occurred");

}

}

The static class TRACE is replaced by the class Location

This class has to be instantiated by the static method getLocation

The instance can now be used like the old class TRACE


Example 2: Logging to Audit Log

For each message, an audit log is written that shows processing details(e.g. the executed module chain).

SAP PI AF provides standard methods within its logging framework.

Another example for code changes in the adapter module is in the audit log

With the adapter module, you can write any information to the audit log


Logging: Audit Log (Code Fragment)in AF 3.0/7.0public class CreateAttachment

implements SessionBean, Module {



AuditMessageKey amk =new AuditMessageKey(msg.getMessageId(),

AuditDirection.OUTBOUND);

Audit.addAuditLogEntry(amk, AuditLogStatus.SUCCESS,“Customer Module called");

}

}

This code sample shows the writing of server logs in 3.0/7.0

The highlighted code has to be changed during migration.


Logging: Audit Log (Code Fragment)in AF 7.1

public class CreateAttachmentimplements SessionBean, Module {



MessageKey key = new MessageKey(msg.getMessageId(),msg.getMessageDirection());

PublicAPIAccess pa =PublicAPIAccessFactory.getPublicAPIAccess();

AuditAccess audit = pa.getAuditAccess();audit.addAuditLogEntry(key, AuditLogStatus.SUCCESS,

“Customer Module called“);}

}

The class AuditMessageKey is merged by the class MessageKey, so in the code ishas to be replaced.

The static class Audit is replaced by AuditAccess, which has to be instantiated.

The instance of AuditAccess can be used like the old class Audit


Adjust the Ejb-jar.Xml

<?xml version="1.0" encoding="UTF-8"?>

<ejb-jar xmlns="http://java.sun.com/xml/ns/j2ee"xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" id="ejb-jar_ID"version="2.1" xsi:schemaLocation="http://java.sun.com/xml/ns/j2eehttp://java.sun.com/xml/ns/j2ee/ejb-jar_2_1.xsd">

<description>EJB JAR description</description><display-name>EJB JAR</display-name><enterprise-beans>

<session><ejb-name>YourEJBName</ejb-name><home>com.sap.aii.af.lib.mp.module.ModuleHome</home><remote>com.sap.aii.af.lib.mp.module.ModuleRemote</remote><local-home> com.sap.aii.af.lib.mp.module.ModuleLocalHome</local-home><local>com.sap.aii.af.lib.mp.module.ModuleLocal</local><ejb-class>yourPackage.YourClass</ejb-class><session-type>Stateless</session-type><transaction-type>Container</transaction-type>

</session></enterprise-beans>

</ejb-jar>

The ejb-jar.xml file can be generated with the SAP NetWeaver DeveloperStudio.

Replace thegenerated interface

names

The ejb-jar.xml defines the package and class names corresponding to an EJB name

The interface names of the adapter module classes are always the standardinterfaces of the adapter module development kit. You find them in the librarycom.sap.aii.af.lib.mod.jar

The interface names differ from XI 3.0/7.0 by the sub path lib

http://java.sun.com/xml/ns/j2ee/ejb-jar_2_1.xsd%22


Migrating an Adapter Module Step by StepPart 2

Steps in the SAP NetWeaver Developer Studio:

1. Create an enterprise application project

2. Add the EJB module

3. Adjust the application-j2ee-engine.xml as follows

4. Deploy the application to the PCK/AE

This is the first part for developing the EJB modules, then we come to thedeployment

– This is in principle the same as if you deploy a new adapter module:

– Create a project

– Add the EJB module

– Adjust the descriptor file application-j2ee-engine.xml

– Then you can deploy


The Application-j2ee-engine.Xml

sap.comlibraryhardcom.sap.base.technology.facade

sap.comlibraryhardcom.sap.aii.af.lib.facade

Providername

Referencetarget-type

Referencetype

Reference target

sap.cominterfacehardcom.sap.aii.af.ifc.facade

sap.comservicehardcom.sap.aii.af.svc.facade

sap.comlibraryhardengine.j2ee14.facade

sap.comservicehardengine.security.facade

In this file, you have to create the following references:

In the deployment descriptors, the references to the library have totally changed, thatmeans you refer to the facades that have been introduced in the slides before

The original deployment descriptor is no longer valid


Using a Non-central Adapter Engine

As the migration of the customer adapters and adapter modules might not bedone immediately after SAP NetWeaver PI 7.1 is available, it is an option to usea non-central adapter engine based on 3.0/7.0 connected to the PI 7.1.

Customer adapters and adapter modules run on the non-central adapter engineuntil the migration is finished.

As a workaround during migration time, it is recommended to use a non-centralAdapter Engine based on XI 3.0 / SAP NetWeaver 7.0 and connected to the PI 7.1system

You can run the adapter modules or adapters, which have not been migrated, on thenon-central Adapter Engine until the migration is finished



Agenda


Migrating XI 3.0/PI 7.0 Java Proxies toPI 7.1

The Java proxies have to be redeployed on PI 7.1.

The application-j2ee-engine.xml has to be adjusted before:

a) J2EE library com.sap.aii.proxy.runtimechanged to com.sap.aii.proxy.svc and available as a service

b) J2EE library com.sap.aii.messaging.runtimechanged to com.sap.aii.af.sdk.lib

No changes in the Java code necessary.

All functionality of XI 3.0/PI 7.0 Java proxies available.

The Java proxies have to be redeployed.

The application-j2ee-engine.xml has to be adjusted the same way as the adaptermodules.

The deployment descriptor has to be changed to the new package structure, but nochanges in the Java code are necessary.

All functionality of XI 3.0 Java proxies is available.


Summary

Upgrade to PI 7.1 possible from XI 3.0 and PI 7.0

PI 7.1 only available for 64 bit operating system and ABAP SAP CentralServices Instance (ASCS)

Customer adapters and adapter modules have to be adjusted for PI 7.1

Generated Java proxy EJBs have to be adjusted for PI 7.1 as well.


Copyright 2007 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 changedwithout 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, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, System i, System i5, System p, System p5,System x, System z, System z9, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, Informix, i5/OS, POWER, POWER5, POWER5+, OpenPower and PowerPC are trademarks orregistered trademarks of IBM Corporation.

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.

MaxDB is a trademark of MySQL AB, Sweden.

SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registeredtrademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned are the trademarks of their respective companies. Datacontained 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 writtenpermission 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, andfunctionalities 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 issubject 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 containedwithin 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 aparticular 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.

Date post:	14-Oct-2014
Category:	Documents
Upload:	javier-alcubilla
View:	295 times
Download:	3 times

PI 7.1 Upgrade

Documents