differ between import manager and import server

[Former Member]

Hi to all,

Can any one explain difference between import server and import manager and how the data will be imported to the same.

Regards

MM

[Former Member · Accepted solution]

Hi reddy,

Can any one explain difference between import server and import manager and how the data will be imported to the same

Please follow the text below, which has been taken from the help.sap.com

Both MDIS and the MDM Import Manager can import data from a source file into an MDM repository. However, each has unique capabilities that distinguish it from the other. When each is used to its advantage, the result is an import strategy which provides the most efficient importing of data possible.

The strength of the Import Manager is its connection to the source data, which enables its interactive map-making capabilities. When the Import Manager connects to a source it preloads the entire source file, giving it knowledge of every field and every value in the source data. This u201Ctotal awarenessu201D is crucial for preparing a complete import map. To help ensure a map is complete, the Import Manageru2019s Import Status tab alerts users to any discrepancies between source data values and the current map. The user can fix these problems interactively within the Import Manager and save the corrected map before any data is imported.

Preloading an entire source file comes at a price, however. It consumes memory on the computer running the Import Manager and very large source files may exhaust the computeru2019s available memory.

By contrast, MDISu2019s strengths are its scalability and automation.

For scalability, instead of preloading the entire source file into the host machineu2019s memory as the Import Manager does, MDIS processes records in a stream by loading a record at a time into memory.

This streaming technique enables MDIS to process much larger source files than the Import Manager, as the demand for memory on the host machine is not affected by the size of the import file.

In addition to file size, file quantity poses a second scalability challenge. For example, a real-time transactional environment may produce a staggering number of files, each containing only one or two records. To import these files individually through Import Manager would be extremely inefficient. MDIS tackles this problem with a file aggregation feature that processes files systematically in batches rather than as individual files, resulting in faster, more efficient import of data.

As it relates to automation, MDIS requires no user intervention to import files to an MDM repository. Instead, it relies on maps created previously within the Import Manager. Once an import file is placed in the appropriate folder, its data is imported automatically into the MDM repository using the rules of the pre-defined import map. Once a file is processed, MDIS scans the repository for the next file to import. This process continues 24 hours a day, seven days a week, until either MDIS or MDM Server are stopped.

The trade-off for this scalability and automation is that if discrepancies between the source data and the import map arise, MDIS cannot u201Cfixu201D these problems by itself. Instead, the u201Cproblem casesu201D can be fixed manually at a later time using the interactive capabilities of the Import Manager. Unlike the Import Manager, however, MDIS can set aside problem records or files and continue importing.

These conceptual and operational differences between the Import Manager and MDIS are summarized in the table below.

Item

Import Manager

MDIS

Source file location

Anywhere

Automatic inbound port

Import process

Interactive

Automatic

Import map state

Editable

Read-only

Object loaded in memory

Entire import file

Individual records

Streaming import support

No

Yes

File aggregation support

No

Yes

Maximum import file size

Limited (50,000 records)

Unlimited

Status location

Import Status Tab

MDM Console/Report file

Error correction prior to import

Yes

No

Exception handling during import

No

Yes

For additional info, kindly refer the link below:

http://help.sap.com/saphelp_mdm550/helpdata/en/43/12036df94c3e92e10000000a1553f6/frameset.htm

GO to-> MDM import Server

Hope it helps.

Thanks and Regards

Nitin Jain

[Former Member]

Hi Reddy,

In addition to above this is from the Reference guide.

Item | Import Manager | MDIS

Source file location | Anywhere | Automatic inbound port

Import proces | Interactive | Automatic

Import map state | Editable | Read-only

Object loaded in memory | Entire import file | Individual records

Streaming import support | No | Yes

File aggregation support | No | Yes

Maximum import file size | Limited (50,000 records) | Unlimited

Status location | Import Status Tab | MDM Console/Report file

Error correction prior to import | Yes | No

Exception handling during import | No | Yes

[http://help.sap.com/saphelp_mdm550/helpdata/en/43/12036df94c3e92e10000000a1553f6/frameset.htm]

Go to MDM Import Server(MDIS) -> Overview -> MDIS versus Import Manager

Regards,

JItesh Talreja

[Former Member]

Hi Reddy,

Following are the major differences between the two:

IM : Import Manager is for Manual Importing of Data i.e. we need to give the input file manually.

IS : Import Server is used to Automize the Import process(Batch Importing) and it takes the input file from Ready folder.It scans the Ready folder after some time interval and if the file exists it gets picked up by Import Server and records get added into the repository depending upon the map used. Once imported it moves the file into the Archive folder else if any error occurs during importing it generates the error log and place it inside the exception folder.

IM : There are restrictions on number of records that can be imported at a time using Import Manager (limit is 50000).

IS : No such restrictions while using Import Server because it automatically split the records in chunks.

Regards,

Jitesh Talreja