Skip to content

Commit adbb14b

Browse files
ggalvesdevsapggalvesdevsap
committed
Updates on Tutorial
1 parent 9eb734c commit adbb14b

2 files changed

Lines changed: 6 additions & 23 deletions

File tree

‎tutorials/modernize-rfc-receiver/modernize-rfc-receiver.md‎

Lines changed: 5 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ tags: [ software-product>sap-integration-suite, software-product>cloud-integrat
88
primary_tag: software-product>sap-integration-suite
99
---
1010

11-
# Learn how to modernize RFC Receiver Communications into API-Based protocols in Cloud Integration.
11+
# Learn How to Modernize RFC Receiver Communications into API-Based Protocols in Cloud Integration
1212
<!-- description --> This tutorial describes the different possibilities regarding generating SOAP Web Services or ODATA APIs using the existing RFC Function Module for a ABAP backend system (e.g., SAP S/4HANA, ECC) inbound communication.
1313
Besides leveraging more modern monitoring capabilities, it allows you an easier migration of your scenarios from SAP Process Orchestration to SAP Integration Suite.
1414

@@ -29,7 +29,6 @@ On this Tutorial, we **won't** cover:
2929

3030
- ABAP techniques and best practices.
3131

32-
---
3332

3433
### Generate Service Provider from RFC Function Module
3534

@@ -77,7 +76,6 @@ A Service Provider is created when your requirement is to expose a Web Service i
7776

7877
> Please note that by doing this, you don't have to re-implement your code on the new service or similar. The new Web Service will wrap the existing Function Module code.
7978
80-
---
8179

8280
### Configure Service Binding in SOAMANAGER
8381

@@ -106,8 +104,7 @@ A Service Provider is created when your requirement is to expose a Web Service i
106104
![Image](Ref/sp_14_2.png)
107105

108106
![Image](Ref/sp_14_3.png)
109-
110-
---
107+
111108

112109
### Test the Service Provider
113110

@@ -124,8 +121,7 @@ A Service Provider is created when your requirement is to expose a Web Service i
124121
![Image](Ref/16.png)
125122

126123
![Image](Ref/16_2.png)
127-
128-
---
124+
129125

130126
### Setting up SOAP Receiver Adapter on Cloud Integration
131127

@@ -138,8 +134,7 @@ A Service Provider is created when your requirement is to expose a Web Service i
138134
2. Select the WSDL as described below.
139135

140136
![Image](Ref/SP_16.png)
141-
142-
---
137+
143138

144139
### [OPTIONAL] Re-Generate Service Provider
145140

@@ -154,8 +149,7 @@ If you need to update the structures of your Web Service, proceed as described b
154149
3. Confirm the operation and activate the object.
155150

156151
![Image](Ref/sp_18.png)
157-
158-
---
152+
159153

160154
### Test yourself
161155

@@ -164,5 +158,3 @@ If you need to update the structures of your Web Service, proceed as described b
164158

165159

166160

167-
168-
---

‎tutorials/modernize-rfc/modernize-rfc.md‎

Lines changed: 1 addition & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ tags: [ software-product>sap-integration-suite, software-product>cloud-integrat
88
primary_tag: software-product>sap-integration-suite
99
---
1010

11-
# Learn how to modernize RFC Sender Communications into API-Based protocols in Cloud Integration.
11+
# Learn How to Modernize RFC Sender Communications into API-Based protocols in Cloud Integration
1212
<!-- description --> This tutorial describes the different possibilities regarding generating SOAP Web Services using the existing RFC Function Module for a ABAP backend system (e.g., SAP S/4HANA, ECC) outbound communication.
1313
Besides leveraging more modern monitoring capabilities, it allows you an easier migration of your scenarios from SAP Process Orchestration to SAP Integration Suite.
1414

@@ -29,7 +29,6 @@ On this Tutorial, we **won't** cover:
2929

3030
- ABAP techniques and best practices.
3131

32-
---
3332

3433
### Generate Service Consumer from RFC Function Module
3534

@@ -79,7 +78,6 @@ A Service Consumer is created when your requirement is to communicate from an AB
7978

8079
![Image](Ref/4.png)
8180

82-
---
8381

8482
### Setting up SOAP Sender Adapter on Cloud Integration
8583

@@ -97,7 +95,6 @@ A Service Consumer is created when your requirement is to communicate from an AB
9795

9896
![Image](Ref/100.png)
9997

100-
---
10198

10299
### Configure a Logical Port in SOAMANAGER
103100

@@ -140,7 +137,6 @@ A Service Consumer is created when your requirement is to communicate from an AB
140137
![Image](Ref/13.png)
141138

142139

143-
---
144140

145141
### Update your ABAP source code
146142

@@ -191,7 +187,6 @@ The code above can be replaced with the following ABAP code in order to invoke t
191187

192188
After proceeding with the changes on your ABAP code, don't forget to `Save` and `Activate` your code.
193189

194-
---
195190

196191
### Test the Service Consumer
197192

@@ -209,7 +204,6 @@ After proceeding with the changes on your ABAP code, don't forget to `Save` and
209204

210205
![Image](Ref/16_2.png)
211206

212-
---
213207

214208
### [OPTIONAL] Re-Generate Service Consumer
215209

@@ -226,7 +220,6 @@ If you need to update the structures of your Web Service, you have two options:
226220
![Image](Ref/50.png)
227221

228222

229-
---
230223

231224
### Test yourself
232225

@@ -235,5 +228,3 @@ If you need to update the structures of your Web Service, you have two options:
235228

236229

237230

238-
239-
---

0 commit comments

Comments
 (0)