This document explains us about how to create skyvva asynchronous inbound interface to send base 64 string attachment from SAP PI/PO to Skyvva with new V3 adapter module
Steps needs to be done in Skyvva
Create Asynchronous Inbound Interface
New V3 works only with Skyvva message type.
Create Metadata Provider:
Create Istructure Repository:
Under Repository create message type:
Click on new to create new message type as shown below
the below pop-up wizard will open. Provide the message type name, type as Salesforce sObject and the SObjectType as the one which we are going to use the Salesforce Object then click on Save to save the message type.
Below is the created message type
Now use these created metadata provider, repository and Message type while creating the inbound interface.
Inbound skyvva Interface –
In this example i am creating the interfaces under “Attachment_Test“
Provide all the required details and save the interface. After that click on “Open Mapping” to do the mapping.
Do the mapping as shown below
Download the inbound interface XSD to import to SAP PO for mapping.
In SAP PI/PO we need to create Asynchronous interface
With respect to SAP its an outbound Interface(SAP to Salesforce)
Import WSDL into ESR
First, we have to create a namespace in ESR like “http://SAP2SF/Attachment”.
Now create an external definition under the namespace like below. we can give the name as ED_ContentVersion_IN
Import the XSD and Save and activate it.
We need to create Datatype, Messagetype and Service Interface for Sender system as we are using SOAPUI.
Data type for Sender
Here we are selecting the base64Binary for the field versionData as shown below. In this field we are going to send file attachment from SAP PO.
Source Message type
Outbound Service Interface
Select the Source message type and save and activate the service interface.
Inbound Service Interface
Create service interface
Select the target message type and save and activate the service interface.
Do the respective mapping and save and activate it.
Operation Mapping for asynchronous inbound interface
Select the outbound and inbound service interface and the message mapping to create operation mapping
Then save and activate it.
Creation of Integrated Configuration Objects
After creating the objects in ESR. We have to configure these objects in the integration directory.
First, we have to create Configuration Scenario.Now enter the name of the scenario, description and choose a folder if you have created then press on create button.
An Integration scenario has the following objects.
- Business System for Sender and Receiver
- Sender and Receiver Communication channel
- Integrated Configuration
These are the objects we should create.
We have to define our business component e.g. for the SOAPUI “BC_SOAPUI“. For Salesforce you can use our proposal “Salesforce” as the business system. We have to import these business systems from SLD.
Configuring the Sender SOAP communication channel
Create sender communication channel as shown below.
Since we are using an SOAPUI as a source. So, here we are using SOAP adapter in the sender channel.
Provide the necessary details. After that save and activate the channel.
Configuring the SOAP receiver channel
Configuration for Tab “General”
Specify the parameters as shown in the above screenshot.
Below is the configuration for the “Advanced” Tab.
The value “TserverLocation” has to be entered for the parameter Variable Header (XHeaderName1).
Below are the settings for Tab “Module”. Here, the SKYVVA module containing the logic for session handling and transformation logic must be specified.
Configuration of module parameters are described in detail below
Skyvva Module Parameters
“Skyvva/V3/Integration” to be used with SOAP receiver channels. Module parameters are outlined below
|IntegrationID||This parameter contains the skyvva engine integration id on Salesforce. Here we recommend to use only Integration name instead of id because if we transport the objects from one environment to other environment IntegrationId will be changed but Integration Name will not be changed.||Attachment_Test|
|SessionGlobalFilePath||This parameter holds the path in which the session id is being stored||/usr/sap/O5B/SYS/global|
|SforceAccessPoint||This parameter represents the URL(endpoint) for getting the session id. The URL is that of the Enterprise WSDL for Salesforce used for logging in and getting the session id||https://test.salesforce.com/services/Soap/c/43.0|
|SessionPooling.Active||A flag that actives or deactivates the session pooling. Set for better performance||X|
|SforceRequestPayload||It will show the request payload of skyvva||X|
|SforceSecurityToken||This parameters holds the security token from salesforce. Necessary only of configured in the salesforce instance||By54dfe0000DerYvvv|
|SforceShowSAPChannelParameters||It displays the SAP PI parameters in the output log||X|
|SforceUsername||This parameter is the salesforce firstname.lastname@example.org|
|SforceWebServiceOperation||Defines the webservice operation in skyvva||integrate|
|pwdSforceLoginPassword||It holds the password of the salesforce user used to log in to the salesforce||xxxxxxx|
Create integrated configuration objects as shown below.
Enter the required data e.g. the Communication Component, Interface and Namespace and then click on create button to create an ICO.
Now go through the tabs from left to right to configure the relevant objects. In this first tab “Inbound Processing” here we have to specify the sender communication channel.
Here in the “Receiver” tab, we have to specify the receiver business system.
In Receiver interfaces tab specify the operation mapping.
In the “outbound processing” tab, we have to specify the receiver channel.
Testing the interface –
Triggering the data from SOAPUI
Message is delivered from SAP PO
Check the message in Skyvva message monitoring.
Click on “related to” to check the transferred data in Skyvva
We are sending the base 64 string from SAP PO to Skyvva as we can see the transferred data below