MANUAL SYNDICATION

How can I do manual syndication using with MDM PI Adapter? I open a map, but it prompts me where to save the XML file. For FTP you need to point the XML to the ready but for an MDM PI Adapter, what would I be needing to direct the XML file for the PI to pick it?
Is there a way where I can save the XML Files in my local drive and PI to pick the files from mine?
Many thanks!

Hi,
Is there a way to clear mapping and leave the required map for syndication?
See, if your requirement is to change the existing map and make it work as per the requirement to do manual syndication using Port. You can go ahead but when you open map using File>New>Type=Port, Remote System= required Remote System and Port= Defined in MDM PI Adapter of PI. Here yuo can edit this map but make sure after editing it save it as SAVE AS option (by giving some new map name say XYZ ) so that your existing map remain with you for future reference. Now you need to set this map XYZ into your Outbound Port for this remote system using MDM Console. So afterwards if you go for manual syndication your syndication will occur as per your required map.
Regards,
Mandeep Saini

Similar Messages

Manual Syndication - User ID

Hi Experts,
From one of the repository; the data is syndicated from MDM to ECC around 20,000 records on a particular date. On that particular date only few records got updated i.e. around 20. When we checked the Logs, Connections & Report we could not find the User ID who has syndicated around 20,000 Records manually.
Apart from these can we check which user ID has logged in & Syndicated in Mass for tracking purpose?
Thanks & Regards,
UG

Hi UG ,
I would suggest you to do 2 changes in the your system .
1) Add 4 new fields Created user, Updated user, Created Time , Updated time in your repository.
2) On the Syndication Map check the "Suppress Unchanged record" to true.
What this does is firstly you can track the created and updated user and time stamps on the Data Manager.
Secondly , The user is forced to make a change on the record (Which will make sure his ID is tracked) if the "Suppress Unchanged record" is set to true.
PS : Do make sure no authorization is given to change the syndication map , else there is no point.
Regards,
Vag Vignesh Shenoy

Automatic syndication not working in SP06

Does anyone have problems with automatic syndication in SP06 (version 5.5.62.58)? I upgraded our development system to SP06 few days ago. The syndication server didn't syndicate any changes. I also noticed that the next syndication time didn't get updated in the console. However, manual syndication with syndicator still works.
Am I missing anything? Thanks!

RDNPrasad, the exception folder is empty. I noticed that when I restarted the syndication server, certain ports syndicated and some of those ports did not generate any XML files even though the log file indicated the syndication was completed. Also the export log file didn't get updated at all after that as if the syndication service was crashed.
Ankit, what can you suggest to diagnose my problem? What is the best way to verify if the syndication service is running. I checked the service status using services.msc and it has "Started" status. But the log file never gets updated after initial startup. In SP04, I know the service.msc status is not accurate. Not sure if they fix it in SP06.
If this is indeed a product bug, which version should I use? We are using SP04. Automatic syndication works without major problems except we have to manually restart the syndicate service once a while. But I really like the syndication performance improvement in SP06.
Thanks!

MDM Syndication automatic error notification

I am currently helping to design workflows for my client and one of their requirements is that they have some sort of notification workflow when a syndication fails. So far, it is my understanding that there is no method to track syndication errors other than the syndication just won't go through. Is this accurate? Is there a way to perform this workflow. I am working with MDM 7.1 and we are using a PI adapter, however I am not sure of the version at this time.
Thanks

Hi Steven,
I am currently helping to design workflows for my client and one of their requirements is that they have some sort of notification workflow when a syndication fails. So far, it is my understanding that there is no method to track syndication errors other than the syndication just won't go through. Is this accurate? Is there a way to perform this workflow. I am working with MDM 7.1 and we are using a PI adapter, however I am not sure of the version at this time
Yes, you are correct. There is no robust mechanism to find out any Syndication errors. Foe ex, if its an automatic syndication, and there is some problems with the MDSS, the syndication wont happen, however there will be no error. Hence its difficult for setting any Email Notification for the same.
The main thing is if we are using Automatic Syndication, the export file is sent to the Ready Outbound folder. But it is not passed on to the Archives automatically as it does in Import. And again in Manual syndication anyways it not possible to trigger any notification on failure.Hence, as far as I know there is not much help on this.
Thanks and Regards
Nitin Jain

Workflow - syndication problem

Dear All
We have the workflow with syndication step. All has been working fine, but sudenly today syndication is not working. There is only an information in log: "The system cannot locate the resource specified. Error processing resource "
What does it mean ?
Manual syndication works fine, but it is not working with workflow.
Thank you for help.
BR
Rafal

Hello,
was the server restarted recently.
What entries do we have in the workflow log, also are check if the port associated with the syndication server is open for communication
Regards,
Abhishek
Edited by: Abhishek Biwal on Dec 14, 2011 5:10 PM

On demand syndication

Hi All,
I'm trying to run a on-demand-syndication. I made a workflow with syndication step, I created a port and also a syndication map.
Syndication via the MDSS works fine
Manual syndication works fine
Syndication via workflow, the workflow runs, the history inj the workflow says the steps were oke however no file is in the ready folder.
What do I have to do?
thanks in advance

Syndicating in a workflow, syndication on demand, extracts all records that are within the original search of the mapping.
I prepared a syndication with a search on country and in the map properties " supress unchanged records" and ports.
Using the Syndication server or the manual syndication it works as expected, only the changed records out of the search.
Using the workflow with the defined port the output is different:
All records for the port for this map are syndicated. Not just the records that are in the specific workflow and also not only those that have been changed after the last syndication as was set in the map.

Syndication file transfer

Hi ,
I do not have much knowledge of how XI works.So just want to know if i want to transfer data from MDM to remote system using syndiactor then how XI will receive the file from outbound port of MDM or how XI get the notification that there is some file in outbound port.
Thanks,
Sudhanshu

Mandeep,
I beg to differ to below points
>>For Pt.2 Using Manual syndication: 1st thing is that you need to place file to ready outbound folder somehow which does not happen directly if we use syndicator
We can very well trigger MDSS via manual syndication process, we just need to have configured Outbound Port for this syndication map.
Here is the excerpt from help.sap document.
The syndication event can also be triggered by manual port syndication as follows
                                                  i.       Open the MDMSyndicator.
                                                ii.       Go to File menu u2192 Newu2026
                                               iii.       Set Type=port
                                               iv.       Choose relevant port
                                                 v.       Execute syndication
If the port is not selected, manual syndication is not possible with the MDM PI Adapter
http://help.sap.com/saphelp_nwmdm71/helpdata/en/48/cee75a6dc1581ce10000000a42189c/frameset.htm
At my client side, we have configured several manual Ports (on Demand basis), we simply go to Syndicator and trigger the records manually and it goes to ready folder, from where its picked by MDM Adapter.
>>2nd thing how do you throw the event when Syndication completes through syndicator
Even this trigger is not required, as long as there is a file in Ready folder, MDM adapter will pick it up (pretty much similar to File Adapter).
A simple test could be to copy the file manually in Ready folder (without MDSS) and see if MDM adapter picks it up. works fine for us.
Thanks
Aamir

Merge with MDM automation

Hi Folk,
Has anyone tried the merge functionality with either with syndicator batch or syndication server ?
It doesn't seem tobe working in our testing. Manual syndication, however seems tobe working. Let me know your experiences/work arounds for this.
We are on SP04.
Regards,
Vinay

Hi
I have also this problem with SP05 ;
the "merge-fucntion" create a memory problem
any idea ?
best regards

Syndicate Step in workflow

Hi All,
Is syndication server required for syndicate step in workflow?
I have doubt that syndicate step is for either manually syndicating or automatically syndicating.
Please clarify.
Thanks
Narendra

Hi,
Syndication to other system having two types.
Syndication manual & automatic syndication.
Using the manual syndication we should follow the steps and we can save that as a MAP.
we can use this map for further syndication.
During automatic syndication we have to mention the receiver port which will receive the records.
Regarding workflow , we can trigger the workflow manual as well as automatic.
Regards,
Vijay

MDM Adapter doubt

Hi
what are all the advantages of using MDM adpater in PI 7.1
1.Will MDM adapter accesses directly the repository (in console or data manager or syndicator)?
2.How MDM adapter can be compared with import manager or syndicator .
3. MDM adpater enables to load the data directly to any repository ?
4. how the integration of PI7.1 with MDM 7.1 takes place ?
am bit confused, can you pls explain ?
thanks
manian

Hi Manian,
Please go through this link; it will give you a good idea about the new features of MDM 7.1
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/d0d0b0e7-f144-2b10-17a2-982103c96ac0
Some key points on MDM-PI Adapter; this will definitely answer all your questions:
1. MDM 7.1 will offer new functionality to directly push/pull data into/from MDM using the MDM JAVA API.
2. The MDM PI Adapter will support SAP Netweaver PI 7.0 and 7.1
3. The MDM PI adapter is shipped as a separate file to be deployed on the PI adapter engine.
4. Message flow between PI and MDM can be monitored end to end (e.g. show if messages have been recieved and properly imported into MDM)
5. Error handling is improved because the Communication Channel in PI is pointing to one specific Repository Port.
6. Restarting of messages if a service is unavailable is possible.
7. Configuration/System landscape setup/Integration
       (a) MDM Adapter can be used instead of the File Adapter.
       (b) Configuration of FTP is no longer needed.
       (c) MDM Adapter is easy to implement and straight forward to monitor.
       (d) Higher reliability of data transfer.
8. Message Flow PI to MDM
       (a) Data sent from any connected system to PI is stored within PI's internal database.
       (b) XML message is forwarded to the defined communication channel (MDM PI Adapter).
       (c) MDM JCA Adapter itself invokes the MDM JAVA API sends the message to MDM using MDIS Port Functions.
       (d) Store the message in XMl format in XML format into the corresponding MDIS port folder so that MDIS can import the files independently.
       (e) "Finished import event" is thrown by MDIS and caught by the MDM JCA Adapter.
        (f) The import status is used to update the PI monitoring accordingly.
9. Message flow from MDM to PI
       (a) The Syndication event is triggered by MDSS as soon as the syndication is finished.
       (b) The data is available as XML file in the corresponding port folder.
       (c) The MDM JCA Adapter catches the syndication event and uses the MDSS Port functions to retrieve the data.
       (d) PI XMl message is created and sent to the PI AF for reciever determination and further message processing.
       (e) It is important to understand that only MDSS is able to throw the syndication event.
       (f) A manual syndication using the syndicator does not throw this event, meaning that the MDM 7.1 PI adapter is unable to pick the XMl message coming from manual syndication.
All these points should give you a very clear picture of all the abilities of MDM-PI Adapter.
Hope this will answer most of your questions.
Regards,
Varun

Configure Sap NetWeaver MDM with Sap Netweaver XI

SAP NetWeaver MDM communicates with SAP NetWeaver XI by writing an XML file into a directory on a file server.
Can someone gives me an idea about the path of this file server? How can I configure it?

Hi Stan,
In addition to that Harrison told you,if you want automatic syndication of records ,then you must have to use syndication server.In case of syndication server the path of output file is always fixed and you cannot configure it.Path will be as follows:-
<b>
SAP MDM Root Directory\Server\Distributions\<server name> \ <Database instance name>\<Repository name>\Outbound\<client System code>\<Output Port Code> \Ready\</b>
If u want scheduled syndication of records(i.e. in batch mode) ,then u can use syndicator batch.And for manual syndication ,use syndicator .Both of these components will syndicate file where ever u want/specify on the file system.
For more details about syndicator batch
<a href="http://help.sap.com/saphelp_mdmgds55/helpdata/en/a4/21c4a4f6a247b1940fc8bf1cf41f65/frameset.htm">Click here</a>
Hope it will help you.Let me know the results.
Thanks,
<b>Shiv Prashant Dixit</b>

Pass dynamic values to search-query in wlp-syndication-config for RSS

Hi All,
I want to pass dynamic values to the <search-query> element for the <syndication-feed> node in the wlp-syndication-config.xml file for implementing RSS feeds.
Here's a sample
<syndication-feed>
          <name>RSSFeed</name>
          <search-query>cm_objectClassInstance=='Node' && date == 'x'_</search-query>
          <search-type>pubmeta</search-type>
     </syndication-feed>
I tried passing the parameter in the url but the feed doesn't read it. The only option i have is to manually put the value to get the content from the repository, which sucks...because the values can change any time. is there any way that I can avoid it
Any help on this would be appreciated.
Thanks,
K

James:
Passing filters to an IR within the URL is described here
http://download.oracle.com/docs/cd/E14373_01/appdev.32/e11838/app_comp.htm#sthref989
Varad

QUALIFIED RANGE MAPPING/PI-MDM CONFIGURATION FOR AUTOMATIC SYNDICATION

Hi Experts,
I am setting up automatic import and syndication using an xml schema to a qualified lookup, will this be able to work? I made tuple to work but not with a qualified lookup even the mappings are all corrent, the import doesnt work.
We are using the MDM-PI Adapter instead of the File Adapter to automatically syndicate, Is it possible to create multiple channel? As when we configure the message starts to branch to the other channel since they have existing mapping but different remote port. Other port was configured as Manual while the new one was automatically to syndicate? Is there a workaround to this?
Many thanks!

Hi Elizabeth,
This is true that it uses only Numeric values while defining Qualified Range using Remote System of MDM Console.
But it doesn't allows to key the remote system details all alone for the internal number range as its using a qualified range.
I didn't get you exactly here, if you mean that you want to syndicate records on the basis of account number and want to generate customer number which is numeric then its possible. For this the Qualified field which is look-up to some sub-table, for this sub-table Key mapping Property should also be Yes.
Please refer step by step guide to make use of qualified range:
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/807ce1ba-94c0-2a10-a398-afdfd8135ebd?quicklink=index&overridelayout=true
Kindly let me know if you are looking for something else
Regards,
Mandeep Saini

Syndication event for new MDM PI Adapter in MDM 7.1

Hi,
We have setup the new MDM PI Adapter for MDM 7.1 and have created interface in PI using this new MDM PI adapter. All neccesary steps as mentioned in the installation guides are done.
Also all necessary remote systems/ports/syndication maps are created in MDM, and syndication is running fine on the MDM side (using the syndication server, so not manually!)! The syndication files are created in the Outbound/../Ready folder, so again, on MDM side everything looks OK.
However, when the syndication server has run, there's no syndication event triggered (or at least not captured by the MDM PI Adapter), hence PI is not picking up the files from the outbound folder. It looks like PI is not getting any syndication event, or at least is not catching the event, since monitoring on PI side does not show us any trigger.
Now I have the following questions:
1. Does anyone know how we can verify/monitor if MDM raises any syndication event (the export log in the console of MDM 7.1 does not say anything about an syndication event that is raised, only that the export itself was succesfull)?
2. Is there any additional setup to be done on MDM side in order to make sure that the syndication event is raised as soon as the syndication server is ready (or is the syndication server ALWAYS raising the event, independent of using the MDM PI adapter)?
If anyone else has any experience with the new MDM PI Adapter for MDM 7.1, please share us your valuable information. Thanks in advanve for your answers/advice.
p.s. We are using MDM 7.1 (build 7.1.01.72).
Regards,
Marcel

Hi
We are also currently experiencing a similair issue. Seems to occur when some sort of matching activity occurs on the MDM Server. What happens is that syndicated files remain in the 'Ready' folder on the Outbound Port. In the PI Netweaver Trace Log files we start seeing this error message:
Jul 13, 2009 4:34:41 PM com.sap.mdm.logging.MdmLogger warning
WARNING: NotificationDispatcher - Connection failure. Original exception: 'java.net.SocketException: Connection reset'.
If we restart the Connector and Adapter from the NetweaverJ2EE Application Admin screen, this files still remain in the READY Folder. However, if i syndicate another data record into that folder, the syndication for that file work as well as for the rest of the files that were sitting in the READY folder. Seems like the "failed" files seem to latch off the syndication event.
Doesn't seem like the stability and robustness is there?
Any feedback would be greatly appreciated.

Setup interval on Import and Syndication server in 7.1

Hello Experts:
I am upgrading MDM from 5.5 to 7.1; I am having issues with Import Server picking up files from Ready folder, and Syndication Server creating the files on Ready Folder.
1. I checked Console, and both ports, Inbound and Outbound, are setup as Automatic.
2. I restarted both servers
The files are still on the ready folder for Import Server, and Syndication is not creating the file.
1. Do you know what else can I check to make this process automatic?
2. Do you know where, in 7.1, can I check the interval? I used to check it on the mdis.ini file, but I cannot find it in 7.1.
Thank you for your help,
Claudia Hardeman

Hi claudia,
check the below points:
1) Manually you can import and symdicate those files through import manager and syndicate manager its works fine, then PI not picked those files from ready folder, check the communication channel of receiver and sender systems.
2) files having some special characters (like ", ' etc.) MDM is not supported to special characters.
3)check the MDM server running and repository loaded or not.
Regards,
Bhupal.

MANUAL SYNDICATION

Similar Messages

Maybe you are looking for