SRM-MDM Connection Failed

Hi All,
When we open the following url http://<localhost>:50000/SRM-MDM/SRM_MDM?
and when we enter the server name, and click on "Connect", it says connection to server failed.
Can anyone help in:
1. What password do we enter here?
2. We have deployed all the required business packages, JAVA APIs from SRM-MDM Catalog 2.0. Is any other component required to be deployed?
Thanks and Regards,
Kaushik

Hi,
For open the following url http://<localhost>:50000/SRM-MDM/SRM_MDM
Have you deployed the following files in listed order:
1. SCA file with API and Connector (File Name: MDMJAVAAPIXX_X.sca)
2. SCA file for search and configuration UI (File Name: SRMMDMCATXX_X.sca)
which could you know about exact version by using SAP NOTE 1083126 for version mapping of SRM-MDM CATALOG 2.0.
Aftyer deploying the files, Restart your WEBAS
You need to put Server name of your MDM (HostName or IP Address) and Password = your MDM Server if you have set any otherwise leave it blank. once you able to Connect to your MDM Server you need to select your corresponding Repository and Put the User = Master and Pwd leave it as blank. then you could move to screen of configuration.
Hope it solve your Problem,
Thanks,
Mandeep Saini

Similar Messages

SRM MDM connection problem

Hello,
When I try to create a SC in SRM wizard the following error appears:
java.lang.NoClassDefFoundError: com/sap/mdm/blobs/BlobCacheException
Thank you.

please check this NOTE
Note 1015201 - SRM-MDM Catalog 1.0 Patch02 Release Note
for Bug-Fixes

Problem with SRM MDM connection

Hello,
When I try to create a SC in SRM wizard the following error appears:
java.lang.NoClassDefFoundError: com/sap/mdm/blobs/BlobCacheException
Thank you.

is it when
1 . u try to lauch the catalog from the SC ??
OR when u try to send the data from Catalog to SC back ??
when do u get this error ?
1 - ask the basis guy to check if the MDM server is up and running and whether the necessary deployables are deployed in the Java server ??
2- check OCI mappings and see if any fields concerning to BLOB tables in the MDM are mapped to some SRM field
hth
thanks
-Adrivit

SRM MDM 3.0 Catalog in MDM 7.1 - Portal Integration - Failed Connection

Hi All,
We are in the process of building up SRM MDM Catalog 3.0 in MDM 7.1 environment, we are able to
login/Configure using http://Server:port/SRM-MDM/SRM_MDM , but when we try to connect to the same URL using portal workset - Emplyee Self service ( Configured the same URL in SRM Server - defined external web service and linked with all mdm-user credentails ), it gives error - saying like "error connecting catalog - see system administrator "
My questions are
1. Is it mandatory to use Portal-MDM ivews to build the catalog page and assign it to users or we can also follow the same methadology like defining the webservice in SRM by providing URL with credentials?
2. if we can define SRM MDM catalog UI using external catalog webservice definition, then how we would integrate it to the portal page ( in Shop page ) - is any config required in portal side?
Please help

Hi Sandip,
I'm having a similar issue with SRM 7.0 and SRM-MDM Catalog. Did you resolve this problem? I'd be very grateful if you could advise if you managed to find a solution.
best regards,
Matt

SRM-MDM 3.0 SP10 Patch 1 - logon failed

Hello there,
we have a urgend problem after upgrading the SRM-MDM Components and the MDM Server.
Problem is, that we are not able to logon to the app ui or the search ui. It's not a Problem with the user. When logon to the app ui we receive the message "logon failed".
Connection to the Repository via MDM Clients works very well. Only the Web UI is not accessable.
To be sure we are having the right SPs for the Components we downloaded the latest Support Stack that includes all components versions that fits to each other (thats what i think).
At least we have now
MDM Server SP06
MDM Catalog SP10 Patch 1
Java API SP10 Patch 0
MDM Connector SP10 Patch 7 (?)
Here's the information from the connection test via mdm utilities
!======================================!
Host-Adresse = 10.199.29.243
Host Name = mpgmdms
Repository-Port = 2000
!======================================!
MDM-Server-Ports werden geprüft...
Verbindung ok (Port 59950, Zeit = 0 ms)
Repository-Ports werden geprüft...
Verbindung ok (Port 2000, Zeit = 0 ms)
Verbindung ok (Port 2001, Zeit = 0 ms)
Verbindung ok (Port 2002, Zeit = 0 ms)
JAVA-API-Version von MDM ermitteln
Admin Version = 7.1.07.101
Build Version = 7.1.07.166
Content Version = 7.1.07.101
Meta Version = 7.1.07.101
!======================================!
Verbindung zu MDM-Server 10.199.29.243 wird hergestellt
MDM-Server-Version wird ermittelt...
Version = Version 7.1 (7.1.06.234 Win64)
!======================================!
Installierte Repositories werden ermittelt...
-> MPG_DEV_MASTER (S36/ORCL)
-> MPG_DEV_SLAVE2 (S36/ORCL)
-> MPG_DEV_SLAVE (S36/ORCL)
-> MPG_TEST_REPOSITORY (S36/ORCL)
From the visua administrator we get the following releaseinformation:
MDM_Connector 1000.710.700.7.1.201105150802
MDM_JAVA_API 1000.710.0.7.166.20110410110411
SRM_MDM_CAT 1000.3.0.10.1.20110429065011
Within the MDM Console we get a some log entries when trying to log in.
Hope you can help me.
Thank your
Rico
Edited by: Rico Stoll on May 25, 2011 6:31 PM

ur API / connector and MDS are on diff SP levels :
JAVA-API-Version von MDM ermitteln
Admin Version = 7.1.07.101 Interface CRC=0x7d50b0cf
Build Version = 7.1.07.166
Content Version = 7.1.07.101 Interface CRC=???
Meta Version \t= 7.1.07.101 Interface CRC=0x3a0a3732
!======================================!
Verbindung zu MDM-Server 10.199.29.243 wird hergestellt
MDM-Server-Version wird ermittelt...
Version = Version 7.1 (7.1.06.234 Win64)
upgrade the MDS to SP 07 and things should start working !
thanks
-Adrivit

SRM-MDM 3.0, assignment failed, runtime error

Hi all,
We are using SRM-MDM catalog 3.0, MDM-Client version are 7.1.01.78.
When building assignments which include lookup tables, the assignment failes giving the following runtime error:
"Assignment operation failed: A runtime error occurred while evaluating an validation or calculation field"
The assignment is initialising the item type with "Normal". If it is already filled, leave the old value.
Assignment Code Used: IF(IS_NULL(Item Type.[[Record]]), Item Type [[Normal]],Item Type.[[Record]])
The runtime error only occures when the Else-branche is processed.
This code above is also used in version 2.0 of the srm catalog, it is valid and working properly.
The code was re-entered in a, newly created, version 3.0 catalog-repository.

Error solved, we upgraded to version 3.0 Support pack 05 patch 2

Error when connecting to SRM MDM UI

<pre>Hello Java Experts,
I get the following error when I try to access our SRM MDM UI for catalog config. Can anynoe suggest any hints or tips on how to resolve this issue?
regards
The error message is below:
The initial exception that caused the request to fail, was:
   com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to get deployable object part info for component com.sap.mdm.srmcat.eform.ElectronicForm
    at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.getComponentDeploymentDescription(ClientComponent.java:784)
    at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.createComponent(ClientComponent.java:934)
    at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.createComponent(ClientComponent.java:177)
    at com.sap.tc.webdynpro.progmodel.components.ComponentUsage.createComponentInternal(ComponentUsage.java:149)
    at com.sap.tc.webdynpro.progmodel.components.ComponentUsage.createComponent(ComponentUsage.java:116)
    ... 58 more
Detailed Exception Chain
com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to get deployable object part info for component com.sap.mdm.srmcat.eform.ElectronicForm
     at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.getComponentDeploymentDescription(ClientComponent.java:784)
     at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.createComponent(ClientComponent.java:934)
     at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.createComponent(ClientComponent.java:177)
     at com.sap.tc.webdynpro.progmodel.components.ComponentUsage.createComponentInternal(ComponentUsage.java:149)
     at com.sap.tc.webdynpro.progmodel.components.ComponentUsage.createComponent(ComponentUsage.java:116)
     at com.sap.tc.webdynpro.progmodel.components.ComponentUsage.createInstanceIfDemanded(ComponentUsage.java:728)
     at com.sap.tc.webdynpro.progmodel.components.ComponentUsage.getInterfaceControllerInternal(ComponentUsage.java:346)
     at com.sap.tc.webdynpro.progmodel.components.ComponentUsage.getControllerInternal(ComponentUsage.java:387)
     at com.sap.tc.webdynpro.progmodel.controller.Component.getMappableContext(Component.java:421)
     at com.sap.tc.webdynpro.progmodel.context.MappingInfo.getDataNode(MappingInfo.java:83)
     at com.sap.tc.webdynpro.progmodel.context.MappedNodeInfo.getDataNode(MappedNodeInfo.java:207)
     at com.sap.tc.webdynpro.progmodel.context.MappedNodeInfo.getStructureType(MappedNodeInfo.java:109)
     at com.sap.tc.webdynpro.progmodel.context.MappedNodeInfo.getStructureType(MappedNodeInfo.java:110)
     at com.sap.tc.webdynpro.progmodel.context.NodeInfo.initStructureType(NodeInfo.java:718)
     at com.sap.tc.webdynpro.progmodel.context.NodeInfo.initAfterCompletedMapping(NodeInfo.java:706)
     at com.sap.tc.webdynpro.progmodel.context.MappingInfo.initAfterCompletedMapping(MappingInfo.java:140)
     at com.sap.tc.webdynpro.progmodel.context.MappingInfo.initMapping(MappingInfo.java:133)
     at com.sap.tc.webdynpro.progmodel.context.MappingInfo.setMapping(MappingInfo.java:183)
     at com.sap.tc.webdynpro.progmodel.context.MappedNodeInfo.setMapping(MappedNodeInfo.java:130)
     at com.sap.tc.webdynpro.progmodel.components.ComponentUsage.createReverseMappings(ComponentUsage.java:675)
     at com.sap.tc.webdynpro.progmodel.components.ComponentUsage.createComponentInternal(ComponentUsage.java:168)
     at com.sap.tc.webdynpro.progmodel.components.ComponentUsage.createComponent(ComponentUsage.java:116)
     at com.sap.tc.webdynpro.progmodel.components.ComponentUsage.createInstanceIfDemanded(ComponentUsage.java:728)
     at com.sap.tc.webdynpro.progmodel.components.ComponentUsage.getInterfaceControllerInternal(ComponentUsage.java:346)
     at com.sap.tc.webdynpro.progmodel.components.ComponentUsage.getControllerInternal(ComponentUsage.java:387)
     at com.sap.tc.webdynpro.progmodel.controller.Component.getMappableContext(Component.java:421)
     at com.sap.tc.webdynpro.progmodel.context.MappedAttributeInfo.initAttributeMapping(MappedAttributeInfo.java:323)
     at com.sap.tc.webdynpro.progmodel.context.MappedAttributeInfo.getDataAttribute(MappedAttributeInfo.java:82)
     at com.sap.tc.webdynpro.progmodel.context.AttributeInfo.getDataAttributeInternal(AttributeInfo.java:157)
     at com.sap.tc.webdynpro.progmodel.context.MappedAttribute.getDataPointer(MappedAttribute.java:72)
     at com.sap.tc.webdynpro.progmodel.context.MappedAttribute.setInt(MappedAttribute.java:264)
     at com.sap.mdm.srmcat.uisearch.master.wdp.IPublicMaster$IContextElement.setUsePriorityCount(IPublicMaster.java:2106)
     at com.sap.mdm.srmcat.uisearch.master.Master.wdDoInit(Master.java:146)
     at com.sap.mdm.srmcat.uisearch.master.wdp.InternalMaster.wdDoInit(InternalMaster.java:769)
     at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.doInit(DelegatingComponent.java:108)
     at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)
     at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
     at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.init(ClientComponent.java:430)
     at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:362)
     at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:756)
     at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:291)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:713)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:666)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250)
     at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
     at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
     at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
     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(AccessController.java:219)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
</pre>
Edited by: Onyedika O. on Jul 16, 2009 9:59 PM

Hi
Intial Exception suggesting some of its reference component Failed to get deployable on server.... try to check the reference componenet, which is not getting deploy.
Some times it also get resolved by restarting the server then deploy.
Thanks

SRM-MDM Catalog Installation/Landscape

Hi,
We are currently having the following landscape in place with regards to the SRM, MDM and SRM-MDM Catalog :
Server 1 : SRM 5.0 Running   (HP-UX)
Server 2:   Enterprise Portal running with MDM Content and SRM-MDM Catalog JAVA components (HP-UX)
Server 3:   Standard MDM Server installation (Windows 2K)
We have configured everything according to the notes and guides (including the guide from Sudhendu Pandey), but when we try to configure the Search UI in Webdynrpo, the java components cannot connect to the MDM host and we are getting just the connection failed error.
My questions are :
1)   Can we run with the above landscape or is it necessary to have the SRM-MDM Catalog Java components installed on the same server as MDM.
2)   Do we have problems with versioning of the MDM server and the SRM-MDM java components ? We already replaced the MDM_JAVA_API with the correct one, but I do not have a newer version of the other api.
3)   Do I need to configure anything on the MDM server to get this running ?
Thanks in advance for your help
Regards
Raymond

Hi Foh,
Apologies for my late reply, but I was travelling. Thanks for this tip. We were using the latest versions for the MDM Portal Content, but the API for the SRM-MDM catalog was different.
I have updated this API with the latest version (Patch 3 HF 1) and now I can logon to the MDM server and I see the MDM Repositories. However if I now try to logon to one of the repositories he gives me the same error that the Login has Failed. The user that I am using is the default one coming with the SRM-MDM repository (Admin).
Regards
Raymond

SRM MDM, Error, "Table with Code 'null' does not exist in repository"

Hi experts,
We has SRM MDM scenario, while doing OCI settings, we are able to connect with MDM repository but getting follwoing error message in portal, "java.lang.IllegalArgumentException: Table with Code 'null' does not exist in the repository 'Repository' or is one of the system table (e.g. Workflows) that is not exposed in repository schema"
Can You please suggest,
Thanks and Regards,
Munish

Hi everyone,
Sudhanshu and Anshuk:- Thanks for your response, let me try and explain the real scenario in details:-
We have deployed the SRM-MDM Catalog Search UI in Portal.
We tried accessing the http://<Portal Host>:<Portal Port>/SRM-MDM/SRM_MDM
Then we got a screen (Search UI App screen), where in we have provided the MDM Server name, then the MDM Server Password, then presses the Connect button, then below this, it displayed the Repository name created in the MDM. We have selected the Repository, then provided the Credentials of a User (Name: T_CORP) in MDM which has "Catalog Manager", and the "UI Configuration Manager" Roles. Please note that these Role names were created by us in MDM. Is it the right procedure or do we have any standard Roles delivered by SAP in MDM to map? If any standard Roles are available, where we need to check these.
Once the Credentials of MDM User is provided, and then selected the "Login" button.
Then we are getting the below error.
"java.lang.IllegalArgumentException: Table with Code 'null' does not exist in the repository 'Repository' or is one of the system table (e.g. Workflows) that is not exposed in repository schema"
Please clarify; we are not configuring any values in iViews. Where we need to do this, I mean name of the iView, and what values do we need provide generally? We are just running the Search UI App application; I don't think it is an iView, because the URL shows the Application name details, etc...
Please guide us, how to fix this Error.
Thanks and Regards,
Munish

SRM-MDM catalog 3.0 - Installation Process

Hi All,
I'm in the process of installing SRM-MDM catalog 3.0 but I'm not sure about the correct installation process.
The SRM-MDM catalog 3.0 installation guide indicates that the following instances are mandatory for SRM-MDM Catalog system:
1- Java system with the central instance, the central services instance, the database instance
2- MDM Server, and MDM Import Server
We have covered the first point by installing an SRM 7.0 JAVA system. Regarding the second requirement, I have some doubts in the way it should be completed. What we did so far was to install the SRM-MDM catalog 3.0 from the MDM 7.1 installation master. So, we now have two MDM server instances: MDS and MDIS.
I'm stuck now. I'm not sure on how to connect my SR-MDM system to the JAVA DB (created in step 1) to create a new MDM schema within it. This makes me wonder if I've followed the correct process. Could you please clarify and explain which steps should be performed to get my SRM-MDM system up and running? Actually my main concern is..Should I first install a MDM system as it's described in MDM IG, and after that perform the installation of the SRM-MDM catalog as I've already done in step 2?
Hope being clear enough I'll wait for your suggestions.
Thanks and regards

Hi Diego.
The Installation Note Number for SRM-MDM Catalog 3.0 is : 1177779. The recommended steps would be to follow how the Installation Guide recommends you to do so.
But still your assumption is correct. MDM landscapes and Java landscapes are both different set of categories to be installed to make the Catalog scenario to be successfull.
Step 1: Make sure you have the back end database server(SQL/Oracle/???) is installed.
Step 2: Make sure all the MDM components(MDS, MDIS, etc) is installed.
Step 3: Make sure Java WebAS is installed correctly.
Step 4: Now deploy the Catalog SCA and MDM Connector deployed in the Java WebAS.
Step 5: You can unarchive and load the repository.
Step 6: Try to launch the catalog using the URL provided to check and make sure if the connection is fine.
Also what Masa has mentioned is the communication path how the whole process is achieved technically and that doesn't mean that it has to be in the same order which he has mentioned. The below sequence is just an path to describe how the communication is achieved technically.
User -> Browser(Search UI deployed on AS Java) -> (Java API on AS Java) -> MDM Server -> MDM Repository -> DB
Relating Masa's path with the above steps
User ->
Browser(Search UI deployed on AS Java) -> Step 3 and 4
(Java API on AS Java) -> Step 3 and 4
MDM Server -> Step 2
MDM Repository -> Step5
DB-> Step 1
Hope this helps.
Regards
Bala
Edited by: chandar_sap on Aug 30, 2010 6:16 PM

SRM 7.0 and SRM MDM Installation query

Hi,
I have installed Both AS ABAP and AS JAVA Stack separately and going forward I need to know
1) Do I need to install any other servers other than this like EP and PI etc?
2) I also wanted to install SRM MDM, for that I have gone through some documents and threads and found that
Prerequisites
1. SRM Server- Installed with ORACLE database
2) For SRM MDM
Ø        Download the SRM-MDM Catalog 2.0 installable from Market Place-- Done
Ø         Install the MDM Server and other GUI Clients--Done
Ø     UnArchive the SRM-MDM repository available with the installables only
                     Need help for
             . Not able to find DBMS server
             . User
               . Password for DBMS setting
Ø      Deploy the two SCA files - MDMJavaAPI and SRMMDMCAT on WAS and restart the Portal- Done
Ø        Access the Config UI by using the URL http://:/SRM-MDM/SRM_MDM and change the layout as per the requirement. In this you can specify the fields to be displayed for Search, type of UI etc for the particular user
. Where I can get the "Port"
Will follow the below steps once the above issues are resolved
*Create the Web Service in SRM system and specify all the required
parameters. You should get the SRM-MDM configuration guide from Market
Place.
*Change the Org Plan in SRM to assign the Catalog to the SRM users.
*Login into EBP and select SHOP, you should get the SRM-MDM Catalog link
if all the configurations are there in place.)
3. Web Application Server
> Is seperate WAS required even after installing SRM AS JAVA stack, if yes what to install
       4) In the market place I have found that SRM MDM install.exe and in that there are two options to execute. Install MDM
           . Install SRM MDM
          Do I need to install both or only one or is this not required, if I install SRM MDM my question is what is the use of
          the above point 2 steps process this one
         Thanks,
          Jairaj
Edited by: M Jairaj on Feb 3, 2010 3:43 PM

Hi,
> I have installed Both AS ABAP and AS JAVA Stack separately and going forward I need to know
>
> 1) Do I need to install any other servers other than this like EP and PI etc?
>
As you have already installed Java stack then it will be your EP. You don't need PI for SRM MDM.
> 2) I also wanted to install SRM MDM, for that I have gone through some documents and threads and found that
>
>                      Need help for
>
>              . Not able to find DBMS server
The DBMS Server property defines the network identification string of the DBMS instance / machine / server that is used by the DBMSspecific client on the MDM Server machine to connect to the DBMS. The brand of DBMS on which the repository is running is shown in the DBMS Type property.
NOTE ►► When you mount two MDM repositories with the same name (but located on different DBMS Servers) on the same MDM Server, MDM distinguishes them in the Console Hierarchy pane by appending the name of the DBMS Server in angular brackets to the repository name (e.g. u201Crepository <server>u201D).
>              . User
>                . Password for DBMS setting
>
ent. In this you can specify the fields to be displayed for Search, type of UI etc for the particular       user
>
>       . Where I can get the "Port"
>
Note 1414670 - MDM 7.1: Adjusting MDS port in MDIS and MDSS ini files
Check SAP Note 1077701 - SRM-MDM Catalog - FAQ
>        4) In the market place I have found that SRM MDM install.exe and in that there are two options to execute. Install MDM
>            . Install SRM MDM
>
Check installation guide for this.
Thanks
Sunny

SRM MDM Installation

Hi,
I am new For SRM MDM
Regarding SRM MDM< installation i need some help
1) Is SRM MDM is inbuilt in the SRM 7.0 or we need to install seperately
2) In the installation manual it is given that we need to install SAP netviewer JAVA AS is this SRM JAVA AS or do we need seperate SAP Netviewer JAVA AS
3) I have seen that in the market place MDM installaions available under SRM 7.0, and if i run installation.exe i can find two options(Oracle ) a) MDM b) SRM MDM which one i have to select to install SRM MDM or this is not required
4) In market place under Netviewer MDM there is a SRM MDM installables in this i can find
a) MDM servers installables
b)MDM Import manger
c)etc..
is above installable are sufficient to run SRM MDM after installing SRM 7.0 or any other components required
5) Do we need to install Orcale for SRM MDM also if yes how to connect to SRM MDM
Thx
Jai

Hi ,
1.What to download from service marketplace?
Install the SRM MDM catalog 2.0 business content.This contains a separate MDM server,GUIs ,a2a file,sca files .
2. Where to install?
Install MDM server and GUI.Aprt from MDM and SRM server we need to have WebAS.
3. What all other configuration/setup needs to be done?
Unarchive the SRM MDM repository(.a2a file)
create roles ,users and fields in that.Load it.
Import the data .
check the data in data manager.
Side by side u need to deploy the sca files on WebAS.
on SRM side EBP configuration to be done (define external webservices)
Also assign the catalog to users in SRM
then using the URL
http://J2EE server:port/SRM-MDM/SRM_MDM do the OCI mappings
then u can see the MDM catalog in SRM
U can refer note 1057316
Regards
Nisha

SRM MDM Installation Problem (.a2a file Unarchive issue)

Hi All,
I am totally new for SRM MDM, and need to install SRM MDM and configure the system.
Below are the steps what i have done till up to
Already SRM 5.0 Installed
Installed Oracle 10g ( with diffrent Oracle SID as I have already one Oracle installed for SRM)
1) Installed MDMServer- Version.5.5.41.70.exe
2) Installed SAP MDM Console
3) Installed SAP MDM Data manager
4) Installed SAP MDM Import manager
5) Copied .a2a file in -Program Files\SAP MDM 5.5\SERVERS/Archive
Could you please explain....
1) How to deploy MDMJAVAAPI05_1.sca and SRMMDMCAT01_0.sca in the SAP WAS
Not able find "RemoteGui.bat" or "Configtool.bat" in Program Files\SAP MDM 5.5 but I can find these files in SRM
G:\usr\sap\ECC\DVEBMGS04\SDM\program\RemoteGui.bat and
G:\usr\sap\ECC\DVEBMGS04\j2ee\configtool\configtool.bat
2) How to Unarchive the SRMMDMCAT01_0.sca in MDM Console
In fact I am not getting any User folder under "Program Files\SAP MDM 5.5 "
Thanks
jairaj

Hi,
1. Deploy MDMJAVAAPI05_1.sca and SRMMDMCAT01_0.sca in the SAP WAS using SDM.
For more information about installation and Configuration please refer SAP Note # 1057316
2. to unarchive repository steps are follows:
     1. copy .a2a file in the archive directory of MDM server
      2. open console and mount MDM server.
      3. right click on server and select unarchive repository. provide the DBMS connection details and Repository Name and specify the .a2a file. then click ok. This will unarchive your repository. For more details please refer to console reference guide.
kindly let us know if you have any query.
Regards,
SHiv

SRM-MDM AS Java Sizing

I have some sizing questions regarding the SRM-MDM NW AS Java instance.
In the document "Sizing SRM-MDM Catalog 2.0 SP03" the following equation is provided for calculating memory requirements for the NW AS Java server:
Fixed Memory = CMULANG*CAT + 50MB
C = fixed memory contant (~ 15mb per 100k items in catalog)
MU = number of MDM users
LANG = number of languages for concurrent connections
CAT = number of catalogs
It is unclear whether these variables are for all catalogs or for each catalog. I would assume that since there is a multiplier for the number of catalogs (CAT) that the rest of the parameters are for each catalog.
With that assumption I would have the following values for my system. Can anyone confirm that I am interpreting the meaning of the variables correctly?
C is based on the number of items I have per catalog (not total), in my case 1000items/catalog. So C= .15 MB
MU is the number of MDM users where an MDM user is defined in the document as: "the user who is maintained in the URL of the catalog. The available MDM users can be seen in the MDM Console. Only those users who have role Catalog User assigned can access the SRM-MDM Catalog." I am not sure why more than one MDM users would be needed so I am using the value 1.
LANG is the number of languages for concurrent connections. Is this per catalog or for all catalogs? If I assume all I would guess that I might have 5 separate languages at any given time.
CAT in my case is a very large number as we have a large amount of small catalogs (~250).
Fixed Memory = .15MB * 1 * 5 * 250 + 50MB = 237.5MB

Hello Michelle,
MU--> How many no of MDM user will use the catalog on the web.(In current version of catalog max 50 user can log into the catalog concurrently)
If you not mentioned the user credential in the catalog access URL, it will ask fior the catalog user name and pwd. It totally depend on the business req, how you have to use the MDM users for the catalog.
TNR,
Saurabh...

SRM MDM 3.0 Integration with PI 7.1

I have the integration scenario where Supplier list need to transfer from SRM 7.0 to MDM 7.1 using the PI 7.1.
Imported the content into ESR (SRM Server 7.0,SRM MDM catalog 3.0 ) . I have 2 issues.
1. Try to transfer the process integration scenario from ESR to ID , I am able to see the SRM_MDM_Catalog_30 scenario. But when it did not allow me to assign the business systems and connections .
It throws an error saying that" Cannot load action; check whether all the required actions have been released in the Enterprise Services Repository". So I have done all the steps manually.
I have created the Interface determination with the following details :
Sender Interface: CataloguePublicationRequest_Out
Sender Namespace: http://sap.com/xi/EBP
Receiver Namespace: http://sap.com/xi/SRM-MDMCatalog
Receiver Interface: MDMSupplierListTransmission_In
The issue is, it does give me the option to select the any operationmappign with the above details.
Any steps in ESR missing or any CacheRefresh issue?
Thanks in advance for any suggestion.

Check the Operation mapping,like what is anbound interface and outbound interface, these details should match with interface determination details(outbound interface details).if you have configured perfectly then it will show the operation mapping.
still if you have a problem then better to refresh the cache,it will solve the problem.even you can manually type the operation mapping name in Interface determination,and test end to end.
if it is also not working out,then create one interface copy objects from two name sapces http://sap.com/xi/EBP
, http://sap.com/xi/SRM-MDMCatalog . and finish ESR and and finish ID too..
Regards,
Raj

SRM-MDM Connection Failed

Similar Messages

Maybe you are looking for