SAP PO for Beginners Part – 11 – Synchronous Interface Development – SOAP Proxy to SOAP Webservice
In this post, “SAP PO for Beginners Part – 11 – Synchronous Interface Development – SOAP Proxy to SOAP Webservice,” we will guide you through creating a mediator to SOAP web service interface without any initial setup. This will be an ad hoc interface, triggered as needed from ECC, where configuration will take place and be sent to the target web service.
Thus, under is the substance we will be mind boggling in this educational activity:
Outline
Situation
Objects associated with Connection point Advancement
Fabricate Undertaking Administration Store Items
Assemble Correspondence Channels
Assemble Coordinated Setup (ICO)
Testing the Point of interaction
1. Overview:
Imagine a scenario where there is a business requirement to send the XML payload through ABAP Proxy and communicate the same to the recipient web service. You would also need to handle the response from the web service, as it is a synchronous interface. In “SAP PO for Beginners Part – 11 – Synchronous Interface Development – SOAP Proxy to SOAP Webservice,“ we will cover how to effectively manage this process, ensuring smooth communication between the systems.
2. Scenario:
3. Objects involved in Interface Development:
In the first place, we should make information objects for the solicitation and for the reaction. In this model we won’t make information type and message type, rather we are utilizing the Outside Definitions given by the merchant. Outside Definitions are like pre-characterized field structures which you can simply import and use it in Message planning.
There will be 2 Message mappings that must be made. Solicitation to reaction and reaction to ECC yield structure.
Second, we will make a source correspondence channel of connector type Cleanser with Message Convention as XI 3.0, for ECC association. For Cleanser Intermediary association from ECC to PI, I have proactively posted a blog on it To some extent 4 of my “SAP PO for novices” series.
Third, a recipient correspondence channel of connector type Cleanser with Message Convention as Cleanser 1.1.
At last, we will make an ICO and import the shipper, recipient, and activity planning.
4. Build ESR Objects:
Prior to continuing with the making of Correspondence channels, how about we start with the result structure creation.
External Definitions:
Click on Make NEW – > Outer Definitions
Select the classification as WSDL from the dropdown and import the WSDL document. Click on SAVE and Initiate.
Service Interface:
Make two assistance interfaces. The justification behind two help connection points is:
The document is passed from ECC to PI and the reaction from PI to ECC – Outbound Assistance Point of interaction – 1
PI to Web administration and webservice to PI – Inbound Assistance Connection point – 2
Pick the Mode as Simultaneous
Outbound Assistance Connection point:
Inbound Service Interface:
Message Mapping:
Import same message types in source and target region and perform adjusted arranging. If the objective webservice contains username token (username and secret expression for security), add those fields in the objective XSD and import it in message arranging.
The username and secret key the recipient webservice can be different for every client. Like, the outsider would have arrangement different username and secret phrase for dev, QA and Push. What’s more, in the event that you offer a consistent benefit to username and secret word in DEV and on moving ESR objects to QA, you will not have the option to change the certifications in QA as it is unmodifiable.
At these kinds of cases, esteem planning comes into picture.
You should make esteem planning in Joining catalog, yet before that you want to import the standard worth planning capability in the graphical planning region and give source and target outline (simply an irregular worth to relate with diagram you make in Mix registry. Against the construction just, you will appoint username and secret phrase).
On double tapping the worth planning capability, you will be provoked to enter source office, pattern, and target organization construction. Enter an important string, so in future it will be engaging. Up until this point, you haven’t entered any accreditations. With this office pattern, you will dole out this in esteem planning bunch made in ID and referencing the certifications.
Click on SAVE & ACTIVATE.
Value Mapping:
Map the objective office and construction and guide the accreditations in the worth region. At planning runtime, framework will pick the planned certifications. By this way you can have the certifications put away in one spot and can change it in every client.
Solicitation to Reaction planning is finished, next is the webservice reaction to ECC yield structure planning.
In this way, make another message planning and import the necessary WSDL documents at the source and target.
Operation Mapping:
Import both the outbound and inbound help interfaces. Once imported, click on READ Tasks button which would peruse the message types put away in help interfaces.
When done, select the kind of planning and import the message planning made.
Moreover, in the solicitation and reaction we have imported XSL planning record in light of the fact that while sending the solicitation payload to webservice, it just acknowledges Cleanser Envelope payload body, thus while outbound we add Cleanser design to payload and keeping in mind that reaction, we eliminate it, since ECC doesn’t comprehend Cleanser structure.
In the reaction tab, import first the XSL eliminating document and afterward the message planning.
Click on SAVE & ACTIVATE.
ESR Items creation done. We should begin with the Incorporation Items advancement.
5. Build Communication Channels:
Sender Communication Channel:
Open the Joining Catalog – > Snap on Make New symbol and pick Correspondence Channel.
Give the channel a reasonable channel name and namespace and tap on Make. Pick Connector type as Cleanser and Source Radio button.
Message Convention – XI 3.0
That is all there is to it. No extra configs in channel. Click on SAVE and ACTIVATE.
Receiver Communication Channel:
Click and Make New – > Correspondence Channel – > Pick Recipient radio button and connector type as Cleanser with Message Convention as Cleanser 1.1.
Under the Association Boundaries, enter the Objective Webservice URL. As we are adding Cleanser envelope through planning, actually take a look at the choice – Don’t utilize Cleanser Envelope.
Click on SAVE & ACTIVATE.
6. Build Integrated Configuration (ICO):
Click on NEW – > Incorporated Design.
Give the Incorporated design name and namespace. It ought to be indistinguishable from the ESR Outbound Assistance Connection point name and namespace.
Import the source direct and in next tab, select the business part under which the beneficiary correspondence channel is made.
Determine beneficiary condition if any.
Import the Activity planning from ESR. Activity planning will naturally show assuming that you have offered right Support Connection point name and namespace while characterizing Coordinated arrangement name and namespace.
Import the recipient correspondence channel.
Click on SAVE and Enact.
That is finished. We have made Cleanser Intermediary to Cleanser Webservice interface without any preparation. How about we test it.
7. Testing the Interface:
For testing a simultaneous connection point, you can either do it in Cleanser UI or from PI Send Test message wizard or illuminating functionals to set off the exchange.
I will do it from PI Send Test Message Wizard.
I have the XML payload. Explore to the Send Test Message wizard, PI Landing page – > Arrangement and Checking – > Testing tab – > Send Test Message.
Select the Incorporated arrangement you made. Pick the Nature of Administration as Best Exertion. Glue the payload. Click on SEND once finished.
Note: For Simultaneous connection point, you ought to set off from the shipper framework, for this situation ECC. For testing reason, I’m setting off from PI.
1 – PI to Webservice
2 – Webservice to PI to ECC
Both are effective.
To see the effective planning, explore to the message and snap on OPEN MESSAGE button. Under the payload choice you can see the various variants of the payload.
0 – addresses the before-planning variant
2 – addresses the subsequent to planning rendition
That concludes SAP PO for Beginners Part – 11 – Synchronous Interface Development – SOAP Proxy to SOAP Webservice. I hope you found it informative and engaging. If you have any doubts, questions, or suggestions, please feel free to leave your comments below.
YOU MAY BE INTERESTED IN
ABAP for SAP HANA. ALV Report On SAP HANA – Opportunities And Challenges
OData in SAP ABAP: Streamlining Data Exchange and Integration
ABAP on SAP HANA: ATC – ABAP Test Cockpit Setup & Exemption Process