8/4/2019 7.1 Presentation http://slidepdf.com/reader/full/71-presentation 1/54 SAP NetWeaver Process Integration 7.1 Upgrade Considerations Paul Médaille, Principal Consultant National Competency Center Jan 2008
8/4/2019 7.1 Presentation
http://slidepdf.com/reader/full/71-presentation 1/54
SAP Net Weaver Proc ess Int egrat ion
7.1Upgrade Considerations
Paul Médaille,Principal Consultant
National Competency Center
Jan 2008
8/4/2019 7.1 Presentation
http://slidepdf.com/reader/full/71-presentation 2/54
© SAP 2007 / Page 2
1. SAP NetWeaver Process Integration 7.1 at a Glance1.1. New Features in brief
1.2. Why upgrade to SAP NetWeaver PI 7.1?
2. Upgrading to SAP NetWeaver PI 7.12.1. Upgrade Overview
2.2. Adapter and Adapter Modules
2.3. Java Proxies
3. Summary / Q&A
Agenda
8/4/2019 7.1 Presentation
http://slidepdf.com/reader/full/71-presentation 3/54
© SAP 2007 / Page 3
New Capabi l it ies of SAP NetWeaver Proc ess
Int egrat ion 7.1
Enterprise ServicesRepository and Registry
High Volume Support
Reduced Sizing
New Modeling Constructs
Mapping Improvements
Functional Enhancements
Central Configuration and
Monitoring
Payload Validation
Direct Connections
…and more…
8/4/2019 7.1 Presentation
http://slidepdf.com/reader/full/71-presentation 4/54
© SAP 2007 / Page 4
Ent erpr ise Serv ic es Reposit ory and Regis t ry
Enterprise Services Repository
Services Registry
Yellow pages of Services Deployment information (i.e.
endpoint)
Services management
Ease of consumption: Browse,discover, and use services.
Enterprise ServicesRepository and Registry
Services Registry
Definition of Processesand Services
Service Metadata
Central modeling anddesignenvironment
8/4/2019 7.1 Presentation
http://slidepdf.com/reader/full/71-presentation 5/54
© SAP 2007 / Page 5
Serv ice Model ing
In tegra t ion
Scenar io ModelProcess Component
Models
Process
Component
In te rac t ionModel
<Integration Scenario>
8/4/2019 7.1 Presentation
http://slidepdf.com/reader/full/71-presentation 6/54
© SAP 2007 / Page 6
Ex ample: Process Component In t eract ion
Model
8/4/2019 7.1 Presentation
http://slidepdf.com/reader/full/71-presentation 7/54
© SAP 2007 / Page 7
Serv ice Inter fac es
Service Interfaces
Are built out of GDTs and Message Types
Specify the operations of a service
Are abstract and language-independentdesign time representations of services
Interface Patterns
Describe the type of communication that is tobe executed on the message
8/4/2019 7.1 Presentation
http://slidepdf.com/reader/full/71-presentation 8/54
© SAP 2007 / Page 8
New Model ing Concepts
Extended conditions and expressions
Configurable parameters
Language-dependent texts
Step groups
User decisions
Alert categories
8/4/2019 7.1 Presentation
http://slidepdf.com/reader/full/71-presentation 9/54
© SAP 2007 / Page 9
New Features in Graphical Mapping
(par t ia l l is t )
Multiple Targets
Graphical Variables
Parameterized Mappings
Graphical Lookups
Function Libraries
8/4/2019 7.1 Presentation
http://slidepdf.com/reader/full/71-presentation 10/54
© SAP 2007 / Page 10
Local Processing in Advanc ed Adapter Engine
Bypass Integration Server formany scenarios
Eliminate several persistencesteps, context changes
Direct Adapter-to-adaptercommunication
For sync and async scenarios
Supported by all J2EE-basedtechnical adapters from SAP
Up to 10x boost in performance
SA PSA P
Integration ServerIntegration Server
Integration Engine& ccBPM Engine
Integration Engine& ccBPM Engine
Advanced Adapter EngineAdvanced Adapter Engine
SOAP etc.File
3rd PartyApplication
SA PSA P
JDBC RFC
Mapping Program
8/4/2019 7.1 Presentation
http://slidepdf.com/reader/full/71-presentation 11/54
© SAP 2007 / Page 11
WS-Reliable Messaging (WS-RM) Asynchronous messaging (EO, EOIO) based on open WS standard
Native support through Integration Engine (w/o adapter engine)
Integrat ion Server
Integration EngineIntegration Engine
Business Process EngineBusiness Process Engine
Central Adapter EngineCentral Adapter Engine
FTP JMS SMTP …XI Protocoll WS-RM
WS-ReliableMessaging
8/4/2019 7.1 Presentation
http://slidepdf.com/reader/full/71-presentation 12/54
© SAP 2007 / Page 12
Payload Val idat ion
8/4/2019 7.1 Presentation
http://slidepdf.com/reader/full/71-presentation 13/54
© SAP 2007 / Page 13
Centra l Conf igurat ion and Moni tor ing
/NWA
/NWAPI
8/4/2019 7.1 Presentation
http://slidepdf.com/reader/full/71-presentation 14/54
© SAP 2007 / Page 14
Why Upgra de t o SAP NetWeaver Proc ess
Integrat ion 7.1?
SAP NetWeaver Process Integration 7.1 includes several new capabilities to support SAPenterprise Service Oriented Architecture:
Enterprise Services Repository as the central design time repository for service modeling,service metadata, and design time governance.
UDDI v. 3-based Service Registry for discovery of Services
Note: SAP NetWeaver PI is not absolutely necessary for these capabilities – alsodelivered with SAP NetWeaver Composition Environment
Capabilities for “managed” or “brokered” service calls:
Routing
Mapping
Multiple receivers Business Process Management
A “natural fit” for enterprise SOA – an important component of the Enterprise Service Bus
8/4/2019 7.1 Presentation
http://slidepdf.com/reader/full/71-presentation 15/54
© SAP 2007 / Page 15
Why Upgra de t o SAP NetWeaver Proc ess
Integrat ion 7.1?
SAP NetWeaver Process Integration 7.1 includes several enhancements that extend theexisting capabilities and improve performance:
Message Bundling
Enhanced Adapter Engine
Direct Adapter-to-Adapter communication for many scenarios
Reduced Sizing
Mapping enhancements
XML Validation
Central configuration of point-to-point service calls
Business Process Management enhancements
Unified administration is NetWeaver Administrator
In short, existing SAP NetWeaver XI customers will find the new version to be significantly more capable than existing versions.
8/4/2019 7.1 Presentation
http://slidepdf.com/reader/full/71-presentation 16/54
© SAP 2007 / Page 16
1. SAP NetWeaver Process Integration 7.1 at a Glance1.1. New Features in brief
1.2. Why upgrade to SAP NetWeaver PI 7.1?
2. Upgrading to SAP NetWeaver PI 7.12.1. Upgrade Overview
2.2. Adapter and Adapter Modules
2.3. Java Proxies
3. Summary / Q&A
Agenda
8/4/2019 7.1 Presentation
http://slidepdf.com/reader/full/71-presentation 17/54
© SAP 2007 / Page 17
Upgrade Paths t o SAP Net Weaver Proc ess
Integrat ion 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 ‘04SAP NetWeaver 7.0
(2004s)
SAP NetWeaverPI 7.1
U
p g r a d e U p
g r a d e
8/4/2019 7.1 Presentation
http://slidepdf.com/reader/full/71-presentation 18/54
© SAP 2007 / Page 18
Changes in t he Technic al Envi ronment
32 bit OS not supported
Migrate to 64 bit OS before upgrade?
SAPJVM is installed during upgrade
No other JDK are supported
Check the Product Availability Matrix( //service.sap.com/pam )
Is your DB version supported?
8/4/2019 7.1 Presentation
http://slidepdf.com/reader/full/71-presentation 19/54
© SAP 2007 / Page 19
High Avai lab i l i ty Considerat ion
SAP NetWeaver 6.40• ABAP: The message server and the enqueue server are integrated within the ABAP
Central Instance (CI)
• Java: The message server and the enqueue server are implemented as serviceswithin the SAP System Central Services Instance (SCS) and separated from the centralinstance (CI) this way
SAP NetWeaver 7.0
• 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)
SAP NetWeaver 7.1
ASCS is recommended, but not required
8/4/2019 7.1 Presentation
http://slidepdf.com/reader/full/71-presentation 20/54
© SAP 2007 / Page 20
Upgrade or New Ins ta l l?
Existing XI/PI systems (> XI 2.0) can be directly upgraded to SAPNetWeaver Process Integration 7.1, but…
…in certain cases customers may wish to do a fresh install and then
transport Repository and Directory content to new system.
Decision Factors:
Technology-related (e.g. Database upgrade required?)
Landscape-related (e.g. Production downtime)
Interface-related (many complex productive interfaces?)
8/4/2019 7.1 Presentation
http://slidepdf.com/reader/full/71-presentation 21/54
© SAP 2007 / Page 21
Upgrade Conside rat ions/Concer ns
Local or Central SLD? Central 7.0 SLD supported, but new features not available
Third-party Adapters?
Certified for your target SP level?
Yes – Upgrade PI + adapters No – Decision time!
Hold off on SP upgrade; but then you may encounter fixedbugs!
Separate projects: upgrade PI to work with base objects,
upgrade adapters when certified (use de-central adapter asworkaround)
Combined usage types?
If multiple NW usage types are installed on PI system (e.g. BI andEP on PI system), no support for PI upgrade at this time.
8/4/2019 7.1 Presentation
http://slidepdf.com/reader/full/71-presentation 22/54
© SAP 2007 / Page 22
Non-Cent ral Adapt er Engine
Customer and 3 rd -party adapters and adapter modules run on the non-central adapter engine until the migration is finished.
Adapters developed by customers,adapter modules, and adaptersfrom the partner ecosystem mustbe migrated to the new version.
As the migration of the
customer/3rd-party adapters andadapter modules might not bedone immediately after SAPNetWeaver PI 7.1 is available, it isan option to use a non-centraladapter engine based on 3.0/7.0
connected to the PI 7.1.
8/4/2019 7.1 Presentation
http://slidepdf.com/reader/full/71-presentation 23/54
© SAP 2007 / Page 23
Upgrade St eps
Migrate Operating System, if necessary
Upgrade Database, if necessary (see PAM)
Cleanup XI/PI tables
Activate/Delete open change lists
Upgrade SAP NetWeaver to 7.1
Redeploy Adapter modules / proxies
New HA setup, if necessary
Testing
Note: Solution Manager should be at highest SP Level!
(Currently version 7.0 SP 16)
8/4/2019 7.1 Presentation
http://slidepdf.com/reader/full/71-presentation 24/54
© SAP 2007 / Page 24
Upgrade of PI object s and c ustom er
enhancements
After upgrade to PI 7.1:
All objects in the Integration Repository (IR) are available in the EnterpriseSOA Repository (ESR) and can be used without change
All objects in the Integration Directory (ID) are available and can be reusedAll mappings (graphical mapping, XSLT, Java mapping and ABAP
mapping) will work without change
Customer Adapters and Adapter modules have to be adjusted andredeployed
Java Proxies have to be redeployed
8/4/2019 7.1 Presentation
http://slidepdf.com/reader/full/71-presentation 25/54
© SAP 2007 / Page 25
Upgrade Document at ion
8/4/2019 7.1 Presentation
http://slidepdf.com/reader/full/71-presentation 26/54
© SAP 2007 / Page 26
How -t o Guide for U pgrades
Wouldn’t it be nice if there were a How-to guide for PI 7.1 upgrades published on SDN?
Coming soon! PI RIG in EMEA and America are working to produce aHow-to Guide for PI 7.1 upgrades, which will be published on SDN
(sorry, no publication date announced)
Coming soon! PI RIG in EMEA and America are working to produce aHow-to Guide for PI 7.1 upgrades, which will be published on SDN
(sorry, no publication date announced)
8/4/2019 7.1 Presentation
http://slidepdf.com/reader/full/71-presentation 27/54
© SAP 2007 / Page 27
TechEd Sess ion SOA213
Going to SAP TechEd in September?
Attend session SOA213:
“How to Plan, Strategize and Upgrade to SAP NetWeaver PI 7.1 SOA Middleware”
(2 hour lecture; speaker: Prasad Illapani,PI RIG Americas)
Session Content:
Preparation Phase• Clarify Business Use-Cases
• Clarify Technical Constraints
Upgrade Options
Upgrade
• SLD Considerations
• Upgrade Project Steps• Adjust Scenarios to SAP PI 7.1
capabilities
New Installation
• Installation Project Steps
• Out Phasing Steps
Best Practices – Decision Support
8/4/2019 7.1 Presentation
http://slidepdf.com/reader/full/71-presentation 28/54
© SAP 2007 / Page 28
1. SAP NetWeaver Process Integration 7.1 at a Glance1.1. New Features in brief
1.2. Why upgrade to SAP NetWeaver PI 7.1?
2. Upgrading to SAP NetWeaver PI 7.12.1. Upgrade Overview
2.2. Adapter and Adapter Modules
2.3. Java Proxies
3. Summary / Q&A
Agenda
8/4/2019 7.1 Presentation
http://slidepdf.com/reader/full/71-presentation 29/54
© SAP 2007 / Page 29
PI Adapt er Framew ork API : f rom 3.0 t o 7.1 –
API St ruc ture
Complex, distributed class structure(High number of references) (high number ofdeployment descriptors) = confusing complexity
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 andTests
• 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
8/4/2019 7.1 Presentation
http://slidepdf.com/reader/full/71-presentation 30/54
© SAP 2007 / Page 30
Adapter Framew ork 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!
8/4/2019 7.1 Presentation
http://slidepdf.com/reader/full/71-presentation 31/54
© SAP 2007 / Page 31
Semant ic vs. Syntac t ic AF API Changes
The Adapter Framework programming model has not changed!
Message layer (addressing, quality of service, etc.)
AF modules
CPA access
No new JCA Technology (still 1.0)
Same transactional model
Same administration model
Changes due to migration are merely syntactical!
8/4/2019 7.1 Presentation
http://slidepdf.com/reader/full/71-presentation 32/54
© SAP 2007 / Page 32
Migrat ing an Adapt er Module St ep by St ep
Part 1:
St eps in t he SAP NetWeaver Developer St udio:
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
8/4/2019 7.1 Presentation
http://slidepdf.com/reader/full/71-presentation 33/54
© SAP 2007 / Page 33
Use t he New AF 7.1 Library Fi les
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
new libraries from your 7.1 PCK/AF installation.
8/4/2019 7.1 Presentation
http://slidepdf.com/reader/full/71-presentation 34/54
© SAP 2007 / Page 34
Use t he New AF 7.1 Pac k ages
The interface module: com.sap.aii.af.mp.modulecom.sap.aii.af.lib.mp.module
Dealing with payload and attachments:com.sap.aii.af.ra.ms.apicom.sap.engine.interfaces.messaging.api
Writing in audit log:com.sap.aii.af.service.auditlogcom.sap.engine.interfaces.messaging.api.auditlog
Writing in J2EE server log:com.sap.aii.af.service.tracecom.sap.tc.logging
Accessing communication channel data:com.sap.aii.af.service.cpacom.sap.aii.af.service.administration.api.cpa
or com.sap.aii.af.service.cpa
For the module migration, you have to adjust the import statements in your Java code
8/4/2019 7.1 Presentation
http://slidepdf.com/reader/full/71-presentation 35/54
© SAP 2007 / Page 35
Ex ample 1: Logging t o Serv ice Trace
SAP NetWeaverAdministrator provides aLog Viewer.
Trace output is configuredin the Log Configuration.
Each log destination can
be separately displayedand filtered according touser-specific needs.
8/4/2019 7.1 Presentation
http://slidepdf.com/reader/full/71-presentation 36/54
© SAP 2007 / Page 36
Logging: Servic e Trac e (Code Fragm ent ) 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");
}
}
8/4/2019 7.1 Presentation
http://slidepdf.com/reader/full/71-presentation 37/54
© SAP 2007 / Page 37
Logging: Servic e Trac e (Code Fragm ent ) in AF
7.1
public class CreateAttachment implements SessionBean,
Module {
private Location loc = null;
public ModuleData process(ModuleContext moduleContext, ModuleData inputModuleData)throws ModuleException {
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");
}
}
8/4/2019 7.1 Presentation
http://slidepdf.com/reader/full/71-presentation 38/54
© SAP 2007 / Page 38
Ex ample 2: Logging t o Audi t 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.
8/4/2019 7.1 Presentation
http://slidepdf.com/reader/full/71-presentation 39/54
© SAP 2007 / Page 39
Logging: Audi t Log (Code Fragm ent ) in AF
3.0/7.0
public class CreateAttachment
implements SessionBean, Module {
public ModuleData process(
ModuleContext moduleContext,
ModuleData inputModuleData)
throws ModuleException {
Message messageIN =(Message) inputModuleData.getPrincipalData();
AuditMessageKey amk =
new AuditMessageKey(msg.getMessageId(),
AuditDirection.OUTBOUND);
Audit.addAuditLogEntry(amk, AuditLogStatus.SUCCESS,
“Customer Module called");}
}
8/4/2019 7.1 Presentation
http://slidepdf.com/reader/full/71-presentation 40/54
© SAP 2007 / Page 40
Logging: Audi t Log (Code Fragment ) in AF 7.1
public class CreateAttachment
implements SessionBean, Module {
public ModuleData process(
ModuleContext moduleContext,
ModuleData inputModuleData)
throws ModuleException {
Message messageIN =(Message) inputModuleData.getPrincipalData();
MessageKey key = new MessageKey(msg.getMessageId(),
msg.getMessageDirection());
PublicAPIAccess pa =
PublicAPIAccessFactory.getPublicAPIAccess();
AuditAccess audit = pa.getAuditAccess();
audit.addAuditLogEntry(key, AuditLogStatus.SUCCESS,
“Customer Module called“);
}
}
8/4/2019 7.1 Presentation
http://slidepdf.com/reader/full/71-presentation 41/54
© SAP 2007 / Page 41
Adjust t he 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 Developer
Studio.Replace the
generated interfacenames
8/4/2019 7.1 Presentation
http://slidepdf.com/reader/full/71-presentation 42/54
© SAP 2007 / Page 42
Migrat ing an Adapt er Module St ep by St ep
Par t 2
St eps in t he SAP NetWeaver Developer Stud io:
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
8/4/2019 7.1 Presentation
http://slidepdf.com/reader/full/71-presentation 43/54
© SAP 2007 / Page 43
The Appl icat ion- 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
I n th is f i l e, you have to c rea te t he fo l low ing re ferences :
8/4/2019 7.1 Presentation
http://slidepdf.com/reader/full/71-presentation 44/54
© SAP 2007 / Page 44
1. SAP NetWeaver Process Integration 7.1 at a Glance1.1. New Features in brief
1.2. Why upgrade to SAP NetWeaver PI 7.1?
2. Upgrading to SAP NetWeaver PI 7.12.1. Upgrade Overview
2.2. Adapter and Adapter Modules
2.3. Java Proxies
3. Summary / Q&A
Agenda
8/4/2019 7.1 Presentation
http://slidepdf.com/reader/full/71-presentation 45/54
© SAP 2007 / Page 45
J ava Prox ies
Existing Java proxy structure is migrated to JEE 5-basedproxies, but the Java Proxy Runtime supports 3.0/7.0 proxies ifthe interface remains unchanged.
If the interface needs to be changed, the existing proxies mustbe migrated to JEE 5-based proxies. Code changes will be
required as the programming model is different
Java Proxy Generation in the Integration Repository is nolonger available as of PI 7.1. Instead, Java Proxy developmentis done in the SAP NetWeaver Developer’s Studio.
8/4/2019 7.1 Presentation
http://slidepdf.com/reader/full/71-presentation 46/54
© SAP 2007 / Page 46
Migrat ing XI 3.0/PI 7.0 J ava Prox ies t o PI 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.runtime changed to com.sap.aii.proxy.svc and available as a service
b) J2EE library com.sap.aii.messaging.runtime changed 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.
8/4/2019 7.1 Presentation
http://slidepdf.com/reader/full/71-presentation 47/54
© SAP 2007 / Page 47
Transport ing XI 3.0 J ava Prox ies t o PI 7.1
The Java Proxies have to be redeployed on PI 7.1
The application-j2ee-engine.xml has to be adjusted:
a) J2EE library com.sap.aii.proxy.runtime changed to com.sap.aii.proxy.svc andavailable as a service
b) J2EE Library com.sap.aii.messaging.runtime changed to com.sap.aii.af.sdk.lib
No changes to the Java code are necessary
All functionality of the XI 3.0 Java Proxies are available
8/4/2019 7.1 Presentation
http://slidepdf.com/reader/full/71-presentation 48/54
© SAP 2007 / Page 48
Migrat ing 3.0 prox ies t o PI 7.1
Migrated proxies allow reuse of configuration (like communication channel) and XI 3.0 Javaproxy-specific features (like acknowledgments)
New Proxies have to be created in NetWeaver Developer Studio
Receiver proxies are EJB 3.0-based; sender proxies do not use EJB
Due to the different programming model, the Java proxy code has to be adjusted
Some JPR 3.0 classes are not available for JEE 5-based proxies, for examplecom.sap.aii.proxy.xiruntiume.core.MessageSpecifier
8/4/2019 7.1 Presentation
http://slidepdf.com/reader/full/71-presentation 49/54
© SAP 2007 / Page 49
Ex t ending 3.0 Prox ies as J EE 5-based Proxies
Migrated proxies need different configuration (SOAP or WS-RM adapter instead of XI adapterin communication channel)
XI 3.0 proxy-specific features (like acknowledgements) cannot be used
New proxies are created in the NetWeaver Developer Studio
Receiver proxies are EJB 3.0-based, sender proxies do not use EJB
Due to the different programming model, the Java proxy code has to be adjusted.
8/4/2019 7.1 Presentation
http://slidepdf.com/reader/full/71-presentation 50/54
© SAP 2007 / Page 50
1. SAP NetWeaver Process Integration 7.1 at a Glance1.1. New Features in brief
1.2. Why upgrade to SAP NetWeaver PI 7.1?
2. Upgrading to SAP NetWeaver PI 7.12.1. Upgrade Overview
2.2. Adapter and Adapter Modules
2.3. Java Proxies
3. Summary / Q&A
Agenda
8/4/2019 7.1 Presentation
http://slidepdf.com/reader/full/71-presentation 51/54
© SAP 2007 / Page 51
Summary
SAP NetWeaver Process Integration 7.1 is a new generation EnterpriseService Bus with SOA Middleware capabilities
PI 7.1 has several features which boost performance compared toearlier versions
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 and 3rd-party adapters and adapter modules have to beadjusted for PI 7.1
Technical Upgrade or Side-by-Side Install are possible; consider
decision factors carefully.
Interoperates with central 7.0 SLD
Generated Java proxy EJBs have to be adjusted for PI 7.1 as well.
8/4/2019 7.1 Presentation
http://slidepdf.com/reader/full/71-presentation 52/54
© SAP 2007 / Page 52
Quest ions?
8/4/2019 7.1 Presentation
http://slidepdf.com/reader/full/71-presentation 53/54
© SAP 2007 / Page 53
Thank you!
Paul C. MédaillePrincipal Consultant, NCC
SAP NetWeaver Process Integration
8/4/2019 7.1 Presentation
http://slidepdf.com/reader/full/71-presentation 54/54
© SAP 2007 / Page 54
Copyr ight 2007 SAP AG
Al l r ights 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, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, Duet, Business ByDesign, ByDesign, PartnerEdge and other SAP products and services mentioned herein as well as theirrespective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned andassociated logos displayed 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. 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 these
materials 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, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, Duet, Business ByDesign, ByDesign, PartnerEdge und andere in diesem Dokument erwähnte SAP-Produkte und Servicessowie die dazugehö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ähntenNamen von 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 bestimmten
Geschä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.