This document describes how to create an inbound interface using Integrate AutoSwitch mode with SKYVVA connector module.
What is Auto-Switch mode?
Auto-switch mode is a data processing mode provided by SKYVVA. When the auto-switch mode flag checked, It means that Agent automatic switch SKYVVA API based on a number of record and IntegrateMaxSize, IntegrateBatchMaxSize. And when the flag is unchecked it means that data is integrated with normal mode (no batch or bulk) no matter what is the size of records. Before configuring Auto-Switch Mode, you have to know about the parameters:
- Integrate Max Size: Maximum number of records that SKYVVA Integration Agent can integrate using method integrate. The default value is 200. If the number of records to be integrated is bigger than this value, Agent will switch the API method automatically.
- Integrate Batch Max Size: Maximum number of records that SKYVVA Integration using method integrate Batch. The default value is 5000. If a number of records to be integrated is bigger than this value, Agent will switch to use the Bulk API method automatically.
If the number of records (Data) <= Integrate Max Size, Interface will run in Normal Mode.
If the number of records (Data) > Integrate Max Size and number of records (Data) <= Integrate Batch Max Size, Interface will run in Batch Mode.
If the number of records (Data) > Integrate Batch Max Size, Interface will run in BULK Mode.
2. SKYVVA interface creation
Create an interface, for example, “AutoSwitch_IN” as shown below.
maximum integrate Batch size will be 5000
Now save the interface and download the WSDL from the classic mode.
Step 3 – Import WSDL into ESR
First, we have to create a namespace in ESR like “urn:skyvva:integrateAutoSwitch“.
Now create an external definition under the namespace like below. Here the WSDL is for Account. So, we can give the name as ED_Account.
Import the WSDL and save and activate the external definition.
- Sender 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.
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.
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 SOAP UI as a source. So, here we are using SOAP in the sender channel.
Provide the necessary details as shown and then 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 must be specified.
Configuration of module parameters are described in detail below
- SKYVVA Module Parameters
|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.||Skyvva_SAP_Salesforce|
|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://ap4.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 email@example.com|
|SforceWebServiceOperation||Defines the webservice operation in skyvva||integrateAutoSwitch|
|pwdSforceLoginPassword||It holds the password of the salesforce user used to log in to the salesforce||xxxxxxx|
This parameter determines how many records are split into chunks of the package size. For example if PI message contains 1000 records and the value of this parameter is 100 then we will get 10 batches each contain 100 records.
Ex – 1000
|sforceBulkMode||It specifies the mode of Bulk||Skyvva Bulk/SFDC Bulk|
|skyvvaVersion||Skyvva version needs to be specify here||Ex. 2.44|
|SforceBulkOperation||This parameter is set when the interface uses the Bulk API. The bulk API enables transferring of mass data||X|
|SforceBulkInterfaceId||It specifies the name of the skyvva interface||AccountintegrateAutoSwitch|
|SforceUseAutoSwitchMode||If the number of records (Data)<=Integrate Max Size, Interface will run in Normal Mode.|
If the number of records (Data)>Integrate Max Size and number of records (Data)<=Integrate Batch Max Size, Interface will run inBatch Mode.
If the number of records (Data)>Integrate Batch Max Size, Interface will run in BULK Mode.
This parameter will switch automatically based upon the above results.
Maximum number of records that SKYVVA Integration using method integrate Batch. The default value is 5000. If a number of records to be integrated is bigger than this value, Agent will switch to use the Bulk API method automatically.
|SforceIntegrateMaxSize||Maximum number of records that SKYVVA Integration Agent can integrate using method integrate. The default value is 200. If the number of records to be integrated is bigger than this value, Agent will switch the API method automatically.||200|
|SforceShowSAPChannelParameters||When set displays the SAP PI parameters in the output log||X or Empty|
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 Inbound Interface.
Triggering 10 records from the Source SOAP UI.
We have to check the result in SKYVVA message board as shown below.
Triggering 15 records from SOAP UI.
We can see the message in batch control board
Now triggering 60 records from SOAPUI
As we set package size as 20 in the channel configurations. So we can see three attachments. Each contains 20 records.