XI Connecting to MDM Inquiry

Hi,
I just have a question regarding XI mapping development. Not sure if this is possible, but we're trying to look at an angle where XI will connect to an MDM Repostory in XI mapping.
Has anyone experienced such a scenario before? I'm thinking using User Defined Function here.
I would appreciate if you can give me some source codes too if there are any available.
Thanks!

Hi Angelo,
I never tried though but cant we go for lookup?
Refer these blogs:
http://www.sdn.sap.com/irj/scn/weblogs;jsessionid=%28J2EE3417400%29ID0036526650DB11206996391693652681End?blog=/pub/wlg/13342
http://www.sdn.sap.com/irj/scn/weblogs;jsessionid=%28J2EE3417400%29ID0036526650DB11206996391693652681End?blog=/pub/wlg/2278
http://www.sdn.sap.com/irj/scn/weblogs;jsessionid=%28J2EE3417400%29ID0036526650DB11206996391693652681End?blog=/pub/wlg/5326
Regards
Suraj

Similar Messages

Error while connecting to MDM server from Webdynpro

Hi ,
   I am trying to connect to MDM server (5.5 SP04 no patches) through a webdynpro application . The following is the piece of code that I am using as a test .
CatalogData CatalogData = new CatalogData();
    int resultLogin = 0;
    try {
          resultLogin = CatalogData.Login("USNOC01AQ05",2005,"Admin","Erico1234","English [US]");
    }catch(Exception e){
          wdContext.currentContextElement().setValueattr("Not Connected");
         //System.out.println("Error while establishing connection");
    if (resultLogin != RC.RC_OK){
          wdContext.currentContextElement().setValueattr("Not Connected");
         //System.out.println("Error logging to the SDM server");
         //System.exit(-1);
     wdContext.currentContextElement().setValueattr("Connected");
    //System.out.println("MDM server connected");
The import statements are as follows
import a2i.common.CatalogData;
import a2i.generated.RC;
I have put the following jar files in the java build path
MDM4J
mdm-admin
mdm-common
mdm-core
mdm-data
mdm-protocol
When I deploy my application I get the following error
java.lang.NoClassDefFoundError: a2i/common/CatalogData
It can't be determined from the exception chain, which class loader failed to load the above class. But at least the class loader of the current application does not contain a resource with name 'a2i/common/CatalogData'.
What do you guys think is the problem ?
Regards
DeepaK Singh

Hi ,
   I found a document which says that MDM4J is the legacy API and is considered deprecated .The MDM Java API is the new one .I have both of them in the java build path . I am not sure if this is that cause of the problem .
Now I had a look at the javadoc for the new API but I am not able to locate the class to obtain a connection to the MDM server from a custom application being built in Netweaver Developer Studio . Can someone help me out with the same ?What would be the code to obtain the connection to the MDM server with the new JAVA API ?
Regards
DeepaK Singh

Failed to connect to MDM via Java API

Hi,
I wrote a very simple application in which there is a view which
calls the component contoller. The Component Controller
connects to MDM Repository.
I think I am wrong with the calling of Component from Web Dynpro view.
As, the code resulting in no error or success.
Please suggets something.
public void getRepositoryConnection( java.lang.String hostName, java.lang.String repositoryName, java.lang.String userId, java.lang.String passWord )
    //@@begin getRepositoryConnection()
//          create connection pool to a MDM server
         String serverName = "kolapon.HCLT.CORP.HCL.IN";
         ConnectionPool connections = null;
         try{
              connections=ConnectionPoolFactory.getInstance(serverName);
         catch(ConnectionException e)
         { e.printStackTrace();
              return;
//          specify the repository to use
                           // alternatively, a repository identifier can be obtain from the GetMountedRepositoryListCommand
                       repositoryName = "KaushikRepo";
         String dbmsName ="MDM";
          RepositoryIdentifier reposId = new RepositoryIdentifier(repositoryName, dbmsName, DBMSType.ORACLE);
//          get list of available regions for the repository
          GetRepositoryRegionListCommand regionListCommand = new GetRepositoryRegionListCommand(connections);
          regionListCommand.setRepositoryIdentifier(reposId);
          try{
               regionListCommand.execute();
          catch(CommandException e)
               e.printStackTrace();
               return;
     RegionProperties[] regions = regionListCommand.getRegions();
//      create a user session
      CreateUserSessionCommand sessionCommand = new CreateUserSessionCommand(connections);
      sessionCommand.setRepositoryIdentifier(reposId);
      sessionCommand.setDataRegion(regions[0]); // use the first region
     try {
                               sessionCommand.execute();
                          } catch (CommandException e) {
                               e.printStackTrace();
                               return;
     String sessionId = sessionCommand.getUserSession();
//      authenticate the user session
      String userName ="kaushikb";
      String userPassword ="taton";
      AuthenticateUserSessionCommand authCommand =
                                new AuthenticateUserSessionCommand(connections);
      if(authCommand!=null)
           wdComponentAPI.getMessageManager().reportSuccess("Success");
      else{
           wdComponentAPI.getMessageManager().reportWarning("Failure");
      authCommand.setSession(sessionId);
      authCommand.setUserName(userName);
      authCommand.setUserPassword(userPassword);
      try {
                                authCommand.execute();
                           } catch (CommandException e) {
                                e.printStackTrace();
                                return;
                           // the main table, hard-coded
       try{
          GetRepositorySchemaCommand getRepositorySchemaCommand = new GetRepositorySchemaCommand(connections);
          getRepositorySchemaCommand.setSession(sessionId);
          getRepositorySchemaCommand.execute();
          RepositorySchema repositorySchema;
          repositorySchema = getRepositorySchemaCommand.getRepositorySchema();
          TableId tableId= repositorySchema.getTable("MDM_BUSINESS_PARTNERS").getId();
     RecordFactory.createEmptyRecord(tableId);
     //RecordFactory.createEmptyRecord(mainTableId);
     if(tableId!=null)
          wdComponentAPI.getMessageManager().reportSuccess("It is success");
     else{
     wdComponentAPI.getMessageManager().reportWarning("Failure");
catch(Exception ce)
ce.printStackTrace();
// catch(SessionException se)
//se.printStackTrace();
    //@@end
Regards
Kaushik Banerjee

Hi Jitesh,
getRepositoryConnection() is my method which does the connection.
Now, there are methods as :
getFields
public FieldId[] getFields()Get array of field IDs for all populated records.
Returns:
array of field IDs. Empty array is returned if any field was populated
getFieldValue
public MdmValue getFieldValue(FieldId fieldId)
                       throws java.lang.IllegalArgumentExceptionGet value of the specified field.
Parameters:
fieldId - field ID
Returns:
field value
Throws:
java.lang.IllegalArgumentException - if field with specified ID does not exist or was not populated
I want to use all these methods.
So, I need to declare these methods in the Controller Class and these methods will call themselves so, that I can achieve the real purpose of creating records, getting values from the field and getting field Ids etc.
Regards
Kaushik Banerjee
Edited by: Kaushik Banerjee on Apr 28, 2009 7:09 AM

MDM 7.1 Portal Connectivity to MDM server

Hi all
I was running the MDM 7.1 ramp up version so far with full connectivity from the portal to MDM. I had configured both the standard business partner and a custom repository using the Portal Business Content . Now that I have migrated to the just released MDM 7.1 (GA ) , I am encountering the following error at the portal level . I am using the standard "Using Mapping" to connect to the MDM server from the portal and not the newly introduced "Trusted Connection" . Any body has any clue as to whats going wrong ..
com.sap.mdm.commands.CommandException: com.sap.mdm.internal.protocol.manual.ServerException: The connection is not trusted
at com.sap.mdm.commands.TrustedUserSessionCommand.execute(TrustedUserSessionCommand.java:61)
at com.sap.mdm.blobs.ObjectCache.initialize(ObjectCache.java:521)... [see details]
DETAILED MESSAGE
com.sap.mdm.commands.CommandException: com.sap.mdm.internal.protocol.manual.ServerException: The connection is not trusted
at com.sap.mdm.commands.TrustedUserSessionCommand.execute(TrustedUserSessionCommand.java:61)
at com.sap.mdm.blobs.ObjectCache.initialize(ObjectCache.java:521)
at com.sap.mdm.admin.utils.MdmConnectionProvider.createBlobObjectCache(MdmConnectionProvider.java:308)
at com.sap.pct.mdm.appl.masteriviews.MdmeBaseDynPage.initContexts(MdmeBaseDynPage.java:364)
at com.sap.pct.mdm.appl.masteriviews.MdmeBaseDynPage.doProcessBeforeOutput(MdmeBaseDynPage.java:154)
at com.sapportals.htmlb.page.PageProcessor.handleRequest(PageProcessor.java:127)
at com.sapportals.portal.htmlb.page.PageProcessorComponent.doContent(PageProcessorComponent.java:134)
at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215)
at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:645)
at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:753)
at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)
at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:524)
at java.security.AccessController.doPrivileged(Native Method)
at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:407)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
Caused by: com.sap.mdm.internal.protocol.manual.ServerException: The connection is not trusted
at com.sap.mdm.internal.protocol.manual.AbstractProtocolCommand.execute(AbstractProtocolCommand.java:126)
at com.sap.mdm.commands.TrustedUserSessionCommand.execute(TrustedUserSessionCommand.java:56)
... 38 more
Thanks
Ray

Hi Ray,
This is a trusted connection problem. For this you need to create allow.ip and deny.ip files in your server. In allow.ip you need to give those ip address through which you would be connecting to MDM server executable file(mds.exe) like in your case your portals ip address. And in deny.ip you need to specify those ip which you feel shouldnt connect to MDM server. After assigning this ip remember to restart your mds.
Also the users through which you are trying to connect to an MDM repository, their usernames must exist on the MDM repositoryu2019s Users table.
For more details please see page 299 from MDM 7.1 Console refernece guide
I hope I am able to solve your problem
Thans & Regards
Dilmit Chadha

Problem while creating JCA connection to MDM server

Hi All,
I have restarted my mdm connector(com.sap.mdm.tech.connector) along with the applications related to Enrichment Controller. All applications restarted successfully. After that I tried accessing the URL
http://MDMSERVER:50000/MDM_EnrichmentController/WorkflowPolling?process=Monitor
but I am getting following exception in this page
Polling Repository
    name=Vijaybabu_Repo_on_MDMSERVER, status=No repository connection, error description=com.sap.mdm.net.ConnectionException: Problem while creating JCA connection to MDM server MDMSERVER
        Enrichment Request Threads
Could somebody help me pointing if something I have missed..
Thanks and Regards,
Manoj

hi Swarna,
I have verified the repository and found 0 fatal errors, 0 non-fatal erros and 0 warnings. I also checked the MDM Factory and Connector service is running fine.
The detailed exception is
Sep 2, 2008 12:49:40 PM com.sap.mdm.logging.MdmLogger error
SEVERE: Problem while creating JCA connection to MDM server 'KOLAPON'
com.sap.mdm.net.ConnectionException: Can not resolve JCA connection
     at com.sap.mdm.internal.session.JcaConnectionUtil.getJcaConnection(JcaConnectionUtil.java:119)
     at com.sap.mdm.internal.session.JcaConnectionUtil.getJcaConnectionAccessor(JcaConnectionUtil.java:62)
     at com.sap.mdm.internal.session.JcaConnectionAccessor.reserveConnection(JcaConnectionAccessor.java:70)
     at com.sap.mdm.internal.session.JcaConnectionAccessor.reserveConnection(JcaConnectionAccessor.java:59)
     at com.sap.mdm.repository.commands.GetRepositoryStatusCommand.execute(GetRepositoryStatusCommand.java:67)
     at com.sap.mdm.enrichment.common.ECAdminUtils.getRepositoryStatus(ECAdminUtils.java:125)
     at com.sap.mdm.enrichment.common.EnrichmentUtils.validateRepostiryConfiguration(EnrichmentUtils.java:889)
     at com.sap.mdm.enrichment.common.EnrichmentUtils.getCatalogManager(EnrichmentUtils.java:144)
     at com.sap.mdm.enrichment.workflowpolling.PollingThread.getCatalogManager(PollingThread.java:166)
     at com.sap.mdm.enrichment.workflowpolling.PollingThread.run(PollingThread.java:102)
Caused by: com.sapportals.connector.connection.ConnectionFailedException: Connection Failed: "ConnectionManager" is closed. Possible reasons: 1) connector "MDM Factory" is stopped or not started, 2) Connector service is stopped or has not been started.
     at com.sap.mdm.connector.connection.MdmConnectionFactory.getConnectionEx(MdmConnectionFactory.java:223)
     at com.sap.mdm.internal.session.JcaConnectionUtil.getJcaConnection(JcaConnectionUtil.java:108)
     ... 9 more
Caused by: com.sap.engine.services.connector.exceptions.BaseResourceException: "ConnectionManager" is closed. Possible reasons: 1) connector "MDM Factory" is stopped or not started, 2) Connector service is stopped or has not been started.
     at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateConnection(ConnectionManagerImpl.java:122)
     at com.sap.mdm.connector.connection.MdmConnectionFactory.getConnectionEx(MdmConnectionFactory.java:213)
     ... 10 more
Regards,
Manoj
Edited by: Manoj Kumar Nanda on Sep 2, 2008 9:21 AM

Error connecting to MDM server

Hi all,
I am getting the check user mapping error while connecting to MDM server. The MDM Server and EP Server are on different systems. And when i try using the group "Everyone". The connection test was successfull but when i login with that user id/pwd no data is displayed.
I am using MDM 5.5 SP03 and EP SP14.
Regards,
Jaydeep

Hi Simona,
I tired to import schema, but its not over written(user names & roles) by the merging it with the other Repsoitory schema.
I tried creating duplicate, but could not see the duplicate repository in the Console - server - repository, but could see the repository at the database level(Oracle DBMS).
Anyways SAP has adviced to Connect to Oracle DBMS directly and remove the trailing space in
USERNAME column of A2I_CM_USERS table for the user mentioned.
But, its not possible to reduce the length of the username field.
Could you please guide me, if u have any idea??
Cheers
Srihari Reddy

Error connecting to MDM over Portal

Hi!
I have some difficulities with connecting to MDM repository over Portal. I have a working Java project, which connects to the repositroy and executes a search without error.
I developed a WD type DC where I want to use the previous Java program. So I put the java files into a package inside the WD project. The MDM jars have been deployed and added as "Used DC" to my WD DC. On the Portal there is an MDM system created. But when I test my first component, which should execute the search I got the following error message:
"java.lang.IllegalStateException: Login method has not been successfully called.
 at a2i.common.CatalogData.Preprocess(Unknown Source)
 at a2i.common.CatalogData.GetResultSet(Unknown Source)
 at com.sap.excercise.util.jani.MDM_data.Get(MDM_data.java:50)
 at com.sap.excercise.util.jani.Start.Check(Start.java:47)
 at com.sap.excercise.gp.wd.reqbupa.CReqBuPa.search(CReqBuPa.java:284)"
These error appear at the connection part of the code. The connection is done by the following code:
import a2i.common.CatalogData;
import a2i.generated.RC;
public class Connect {
 // file with connection specific information
 static private CatalogData catalog = null;
// // variables to be populated from a file
 static private String hostname = "localhost";
 static private int port = 2345;
 static private String username = "Admin";
 static private String password = "Admin";
 static private String language = "English [US]";
 static private int mincon;
 static private int maxcon;
 static private int timeout;
 static private String log;
 static private int logging;
 // used for single instance catalog object
 static private Object singletonLock = new Object();
 public CatalogData instance() {
 // if there is no catalog instance
 if (catalog == null) {
 // get a lock to create the singleton instances
 synchronized (singletonLock) {
 // check again
 if (catalog == null) {
 // get parameters of connection from property file
// loadProperties();
 // create catalogdata instance
 catalog = new CatalogData();
 // try logging in
 int resultLogin =
 catalog.Login(
 hostname,
 port,
 username,
 password,
 language
 if (resultLogin != RC.RC_OK) {
 System.out.println(
 "Error logging into MDM server: "
 + RC.GetTextForError(resultLogin)
 + " ("
 + resultLogin
 + ")");
 return null;
 System.out.println("nLogged into MDM server.");
 // return catalog instance
 return catalog;
 public void logout() {
 try {
 catalog.Logout();
 }catch (a2i.core.StringException e){ e.A2iPrintError(); }
 finally
 System.out.println("Finished.");
Have you any ideas this problem can be caused by?
Regards,
Peter

Hi Namrata,
I found the following description of com.sap.tech.mdm.tech.mdm4j:
Name: com.sap.mdm.tech.mdm4j.sda/
keyname: com.sap.mdm.tech.mdm4j
keyvendor: sap.com
keylocation: SAP AG
keycounter: 5.50.20061217101225.0000
Implementation-Title: com.sap.mdm.tech.mdm4j
Implementation-Vendor-Id: sap.com
Implementation-Version: 5.50.20061217101225.0000
Specification-Title: SAP MDM Java API
Specification-Vendor: SAP AG
Specification-Version: 5.5.4.3
Implementation-Vendor: SAP
componentelement: <componentelement name="com.sap.mdm.tech.mdm4j" vendor="sap.com" comp
onenttype="DC" subsystem="NO_SUBSYS" location="SAP AG" counter="5.50.2
0061217101225.0000" deltaversion="F" updateversion="LB-20061227155700"
componentprovider="SAP AG"/>

Exactly the project I am developing is a Web Dynpro type Development Component, so it is not a simple Web Dynpro Application. Thats why I have created another DC which includes all the MDM jars (Version 5.5.35.16) and added to my WD DC as "Used DC..".
Thanks,
Peter

User not found error when connecting to MDM server using NWDS

Hi,
I am getting the error as " User not found " when i am connecting to MDM server from the code written in NWDS.
If i make that user as admin in usermapping in MDM den it works fine bt if that user is not admin den get the error as user not found.
Please help.

Hi,
Thanks for the reply.
I have added the user in user mapping in MDM server. but i have to give the authority as admin.
other users who are added in usermapping bt not assigned as admin are getting the error.

Connecting SAP MDM to UG (UniGraphics)

Hello all,
I wonder if anyone there connected SAP MDM to UG (or other CAD-CAM systems), without creating the whole master data in those systems. I have a customer that wants to use the search and hierarchy capabilities of MDM (by many users) - when the user find the right material - he should "drag and drop" it (the material master number) into the CAD-CAm (e.g., UG) system.
The UG will look for the drawing of that material and add it into the drawing,
The purpose is to create active drawing that not only has the related parts but also the material master data.
What do you think ? Is that possible ?
Thanks,
Isaac

Hi Michael,
first of all CRM does not make use of IDocs. Instead it has its own middleware layer using the so called BDocs, which are used for communication with R/3.
For CRM 4.0 there is some standard XI Content and the according Proxies you can use. You can download it from http://service.sap.com/swdc --> Support Packages and Patches --> SAP Content --> Process Integration Content (XI Content) --> XI CONTENT BBPCRM --> XI CONTENT BBPCRM 4.0.
Import this contetn to XI, then open SPROXY in your CRM, if CRM is connected to XI you'll see all XI components including BBPCRM there. This component contains a proxy ProductSetIn and ProductSetOut as already explained by Lars. Use this to transfer material data.
Best regards
Christine

Connection Issues MDM Data Manager using Vista

Hello
I am trying to connect to the MDM Data Manager(v 5.5) and get a message "Cannot Connect to MDM Server". My colleague is doing the same thing and it works for him. The only difference is that he is on XP and I am on Vista.
Is there something which I need to do from my side to make it work from Vista ?
Appreciate your help.
Thanks
Bhavin

Hi,
There are additional patches you need to install for working on Vista. This is the file name - "MDMGC55006P3HF_10-10003297" you need to download from SMP and install them on your local machine for all the clients namely console, DM,IM,Syndicator.
After instaling this, it'll surely work.
Manish

Error in MDM - EP integration : "Failed to connect to MDM server. ....."

Dear SDN,
I m in middle of configuring the MDM and EP integration.
EP Version Info :
J2EE Engine 6.40 PatchLevel 108290.313
Portal 6.0.20.0.0
BP has been installed.
We are able to view MDM system and MDM search IViews in the Wizards in the portal.
MDM Version Info : MDM 5.5 SP 04
I come across the following error :
Step 4: An error has occurred
Failed to connect to MDM server. Check your system. The server may be down or there may be an error in one or more of your system parameters.
System parameters are Server name and pwd .
This parameters are used to start the server and pwd for accessing the server while mounting the server.
Also at the same time, my MDM server is running and repository is shown loaded and running.
Kindly suggest what should have been missed out from our side or some way we can make sure that error does not occur.
Please help.
Regards,
Chandani Shah.

Hi Chandani,
in Portal clik on Personalization, and in User Mapping you need to map the MDM repository user (may be Admin)..... then try another time.
Please, check the BP version in order to unserstand if it is the rigjt version for your MDM.
Hoper this help you.
Regards,
Vito

MDM WebServices Problem while connecting to MDM repository

Hello,
we have installed the Web Services for MDM.
When I test the Services, say the MDMSearchRecords I always get a ERROR status and the Message:
id (String) WS_LogonProblem
severity (String) ERROR
text (String) Problem while connecting to MDM repository: z_Material on server: debmu416.server..... at port: 4000. Maybe the Repository-Information has not been set correctly at the requested query.
status (String) FAIL
The Repository Information I try to connect with is correct (Repository Name, Server Name, Port, data Language and schema Language).
Can you pls tell me where the problem could be?
Points will be generously rewarded!
Best Regards,
Mircea

Hi Arun,
Thanks a lot!
you were right! The WebServices version was too old.
Now I can connect to the Repository in Test mode.
I get some other error Messages, like "Field Material_Number is not defined at Table Products." and "Repository Data is not available in the requested Language ." which isn' right.
Do you have a clue where this could come from?
BR,
Mircea

Error when connecting to MDM from different lan

Hi,
I got "Image Server Login Error" when connecting with client to server from different LAN, server is up, and i can connect to it when i in the same LAN. Ports 20003, 20004, 20005 for MDM server discovering and repository port 2345 is accessible through router. Running SP2 5.5.24.06.
Rem: it's not a port problem, when port 2345 is closed i got "WinSock error on connect"
PS: When I used MDM SP1 i connected to him properly in the same case.

Hi Dmitry,
If your repository is set to port 2345, then 4 subsequent ports should be openned also, i.e. 2346-2349.
Regards, Lev

Different ways to connect to MDM from R/3

Hi Frds,
I am wondering what are the different appraoaches to connect MDM from R/3 except XI?
Thanks and regards,
Rajeev.

Hi Rajeev,
We can also use Tibco as a middleware instead of XI to connect to R3. We have used it in one of our projects.
Regards,
Dheeraj.

Webdynpro Java API Connection to MDM 7.1

Hello,
I have created several Webdynpro Java Applications to Connect to the MDM Repository and update/delete Records. To connect to the Repository ,I used the UserSession Context with which the userid/password is specified to connect to the Repository.
Now , if in future the password changes, I have to modify it in the UserSession Context Object each time . So is there a way ,we just update the password in one central location/file and the Webdynpro Java Application picks it up from there.
Any help would be highly Appreciated.

Sure
Thanks for the SAP Note, its a direct solution from SAP.
However I didnt have much time to implement it so found a workaround.
In my project we use MDM WD Configurations as well.
So I created a dummy ItemDetails WD Configuration( whose project uses the Destination is configured to use PROPAGATION)
line 1 : Created an emty RepositoryBean object : _repositoryBean = new RepositoryBean()
line 2 : wdThis.wdGetUC_ItemDetailsInterface().setConfiguration("<MDM WD PROJECT>", "<MDM WD CONFIG>"); //could be any config : resultset search ID
line 3 : (UserSessionContext)_repositoryBean.getUserSessionContext()
And viola I got it without any more coding

XI Connecting to MDM Inquiry

Similar Messages

Maybe you are looking for