difference between pi 7 and pi7.0

8/18/2019 Difference Between PI 7 and PI7.0

1/7

Difference Between PI 7.0 and PI 7.1

PI 7.1 is based on Enterprise SOA (service-oriented architecture) which has many eatures than

e!istin" PI 7.#.

1) Inte"ration $epository is rep%aced by Enterprise Service $epository which consists o Enterprise

Process &ui%der and Services re"istry.

') Advanced Adapter En"ine

sin" this appin" and routin" can be done in Adapter en"ine and &ypassin" Inte"ration En"ine so it

reduces process time

*) +unction ,ibraries

A%% the user deined unctions are stored in unction %ibraries and can be accessed easi%y.

) irect /onnection

It is provided in Inte"ration irectory and supports direct connection between sender and receiver

throu"h Inte"ration server.

0) appin" Enhancements

it supports Parameter appin" i.e you can use parameters in mappin" pro"ram and provide va%ues

in runtime

2) 3a%idations o data

In sender a"reement you have a option to va%idate the Incomin" data so this he%ps to Improve

eiciency.

7) essa"e Interaces are rep%aced by Service Interaces

A service interace can perorm many operations and here ater we do not see term Interace mappin"

it is ca%%ed Operation appin".

4) 5raphica% ,oo6ups

$+/ and 8&/ ,oo6ups are supported or 5raphica% essa"e appin".

9) +o%der option in ES$ : I.

1#) ;here are many new eatures avai%ab%e in cc&P.

---------------------------------------------------------------------------------------------------------------------------------------

The Various Components of Process Integration PI 7.1:

a) SAP Solution Manager


2/7

SAP Solution Manager is used to manage the entire SAP solution landscape which seems to

be a challenging task. Companies can minimize risk and increase the reliability of their IT

solutions. SAP Solution Manager helps reduce TC throughout the solution life cycle.

b) nterprise Ser!ice "epositor#

!S" is a central repository of information that contains all the ser#ices. !S" is a container$

stores all the underlying Meta data of application ob%ects like ser#ice interfaces and

descriptions. The global data types$ interfaces and business processes maintained in

!nterprise ser#ice repository which can be reuse where needed

c) Ser!ice "egistr#$S")

Ser#ice "egistry is a common pool a#ailable in SA platform where the ser#ices of an

enterprise are shared. Pro#iders publish the ser#ices in the registry and Consumers disco#ers

the ser#ices that need to be consumed. Ser#ice "egistry is the &''I part of the !nterprise

Ser#ice "epository (!S") which enables ser#ice consumers to find ser#ices.

%) Integration &irector#$I&)

The Integration 'irectory is the central tool for configuring the processing of messages$ such

as the systems and e*ternal communication partners that are in#ol#ed in the process$ the

routing rules that go#ern the message flow between these entities$ as well as the settings for

communication incl. security.

e) Integration Ser!er

The Integration Ser#er is the runtime en#ironment to pro#ide secure$ standards+based$

reliable$ and scalable communication between pro#ider and consumer applications

f) A%!ance% A%apter ngine $AA)

The Ad#anced Adapter !ngine AA! pro#ides built+in mediation capabilities to reconcile

incompatible protocols$ structural maps$ schema$ and data formats between pro#ider and

consumer applications which eliminate the need for A,AP Stack during the process.

e)SAP 'et(ea!er A%ministrator $SAP '(A)

The SAP -A safeguard the deployment and operations of the processes in order to ensure

runtime go#ernance$ security with access control$ authentication$ auditing$ enforcement of

compliance to policies$ and monitoring of the ser#ice e*ecution.

It handles !nd to !nd Monitoring$ Performance Monitoring$ Message Monitoring$

Component Monitoring$ Alert Monitoring$ Adapter Monitoring$ Cache Monitoring$ Se/uence

monitoring and 0ogging and tracing.

f) S#stem an%scape &irector#$S&)

The System 0andscape 'irectory of SAP -etea#er (S0') ser#es as a central information

repository for your system landscape. A system landscape consists of a number of hardware


3/7

and software components that depend on each other with regard to installation$ software

updates$ and demands on interfaces.

*eatures of +I ,.- o!er +I .-

1. /usiness process ob0ects (CC,PM) are introduced to design a stateful crosscomponent business process.

2. Contet 2b0ects are introduced to increase readability of routing rules instead of

ha#ing 3PAT4 e*pressions.

5. Channel Template is introduced that can be instantiated to 'irectory

6. (S&3+S&3&T& can be imported to interface ob%ects in ternal &efinition 7

+ST3 4a!a are imported to Mapping b%ects in Importe% Archi!es

8. Message e*change between A/AP Proies is introduced to impro#e performance byha#ing no ser#ices of Integration Ser#er.

9. Mapping Templates are introduced to ha#e reuse of mappings$ and to split and merge

messages for ,PM.

:. Support of pac5ages of a Soft6are component !ersion can be used in #ersioning

all "epository ob%ects.

;. &ata t#pe enhancements can be introduced to for customer specific fields.


4/7

9. Archi!e% messages can be displayed in Message Monitoring

:. Maimum concurrenc# can be defined in recei#er adapters (@I0!$ >',C).

;. 2ptimiing threa% usage is possible in >MS adapter by reusing the spare threads

from SAP >2!! !ngine


5/7

2. utput of fields and functions can be used for Multiple target fiel%s for "eusable

,etter "untime Performance

5. Tool support to ad%ust the mappings after the structure changes to a#oid structural

inconsistencies.

6. Storing interme%iate "esults in a !ariable can be possible and can be reused.

8. Complete cop# of +M sub trees is possible

9. Parameterie% mapping is useful for Channel 0ookup and "euse of multiple

mapping in Interface 'eterminations and to transfer content of Container in &'@.

:. *unction ibraries is useful for "euse of &'@ and enhanced portability of &'@.

;. raphical Support of "*C oo5up an% 4&/C oo5up is a#ailable.


6/7

c) CC/PM

1. Step 8roups= Set of steps that can be reused by embedded in Integration Process

across SCB. Step Parameters can also be used in step groups.

2. Configurable Parameters+ 'efined in Integration process and the #alues can be used

assigned in I'. 4ere Agents$ Communication channel and simple data type can be

used as parameters.

5. >ser Interaction + &ser 'ecision Step in IP with an agent configured in I' is used to

get the workflow message to make a decision

%) Configuration 2b0ects

1. (eb Ser!ice "eliable Messaging (S="M for Asynchronous messaging is

configured in Sender Agreement and Communication Channel for a considerable le#el

of reliability and security.

2. Principal Propagation base% on Securit# Assertion Mar5up anguage $SAM

1.1) can be configured in S adapter. It means user is securely propagated from a

sender system to recei#er systems. An authorization check in recei#ing system based

on original user.

5. A%!ance% A%apter ngine $AA) is used to increase the performance of message

processing by eliminating the need for A,AP stack during the process.

6. "eusable "ecei!er "ules for logical routing can be used in different "ecei#er

'etermination.

8. Cache 'otification function is enhanced to analyze the possible error.

9. +M Pa#loa% !ali%ation is possible in sender and "ecei#er agreement.

:. Publish the sen%er agreement in Ser#ice "egistry (S") for S Client and Pro#ider

connected to IS.

;. Centralie% a%ministration an% monitoring is done by SAP 'et(ea!er

A%ministrator.


7/7

difference between pi 7 and pi7.0

Documents