mdis.ini

[Former Member]

Hello everyone,

We tried several combinasions in order to run the import server automatically but still it does not work. Can anybody tell us where we did a mistake?

In advance thanks,

Aklilu

Our mdis.ini

[SERVICE]

Server=seaman305

Interval=30

Automap unmapped value=True

Unmapped Value Handling=True

Always use unmapped Value Handling=1

[GLOBAL]

Server=seaman305

Interval=30

Automap unmapped value=True

Unmapped Value Handling=True

Always use unmapped Value Handling=1

String Resource Dir=C:\PROGRA_1\SAPMDM1.5\IMPORT~2\LangStrings\

Log Dir=Logs

SLD Registration=False

Verbose=0x0000

VXR_MAX=25000

[Material_1seaman305MSQL_8_8_4_3]

Login=Admin

Password=

Chunk Size=50000

No. Of Chunks Proccessed In Parallel=5

[mdm_demoseaman305MSQL_19_8_4_3]

Login=Admin

Password=

Chunk Size=50000

No. Of Chunks Proccessed In Parallel=5

[Vendor_55310seaman305MSQL_12_4_4_3]

Login=Admin

Password=

Chunk Size=50000

No. Of Chunks Proccessed In Parallel=5

[michael_theis · Accepted solution]

Hi Aklilu,

just a copy & paste of my reply in the other thread

> We are trying to parameter the mdis.ini and until now it does not work.

Could you specify this? In addition, I've got a few hints:

MDIS has to have the same build version as the MDM Server. In addition, MDIS has to be running (in Windows, you can check this in the Services Screen). Furthermore you should have a look at the Console's port definition (select your repository, go to Admin -> Ports in the menu tree). The port has to be configured correctly (XML Scheme, which map to be used, and so on). Very important: you have to set the port to automatic processing.

Here's a sample for the MDIS.ini:

[GLOBAL]
Version=5540
Server=WDFD00146633A
Interval=30
Automap Unmapped Value=True
Unmapped Value Handling=Add
Always Use Unmapped Value Handling=False
VXR_MAX=25000
Verbose=0xFFFF
-- Verbose OFF:     0x0000
-- Verbose ON:      0xFFFF
-- FI  Verbose:     0x0001
-- XML Verbose:     0x0002
-- MAP Verbose:     0x0004
-- THRD Verbose:    0x0008
-- PARSER Verbose:  0x0010
-- STRUCTX Verbose: 0x0020
-- VALUEX Verbose:  0x0040
-- IMPORTX Verbose: 0x0080
String Resource Dir=C:PROGRA~1SAPMDM~1.5IMPORT~2LangStrings
Log Dir=Logs
SLD Registration=False
 
[SP04_BUSINESS_PARTNERWDFD00143366AMSQL_21_13_4_3]
Login=Admin
Password=
Chunk Size=50000
No. Of Chunks Proccessed In Parallel=5

Using the Verbose parameter you can define which errors, issues, messages and so on should be written into the MDIS log. You can find the logs directly in the port's log folder and in the log folder of your MDIS installation directory. If MDIS is not working or the import fails, these files contain some helpful information.

Kind regards

Michael

[Former Member · Accepted solution]

Hi Michael,

Sorry I answer a little bit late. (Time shift).

I noticed 3 differences between your mdis.ini and mine :

1) I don't have : Version=

2) I do have : [Service] but not in you

3) AND the verbose part :

Verbose=0xFFFF

-- Verbose OFF: 0x0000

-- Verbose ON: 0xFFFF

-- FI Verbose: 0x0001

-- XML Verbose: 0x0002

-- MAP Verbose: 0x0004

-- THRD Verbose: 0x0008

-- PARSER Verbose: 0x0010

-- STRUCTX Verbose: 0x0020

-- VALUEX Verbose: 0x0040

-- IMPORTX Verbose: 0x0080

Regards,

Aklilu

[Former Member · Accepted solution]

run the following command (I assume you are on unix?)

ps -ef | grep mdis

If nothing shows up then the service is not running. You need to go into your MDM home directory, for example /opt/MDM and start the service. The service should be in the same directory as the .ini file. It does not start up by default when you start the MDM server. You can start it by running a command similar to:

./mdis

Depends on your box configuration though. Also, check the port folders for logs and exceptions. If the import server is rejecting your file, an entry should show up in the /Exceptions folder.

[Former Member · Accepted solution]

Hi Harrison,

Can you please tell me what do you mean by saying

"The service should be in the same directory as the .ini file."

Because the mdis.ini is located in MDM Import Server Directory and

the importbatch.ini in MDM Batch Import Sever Directory.

Kind regards,

Aklilu

[Former Member · Accepted solution]

What I meant is that the service, being the actual program, should be in the same directory as the .ini file. Meaning if you navigate to the same directory as your .ini file, you should be able to run the command:

./mdiis

[michael_theis · Accepted solution]

Hi Aklilu,

my MDIS.ini is a bit older one, so this may explain the different structure. The "Verbose" command configures the logging of the Import Server.

Verbose=0xFFFF <-- this means that logging is fully enabled

Verbose=0x0010 <-- this would log parser errors only

Since you may have only one statement in your MDIS.ini, the others are just comments with explanations what will be logged (thats why the lines start with --).

Kind regards

Michael

[Former Member · Accepted solution]

I would like to say thank you for everyone, it was very helpful.

Kind regards,

Aklilu

[markus_breiter · Accepted solution]

Is your mdis now running succesfully?

Did the check in services work? Even if the service is running it happens that specific ports are´suddenly not polled and for the user it looks like the Import Server is not working again.

In most of this cases the last "succesfull" import caused an exception. this exception is stored in log files in the port/exception directory. The Import Server is then no longer acting on this port until the erroneous input file was fixed by the user. To do this best use the Import Manager with port access - you will be provided the erroneous ports on the selection screen.

Regards

Markus

[Former Member · Accepted solution]

Hi Markus,

First thank you for your explanation and sorry to answer late. At this moment we are busy with other project but in the coming weeks I will check it again.

Kind regards,

Aklilu

[Former Member · Accepted solution]

Hi ,

We are facing a similar issue, the port has been created in the console & set to automatic processing. The MDIS service is started and running, as the repository, the xml files are placed in the 'Ready' folder by XI. However, data does not get loaded to the repository.The MDIS.ini file is given below, the main difference from the files discussed here is that this one does not have the server path for logs .

[GLOBAL]

Version=5540

Server=eimreymmd0

Interval=30

Automap Unmapped Value=True

Unmapped Value Handling=Add

Always Use Unmapped Value Handling=False

VXR_MAX=25000

Verbose=0x00F8

-- Verbose OFF: 0x0000

-- Verbose ON: 0xFFFF

-- FI Verbose: 0x0001

-- XML Verbose: 0x0002

-- MAP Verbose: 0x0004

-- THRD Verbose: 0x0008

-- PARSER Verbose: 0x0010

-- STRUCTX Verbose: 0x0020

-- VALUEX Verbose: 0x0040

-- IMPORTX Verbose: 0x0080

-- CHUNK Verbose: 0x0100

-- VxR Verbose: 0x0200

[Test_uploadEIMREYMMD0MSQL_11_10_4_3]

Login=Admin

Password=

Chunk Size=50000

No. Of Chunks Proccessed In Parallel=5

[Test_R3CustomerEIMREYMMD0MSQL_15_10_4_3]

Login=Admin

Password=

Chunk Size=50000

No. Of Chunks Proccessed In Parallel=5

Currently the data manager too gives an error - 'Image server logon error x83000006 ' if we try to access this repository

Thanks in advance for your help ,

Regards,

Anita

[Former Member]

Hi Akilu,

Did u start the MDM Import Server? Just go to services and make sure the service by name <b>MDM Import Server 5.5</b> is started. If it is not started, do start the service.

Check the logs in your MDM console. Go to Repository-> Admin -> reports. There should be a report of type <b>import</b> if the import process has triggered. If it is not there, the import process has never triggered. If it is there, check the report and post the log here.

Regards

Suman

[Former Member]

Hi Aklilu,

Does the user Admin exist in all your repositories?

If so, is the password always empty?

Regards,

Richard

[Former Member]

Hi Richard,

Thanks for your quick response. The user Admin exist without pasword, I use it to do every manual operations.

Regards,

Aklilu

[Former Member]

Hello again,

We even tried to put directly the xml file in the Folder Ready but the problem persist.

Kind regards,

Aklilu

[Former Member]

The file has to be in the Ready folder for the Import Server to process it, otherwise it won't work.

Richard

[Former Member]

Hi,

Please check your log files and let us know.

Regards,

Rajani