Skip to Content
author's profile photo Former Member
Former Member

PI 7.0 and XI 7,0

Hi,

I was working on XI 3,0 and now I am going to work on PI 7.0, now i wanted to know what are the differences between these two versions in terms of functinality and look n feel.

If you have some specific doc's which states the difference between them, please email that to me on

________

https://www.sdn.sap.com/irj/sdn/wiki?path=/display/home/rulesofEngagement&">Rules of engagement</a>

________

Thanks and regards,

Puneet

Message was edited by: PI/XI SDN Forum Moderator

Kenny Scott

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

7 Answers

  • Posted on Dec 04, 2007 at 05:40 AM

    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:

    • Adapter Enhancements like JMS, JDBC, Oracle-JDBC and CIDX Enhancements

    • New Conversion Agent,

    • Receiver Determination Enhancements

    • Multi mapping

    • User defined enhancements

    • 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

    please visit

    difference-between-xi-30--pi-70

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Dec 04, 2007 at 05:41 AM

    Hi Puneet,

    read this thread:

    differnce-between-sap-xi-and-sap-pi

    regards,

    vikas

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Dec 04, 2007 at 05:42 AM

    hi puneet,

    there is no diff in PI 7.0 and XI 3.0 as far as functionality is concerned. There are changes in only UI of SLD in PI 7.0 , otherwise everything wrks the same way!!

    SAP released this version to bring all netweaver releases at par.

    [reward if helpful]

    regards,

    latika.

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Dec 04, 2007 at 07:03 AM

    Hi Puneet,

    Fully agreed with Latika's statement.....not much difference functionality wise...looks are different that too in SLD...just to bring EP/BW(now BI) and XI(now PI) in sync it was released..

    Regards,

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Dec 05, 2007 at 04:33 AM

    Hi Puneet,

    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.

    Thanks.

    Message was edited by:

    rama krishna

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Dec 05, 2007 at 05:55 AM
    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Dec 05, 2007 at 07:27 AM

    Thanks...the info provided is really helpful.

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.