Expose SOAP API That Internally Calls Another SOAP Service In OIC
Expose SOAP API in OIC
What is SOAP?
SOAP stands for Simple Object Access Protocol.
SOAP is the XML-based message protocol that enables the distributed elements of an application to communicate. SOAP can be carried over various standard protocols, including the web-related Hypertext Transfer Protocol (HTTP).
SOAP is a lightweight protocol used to create web APIs, usually with Extensible Markup Language (XML). It supports a wide range of communication protocols across the internet, HTTP, Simple Mail Transfer Protocol (SMTP), and Transmission Control Protocol.
SOAP building blocks and message structure example
Simple Object Access Protocol, as a specification, defines SOAP messages that are sent to web services and client applications. SOAP messages are XML documents that are comprised of the following three basic building blocks:
- The SOAP Envelope encapsulates all the data in a message and identifies the XML document as a SOAP message.
- The Header element contains additional information about the SOAP message. This information could be authentication credentials, for example, which are used by the calling application.
- The Body element includes the details of the message that must be sent from the web service to the calling application. This data includes call and response information.

SOAP Specification: Soap API is described by an XML-based document, WSDL.
Sample WSDL:



Now go to the OIC Integration Platform to develop a SOAP API
Step 1: Go to the Sign-in page.
Use Username and Password to log into the OIC Instance.

Step 2: Click on the hamburger button.

Step 3: Click on the Design tab.

Step 4: Click on the Connections tab to create a SOAP Connector.

Step 5: Click on the Create button to configure a SOAP Connector.

Step 6: Search SOAP in the search box and select the SOAP Adapter.

Step 7: Give a suitable name to the SOAP Connector and the role should be Trigger as it is an inbound Integration and click on the Create button.

NOTE: Identifier should populate automatically but we can change this and need to give any unique name.
Step 8: Fill the required credentials and click on Test.

Properties
- Need to upload a WSDL file
Security
- Username Password Token
- OAuth 2.0
- Security Assertion Markup Language (SAML)
- Basic Authentication
Step 9: Click on Validate and Test.

NOTE: The difference between Test and Validate & Test is that Test will just test your connection it will not validate the credentials but Validate & Test will first validate your all credentials and it will test the connectivity.
Step 10: Change the Security to Basic Authentication and Click the Save button after the successful test.

NOTE: Only you can ensure successful connectivity with Salesforce if the Configuration progress bar reaches 100%
Step 11: Click on the left arrow when the connection goes to the Configured stage.

Step 12: Now we need to configure another SOAP Connector with Invoke Role, as it is an Outbound call, that will call an actual soap service.

Step 13: After that, we need to upload that same WSDL file, set the security No Security Policy, and click on Test, after the test we need to click on Save and at least click the left arrow to go back.

Step 14: These are the two SOAP connections that we need, now we need to go to the Integrations tab.

Step 15: Now Click on the Integrations tab and click on the Create button.

Step 16: Click on the Application tab to create a real-time integration.

Step 17: In this create integration page give any suitable name and unique Identifier name and click on create button.

Step 18: After clicking the Create button search for the SOAP connector that we configured previously with Trigger Role, and select the connector.

Step 19: After choosing the connector we need to give some name to the required field and click on the Continue button.

Step 20: Select the Operation “NumberToWords” and click on Continue.

Step 21: After that, we need to click on Continue because we don’t need to configure the Headers.

Step 22: After that, we need to review the summary of the Integration and click on the Finish Button.

Step 23: After clicking on the finish button one Trigger connector and Map will be created.

Step 24: After that, we need to add the SOAP_Invoke connector in between the SOAP Trigger and the Mapper to invoke external Soap service.

Step 25: After choosing the connector we need to give some name to the required field and click on the Continue button.

Step 26: After that, we need to Select the Port “NumberConvertionSoap” and Select the Operation “NumberToWord” and click on the Continue Button.

Step 27: After that, we need to click on Continue because we don’t need to configure the Headers.

Step 28: After that, we need to review the summary of the Integration and click on the Finish Button.

Step 29: After clicking on the finish button, one Invoke connector and Map will be created.

Step 30: Now we need to configure the first map shape, for that we need to double click on the map.

Step 31: After that, we need to map the source “ubiNum” with the target “ubiNum” and click on the Validate button and at last click on the left arrow to close the map.

Step 32: After that, we need to configure the second map shape, for that, we need to double-click on the map.

Step 33: After that, we need to map the source Soap Response “NumberToWordResult” with the target “NumberToWordResult” and click on the Validate button and at last click on the left arrow to close the map.

Step 34: Our Integration is completed now we need to set the Business Identifier, for that we need to click on the (I) button.

Step 35: After that, we need to drag the “uniNum” from the source side and paste it in the Business Identifier field, and click on the save button.

Step 36: After that, we need to click on the left arrow to close our Integration.

Step 37: Our Integration is in the Configured stage, after that, we need to activate our Integration.

Step 38: To activate our Integration we need to hover over the Integration and click on the power button.

Step 39: In this Activate integration page we need to select the Audit and click on the Activate button.

Step 40: After that, we can see our Integration is in the Active stage.

Step 41: After that, we need to hover over the Integration and click on the three dots.

Step 42: After that, we need to click on the “Run details” button.

Step 43: In this Run details page we need to copy the Metadata URL.

Step 44: Now we need to open the SoapUI application to test our SOAP API. We need to click on the SOAP button.

Step 45: Now on this New SOAP Project tab we need to give a Project Name and Initial WSDL (metadata URL that we copied previously) and click on the OK button.

Step 46: After that, we will get a tab like this, now we need to give the Auth details to run our SOAP API.

Step 47: Now we need to select the Authorization as Basic, give the Username and Password, and give any number to the SOAP request and click on the Play button.

Step 48: After hitting the Run button we will get the required Response.

Step 49: We can see the Instance also in the OIC console.

Thank You