MDIS Question

[Former Member]

Could anyone clarify the following?

We set the file aggregation count = 1 . This means even if we have more than one file in the ready folder still it will process the files one by one meaning first file has to complete then only the next file will pick up and load. This is correct?. Some times we may have many files in the inbound ready folder. We use sinmple workflow also. Does this cause record lock exception?

Some times we get record lock exception and the Import log says u2018operation="Import" import-action="Update (All Mapped Fields)" row="??">The record is currently used in the workflowu201D. But the workflow completed successfully and not holding any record in the workflow

MDIS Configuration file:-

Chunk Size=??? u2013 What exactly this is used for?

No. Of Chunks Processed In Parallel=?? u2013 What exactly this is used for?

[Former Member]

Hi Lamp,

File Aggregation Count:The number of import files to aggregate for batch processing.

As you set it to 1 so your understanding is correct here.

Chunk Size: The Chunk Size value tells MDIS how many records from an aggregated file set to process at a time.Once MDIS processes a chunk of records, it immediately sends this chunk to MDS for import into the repository. When MDS receives the chunk, the Import Slice Size setting controls how many records from the chunk it should process at a time.

Note: The MDM Server is locked during record import.

Note: Each of these parameters must be added manually to the server-level settings in the mds.ini file. If these parameters are not added to mds.ini or have no values set, their default values will be used.

Currently, MDS only and always uses the average of these two values (Import Slice Size Min, Import Slice Size Max).

We use sinmple workflow also. Does this cause record lock exception?

If you are importing records into a workflow, the workflow is not launched until all import slices from an import package have been processed. An import package refers to the complete set of records received from a set of import files aggregated by MDIS.

Note: The port is locked during MDIS processing.

No. of Chunks Processed In Parallel is the number of chunks processed simultaneously during streaming import. Default is 5. This parameter determines how many chunks MDIS can manage simultaneously, counting one chunk per stage plus chunks queued between stages

For more details, refer MDM Console Reference Guide.

http://help.sap.com/saphelp_nwmdm71/helpdata/en/4b/71608566ae3260e10000000a42189b/MDMConsole71.pdf

Hope this helps...

Regards,

Mandeep Saini

[Former Member]

Hi

Your understanding on File aggregation count is Correct.

Regarding the chunk size and no of chunks processed in parallel please refer tobelow self explanatory text from the ref guide:

The Chunk Size and No. of Chunks Processed In Parallel parameters in

mdis.ini help optimize MDIS performance and reduce import times.

The Chunk Size parameter defines the number of virtual extended

records to include in a chunk. Typically, the smaller the chunk size the

better, as smaller chunks can be processed faster within MDIS and also

require less wait time in transactions between MDIS and the MDM

Server. However, setting the chunk size too low can reduce overall

performance because there is a fixed overhead per chunk.

The No. of Chunks Processed in Parallel parameter optimizes the way

chunks are processed within MDIS. Rather than wait for one chunk to

pass through all three processing stages before starting work on the

next chunk, MDIS instead moves chunks from stage to stage as each

chunk is processed (see u201CVirtual Extended Recordsu201D on page 390 for

more information the processing stages within MDIS). This parameter

determines how many chunks MDIS can manage simultaneously,

counting one chunk per stage plus chunks queued between stages.

Hope this clarifies.

Best regards

ravi