DPI73

DPI73
SAP NetWeaver Process Integration- Delta PI 7.3

Collection 95- Participant Handbook
SAP Education
111
111
DP173
Version 95
Material number 50106395
1.
Exercise 0: Logon and change passwords
new
and new Ul
Exercise 1: Define and assign Custom Attributes
Exercise 2: AEX configuration with IDoc__ AAE adapter
n
Exercise 3: AEX configuration (2nd scenario)
on
n
Exercise User-defined Search on AEX
Exercise 5: User-defined Search in ABAP
Page 2
DPI73
1.
rv
I ,~
I
II:
f) I 1 f
i i('
'i
''
Page 3
DP173
At the end of this module, you will be able to:

list the new topics for SAP NetWeaver Process Integration 7.3
- OP!7)
DPI73
Page 4
t~l-D<>~;.-,Oa.U<.::<omf':T-e.-.1.>
;~-"' ~-;: -~.-, w
TetE
Optimized Monitoring
--~'-
Single stack ESB capabilities through

Advanced Adapter Engine
- Up to 60% less energy consumption
- Lower footprint, easy maintenance:
1h installation*, Yz HW requirements*
comp. to dual stack, 90 sec restart*

Major Improvements for
Reduced cost of operations via
increased fault tolerance
Design governance
Standards based interoperabiHty

and connectivity
*Hardware dependent
Page 5
Major improvements are:

Single Stack ESB: Java-only installation, called AEX
111 Optimized Monitoring
111 Enterprise Services Repository Governance and usability
111 Reduced TCO
111
111
DPI73
AS Java is based on Java EE 6
w""'"'~""G
Quick access to ES Repository

content for business users
Governance features like lifecycle

management status are supported
Search and browse for objects,

subscribe to object changes
:;~~~i;;,:-.;--~.~~-~---:1
~--"''-"'''~
'-
s,'<t5>;8l
111
All ES Repository related functions are

consolidated into one perspective in the
SAP NetWeaver Developer Studio
Browse Content, Edit Objects,

Change Lists, Subscribed Objects
l_l1
s--;:f_T(5T, I t:i~Z:l",'<;<c':-rn
:n ~y. '..\'...A l
' -
- OP17:';
L, ~~--'>'~!
:llS<',c.-_~;._! r,.F~;-:.,
"
Page 8
The ES Repository can be accessed with two new User Interfaces:

111 the Web Ul, mainly for Business Users that want to have a quick and easy view on existing
interfaces
111 the SAP NetWeaver Developer Studio, based on eclipse
DPI73
ES Repository, Registry & Integration Directory
System Landscape Directory
ES Repository
SR, ID,SLD
Adapter
Engine
(Java SE)
i[ ____ ::,_:
Advanced Adapter
Engine Extended
(optional)

Mediation
Connectivity
Security
(incl. !Doc, HTTP)
Med., Sec.
Connectivity
incl. !Doc, http
Med., Sec.
Connectivity
incl. IDoc, http
I.Adapten
~
File
DB
Service
Provider
Service
Conswner
SOAP
of
Business
Partners
Page 7
AAE
.. Advanced Adapter Engine
Installed centrally on dual stack, optional non-central installation
AEX
Advanced Adapter Engine Extended
Optional installation
Stand alone or non-central
Adapter Engine
.. Java SE installation
111
Still supported, e.g. for existing scenarios
DPI73
SenderS
:1
AAE
--
~-
nregration S~rv~r
Integ~ I ~-verSys!Pm
Engine
rati. 00
r: .
Full (dual-stack) SAP

NetWeaver PI installation
Integration S~rv~r
Integration
AAE
Engine
Bypassing Integration Engine

by using the AAE only at
runtime
(as of SAP NetW(>_aver PI 7.1)
SAP NetWeaver PI 7.3:

Advanced Adapter Engine Extended
Design + Configuration +
Runtime + Monitoring
Page 8
DPI73
111
The Advanced Adapter Engine Extended (AEX) is an Advanced Adapter Engine with a local ES
Repository and an Integration Directory. In the Integration Directory you have only the objects
available that have already been used for local processing on the AAE, mainly the Integrated
Configuration object.
11
In addition, you also have the local monitors of SAP NetWeaver Administrator and it is possible
to connect the AEX to the central monitoring in the SAP Solution Manager 7.1.
You should now be able to

list the new topics for SAP NetWeaver Process Integration 7.3
Pa e 9
DPI73
DPI73
10
DPI73 Exercise 0: Logon to systems

1) Ask your instructor for information on how to logon to PC and to the SAP network.
2) Logon to WTS (Windows Terminal Server "Common Training")
http:llwts.wdf.sap.corp: 1080
->choose your region-> Training-Zone-> Common Training
\
lHAilllHG
l rummq lone
lOll~
Appl!c;~tmns
Mam
Hint: Preferences I Session settings I Display: choose "Fullscreen"

3) Logon to PI-WTS via Remote Desktop Connection (RDP)
On the WTS: Start I Programs I Accessories I Remote Desktop Connection
(xx: ask instructor)
Log on to server CB-PI73-0xx
Log on with user train-## and password initial(##: group number)
On this server (CB-PI73-0xx) you logon to the systems using SAPGUI and browser.
4) Logon to training systems
Role
System ID
Product version
Client
User
Initial Password
Language
Application Server
System number
HTTP Port
PI dual stack
RWN
PI 7.3
800
train-##
AEX
NWJ
PI 7.3
train-##
Backend SYSl
RWN
AS ABAP 7.3
811
train-##
EN
rwntdcOO.wdf.sap.corp
00
50000
EN
wdf1bmt2073. wdf.sap.corp
00
50000
EN
rwntdcOO
00
50000
## is the group number

Initial password is provided by your instructor
5) Logon to all training systems & change your initial password.

6) Compare the PI Tools homepage for RNW and NWJ.
11
12
new Ul
i. ) f i 1
ii
ill( ;
Page 13
DPI73
13

list the new topics for Enterprise Services Repository 7.3
Poge 14
DPI73
14
Metamodel:
Types & Attributes
Status: f~cc!leasecf
Description: Send Material
1) Object type(s): Create

Custom Attribute Definition
ES Builder
out
Service I
-{~}---B
2) Object instance: maintain

Custom Attribute value
Page 15
I maintain a Custom Attribute Definition (CAD), eclipse has to be used.
111
To create
111
Custom attribute values can be edited in eclipse or in the ES Builder (swing based client).
111
In the Web Ul, the custom attributes are visible.
111
In the Web Ul, only custom attributes of type Lifecycle Status can be edited.
111
Built-in support to configure the behavior of assets by

Providing pre-delivered values, setting value types
Constraints to restrict possible values (e.g. Integer Range, String patterns)
DPI73
111
Support to search based on custom attributes
111
Attributes are included in existing transport mechanisms
15
Benefits
Define a custom lifecycle for ES Repository assets with a defined transition
procedure and assigned authorizations for different users
Functional Insight
Define custom lifecycle for assets including
Different lifecycle states and possible transitions from one state to another
Authorizations to determine who can set a lifecycle status from one state to another
Assign unique lifecycle for different asset types

Provide a public Web services API to support transition from one state to another
.=.' ).(; 1 J S.~P AG .
Page 16
.. A custom attribute of type Lifecycle Status can be edited in the Web Ul.
.. Custom attributes of other types cannot be edited, but viewed in the Web Ul.
.. In addition, a custom attribute of type Lifecycle Status can be set from "outside" by an API, a
Web Service. The URL to the WSDL is
.. http://<hostname>:<port>/
CustomAttributeService_ln_Service/CustomAttributeServicelnlmpiBean?wsdl&mode=ws_policy
DPI73
16
Benefits
Subscribe to and get information about object changes in the ES Repository
functional Insight
Define subscriptions to individual object changes in ES Repository
Supported in different interfaces (Eclipse, ES Builder, Web Ul)
Provide notifications via e-mail on subscribed actions
(publish, classify, modify, delete)
Notification via E-mail to default (UME) or custom e-mail ID
Customize e-mail template
Page 17
DPI73
11
Subscriptions to object changes can be viewed and edited in all three ES Repository Uls.
11
To view all subscriptions in ES Builder, the widget in the new "context" perspective has to be
used.
17
Currently used
objects
Customized search
folders based on
search conditions
Recently used objects

(Today/This
Week/Month/Older)
Widgets
.=;2011
13
Increased developer productivity through streamlined and faster access to SOA assets
Improved user experience from an adaptive ES Repository that "learns" from usage patterns
.. The new user-centric Ul perspective in the Enterprise Services Builder eases the work by
providing a list of last used objects, search folders, easy display of dependencies .
.. You open the perspective using the new menu "Perspective I Select Perspective: Context"
A new Ul perspective tailored to your usage of SOA artifacts:
Views to capture objects that users viewed or edited
Support for creating customized search folders based on search conditions
Widget framework to support extensible capabilities as Widgets
Support for viewing outgoing and incoming dependencies
DPI73
18

list the new topics for Enterprise Services Repository 7.3
Page 19
DPI73
19
Ul
11
,~,
DPI73
2011 SAP
I 1\1
II
liJII(
Page 20
20

configure eclipse to access your ES Repository
use eclipse to display and edit ES Repository objects
create a customer defined attribute in eclipse
assign a customer attribute to a service interface
subscribe to changes on an ES Repository object
Page 21
DPI73
21
1) Specify ES Repository server
Enh!lpti::m Servin: Hnm::;-cr

-'.!~~-~---~-
Window I Preferences I Web Services:

Enterprise Services Browser
..
1~- r&-i(..-_~----~/.~;p -c-c.p
~~IX()
2) Open Enterprise Service Repository perspective

(Window I Open Perspective I Other)
3) Connect to the Server using the login credentials
_co;
2(J11 SAP .4G. PJ! (:qhls
;"""s~r\'~'..i
- DPI7:1
Page 22
You have to configure the access parameters to the ES Repository for your installation of SAP
NetWeaver Developer Studio (eclipse).
111
111
111
DPI73
Settings are configured in the menu "Window I Preferences", then area Web Services, subarea
"Enterprise Services Browser".
The eclipse perspective "Enterprise Services Repository" can be used for viewing and editing ES
Repository content.
To view the ES Repository content, you have to log on, using your user and password.
22
~h\.l~"i~:s?.;;:;:.:;.n~J.i'<~,;_g_:t_;ill-1SJi::.
r------'-'--------,
F.!C!,'<"-t\.l\1,>':-f-i_;:f'!J<':i()'Jfr)f<H(>:'-'"3~
cr.:-ge-0 c;,,- feb C>G, 2lll'~ C.;<;(lJ F11

CP.?::o:;,>.j.Qf.
:;)lllB
F;C1'>t. ')';Cl'Clc!f-c-:~.c-flt:F>c--.3-Y.:>j,-------,.,J
Advan<xd
Page 23
111
You can view ES Repository content in the browser pane on the left hand.
111
SWCV, namespaces, and object types are listed .
.. If you open an object, for example a service interface, and start to edit, for example the short
text, the view switches to edit mode, and you have to select or create a change list .
.. Change lists are listed in the below left corner of the perspective.
DPI73
23
"' m
D1fr0 t.o of d~m\J,(Qj'j')

IT) EA-IIf'Pl 60i
J-; [)} ESA ECC-5 603
;, W ESA ECCS 60i
ES Repository details from the server

get refreshed in the ES Repository
perspective
>:
., ill Gl'~_l
,: ffi JAVl<-PROJ:Y 1.0 of tra:rif"1g,.;eom
"ti DJ LCL_SWCJli:T)XMO
=; [)} LCL_SWC__RKT j'CLIPSE_Cft<))
l1:!J Wp:flp.<e<>lrH/edJ)5e/demo
Access the Software Component

Version and the namespace that is
already created in the swing client.
:~;L:;-~
', C.:::J" Event$
:.i.'
FEtt.ftff;;.$$?']-$
.t~
M-es:;a.9a Types
:;, 1::__:r 5-t-rvlce lffitrf<),_:_e:;
; ill SAP ASA 7.10

-+~ DJ SAP APPL 6.03
Note: You cannot create SWCV or

namespace in SAP Netweaver
Developer Studio
Create design objects like
data type
message type
service Interfaces
Page 24
DPI73
24
i1 ~n:~:k'-eeosi_b
'~l
it.. ~;::-~B,.~~""'h~.,~xt;.:t\:'~~n~-s=-.~-srr,.:
~r;;, Service Interface Overview
I!
<o.w"'
::~::~-ten d~l:~
tre o~-~:~;~~;-~:~::~; :~ -:~rt):~
f)r<r>ll0n~(J)
H- 5 56--i:<:n',-r,_; t'r.co;,;.-,;'::.:rc; cft\-.s ;tf'<.:e r,t~f.;.::-e
~------------------~
cvl~: '~ :~., , , ,._,.,". ;;:;~~~::~~:::;,,cj """c

;o,..,~_,,I-:<"',C'-i''"l'=::
l ~:::~:,
,-1;o.<;,<
J..,:..:; tl-i'-
'f~ '+ch-~o><: fi-,~ ~,_, .,-;>

(),..;.,
(';)'\'''''l""!On: t-.rb~.:6, J~. :.,:.l~i:J.)l ~n
<'<"e,-f;>.._i>
\.!:;JJ.--;,..ll-!,: ,,n;..,-;
I ----- "'' r,;:,. ;;;-;:",,---- -----::::~
'Atlv,w{nJ
0
i
I
lnh:HJ$.10<-'l.utr,,..ot.:~thu
U'""!!"
~J. L~-'
t" .._,e..-:, v
~J~
c;, ,L .. o..
~!
r...
u-,~
o: ''-"
t.:,.d~\."'
Service Interface Definition
).~Tt.
r:~~~Tf"U',:
V:~:~~ct(2'Di,;\:,;P,;-;,__;(,t:>;,(:<Jt/J:;EcS[G5-e
rr;.,~::~-:_;p;;~--;;r.;,~-~-;,-;r,~~,:A-1
..
-~--- ~----~------
-----
I
Page 25
1. Service Interface Overview

2. Lifecycle information
3. Advanced: in this section you can find attributes that are relevant for the PI use case
4. Operations of the service interface
5. Classifications
6. Documentation
7. Overview of service interface structure
8. Details of service operations
DPI73
25
Create a new change list or use an

existing change list.
. Clv.,nge
i:\
:i~ Wlr.e = Ll
ystem; RWN
Right click on pending

change list and activate
or reject the changes.
(\if tf/1
tf.) Reject
Page 26
.. No automatic creation of a "Standard Change List" like in ES Builder.

.. No change list necessary for custom attribute definitions.
DPI73
26
Er~erpr
! .:f. Netamo
/:\
5y>tem: RWN
''+;
<i;i Context Object
'+;
t2J Data Type
f:f ~
:,.; cifJ t\essage Type

r...; ~ .... Process Corr,ponent
Custom attribute (CA) definition is defined in the Meta

Model extension tab in the ES Repository perspective.
Data Type Enhoncemmt
;~ ~ Extern~l Defi1ttton
:,.; JJ,f'il Fott~ llessage Type
:-: (q)
~ 0
X ""
CAD can be assigned to any of the entities in the Eclipse

Perspective of the ES Repository.
SerVILe Interface
-.,. ttbf1tJl4lr!:M;tl
,, f ri Ul Text Cbject
;_t: fJ Un.:Jssigned
Attribute Definition
CAD may be associated with

multiple entities.
You can define constraints for the

attribute values and predefine
values.
h 1<;'<'-1f:'l<ttD{vtJN<! _.,,,,..,,~
0
... Ahod.>t.-dtrJ!iln
r'~Y~f"~ uUy .~;;.x.Y-;,r,~
f(t
&~tr~-.1-:: &!.~rt<:
Page 27
An administrator has to assign the ID of a Software Component Version {SCV) in which the
metamodel extensions {custom attribute definitions) are stored.
It is parameter com.sap.aii.ibrep.server.mme.swcv in the Exchange Profile that has to have that
SWCD ID.
In the ES Builder, the Attribute Definitions are visible in that SCV. The can be viewed and copied,
but not edited in the ES Builder.
DPI73
27
Defining Asset Lifecycle Model

Custom attribute definition using editors in SAP NetWeaver Developer Studio
Pre-delivered transition constraint to configure transitions from one state to another
Support to configure authorizations for each state transition

: /\Hribule 0Bfinitio.n
(:-,.tr,.:-.!J
n-, )~(,<~ r:.~) ~;;'.(1~--.,~~~.
c.,, ..... J
2B
Custom attributes of Value Type "Lifycycle Status" are special:

111
they have pre-delivered transition constraints
111
only custom attributes of this definition type can be edited in the Web Ul
111
they support the configuration of authorization for each state transition
So for example a developer may change the status from "Draft" to "In Review", but the transition
to "Review" may be restricted to an architect.
DPI73
28
(~Ne-w $ub3ctiption
Munug~
I~
Edit Submiption
SobscripHon
Sub~cr!pti-on
.>tttings fot (u.!tomerHfPUnlo1.dmgPomHhmdC:y!OQueryRespona._ln
Subscrip\ion Narne ':substrip\i.;n on Reteiving Partrl

t~obflobi!n
j~ M~Jd!fy
Em~il
id;
Notification Event
event
.._; Odeto.:
t __j
(l:usity : _j Put.l\sh
Edit Subscription
Subs('nptwn Hamc-'
und~r!yi!,g
Pi!blish
QJassil\'
Modi!\'
Qelele
Notification wit! be senllo
Em~illtl 'r~\f,ish b~\~l<rishn~n@s;,r,H'u'
\JME M:.lliD
Holifi;:;a1ion will ba sent to
@ CtJS!DI'fl Ma)IID
[2!LJ I Cancel I
Subscribe to changes to individual objects in the ESR

Support for subscribing to object-specific actions (Publish, Classify)
Notification via E-mail to default (UME) or custom e-maiiiD
Page 29
DPI73
111
Subscriptions to object changes can be viewed and edited in all three ES Repository Uls.
111
To view the subscriptions, the widget in the new "context" perspective has to be used.
111
The template for the email send out can be maintained by an administrator, using the
"Administration" link from PI Tools Homepage, area Repository, "Notification Template
Administration I Customize Notification Template".
29

configure eclipse to access your ES Repository
use eclipse to display and edit ES Repository objects
create a customer defined attribute in eclipse
assign a customer attribute to a service interface
subscribe to changes on an ES Repository object
Page 30
DPI73
30
nd
!l
d. I
enc!
:)
illil i'
II
Page~~
DPI73
31

use the Web Ul to search for a service interface definition
maintain the lifecycle status of a service interface in the Web Ul
Maintain your subscriptions in the Web U I
Page 32
DPI73
32
Web-based user interface to enable quick access to ES Repository objects

Supports key capabilities including- Viewing objects, Search and Subscription
Support for changing lifecycle status focused towards Business User
RWII: Process lnwgra!ion I ools
Search
S<ervice Interface
Page 33
DPI73
111
You can open the Web Ul from the PI Tools homepage.
111
You can search for objects like Data Types or Service Interfaces.
111
In the result list, you can navigate to further details by using the links.
33
Custom fi1etadata
$-!';rvh:;e owncr
Service Operations
Re,iewed
Service Ovmer
Udo
P.Y~zer
Service Operations
~Jr Ojf( tC et~c Uiil.tt~}-\~rsonD~)v;~( Juet Vkt:sptJnSP 1~ync iFonov:-: 1
{ Svnc!lrtA'IOU""),J
Change Description
Page 34
Having selected an object, go to the bottom of the page and click on Edit.
You can now change the Lifecycle status, and can add a Change Description.
The Change description is used in the email send out for existing subscriptions.
Note: Authorizations for Lifecycle Status are maintained in the ES Repository perspective in the
SAP NetWeaver Developer Studio.
DPI73
34
Subscribe to changes of service interface or data type

You can get notified when:
Classification is added to service
Service is published
Object is modifed
Searoh
Object is deleted
f.fll,)l[ ID
OJt (;.y-;!: Pr0'.'1\!
in for U\d
F\tHkfH-HJ:
m V1Jl
Use the UME

E-maiiiD or define
a custom ID
suoscnprion uame-,
~-
Pro;ectEsknateCost_ln
flotitic.J.tion Events
I ' ClH<l~i
' Pw<,>h
lloHflc.ltion wrfl be
~ent
t.cdof)'
c,:,t;
to;
f:-miuliO
.-:o:
111
DPI73
;?011 SAP AG. td
tf..s~:\'B::i -
OP!73
Page 35
The Web Ul offers the maintenance of subscriptions, independently from the fact where they
have been created (for example in eclipse).
35

use the Web Ul to search for a service interface definition
maintain the lifecycle status of a service interface in the Web Ul
maintain your subscriptions in the Web Ul
Page 36
DPI73
36
[J
At the conclusion of this exercise, you will be able to:

browse for service interfaces in eclipse I NWDS
create and use custom attributes in NWDS
use the ESR Web UI to browse for service interfaces
Task 1: Start the SAP NetWeaver Developer Studio (NWDS) and connect toES Repository of RWN
1.1 Start the SAP NetWeaver Developer Studio (NWDS)
Use "Start I Programs I SAP NetWeaver I CE7.3 SP03 I SAP NWDS CE7.3 SP03" (on the WTS)
1.2 Open the Workbench
On the NWDS welcome page: choose the link to the Workbench
1.3 Configure the Enterprise Services Browser to connect to system RWN
Use menu Window I Preferences: section Web Services I Enterprise Services Browser,
specify ESR System RWN on ESR Host rwntdcOO.wdf.sap.corp with ESR Http Port 50000
(Note: parameters are case sensitive!)
OK
Cancel
1.4 Open the Enterprise Services Repository perspective

Use menu "Window I Open Perspective I Other ... ", and in the "Open Perspective" dialog box, choose the
Enterprise Services Repository entry. Choose OK.
The perspective opens, and two tabs are listed: the Enterprise Services Browser and the Metamodel Explorer
(both with an ent1y named "offline").
1.5 Connect to ESR of RWN
You may connect to the ESR from both tabs. The Enterprise Services Browser offers a button "Connect to
ESR", and you have to specify your user and password. After that, the SWCVs are listed. On the Metamodel
Explorer tab, if no connection to ESR is established yet, you have to open the little plus icon nearby the
"Offline" entry to connect to ESR.
File
Edit
Navigate Search
Project
ESR
Run
Window
Hell
37
Ifthe Metamodel Explorer shows an entry "Improper Configuration", you may have to refresh the tab with the
refresh button.
1.6 Switch the grouping ofthe custom attributes
On the Metamodel Explorer, nearby the refresh button, a triangle icon offers a drop-down menu. Switch to
"Group by Categories" to see the existing categories. Switch back to "Group by Types" to see the list of types
for custom attributes.
ll q[! Context Object

I:H & Data type
i+l 15!1 Data Type Enhancement
t+J ~ External Definition
o1 Group by Types
Group by Categories
2.1 NWDS: Create lifecycle attribute "status_##" for Service Interfaces in Metamodel Explorer
2.1.1 Open ES Browser in NWDS
Assure that you are connected to system RWN in the ES Browser, see 1.5
2.1.2 Open Metamodel Explorer
Choose the Metamodel Explorer of the ESR perspective, switch to "Group by Type"
2.1.3 Create custom attribute "status_##" of value type "lifecycle status"
Right-click on the node "Service Interface" and choose "New Attribute Definition"
Enter "status_##" as Name, "##"as Categ01y, and select "Lifecycle Status" as
Value Type from the drop-down menu. Choose "Finish" to create the attribute.
' Enterprise Serv
Met<l'OOde! Exp!
:Sy$tero: RWN
+; o, j Context Obtect
} -+l
+]
+1
ni. UI Text Object

Unassigned
2.1.4 Maintain values for custom attribute "status ##"

In the Attribute Definition, in section Values, enter the following values:
draft - in review - approved - rework required
38
2.1.5 Maintain constrains for custom attribute

Accepts Multiple Input Values
Switch to the "Constraints" view (tab on bottom of view) and add the following
constraints using the "Add ... " button, and selecting the (one and only available)
Constraint "Transition Constraint":
Source state
Target state
Initial
draft
draft
in review
m review
approved
approved
rework required
Note: it is possible to assign authorizations for transitions, this is not used here.
2.1.7 Save the custom attribute
Save the attribute "status_##" and check if it is listed in the Metamodel Explorer.
2.2 NWDS: Set the status of attribute "status_##" to draft for Service Interface Customerlnformation_Request of
SWCV SC_BIT_MAP 1.0, namespace http://educationsap.com/pilmapping##.
2.2.1 Open Service Interface Customerlnformation_Request
On Enterprise Service Browser tab: open SWCV SC_BIT_MAP 1.0 -7
http://educationsap.com/pi/mapping## -7 Service Interfaces -7 Customerinfonnation_Request and open the
object overview with a double click.
2.2.3 Create a new change list
In the Service Interface Overview, open the section Custom Attributes, select your attribute "status_##" and
use the button "Edit". The popup window "Select Change List" asks for a change list, you will have to create a
new change list with button "New ... ". Name the change list CL_CA_## (or any other name) and choose
"OK". Now this change list is listed and you can proceed with "OK".
~
.... clas
Define
r
39
2.2.4 Set the custom attribute "status ##" to value "draft"

A new popup window "Edit Attributes" appears in which you can use the drop-down menu to select the value
"draft" for the custom attribute. Save the change. Check that your custom attribute now lists the value draft in
the Service Interface Overview.
ltl (_"Qj Customerlnforrnation_p,
~customerinformation_Provide
status23:
~
J
Reset
Cancel
2.2.5 Activate your change list CL_ CA_##

Open the Change Lists view below the ES Browser, select your change list CL_ CA_## in the SWCV
SC _BIT_MAP, and use the right-mouse menu to activate the change list.
Hint: in NWDS, use menu ESR I Refresh Attribute for a refresh.
,-,~,,-~~,-~,~----'"
---~,,-~~
~,._c
__
,_,~,
Change Lists 1::3 ,

;system: RWN
[-J
_ Pending Change Lists

'~i
rn
1.0 of bit420
i*.l
2.2.6 Optional: check the value for the custom attribute in the ESR swing client (ES Builder)
Open the "classical" ES Builder for system RWN, open SWCV SC_BIT_MAP 1.0, open the Service Interface
Customerinformation_Request (http:lleducationsap.comlpi/mapping##). Use Menu View I Custom Attributes
to display the custom attributes below the Operations section.
Hint: you may have to do a refresh with menu Tools I Refresh Attribute Definitions.
(!}) Dis111ay Service lnte

Name
Namespace
Software Component Ver
Description
3.1 ESR Web UI: Open the Web UI for the Enterprise Services Repository
3.1.1 Use the link on the RWN PI Tools page
On the PI Tools page for system RWN, choose the link Enterprise Services Repositmy I Web UI. Logon with
40
your user train-# and the password from RWN ABAP stack client 800.
RWN: Procris.s Integration Tools
[]'
Enterprise Services
Enterpri:3e. ::;ervicec: Guii>Jer
:::;ervic e3 F:e~ustrv
3.2 ESR Web UI: Search for the service interface Customerinfonnation_Request
3.2.1 Search for "Customerlnformation_Request" as type Service Interface
Type the service interfaces name into the search field. Keep only the checkbox for Service Interfaces selected,
and press enter. On the result list, use the link to the service interface (in the correct namespace
http://educationsap.com/pi/map~ and SWCV!) to get the details for the object listed.
Home
Search
Cih~r::
Su!IWdf~ CUIIIIJQIWH~
Vt!f'>lllll
3.3 ESR Web UI: Set the attribute "status ##"to "in review" and add a comment
3.3.1 Switch to edit mode and set the custom attribute to "in review"
The status of the custom attribute is listed in the section Custom Metadata. Below that, under "Service
Operations", is the edit button. Use it to find the drop-down menu that you defined earlier in NWDS. Enter a
change description and save your settings.
r II Ji
Object OvervievJ
Technical Data
Custom liletadata
draft
draft
Service
41
0.1 ESR: Check the GUID of Software Component Version SAP BASIS 7.30
0.1.1 Logon to the Enterprise Services Repository of the RWN
Open the PI Tools page ofRWN, e.g. by using transaction SXMB_IFR
Use the link Enterprise Services Repositmy I Enterprise Services Builder
Logon with your user train-## (and the password ofRWN client 800)
0.1.2 Display Software Component Version (SWCV) SAP BASIS 7.30 details and check the ID
In the SWC hierarchy, open the node SAP BASIS and double-click on SAP BASIS 7.30
The ID is listed under the name of the SWCV (8ed90f952da4lldea915d23a0a424100)
E!lil
l[iew
Toojs
Local Software Component Versions
~ @ BIT400_XX ofeclucation.com
f
f
@
@
@
ESA ECC-SE
ESM INTEGRATION
JAVAPROXY ortraining.com
f @SAP ABA
f
Objects Are Original Objects
@ SAPAPPL
Use ortnterface Objects
~@SAP BASIS
>
Gd SAP BASIS 7.10
Original Language
&CL~~~~~~E~T}~9:1
Permittee! Target Languages for Translations
0.2 Exchange Profile: Check that this GUID is set as property com.sap.aii.ibrep.server.mme.swcv
0.2.1 Open the Exchange Profile for system RWN
On the RWN PI Tools page, use the link to Administration. On the PI Administration page, use the link
Prope1iies Administration I Aii Properties (or Properties Administration I Exchange Profile).
SAP NetWeaver"
HWtl: Process lnlegr<ltion Tools
Enterprise Services Repository
[J
Integration Directory
0.2.2 Search for the property

The Aii Properties page can be used to search for the property and to display it: in the table header, just enter
the Key "com.sap.aii.ibrep.server.mme.swcv" and press enter. The key and value pair is displayed if it was
maintained before (no edit possible). Compare the value with the value of step 0.1.2. To maintain the property,
you have to use the Exchange Profile.
Reposffory
Directory
System Information
Soft\Nare Build lnfonn::-dfon
General !nfornV'ltion
Us:et fv1an3qement Enqine
,.D.,:~siqnment
llotification Template Administration

Customize tlotitic:ttlon Tempktte
lock and Cache Administration
42
0.3 On the AEX, the property has to be set in the Java System Properties of the NW A:
Configuration I Infrastructure I Java System Properties: Service XPI Service: All Config Service
(in our NWJ, the property is not yet set)
Favorites
-;;:?Java
Sy,tem Properties- SAP NetWeaver Adminis ...
System Properties...
c;>
Restore
Page
Safety
Tools
History
Search for:
Applications
VI.! Environment
'iO
Memorf VM Parameters
System VM Parameters
Service Component l!ame
)p XPI Ser.. ice: All Con fig Ser.ice

com.sap.aii.utilxi.cfg.S'lC
XPI Service: All Con fig Ser.ice
Extended Details
Properties
'iQ lJl Name
lf.
De faun Calculated Value
Modifiable Online
Custom Calculated Value
com.sap.aii.itrep.sEwter.mme.swcv
cam.sap.aii.ibrep.server.mme.sNcv
8"d90f952da411dea915d23a0a424100
43
44
I:
Jl
IZ
Paqe 45
DPI73
45

explain the purpose of the installation option AEX
list new functions of the Advanced Adapter Engine
Page 46
DPI73
46
Leaner SAP NetWeaver Process Integration

installation alternative
AS Java with
ES
Local Monitoring of SAP NetWeaver Administrator
Repository
LocalES Repository (connected to an SLD)

lntegr.
Directory
Routing
Mapping
Local Integration Directory with the option to

configure Integrated Configuration
No ccBPM, no WS adapter
SLD
No upgrade path available from older releases

Messaging System
Installation takes about half the time as dual stack

system installation
NWA
Hardware requirements are about half as high as

for dual stack system
- 0Pf7J
Page 47
"'AEX does not support ABAP functionality, like ccBPM, or WS adapter.

"' Furthermore, there exist some restrictions due to the fact that the AEX is configured with an
"Integrated Configuration" object:
Integrated Configuration does not support parameterized mappings (like the Interface
Determination does)
Integrated Configuration does not support dynamic receiver determination (content-based
routing, like the Receiver Determination does)
"'But the Integrated Configuration does support Multi-Mapping based message split, that is
splitting the message for one receiver into separate parts (see later in this section).
DPI73
47
Benefits
Highly petiorming business processes based on faster message processing on a
wider set of protocols
Ability to leverage the high performance capabilities of the Advanced Adapter Engine
for IDoc and HTTP message traffic
Functional Insight
New Java based adapter types for IDoc and HTTP in the Advanced Adapter Engine
Currently, the Java based I Doc adapter does not have the
complete functionality of its ABAP based counterpart.
Example. The Java based !Doc adapter does not support
systems with multiple code pages {MDMP), qRFC
Pnge 4G
111
DPI73
The Advanced Adapter Engine AAE (as well as the Advanced Adapter Engine Extended AEX)
supports IDoc- and HTTP adapter.
48
Benefits
Accelerated and resource friendly message processing for complex scenarios
Ability to leverage the high performance capabilities of the AAE for message based
split scenario
Functional Insight
Ability to split an outbound message in parts and send to multiple receivers
via a single 1:n mapping
Possibility to split the message using complex payload conditions
Messages are sent via the same AAE.
Receiving interfaces must run on the same system
Poge 49
.. The Integrated Configuration does support Multi-Mapping based message split, that is splitting
the message for one receiver into separate parts.
DPI73
49
Examples of basic communication patterns thal can be

t~eceiver
for the Advanced .1\dapler Engine:
split
Sender
AAE
Inbound-Interface 1
D
D
Inbound-Interlace 2
1:n multi mapping
I
sender
AAE
Inbound-Interface 1
Inbound-Interlace 2
Inbound-Interface 3
Page 50
.. Receiver split (not dynamic) was already supported on the AAE.
DPI73
50
:/' Edrt lnteurated Configuration
Q Oispi3'J Orer ?Jt!Ofl Mapping (Software component wrskm cannot be cllanqedl
Sender
Communication P;utr
llFMSP~ie
r,::vrmw"'rnsp;nJHlS
Gc.-:ttHr~ Cornp)n<:r!\Vei~H!n
}l.t.P_8<'.-'HPLES SViC'/ I 0 of 'Hn
aile
Communication Component
lntetface
r<amespace
"htlpJimullimapp"tngsns
Receiver
t~?m~sP<~~_.-:(:v..-are
Communication Part,
G_ Qf_\UIH?nce
liltpl!mv\tma PAP _E\I:;.!J Pll
Communication Component i
D-escriptiOn
Inbound Protesstng
,,
Receiver '
Receiver
'communication Component
1 lrype
!Communication component
:Jcommunlcalion Component
8XT_100
Yf>tUO'\
I''i
Operation
UserMasterDB_Out
Rece-iver Interfaces
[~[[j]
Ooer a:tion Maor:f1o
userSQLt To User
- -
! Name ""
cJlt USER- t - in
11 ;
' EmploYBe_ln
:Namesoace
htlp:Jimultirnappingsns
htlp:ilmultrmappingsns
ISofttvare Comoonent Version
'MultlolieftvMAP _EXA.MPLES_SWCV LO of sap O""unbounded
Ml\P_EXI\J;IPLES_SWCV 1"0 of sap O."tmbounded
Two different split messages are routed to the

corresponding inbound interfaces of receiver BXT_1 00.
Page 51
"'The screenshot shows that in the Integrated Configuration, tab Receiver Interfaces, an Operation
Mapping is referenced that references a Multi-Mapping, and so splits the message into two
parts.
DPI73
51
Benefits
Faster and more reliable enforcement of message payload compliance
Automated and simplified configuration of XML schema validation
Functional Insight
New automated transport and synchronization of XML schemas from the ES Repository
to runtime cache
Visibility into the synchronization status of XML schemas from the PI monitoring
environment (Cache monitor)
o Due to a JDK limitation, for IDoc scenarios

ma x o c c u r s
parameter has to be modified

(<5000) to use XML validation. This applies
also for unbounded IDocs.
_~; ;l(J
11 SAP AG. C.. 11
Page 52
XML Validation does not require any more to store the schemas (XSDs} as local files on the
server directory.
111
DPI73
"Transport" means that the schemas to be validated are taken from Enterprise Services
Repository and stored in the Cache Monitor. The monitor is visible in /pimon, area "Monitoring I
Mapping Runtime-> Cache Monitor-> XML Schema".
52

explain the purpose of the installation option AEX
list new functions of the Advanced Adapter Engine
Page 53
DPI73
53
I,
<
;j I( J
Ul!l
DPI73
ill
54

List use cases for the AEX
List limitations for the AEX
Page 55
DPI73
55
AEX stand-alone
Using AEX as lean, low-cost integration
middleware
Using AEX as test environment
AEX in combination with SAP NetWeaver PI

Separating landscapes for different regions or
organizations of an enterprise
Separating network zones
Note: May require sync of design and/or configuration
content w/ suitable transport scenarios
Page SO
DPI73
56
Using AEX as lean, low-cost integration middleware

Fundamental-to-advanced messaging capabilities for SAP and non-SAP integration
(no immediate or major BPM requirements)
High performance and robustness
Avoid larger system resource and operational footprint and TCO of dual-stack PI installation
,~
2(J1 ! SA.P t..G.
Page 57
Using AEX Stand-Alone
DPI73
111
This use case is suitable in the following situations (examples):
111
Using AEX as "lightweight" and low-cost integration middleware
111
For scenarios that require only connectivity capabilities provided by the AAE and that do not
contain any integration processes (cross-component BPML you can choose the installation
option AEX which is technically based only on the AS Java. In former releases, also for those
scenarios a standard installation of SAP NetWeaver PI (technically based on both AS Java and AS
ABAP) was required.
57
Separating landscapes for different regions or organizations of an enterprise

Subsidiaries in different region or organization require "local" integration solution with local
design and development or independent operation
Global or central integration requirements via dual-stack PI
PI
AEX
PI/AEX
Business System
Page SB
"'This is a "federation" option and valid use case. However, recommendation would be to utilize or
investigate De-central adapter engine (distributed) deployment first before jumping to isolated install
with AEX.
'" Using AEX in Combination With an Additional SAP NetWeaver PI Landscape
"'You can connect your AEX-based landscape to a landscape that is based on SAP NetWeaver Pl. The basic
communication options are illustrated in the following figure:
11
Separating network zones
11
As an example, you can set up a landscape based on an SAP NetWeaver PI standard installation for your
security-critical scenarios. You can add an AEX installation in your demilitarized zone (DMZ) that is used
for the external communication. Between the AEX in the DMZ and the "PI standard system", you can
easily configure a change of the transport protocol in order to provide maximum security.
"'Separating landscapes for different regions of an enterprise

11
As an example, you can use landscapes based on AEX as cost-saving integration solution for the regional
business processes and a PI standard installation for the central processes of an enterprise.
"'Caution
" When you use AEX in combination with a landscape based on an SAP NetWeaver PI standard installation,
you carefully need to take into consideration all implications that come along also in case of federated PI
landscapes. For example, the content of the individual ES Repositories (installed with the AEX on the one
and with the standard PI system on the other hand) is not aligned automatically so that suitable transport
scenarios have to be planned.
DPI73
58
Separating network zones (A2A and 828)

Set up a landscape based on an SAP NetWeaver PI standard installation for your securitycritical scenarios
Add an AEX installation in DMZ that is used for the external communication
Easily configure a change of the transport protocol between AEX and PI in order to provide
maximum security
. High Security Area

Internal Network
Application
Gateway
SAP
Applications
Page 59
.. This also is a "federation" option and valid use case ... and a variant of the previous slide.
However, recommendation would be to utilize or investigate De-central adapter engine
(distributed) deployment first before jumping to isolated install with AEX.
DPI73
59

list use cases for the AEX
list limitations for the AEX
Page 60
DPI73
60
on

Create an Integrated Configuration for the AEX
~~~
Use Multi-Mapping in Interface Determination of the AEX
~~~
Configure the Java IDoc Adapter on the AEX
~~~
Monitor the message flow in the AEX during runtime
In your project, you have installed the Advanced Adapter Engine Extended (AEX). Now you have to
configure a scenario where a message has to be routed to an ABAP target system as an IDoc. In addition,
several parts of the data have to be saved as separate files.
NWJ (AEX)
!Doc AAE
-~
........
HTTP AAE
Configure a scenario on the AEX where a Booking Order Request (send via HTTP) from your Agency
(Agency_##) is forwarded to system SYS 1 and AgencyTracking using different interfaces.
61
Configuration Scenario
AEX_Flight_Scenario_##
Sender System
Sender Interface
Sender Interface Namespace
Sender Communication Channel
Agency_##
BookingOrderRequest_Out
http://flight.com/agency
HTTP _S_Agency_##
Communication Channel for SYS 1

RFC Client Parameters
Destination
Comm. Channell for AgencyTracking
Target Directory
File Name Schema
Comm. Channel 2 for AgencyTracking
Target Directory
File Name Schema
Comm. Channel 3 for AgencyTracking
Target Directmy
File Name Schema
Integrated Configuration
IDOC- R - SYSl ##
Default (Recommended)
IDOC PI 811
File_R _BookingRequest_##
/usr/sap/trans/tmp/AgencyTracking/BookingRequest
BookingRequest ## oxml
File_R_ FlightData_ ##
/usr/sap/trans/tmp/AgencyTracking/FlightData
FlightData ## oxml
File_R_PassengerData_##
/usr/sap/trans/tmp/AgencyTracking/PassengerData
PassengerData ## oxml
Sender Communication Component

Sender Interface
Sender Interface Namespace
"Inbound Processing"
Communication Channel
"Receiver"
Receiver 1
Receiver 2
"Receiver Interfaces"
SYS 1 - Operation Mapping:
AgencyTracking
Agency_##
http://flight. com/ agency
"Outbound Processing"
System & Interface:
AgencyTracking BookingOrderService_In
AgencyTracking FlightDataService_In
AgencyTracking PassengerDataService_In
SYSl FLIGHTBOOKING
0
HTTP S Agency ##
SYSl
(Condition TrackingOnly =false)
AgencyTracking
"BookingOrder_Agency2AirlineiDoc"
Operation Mappings "BookingOrderService" and
"Split FlightData PassengerData"
Communication Channel:
File_R_ BookingRequest_##
File_R_FlightData_##
File_R_Passenger Data_##
IDOC R SYSI ##
Hint:
Replace ## with your group number
The objects written in bold have to be created during the exercise
62
1. Log on to the Integration Builder of the AEX (System NWJ).

a) Open a browser window and use URL http://wdflbmt2073.wdfsap.corp:50000/dir
b) Use the link Integration Directory I Integration Builder, and log on user train-##.
SAP
NetWeaver~

Enteq~'!l-:c,e ~::;er/1(8'3
Builder \ V>./8\:t !_!I
2. Create a Configuration Scenario AEX_Flight_Scenario_##.

a) Use menu Object I New, select CoJ?fzguration Scenario, enter AEX_Flight_Scenario_## as name,
keep "No Model" for "Type ofES Repository Model" and choose "Create" .
., Configuration
,}' Configuration Wizard
"" Collaboration Profile
Party
Business Component
);;~ Communication Cl1annel
..,. Collaboration Agreement
;j Integrated Configuration
..,. Configuration Objects
~'1] Value Mapping Group
"" Administration
(g) Configuration Scenario
00
(g) Configuration Scenario
AEX_Fiigtlt_Scenario_:
Description
Add to Folder
TYJ!e of ES ReJIOSitory Model
@) No Model
0
0
0
SAP Process Variant Type Model

Process Integration Scenario
SAP Process Component Interaction Model
3. Create Business Component Agency_##, assign BookingOrderRequest_Out (http:llflight.comlagency)

as outbound interface. Save the Business Component. Create a Communication Channel
HTTP _S _Agency_## of type HTTP_AAE I Sender for Agency_##.
a) In the Scenario AEX_Flight_ Scenario_##: use the button to create a new object
(Q) Edit Configuration Scenario
AEX_Fiigtlt_Scenario_:
Description
b) Select Business Component, enter Agency_## as name, and choose ,Create"

c) Switch to tab "Sender" and use the F4 help to select the outbound interface
BookingOrderRequest_Out from namespace http://flight.com/agency.
63
.Q.omrnunication Component
EQit l,:'iew
Edit Communication ComrlOnent
Statt
'Agency_23
Other Attributes
Search Criteria
value
[Attribute __ _
[Software Component Version All Versions from SLD
Outbound
rategory
BookingOrderRequest_ Out*
[Name
Searc11 Result
[]
!:=J
Search
[i\~~~e ;~~~~~~~---~[so~ar;c~m~!c~i
10 BookingOrderReque... http:llflight.comlagency IFLIGHT_BOOKI... Out... I
]
'BookingOrderReque ... httpJisap.comlxiiXIIDem ... SAP BASIS 7.30
out..!
.
d) Save the Business Component now.

e) In the section "Communication Channels" below, use the button to create a new channel named
HTTP_S_Agency_##
Jut r'arty
Business Cotnflonent
Outhoumllnterfaces
~]
1el
IN~Il1~ -- ~
---- ------
~-o~kin~O~cle~~equest=-O~tt______
est_Outl I
\sync_Out I
http:/fflightcorn/agency
15
l5
"" Configuration
;;.:> Configuration Wizard
...- Collaboration Profile
't;>a. Communication Channel

Party
'*
00 Party
0 Business Component
Agency~##(
Communication Ct1annel
'HTTP _S_Agency_##
't;>a. Communication Channel
Description
f) Specify the name as HTTP_S_Agency_##, delete the"*" in Party, and choose "Create".
g) Choose Adapter Type HTTP_AAE and keep all other parameters as default.
h) Save the Communication Channel. You may close the objects. Save the configuration scenario as
well.
4. Create a Communication Channel "IDOC_R_SYSl_##" for Business System SYSl of type IDoc_AAE
Receiver.
a) In the Scenario AEX_Flight_Scenario_##: use the button to create a new object.
64
b) Select "Communication Channel", set the Communication Component to SYSl. Enter

IDOC _ R _ SYS 1_## as name for the Communication Channel, choose "Create".
c) Choose Adapter Type IDOC_AAE, switch to type Receiver. Keep the RFC Client Parameters
selection to "Default (Recommended)", enter IDOC _PI_811 as Destination.
: RFC Client Parameters

RFC Client Parameters
Destination-
IDOC_PI_811
Release and Version Info

Interface Version SAP Release
730
d) Switch to the Advanced tab and choose "Apply Control Records from Payload".
RFC Parameters
Optional Parameters
Advance Orltions
Control Record in IDoc XML -
D Apply Sender from Payload

D Apply Receiver from Payload
e) Save the channel. You may close the object.
5. Create three Communication Channels (type File Receiver) for Business Component AgencyTracking.
b) Select "Communication Channel", switch the Communication Component to AgencyTracking,
enter "File_R_BookingRequest_##" as name for the Communication Channel, choose "Create".
c) Choose Adapter Type File, and switch the type to Receiver. Keep the settings for Transport
Protocol (File System NFS), Message Protocol (File), and Adapter Engine (Central Adapter
Engine).
d) Set Target Directory to "/usr/sap/trans/trnp/AgencyTracking/BookingRequest" and the File
Name Scheme to "BookingRequest_##_.xrnl". Save &close the channel.
65
ldentit1ers
Module
!File
[t1ttp:llsap.comfxifXI!System
''
Transport Protocol
fl'
Message Protocol
Mapter Engine
. ,, ,
Processing
Advanced
File Access Parameters

1
/usr/sap/transltmp/AgencyTracking/BookingRequ
e) Repeat the steps for two additional channels:

Channel File_R_Flightdata_## with File Name Scheme FlightData_##_.xml and Target
Directory "/usr/sap/trans/tmp/AgencyTracking/FlightData", and channel
File_R_PassengerData_## with File Name Scheme PassengerData_##_.xml and Target
Directmy "/usr/sap/trans/tmp/AgencyTracking/PassengerData".
f) Save and close the 3 channels. You may save the Configuration Scenario as well.
6. Create an Integrated Configuration for the scenario
b) Select "Integrated Configuration".
For the sender parameters, use the F4 help to maintain the following parameters:
Communication Component:
Agency_##
Interface:
Namespace:
http://flight.com/agency
Choose "Create" to create the Integrated Configuration.
c) "Inbound Processing": use F4 to select the existing channel HTTP_S_Agency_##.
d) "Receiver": use F4 to select AgencyTracking and SYSl as separate lines. For SYSl, maintain the
condition "TrackingOnly=false".
Edit Integrated Configuration
Status
.In Proces
Displayr
Sender
communication Party
Agency_23
Interface
Boof;ingOrderRequest_Out
Namespace
'http:hllight.comlagenq
Receiver
Communication Party
Description
communicatio~ -:.rc~~~~;~~ic-;i,~~ gor

. (lp1
BookingOrderRequ~~,Jf~~~o-;-:r;;-~2]
AgencyTracking
SYS1
66
e) "Receiver Interfaces"
Select Receiver SYSl and use F4 for the Operation Mapping to select
Booking0rder_Agency2AirlineiDoc. (Note that the receiver interface
FLIGHTBOOKING CREATEANDRESPOI is automatically derived from the mapping.)
Select Receiver AgencyTracking and use F4 help to select the Operation Mapping
BookingOrderService in one line, and in a second line the Operation Mapping
Split_FlightData_Passenger Data.
Inbound Processing
t=~,~~"1
Outbound Processing
b,~JL~,<~~,d
ConclitiOtiEI
o~~Jation Ma) in
Boo k:i ngOrje rS er.;i ce
t
Split_FiiglitOata_PassengerData
=c-="~=,-,,=,=-~'<~=~~'~'~~~"="~"
,.. Boof;ingOrderSer.,ice_ln
,.. FlightDataSer.;ice_ln
PassengerOataService_ln
l1ttp:/
f) "Outbound Processing"
In the list of receiver interfaces, assign the following Communication Channels:
AgencyTracking BookingOrderService_In
File_R_ BookingRequest_##
AgencyTracking FlightDataService In
File_R _ FlightData_ ##
AgencyTracking PassengerDataService_In
File_R_Passenger Data_##
SYSl
FLIGHTBOOKING . . .
IDOC R SYSl ##
vonu:nun1cauon 'f~~~~~:-':':'Jlil~~~~~~~l~ ,~,
~~ <~,~~-~
INa
hi!J:
PassengerDataService_ln
hiiJ:
hiiJ:
FLIGHTBOOKING_CREATEA~IDRESP,FLI<<.
urn
g) Save the Integrated Configuration. You may close the object, and save the Configuration Scenario
as well. Activate all objects in the Change list.
Send a message to the AEX and monitor the message flow.

1. Open the "HTTP client for RKT 7.3".
a) Your instmctor will tell you where to find the HTTP client.
2. Replace all occurrences of XX with your group number## and send a message.
67
a) Replace XX for the Sender Service.

b) In the payload section, you may set your group name in the field Surname as well.
c) Specify your user for AEX (System NWJ) as user id, and set the password.
Use the "Send" button to send a message to the AEX. Since the scenario is asynchronously, you
will not get responds. Just check for any error messages.
RAPI73_1inks
RAPI73: Bll!lli (dual stack) - NWJ (AEX) {tiTfP client]
Client Http Adapter foi' PI 7.3

Header
ServerHost
SenderServic
_ wdilhml2lll:l_w f.sap.corp
jAgency_;o(
ServerPort
QOS
Senderlnterfa e BookingOrderF equest_Out
SenderNac
user id
password
studentX:<
Optional Panuneters
\senderParty
3. Monitor the message flow in the AEX and check the file folder
a) Open the PI Tools page for AEX (System NWJ) and use the link to "Configuration and
Monitoring Home" (quick link /pimon)
SAP
NetWeaver'~

:::,.;:rvtc.::s BuJ!G'?f l
Ul
[]
En!erpns~
.St>fVlC'3~
F::0291-=-h.
System Landscape
b) In the opening window, choose the Message Monitor.

Monitoring Home
System: HWJ
Monitoring
Adapter Engine
Configuration and Admioislra!ion
Mapping Runtime
Display messabproce-sslng including aggregated
and detaile-d information about s-tatus of messages.

!dentlf>l errors in message processing and perform
68
c) In the next window, you should switch on the filter row with the button left hand:
Enter your Agency_## in the column ,Sender Component", and press enter to use that filter.
Message Monitoring: Monitor Messages
Message Status Ove!View
Database
Archrve
[_J
Time Range: l26.012011-DI 0000:-2701.20 II 0I 00 00
Overview of Messages and their Statuses
liD
Error
Scheduled
Success
Canceled
'
Sender Party ' ender Component
Receiter Party
Receiver Component
Interface
.'<gency_X,\
t1
Agency_)(,\
AgencyTracking
4gency_XX
AgencyTracUng
Bockin gO rd erS erv ice_In
Agenc~r_XX
Agenc\'Tracking
FlightDalaSerlice_ln
:;:
.Q
Agency_X,'\
Agency;-racl,ing
PassengerDataService_ln
Agency_Yv\
SYSI
FLIGHTBOOKIIIG- CREA~EAIIDI
d) Open the share where the File Communication Channels write the files. Use the Start Menu on the
WTS ("Start~ Programs~ XI Server Connector~ tmp on wdfblmt2073") and use "kpsuser"
with password "training" to open the share.
5ymantec p<Anywhere
,:::J
WebEx Recorder & Pklyer
Crystal Repo~ts Viewer 2011
e) Check all three directories to see your files created:
69
'_:-, BookingRequest_XX_20110118-172155-330.xrnl
, BookingRequest_XX_20110119-130538-665.xrnl
BookingRequest_XX_20110121-152118-967.xrnl
::d BookingRequest_XX_20110126-154901-522.xrnl
f) Logon to target system SYS 1 (System R WN, client 811) and use transaction BD87 to check for
your incoming IDoc.
IDoc Sel~ct!on
.[;dit:
oto
_;i_ett1ngs
System
!:!~lp
<l
Status Monitor for ALE Messages
~
113 'ii5 Select !Docs
.)ifDisplay !Docs
aitTrace !Docs
!Docs
T
@Process
!Doc Status
c:Y?_jii~_s3~~I~iJ9~~-~~:~_-_-_-_-_-_~_~_-_-_-_-_-_-_-~=-~::.-.-.-~.-.--~.-~---_-_-_-_-_~-~--_-_-_-~~~~=-~--_---_~_-_-_-_~-~--~-~==-~-_-_-_-_-_-_-~~-~-~--~-----~ ......,____________.
'iP Chonged On is in the range 26.01.2011 to 26.01.2011
.,. ~ ERP System
0 Application document posted
113
FUGHTBOOKING_CREA TEANDRESP
!d_ser
53
RUBARTH
_Besponse Time
265 ms
Interpretation Time
249 ms
Round Irips/Fiushes
2/1
g) You may use transaction WE09 to search for the content ofyour IDoc.
70
lll'
::I
Page 71
DPI73
71

configure the IDoc_AAE adapter
Page 72
DPI73
72
Overview of Features
Enables IDoc connectivity for "local" AAE processing (as well as "classic")
Integrated with channel monitoring for administration (unavailable for ASAP-based adapters)
Specific IDoc Monitor for monitoring I Doc message traffic and metadata processed on AAE
Supports sender IDoc Packaging and IDoc flat file modules introduced in 7.1 EHP1
Integrated with RFC destinations in NWA (reuse connection across channels)
Metadata connection details can be provided in the channel (in addition to default)
ALEAUD support
Page 73
DPI73
73
Modes of Connection
Default
Uses RFC destinations
Connection details are decoupled from channels (central gateway used)
Recommended
Manual
Enter connection details in channel configuration
Can affect performance as separate connection is created for each channel
From NWA
Configuration taken from specific resource adapter configuration from NWA
For debug/test only
RfC Se!Wr Parameters
Ack Destination
Page 74
111
For default mode, sender channel, nothing has to be further specified (though it can)
RFC destination can be specified for Senders expecting an ALEAUD (configured in "Ack
Settings" tab and based on system or application acks received by PI (these get converted to
an ALEAUD by adapter).
111
For default mode, receiver channel, a RFC destination has to be specified for the target system
RFC destination is configured using NWA, which can be shared therefore results in better
resource utilization
DPI73
74
NWA
Application Resources: Overview
Configuration
Infrastructure
~Application Resources
~
Resource List
LG~~~&.e~:!J3~-~~~~~J-
Default Mode
lfo
Configure central gateway

for all sender IDoc
connections
St1!~
\i?
~tcuq1
int-:iundRA
JCA Re:s.curce
ifl-tvtJndR.A.
Res,ovrce tu:fap-ter
ht~tmdPA_Cf
JCA Conne~t>ol'l Factory
Senders can optionally

configure sender side
gateway and use "Manual"
mode for channel
' "} RtM!Jftd Hl!f~
.on factory
Resource Oetails
- ---inboundRk-- --
-1
Resource Adapter
! s,-..)
Uessilge listeners
Chn }a<'~ 't)'79 S!inq
:~u~oc_rrr.t.'!.Xt.:r~?D
Cfi.l:>s_iaaliln?h!e;cr
10
l:ll.ss_hva Un9 Slr'ng
XLCDt_t:HA\Jli_C~~i~l4."ft:Jii
(>.nsj3a tang
Str~l9
scrrehost
C1,)i$ wa llr.y Stn<g
- DFl73
DPI73
Page 75
75
3 Modes of RFC Server

Configuration
\ABIJlrm!l!
Default (Recommended)
ldentlfters
Map\et Type'
Module:
IDoc_.".A
0 Recer<e-r
Senr.ter
Transport. Protocol
t:lp~~~~1_t.
Message P1(Hoco1
Adapter Eng me
Ack destination can be specified

ALEAUD
Ack Settings tab for acknowledgement
type
Other Settings
Sender Packaging
EOIO enablement
RFC Paratueters
RFC SM'~' P~r~met~rs
Defilull(Recommended)
efau/1 (Recommendetl)
RFC Server Parameters
i',ck Oesltnalton
Jnhound Message Sehl!JS
0
0
Multiple !Docs In Single ;<t Messaye (or IDOCXML)

EOIO enabled
Ackuowlectuement Parameters
0
0
0
0
0
Syslern Ack Ok Requested

System A(k Error Requested
AppliCation Ack Ok Requested
~,ppllcalion
Jl,ck Error Requested
ALEAUD Special Handling Needed
Page 76
DPI73
76
Target destination required

Created in NWA and referred to
in channel
RfC Parameters
RFC Client Parameters '
RfC Client Parameters
Metadata can be retrieved

from alternate SAP system
Destination
XU DOC _DEFAllLT _DEST!NATION_M 16
Release and Version Info
e.g. target system does not

offer required metadata
lnlerfac~
Versron
SAP Release
lnleriace Version 4.0 or above
,no
Control record optional

Sender system adapter-specific
identifier must be specified to
fulfill a proper IDoc to target
system
Opttooatf.tetadata Patameh?!S
Advance Options
Control Record in IDoc XML
r-:N..._ot-'-kt.....
an'-'-d.....
ato='""'-'- - . , . - - - - Apply Con~rol Records trom '~amJa\\1!)1 \Riltllmmll!\1\ll\l)
D
0
Apply Sender from Payload
~N~ot.....
M.....
an'-'-d=ato'-ry~-----
Apply Recerver from Payload
Paue 77
111
"Control Record In IDoc XML"

Mandatory (Recommended)
Not Mandatory
111
Not Mandatory
By default It will take effect when control record is not there .
But you need to give sender system ID (SAP ID) and client for both sender and receiver
systems-> as Adapter specific attributes (else it cannot create a MANDT field and sender
system details so that a proper IDoc can be sent to target system)
-You can set Adapter specific attributes (SAPID, Client)
DPI73
77
Adapter Characteristics and Differences to ABAP based Adapter

IDoc versions as of 3.1x
No support for MDMP (Multi Display Multi Processing)
QoS: EO and EOIO (but NOT using qRFC, function module
IDOC_INBOUND_IN_QUEUE is not supported on AS Java)
Processing as file not supported
Security: Basic authentication, but no security on transport level
Segment data reduction not supported
Automatic generation of Java based IDoc adapter not supported
I Doc tracing (tracking) not supported
I Doc Packages supported
ALE Audit supported
Partner conversion supported
Page 711
DPI73
78

configure the IDoc_AAE adapter
Page 79
DPI73
79
I.
! I(
'
:J
~1
i! II H
UIJilrJ
il
Page DO
DPI73
80

configure the HTTP_AAE adapter
- 0Pi7J
DPI73
Page 01
81
DHTTP POST
DQuality of Service (BE, EO, and EOIO)
OSecure communication via SSL
DAdapter-specific message attributes (Dynamic Configuration)
MPier Tvrle
HTTP _IV.
httpJ/sap.tomi,WVSysl~m
DHTTP GET
@ Sender 0 Receiver
Transport Protocol
'HTTP II
DMultipart documents
Protocol "
MapWEnglne
DForm submission
DAttachments
DSystem Acknowledgement (positive & negative)
ISliP 8/I.SIS 730
1: Y rJll
1
M~ss~gB
Page 82
DPI73
82
Form Submit Request
Yes
No
POST
Form-Based File Upload
Yes
Yes
POST
Generic Multipart Request
No
Yes
POST
No
No
GET
URL Parameter
Page 33
DPI73
111
Form Submit Request: HTTP POST request is a form submit request. Content type is
'application/x-www-form-urlencoded'. XI main message payload from one of the parameters of
the form submit request.
111
Form-Based File Upload: HTTP POST request is form based and is multipart {RFC 1867). XI
message payload and XI main message attachments from a form-based file-upload.
111
Generic Multipart Request: HTTP POST request is a multipart request. XI main message payload
and XI message attachments from a generic multipart request.
111
URL Parameter: HTTP GET request. XI main message payload from a URL parameter.
83
Message Protocol
POST I GET
Adapter Type '
HTTP_AAE
@ Sender
::http:llsap.com,xiiXIIS;stem
)SAP BASIS 7.30
~~~
Qli
Receiver
:'!
Transport Protocol
Request Details
Message Protocol
Set Form
Set Multipart
li:l
Attachments
AdaiJier.SIJedfic Messaue ProJrerties
0
0
0
0
Sender HTTP Adapter Address
Se\Ma~ler-Specifit !Aessage Properties
HTTP Header Fields
URL Parameters
HTTP Header Fields (Synchronous Response)
Addrtional Parameters
SeiAddilionat Par<lrneters
URL: !Jttp:/1</Jostname.pott>l<path>?<quety-string> where:
path -
/HL LpAdap Ler /ll L1_pMessa9eSe.c v le L
query-string = ? in tertetceNumespc;ce=<interf aceNo.mespo.ce>&interface=<interf uce> &
senderServlce-<sende.r:Se.cvlce>&senderPa.r:Ly-<sende.r:Pa.r:Ly>&.cecelve.r:ParLy<recei verParty>&recei verService=<recei verService> &qos=<qo.'J> &queueid=<queueid>

~msgguid=<msgguid>
Page 34
Set Form
111
If the HTTP input is through the form submission, select the Set Form checkbox.
In the Main Payload Parameter Name field, specify the name of the request parameter whose
value should be copied to the XI main payload
Set Multipart
111
If the HTTP request is a multipart request where one or more different sets of data are combined
into a single body choose the Set Multipart checkbox.
In the Main Payload Parameter Name field, specify the name of the request parameter whose
value should be copied to the XI main payload
In addition, if you want the attachments in the HTTP request to be copied as XI message
attachments, select the Keep Attachments checkbox.
DPI73
84
Standard configuration
URL address
Addressing mode' 'uRL address
Security and proxy options
Target Host
Target Port'
Query parameters
Path
Adapter -specific message

properties
security and 1\uthenucatton
IJseSSL
User Authentication
Request Details
Set form source
Proxy
Set multipart source
Use Prcq
Attachments
Content Details
'!\lwnymous 10~1on
Query Parameters
Sender Party
[] semJer Setvlce
0
0
0
0
Receiver Interface
Message ID
Oualrty Of Service
OueueiD
[] /l.ddilional Ouerv Parameters

Request Details
SeiForm
!.lain Pa,Joad Parameter Hame
Set Multipart
0
0
Keep l'.nachments
1\rlapter -Specillc Message Proper1tes
Sel Mapler-Specrfrc Message Proper\ies
SpecitY Conterrt Del~lls

Character Encoding
Content Type
- OPJ7)
Page fi5
Set Form Source

"'If the HTTP input from the receiver channel to the target system is form submission, enter the
Main Payload Field Name.
In the Main Payload Parameter Name field, specify the name of the parameter whose value
should be copied to the XI main payload
Set Multipart Source
"'If the HTTP request is a multipart request where one or more different sets of data are combined
into a single body, choose the Set Multipart Source checkbox.
In the Main Payload Parameter Name field, specify the name of the parameter to which you
want to copy the value of the XI main payload
In addition, if you want the attachments in the request to be delivered to the target system,
select the Keep Attachments checkbox.
Specify Content Details
"'If you want to specify the character encoding or the content type of the HTTP input, select the
Specify Content Details checkbox.
"'Specify the character set of the payload
"'Specify the content type of the payload
For a multipart request specify the character set and the content type details for the main
payload.
DPI73
85

configure the HTTP_AAE adapter
Page 06
DPI73
86
Ill\
',
:.;l.,f)
'I
News
Pare 37
DPI73
87

list the adapters with new functionality
configure large (Binary) File-To-File Transfer
Page flC
DPI73
88
Page 39
111
DPI73
In this session, we will take a look at the new adapters and also enhancements to the existing
adapters.
89
OoS EOIO must be selected

Queue Name = any name
Benefits
Improved system robustness and reliability
during large data transfer
Processinu Par ameters

Quality of ServJCe
Functional Insight
lJ'!,;i't Once in Or<l_:r_]
Queue Name -
:queue name
Polllnlerval (sees)
:6o
Poll Interval (mSe(s)
Enhanced capabilities to copy very large files

between locations (file share, FTP)
Data streaming mechanism available for
File/FTP adapter
Complete document is not stored in memory
Configurable byte length of transferred chunks
File chunks are merged on the receiver side
Adapter Status
status ;/l.dr;e
File Stllitting (For EOIO Processlnu of Larue Binary Files)
0
l.irnitation
Mapping or content based routing is not supported
Set Adapter-Specific Message Attributes
File Splittmg Active (No Pa;1oad Access Possible In PI)
Maximum Size of File Par1 (MBytes)
!1o
AddKional Parameters
Service interface has to be type "XI3.0 compatible"

Page 90
.. "XI3.0 compatible" service interfaces have just one operation .
.. For other service interface types, the operation will be determined by accessing the payload.
DPI73
90
Benefits
Assurance of smooth system operations by controlled handling of large JDBC messages
Enhanced system reliability
SAP NetWeaver XI 3.0 &
SAP EHP 2 for SAP NotWel'lver 7.0
functional Insight
Ability to configure the maximum message and row size fetched from data base
Configuration is made
on the Sender JDBC adapter
in the Advanced Mode
Advanced Mode
Additional Parameters
Transaction Isolation Level
D
D
Default
Database AutoComrnitEnabled (t<

Disconnect from Database After Pro
D Rernove Empty Tags
!!l~r
---
lmsglimit
lrnaxMsgSize
!rnaxRowSize
lmaxllrnilErrorlnterval
Switch on
(kb)
(kb)
(seconds)
Page 91
Due to messages of large size, it is possible that there could be out of memory errors, which could
lead to JEE server node failures.
Following are the parameters to be set in the table to limit the message size:
111
msglimit: This parameter is used to enable the max message size limit feature for JDBC adapter.
When this parameter is set to true, JDBC adapter does not process the message of size higher
than the values specified through maxMsgSize and maxRowSize. If msglimit is set to true then,
maxMsgSize and maxRowSize parameters are mandatory.
111
maxMsgSize (in KB): This parameter is used to limit the message size to an optimal value. JDBC
adapter does not process the message size of more than the value provided for maxMsgSize, if
encountered at runtime.
111
maxRowSize (in KB): This parameter is used to provide the maximum row size. This parameter is
used to calculate the maximum number of rows that could be sent through channel in one
interval.
111
maxlimitErrorlnterval (in seconds): This parameter is used to provide a special interval to

change the next polling interval incase an error occurs when a maximum message size is
reached for the current interval. This reduces the load on the system.
More information on configuring the maximum row size: SAP note 1253826.
DPI73
91
Benefits
Improved system performance via optimized resource usage
Assurance of lower memory consumption on the Service Bus by
controlling connection time-out for synchronous communication
Functional Insight
Ability to configure connection time
out to terminate connections to
backend systems after a defined
period of time
Configuration per individual
communication channel
Configuration can be made on the
sender adapters for JDBC, RFC,
SOAP, XI, HTTP (AAE), IDoc (AAE)
.~.'
20 l 1 S\P AG
There are 2 ways of entering the configuration:
DPI73
1.
For RFC and XI adapters, there are synchronous time-out parameter in the configuration
screen.
2.
For the other adapters, parameter entry can be made in the module configuration screen, by
using the parameter name of SyncTimeout.
92
Benefits
[ ______~~=~c~s=!or~Pu=~=tsh~IS=ub=sc=w~eC=o=mm=u~m~='i=on~---
A wider variety of options for

standards based integration to
leverage current IT investments
JMS Provider
SAP JMSAdapter
1 Each atlive ~ubscnber ge\s a copy o! \he l'r'tessa~e

1
Acopy of \he message is relamed for ever; inaclive durable
functional Insight
subscriber
Support for JMS topics for the JMS sender and receiver adapter to enable pub/sub
scenarios:
Subscribe: Once a message is published by a JMS provider for a subscribed topic,
the message is fetched and processed via SAP NetWeaver PI
Publish: SAP NetWeaver PI allows publishing messages to a JMS provider, such as
SAP's JMS provider
Support for durable subscriptions only

Pane 93
11
JMS topics provide true pub/sub scenarios.
11
Topics allow multiple entities to subscribe to the same message.
11
With queues, we can only have 1 entity subscribe to a message. If multiple entities want to
subscribe to the same message, then multiple queues must be used.
11
By using topics, multiple entities can subscribe to the same topic. We need not duplicate the
message to multiple queues.
JMS Queues
Queues for Point-to-Point Communication
Each client gets a different message
Once a message is received, it is deleted from the queue
DPI73
93

list the adapters with new functionality
configure large (Binary) File-To-File Transfer
Page 94
DPI73
94
Installer, Inc is a company that installs windows for businesses and homes. Most of its installers are contractors and
they are hired on an as-needed basis. When a contractor is hired, we must enter his HR information into our ERP
systems. At the same time, his information must also be replicated to a data warehouse system for reporting and
planning purposes. In addition, a log file is also created to track the process. This log file contains the date and time
of replication to help identifY or trace any problems.
3-1
i
SAPERP
I(RWN 811)
__ _j
~l[)oc;
HRI,\D_ABA
JDBC
Pl7.30
AEX
(NWJ)
3-2
File
HR data is created on RWN and an IDoc is sent to the AEX.

2 In AEX, one receiver is specified, and a multi-mapping is used to split the message to send
to 2 different interfaces.
3-1 The 1st message will be sent to update a table in the data warehouse system.
3-2 The 2nd message will be sent to a log tracking the replication process.
1
95
(1 Exercise overview)
2 Review ESR content
Logon to the ES Repository of the AEX (System NWJ) and examine the existing operation mappings in SWCV
HR WORKSHOP SC 1.0
3 Configure Integration
Logon to the Integration Directory of AEX (System NWJ).
In the existing Configuration Scenario "Student##": create an IDoc Sender adapter "SYSl_Sender_##" with RFC server
parameters maintained manually, esp. Program ID "ZHRMD_ ##". Create an Integrated Configuration for the given
scenario.
4 Checking back-end gateway configuration
Logon to SYSl (RWN, client 811, user train-##) and check the registration of the IDoc Sender Adapter on the SAP
Gateway Monitor (transaction SMGW).
5 Checking ALE Configuration
Continue in SYS I: check the ALE configuration, starting with Partner Profile (transaction WE20) for logical system
ZHRMD_##, and drill down through receiver port ZHRMD_## to the SM59 destination ZHRMD_##. Execute a
connection test on the destination.
6 External Employee Creation in Back-end system
Continue in SYS 1: start transaction PQ08 to create an external employee.
7 Checking ALE distribution layer in backend
Continue in SYS 1: start transaction BD87 to check if the IDoc was send.
8 Monitoring in AEX
Start the Configuration page for the AEX (System NWJ) to check the message flow.
9 Monitoring in File system
Connect to the share \\wdflbmt2073\tmp\rkt to check whether the file was created or updated.
10 Monitoring in target Database

Use the Database Studio to connect to the database DEMO_DB (user DBADMIN, password training) and check ifyour
records were written to table EXTERNALS.
96
Logon to the ES Repositmy of the AEX (System NWJ) and examine the existing
operation mappings in SWCV HR_ WORKSHOP_SC 1.0
NWJ
http:/ /wd1lbmt2073. wdf.sap. corp: 50000/dir

http: //wdflbrnt2073, wdf, sap, corp: 50000/dirl

I l.i',ieb Ul
Available Profiles
Find the
SWCVand
Operation
mappmg
you will be
using later.
:v:l
Unrestricted (SAP BASIS 7.30)
Modeling
tal littp:lfttr_vtorkshop.cornf ##
f~ Operation Mappings
HRMD_ABA_externals 2
Message Mappings
HRMD ABA to external~; 2
"' ifdl
~ tal http:firC:s-vv~rksh~p~om/01
Check
details 1:N
Definition
Source Messaoe(s)
Scltware Component V~rsion
Target Message(s)
DEMO 1.0 of demo. com
; Names ... ; Occurr ..
Soltware Cornponent Version
Type
rnn satHC1
Check
details 1:N
DEMO 1 0 r
Name
. MT_sql
MT_userlnfo
'i Taruat onr.ration

I
NarneL Softvvar... Occurr...
urn:sap-crDEt.tO 1.01
]Name
LJtnsert_Async _In
l_jusetlnfojl.syne_ln
Names
httpffde
i'i11PIIdt>
Source MessarJe
Type
ZHRMD_##HRM0ji8Ar "
Name
, Namespace/Binding
HRMD.W_1o_eY1emals_2
http:llrll_worh
Logon to the Integration Directory of AEX (System NWJ).

In the existing Configuration Scenario "Student##":
create an IDoc Sender ada ter "SYSl Sender ##" with RFC server arameters
97
maintained manually, esp. Program ID "ZHRMD_##".

Create an Integrated Configuration for the given scenario.
Open your
group specific
Configuration
Scenario
,.. 'rgfccinficiLlratforis;;8t-i~iria:
...
... -- .... -.:..."'::' .... -.. -..... --- .. -- ...... --"'
-~--
Stuclen~
Stucleti(J
(Q) Edit Configuration Scenario
Configuration Scenario :student##

Description
'\:>~ Communication Channel
Party
'SYS1
SYS1 ~Sender_##/
Description
Add to Scenario
Student_##
Add to Folcler
'I:>Q. Edit Communication Channel
SY81_Sender_ ##
Cornrnunicat10n Channel
Partv
SYS1
Description
identifiers
A.dapter Type
Sender
Module:
!Doc ME
+-R
hltp:f/sap.com/xlfXIfSystern
Receiver 1"-S
Transport Protocol
IRFC
Message Protocol
!doc XML
Adapter Engine
.central Adapter Enqine
Select Manual
configuration.
This is the
right option if
you want to
use an ABAP
98
gateway
(better
throttling and
monitoring)
RFC Parameters

"Program
ID" must
exactly match
the one
defined in the
sender RFC
destination
from the Back
end system.
l~J
Manual
Default (Recommenclecl)
Manu:rJ..
From k~'0!A
811
Password
.......
Language
EN
SeJVer Name
rwntclcOO.wclf.sap.corp
System Number
00
User Name
train-##
For simplicity in this exercise the ALE Logical system name, ALE Port name,
ABAP RFC destination name and the shared "Program ID" are all the same.
(note: "Program ID and "TP Name" are 2 different names for same thing)
The server name you are using is the ABAP backend system/number and
corres onding logon data.
(Q) Ellit Configuration Scenario
Student##
Description
Setuler
Cornrnunica!lon Party
Cornmunication Component
SYSI
Interface
ZHRMD.~##.HRMD_ABA05
Narnespac e
urn:sap- corn:docurnent sap:idoc:rnessages
Receiver
Cornrnunication Party
Cornrnunication Component
Description
Recetver Interfaces
Configuration for Interface ZHRMO _OO.HRMD _ABA05
Cornmunrcalion Channel
$Y.?:i3~i~~~;~~:::::::::::::::::::::::::::::::::::::
Adapter Type
IDoc_ME
Adapter Engine
!Central Adapter Engine
Software Component Versron of Sencler Interface
DEMO 1.0 of clerriO.com
Sct1erna Validation
No Va!idal!on
litlp:Jisap.con
Valiclation by .A.clapter
99
i Communication Party
~ondition
;Communication
Externai_Sys
Receiver
;Type
~Communi~ au~~
Party
\communication Component
Externai_Sys
.. i Operation Mappin~
Condition
Inbound
iSollwareCompon<
;Namespace
HRMD _ABA_externals_2
lnsBit_Async_ln
llttp:l/demo.comlhr
DEMO 1.0 of dem<
Userlnfo_Async_ln
http://demo.com/hr
DEMO 1.0 of dern<
users
Receiver
Assignee! Receiver Interfaces

,Receiver
!Receiver Interface
..
Communication Party
:Name
Namespace
Externai_Sys
lnsert_Async_ln
http://demo.com/hr
Externai_Sys
Userlnfo_Async_ln
httpJ/demo .com/hr
Configuration for Interface tnsert_Async_tn I httrl:llcfemo.comnlr 1DEMO 1.0 of !femo.com

R_JDBC_MaxDB
Adapter Type
JDBC
Adapter Engine
Central Adapter Engine
, http:l/sap.comlxi/XI/System
Sollware Component Version of Receiver Interface

'>em a Validation
Assigned Receiver lntllf f<>cUs

RE.'C!:H\'~r !nti!!tfat~
R~t8fv-tH
(~ornmonlcatJon
Partt
r:.:onvnwo,:Jt1on Comporlc~nt
mm.~
r~amo~pace
E:.temai .. Svs.
rnse1(}.synr: Jn
tH:tp Jh1orno.cornR~t
E'Mnai_SI>
Uti?tltdu_,}\'2>fn(jn
htffll/dt!HHJ.lorn.rm
Conligur iltion for lntmface Userlnfo_A~")IliC_In I hl!p:.((lll!!llu..cMwWJfMO 1.0 of domo.com

corrunnrtiL)hon t:.tHnnel'
Adaph:r T-me
AdJ:flit:"r
EngJne
Compone-nt VtS!(HJ t)f RL1Cf.!<V!1r !n1(Hf~l::-e
(:~ntraJ
Adaph-;r E:ngm~
Suftwdtl?
SthF<rna V3lld<11JOn
100
.Qonfiguration Scenario
~
>./
E.Qit }{iew
~ Qisplay/Eclit
1:0 .Qopy otJject. ..

Of O.lete ...
[j'"'o Check
F7
ff1e 8ctiv~ ...
H Prope
1-Hctnt'\1
Ctrl+:=:hitt+C
ies
ati
,11:
11:...
101
Logon to SYS 1 (RWN, client 811, train-##) and check the registration of the IDoc Sender
Ada ter on the SAP Gatewa Monitor (transaction SMGW).
I Qoto 1
?_ettintJs
~3ystem
LQgged on Clients
Cielp
t::{
Remote Gateways
A~;;tive
connections
Release Notes
Select "TP
Name"
column
and Sort
descending
fJ.wdl
m
~H
[@ rNu...
LU Name
-,
0 rwntdcOO.wdf.sap.corp
2 wdftbmt2074
Local ,e.,pp
wdftbmt2074.ccmsping,OC Registerec
nRTT71
You
should see
the
"Program
ID" you
defined in
the
Channel.
8!]3 1Ndftbrnt207:3
525 wdfibmt2071
ni=Mrl A AI= TO::
'ZHRMO _##
L
XI _IC()C _DEFfcUL T _PID
526 wdfibmt2074
527 v,rdfibmt2074
528 v."jf1brnt2074
529 \vdftbmt2074
530 wdftbmt2074
--~
R anictara1
'Regqstered Server
Reg>tered Server
wdHbmt:
vvdRbmt;
Regdered Server
Reg;sb?red Smver
'Ndftbrnt:
1NdAbmt;
wdfibmt:
1Ndfibmt:
'Ndftbmt:
Rec_t,ste.teci <;.erver
Regstered Serv?t
Rer~stered
Server
102
Continue in SYS 1: check the ALE configuration, starting with Partner Profile
(transaction WE20) for logical system ZHRMD _##,and drill down through
receiver port ZHRMD_##to the SM59 destination ZHRMD _##.Execute a
connection test on the destination.
f~
/nwe20I
~I
Partner
...
P.:n tner Prt:)ftles
Partner
Partner
Partner
Partner
Partner
Type
Type
Type
Type
Type
CLNT811
CLNT812
r"JIIV J
XI_0CU300
ZHRMQ ##
2Hru;&~
Make sure
you select
ZHRMD #
#!
Oesu1pt1on
8 Bank
GFBusiness Partner
KL Customer
LI Vendor
LS Lor;;Jical system
ERP
.LI.idine LH
'=;.li.Pr'-Jet'Weaver PI
RVVN Inte9ration '=
HR System Group 1
HR. System Group 1
Outb. Parameters
Partner . ..
Message type
Message ...
HRfv1D _.LI.BA.
SYNCH
103
Double
click
P.3rtner No.
ZHRHD ##
HR System Group 00 (via ,8.EX)
Partn. Type
LS
L01;Jical systern
Partner Role
~ fvl.::!ssage Type
ZHR}ID ##
HR: Basis
~~
fvlessage code
Message function
Outbound Options
Postprocessing; Permitted A1;;Jents
Telephony
Transactional RFC
ZHRMD_I
Receiver pmt
Double
click RFC
destination
Ports in IDoc Processing
Description
Ports
Transactional RF
J.\.000000001
RWN /800
IDOC_.l>.EX
IDOC_AEX
ZHRfv1D_ ##
ZHRiv1D _ ##
ZHRMD _01
ZHRiv1D _01
ZHRJv1D_02
ZHRfvlD_02
ZHRM0_03
ZHRJv1D_03
ZHRfvlD_04
ZHRMD_04
ZHRfv1D_05
ZHRiv1D_OS
ZHRMD_06
ZHRMD_06
ZHRMD_07
ZHRiv1D_07
Port
ZHRIU>_##
Description
ZHRMD_##
Version
!Doc rec.types SII.P Release 3.0
!Doc record types SAP Release
RFC destination
104
Confirm
"Program
ID"
matches
the
gateway
RFC Destination ZHRMD_##

Connectron
T~::-~.
RFC Destrrntton
"TP
Connectron Tvpe
Natne"
Oe,:cription
Descriptron 1
ZHRMD_##
T
Descnpt
TCP/IP Conne.:tion
Connectron to ZHRMD _IJO to .t\EX
Descrlptron 2
Description .3
Administratfon
TeA:hrdcal Settings
Logon~:,
Secunty
Unicode
Activation Type
Start on .l<pp!;catfon Server ['
ReJiste;ed Server Pn
.ot
Start on Exp!\Cit Host
"
Start on frontEnd Work Station

Regist?ted ServE!! Progr Jrn
Pro,Jr,1m 10
!_
ZHRMD_##
RFC Destin.:."'.,...
Connection Type
TCP/IP Connection
Description
ALE->
AEXperfect
RFC - Connection Test
Connection Test ZHRMD

Connection Type TCP/IP Connection
1Action
LLogon
i Transfer of 0 KB
!.Transfer of 10 KB
I Transfer of 20 KB
ITransfer of 30 KB
Result
rnsec
12 rnsec
19 msec
18 rnsec
16 rnsec
5
.I
105
Continue in SYS 1: start transaction PQ08 to create an external employee.
~
Clear the
External person
number and
execute ~
[Q]
~~I
:PQOBI
_j
<1
01! Current plan
Plan version
r~
External person
<c1ea:t: this>fo
J
Object name
External person
Planning Status
Active
Validity
19.01.2011
31.12.9999
to
160'>
Cha1
Object
First name
Gino
t;
Last name
Find the
company for
your group
number and
press enter
Make sure you
~ress "Enter" (
@)to create
the
relationshi~ !
After making
sure the
company is
assigned, save
the infotype.
Mapped Fields:
-Street/Hse No.
- housenumber
-City
- Countty
Then save (
[Q] ) the
info type
-1
Rennil
.J
Relationships
Relationship type/relationship
003
Belongs to
Related object
Type of related object
Cornpany
ID of the related object
""##
""'
1'
~~
.e.bbreviation
Name
Priority
Address suppl.
Street/Hse No.
House number
Street
r
I
LTreviso
PCode/City
Country
Italy
Region
106
Continue in SYS I: start transaction BD87 to check if the IDoc was send.
~ ~/nbdB71
Fill time
range and
Partner
System
ZHRMD ##
Select IDocs
f1:\
~~~
!Doc Number
to
Created On
to
Cteatecl At
00:00:00
to
00:00:00
Chant;Jed On
19. OL 2011
to
19. OL 2011
to
19:Si3:28
Changed .ll.t
18:
s4 24
to
Partner Systern
Status03, 12
or 41 are all
good (any)
ZHPJ!D ##
to
!Doc Status
t#POCS
"" 'li? !Doc Selection

Changed On is in the rangr:.> 19.01.2011 to 19.01.2011
'li? Last Changed At is 1n the range 18:56:24 to 19:58:28

03 ->in
ABAP still
not accepted
byAEX
(different
behavior
than IE)
12 ->In
AEX
41 ->
reached
target system
(DB)
~ Partner System is equal to ZHRfvlD _##

ERP System
..'~'..
~ Outbound !Docs
~ HR System Group## (via AEX)
"' 0 .ll,pplicatlon doo_ment created In target system
f.:i
41
"~
Note: All the information and other status 41 details are recovered by polling new
records from the target system (database) using PI
107
Start the Configuration page for the AEX (System NWJ) to check the message flow.
II
Configuration and Monitoring
meO~e
Display
processing inclucling aggregated and detailed information about status of
messages. lclentify errors in message processing and perform problem isolation. Manage
individLlal messages by, for example, resencling individual message versions.
'iO
Sender Component : Receiver Patty
Receiver Component
Interface
Externai_Sys
SYSI
ALEAUD .ALEAUDOI
14ti
Externai_Sys
SYS1
lnsert_Async_ln
21.
Externai_Sys
SYSI
Selec!Externals _.B.sync _Ou
II :3
Externai_Sys
SYSI
Userlnfo _Async_ln
Error
Scheduled
Success
Canceled
Sender Party
:i
SYSI
Externai_Sys
lnseti_Async _In
1Q
SYS1
Externai_Sys
Userlnfo _Async _In
SYSi
Externai_Sys
ZHRMD _00 .HRMD _ABAOS
<()
SYS1
Externai_Sys
ZHRMD 18.HRMD_ABAOS
SYSl
Externai_Sys
ZHRMD _1 9.HRMD _ABAOS
SYSl
Externai_Sys
ZHRMD _20.HRMD _ABAOS
Connect to the share \\wdflbmt2073\tmp\rkt to check whether the

file was created or dated.
1.
Check the log file:

Go to: Start~ Run ...
2.
Enter:
\\wdflbmt2073\tmp\rkt
Type the name of a program, folder, document, or
Internet resource, and Windows will open it for you.
Qpen:
j \\wdflb~t2073\t~p\rktl
OK
Cancel ..
!2fowse ...
108
3. Double-click on your
log file. Look for file
with your student
number. The content
will show the data sent
by the IDoc.
Eile !;.dit FQ.fmat Y]ew t:!elp

~011/01/20, 21 :53 :30,0000000000001312,50000051, Gino Renn, IT, Tev iso ,pending
When you submit

another IDoc, a new
record will be
a
to this file.
Use the Database Studio to connect to the database DEMO_DB (user

DBADMIN, password training) and check if your records were written to
table EXTERNALS.
r---------------------------------,_
2.
~~---------------------
Go to:
Start 7 Programs 7 SAP MaxDB
7 Database Studio
lli3 Status Monitor for AL ... , ,[) NWJ: SAP NetWeave ... 111:1 Conf
3. If the database does not exist, then

add it.
Right-click and select:
Servers -?Add -?Server/Database
4.
Enter the Server Name:

wdflbmt2073
5. Click: Next
6. Select: DEMO DB
7. Click: Finish
Server
Enter a server name.
Cancel
109
Databases
Select the database(s) you want to be add.
Register all databases automatically,
Name
0
0
~"-'"''
-'-Ve;:.:r..:csi..:con'-'--_ _,_I.:::In.:::s.::cta=lla;::;t::.:io"'n-'-P..::a"""th=-------D:\sapdb\NWJ\db
7.8.01.14
D:\sapdb\NWJ\db
L-1
[~~~C::\.,.Q~_j 7.8.01.14
NWJ
Select All
J Deselect All I Refresh I
__<_~a_c_k_ _,____r_J'_:r__
8.
__.II
Einish
Cancel
Click: the"+" of DEMO DB

Servers
[,_,J
lj <Local>
L':'!
(
l.J wdflbmt2073
r.p. .. \
\.'"' )
9.
Enter authentication information.

User Name: DBADMIN
User Pswd: training
Landscapes
Landscape Name:
Server Name:
Database Name:
I-----~
---
iJ_,
....
iJ
D_E_M_O___D_B_ _ _ _ _ _iJ___,v
,Irv_l.,y-.L."""a_n_ds_c_ap,_e_ _ _ _ _
Iwdflbmt2073
.-1
-~----..
Authentication- ..... --- .. ----

User Name:
IDBADfvl!N
User Password:
I """"
r
"""'
Authentication by OS user
E.inish
110
10. Expand and traverse down to

"Tables".
11. Right-click on "EXTERNALS" and
select: Content
l":ly L.;:;nd~~Cip.:
- ..iJ Servers
:+
- j
<Local>
wdflbmt2073
DEMO_DB
New
DBADMIN
'+< l1 Database Server
Open
i+:
~<1
'+; ,
Diagnosis Files
SOL SQL Editor
Roles
Schemas
Check Database Structure.,.
- tlcl DBADMIN
+;
Domains
~f
Functions
+~
Indexes
';' j
Copy
Procedures
Paste
Sequences
Delete
Tables
;~
CONFIGURI>
!lfuJ CONSISTEN'
~~ DB_STATE
Explore
, Refresh
-- -----
'1llB!!!IBBBII
!.lfui DBP'ARI\MEllij
-~ DBTI~lES
~DUAL
D!mi'Dm-~~~----.:J
~ GARBAGECOLLECTOR_:
!.lfui HISTORYINFO
% INDEXPAGES
12. Examine the content and find your
record.
i0
=Eli
DBADMIN.EXTERNALS 2-'.
wdflbmt2073:0EMO_DB
DBADMIN
(Auto Commit: On, SQL Mode: Internal, Isolation Level: Read Committe
DOCNUM
111
112
I
I' ;i
I( ) I I
''
l
II
Paqe113
DPI73
113

use the PI monitoring capabilities of /pimon
explain the advantage of the user-defined search
Poge 114
DPI73
114
____.
Configuration and Monitoring
Monitoring Home
System: 11'/IJ
Monitoring
Adapter Engine
Conrt9uration and Adrr,n\strabon

Mappmg Runtime
t.1t;<:.'>Joe i,lon ~or

D~sp!.ay message processing mdud~n:g
aggrepated and d-etafed in.formatfon about
status o1 messa9es.
~1entity
errors Hi:
Display the status ollhe communk

the correso-ondin9 adapters to 9et
da'e runtrrrre 'fn~ornuhon about ind1

communication channet3
Monitoring Home
Jcr, a Pro .v
System: R\'itl
Adapter Engme
Get an o'ter/,ew of message processhg
during a specific tirr<e penod. !.!essages are

aggregated by processtng status
Mapplng Runftme
Search for messages using rness.lge paybad

content You require the Search and
C\.assiftcation En9ine TREX for indexing and
seardung documen,s ..h.ddff-Jflaky, you have set

up and acti.-ated the rnessage inde;.;hg_
Monitor the infrasttucture comp-onents of SAP

tletkVea~'er Process Jnlegration and the path
of mdr,K:lual messages through these
components from start to end.
Gel insight in\o the health status of the

indr.tdual corn,oonents of SAP HetWeaver
Process pendlflg message-based alerts ra~sed by

SAP HetWeaver Process ble9rattJn, Alerts can
prov~1e you Wtth runhrne !;itorffi.lt~on a nO lo),s \o
troub~shooting tools to fac;'1ate faster problem
i::so.lat~~rL
Pro-cess !ntegratiOn
Page 115
The link to "Configuration and Monitoring Home" (/pimon) on the PI Tools homepage opens a
new browser window. The available links and section depend on whether it is the PI dual stack
installation, or the AEX (java standalone). Using a link, for example "Communication Channel
Monitor", opens a new browser window that is part of NWA.
Other examples are:
IDoc Adapter Monitor for the Advanced Adapter Engine
Monitor IDoc message traffic and metadata processed on the AAE
IDoc Message monitor to find in/outbound IDoc messages from/to a backend system
IDoc Metadata monitor to preload or delete IDoc types
Performance monitor for the Advanced Adapter Engine
Identify abnormal message processing time on the AAE to optimize performance
Monitor the amount of processed information over a period time
Monitor the message processing time on module processor level
DPI73
115
Functional Insight
Communication channel
monitor:
adapter log for the AAE
Faster problem isolation via integrated

cross-navigation between monitors
Navigate from the Communication Channel
to the individual messages in the Message
monitor
Monitoring of events
(transaction
~;xr _[vJONITOR)
Asynchronous messages of type "event"

View parent-child events relations and
subscribed event recipients
XML
monitoring in the
Cache monitor
View the synchronization status of
XML schemas in the cache
Search and synchronize XML
schemas in the cache
Sequence monitor
(transaction SOAlV!ANAGER)
New sequence and message
statuses for seamless visibility into
WS-RM message traffic in
interoperability scenarios
Monitor and restart event messages

~.'
DPI73
;':(;1 l SAP .L.G
Page 116
116
Functional Insight
Performance-friendly search configuration for optimal resource utilization
Enable the search on individual integration engines or adapter engines
Use richer options for configuration of search filters (sender/ receiver party,
service, interface name and interface namespace)
Perform message indexing on demand
Track search configuration changes in an
audit log
Value help for XPATH expressions
- DP!7.J
DPI73
SAP EHP 2 for SAP NetWeaver PI 7.0
Partial down port to AS ABAP

User-defined message search
capabilities on SAP NetWeaver
Application Server (ABAP)
Search for messages on the local
integration engine on AS ABAP
Search configuration in transaction
SXMS - LMS - CONF
Search for messages in transaction
SXI lVIONITOR
Pane 117
117
Benefits
o Easy of finding archived messages

Functional Insight
o Advanced technical and payload

search criteria for archived
messages (ABAP)
Searc/1 for Arcllived Messages
<
LMO!h of Output List
200 '
Mes-:.>&(lt' status
Standard Selection Criteria
Advanted Selection CriteriJ.t
User-Defrned Selection Criteria
Date!Time
End ofE-.:ecution From
03012010'
16: 1!); I
End Of Execui!On Until
03172010
00 00 1
: Message 10
Advanced Seleclion Criteria
i~>l
Standard Seiedton Crile;ia
Quality of Setvlce
Uset'Defined SeiE
s-earcr1 for All Pitnbt.tles
A&tanced Selection Criteria
UserDefmed Selecbon Criteria
'Searc11 for One of ltJe P.iJ/HJUJ
Logical Pipeline ID
A.'1nhu!i7
rttr11Ju1e
DPI73
'Ut<TNAilE
Va!tJe
Value
118

use the PI monitoring capabilities of /pimon
explain the advantage of the user-defined search
Page119
DPI73
119
i.
;j
! ('
Page 120
DPI73
120

set up a filter for user-defined search
use the IDoc monitor in /pimon
use the Integration Process monitor in /pimon
Page 121
DPI73
121
SAP NetWeaver PI 7.3 introduces an

improved set of web tools to monitor
the complete PI installation:
ABAP
c
0
E
E
Configuration and Mon'1tor'mg
Java
ccBPM
Mess
MaJ)pifiU
w
~
SAP NetWeaver Pl7.3 comes with a Web-based consolidated access to the local monitoring
capabilities for the local PI system. That is available through a Monitoring&Configuration home
page that links you to the tools you need to configure, monitor and test your PI system.
DPI73
122
Payload fields are extracted during message processing, and stored in an index
table
Only for messages that meet specific filter criteria
Index is archived together with message
Payload search integrated into local message monitoring on each component

Search for all attributes (AND) or search for at least one attribute (OR)
User-defined attributes are displayed for each message (if available)
M-es.sa-g& status OVF3veN
Advanced
:.~~~~~~$
I s.rlf".rN
Messages By,
l Time Pel~,)d
:cvs\:>rrt
Message !leader Oata
:"i
User-Oefined Search Criteria
[_6~~-~~t-;nt~I! }f''t)~~e\-~]
r;o
Seareh for:! i .hJl 'V a~ues
Norr~C
, Lasm"""
- DP!73
Page 123
"Search of messages based on payload data

"No full index, pre-selected payload fields only
"Alternative to using a TREX server
11 Distinguish between filter configuration and search
11 Configuration: define filter via xpath pointing to the tag in xml which should be indexed
"Search embedded in message monitor, both for java and abap
"2 index options: during processing or afterwards via batch job (latter for messages that have been already
processed)
"Interface independent: filter name does not have to be unique, IF and NS are only used to find filter
criteria, e.g., you can define 3 different criteria with name 'CustomeriD' referring to different interfaces,
so that you can search across interfaces
Payload fields are extracted during message processing (Xpath expression)
Optionally, index is possible via background job
Fields (name and value) are stored into an index table
Only for messages which fit to a filter
Index can be used for message search
Search integrated into local Message Monitors (AE and IE)
Indexed fields are also displayed in message-based alerts
"Value Help showing all available attributes for an Interface
"Multiple Attributes Possible
"Search for All Attributes (AND) or Search for at Least One Attribute (OR)
"User-defined Attribute are Displayed for Each Message (if available)
DPI73
123
Local configuration on each component

NWA for Adapter Engine
SAPGui for Integration Engine
Configuration steps:
Define Filters for indexing
For each filter, define Extractors
XPath expression for
Payload Fields
Adapter -specific Headers
Page 124
DPI73
111
Payload fields are extracted during message processing (Xpath expression)
111
Fields (name and value) are stored into an index table
111
Only for messages which fit to a filter
111
Index can be used for message search
111
Search integrated into local Message Monitors (AE and IE}
111
lndexed fields are also displayed in message-based alerts
111
124
Monitoring Home
Monitor !Doc traffic on the
AAE
Sys te 01! .t.X I
Monrtoring
Adapter Engine
Confrg:uratlon and Ad:mimstrat>On
Two level of monitoring:
Mappng Runt~
l<:>'l
o.spt1y message processing m-cbdng

aggregated and deta%d infornut-'On about
status of messages. klentdy errors
message processng and ~erform probloem
isolation. f,!anage irldNidua! messages by,
for example, resendng mdr.dual message
-'"'<:;J~,:.fl
versions
l.loMor the
Uon~or the perforrt"lnce o t ffi.$Ssage

process\og on the .L..d.-anced Adap-ter
Eng,,e by inspech'1glhe arr,ount of
Retr~;e
processed data over v.srious per:>ds of

kre and the rnessaoe processmo kr,e at
nd;v4ual adapter r;.cdu\es.
1111
(h,Fin,;:ll.ic,n-:or
Disp\ly the status o! the cornmun!cat>On channels and

th-e correspondrng ad,;pters to get detar.;a and
up-to-date runkne trdorrr-.lhon about V'!dr,~:lual
corrm.Jm<:Jtion channel.-s
overa~
status of the Java Proxy
IIIIMetadata
Obtain an overview of the
IDoc message traffic
Runttrr~
Search IDocs
information about the messag.r\g system of
Access the payload
an AOianced Ada-pter Eng:i11e lnc!ud:09 data about
n'iessage status. d-atabase lo.cls, queues. bacuogs,

eiel'it han:1\tis.
Analyze the metadata
D'.sp~y
Monitor
acknowledgements
!,1oMor cache objects ir1 the SAP

tleh'/ea.. er Process btegrahon runt.~
caches of the AQloter En orne
Obta11 a tH~toncal cr:er;iew of tne
Message traffic
processing steps of adapters that cannot be

ass:gned to a parhoJ1.:1r commumcat<On channel
S-elect an adapter to d>Sp~3~' i:rdormat.;;n about au
entrres for proceSS''1Q for thts adapter
~;arf:n.ls
types of cache updates to the database

V~l'l
the cache response to the htegrat>1n
O"'ectory for a rr..;re ;oform>$d ettOt

tH'l;i!ySIS
Page 12.5
-{)PC':)
Prerequisite:
Ensure that the persistence of I Doc traffic via the Java-based IDoc adapter is enabled:
1. In SAP NetWeaver Administrator {http:/l<host>:<port>lnwa), go to Configuration
Infrastructure.
2. Select Application Resource.

3. Under the Resource name filter by type I Doc
4. Select the Resource with Name "JavaldocAdapter" and type "Resource Adapter"
5. In the properties Tab, ensure that the properties for "Persistance" and "AutoNumberFromDB"
are set to true.
You can validate that IDoc traffic via the Java-based IDoc adapter is persisted by checking the
database tables:
l. In SAP 1\JetWeaver Administrator, navigate to Troubleshooting
Database.
2. Open SQL Data Browser, and check the following tables: XI_IDOC_IN __ MSG,
XUDOC_OUT_MSG {you find the table by name in the Show input box)
3. Check if there ar-e rows available.
DPI73
125
PI IDoc Adapter Monitoring: Message Monitor
\dapter Monitoring: Message Monitor
!Doc Messa!le Uonltor

.,..:~
[TCil{
hod:
rQ OV.:.H..rn
!Doc Basic Search:

Select distribution direction
Oocl'fP'!
H!fDT
~oc6";sr,gT
.::i:li0-!(!...2'1
!Doc Basic Search:

Select time \n\eNal
\1"onitot
\/
1
O)X::OX).
H'i:YQ_AEL H'it"D..).l:JA LOHt-f0-2
H:;ey_.r.j
811
1-fi.v
.ht<r.rd
Sll
lB
1-n''D >\E.-\ 2')loJ,JO.!
~ t"'X)'~YJ
] ((((0)):))
811
Y,ifl:: cf-C.il:/,
T.;,"t~y
;'1)10..10-11
PI IDQc Ad;~pter HQnitQrlng: Message Hanltar

i;Jb_.
$A-
ts
;<)1~1-t(I-Z
:orO-riJ-;7'
,.lff?JO):!JfJf
M'<'!
::o:o.to-2.
::ow-to-21
~co:xxo::~Jt
M\'J
LS
<J.IJCI-1~1-z/
t.t...v,.Y;l
nn
l':J
X;C'-I0-21
AC)))).):)J1
l.'?d
lS
~c~l(L1~~-z
ellA ?:JfCt-10-2
r-<;-.:l~c:t .,..~""'
i-t<>.ni
011
'!Doc Advanced Search:
search by any message

attribute
DPI73
126
PI IDoc Adapter Monitoring: Message Monitor

S~UthfQf!
Message details for the

selected entry
!Doc Mes:s<1ge Monhor
Ckect_.;...,
Oo:lyp~
tJ~n*
t"RtJD_AB
H""JJ_AEA 20H)-It2,
H%4
"""'
.,
2010-10-27
ACOOXOXtl
tNtJ
LS
SftF1?;\N
CWT$1t
lS
~I'Oj5 ..
1-'i'i:J,'V_J.BA :>)10.02 ___
r~!.<O'.fti
rm
.:v~o-Jo.-27
J.O:t..(>)..>OJl
P.NJ
lS
S.t.FRV!.l
>:UHS1~
lS
lifi!-"f_AO
h"i''l.}_APA
}~11
;~H!)..!Q.:)J
~()XO.l))l
),I.VJ
IS
S.Lf-f,\'.tj
(!)IT;lli.
IS
s.-n
1Dit\\Ct27 ..
N)'X00X(!1
h\'l)
lS
S-\';R\'ll
CLNT61l
lS
t--fit'-C.AB . . H'i'f":>
/E'~
VeiDx.fi
;~-It
'--1(}../
2-'!(LIO.L
l'.t:-~,J
' Fields of the control record

' for the selected enlry as l\1\ed
by the receiver lDoc adapter
ll').:<:l.\rtbtf
OCVXO:tX>:0:001ZL
IC\>~ Typ~
~i'i>V _ABA05
!~::~::r. f)f"~
I-+!'H_A8A
C~rt
8\l
S->:r.krP~rl
S.~P7\',',H
S:.,--~.8
:_-~r.-t<;tf'.:.-F"'" rw~
L':::
R~0~I
R~.:"'"'"'' f'<:1tr~r l~....rl.,;r
tJ.VJ
P:.rtn.-.f
fs-rl:
t-i.r.L~r
(LNT611
.A))(I..":o))tF
MAHnl:liU
(X)CkUMJ~t))
ID<>CIW:HMm_AAM$
OM.Ii'f>l
tAf'if'Jf'ti*'-~(AIJI\
~~!SM'P'<'M
~lf1H:LS
'>tUJf'fCt
Wlif'P)4:Cl1Hil1
RC~:~1
V:CVNll :IS
ReVlOC:
J..'CVlP:H : tHI J
Pcl(]B 127
111
DPI73
1n the lower "I Doc Message details" tab the detailed information of the selected message can be
visualized
127
Obtain an overview of the
Monitoring Home
process activity pm the Business

Process Engine
System: 84'{
Monitoring
Common
IJ
Confrgurat~:;n
hlecyrat'O)n En9ne
and Adrrb'{&tfdt'<On
Adapter nq:ine
l.!ontor and rr,Jnage tMe exec..t:Jn ol ntegrat-on

process.es on the Bus ness Process EngM
V~w aggregJted and deta '.;-0 nformJ!Dn ab:;lut
processe:; ar:O rroco?,.:c.') ~1<:;\ance-s
Test~19
Business Process Enqlne
Vapp-1\g Rontlrr-e
Get an ooerv~w and ft'1-Jilil9e tr-,e bsdgroum:l

iObs sceC!f'C to the Bus1'1ess Process Eng r1e
of SAP Heh'tea-..er Process hlegrat>On
Monitor the processes

deployed on the
Integration Server, their
instances, status and
runtime behavior
IIIView messages related
to a process type
Configuration & Monitoring Home

~ Monitoring ~ Business Process Engine ~ Integration Process Monitor
Page 120
'"Integration Process Monitor is a new Ul for Business Process Engine monitoring. This screen is
based on Web Dynpro for Java technology.
DPI73
128
PI Monitoring: Integrarion Processes
. ,_"_-,_...,.,..."
List of Integration Process
,_
~
,,
.._:..-_:: __ ):",:::.
PI HonitPr)ng; .JntegrnUon Prpcesses
List of Process Instances
Process Instances Detail

Page 129
.. Integration Process monitor consists of 3 levels of monitoring screens.

Process Overview Monitor
Process Instance List Monitor
Process Instance Detail Monitor
01
lt consolidates and streamlines access to ccBPM-specific information that has been previously
distributed in a number of ABAP transactions, such as RSWF _CRL_MAINTAIN (correlation
information), SWF _XI_SWil (Workitem List), SWF _XI_SWPR (Restart of Process Instances),
.. SWF _INB_MON (Inbound Monitoring) .

.. The Integration Process monitor does not replace the ABAP transactions, it enhances the
usability of accessing Business Process Engine monitoring information, and adds visibility into
information that was previously not available: eg. Process Overview Monitor gives an overview
on the process instances and their status.
DPI73
129
Unified and simplified status details across PI components

New error labels combining several error codes
Integration Engine
1.1 cssa_g rg: Gcilera: Error

\l.~L
\Ja' .:;ak~:
G-n;;~,l'l ~rror
Missing or Invalid Receiver Agreement

XML Validation: General Error
Integration Engine: General En or
Missing or Invalid Recerm AgrMment
Missirw or Invalid Receiver Agreement
. Missing or Invalid Receiver Agreement
23.09.2010
15:01
Adapter Engine
Poge f30
111
Unified and Simplified Status Details for ABAP and JAVA (Replacing Error Codes)
111
Message status detail

So far, we distinguished status categories and status codes
Status category too generic, e.g., waiting, not delivered, etc
Code too specific, too detailed
Error status not consistent across PI components
New: we have introduced error labels which group codes, and which are used consistently
across PI components
DPI73
130
Mess$;ffl Status Overview
Improved message content view
Database
via streaming
downloading large messages as file
! Defrvered
t:nt
2710 2010 13:21
27.10201o
:!7.1020101321
~7,1020101321
27.10.2010 13.21
27.10 2010 13.21
271020101321
27J020t013.2J
27 10.2010 13 21
27 10.2010 13.21
Message Details
Used)et<>e<l Atlnbules
Do you wanllo open ot .ave lhi li!e?

Harne
v XMLMessag.e
v SOAP Header
1'f\Jt$~.ht
T}').:<C. TejtDo.;.IJfr.er~
Fui(fr rwrJ:d."1)(l.~'".jf.$ep,cc:>rp
tA~n
\vldettes trc.rn ihefrlernet con be uoefu!.
sore~ tle~
can {:~entiQ!ly
h-&ftl }'V!Jf C<)!Y-i=>l$et II )'Otl do riOt tll..nt the SJ*JJce. do rr:>t OD''tl 01
S-:ivethislk Wlnt'st!f{"fd:?
Paue 131
DPI73
111
Download for large messages to avoid that display of the payload is impacting the overall system
performance
111
Streaming, complete message is not loaded into main memory, it's loaded byte by byte
111
Payload is not directly displayed in message monitor, follow link to view message
111
Download functionality for large messages in NWA message monitor
131

set up a filter for user-defined search
use the IDoc monitor in /pimon
use the Integration Process monitor in /pimon
.~;
DPI73
201! S.<..P
Page i 32
132

~
Define Filter and criteria for User-Defined Search
Find messages based on User-Defined Search
In your project, you have installed the Advanced Adapter Engine Extended (AEX). Now you have to
configure a scenario where a message has to be routed to an ABAP target system as an IDoc. In addition,
several parts of the data have to be saved as separate files.
NWJ (AEX}
IUoc 1\f\E
___.,
~-...
HTTP A/I.E
i:(J
/F1Ie
~B
AgoocyT"c""'
0
Configure the User-Defined Search (UDS) on the AEX, send another message, and use the UDS for your
messages.
1) Configure the User-Defined Search on the AEX (System NWJ)
a) Open the PI Tools page for AEX (System NWJ) and use the link to "Configuration and
Monitoring Home" (quick link /pimon)
SAP NetWeaver"

I
Ul
Entt>r~:ns;;. :3~'1\'IC-25 2Ut!=~t'l
Sef\'IC.o?'; REyistr/
System Landscape
133
b) Switch to tab "Configuration and Administration" and use the link to "User-Defined Search
Configuration''
Monitoring Home
System: tlWJ
Configuration and Administratio-n
Monitoring
Adapter Engine
~>:::ti
SJC rr0r:t!;:g_L_Ql}_
Schedule the t::adground processing of routine

the Advanced Adapter Engtne such as the- arct
e-drt.ed or successfulty processed messages. tt
of messages that are not to be archt'<'ed, and th
Manage rules for the priontization of message

processmg. The mess.1ging system
processes the messages in the queue based
on the prionty assigned. You can set le',els of
prionty to high, me-drum, or IO'N. !.less-age
priorttizatfon rules can be set based on
Sender Partner. Sender Component, Recer.:er
Partner, Receiver Component. Interface name,
and ln1erface flamespace
c) On the opening window: use the button "New" to create a new filter:
--------------------------- - - - - -
PI Adapter User-Defined Message Search Configuration:

Favornes _.
Relaled Links_.
Go To 4
I<>
Defaufl
'3upport
list ol filters
Ois play: :All F;~,-;~

I! ame:
'i[] llame
Description
Sender party
Flight booking fifter '
flightBookinLXX
Sender compon. .
Receiver party
Agenc)'_XX
Receiver comp...
Interface
llamespace
SYSI
BookingOrderR._.
htlp:llfiightcoml... !
Fill the details for the new filter as shown below by using the drop-down menu where possible.
List of unsaved filters
'iQ
Name'
Description
Sender pariy
_Sender component
Receiver party
Receiver component
Interface'
Namespace'
: status
Enter details for new fitter

Description:
Sender party:
'~
Receiver party: '

Interface':
status:
jEiookingOrderRequestj:!trt
Sender component:
'Agency~#_#
Receiver component:
"' J Namespace*:
ihttp: llflightcomlagency .
i"[-cl8arTomll
Use the "Add" button to add the new filter to the table of unsaved filters, and use the "Save" button
to save the filter.
Make sure that in the table of existing filters, the new filter is selected.
134
d) Scroll down to the details area, and switch to the tab "Prefixes" and choose "New".
SYSI
for filter FlightBooking_##

Search Criteria
Prefoc namespace
Enter as Prefix namespace "http://sap.com/xi/XI!Demo/Agency" which is the namespace of the used

message type. Enter as Prefix value to "ns##". Choose "Add" to add the prefix to table ofunsaved
prefixes.
Enter details for new 1nefix
Prefix value':
Prefix namespace': [;-rttp:llsap.con;lxiiXIIDemof
~ [l:~ar
Q_
'ns#li
form j
.........-
!.i\ddc r:.:cb tc table of unsaved

'~. ~--r-r----
... ----
~----
Now choose "Save" to save the prefix.

e) This prefix will now be used in a Search Criterion: switch to tab "Search Criteria" and choose
"New" to create a new Search Criterion.
IDetails for filter FlightBooking_##
PrefiXes
Type
Specify a name and description, switch to Type "XPath Expression", and specify the XPath with
your prefix as /ns##:BookingOrderRequest/PassengerData/Surname. Choose "Add" to add the
search Criterion to the list ofunsaved criteria. Choose "Save" to save the search Criterion.
Search Criteria Details
Type:
[Passen~erNanrej#
Description:
lsearchbyPassenger last
~~-~-~~~ x~~~~~-~~~:-_ ~ J
XPalh':
[irrs##sookingOrcterRecic~
~'-""'""-''~
!Add to list of unsaved search criteria!
135
2) Use the HTTP client to send another message

a) Proceed like in Task 2. Note the content of tag Surname.
Payload
Type in X:vll
<Co~~ect!o~:D>0017</Co~~ect~
<Fl!g~tDate>2011-03-30</Fl!g
<.l F:.::..r;::-.. t:D>

<Passe:-,gerDat.a>
</ 3...~r:-.~.an-.e
3) Use the User-Defined Search for your messages.

a) Open the AEX Message Monitor like done before. Switch to tab "Database" and open the
Advanced selection
Message Mon.
0
I <?
Rsstor2 Cefault
History.,
!:: messages selected
FavoriTes...
Related
Lln~~s .4
Go To...
Search for:
:::upport Cetatts
Maximum !lumber of Resutt:
II00
~!
r.~Fl~
Message List
1St]~
lfO
Status
Status..
Start Ti...
End Time ' Sender...
Sender...
Receiv...
Recerr...
Interface ' lnterfac...
Mark the checkbox for "User-Defined Search Criteria" and choose "Add Predefined" on the dropdown list.
Message Status Overview
Database
.A.rchive
Advanced
Show Messages By:
Maxir
Time Period:
; Message Header Data

User-Defined Search Criteria
Search for:: iAn Values
136
In the popup "Add User-Defined Search Criteria", select the Interface BookingOrderRequest_Out,
select your Search Criterion, and enter the value of the field Surname you specified on the HTTP
client.
Name
Namespace
BookingOrcferRequest_Out
http:flflight .com/agency
User-Defined Search Criteria for

Booking Or derRe<1uest_Out
lfO
Name
Description
! Passengert,lame_XX
Search by passenger last name
PassencferName_##
Search be passenger last name
Value: :stucfent_xx
Now choose "Go" to apply the Search Criterion. Check if the Message List shows your message.
137
138
Messages used in HR Distribution (Exercise 03) go to AEX and IE. AEX is working but the message you sent via IE did
not succeed. Find out the reason why the message created based on the External Employee you created did not work.
Logon to the Integration Server (System RWN) and check the PI Message Monitor
with the hel of the user-defined selection criteria.
Start
sxi monitor
'ifj
Use the new

tab "UserDefined
Selection
Criteria"
sxi_monitoq
View
C!) Standard
0 Process
Len gtt1 of 0 utp ut List
@ Status Group
0 Status
(!) Search for All
F4 Help
available
Search for All
Advanced Selection Criteria
0 Search for One
Search for One
.,~)Value
l::walue
Name
Name
Select the
Name
"NAME"
Name Descr~~Unterta-ceName
NAME Full Name HRMD_ABA.HRMD_ABA05
Enter the
value for the
employee
name that you
supplied
earlier in
transaction
PQ08
(Supports
"Starts With")
ts
I Name
1
Name
Name
iNME
Value
Gino1
Value
Value
139
Errors Inlined
(new)
Receiver Determination: t<,Jo Receiver Could be Determined
Optional: you may select a message and copy the message ID from the message
header main, e.g.
"0050563F-060B-1 ED0-89AE-A63423CAB 12F"
Use transaction SXMS_LMS_CONF to check the existing filter (that is valid for
all exercise rou
Double click
the line with
the filter to
select the filter
Scroll down to
see the
"Search
Criteria for the
Selected
Filter"
Optional
~lfYILGJ.J~I~
Filter List
-
Sndr Party Sender Component

[~rrravei_Agenc,_summer
Rcvr Party Rcvr. Comp Interface N;;me

HRI,ID_ABA.HRMD_ABA05
Interface Namesp;;ce
urn:sap-com:document:sap:idoc:r
~~[QJ~[}]
Sea[ ---}teria for Selected Filter
Name-- "'"'""''.,Pt. f4ethod XPath
-f'.l.O:..ME idif Full Name
iE1 /HRfv1D_ABA05/IDOC/E1PLOGI/ElPITYP/E1PlOOO/STEXT
Dyr
-_J
In edit mode, you see all parameters. Please do not change the criteria!
In case you had copied a message ID in part 2 of the exercise, you can test the
search criteria:
Manage Filters and Search Criteria
@S Test Search Criteria
1~\tYl~IG:ll[}]
Filter List
Sndr Party Sender Component
1~1 Travei_Agenc,'_Summer
Please note that the Message ID has to be entered without delimiter signs.
140
.i;
li l
I ( (l
II I'
umrna
II
Pogc 141
DPI73
141
User Interaction (for example, Business Task Management)
Repository and Governance

II Improved design governance
11111 Eclipse-based design time for service
provisioning
11 Unified WS-RM compliant event
provisioning and subscription
ESB
11111
Single stack ESB capabilities via AAE
11 Increased productivity & richer
connectivity on AAE
11111 Processing of very large files
II Further support of pub I sub scenarios
11 Adoption
of standards (SOAP 1.2, WS
Policy 1.2, WS Trust 1.3, Java SE 6 ... )
Unified Lifecycle Management

II Central monitoring via SAP Solution
Manager
11111 Search for payload attribute values
II Improved upgrade and fault tolerance
. B2BPartner
DPI73
3rd Party
Application
3rd Party
Middlewafe
142

- ......... .
Improved design governance

User-centric perspective in ES Repository
Mass import of external data types in ES
Repository
Find SOA assets by documentation URL
in ES Repository
Mass publication of services from
ES Repository to Services Registry
Auto-publication of service interfaces from
ES Repository to Services Registry
Wizard-based configuration of a central
ES Repository
Usability improvements in Services
Registry
Unified event provisioning and subscription

Definition, implementation, configuration,
monitoring and subscription of WS-RM
compliant events
3Jd.P~Y ......
Application
3rd Party
Middleware
(')Capabilities also available with SAP NetWeaver CE 7.2

Page 143
DPI73
143
Key governance features

1111 Extend SAP's pre-delivered entities (e. g.
service interface) with custom attributes
11111 Define custom lifecycle for assets including
possible transitions and authorizations
1111
1111
Subscribe to object changes to be notified

via e-mail on specific actions (edit, delete)
Web-based Ul for specific scenarios
(search, view, subscribe to objects)
Editors in Eclipse
1111
11111
NWDS-based editors for creating and

editing service interface and data type
Support to use Eclipse based standard
editors for viewing ES Repository content
11 Subscribe to object charrges via ES browser

in NWDS
B2BPartner :
3rd Party
Application
3rd Party
-Middleware-
Improved roles and authorizations

1111 Fine-granular ACL's to restrict actions
(create, edit, delete) on individual objects
11111 Improved logging to ensure transparency
IIIII Enable I disable advanced capabilities
through pre-delivered configuration wizard
Page144
DPI73
144
Single stack ESB capabilities via AAE

11111 AAE with local ES Repository and
Increased productivity and richer

connectivity on AAE
1111
I Doc- and HTTP- adapters in AAE
111111
Very large (binary) file-to-file transfer
11111
Mapping-based message split on AAE
11111
Time-out configuration per communication
channel
1111
Automated Transport for Schema Validation
1111
Increased Integration Directory API support
Creation of Integrated Configuration with

Model Configurator
1111
Increased standards based interoperability

! ;:
IIIII Publish and subscribe messaging for JMS

Topics
1111 Support for SOAP 1.2, WS Policy 1.2, WS
Trust 1.3, Java SE 6
B2B Partner :
3rd Party
ApPJTCatiol'l~
1111
WS-RM based interoperability
with Microsoft .NET 3.5, 4

Page 145
DPI73
145
- L- ~;~~--- J
!:-;~!;
~
Greater visibility into landscapes

Search for payload and adapter-specific
message attributes
!Doc- and performance monitor
Enhanced search for archived messages
Test (ping) for communication channels
Additional message persistence on AAE
Improved upgrade procedures

11111
11111
Automated steps using CTC templates

Flexible upgrade paths
Improved fault tolerance(**)

11111 Optimization of cache refresh
Optimized message processing
11111 "Safe Mode" during startup
Optimization of EOIO handling
Optimized technical acknowledgements
Configuration Wizard with system
parameters settings
Piece list of transported objects in CTS+
111111
111111
111111
111111
111111
B2B-Partner;
3rd Party
-Apr)lication--
3rd Party
Middleware-
(")(Partial) down port to SAP Ne\WeaverP\ 7.~ SP~1 &

EHP 1 sPos
f'age 146
DPI73
146
: ; i j( ' l '
: I
; :
:\
i 1
111
Page 147
DPI73
147
. (I
1Vles~ag1ng and i::ventmg
Synchronous and asynchronous messaging, different message patterns, pub/sub
~:itandards
Support
Web Services (SOAP, WS-RM), metadata (WSDL, XSD), integration-centric

orchestration (BPEL)
~ervice
Enablement & Connectivity
Wrap legacy applications and expose them as managed and reusable services
f:lediation Capabilities
All routing patterns including dynamic routing, data mapping, transformation,
graphical micro-flow based development of flexible mediations
Leanness
Wizard-based integration, lightweight footprint and flexible deployment options
('erformance and Sc::tlabilitv
Page 140
These key characteristics are related to the Enterprise Service Bus. They are also fullfilled by SAP
NetWeaver Pl.
DPI73
148
f}\
Protocol Switching
lnteroperability between consumer and providers with different proprietary protocol:.
?,Extensibility
Ability to add additional transports/bindings cartridges, add additional mediation
capabilities for message enrichment
ntegration into meta data management

Integration with Enterprise Services Repository and Registry, design-time and runtime governance
llonitoring and Management

Local management, federated deployment and management, integration with
enterprise management
)ecurity
SAP NetWeaver PI supports the most commonly named ESB characteristics!
DPI73
149
\vailability of a high number of solutions to allow out-of-the box integration:

From SAP: Pre-packaged process integration content semantically interlinked
with SAP applications and industry solutions
From partners and ISVs; certification programs help to ensure quality
,)NE platform (and not several) to support all integration scenarios:
A2A, 828, interoperability with other ES8s, SOA, ...
)trategic building block of SAP's enterprise SOA infrastructure with clear 3-year
.oadmap
)upport of replacement of 3rd party integration solutions to lower TCO
.nteroperability with other ESBs to protect investments
)upport of most of commonly accepted ESB characteristics
)upport of broad range of operating environments and databases
Page ISO
DPI73
150
:I
,-,
'1 ,
, }i
; 'i ' 1 il I ! 1 II i
n
rn
Pogo IS-I
DPI73
Technical Conn
commun
File/FTP(S) (File Systems I FTP Servers)
with SAP and
JDBC (RDBMS systems)

JMS (Messaging systems, e. g. MQSeries, SonicMQ)
SOAP (Web Services based on SOAP)
WS (Web Services based on WS Reliable Messaging)
HTTP(S) (ASAP and Java)
Mail (Mail Servers via SMTP, IMAP4, POP3)
SAP Business Connector (SAP BC)
Marketplace (SAP Marketplaces)
RFC
IDoc (ABAP and Java)
Proxy (ABAP and Java)
SAP Industry
ness
RNIF 2.0 (RosettaNet)

RNIF 1.1 (RosettaNet)
CIDX (RNIF 1.1)
Page 152
DPI73
152
u
AS2 (EDIINTIHTTP(S))
Protocol: AS2
Automotive
OFTP
Protocol: OFTPIISDN, OFTP/TCPIP
Consumer Products
VAN Access
Protocol: P7 I X.400, VAN FTP
Pharmaceutical
Chemicals
High-Tech
Retail
Business Content
Generic EDI
Protocol: OFTP/ISDN or P7 I X.400, VAN FTP
EDI Converter: ANSI X.12, EDIFACT
Mapping Templates: Purchase order, Order
confirmation, Dispatch advice, Invoice
Mapping Templates within Enterprise Services Repository

Message Library for Enterprise Services Repository
Huge message catalog with EDI XML schemas
Communication Protocols
OFTP/ISDN, P7 I X.400, VAN FTP
Payment (Financial Service Providers)

Protocol: OFTP/ISDN, P7 I X.400, VAN FTP
ED! Converter: EDIFACT, SWIFT
Mapping Templates: Payment orders, Debit
advice, Credit advice, Account Statement
EDI Converter (EDI <-> XML)

AECMA/SPEC 2000, ANSI X.12, CHEM eStandards,
EDIFACT, GALlA, ODETTE, TRADACOM, VDA
*Details are published at SON (direct link)

Page 153
DPI73
153
JOE One World XE

JOE World
Oracle Applications
Peoplesoft
Siebel
re
inC
rn
* Details are publlshed at SON (direct link)

Page 154
DPI73
154
Listing of connected PI
domains in system
Access to PI Monitoring
applications
landscape
SAP Solution Manager
Detailed Seleclio,
Alenlntxn:
Statuti Monitoring
Connectt>On Monitoring
HaT~
: dC'Tln2B':!::-t,<J
Af?-.Jt.VA
SXJ~Jt.V.:O.
8\:J-.J.8:.?,LK3-.J!..VA
8Jh:,e.:.P.l!h~8t.P LU6~Jt..Vt:. !.l~~Jf..VA.C!i4 . . >-6t..>:.U2R-JAVA
u:; . . :..e.:.p
;cc'f.JJ,!0.'.!3l2.!.
: dcrr.Jn ~D >.:~ l~~
ReiJted links
8.!X-.J4VA,84X-.A6AP,V.!X... J4.VA
Page ISS
DPI73
155
Benefits
More detailed monitoring of message processing on the Advanced Adapter Engine
Assurance of better compliance with legal requirements
Improved accountability of the message transformations during message processing
on the Service Bus
Functional Insight
In SAP NetWeaver Administrator
Configuration Management ->Infrastructure >Java System Properties, XPI Adapter: XI
S.we: Me$sage Vers1on:
XMI. Vtlldottion Inbound
Set xiadapter.stage.confparameter to:

No storage
Store on error
Store and continue
Store and return
Me-ssaging System Outbound
."': 2(! i I SAP M3.
Page 156
From Note 1334027:

111
Code 0 = MODE_NO_STORE
The processor continues to the next stage without any storage

111
Code 1 = MODE_STORE_ON_ERROR
The processor stores the message only if its next stage throws an exception.
111
Code 2 = MODE_STORE_AND_CONTINUE
The processor stores the message and continues to its next stage. If its next stage throws an
exception, the processor reschedule the message from this storage and returns.
111
Code 3 = MODE_STORE_AND_RETURN
The processor stores the message, reschedule the message, and return.
Difference between 2 and 3:
The difference is that mode 3 always reschedule the message but mode 2 only reschedules the
message if some error occurs.
Ill Example: Lets say you have one stage A. This means, a message comes in and potentially
persisted at A and transmitted. If A=2: The thread 1 takes the message and persists it at A and
transmits. If no error occurs, it is completed. If some error occurs, the persisted message is
retransmitted by thread 2. If A=3: The thread 1 takes the message and persists it at A. Thread 2
takes the persisted message and transmits.
The difference is which thread performs the steps after stage A. Without stage 3 (different
thread), interference with queue prioritization would take place (by bypassing it).
DPI73
156
Benefits
Consistent usage of classifications
Functional Insight
WSDLs published from Integration Directory with classifications assigned in the ES
Repository are now published together with classifications to the Services Registry
- DPl?:J
DPI73
Poge 157
157
DPI73
158
50106395- 2012 SAP AG. Aile Rechte vorbehalten. SAP und das SAP-Logo sind eingetragene Marken der SAP AG in Deutschland und anderen Landern weltweit.
Business Objects und das Business-Objects-Logo sind Marken oder eingetragene Marken der Business Objects Software Ltd. Business Objects ist ein Unternehmen der
SAP AG. Sybase und das Sybase-Logo sind eingetragene Marken der Sybase Inc. Sybase ist ein Unternehmen der SAP AG. Crossgate ist eine eingetragene Marke der
Crossgate AG in Deutschland und anderen U:indern. Crossgate ist ein Unternehmen der SAP AG.

DPI73

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

DPI73

Uploaded by

Copyright:

Available Formats

DPI73

SAP NetWeaver Process Integration- Delta PI 7.3

Exercise 1: Define and assign Custom Attributes

Exercise 2: AEX configuration with IDoc__ AAE adapter

At the end of this module, you will be able to:

Single stack ESB capabilities through

comp. to dual stack, 90 sec restart*

Standards based interoperabiHty

Major improvements are:

AS Java is based on Java EE 6

Quick access to ES Repository

Governance features like lifecycle

Search and browse for objects,

All ES Repository related functions are

Browse Content, Edit Objects,

The ES Repository can be accessed with two new User Interfaces:

ES Repository, Registry & Integration Directory

System Landscape Directory

Advanced Adapter Engine

Full (dual-stack) SAP

Bypassing Integration Engine

SAP NetWeaver PI 7.3:

You should now be able to

DPI73 Exercise 0: Logon to systems

Hint: Preferences I Session settings I Display: choose "Fullscreen"

## is the group number

5) Logon to all training systems & change your initial password.

At the end of this module, you will be able to:

1) Object type(s): Create

2) Object instance: maintain

I maintain a Custom Attribute Definition (CAD), eclipse has to be used.

In the Web Ul, the custom attributes are visible.

Built-in support to configure the behavior of assets by

Support to search based on custom attributes

Attributes are included in existing transport mechanisms

Assign unique lifecycle for different asset types

.=.' ).(; 1 J S.~P AG .

Recently used objects

You should now be able to

At the end of this module, you will be able to:

1) Specify ES Repository server

Enh!lpti::m Servin: Hnm::;-cr

Window I Preferences I Web Services:

1~- r&-i(..-_~----~/.~;p -c-c.p

2) Open Enterprise Service Repository perspective

2(J11 SAP .4G. PJ! (:qhls

cr.:-ge-0 c;,,- feb C>G, 2lll'~ C.;<;(lJ F11

SWCV, namespaces, and object types are listed .

D1fr0 t.o of d~m\J,(Qj'j')

ES Repository details from the server

Access the Software Component

', C.:::J" Event$

:;, 1::__:r 5-t-rvlce lffitrf<),_:_e:;

; ill SAP ASA 7.10

Note: You cannot create SWCV or

~r;;, Service Interface Overview

tre o~-~:~;~~;-~:~::~; :~ -:~rt):~

H- 5 56--i:<:n',-r,_; t'r.co;,;.-,;'::.:rc; cft\-.s ;tf'<.:e r,t~f.;.::-e

cvl~: '~ :~., , , ,._,.,". ;;:;~~~::~~:::;,,cj """c

'f~ '+ch-~o><: fi-,~ ~,_, .,-;>

(';)'\'''''l""!On: t-.rb~.:6, J~. :.,:.l~i:J.)l ~n

I ----- "'' r,;:,. ;;;-;:",,---- -----::::~

Service Interface Definition

1. Service Interface Overview

cvl~: '~ :~., , , ,._,.,". ;;:;~:::::;,,cj """c