This document describes how to create an inbound interface using integrate batch mode with Skyvva connector module.
Batch data processing is an efficient way of processing high volumes of data, where a group of transactions is collected over a period of time. Data is collected, entered, processed and then the batch results are produced. So, now we are going to create an inbound interface using integrate batch with Skyvva connector module
Initially, we have to start with Salesforce Skyvva. This interface is also the same as “How to create an inbound interface to post a single sObject?” but few things to be added in Skyvva interface settings and in the module parameters configuration.
Skyvva interface creation
Create an interface, for example, “integrateBatch” as shown below.
maximum integrate Batch size will be 5000
As we are using integrate batch So, we have to check the Batch mode checkbox as shown below
Now save the interface and download the WSDL from the classic mode.
Import WSDL into ESR
First, we have to create a namespace in ESR like “urn:skyvva:integrateBatch“.
Now create an external definition under the namespace like below. Here the WSDL is for Account. So, we can give the name as AccountIntegrateBatch.
Import the WSDL and save and activate the external definition.
- Source data type
Create sender data type as shown below
after creating the source data type click on save and activate.
- Source message type
Create the message type as shown below.
- Outbound Service Interface
Create an Outbound service interface, in that select category as outbound and select the respective message type.
then save and activate the outbound service interface.
- Inbound Service Interface
Create an inbound service interface, in that select category as inbound and select the respective external definition.
Save and active the inbound service interface.
- Message Mapping
Create message mapping as shown below
Insert the respective source and target structure and then do the mapping.
Now save and activate the message mapping.
- Operation Mapping
Create Operation mapping as shown below
Select the respective outbound and inbound service interfaces and also the message mapping then save and activate the operation mapping.
- Mapping logic flow with Skyvva runtime
You have to map business data from SAP e.g. IDoc, BAPI or Proxy into the Skyvva WSDL business structure. This business structure is the result of your operation mapping in PO and will be passed into the soap receiver channel. This structure will be converted by the Skyvva module “Salesforce/Transformation” which is a custom module used in the soap receiver channel.
We have to use Skyvva connector module in the soap receiver channel.
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 system e.g. for the SAP-Backend. 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 SOUP UI 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
Starting from version 2.27 Skyvva provides a single module, “Salesforce/GetSessionID_V4”, to be used with SOAP receiver channels. Module parameters are outlined below
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.
This parameter holds the path in which the session id is being stored
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
A flag that actives or deactivates the session pooling. Set for better performance
It will show the request payload of skyvva
This parameters holds the security token from salesforce. Necessary only of configured in the salesforce instance
It displays the SAP PI parameters in the output log
This parameter is the salesforce username
Defines the webservice operation in skyvva
It holds the password of the salesforce user used to log in to the salesforce
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 the “outbound processing” tab, we have to specify the receiver channel.
Test the Inbound Interface.
Triggering the data from the Source system. Now we have to check the result in Salesforce batch control board as shown below.
Now click on View to see the attachment.
As we are sending 2 records from Source system.
Now we can see the successful messages in message monitoring.