The Skyvva bulk mode can handle more data than the batch mode. It uses the Salesforce bulk API to create ContentVersion (Files) and therefore can handle bigger data sizes than using the REST or SOAP API as we do in the Skyvva batch mode. When you run into the data size limit while using the Skyvva batch mode, you can switch to the Skyvva Bulk mode.
As the operation integrate your old interfaces can be built by using the V2 or V3 connector module with the soap adapter. Therefore we have a similar way to replace the V2 and V3 soap module with the V2 and V3 rest connector modules.
Again here, you don’t need to migrate the ESR object. You need only to make the configuration changes of the Directory object and replace the soap with the rest receiver adapter.
Here is an example of the rest receiver channel.
The same parameters are used as shown above with the operation Integrate XX and Skyvva Batch. What you need to do is here setting the parameter Operation to “Skyvva Bulk” to indicate that the processing mode is a Skyvva bulk operation mode.
The configuration of the OAuth authentication is the same as you have seen above in the Skyvva batch mode. You have to set the consumer-key and consumer-secreat, username, and password. Note that also here the password is the concatenation of the password and the security token.
The parameter to set the package size for the bulk mode is called “BulkPackageSize” and works in a similar way as the package size for the Skyvva batch mode. The processing logic is the same and the setting of the parameter in the module overwrites the setting on the interface. Unlike the package size for batch, you can set this parameter on the Skyvva interface on any version up to 2.49.
6.1 V2 Interface #
You use the module “Skyvva/V2/RestIntegration” here. Note that the OAuth configuration is the same as you have seen for the operation “Integrate XX” and is not repeated here.
Here is an example of the V2 module.
6.2 V3 Interface #
You use the module “Skyvva/V3/RestIntegration” here. Note that the OAuth configuration is the same as you have seen for the operation “Integrate XX” and is not repeated here.
Here is an example of the V3 module.