Hi,
Here is the breif discription about MDM ABAP API.
_Introduction_
The MDM ABAP API (MDM4A) provides an interface for accessing SAP MDM 5.5 using ABAP. The interface is easy to configure and convenient to use. The MDM4A is delivered on SAP Web AS 6.40 and 7.00.Using MDM4A functionalities operations on records (create retrieve, update, delete, query, etc) and metadata (tables, fields etc) and administrative functions (such as repository) are delivered. By using MDM4A ABAP developers do not have to learn the SAP NetWeaver MDM specific data types.
Customization settings for MDM ABAP API
u2022Integration
The API is automatically registered in the SLD when the repository and connection information is configured in a system. The MD ABAP API customizing is done through a transaction MDMAPIC, this transaction consists of following elements
1.MDM DBMS Hosts
Stores the information regarding the database server connection.
Repositories may reside on a DBMS that is a different physical system than the MDM server itself
The Drop Down Box for DB Type will show all support DBMS types.
The name in the MDM DBMS field is arbitrary and only know to ABAP
2.MDM Server Connections
Stores the information regarding the database server connection.
Define the TCP/IP communication settings for connection to the MDM Server
Enter the Server Hostname and the Port for communication
Typically the MDM server runs on Port 20005
The name in the MDM Connection field is arbitrary and only know to ABAP
3 ABAP Implementation for MDM version support
Stores the information regarding the used provider implementation.
Different releases of SAP NetWeaver MDM may require technical differences in the Low Level Provider Class
This configuration will allow you to assign a provider class to a set of repository configuration settings
4.MDM Repositories
Stores the name of the target Repository, and a logical object name that refers to the information regarding MDM server, DBM etc.
We tie all our configurations together by specifying for a repository: what server, DBMS, and Provider it should use
The Object name is arbitrary and only know to ABAP u2013although it is used as the key to read all the configuration
The MDM Repository must be the real repository name as it is displayed from the MDM Console.
u2022Trusted System Connection
The SAP NetWeaver MDM Server(s) must trust their AS-ABAP counterparts.
Trusting is configured via two files on the SAP NetWeaver MDM server u2013allow.ip and deny.ip.
These files contain the IP addresses of the AS-ABAP systems that you want to control access from.
Configuration at Server Side
To establish a trusted relationship between R\3 and MDM we need to do some configuration. This configuration is done so that MDM server should know which client is trusted for connection and communication.
This is necessary to create a text file u201Callow.ipu201D which contains the IP addresses of Systems that want to connect to MDM Server. This file should be placed in the same directory where mds.ini file exists. It is also possible to use a wild card for the entire subnet .For example 10.58.0.* this indicates that any address with in the network 10.58.0 is considered to be trusted.
deny.ip.
In order to allow an entire subnet but specify some exceptions it is necessary to define these IP address in the deny.ip file. Put this file in the same directory where the mds.ini file exists.
User Authentication
Because there is a trusted relationship, no passwords must be passed through MDM4A The AS-ABAP user identity (SY-UNAME) will automatically be passed through the MDM4A interface.
A repository user with the same ID must exist on the SAP NetWeaver MDM server side for a role to be assigned to the request.
You can Dowbnload documents related to MDM ABAP API from here
https://websmp210.sap-ag.de/~sapidb/011000358700004121872006E --> Operations
Hope it will help you,
Regards,
Vinay Yadav
Edited by: Vinay Yadav on May 26, 2008 11:07 AM
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.