Registring MDM 5.5 SP06 with SLD

Hello,
I did referred the document as follows :
Document available in Service Market Place "HowToRegisterMDM_SLD_P22.pdf".
Link is ->
https://websmp210.sap-ag.de/installmdm -->Operations ---> MDM 5.5 - Monitoring Guides (ZIP File) in this Zip folder you will get "How To Register MDM Servers in the SLD"
and now we do have sld.xml file at MDM_HOME directory but still on SLD side we cant see MDS server and we dont also have sld.log at MDM_HOME
Can someone please help us to troubleshoot this issue?
points will be rewarded accordingly.
Regards,
Pravin

I was told by lot of friends that MDM 5.5 sp06 has also got many bugs ? is it right ? have you ever experienced ? what are those those ?
Thanks
SUNNY

Similar Messages

How to use SessionManager (MDM 5.5 SP06 JAVA API 2) with TrustedConnection

Hello MDM 5.5 SP06 JAVA API Experts,
Is it possible to Use the SessionManager in conjunction with TrustedConnections ? The trusted connection is setup properly (adding the client IP to the allow.ip file on MDM-Server).
I tried a lot but I didn't succeed with the new JAVA API 2 SessionManager functionality.
I'm initializing a UserSessionContext object and set the field for trusted connections to true.
Later I request an instance of SessionManager and call the createSession() method.
Although I've set the trustedConnection (=true) field of UserSessionContext, I get an exception, if the password is not set correctly. Due to my understanding, the password should be ignored if the UserSessionContext --> trustedConnection field is set to true. Is this a bug or am I missing any important step ?
I have also used several constructors of UserSessionContext but no chance.
Could anyone use the SessionManager with trusted Connections ?
Any help would be greatly appriciated.
Best regards.
      public static void main(String[] args)
        Settings settings = new Settings();
        RepositoryIdentifier repId = new RepositoryIdentifier(settings.repository,
                                                              settings.dbServer,
                                                              settings.dbmsType);
        //Create a UserSessionContext
        //UserSessionContext sessionContext = new UserSessionContext("<servername>", "<repositoryName>", "<userName>");
        UserSessionContext sessionContext = new UserSessionContext( "<servername>", repId, "English [US]", "<userName>");
        sessionContext.setConnectionType(ConnectionTypes.LOCAL_POOL_CONNECTION);
        sessionContext.setRegionLocale(Locale.US);
        sessionContext.setTrustedConnection(true);
        //Get an instance of SessionManager
        SessionManager sessionManager = SessionManager.getInstance();
        //Create user session
        String userSession =
        sessionManager.createSession(sessionContext, SessionTypes.USER_SESSION_TYPE, "<any pwd !!!>");
        System.out.println("Created user SessionID: " + userSession);

Hello Jitesh Talreja,
thanks for your reply and hint. The trusted connection configuration on MDM server is already setup correctly.
My concrete problem is to establish a trusted connection using the SessionManager.
If I use the TrustedUserSessionCommand, everything works.
        CreateUserSessionCommand createUserSessionCommand = new CreateUserSessionCommand(connection);
        createUserSessionCommand.setRepositoryIdentifier(repId);
        createUserSessionCommand.setDataRegion(dataRegion);
        createUserSessionCommand.execute();
        session = createUserSessionCommand.getUserSession();
        state = STATE_SESSION_ESTABLISHED;
        try
            TrustedUserSessionCommand tuscTrustedUser = new TrustedUserSessionCommand(connection);
            tuscTrustedUser.setUserName(userName);
            tuscTrustedUser.setSession(createUserSessionCommand.getUserSession());
            tuscTrustedUser.execute();
            session = tuscTrustedUser.getSession();
         catch (com.sap.mdm.commands.CommandException e)
            /* In Case the Connection is not Trusted */
            System.out.println("Could not established trusted connection!!!");
            e.printStackTrace();
But I want to make use of the SessionManager advantages see [MDM Java API Guide|http://help.sap.com/saphelp_mdm550/helpdata/en/47/9f23e5cf9e3c5ce10000000a421937/frameset.htm] -> API Structure and Basic Concepts

MDM 5.5 SP06 Support on SRM 7.0

Hi
We are using SRM 3.0 (EBP 4.0) with requisite catalog to maintain the catalog
We are going to upgrade SRM to SRM 7.0 and would like to use our existing MDM 5.5 SP06 lanscape (It is being currently used to maintain our company Product Master)
Can someone tell me that the latest SRM version 7.0 can use existing MDM Landscape without any issue
We have very small size of Catalog which we are using with SRM 3.0
Thanks in advance
Thanks
Deelip

Hey Deepali,
I informed you about best practice and SAP's recommendations.
My thoughts on WHY SAP RECOMMENDS SEPARATE LANDSCAPE FOR SRM-MDM CATALOG are as follows:
1. Version strategy of SRM-MDM Catalog is different from MDM Product version strategy. And from my experience what i have seen, compatible package of SRM-MDM Catalog is released with in 1-2 month of release of normal MDM. You may face a situation that a new version of MDM is available but SRM-MDM Catalog version compatible to this MDM version is not released..
For example, As of now, MDM 7.1 SP05 is the latest version, but latest version SRM-MDM Catalog version is based on MDM 7.1 SP04 and as of now MDM 7.1 SP05 is not yet supported for SRM MDM Catalog.
2. if You face any compatibility problem or issue in SRM-MDM Catalog and have to upgrade MDM patch to fix it, then it will disturb your other master data object processes too.
3. SRM-MDM Catalog UI should be compatible to MDM Server Version and is based on a specific MDM Release. You may face a situation that SRM-MDM Catalog package not exactly matching your MDM Server version.
Please check the version mapping note for SRM-MDM Catalog 2.0 and MDM 5.5. this will explain this point in a better way..
SAP Note 1083126 - Version mapping SRM-MDM Catalog 2.0 to SAP MDM 5.5
But, on the other side, i don't see any technical restriction in using SRM-MDM Catalog with other Master data objects (* if you can get SRM-MDM Catalog package matching to your MDM server version)
So, you can also use same MDM server in above case.
Hope this will clearify things more...Revert if any further question...
Best Regards,
Shiv

Integration Engine does not connect with SLD

Hi all,
We have an XI 3.0 system that acts as QUA system in our track. This XI 3.0 system is connected to a central SLD installed on a PI 7.1 system that acts as our DEV system.
Everything seems to be OK in the Java part. We refresh the caches successfully and enter the SLD in DEV system.
We have a problem, though with the SXI_CACHE transaction. It shows the following message:
"Unable to refresh cache contents.Error during last attempt to refresh cache"
And the detail of the error is: "LCR_GET_OWN_BUSINESS_SYSTEM - NO_BUSINESS_SYSTEM"
We have checked in the SLD and the Business system is created.
In transaction SXMB_ADM when checking the Integration Engine connection with SLD we get the following error: "No access to system landscape at present"
In the Runtime Workbench of the system, when checking the Cache Connection, the Integration Engine part shows a warning. In the RWB also the Self Status Check of the Integration Engine gives errors:
"Are roles in SXMS_CONF_ITEMS and SLD consistent?"
We have already followed all the post installation guides, and the cache checks, and SLD checks guides.
Do you know which the soltion could be for our error??
Thanks!

Hi,
We have checkes
SM59: TCP/IP Destination: LCRSAPRFC y SAPLSDAPI. check the program ID is correct.--> connection test goes OK
HTTP destination: INTEGRATION_DIRECTORY_HMI: do a test connection: result=500--> connection test gives us 500 result
SLDAPICUST: Check the user and password and the server defined. the PI server should be the main server.--> checked, OK
SXMB_ADM>Integration Engine Configuration: Check if the destination is properly defined. should be dest://http://<server><port>/sap/xi/engine?type=entry> checked. OK
Check RZ70: wich configuration you have there?--> The configuration in the RZ70 for the SLD is pointing to the DEV system, so it is correct
SLDCHECK results:
"Properties of RFC destination SAPSLDAPI
RFC host:        %%RFCSERVER%%
program id:      SAPSLDAPI_XXX
gateway host:    XXXX
gateway service: XXXXX
Testing the RFC connection to the SLD java client...
RFC ping was successful
SLD server access settings:
host name:   XXXXX
port number: 50000
user       : XIAPPLUSER
Use transaction SLDAPICUST if you wish to maintain the SLD server access data
Launching the SLD GUI in a separate browser window...
=> Verify in the browser GUI that the SLD is in a healthy running state!
Calling function LCR_LIST_BUSINESS_SYSTEMS
Retrieving data from the SLD server...
Function call terminated sucessfully
List of business systems maintained in the SLD:
    (...more...)
Calling function LCR_GET_OWN_BUSINESS_SYSTEM
Retrieving data from the SLD server...
No corresponding business system found for system XXX      client 450
=> Check and maintain the SLD content for the current client
Summary: Connection to SLD works technically, but the SLD content may need maintenance
=> Check and maintain the SLD data content
*Unable to refresh cache contents.Error during last attempt to refresh cache" * this error is related with the RFC destination type HTTP. ( HTTP destination: INTEGRATION_DIRECTORY_HMI: do a test connection: result=500)

How to get Systems definition in SMSY with SLD ?

Hello,
I have configured SMSY to work with SLD and it works fine.
After synchronizing, I can see Server, Database and System Component provide by the SLD. But I can only see one System (Solution Manager itself).
Is it a bug or there a solution to import Systems form SLD that are not SM ?
Thanks
Regards
Chris

Hi Chris,
After adding JAVA system into SLD.Then you can choose Relevant main instance for that java system as XI or XSS.Once you choose relevant instance then those JAVA system will be shown into SLD.
Regards,
Sumit

Explorer Version for MDM 5.5 SP06

Hi,
I was wondering if MDM 5.5 SP06 supports any other internet explorer version than IE6?
I found a note (1422355) regarding 7.1 where support for IE 8 is mentioned, but nothing about the 5.5 version.
I think the PAM mentions IE6, but I just want to make sure, since there are so many hotfixes
Best Regards
Olof

Hello Olof
Sorry i don't have "Portal Business Package" guide for SAP MDM 5.5 SP5
But As i told you early.
if you look at that guide ( for SAP MDM 5.5 sp6) (Page 10):
https://websmp201.sap-ag.de/~sapidb/011000358700001119502007E
"...Browser Recommendation: Any browser supported by EP 6.0 or EP 7.0..."
Do you have "Portal Business Package" for SAP MDM 5.5 SP5 guide for supported browsers search?
and you can ask your Portal consultant or found in TEP10 which kind of browsers aresupported.
Regards
Kanstantsin Chernichenka
Edited by: Kanstantsin Chernichenka on Mar 29, 2011 3:39 PM

Does CTS+ work with SLD transport targets for ID transports?

Hi,
does CTS+ work with SLD transport targets for ID transports?
did any of you ever used it ?
thank you,
Regards,
Michal

Hi Michal
I would be interested to find out about this..
Hopefully this new project will use 7.1 and Basis are doing all the SLD and the CTS+ config..
I have every faith in them!!!! :-O
There is a document about transporting repository and directory objects, but every version I have found is corrupt - or I cannot open in Adobe...
You may have more luck!
Change and Transport System
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/80bbbd55-5004-2a10-f181-8bb096923cb6
"This How-to Guide explains stepby-step how to set up the enhanced Change and Transport System (CTS) for use in conjunction with usage type Process Integration (PI) of SAP NetWeaver (formerly known as SAP NetWeaver Exchange Infrastructure or SAP NetWeaver XI). CTS introduces a new transport handling mechanism that offers tighter integration for the transport of ABAP, Java, and Integration Builder objects (Integration Repository and Integration Directory) using the Change and Transport System (BC-CTS) functionality."
Maybe in six weeks I can actually answer this for you! I'm sure you'll have the answer by then!

A2a file MDM 5.5 SP06

HI,
Please guide me where i can download sample a2a file for MDM 5.5 SP06
Regards
Subhash

Hi,
you can find DEMO repository here:
SAP NetWeaver - Demo Model;jsessionid=%28J2EE3414900%29ID1355369050DB11065073906383630678End#section21
Hope this help you.
Best Regards,
Vito

Apply of MDM 5.5 SP06 Patch02 and its hotfix's

We would like to apply MDM 5.5 SP06 Patch02 and its from Hotfix01 to Hotfix09 and would be an additional incentive to consider upgrading to the latest hotfix
(see the list of SAP Notes):
1161112,,MDM 5.5 SP06 Patch02 Hotfix01 Release
1161921,,MDM 5.5 SP06 Patch02 Hotfix02 Release
1163274,,MDM 5.5 SP06 Patch02 Hotfix03 Release
1165957,,MDM 5.5 SP06 Patch02 Hotfix04 Release
1170620,,MDM 5.5 SP06 Patch02 Hotfix05 Release
1171782,,MDM 5.5 SP06 Patch02 Hotfix06 Release
1174451,,MDM 5.5 SP06 Patch02 Hotfix07 Release
1176439,,MDM 5.5 SP06 Patch02 Hotfix08 Release
1178352,,MDM 5.5 SP06 Patch02 Hotfix09 Release
Please guide us to complete this MDM 5.5 SP06 Patch02 and its hotfix's still 9
Thanks
Rama k Junnuru
Edited by: Rama K Junnuru on Jun 24, 2008 8:24 PM

Hi,
Anybody applied hotfix from 1 to 9 , if applied please let me know.
Thanks
Rama K Junnuru
Edited by: Rama K Junnuru on Jun 25, 2008 10:42 AM

Supplier Registration in ESourcing ( Vendor integration with ECC or MDM )

Hi All,
SAP ESourcing has the functionality of Supplier Registration. As per the functionality, Supplier will provide all the required information in the registration form. The Supplier form will go for approval to the Buyer / Purchaser. Once approved, the supplier will considered for RFx event. My questions are :
1 :Is there OUT OF BOX standard solution provided by SAP for integration of newly Approved supplier / vendor of ESourcing system with ECC so that system will automatically create new vendor in ECC.
2 : Is there OUT OF BOX standard solution provided by SAP for integration of newly Approved supplier / vendor of ESourcing system with MDM (Master Data Management system ) .
Please through some pointer on this ?
Regards,
Kalandi

Hi Kalandi
For your first question, if you deploy standard integration package provided by SAP for e sourcing-ECC integration, you can replicate approved e sourcing vendor to ECC using standard script (I think script name is "Publish to ECC" ).
In case you prefer a custom option,you can write a customized script to get a flat file (.CSV) download of e sourcing vendor whcih can be used to update ECC
As far as OUT OF BOX standard solution provided by SAP for integration of newly Approved supplier / vendor of ESourcing system with MDM (Master Data Management system ) is concerned, there is no standard solution provided by SAP but again since it is possible to get a CSV export of vendor field, it can be used to update MDM as well
Hope this helps!
Regards
Mudit Saini
Edited by: Mudit_UCB on Jun 28, 2011 1:20 PM

Problem with Individual Registration of HTMLDB app schema with SSO

I have successfully registered HTML DB instance as partner application to SSO and it works well.
Then, I also want to try with Individual registration of partner application schemas on the same HTML DB instance.
I have followed every steps in 'How-To' but keep getting this following error message:
Error Unable to run parse_url_cookie procedure as schema ICONNFNB with partner app name ICONNFNB_WORKSPACE
ORA-06550: line 1, column 7: PLS-00306: wrong number or types of arguments in call to 'PARSE_URL_COOKIE' ORA-06550: line 1, column 7: PL/SQL: Statement ignored
Anyone knows how to deal with this error ?
Thanks in advance for any help.
-Gary

To add more info to my previous question, my HTML DB version is 1.6.0.00.87
I have successfully registered HTML DB instance as
partner application to SSO and it works well.
Then, I also want to try with Individual registration
of partner application schemas on the same HTML DB
instance.
I have followed every steps in 'How-To' but keep
getting this following error message:
Error Unable to run parse_url_cookie procedure as
schema ICONNFNB with partner app name
ICONNFNB_WORKSPACE
ORA-06550: line 1, column 7: PLS-00306: wrong number
or types of arguments in call to 'PARSE_URL_COOKIE'
ORA-06550: line 1, column 7: PL/SQL: Statement
ignored
Anyone knows how to deal with this error ?
Thanks in advance for any help.
-Gary

Problem with SLD and Creation of JCo

Hello everyone!
I have a problem with the SLD and the Creation of JCo on the Portal, in trying to create the JCo always tells me that the name used there in the SLD, being that the facility is new.
Who performs the installation, set in the SLD the ECC 6 PRD, delete it to see if I could create a JCo but still the error again when creating the ECC 6 PRD in the SLD I said that already exists and can not create it.
I found a forum which recommended re-import the cimsap .... .... zip and zip CR_Content which would clean everything, I managed to import the zip cimsap ... but in trying to raise CR_Content gives me the following message "All incremental updates of the selected aggregate import for export SAP_CR line have already been loaded before. You require a newer import to update your current content SAP_CR version 4.11." .
I recommend, do the installation again, reload the cimsap.zip and CR_Content.zip a copy homogeneous.
from already thank you very much
Text of error to create JCo destination
Failed to process request. Please contact your system administrator.
[Hide]
Error Summary
While processing the current request, an exception occured which could not be handled by the application or the framework.
If the information contained on this page doesn't help you to find and correct the cause of the problem, please contact your system administrator. To facilitate analysis of the problem, keep a copy of this error page. Hint: Most browsers allow to select all content, copy it and then paste it into an empty document (e.g. email or simple text file).
Root Cause
The initial exception that caused the request to fail, was:
   java.lang.NullPointerException
    at at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.checkStatus(SystemLandscapeFactory.java:991)
    at at com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscape.checkStatus(WDSystemLandscape.java:469)
    at at com.sap.tc.webdynpro.tools.sld.ButtonBar.onActionGoForward(ButtonBar.java:505)
    at at com.sap.tc.webdynpro.tools.sld.wdp.InternalButtonBar.wdInvokeEventHandler(InternalButtonBar.java:280)
    at at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87)
    ... 28 more
See full exception chain for details.
System Environment
Client
Web Dynpro Client Type HTML Client
User agent Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; Trident/4.0; .NET CLR 1.1.4322; InfoPath.1)
Version null
DOM version null
Client Type msie7
Client Type Profile ie6
ActiveX enabled
Cookies enabled
Frames enabled
Java Applets enabled
JavaScript enabled
Tables enabled
VB Script enabled
Server
Web Dynpro Runtime Vendor: SAP, build ID: 7.0017.20081210091801.0000 (release=NW04S_17_REL, buildtime=2009-01-12:09:43:27[UTC], changelist=52884, host=pwdfm114), build date: Tue Apr 28 19:28:39 CLT 2009
J2EE Engine 7.00 patchlevel 48199.450
Java VM IBM J9SE VM, version:2.2, vendor: IBM Corporation
Operating system Linux, version: 2.6.18-92.el5, architecture: amd64
Session & Other
Session Locale en
Time of Failure Fri Aug 28 11:43:53 CLT 2009 (Java Time: 1251474233677)
Web Dynpro Code Generation Infos
sap.com/tcwdtools
No information available null
sap.com/tcwddispwda
No information available null
sap.com/tcwdcorecomp
No information available null
Detailed Error Information
Detailed Exception Chain
java.lang.NullPointerException
     at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.checkStatus(SystemLandscapeFactory.java:991)
     at com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscape.checkStatus(WDSystemLandscape.java:469)
     at com.sap.tc.webdynpro.tools.sld.ButtonBar.onActionGoForward(ButtonBar.java:505)
     at com.sap.tc.webdynpro.tools.sld.wdp.InternalButtonBar.wdInvokeEventHandler(InternalButtonBar.java:280)
     at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87)
     at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:67)
     at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doHandleActionEvent(WindowPhaseModel.java:420)
     at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:132)
     at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
     at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
     at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:321)
     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:207)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)

Hello!!
The "SLD" with which I am working up to Portal, the "ECC" installs itself as "ABAP.
Who did the installation and initial configuration, do not leave any documentation about it.
Now I need to create the systems and "JCo" necessary to enable them to implement the "ESS", but errors are presented above.
Some days ago I managed to update the CR_Content, which allowed me to create the "JCo" but at the time of the test, says' com.sap.mw.jco.JCO $ Exception: (103) RFC_ERROR_LOGON_FAILURE "name or password incorrect .
I managed to also create the portal systems, "System Administration -> System Configuration -> Content Portal" and to test it fails on "Test Connection with Connector", which as noted is associated with the connectors "JCo".
For the creation of the system, I think I should create something in the Visual Administrator ", but within the documentation that I do not see anything about it.
thanks for your help!

Solution Manager with SLD Question

Hi,
We have SM 4 and PI 7.0 BI 7.0 both system SLD are configured with solution manager 4.0, including Transport setup as well... The question is how to check that system are configuration I want to check everying is ok in Solution Manager is working perfect ?
How to configurion that SM... any special Transaction code or not ?
please advised
Thanks

T A,
check out
[https://websmp208.sap-ag.de/~form/sapnet?_SHORTKEY=01100035870000718044&]
[https://websmp209.sap-ag.de/~sapidb/011000358700000048292009F/]
Hope this helps.
Manoj

PI 7.1 - Problem with SLD and Runtine WorkBench

Hi All,
I have installed PI 7.1 on Solaris with Oracle DB.
When i go to http://<hostname>:54600/dir/start/index.jsp and click on System Landscape Directory its opening the following link:
http://54600:54600/sld/index.html (Instead of hostname its taking 54600 where 46 is our instance Number).
Could you please suggest me whether the above error is due to any parameter wrongly set? i have checked all the exchange profile parameters and everything is fine.
If this is the problem with configuration of SLD, Can I re-configure SLD? if so please guide me how to do that.
Even when i login into Runtime Work Bench and clcik on any option like Component Monitoring or Message Monitoring its taking long time stating "Query being Processes", i waited for long time and then the same error unable to reach "http://54600:54600 "
Could you please suggest me how to proceed further?
Thanks,
Subbu

Hi,
     Please check the following configurations:
ABAP stack:
1. SLDCHECK -    check the error.
2. SLDAPICUST - check the 'Host name'
Then, in browser;
http://<hostname>:54600/exchangeProfile
click and expand 'connections' -
com.sap.aii.connect.cr.name   - fully qualified host name
com.sap.aii.connect.integrationserver.sld.name -    is.<instancenumber>.<Hostname>
com.sap.aii.connect.landscape.httpport - 5 <instancenumber> 00
Use fully qualified host name where ever the host name is asked.
Once you edit the exchange profile, not necessary to restart J2ee Engine. Just refresh and check the value are changed.
Hope this will fix the issue.
Sunil Shetty.

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

Registring MDM 5.5 SP06 with SLD

Similar Messages

Maybe you are looking for