on 07-03-2008 8:02 AM
What is the Difference between XI 3.0 and XI 7.0?
( functionality & architecture wise)
HI
Difference b/w XI3.0 n PI7.0
XI 3.0
1.J2SE adapter engine replaced with J2EE Adapter engine.
2. BPM was available from XI 3.0
3. It is a Part of Netweaver 2004
PI 7.0
1XI renames as Process Integration(PI)
2. It is a Part of Netweaver 2004s.
3. Has all features of XI 3.0 and every SP of Pi 7.0 has a corresponding release for XI 3.0.
4. Runs on WAS 7.0 and has same features as XI 3,0
5.Adapter Enhancements in JMS,JDBC,.Conversion. Multimapping.. userdefined functions.
the major difference is PI 7.0 is based on WAS 7.0
1.All new features for XI 7.0 are almost same as for XI 3.0 at least till SPS 19.
Some differences are as follows:
u2022 Adapter Enhancements like JMS, JDBC, Oracle-JDBC and CIDX Enhancements
u2022 New Conversion Agent,
u2022 Receiver Determination Enhancements
u2022 Multi mapping
u2022 User defined enhancements
u2022 Unbounded Processes (Integration Processes).
2. One more difference is the ABAP stack (which is 7.0 and not 6.40) but from the developer point of view there is nothing new.
3. PI 7.0 = XI 7.0
4. For each SP in XI3.0 there is a corresponding SP being released for PI (XI 7.0). A comparison of the service packs in 2004 and 2004s:
In 2004 - In 2004s
SP12 & lower = SP04
SP13 + 14 = SP05
SP15 = SP06
SP16 = SP07
SP17 = SP08
SP18 = SP09
5. XI3.0 is based on WAS(web application server)6.40 - NW2004
PI7.0 is based on WAS(web application server)7.0 - NW2004's.
XI 3.0 runs on WAS 6.40 and is a part of Netweaver 2004.
PI 7.0 runs on WAS 7.0 and is a part if Netweaevr 2004s.
cheers
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
There is no new features added in PI7.0, if u have working on XI 3.0, PI7.0 Older versions the features same..
But PI7.1 there is new changes u can find below.....
Integarte SAP & Non-SAP Legacy system
PI 7.1 is based on open, web service enabled standards and
Integrate all SAP and non-SAP, A2A, B2B, BPM, service enabling and BAM
Highlight of enhancement in PI7.1
1) Enterprise Service repository (ESR) contains the design Registry
2) Includes significant high-volume message processing is supported by message processed in a single
Service call
3) Also importantly support for asynchronous messaging based Reliable Messaging (WS-RM) for both
Brokered communication between two systems will be supported in this release.
4) Provide Service Registry benefits based on UDDI 3.0
Enterprise Service Repository
In PI7.1 ES Repository is at the heart of Enterprise SOA
ES Repository is really the master data repository of service objects for Enterprise SOA
It contains the definition & process of services
In ES Repository has two parts, one is the ES Repository and the other being the Services Registry
ES Repository (ESR) is really the master data repository of service objects for Enterprise SOA
Besides service definition the ES Repository also provides you with a central point for finding and
Managing service metadata from different sources, including application deployments - this is
Where the Services Registry comes in. The Services Registry is the UDDI part of the ESR which
Enables service consumers to find services
The SAP XI Integration Repository used by process integration has become the basis of the central Enterprise Service Repository: powering Enterprise SOA and Service Enablement.
Objects in the ES Repository include:
Global Data Types (CCTS based)
Process Component Models
Executable Integration Processes (BPEL)
Integration Scenarios
Service Interfaces (Enterprise Services)
Interface Mappings
Enterprise Services built in the ES Repository
Enterprise Services includes:
Are built using a consistent enterprise model based on: GDTs, Process Components, and Business Objects.
Are based on open standards.
Are mapped to the Service Interface object in the ES Repository.
Global Data Types - Building blocks for Service Interfaces
Defined in the ES Repository
Defined company-wide based on open standards (ISO 15000-5, UN/CEFACT CCTS)
Reusable semantic building blocks for service interfaces and message types
Process Component Models
Drill down from high-level models to service interfaces and operations
Process component architecture models enable SOA governance
Process components expose on enterprise services, which are based on service operations
Web Services Reliable Messaging (WS-RM)
Asynchronous messaging (EO, EOIO) based on open WS standard
Support Business Activity Monitoring (BAM)
Embedded Event Infrastructure: Collecting, pre-filtering and publication of events across SAP and non-SAP systems.
Event handling: cast the local event to an event proxy to send out event messages to event Consumers.
Transaction SWF_BAM for event filtering via filter rules and event handling.
Enhancement for Mapping
Re-usable user defined functions.
Look-up function reads multiple fields.
Synchronous DB RFC lookups: Use graphical function to model look-ups.
Specify mapping parameters at configuration time.
Principle Propagation based on SAML
This feature uses the WS-RM protocol.
The implementation of this feature is based on the open standard SAML and can
be used with backend systems that support the SAML technology.
Forward user context from sender to receiver.
Authorization check in receiving system based on original user.
Support BAM Milestone Modeling (BPEL)
Sub-Process Calls: Integration Process Call,
User Interaction: User Decisions (initially not part of this project, but will be covered as well to draw the complete picture),
Alert Categories
Enhancements for Process Automation
Human interaction:
Integration paradigm (design/ configuration).
Generic user decision.
Language dependent texts for end-user display, enriched with variables.
WS-BPEL 2.0 adoption: Preview and implementation BPEL4People, BPEL-SPE Simple user defined functions can be configured directly in the process.
reward points if helpful...
PrasHanT
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
hi praveen,
From functional point, there is no difference between XI3.0 and PI7.0. There are changes only wrt SP. For every SP release on PI7.0 a corresponding SP for XI3.0 is also released.
PI is nothing but Process Integration. As XI is represented in the Process Integration layer of the Netweaver Stack, it is now PI.
In order to bring all Netweaver releases in line with each other, SAP has released XI as PI. Now it is a part of NetWeaver 2004s
A comparision of the service packs in 2004 and 2004s;
in 2004 - in 2004s
SP12 & < - SP04
SP13 + 14 - SP05
SP15 - SP06
SP16 - SP07
SP17 - SP08
SP18 - SP09
For release notes ref:http://help.sap.com/saphelp_nw04/helpdata/en/cf/9844428e9cbe30e10000000a155106/frameset.htm
regards
kummari
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Praveen,
I have worked in both 3.0 and 7.0 and didn't see any difference in IR or ID,there are some differences in SLD and RWB but everything is kinda self explanatory and hopefully u should not have any problem working in 7.0.
Most of the difference is in the interface of SLD and some changes in RWB.other than that its pretty much the same
For More information please check
Thanks
Sudharshan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
84 | |
24 | |
12 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.