ROA_general_gerneric_Template.png

Check your email or visit Credly to claim and share this badge

View on Credly

Go to My Home

Congratulations

Certificate_icon.png

By completing this SAP Learning Journey, you are now prepared to book your certification exam.

Congratulations!

Mountain_White_background.png

Exploring the Technical Essentials of SAP Commerce Cloud

Congratulations Modal

cleanFiles/bookmap_SAP_Commerce_Cloud_Essentials_for_Develope_en-US_learning-sap-com_lsc-prod.zip (MMCP-DROPZONE) - 2023-10-23T13:02:50.000Z

Distributed ImpEx

<div id="content"><p tabindex="0">ImpEx is well-suited to handling a lot of data. But it can still get bogged down by very large data sets.</p><p tabindex="0">Wouldn't it be great to delegate some of that work to other cluster nodes? Distributed ImpEx can do that.</p><div class="kalturaVideoLessonWrapper"><div id="1_vpbfpso9" data-testid="video" class="kalturaVideoLessonContainer"></div></div><p tabindex="0">More information about Distribute ImpEx can be found on the SAP Help Portal: <a href="https://help.sap.com/docs/SAP_COMMERCE_CLOUD_PUBLIC_CLOUD/aa417173fe4a4ba5a473c93eb730a417/3e0138c9bfc642349cad227cfcd72d9f.html" target="_blank">ImpEx Distributed Mode</a>.</p></div>

C4H34b  SAP Commerce Essentials for Developers course - Lesson 6 -21-25

In this topic, you'll learn about distributed ImpEx and how it differs from regular ImpEx. Distributed ImpEx is an extended feature based on the existing ImpEx implementation.  It has been available starting as of version 6.0 of Commerce. The idea behind distributed ImpEx is to split up the import process into separate batches,  then distribute them across the cluster, with the aim of handling large-scale import tasks more efficiently. Distributed ImpEx leverages the existing ImpEx framework to parse and analyze input,  dump unresolved lines, and use the TaskEngine to process single batches of data. It works in the following three phases. In the Prepare and Split phase: a large ImpEx file is read line-by-line and split into batches.  Each header starts a new batch. Value lines are added to a batch until the batch size reaches a set limit.  In the Single task execution phase, the batches are distributed to all available servers in the cluster.  On each server, the TaskEngine executes each assigned batch individually.  That means each task is executed in a single thread.  Since batches are processed across the cluster, they are executed in parallel.  In the Finish phase: the whole process ends.  Clean-up work is done and both the status and result of the overall CronJob is set.  When invoked in the UI, there isn’t much difference between normal ImpEx and distributed ImpEx.  You can execute distributed ImpEx from HAC or from Backoffice, in the same manner you execute regular ImpEx. Just remember to check the “Distributed Mode” checkbox to enable the feature before execution. It’s also possible to enable “distributed impex” mode when you are coding on the API level, similarly to the way of regular ImpEx. To enable it, use the ImportConfig API as the following example. Please note that, before the importService is invoked to execute the import, you should set the distributed impex property  of the import config object to “true.” Finally, let’s take a quick look at the capability comparison table between regular and distributed ImpEx. First, regular ImpEx uses only one server, while the entire server cluster is used to support distributed ImpEx. So where regular ImpEx can only process one line at a time, distributed ImpEx can process multiple lines simultaneously. In some situations, multiple database transactions can be triggered for each line in regular ImpEx.  By contrast, each batch in distributed ImpEx involves a single database transaction. You might also have noticed that JDBC batch mode is used in distributed ImpEx. Furthermore, regular ImpEx persists data using a mix of jalo and service layer direct mode , also known as model mode,  while distributed ImpEx handles persistence solely using model mode. Because of the nature of a distributed ImpEx batch, a single lookup query is triggered for all lines in a batch.  By contrast multiple lookup queries can be triggered for lines in regular ImpEx. If any references are missing in ImpEx scripts, both regular and distributed ImpEx can retry unresolved lines. Last, but not least, regular ImpEx cannot be aborted once started, while it is possible to abort a  running distributed ImpEx job using out-of-the-box API calls. If you want more details about distributed ImpEx, please look at the dedicated documentation in the SAP help portal.

Share feedback

Follow guided learning and develop the skills you need at your own pace

Join a moderated learning group to engage with our experts and peers

Find the right learning resources to drive your career as a developer

Sign up to access exclusive student learning journeys

Discover the SAP product knowledge you need to help you progress in your career

Develop your skills

Learn.png

Want to learn more about the value of learning with SAP?

View available SAP Certifications on SAP Learning 

Purchase a subscription and book your exam

Validate your SAP expertise

SAP Certification validates your skills, sets you apart from the crowd, and demonstrates you have the knowledge you need to succeed.

Certify.png

Accelerate your career 

Upskill in key innovation topics through openSAP's free, expert-led online courses, microlearning, and podcasts.

Join SAP Community and connect with a global network of experts and peers to ask and answer questions.

Search for SAP product documentation or browse all SAP Learning Journeys to become competent in the SAP solutions you need.

Log in to SAP Learning Hub and access the entire SAP Learning portfolio, live practice systems, and social learning opportunities.

Find free tutorials, trials, downloads, and technical product information in the SAP Developer Center.

Book live classes (online and in person) and purchase SAP Certification and SAP Learning Hub subscriptions.