Skip to Content

Use of JAVA APIs

Just wondering.

MDM Database UI in itself is quite nice, with all the User friendly navigation/help/tabs etc etc available to create/modify/delete stuff from different tables.

Then why do we opt to redo the stuff using java APIs?

Add a comment
10|10000 characters needed characters exceeded

Related questions

3 Answers

  • author's profile photo Former Member
    Former Member
    Posted on May 27, 2008 at 02:16 PM

    Hi Nitin,

    A Java Specialist can perform almost all the MDM related Functionalities using MDM Java API with out learning MDM basic data types.

    The MDM Java API enables Java applications to connect to an MDM Server and perform most of the functions available in the MDM Console and MDM Data Manager. For example: adding, updating, deleting, searching and so on.

    The version of the MDM Java API must exactly match the version of the MDM server.

    for more information follow the link

    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/b02f4f88-7bbb-2a10-67ad-d435b9f0c643

    Reward if helpful.

    Regards,

    Vinay Yadav

    Edited by: Vinay Yadav on May 27, 2008 4:17 PM

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on May 27, 2008 at 02:37 PM

    Hi Nitin,

    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

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on May 27, 2008 at 03:16 PM

    One of the biggest reasons I have seen for users opting to go with a view in the Portal (either by using the Java API or by using the standard delivered iViews) is because for security purposes some businesses want to separate the fields which are viewed by certain roles. In the MDM Data Manager GUI client all roles have access to view all fields in the repository. You can put restrictions around the fields they can edit, but not around what they can see. For this reason, you can build iViews that have a different set of fields viewable for different security roles.

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.