Professional Documents
Culture Documents
XI BPM
Email Client
Order Response
Failure
M
A
I
L
Integration Process
4c) XI_MAIL
MI_BPM_TRIGGER_MATCH
MT_BPM_TRIGGER
(DT_BPM_TRIGGER)
DocNum
MI_BPM_TRIGGER
MT_BPM_TRIGGER
(DT_BPM_TRIGGER)
2b) MI_BPM_TRIGGER
4b) MI_BPM_TRIGGER_MATCH
DEMO
XI IS
Order
S
O
A
P
1) MT_ORDER
(DT_ORDER)
CRM
Receiver Determination
2a) ORDERS
(ORDERS05)
I
D
O
C
Sales Order
Middleware
XI IS
ECC
Order Response
F
T
P
4a) MT_ORDERRESPONSE
(DT_ORDERRESPONSE)
Receiver Determination
3) ORDRSP
(ORDERS05)
I
D
O
C
Sales Order
Response
Authored by
Kevin Wilson
With contributions by Alistair Rooney and David Propst
http://www.geniepress.com
http://www.geniepress.com
A big shout out to my fellow road warriors Dave Propst and Alistair Rooney for
their valuable contributions, not only to this quick guide book, but to the SAP
integration community as a whole.
Dave and I have worked several projects together and hes my number 1 go to
guy for Integration Architecture stuff.
Whereas Alistair literally wrote the book on ABAP and Java! Who knows it better
than him? I challenge you to find someone.
Although this book runs the older release of XI, I still have folks finding it useful in
pulling it together for the new versions of PI. The screens may have changed but
the concept and objects havent changed too much. This book helped several
folks find their legs in XI to such an extent that they became XI and now PI
consultants and make a decent living out of it. If this is too old for you then dont
print it and carry on with life, but if it is then know that I am pleased that it has
helped out a little. Please dont ask me to update it to the latest version, as I have
moved on to more fun topics like SAP Event Management and Sybase ESP ;)
Kevin Wilson
Table of Contents
INTRODUCTION
Background ............................................................................................................................... 8
About the Author ....................................................................................................................... 9
How to use this book ................................................................................................................ 9
The Scenario ............................................................................................................................ 10
12
15
Page 4 of 159
71
Page 5 of 159
3.5.5. Email interface between BPE and Email Service ................................................. 104
3.6. Receiver Determination ................................................................................................. 111
3.6.1. DEMO : MI_ORDER ............................................................................................. 111
3.6.2. IP_ORDERS : MI_EMAIL ..................................................................................... 111
3.6.3. SAPECC : ORDRSP.ORDERS05 ........................................................................ 112
3.7. Interface Determination ................................................................................................. 112
3.7.1. DEMO : MI_ORDER : SAPCRM .......................................................................... 112
3.7.2. DEMO : MI_ORDER : IP_ORDERS ..................................................................... 113
3.7.3. SAPECC : ORDRSP.ORDERS05 : DEMO .......................................................... 113
3.7.4. SAPECC : ORDRSP.ORDERS05 : IP_ORDERS ................................................ 114
3.7.5. IP_ORDERS : MI_EMAIL : MAIL_SERVICE........................................................ 114
3.8. Sender Agreements ....................................................................................................... 115
3.8.1. DEMO:MI_ORDER ............................................................................................... 115
3.9. Receiver Agreements .................................................................................................... 115
3.9.1. DEMO : SAPCRM : ORDERS.ORDERS05 ......................................................... 115
3.9.2. SAPECC : DEMO : ORDERRESPONSE ............................................................. 116
3.9.3. IP_ORDERS : MAIL_SERVICE : MI_EMAIL........................................................ 116
3.10. Create and Publish Web Service ................................................................................ 116
120
PHASE 5 : TESTING
122
Table of Contents
Page 6 of 159
GLOSSARY
131
137
138
144
147
151
INDEX TABLE
Table of Contents
156
Page 7 of 159
Introduction
Background
Exchange Infrastructure has grown out of the enormously disparate world of
and I use this in its most general sense Electronic Data Interchange. Exchange
Infrastructure 3.0 brings together a lot of technologies. Some of these
technologies are open standards that have been embraced over the years and
have become the de facto standard. These are XML and its cousins SOAP,
WSDL, XPATH, XSLT and so on. Other technologies are proprietary to SAP AG,
like IDOCS, ALE, ABAP Objects and even certain class libraries used by Java.
One of the most interesting developments in recent years has been the
emergence of graphical mapping to chart out an organizations business
processes. One of the leaders in this has been the ARIS product. SAP and IDS
Scheer1 have teamed up to bring us Business Process Management or BPM. XI
plays an important role in this by linking the business processes together.
This book describes the process to map a BPM scenario in XI. It covers the 5
phases required:
System configuration
Integration Builder Design
Integration Builder Configuration
SAP Configuration
Testing
It does not try to describe all the functionality that you will encounter in XI and the
BPM module. After all BPM is larger than just XI and conversely XI is more than
just BPM! It does not attempt to provide you with a production solution for the
scenario provided. The scenario is made up to incorporate as many aspects of XI
messaging and BPM as is feasible.
A note about authorization: The tasks in the system configuration phase will take
a higher level of authorization then the remaining 4 phases. The tasks in the first
phase will require the role of SAP_XI_ADMINISTRATOR. The remaining for
phases can be performed by a user with the role of SAP_XI_DEVELOPER.
Introduction
Page 8 of 159
Page 9 of 159
Key:
Italic words
Italic words -> Italic words
Underlined
Transactions
Menu path to follow
Indicates a Tab on a
screen
All figures are labeled with a number. If that figure is referenced in the text then it
is reference with this number. For your convenience a table of figures is listed
after the table of contents.
The Scenario
An external system (DEMO) sends an XML representation of an order through to
XI. We want to transform this order in to a small BPM message destined for the
BPM engine and also transform it in to an ORDERS05 IDoc destined for the
CRM system.
This ORDERS05 IDoc creates a sales order in CRM which is then replicated to
the ECC system, via middleware. The sales order in ECC then generates an
ORDRSP IDoc which is then sent to XI. This ORDRSP IDoc is then transformed
in to a small BPM message that is correlated with the ORDERS BPM message
sent earlier. It is also transformed in to an order response XML message which is
sent through the FTP Adapter to a specific file on the Integration server. The
BPM also has timeout and exception handling capabilities using the alert
framework as well as the email adapter.
Dont Panic this all seems rather daunting at this point but the diagram in
Figure 1 will simplify our task considerably!
Page 10 of 159
Email Client
Order Response
Faliure
Integration Process
M
A
I
L
4c) XI_MAIL
MI_BPM_TRIGGER_MATCH
MT_BPM_TRIGGER
(DT_BPM_TRIGGER)
DocNum
MI_BPM_TRIGGER
MT_BPM_TRIGGER
(DT_BPM_TRIGGER)
2b) MI_BPM_TRIGGER
4b) MI_BPM_TRIGGER_MATCH
DEMO
XI IS
Order
S
O
A
P
1) MT_ORDER
(DT_ORDER)
CRM
Receiver Determination
2a) ORDERS
(ORDERS05)
I
D
O
C
Sales Order
Middleware
XI IS
ECC
Order Response
F
T
P
4a) MT_ORDERRESPONSE
(DT_ORDERRESPONSE)
Receiver Determination
3) ORDRSP
(ORDERS05)
I
D
O
C
Sales Order
Response
Page 11 of 159
PHASE 1 :
SYSTEM CONFIGURATION
Page 12 of 159
3.
4.
5.
6.
7.
The Systems Landscape Directory can be viewed as a separate entity to the Integration Builder.
So, if we had to access the SLD from the Integration Builder every time we made a change, it
would slow the whole process down considerably. The obvious solution was to provide a cache
that holds the SLD information within the Integration Builder. Unfortunately this means that when
we make a change to the SLD our changes will not be picked up by the Integration Builder. For
this reason we always clear the SLD cache and reload the SLD Software Components.
Page 13 of 159
3.
4.
5.
6.
Page 14 of 159
PHASE 2 :
Mapping
Message Interface
(WSDL)
(Receiver Determination,
Interface Determination,
Sender agreement,
Receiver agreement)
Interface Mapping
Message Type
(XSD)
Message Mapping
Data Type
(XSD)
These elements will then be used in the XI configuration phase to assemble the
required interface.
Page 15 of 159
2.1.1. XI_MAIL
1. Open up your applicable namespace under the DEMCOMPONENT
software component
2. Open Interface Objects
3. Right click External Definitions -> New
4. Enter Name (XI_MAIL) and Description -> Create
5. Change category to XSD
6. Click
to Import External Definitions
7. Browse to the XIMAIL30.XSD file -> Open (See definition at APPENDIX
C)
8. Your External definition should look like that shown in Figure 9
Page 16 of 159
an important step, if you do not see the messages defined here; there was
a problem with the import.
Naming Conventions
At this point Id like a quick word, if you dont mind. Its important that we emphasize the
importance of Naming Conventions here. As you have probably noticed, Data Types have a
prefix of DT, Message Types have a prefix of MT and Message Interfaces have MI and so on.
This is not the whole picture, however. You may want to qualify the interfaces further by using a
suffix of OUT for outbound (Remember this is outbound from the server never from XI) and IN
for inbound. Trust us, (Were professionals), defining your standards up front will take away hours
of frustration later.
Page 17 of 159
2.2.1. DT_ORDERS
1. Right click data types -> New
2. Enter Name and Description -> Create
3. Complete the definition as shown in Figure 11 (See the XSD definition in
APPENDIX A on page 137) and yes, if youre feeling lazy, you could just
import this but keying it in will give you a better understanding of the
whole process!
4. Save
2.2.2. DT_ORDERRESPONSE
1. Right click data types -> New
2. Enter Name and Description -> Create
3. Complete the definition as shown in Figure 12 (See the XSD definition in
APPENDIX A on page 139)
Page 18 of 159
4. Save
2.2.3. DT_BPM_TRIGGER
1. Right click data types -> New
2. Enter Name and Description -> Create
3. Complete the definition as shown in Figure 13 (See the XSD definition in
APPENDIX A on page 141)
4. Save
Page 19 of 159
2.3.1. MT_ORDER
1. Right mouse click Message Types -> New
2. Enter Name and Description -> Create
3. Select the data type DT_ORDER by clicking
4. Save
Page 20 of 159
2.3.2. MT_ORDERRESPONSE
1. Right mouse click Message Types -> New
2. Enter Name and Description -> Create
3. Select the data type DT_ORDERRESPONSE by clicking
4. Save
2.3.3. MT_BPM_TRIGGER
1. Right mouse click Message Types -> New
2. Enter Name and Description -> Create
3. Select the data type DT_BPM_TRIGGER by clicking
Page 21 of 159
4. Save
Page 22 of 159
2.4.1. MI_ORDER
1.
2.
3.
4.
5.
6. Save
2.4.2. MI_ORDERRESPONSE
1.
2.
3.
4.
5.
Page 23 of 159
6. Save
2.4.3. MI_BPM_TRIGGER
1.
2.
3.
4.
5.
6. Save
2.4.4. MI_BPM_TRIGGER_MATCH
1. Right mouse click Message Interfaces -> New
2. Enter Name and Description -> Create
Page 24 of 159
6. Save
2.4.5. MI_EMAIL
1.
2.
3.
4.
5.
6.
Page 25 of 159
8. Save
Page 26 of 159
2.6.1. MM_Order_to_ORDERS05
1.
2.
3.
4.
Page 27 of 159
8. Save
2.6.2. MM_Order_to_BPM_TRIGGER
1.
2.
3.
4.
Page 28 of 159
8. Save
2.6.3. MM_ORDERS05_to_OrderResponse
1.
2.
3.
4.
Page 29 of 159
8. Save
2.6.4. MM_ORDRSP_to_BPM_TRIGGER
1.
2.
3.
4.
Page 30 of 159
8. Save
2.6.5. MM_BPM_to_EMAIL
1.
2.
3.
4.
Page 31 of 159
8. Save
IM_Order_to_ORDERS05:
o Source interface: MI_ORDER
o Target interface: ORDERS.ORDERS05
o Message mapping: MM_Order_to_ORDERS05Error! Bookmark not defined.
IM_Order_to_BPM_TRIGGER:
o Source interface: MI_ORDER
o Target interface: MI_BPM_TRIGGER
o Message mapping: MM_Order_to_BPM_TRIGGER
IM_ORDRSP_to_OrderResponse:
o Source interface: ORDRSP.ORDERS05
o Target interface: MI_ORDERRESPONSE
o Message mapping MM_ORDERS05_to_OrderResponse
IM_ORDRSP_to_BPM_TRIGGER_CATCH:
o Source interface: ORDRSP.ORDERS05
o Target interface: MI_BPM_TRIGGER_MATCH
o Message mapping MM_ORDRSP_to_BPM_TRIGGER
IM_BPM_to_EMAIL:
o Source interface: MI_BPM_TRIGGER
Page 32 of 159
2.7.1. IM_Order_to_ORDERS05
1.
2.
3.
4.
5.
6.
7.
8.
9.
10. Save
2.7.2. IM_Order_to_BPM_TRIGGER
1. Open Mapping Objects
Phase 2 Integration Builder Design Genie Press 2007
Page 33 of 159
10. Save
2.7.3. IM_ORDRSP_to_OrderResponse
1.
2.
3.
4.
Page 34 of 159
10. Save
2.7.4. IM_ORDRSP_to_BPM_TRIGGER_CATCH
1.
2.
3.
4.
5.
6.
7.
8.
9.
Page 35 of 159
2.7.5. IM_BPM_to_EMAIL
1.
2.
3.
4.
5.
6.
7.
8.
9.
Page 36 of 159
10. Save
2.8.1. Actions
6 Actions need to be created as follows:
Send_Order: Demo system sends order using Message Interface
MI_ORDER. It has 2 receivers, being the Integration Process
(IP_ORDER) and the CRM system
Receive_Order: Receive the ORDERS IDoc in to the CRM system
Receive_BPM_TRIGGER:
Receive
the
Message
Type
MT_BPM_TRIGGER
via
the
Message
Interface
MI_BPM_TRIGGER. This will be correlated (through field DocNum)
to the MI_BPM_TRIGGER_MATCH Message Interface
Send_OrderResponse: Send the ORDRSP IDoc from the ECC
system. This IDoc will then have 2 receivers, being the Integration
Process (IP_ORDER) and the DEMO system
Page 37 of 159
Receive_OrderResponse:
Receive
the
Message
Type
MT_OrderResponse
via
Message
Interface
MI_ORDERRESPONSE
Receive_BPM_TRIGGER_MATCH: Receive the Message Type
MT_BPM_TRIGGER
via
the
Message
Interface
MI_BPM_TRIGGER_MATCH. This then correlates (through field
DocNum) to the MI_BPM_TRIGGER Message Interface of the
Send_Order action
2.8.1.1. Send_Order
1.
2.
3.
4.
5.
Page 38 of 159
8. Save
2.8.1.2. Receive_Order
1.
2.
3.
4.
5.
8. Save
2.8.1.3. Receive_BPM_TRIGGER
1.
2.
3.
4.
Page 39 of 159
8. Save
2.8.1.4. Send_OrderResponse
1.
2.
3.
4.
Page 40 of 159
8. Save
2.8.1.5. Receive_OrderResponse
1.
2.
3.
4.
5.
Page 41 of 159
8. Save
2.8.1.6. Receive_BPM_TRIGGER_MATCH
1.
2.
3.
4.
5.
Page 42 of 159
8. Save
Page 43 of 159
Page 44 of 159
9. Click Apply
10. Your Integration Scenario should now look as described in Figure 43. Note
that these vertical columns that we are building up are termed Swim
Lanes. If youve done any swimming youll know why, if not, dont worry
about it.
Page 45 of 159
22. Now we need to add our actions that we created earlier to the Integration
Scenario are you getting excited yet?
23. Right mouse click the Order swim lane at the top -> Insert Action
24. Expand your Software Component for the Demo system and select the
Action Send_Order -> Apply as shown in Figure 46
Page 46 of 159
26. We now will add the 2 receive actions. One in the integration process and
1 in the CRM system
27. Another way of adding actions is to drag and drop them on to the right
swim lane at the right position. This is pretty cool so well use this
technique to add all the actions!
28. Drag the Receive_BPM_TRIGGER to the 2nd swim lane below the level of
the send order action (this ensures that its not treated as a parallel action
to the send order. We need this in order to link them together).
29. Similarly Drag the Receive_Order to the 3rd swim lane (CRM) below the
level
of
the
send
order
action
and
adjacent
to
the
Receive_BPM_TRIGGER action (again this tells XI not to treat these as
parallel or synchronous actions).
Page 47 of 159
30. Now add the last 3 actions (to end up with a view as shown in Figure 49)
as follows:
a. Send_OrderResponse in ECC system down and to the right of Receive_Order
b. Receive_OrderResponse in Demo system down and to the left of
Send_OrderResponse
c. Receive_BPM_TRIGGER_MATCH in Integration Process template down and to
the left of Send_OrderResponse and adjacent to Receive_OrderResponse
31. This is great! We have all the actions, but now we need to focus on
linking the actions together
32. Single click the Send_Order action -> Hold down the Shift Key and single
click the Receive_BPM_TRIGGER action to select both
33. Right mouse click one of the selected actions -> Create Connection
Between Selected Actions as shown in Figure 50
Page 48 of 159
39. Similarly connect the following actions together and add the respective
interface mappings shown in parentheses:
a. Send_Order -> Receiver_Order (IM_Order_to_ORDERS05)
b. Send_OrderResponse -> Receive_OrderResponse
(IM_ORDRSP_to_OrderResponse)
c. Send_OrderResponse -> Receive_BPM_TRIGGER_MATCH
(IM_ORDRSP_to_BPM_TRIGGER_CATCH)
Page 49 of 159
41. We can now define our action start and end points
42. The Send_Order is our start action so Right mouse click Send_Order
43. Click Define Action as Start Action as shown in Figure 53
44. Similarly
we
will
define
the
Receive_OrderResponse
and
Receive_BPM_TRIGGER_MATCH actions as end actions
45. Right mouse click Receive_OrderResponse and select Define Action as
End Action
46. Right mouse click Receive_BPM_TRIGGER_MATCH and select Define
Action as End Action
47. After completion of the definition of the Integration Process described in
2.9. Integration Process starting on page 51, you need to add the
Integration Process to the Integration Process Component
a. Double click the Integration Process component and select the
Integration Process tab
b. Select IP_ORDERS as the name from the dropdown list
c. Your definition should now look as shown in Figure 54
Page 50 of 159
Page 51 of 159
If the order response message does not come in 5 minutes, then fire off
an alert and send an email
If the order response message is received in time then end the process
gracefully
If the entire integration process does not end in 30 minutes then fire off an
alert and cancel the process. This prevents an orphan process from
hanging around in the BPM engine forever, which will use unnecessary
resources.
For the completed view of what we will develop see Figure 56. We will be
working in the Container, Properties and Graphical Definition windows. We will
also switch to the Correlation Editor to perform the correlation mapping there.
2.9.1. IP_Orders
1.
2.
3.
4.
Page 52 of 159
3. Click the
button in the Type field to choose Message Interface
MI_BPM_TRIGGER
4. To add the Order Response message, type OrderResponse in the name
field and choose Abstract interface in the Category field
5. Click the
button in the Type field to choose Message Interface
MI_BPM_TRIGGER_MATCH
6. The container should look as shown in Figure 58
3. In the Properties window you will notice that the Receive step is displayed
there.
Phase 2 Integration Builder Design Genie Press 2007
Page 53 of 159
Page 54 of 159
Page 55 of 159
21. With the receive orders step highlighted, click the Value field next to the
Activate Correlation name and choose DocNum as shown in Figure 67
2.
3.
4.
5.
Page 56 of 159
6.
7.
8.
9.
10. Your scenario and Container Operation step should look as shown in
Figure 72
Page 57 of 159
3.
4.
5.
6.
Page 58 of 159
2.
3.
4.
5.
6.
7.
Page 59 of 159
9. For the target message, from the dropdown ( ), select the BPM_EMAIL
Interface Variable created in item 1 of this step.
10. Your transformation step should now look as shown in Figure 81
Page 60 of 159
2.
3.
4.
5.
6.
7. Select SystemError from the dropdown for field Exception. This system
error exception was defined against the block defined in STEP 4 Create Block on
page 57
8. Leave the other fields as defaulted. Your completed send step properties
should look as shown in Figure 84
Page 61 of 159
2.
3.
4.
5.
6.
2.
3.
4.
5.
Page 62 of 159
Figure 89: Integration Process - Add Alert Control step to Exception SystemError
2.
3.
4.
5.
6.
7.
Figure 90: Integration Process - Add Cancel Process Control step to Exception
SystemError
Page 63 of 159
2.
3.
4.
5.
Page 64 of 159
Figure 93: Integration Process - Add Cancel Process Control step to Exception TimeOut
Figure 94: Integration Process - Add receiver step for order response
2. In the Properties window change the step name from Receive1 to Receive
Order Response
3. Click the
button in the Message field to choose the Interface Variable ->
OrderResponse as shown in Figure 95
Page 65 of 159
4. Select DocNum from the dropdown menu for variable Use Correlations
5. Save
6. Select DocNum from the dropdown menu for variable Activate
Correlations
7. Save
8. Your Send Order Response step properties should now look as shown in
Figure 96
Page 66 of 159
2.10.1. TESTALERT
1. Click the create alert category icon
2. This adds a line to the ALV grid. Fill in the Alert Category name
TESTALERT and a description BPM Alert
3. Hit Enter to see the alert as shown in Figure 101
Page 67 of 159
4. Click the Dynamic Text checkbox on. The 2 tabs Long and Short Text
and Optional Subseq. Activities disappear. Clicking this checkbox
allows you to pass variables to the alert in the BPM process as
shown in STEP 5a Create process control step to throw alert in
deadline branch on page 59
5. Leave the other fields with their defaults
6. Save. Your alert now looks as shown in Figure 102
2.10.2. TESTALERT1
Adding the 2nd Alert Category called TESTALERT1.
1. Click the create alert category icon
2. This adds a line to the ALV grid. Fill in the Alert Category name
TESTALERT1 and a description BPM Exception Alert
3. Hit Enter to see the alert as shown in Figure 103
Page 68 of 159
4. Click the Dynamic Text checkbox on. The 2 tabs Long and Short Text
and Optional Subseq. Activities disappear. Clicking this checkbox
allows you to pass variables to the alert in the BPM process as
shown in STEP 6a Create System Error alert in exception branch on
page 63. This is very useful to us!
5. Leave the other fields with their defaults
6. Save. Your alert now looks as shown in Figure 104
Page 69 of 159
Page 70 of 159
PHASE 3 :
The system landscape and interface repository steps need to have been
completed prior to starting this phase.
1. Start the Integration Directory of the Integration Builder
3.1.1. Order_OrderResponse_Demo
1. Select the Scenarios tab
2. Right mouse click in the window and choose New
3. Enter Description as Order and Order Response Scenario
4. Click
to select the Integration scenario IS_Orders we configured in 2.8.
Integration Scenario on page 37
5. Youll notice that the configuration scenario is changed to IS_Orders which
is our Integration Scenario name. If you want to change it change it before
creating the configuration scenario. Once youve changed the name
(Order_OrderResponse_Demo) is should now look as shown in Figure
106
6. Click create
7. Save
Page 71 of 159
3.2.1. IP_ORDERS
1. Right mouse click on Integration Party (Under Service without a party in
your newly created scenario)
2. Click New
3. Click continue on the screen shown in Figure 107
Page 72 of 159
9. Enter IP_ORDERS as the Logical System. (If you dont do this step then
you will get an error that the Logical System could not be determined for
IP_ORDERS
Page 73 of 159
2. Click Create
3. On the Receiver tab click
4. Click
Page 74 of 159
7. Click
8. Save
2. Click Create
3. On the Receiver tab click
4. Click
5. Save
Page 75 of 159
3.4.1. CC_DEMO_SOAP_SENDER
1. Expand the Business Service DEMO
2. Right mouse click on Communication Channel -> New
3. Enter Communication Channel name CC_DEMO_SOAP_SENDER
4. Click Create
5. Click
for the Adapter Type field to choose the SOAP adapter
6. Enter the following entries:
a. Select the Sender radio button
b. Transport Protocol: HTTP
c. Message Protocol: SOAP 1.1.
d. Adapter Engine: Integration Server
e. Default Interface Namespace: http://www.demo.com/XI
f. Default Interface Name: MI_ORDER (NB: This is required for the
web service to work properly)
g. Quality of Service: Exactly Once = Asynchronous call
Page 76 of 159
7. Save
3.4.2. CC_DEMO_FILE_RECEIVER
1. Expand the Business Service DEMO
2. Right mouse click on Communication Channel -> New
3. Enter Communication Channel name CC_DEMO_FILE_RECEIVER
4. Click Create
5. Click
for the Adapter Type field to choose the File adapter
6. Enter the following entries:
a. Select the Receiver radio button
b. Transport Protocol: File System (NFS)
c. Message Protocol: File
d. Adapter Engine: Integration Server
e. Target Directory: /var/xiftp
Page 77 of 159
f.
g.
h.
i.
j.
7. Save
3.4.3. CC_EMAIL
1. Expand the Business Service MAIL_SERVICE
2. Right mouse click on Communication Channel -> New
3. Enter Communication Channel name CC_EMAL
4. Click Create
5. Click
for the Adapter Type field to choose the Mail adapter
6. Enter the following entries:
a. Select the Receiver radio button
Page 78 of 159
b.
c.
d.
e.
f.
g.
Page 79 of 159
7. Save
3.4.4. GeneratedReceiverChannel_IDoc
Page 80 of 159
Page 81 of 159
6. Click continue
STEP 2 Outgoing Message
1.
2.
3.
4.
5.
6. Continue
STEP 3 Sender Agreement
1. The system should default in the SOAP Communication Channel you
created in 3.4.1. CC_DEMO_SOAP_SENDER on page 76
Page 82 of 159
2. Continue
STEP 4 Receiver Determination
1. The system should display the screen as shown in Figure 118
2. Click Continue
Page 83 of 159
2. Click Continue
STEP 6 Receiver Agreement
1. The system should display the screen as shown in Figure 120
Page 84 of 159
2. Click Continue
STEP 7 Assign object to a Configuration Scenario
1. The system should display the screen as shown in Figure 121
2. From
the
dropdown
list
select
your
Order_OrderResponse_Demo
scenario
3. Click Finish
4. You should get the Configuration Wizard log that shows you all the objects
that were generated as shown in Figure 122
Page 85 of 159
Page 86 of 159
6. Click continue
STEP 2 Outgoing Message
1.
2.
3.
4.
5.
6.
Page 87 of 159
7. Continue
STEP 3 Sender Agreement
1. The system should default in the Sender agreement that you created in
STEP 3 Sender Agreement on page 82
2. Continue
Page 88 of 159
2. Click Continue
STEP 5 Interface Determination
1. The system should display the screen as shown in Figure 128
Page 89 of 159
2. Click Continue
STEP 6 Receiver Agreement
1. The system should display the screen as shown in Figure 129
2. Click Continue
STEP 7 Assign object to a Configuration Scenario
1. The system should display the screen as shown in Figure 130
2. From
the
dropdown
list
select
your
Order_OrderResponse_Demo
scenario
Page 90 of 159
3. Click Finish
4. You should get the Configuration Wizard log that shows you all the objects
that were generated as shown in Figure 131
Page 91 of 159
Page 92 of 159
6. Click continue
STEP 2 Outgoing Message
1.
2.
3.
4.
5.
Page 93 of 159
6. Continue
STEP 3 Sender Agreement
1. The system should default in the Sender agreement that you created in
STEP 3 Sender Agreement on page 82
2. Continue
Page 94 of 159
4. Click Continue
STEP 5 Interface Determination
1. The system should display the screen as shown in Figure 137
Page 95 of 159
2. Click Continue
STEP 6 Receiver Agreement
1. The system should display the screen as shown in Figure 138
3. Click Continue
STEP 7 Assign object to a Configuration Scenario
1. The system should display the screen as shown in Figure 139
2. From
the
dropdown
list
select
your
Order_OrderResponse_Demo
scenario
Page 96 of 159
3. Click Finish
4. You should get the Configuration Wizard log that shows you all the objects
that were generated as shown in Figure 140
Page 97 of 159
Page 98 of 159
6. Click continue
STEP 2 Outgoing Message
1.
2.
3.
4.
5.
6.
Page 99 of 159
7. Continue
STEP 3 Sender Agreement
1. The system should default in the Sender agreement that you created in
STEP 3 Sender Agreement on page 82
3. Continue
3. Click Continue
STEP 6 Receiver Agreement
1. The system should display the screen as shown in Figure 147
4. Click Continue
scenario
3. Click Finish
4. You should get the Configuration Wizard log that shows you all the objects
that were generated as shown in Figure 149
7. Click continue
STEP 2 Outgoing Message
1.
2.
3.
4.
5.
6. Continue
STEP 3 Sender Agreement
1. The system should default in the Sender agreement that you created in
STEP 3 Sender Agreement on page 82
2. Continue
2. Click Continue
STEP 6 Receiver Agreement
1. The system should display the screen as shown in Figure 156
2. Click Continue
scenario
3. Click Finish
4. You should get the Configuration Wizard log that shows you all the objects
that were generated as shown in Figure 158
3.8.1. DEMO:MI_ORDER
3. Click Continue
4. Click propose URL -> Change as follows:
a. http://<srv>:<adapter_port>/XISOAPAdapter/MessageServlet?chan
nel=<party>:<service/system>:<cchannel>) -> Continue
i. <srv> = Server running XI
ii. <adapter_port> = Adapter engine port = 8000
iii. <party> = If communicating outside of your landscape this is
the party you have identified
iv. <service/system> = Sending system or service
v. <cchannel> = Communication channel
b. Our value is:
http://mysapapps02.sapgenie.com:8000/XISOAPAdapter/Message
Servlet?channel=:DEMO:CC_DEMO_SOAP_SENDER
5. On entering the required URL the screen look as shown in Figure 172
6. Click Continue
7. Click
on the name field to select the message interface MI_ORDER as
shown in Figure 173
9. Click Continue
10. Specify sender as shown in Figure 175:
- Service: DEMO
- Interface Name: MI_ORDER
- Interface Namespace: http://www.demo.com/XI
PHASE 4 :
SAP CONFIGURATION
Since we are using IDocs and the IDoc adapter we need to configure the IDoc
adapter and port.
4.1.1. SAPCRM
1. On the XI server use Transaction IDX1
2. Create a new port SAPCRS and complete the Port, client and RFC
destination (Ensure the RFC destination to the CRM system exists and is
operational. Use SM59 to set up and test)
3. This Port relates to the port listed in the communication channel (for the
IDoc adapter) for the business system SAPCRM described in 3.4.4.
GeneratedReceiverChannel_IDoc on page 80.
4. Your port definition should look something like that shown in Figure 178
4.2.1. ORDERS05
This is where you register the allowable IDoc types metadata for the IDoc
adapter. i.e. If you dont put an entry here for the IDoc type that you wish you will
get a metadata error in XI when it tries to read the IDoc metadata from the
system.
1. On the XI server use Transaction IDX2
2. Click new
3. Enter IDoc type ORDERS05 and applicable port SAPCRM as shown in
Figure 179
4. Click Continue
5. The message should come back that the structure was loaded
successfully
6. The client list under the port comes from the RFC destination setting that
you have loaded using IDX1. Your screen should look similar to that
shown in Figure 180
PHASE 5 :
TESTING
Phase 5 Testing
Phase 5 Testing
Phase 5 Testing
6. Click OK
7. Ensure MI_ORDER.wsdl is selected as shown in Figure 186
8. Click OK
9. This ensures that you have the right WSDL for going forward
10. Click OK
11. This brings you to the Window to select soap operation name as shown in
Figure 187
Phase 5 Testing
14. Enter the values we have used to test before as described in 5.1.1. Create
a sample XML payload on page 122. See Figure 188 for the entered data
15. From the menu select Soap -> Send request to server as shown in Figure
189
Phase 5 Testing
Phase 5 Testing
1.
2.
3.
4.
Phase 5 Testing
Glossary
Glossary
Glossary
ABAP
ABAP is a powerful programming language provided by SAP that can be used to
extend the functionality of SAP.
Abstract Interface
An abstract interface is an interface that can be used both inbound and
outbound.
Adapter Engine
The adapter engine is used to connect the integration engine to external systems
via various adapters.. Adapters are used to convert the messages into specific
protocols and formats for the external systems that they were designed for. For
example: the JDBC adapter is used to convert messages into database queries
and execute them against external database systems.
ALE
Application Link Enabling (ALE) is a middleware tool provided by SAP to link
SAP applications with both other SAP applications and non-SAP applications.
Alert
An Alert is a message that is sent when a pre-configured condition is reached
and typically used to monitor for exception conditions in computer systems and
business processes. Alerts can be delivered via e-mail, fax, or SMS. SAP has
extensive functionality for defining, monitoring, and routing Alerts.
Asynchronous Message
The message is "non-blocking". The sending application does not wait for a
response message from the receiving service and continues processing. A
response to the message will come in a separate "call-back" message if required.
See also synchronous.
BPM
Business process Management (BPM) commonly refers to the design and
processing of Integration Processes.
Business Service
A Business Service is used to represent a system that sends and receives
messages. Business Services are similar to Business Systems except that they
are not stored in the System Landscape Directory (SLD). You would typically
use Business Services to represent systems of your business partners because
there systems are not in your landscape.
Business System
Glossary
Business systems are defined in the System Landscape Directory (SLD) and
represent the logical systems that are the senders and receivers of messages.
Communication Channel (CC)
A communication channel defines the adapter (protocol) that will be used to
communicate messages to a business system or service.
Correlation
A correlation is used to match XML messages that are participating in an
instance of an Integrating Process. In a correlation you define XML elements that
are used to join one or more XML messages. You must specify a correlation in a
receive step of an Integration process so that XI will know what inbound
message to match with the run-time instance of the Integration Process.
Data Types
A Data Type is an XML Schema Definition (XSD) and is used to define the
structure of a message type. A data type can be used to validate payloads of
messages.
IDOC
An IDOC is an electronic document that is in a SAP proprietary format for
exchanging data between systems. There are IDOC formats for exchanging
almost any business document, transaction, or master data object.
IDOC Meta Data
IDOC Meta Data is used to validate and process IDOCs. This Meta Data is
managed by transaction IDX2 and can be loaded from the external SAP system
via RFC.
Integration Builder
This is the central tool for the design and configuration of XI objects. The
integration builder is divided into two areas: Design and Configuration. These two
areas are referred to as: Design Integration Repository and Configuration
Integration Directory.
Integration Directory
The Integration Directory is where all XI configuration objects are stored. The
Integration builder is used to manipulate objects in the integration repository. The
Integration Server accesses the Integration Directory to determine how to
process messages based on these configuration objects.
Integration Engine
This is the central run-time component of the integration server. It is responsible
for receiving, processing, mapping, and sending of XML messages.
Integration Process
Glossary
An integration process is where you define a cross system business workflow for
processing messages that span multiple business systems.
Integration Repository
The integration Repository is where all XI design objects are stored. The
Integration builder is used to manipulate objects in the integration repository.
Integration Scenario
An Integration Scenario is used to document the integration between business
systems. It can contain links to all of the objects that involved in the exchange of
messages between systems.
Integration Server
The Integration server is the central engine for processing messages in
Exchange Infrastructure. The Integration Server uses setting in the Integration
Directory to determine what business systems to send inbound messages to and
what mappings are required in the process.
Interface Determination
An Interface Determination is used to define which inbound interface and
interface mapping a message will be processed by. Interface Determination
entries are selected based on the sender, outbound interface, and receiver.
Interface Mapping
Interface Mappings are used to register a message mapping program to an
inbound and outbound interface in the integrating repository. XI uses the
Interface Mapping to select the message mapping programs associated with
request and response messages for the specified interfaces.
Message Interfaces
A Message Interface defines an interface between application systems that is
both programming language and platform independent. In a Message Interface
you define the message type and communication parameters of the interface.
Communication parameters define a message as inbound or outbound and
asynchronous or synchronous.
Message Mapping
A Message Mapping is used to transform one XML message into another.
Message mappings are defined by using the XI graphical mapping editor that is
accessed in the design side of the Integration Builder.
Message Types
A Message Type references the data type that it used to define the structure of a
message.
Namespace
Glossary
**TEMP**.
Receiver Agreement
A receiver agreement is used to determine how to transform a message so that it
can be processed by a receiver. This occurs during outbound processing.
Receiver Determination
A receiver determination is used to define the services that a message will be
sent to. XI uses the sending service, party, and message type to select a receiver
determination entry.
RFC
RFC (Remote Function Call) is the name for the standard SAP interface for
communicating between SAP systems. RFC can be used to call a function
remotely on another SAP system or a non-SAP system that has implemented a
RFC interface using the SAP RFC SDK.
Runtime Workbench
The Runtime Workbench (RWB) is the central tool for monitoring the processing
and performance of messages and for the monitoring and testing the individual
components of Exchange Infrastructure.
Sender Agreement
A Sender Agreement is used to determine how to transform a message so that it
can be processed by the Integration Engine. This occurs during inbound
processing.
SLD
The System Landscape Directory is a server application that stores information
on the hardware and components in your SAP landscape. XI uses the SLD to
store information on business systems, technical systems, products and software
components.
SOAP
SOAP (Simple Object Access Protocol) is an XML-based protocol for accessing
Web services allowing disparate applications to exchange information over
networks using XML syntax. SOAP acts as an envelope to package the XML
messages sent between client applications and Web services. WSDL and SOAP
work together with WSDL providing detailed descriptions of a Web service and
SOAP providing the actual data transport between the Web service and the
requesting client application (usually over HTTP).
Software Catalog
The software catalog is part of the SLD and is used to store information on the
products and software components in the SAP landscape. This is where new
Glossary
software components need to have been created before they can be used for
new development.
Software Component Version
Software component versions are the packages that are used in XI to organize
development objects in XI and are defined in the software catalog.
Synchronous Message
The message will block. The sending application will wait for a response from the
receiving service before continuing processing. See also asynchronous.
System Landscape Directory (SLD)
The System Landscape Directory is a server application that stores information
on the hardware and components in your SAP landscape. XI uses the SLD to
store information on business systems, technical systems, products and software
components.
WSDL
WSDL (Web Services Description Language) is an XML-based language used to
describe and locate Web services. It is the language used by UDDI (Universal
Description, Discovery, and Integration), which is an XML-based registry where
businesses list information about themselves and their available Web services.
WSDL works hand-in-hand with SOAP, where WSDL describes a Web service
and the functionality it provides, and SOAP is used by the client application to
actually call the functions listed in the WSDL description.
XML
The eXtensible Markup Language (XML) is a specification from the World Wide
Web Consortium (W3C) that defines a meta language for describing data. In
XML applications, data is described by surrounding it with customizable, textbased tags that give information about the data itself as well as its hierarchical
structure.
XPATH
XPATH is a language for addressing parts of an XML document.
XSD
An XML Schema Definition (XSD) is an instance of an XML schema written in the
XML Schema language. An XSD defines a type of XML document in terms of
constraints upon what elements and attributes may appear, their relationship to
each other, what types of data may be in them, and other things. It can be used
with validation software in order to ascertain whether a particular XML document
is of that type, and to produce a Post-Schema Validation Infoset.
XSLT
Glossary
Glossary
APPENDIX A.
Abbreviations Used
Abbreviation
BPM
BPE
CRM
DT
ECC
ERP
IDoc
IS
IM
IP
IS
MI
MM
MT
RWB
SLD
SOAP
XI
XML
Description
Business Process Management
Business Process Engine
Customer Relationship Management
Data Type
ERP Central Component Part of the ERP solution
Enterprise Resource Planning
Intermediate Document
Integration Server
Interface Mapping
Integration Process
Integration Scenario
Message Interface
Message Mapping
Message Type
Runtime Work Bench
System Landscape Directory
Simple Object Access Protocol
Exchange Infrastructure
Extensible Markup Language
XSD
WSDL
XSLT
APPENDIX B.
Data Types
XSD DT_ORDERS
<?xml version="1.0" encoding="ISO-8859-1"?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://www.demo.com/XI"
targetNamespace="http://www.demo.com/XI">
<xsd:complexType name="DT_ORDER">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
bc376cb0725011da8f80001321b36514
</xsd:appinfo>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="Order_Num" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
2b77a3506c0811dabc3ec49fac172862
</xsd:appinfo>
<xsd:documentation xml:lang="EN">
PO Number
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="Customer_Num" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
2b77a3516c0811da8d10c49fac172862
</xsd:appinfo>
<xsd:documentation xml:lang="EN">
Customer Number
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="Delivery_Date" type="xsd:dateTime">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
2b77a3526c0811dab62ec49fac172862
</xsd:appinfo>
<xsd:documentation xml:lang="EN">
Expected Delivery Date
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="Order_Line" maxOccurs="unbounded">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
2b77a3536c0811daa027c49fac172862
</xsd:appinfo>
<xsd:documentation xml:lang="EN">
Line Item Detail
</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="Line_num" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
XSD DT_ORDERRESPONSE
<?xml version="1.0" encoding="ISO-8859-1"?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://www.demo.com/XI"
targetNamespace="http://www.demo.com/XI">
<xsd:complexType name="DT_ORDERRESPONSE">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
a80801c0725311dacdc4001321b36514
</xsd:appinfo>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="Order_Num" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
2b77a3506c0811dabc3ec49fac172862
</xsd:appinfo>
XSD DT_BPM_TRIGGER
<?xml version="1.0" encoding="ISO-8859-1"?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://www.demo.com/XI"
targetNamespace="http://www.demo.com/XI">
<xsd:complexType name="DT_BPM_TRIGGER">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
c73bad80725311da9e18001321b36514
</xsd:appinfo>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="DocNum" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
bb38f2506c1711da9677c49fac172862
</xsd:appinfo>
<xsd:documentation xml:lang="EN">
IDoc Number
</xsd:documentation>
</xsd:annotation>
</xsd:element>
APPENDIX C.
WSDL FILES
MI_ORDER.WSDL
<?xml version="1.0" encoding="ISO-8859-1"?>
<wsdl:definitions xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:p1="http://www.demo.com/XI"
name="MI_ORDER" targetNamespace="http://www.demo.com/XI">
<wsdl:types>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://www.demo.com/XI"
targetNamespace="http://www.demo.com/XI">
<xsd:element name="MT_ORDER" type="DT_ORDER" />
<xsd:complexType name="DT_ORDER">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
532bab806c0811da8cbdc49fac172862
</xsd:appinfo>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="Order_Num" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
2b77a3506c0811dabc3ec49fac172862
</xsd:appinfo>
<xsd:documentation xml:lang="EN">
PO Number
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="Customer_Num" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
2b77a3516c0811da8d10c49fac172862
</xsd:appinfo>
<xsd:documentation xml:lang="EN">
Customer Number
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="Delivery_Date" type="xsd:dateTime">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
2b77a3526c0811dab62ec49fac172862
</xsd:appinfo>
<xsd:documentation xml:lang="EN">
Expected Delivery Date
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="Order_Line" maxOccurs="unbounded">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
2b77a3536c0811daa027c49fac172862
</xsd:appinfo>
<xsd:documentation xml:lang="EN">
Line Item Detail
</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
APPENDIX D.
EXTERNAL FILES
APPENDIX E.
Message Mappings
MM_Order_to_ORDERS05
The following is a text view of the message mapping. All constants have been
added between the parentheses.
E.g. setting field DIRECT of Segment EDI_DC40 to constant 2 is depicted:
/ORDERS05/IDOC/EDI_DC40/DIRECT=const(2)
MM_Order_to_BPM_TRIGGER
The following is a text view of the message mapping. All constants have been
added between the parentheses.
MM_ORDERS05_to_OrderResponse
The following is a text view of the message mapping. All constants have been
added between the parentheses.
E.g. setting field DIRECT of Segment EDI_DC40 to constant 2 is depicted:
/ORDERS05/IDOC/EDI_DC40/DIRECT=const(2)
/ns0:MT_ORDERRESPONSE/Status=const(01)
/ns0:MT_ORDERRESPONSE/Order_Line=/ORDERS05/IDOC/E1EDP01=
/ns0:MT_ORDERRESPONSE/Order_Line/Line_num=/ORDERS05/IDOC/E1EDP01/POSEX=
/ns0:MT_ORDERRESPONSE/Order_Line/Line_Status=const(01)
/ns0:MT_ORDERRESPONSE/Order_Line/Material=ifWithoutElse(stringEquals(/ORDERS05/IDOC/E1EDP01/E1EDP1
9/QUALF=, const(002)), /ORDERS05/IDOC/E1EDP01/E1EDP19/IDTNR=)
/ns0:MT_ORDERRESPONSE/Order_Line/Quantity=/ORDERS05/IDOC/E1EDP01/MENGE=
/ns0:MT_ORDERRESPONSE/Order_Line/Price=/ORDERS05/IDOC/E1EDP01/VPREI=
MM_ORDRSP_to_BPM_TRIGGER
The following is a text view of the message mapping. All constants have been
added between the parentheses.
E.g. setting field DIRECT of Segment EDI_DC40 to constant 2 is depicted:
/ORDERS05/IDOC/EDI_DC40/DIRECT=const(2)
/ns0:MT_BPM_TRIGGER/DocName=const(ORDRSP)
MM_ BPM_to_EMAIL
The following is a text view of the message mapping. All constants have been
added between the parentheses.
E.g. setting field DIRECT of Segment EDI_DC40 to constant 2 is depicted:
/ORDERS05/IDOC/EDI_DC40/DIRECT=const(2)
/ns1:Mail/From=const(webmaster@sapgenie.com)
/ns1:Mail/To=const(Kevin@sapgenie.com)
/ns1:Mail/Content_Type=const(text/html)
/ns1:Mail/Content=concat(const(<b>Key field</b> :), /ns0:MT_BPM_TRIGGER/Key1=)
Index Table
A
ABAP Objects 6
Abstract asynchronous 19
Abstract interface 47, 49
Actions 33, 34, 35, 36, 37, 38, 39, 42, 43, 44,
45, 46
Receive_BPM_TRIGGER 33, 35, 36, 43, 44,
45
Receive_BPM_TRIGGER_MATCH 34, 38,
39, 44, 46
Receive_Order 33, 35, 43, 44
Receive_OrderResponse 33, 37, 38, 44, 45,
46
Send_Order 33, 34, 42, 43, 44, 45, 46
Send_OrderResponse 33, 36, 37, 44, 45
Adapter
EMail 7
File 19, 73, 89
FTP 7
IDoc 7, 9, 19, 22, 23, 33, 35, 36, 72, 78, 88,
94, 116, 117, 136
Mail 74, 101, 142
SOAP 19, 72, 73, 77, 83
XI 83, 95, 100
Adapter Engine 72, 73, 75, 122, 124
adapter framework 9
Adapter Specific Identifiers 69
Adapter Type 72, 73, 74
ALE 6
alert 7, 48, 55, 59, 63, 64, 65, 125
alert category 62, 63, 64, 66
fixed recipients 65
role 40, 42, 65
Alert Configuration 62
alert framework 7
Alert Inbox 125
ARIS 6
Assign 45, 47, 52, 53, 65, 81, 87, 92, 93, 99,
105
Asynchronous 19, 20, 21, 22, 57, 72
B
Binary 74
BPM See Business Process Management
Correlation Editor 48, 50
Graphical Definition 48, 49, 50, 51, 52, 56,
57, 61
BPM engine 7, 19, 47, 48
BPM process 14, 19, 23, 33, 64, 65
BPM scenario 6, 9, 23
Index
business landscape 9
Business Process Management 6, 132
Business Service 70, 71, 72, 73, 74, 77, 83, 89,
101
Business services 9
Business System 41, 72, 78, 88, 94
business systems 9
C
cache 10
communication channel
IDoc 72
Communication Channel 72, 73, 74, 78
Content Encoding 75
File Construction Mode 74
File Type 74
Message Protocol 72, 73, 75
SOAP 78
Transport Protocol 72, 73, 75
Write Mode 74
communication channels 9, 72, 76
configuration scenario 67
Configuration Scenario 67, 81, 86, 92, 99, 105
container 47, 48, 49, 52, 55, 59
Container 48, 49, 50, 52, 55, 59
container element 55
Container Elements 49
Container Operation step 52, 53
Container Operation step 53
Container Operation step 53
Container Operation step 55
correlated 7, 14, 19, 33
correlation 47, 49, 50, 51, 61
Correlation Container 50
correlation mapping 48
CRM 7, 9, 19, 33, 41, 42, 43, 72, 76, 116, 132
Customer Relationship Management See CRM
D
data type 14, 15, 16, 28, 132, 133
Data Type 12, 15, 16, 132
DT_BPM_TRIGGER 18
DT_ORDER 14, 16, 17, 133, 139
MT_BPM_TRIGGER 18
E
ECC 7, 9, 19, 23, 33, 41, 42, 44, 72, 88, 94, 132
Electronic Data Interchange 6
F
FTP 7, 14
G
GeneratedReceiverChannel_IDoc 76
H
HTTP 72
I
Idoc
ORDRSP 7, 9, 23, 25, 26, 28, 30, 31, 33, 36,
45, 91, 97, 108, 109, 110, 150
IDoc 132
ORDERS 7, 9, 14, 15, 19, 23, 24, 29, 33, 35,
46, 80, 98, 103, 107, 109, 110, 111, 112,
114, 146
ORDERS05 7, 24, 29, 117, 146, 147, 148,
149
IDOCS 6
IDS Scheer 6
imported IDocs 28
Inbound asynchronous 19
Inbound Interfaces 35, 37, 38
Incoming Message 77, 83, 88, 94, 100
Integration Builder 9, 62, 112
Integration Directory 9, 10, 67, 119
Integration Engine 122, 123
Integration Process 19, 41, 43, 44, 46, 47, 48,
49, 50, 51, 52, 53, 54, 55, 56, 57, 58, 59, 60,
61, 62, 68, 69, 83, 95, 100, 132
Abstract Interface 55
Activate Correlation 52
Activate Correlations 62
block 53, 54, 55, 56, 57, 58, 59, 60
control step 55, 57, 58, 59, 60, 61, 64
Correlation List 50
Correlation Name 50
deadline branch 54, 55, 56, 57, 61
Index
L
Logical System 69
M
Mapping Interface 12
Mapping Objects 24, 25, 26, 27, 29, 30, 31, 32
Message Type
ORDERRESPONSE 17
Message Interface 12, 16, 19, 20, 21, 22, 29,
30, 31, 32, 33, 34, 36, 37, 38, 49, 50, 51, 55,
71, 76, 114, 132
P
port 113, 116, 117, 141
Q
Quality of Service 72
R
Receiver Agreement 80, 86, 92, 98, 104, 111,
112
receiver agreements 76
Receiver Determination 79, 85, 91, 97, 103,
107, 108
Receiver radio button 73, 74, 97, 103
Receiver tab 70, 71
RFC destination 116, 117
Runtime Workbench 62, 65, 122, 123, 124, 125
namespace 11, 13
NFS 73
O
Outbound asynchronous 19
outbound interface 34, 36
Outbound Interfaces 34, 36, 70
Outgoing Message 78, 83, 89, 95, 101
Index
Target Field 52
Test configuration 119
Testing 6, 118, 120
timeout 7, 57, 60
Transaction
ALRTCATDEF 63
IDX1 116, 117
IDX2 117
SM59 116
SWI1 125
SXMB_IFR 9
W
web service 72, 113, 114, 115, 120
Web Services Description Language See
WSDL
Wizard 76, 77, 82, 88, 93, 94, 99, 100, 106, 113
Configuration 77, 82, 88, 94, 100
Configuration log 81, 87, 99, 105
workflow 47
workflow log 125
WSDL 6, 115, 120, 121, 132, 139
DT_ORDERS 15
ORDERRESPONSE 14, 15, 16, 25, 30, 37,
70, 92, 112, 148, 149
XI_MAIL 13, 19, 22, 23, 27, 32
XIAPPLUSER 122
XML 6, 7, 9, 14, 23, 118, 119, 120, 121, 122,
132
XML payload 118, 119
XML Schema Definition See XSD
XMLSpy 118, 120
XPath 51, 53
XPATH 6
XSD 12, 13, 15, 16, 28, 132, 133, 134, 136, 142
XSLT 6, 132
XI Message
DT_BPM_TRIGGER 14, 16, 136
Index