MDM Registration in SLD

Hello All,
I need to register MDM system in my PI 7.1 SLD, so i need to know, i should be doing this by adding as Standalong system type option or can i also do it with SLDREG?
I did read a note # 1018839 regarding SLDREG and as per it.."The "receiving" SLD must be at least Release 7.0. If an old SLD (for example, Release 6.40) receives an "sldreg" data package, it writes the
following error to the SLD log: ERROR". So i think this also applies for MDM system?
So can anybody please advice..how exactly should i be doing this?
Thanks
Anand.

Hello,
Thanks for the information. That is adding system manually, i'm trying to register it through SLDREG.
Anyways, i have ran the SLDREG command for configuring the system in SLD, it also generated file slddest.cfg & slddest.cfg.key, along with sld.xml in all 3 servers namely MDS, MDIS & MDSS. But it has not created sld.log file, from where i can see the logs. (I dont know...why it has not )
While registering i did not got any errors, but still i'm unable to see my MDM system in SLD, do i need to do any setting from SLD point of view in SLD server, after running sldreg command?
Please let me know, if any more settings need to be done.
Thanks,
Anand.

Similar Messages

  • AS-ABAP (BI) system registration in SLD RZ70 Error

    Hi guys, I'm following the SAP note 983156 - BI configuration w. Template Installer and I'm in the step in order to establish communication between my BW IDES and Portal.
    ""Checking the AS-ABAP (BI) system registration in SLD""
    the note says:
    "When configuring the Webdynpro Jco destination connectivity the AS-ABAP (BI) system must be configured in the SLD."
    Procedure:
    Logon to the SLD: http://<host>:<port>/sld. (Your configured SLD (central or local SLD))
    Please check in Home -> Technical Systems -> select type ABAP. This
    should have configuration of your ABAP (BI) system.
    If it is missing, logon to your ABAP (BI) system -> goto transaction RZ70. Fill in the SLD bridge: gateway info -> Activate -> Start data collection."
    Well, when I'm in SDL Home > Technical systems, I have nothing there, so I started to enable the SDL Bridge in RZ70 and after running it, it gives me the error:
    0: ibm_IAM_00                                : Collection of SLD data finished
    0: ibm_IAM_00                                : Data collected successfully
    0: ibm_IAM_00                                : RFC data prepared
    0: ibm_IAM_00                                : Used RFC destination: IBM_PORTAL_IAN
    0: ibm_IAM_00                                : RFC call failed: JCO.Server could not find server function 'SET_SLD_DATA'
    0: ibm_IAM_00                                : Existing periodic jobs removed. Number: 1
    0: ibm_IAM_00                                : Program scheduled: 20100602 000100
    1: ibm_IAM_00                                : Event-controlled job already exists; scheduling not necessary
    I looked through other posts, I eliminated SLD_NUC and SLD_UC from JAVA Visual Administrator, but still, the error persists.
    Any ideas?

    Hi Kuatroka,
    In relation to the following error received: "JCO.Server could not find server function SET_SLD_DATA"
    1) RZ70 could not find gateway - check gateway defined in RZ70 is up and running in host and SLD home page ->Administration -> Data Supplier Bridge and SLD gateway host is reachable from ABAP system host.
    2) Be aware SLD/J2EE does not install a gateway as standard - you must either install a dedicated gateway instance using Presentation CD/DVD or you must use a local ABAP gateway (normally local ABAP stack if SLD runs on J2EE ADDIN) or ensure the definitions are correct for any other ABAP systems gateway you choose to use
    3) Check the definitions in SLD -> Administration ->Data Supplier Bridge match the definitions in RZ70 - try also FQDN. Ensure these are the same!
    4) If you are operating multiple SLD see SAP note 700127
    5) Ensure you have not manually created entries for SLD_UC and SLD_NUC in the JCO RFC provider of the visual administrator. The SLD has its own internal JCO provider so there should be no entries in that of the Engine.
    I am not sure of your SP levels, but this may also apply: if you have a gateway service on the defined host, the definitions
    match between RZ70 and SLD, the gateway is running then it could be a problem with RZ70 - implement notes 906454 and 926089 and 907729.
    I hope this information helps.
    All the best,
    Cristiano

  • Registering MDM servers in SLD - Is it required?

    Hello mates,
    I was going thru this doc MDM 5.5 SP04 - <a href="https://websmp208.sap-ag.de/~sapidb/011000358700006117152006E">Register MDM Servers in the SLD</a>.
    My questions..what is the advanatage of registering MDM servers in SLD? Isn't it enough if we create Technical & Business Systems for MDM in SLD? Do we need to link the Tech/Biz system to the registered MDM servers in SLD? Can these servers be monitored or sth like that?
    I appreciate your inputs.
    thx in adv
    praveen

    I do not need to add the MDM servers..TS & BS did the job.

  • Name Registration in SLD?

    Hi all,
    Can anyone help in getting documents and ways for name registration in SLD?
    Thanks,
    Kannan.

    Hi,
    Get the documents from service.sap.com/sld. You can all your problems solved over here. If any specific issue is there you can revert.
    regards and do reward !!!

  • SMD registration in SLD

    Hello all,
    Could some one help me with SMD registraion in central SLD
    I added my agent to http://host:port/sld >technical system> type as standalone.
    still during my diagnostic self check, I get msg, register SMD to SLD.
    Regards,
    Shyam.

    Hi Shyam,
    do you configure or connect your Solution Manager to your Central SLD? You can check which SLD is used via the SMD Agent Administration page:
    http://<solution manager hostname>:<HTTP Port>/webdynpro/dispatcher/sap.com/tcsmdnavigation/StandaloneApp?APP_ID=ADMIN_AGENT
    or
    Go to the SM Workcenter Diagnostics and click on Agent Administration
    On the Agent Administration page click on the  Agent Candidates Management link:
    http://<solution manager hostname>:<HTTP Port>/webdynpro/dispatcher/sap.com/tcsmdserveragentadmin/SLDAgentCandidates
    Here you can see which is your leading SLD for Solution Manager and SMD agents.
    Also check the attached document from SAP Note 1148028 - Setup SLD in the scope of Solution Manager 7.0
    Hope this helps
    Best regards,
    Mike

  • TREX registration to SLD doesn't work.

    Hi everyone!
    I have installed a new TREX 7.0 with the latest patch level and I have a real issue in the post task of the TREX installation guide. When the TREX tries to update the remote SLD with own data it get's an error message "HTTP ERROR CODE 400" Bad request. I'm using the default port 50000 and XISUPER as user to connect to the SLD. The SLD runs on the same instance as SAP XI. Is it possibly to run SAP XI 3.0 SP 18 with NW2004s TREX or do I need to upgrade the SAP XI instance to the latest WEB AS (ABAP & JAVA) to be able to communicate with the TREX? I have also updated the SLD with the latest CIM model and I'm now running out of ideas. So any suggestions would be nice.
    Thanks!

    Hello,
    As a solution part please cerify that u have to apply the same patch level in ABAP+JAVA, also identify which is the lowest level patch required by TREX to be installed on the system.
    I think the problem is in Patch level..if it is not then please follow all the procedure describe in "Installation - Search and Classification TREX Single Host.pdf" on service.sap.com
    If it helpfull to u please dont forget to reward the points..
    Thanks

  • Registration of TREX in the sld not working

    HI all,
    I need configuration the TREX for  complete instalation of xPD, but the registration on sld of trex no working, However However, I follow in the footsteps of the note 998708 and not working
    Any suggestions to solve the problem?
    Thank you

    It's the multicolored arrow in the bottom right. It has worked before today with no problems. I don't know why it just suddenly stopped working.

  • MDM - XI Issue

    Hi all,
    I have a problems setting up XI for MDM as per SAP Config Guide:
    I imported the newest CIM with XI CONTENT MDME SERVER 5.5, MDM_BUSINESS_XI, 5.5 and MDM BUSINESS CONTENT 5.5 into the sld and in the Integration Repository. However, when I want to use my MDM Business System (defined in the sld) in the Integration Builder, I do not get any MDM Interfaces (e.g. MATMAS04). Any ideas what is missing?
    Regards, Michael

    Hi Michael,
    first of all automatic creation of channel during assignment of BS will NOT create your MDM channels. You'll need to do that manually. However if templates exist, you just create a channel, then don't select anything but navigate directly to menu "Communication Channel --> Import Template". There you'll be able to select the according template which will then fill out some fields. But still there will be fields of the channel you'll need to fill manually.
    To find out what is the cause of your second problem, please navigate to the MDM Business System and doubleclick on it. Then you should see a screen with a tab Sender and a tab Receiver where all available interfaces of this system are listed. Most likely MATMAS etc are not listed there. I've checked MDM Content and MATMAS and the other IDocs are not imported to any of the MDM Software Components. So there are two options to solve the issue. Either also assign SWCV SAP APPL 4.70 to your MDM system in SLD (and make sure the according content is imported in the IR) or create your own MDM Software Component, import the IDoc Definitions there and assign this component to your system.
    Best regards
    Christine

  • Upgrade related query- Repository Update

    Hi All,
    As mentioned in the upgrade guide :
    After installation of MDM 7.1 and having started the MDM 7.1 Server use the MDM Console to update
    your repositories. Choose Update Repository from the context menu of each repository. The MDM Console then updates
    the repository so that it can be used with the latest builds. The data in the repository is automatically
    upgraded.
    But, i did the same thing but in my case after un-archiving  the repository and login in with respective correct repository credentials,Right clicking on repository the option  "Update Repository"  is not active ...How will i do this action ?how do i update the repository now ?
    ( I have tried by Loading & Unloading also )
    Please suggest !
    Regards,
    Harmony

    Hi Harmony,
    Please follow below steps :
    Steps involved in the MDM 7.1 Upgradation
    1.     Installation of MDM 7.1 in Dev Environment
    2.     Archive MDM 5.5 repository from the Production system
    3.     Unarchive the repository in the Dev system
    4.     Update repository in the Dev
    5.     Update and Test Import Maps
    6.     Update and Test Syndication Maps
    7.     Testing at the Portal level
    8.     Java API upgrade and check the custom made functionalities with API in the repository
    9.     CLIX Command Scripts need to be reworked
    10.     MDM ports to be reworked with the help of repository schema
    11.     Import the repository schema to the production environment after installation of 7.1 in production system.
    12.     Transportation from Dev to Production of JAVA API, CLIX
    Others Activities which need to be Noted/Performed
    MDM Servers
    Installed in different directory
    MDM Archive Files
    Archive files to be copied to the new directory
    MDM GUI Client
    Different Installation directory
    MDM Log files:
    5.5 Version is XML based
    7.1 version is CSV based
    MDM 7.1 doesnu2019t support the log format of 5.5 version.
    Copy the files from the u2018logu2019 and u2018report folderu2019 to an extra folder together with MDM_log.xsl, which allows viewing of logs from the browser
    Distribution Folder content
    Copy the files from the 5.5 directory to the new directory
    MDM Server Setting
    Mds.ini parameter settings to be checked.
    Some parameters are obsolete, some parameters are replaced with newer one
    MDM Import Server Settings
    Mdis.ini parameters need to be checked
    MDM Syndication server setting
    Mdss.ini setting to be checked.
    Transfer the settings of
    SLD Registration u2013 Reuse the MDM 5.5 SLD Registration
    Wily Instrumentation
    Wily Instrumentation level Threshold
    MDM Java API activities
    Deploy the 7.1 Java APIs and test the existing Java programs running for the repository
    Checking the MDM Compatability with WebSphere Portal
    Uninstallation of MDM 5.5 SP06 (Optional)
    Thanks and Regards
    Praful.

  • NEW_ITEM-SLD_SYS_NAME

    Hello ppl
    Can any one tell me the significance of NEW_ITEM-SLD_SYS_NAME item in OCI Settings .
    Why its needed?
    and
    How to do SLD of MDM System ?

    Hi Mayank Saxena 
    you can read that's guides:
    https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/e0a1a8fb-0527-2a10-f781-8b67eab16582
    https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/97abb390-0201-0010-718f-d6a0d87cb26a
    https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/500519bb-75bd-2a10-c9b7-878798ae52bc
    For registration MDM server to SLD
    you are need adding next record to mdm.ini file:
    SLD Registration=True
    Best regards

  • No hosts found in SMD Managed Sytem Setup Wizard

    Dear Experts,
    I connected a Portal system to SMD server. I manaualy defined the system in SMSY instead of SLD.
    When I went to the SMD Managed System Setup Wizard, it reported"No instances or
    servers are defined for this system. Please check its definition in SMSY before proceeding to setup".
    I've carefully checked all system definition in SMSY. I wonder if others have come across the similiar
    problem, sincerely hoping for your advice.
    Best Regards,
    Karl

    Hi, David,
    I just can't find my installed agents in SLD view. But under Agent administration Agent Tab I can see them with status green. I installed agent without registration to SLD, but user directly P4 connection.
    I tried go SMD view, I can see my agents there , and it has a column SLD settings, push SLD settings,
    I clicked to push SLD settings, but an error occured:(Failed to send SLD settings to remote agent: sapeppap01 (detail: Failed to save new SLD settings; nested exception is: java.lang.StringIndexOutOfBoundsException: String index out of range: -1).
    Best Regards,
    Karl

  • 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

  • SLD registration for TREX not working...

    SDN Members,
    I am unable to register TREX in SLD. I have put in an OSS message; however, I have yet to receive a response back from SAP... So any help would be much appreciated.
    Thanks,
    -Patrick
    Steps for the Reconstruction 
    1. Generate SLD Configuration file:
    sldreg -configure /usr/sap/TXD/TRX85/slddest.cfg
    2. Copy the SLD Config. File to the Global SLD Directory and run
    command (to transfer data to SLD):
    saposcol -b | sldreg -connectfile slddest.cfg -stdin -oldtransferdtd
    Receive the following:
    (hostnames, ip's, and ports altered to protect the innocent)
    prtdiag can only be run in the global zone
    Thu Dec 27 10:33:04 2007 SLD Registration Program [2.0]  (May  8 2006) [None Unicode]
    Thu Dec 27 10:33:04 2007 No XML data input file set. Will read input data from standard input.
    Thu Dec 27 10:33:04 2007 Supplier Name: ComputerSystem / Supplier Version: 1.0 / Supplier Vendor:  / CIM Model Version: 1.3.21
    Thu Dec 27 10:33:04 2007 Group:
    Thu Dec 27 10:33:04 2007 Group name system1
    Thu Dec 27 10:33:04 2007 validateAttributes OK
    Thu Dec 27 10:33:04 2007 Property Status
    Thu Dec 27 10:33:04 2007 Value OK
    Thu Dec 27 10:33:04 2007 Property NameFormat
    Thu Dec 27 10:33:04 2007 Value IP
    Thu Dec 27 10:33:04 2007 Property Caption
    Thu Dec 27 10:33:04 2007 Value hostname01
    Thu Dec 27 10:33:04 2007 Property Name
    Thu Dec 27 10:33:04 2007 Value usahstxutxd01
    Thu Dec 27 10:33:04 2007 Property IPAddress
    Thu Dec 27 10:33:04 2007 Value X.X.X.X
    Thu Dec 27 10:33:04 2007 Property OpSysReleaseName
    Thu Dec 27 10:33:04 2007 Value SunOS
    Thu Dec 27 10:33:04 2007 Property OpSysCategory
    Thu Dec 27 10:33:04 2007 Value Solaris
    Thu Dec 27 10:33:04 2007 Property VendorRelease
    Thu Dec 27 10:33:04 2007 Value SunOS 5.10
    Thu Dec 27 10:33:04 2007 Property CPUType
    Thu Dec 27 10:33:04 2007 Value sun4v
    Thu Dec 27 10:33:04 2007 Property MachineCategory
    Thu Dec 27 10:33:04 2007 Value SPARC
    Thu Dec 27 10:33:04 2007 Property OpSysBits
    Thu Dec 27 10:33:04 2007 Value 64
    Thu Dec 27 10:33:04 2007 Property NumberOfCPUs
    Thu Dec 27 10:33:04 2007 Value 32
    Thu Dec 27 10:33:04 2007 Property CPURate
    Thu Dec 27 10:33:04 2007 Value 1200
    Thu Dec 27 10:33:04 2007 Property PhysicalRAMInMB
    Thu Dec 27 10:33:04 2007 Value 65528
    Thu Dec 27 10:33:04 2007 Property VirtualRAMInMB
    Thu Dec 27 10:33:04 2007 Value 87224
    Thu Dec 27 10:33:04 2007 Using connect file 'slddest.cfg'.
    Thu Dec 27 10:33:04 2007 No key file 'slddest.cfg.key' used.
    Thu Dec 27 10:33:04 2007 HTTP trace: false
    Thu Dec 27 10:33:04 2007 Data trace: false
    Thu Dec 27 10:33:04 2007 Using connect file 'slddest.cfg'.
    Thu Dec 27 10:33:04 2007 No key file 'slddest.cfg.key' used.
    Thu Dec 27 10:33:04 2007 *** Start SLD Registration ***
    Thu Dec 27 10:33:04 2007 Used URL: http://hostname01:50000/sld/ds
    Thu Dec 27 10:33:04 2007 HTTP open status: true - NI RC=1
    Thu Dec 27 10:33:04 2007 HTTP send successful.
    Thu Dec 27 10:33:04 2007 Return code: 401 --- Return message: (Unauthorized)
    Thu Dec 27 10:33:04 2007 HTTP response: Failure. HTTP status code: 401
    Thu Dec 27 10:33:04 2007 *** End SLD Registration ***
    Thu Dec 27 10:33:04 2007 Data send status: false
    Consequently SLD is not updated with TREX information. Using IE I can go to
    the url http://hostname01:50000/sld/ds , get popup asking for
    credentials (we log in using SLDDSUSER account - w/ Basis Admin level
    auth.), and we receive: Page Cannot be displayed (HTTP 400 - Bad Request
    Internet Explorer ).
    If we go to http://hostname01:50000/sld and login with the same
    account (SLDDSUSER) we see the full SLD Toolset.
    Edited by: Patrick Riggins on Dec 27, 2007 6:06 PM

    UPDATE:
    We were able to work through and
    resolve the error we initially posted in this Thread. Now we run sldreg
    and all looks good; however, we are seeing nothing in SLD (on our XI
    System) even after stop/restart of SLD Server:
    Steps for the Reconstruction 
    1. Generate SLD Configuration Files:
    sldreg -usekeyfile -configure /usr/sap/TXD/TRX00/slddest.cfg
    2. Copied files to Global SLD
    /sapmnt/TXD/global
    3. Run command to transfer data to SLD:
    saposcol -b | sldreg -user <user acct> -pass <password> -host
    <hostname> -port <port #> -datatrace -httptrace -
    logfile /usr/sap/TXD/TRX00/sld_reg.log -stdin
    Looks successful:
    Thu Dec 27 20:31:06 2007 HTTP body length: 0 --- HTTP body: empty
    Thu Dec 27 20:31:06 2007 Return code: 200 --- Return message: (OK)
    Thu Dec 27 20:31:06 2007 HTTP response: Success. HTTP status code: 200
    Thu Dec 27 20:31:06 2007 *** End SLD Registration ***
    Thu Dec 27 20:31:06 2007 Data send status: true
    However in SLD , under content maintenance selecting "All With
    Instances" in the dropdown list and "Class" , no TREX Services showing.
    And no technical system showing for TXD (TREX System)

  • Registration of Business system for the Integration Engine Java in the SLD issue

    Hi,
    We have completed the installation of PI-AEX 7.4 SR1 then we ran the below wizards successfully.
    - Configuration Wizard: PI-AEX initial setup
    - Configuration Wizard: PI Self Test for AEX
    However when we were Checking the AEX Configuration as per help.sap.com
    Check the registration of a business system for the Integration Engine Java in the SLD:
        Enter https://<host>:<port>/sld .
        Choose Start of the navigation path Business System Next navigation step Integration Engine Java <SID> Next navigation step Integration End of the navigation path.
        The pipeline URL must be: http://<host_fully_qualified>:<port>/XISOAPAdapter/MessageServlet?ximessage=true .
    More information: SAP Note 1435392
    for us the Pipeline URL is as below
    http://<host_fully_qualified>:<port>/XISOAPAdapter/MessageServlet
    and the rest " ?ximessage=true "  is not there.
    Also we ran the below wizard
    Configuration Wizard: PI Self Test for AEX
    and it finished successfully without any issue.
    Any Suggestions what could be missing.
    Thanks,
    Regard
    Ahmed Mohammed

    Hi,
    I found the below SAPNOTE which confirms that the Pipeline URL should be
    http://<host_fully_qualified>:<port>/XISOAPAdapter/MessageServlet
    1564449 - PI CTC Wrong Pipeline Url after AEX Initial Setup
    However on help.sap.com it is different.
    Any one experienced the same ?
    Regards
    Ahmed Mohammed

  • Registration of PI components in SLD

    PI 7.0 server was setup successfully on wid 2003/oracle, after all the post configuration steps. Am not able to see the PI structures under technical systems -> exchange infrastructure in SLD. I can only see Adapter ENGINE, Integration server and Doamin, but not IR, ID, RWB.  .
    SLD is running on the same PI server.Exchange profile and all the related PI users and passwords are fine
    Have gone almost all the related threads in the forum, implemented teh note 1117249 but no luck.
    Requesting to experts to give me a roadmap to troubleshooting furhter.
    Thanks,
    Durga

    Hi Durga,
    I am not sure once the PI7.1 system will be ready by BASIS Team (with EHP1) with the required specificaiton ,what steps need to follow to configure the SLD components like SWCV,PRODUCTS etc?
    And who should perform the registration of PI component and if client doesnt know about the specification needed to PI components then who should provide this?
    Will it be responsibility of PI BASIS adminitstrator or Infrastrutre Management Guy?
    Thanks for help!!
    Pushkar

Maybe you are looking for