usage of java API ,

[Former Member]

hi

i am new to sap mdm. i have a doubt . as i know that data manager we use to make some changes to repository , removing duplication etc. then why again we need to design interfaces to the mdm server using java api .

what are the specidic advantages we get , which we dont get in data manager .. please clarify

with regards

sushma

[nitin_mahajan2]

Well i am working on some similar stuff and hasnt been long i started working to my understanding, following are the advantages of using Java APIs.

- Controlled access,

Though MDM GUI is good enough for anyone, we can provide all the functionalities on Portal itself. What MDM Doesnt provide is controlled user access. as in, if we want to limit the access depending on the roles. we can do that through PORTAL(using java apis).

Even the standard functionalities are not enough.

- Look and feel, the MDM GUI is quite boring:-)

- Cannot be exposed to outside world

We cannot let anyone see the content of MDM by giving them access to MDM server. So need a front end.

- Finally we use Java APIs because we love to work on Java APIs. Its fun...:-)

Cheers and enjoy your custom application development.

Regards,

Nitin Mahajan

[Former Member]

thank u ,

harrison , jitesh and and nitesh ,

i rewarded points .

i got the complete idea now on java api

thanks

sushma

[Former Member]

Hi Sushma,

If your query is solved please mark the thread as Answered so that others can also be helpful and reward accordingly.

Thanks

Jitesh Talreja

[Former Member]

Hi Sushma,

MDM Java API helps to bring the MDM Client's functionality on to the Portal and the main advantage is you dont need to install MDM Clients i.e. Data Manager on every users machine.

Also if you need any customization like Dynamic messaging in the notify step of workflow etc then to implement this you have to use MDM Java API.

Regards,

Jitesh Talreja

[Former Member]

The Java API is not typically used for "interfaces" in the sense of transferring data from one system to another, but it is used when you want to build a custom "user-interface", or develop some customizations that can't be done in the data manager. A lot of clients prefer to use iViews for data maintenance because you can't configure which fields are viewed by particular users. However, a lot of clients also have customizations that they would like to implement around the standard functionality of the SAP delivered iView content for MDM. In this scenario you could build a custom iView with webdynpro and use the Java API to communicate with MDM.