cancel
Showing results for 
Search instead for 
Did you mean: 

Syndication server issue

Former Member
0 Kudos

Hi All,

I am facing an issue with the syndication server. The syndication server is scanning only 2-3 ports out of a total of 30.

It is bypassing the rest of the ports.

When i am checking the syndication server logs, i am able to see few ports only.

Can you let me know what could be the reason for this unusual thing.

I have unloaded the repository and again loaded it. Restarted the syndication service as well as the syndication server

We are still in MDM5.5 SP04.

Please let me know what i need to do now.

BR

SK

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

This message was moderated.

Former Member
0 Kudos

Dear Ravi,

Thanks for the quick reply. We are supporting MDM5.5 SP04, so there is no update option. It is there for MDM7.1

BR

SK

former_member182007
Active Contributor
0 Kudos

Sushil -

Please confirm that your all ports has been set as Automatic, MDSS will not scan manual ports. Also see the time interval.

hth

thx

Deep

Former Member
0 Kudos

Hi Susil,

Can you resave your maps and close them,currupt maps will be skipped by MDIS.

I am assuming all ports are automatic.

Thanks,

Ravi

Former Member
0 Kudos

Hello Deep,

All the ports are automatic.

BR

SK

former_member182007
Active Contributor
0 Kudos

Sushil -

You need to revisit your maps and then start the services again.

thx

Deep

Former Member
0 Kudos

Hi Deep/Ravi,

I have saved the maps once again but it is not working.

BR

SK

former_member182007
Active Contributor
0 Kudos

Sushil -

make sure below points

Type : Outbound

Processing Type : Automatic

Map: Name of the syndication map to use with the port

When MDSS completes a syndication to a port, it places the syndication file in the portu2019s Ready folder. The Ready folder is part of the following fixed directory structure, located beneath the Master Data Serveru2019s distribution root directory

root/DBMSinstance_DBMStype/RepositoryName/Outbound/ RemoteSystem/PortName/Ready

here root need to set in mds.ini

This time again see the exact log and let us know.

thx

Deep

former_member182007
Active Contributor
0 Kudos

Sushil -

Let us know your findings.

thx

Deep

Former Member
0 Kudos

Dear Deep,

I do not think we need to maintain the path mentioned by you in the MDSS.ini file. Just to share that we are supporting

application running on MDM5.5 SP04 so in the MDSS.ini file you would have the user id as Admin and the password along with the repository name.

BR

SK

Former Member
0 Kudos

Hi Susil,

Did you verify the repository?

Thanks,

Ravi

Former Member
0 Kudos

Hi Ravi,

The repository is up and loaded. Since it is in production so cannot unload it. had it been the issue with the syndication server

then nothing would move from MDM and the issue is understandable. But syndication server only scanning few ports and

bypassing the rest is a strange thing to happen.

BR

SK

former_member182007
Active Contributor
0 Kudos

Sushil -

What is your syndication log stating ?

thx

Deepak

Former Member
0 Kudos

Hi Deepak,

Syndication server logs are getting generated but there are very few ports which are being scanned by the

syndication server.

Same configuration is with QA and it is running fine. Actually we have a .BAT file which is being used for the automatic

syndication job. I have recreated the job and restarted the MDM server and the syndication server services and made the auto

task delay in the MDSS.ini to 10 secs. But no respite till now.

BR

SK

Former Member
0 Kudos

Hi Susil,

Create a new port with same details as one of the already created but non scanned ports.

Assign a map and see if it is working.Compare the 2 ports and logs.

Let us know your findings.

Thanks,

Ravi

Former Member
0 Kudos

Hi Ravi,

I had deleted one port and recreate the same but that also did not worked.

BR

SK

Former Member
0 Kudos

Hi Susil,

Did you right click on repository and select Verify Repository option?

check if you have warnings and errors.If present take a backup of your repository and Repair.

Thanks,

Ravi

Former Member
0 Kudos

Hello Ravi,

Solved it. Thanks for your patience and replies.

Actually the problem was with a particular port. We deleted the port and recreated it and used a fresh map.

That solved the issue.

BR

SK

Former Member
0 Kudos

Thanks for update.

good work