SLD configuration for NW04s EP7

Hello,
Is there any step by step procedure to configure SLD for NW04s EP7.
Backend system is ECC6
*Points will be awarded based on answer

Mickey,
Still I am facing problem.Please send me configuration document to the following E-Mail ID
[email protected]
I will give you points once I received you E-mail
Thanks in advance

Similar Messages

  • Sld configuration for rfc to soap scenario

    Hi all,
    The scenario which i am planning to do, describes how the Custom RFC client application in SAP R/3 System invokes a free Web service (that is hosted over the internet) using SAP XI. For our demo purpose, we have used a free web service available on the Internet.
    In this scenario we will be using “GetQuote” method of Web service “DelayedStockQuote”. This method retrieves the Stock quote for the given Stock symbol. The method “GetQuote” has an input that takes in two parameters Stock Symbol and License Key and returns the following information.
    StockSymbol,
    LastTradeAmount,
    LastTradeDateTime,
    StockChange,
    OpenAmount,
    DayHigh,
    DayLow,
    StockVolume,
    PrevCls,
    ChangePercent,
    FiftyTwoWeekRange,
    EarnPerShare,
    PE,
    CompanyName.
    Link to web service:
                http://ws.cdyne.com/delayedstockquote/delayedstockquote.asmx?op=GetQuote 
    In this scenario, I planned to create two mappings, first between RFC Request  to SOAP Request  and second between SOAP Response to RFC Response .
    Adapter in sender communication channel is RFC.(RFC  Protocol)
    Adapter in receiver communication channel is SOAP.(HTTP Protocol)
    Result:
                On testing this scenario, In the Sender R/3 system  we have to Execute the Report program we have created earlier. When the program is executed with Stock symbol it should get the details of that stock symbol from the Web service.
    My question here is what would be the sld configuration for webservice.whether it is a Java WAS or third party.If it is a third party or java WAS,what would be the system name and host name.
    Any clarification from you all is welcome and will be highly appreciated.
    With Regards
    Karthik.

    Hi,
    I would suggest you is to use third party. It is a web service, and does not matter the technology behind it (if it is java, abap, .net, cobol, no difference! it will be described by a wsld).
    System name and host name doesn't matter too, you will not use this information in runtime, and you will specify host name and so at integration directory. You can make your standard on it, for example, put the name as DelayedStockQuote and host as http://ws.cdyne.com.
    regards.
    roberti

  • SLD configuration for DXI / PXI technical systems

    Hello,
    we have a problem when transporting XI configuration objects from XI dev to XI prod. The transport objects arrive in XI prod, but the name of the business system (for the SAP backend system) is not converted from dev business system (T01CLNT010) to prod business system (P01CLNT01) although the transport target for T01CLNT010 business system was set correctly (we are using business system groups Dev and Prod). And the "related integration server" for T01CLNT010 was also set correctly to DXICLNT010.
    But then I noticed that the technical system for the DXI (XI Dev) is configured as follows:
    TMS Domain ("DOMAIN_PXI") and TMS Transport Group Name GROUP_PXI ("GROUP_PXI") have the same values as PXI. Is that correct ?? We are using file transport, not CMS.
    Another strange effect is that when I set the group in business system DXICLNT010 to Dev, that is also applied to business system PXICLNT010 ! Which is of course not what I want.
    I assume I have to associate DXICLNT010 to Dev and PXICLNT010 to Prod, same as for T01CLNT010 / P01CLNT010. Correct ? Or does the group in the XI business systems not matter ?
    Can anyone post an example of a working SLD configuration with two XI system dev and prod ? What values do I have to use in the XI technical and business systems, so that the transport will work ?
    CSY

    There's obviously something wrong in the SLD configuration for the exchange infrastructure systems. The error you're describing (one system pointing to another) usually occurs when one system is generated through homogeneous system copy of another system (was that your case?). I've seen that behaviour once and they corrected it by manually deleting the exchange infrastructure systems from SLD and creating them again from scratch.
    Anyway, I highly recommend you to get an expert NW Basis consultant to realize a check in it before you proceed any further.
    Aside of that, you're correct in your assumptions.
    Your config in SLD should be like:
    DEV_GROUP:
    - DXI
    - T01
    PRD_GROUP:
    - PXI
    - P01
    It's always 1 XI BS per group.
    Also, if you use separate SLDs for XI Dev and XI Prd, you have to make sure that this configuration is reflected in both SLDs. So, if you make it one SLD instance, you must generate a delta export zip file from the SLD where you did the configuration and import this zip file in the other SLD instance.
    If you use a central SLD, then it's not necessary.
    Regards,
    Henrique.

  • SLD Configuration for WEB As JAVA

    SDN TEAM,
    PLease can you send the screen shots for configuring SLD for WEB AS Java
    For valuable answer definity i will reward points
    Regards'
    CHANDU

    Hi,
    Fisrt you have to define a technical system in SLD
    using the URL
    http://<host>:<port>/sld u2192 Link Technical Landscape
    there you have select under landscapes---->technical systems
    select new technical system.
    select the server either (web As ABAP.Web AS java)what ever is ur server select it.
    next u have another screen
    asking SID,Installation no.,Database host name.
    For all the details webas abap.
    you can view after looging in the option in the menu bar system->status.
    next
    Enter the message server host, application server host, the instance number, the
    message server port and all logon groups.
    On the next screen you can add the name of all application server hosts (and their
    instance numbers) belonging to the same SAP system. Press Next.
    Now enter all clients, you want to use with the JCo connections. At least one
    client has to be defined
    Thnaks & Regards,
    Lokesh.
    If you have any doubts.
    please let me know

  • SLD configuration for R/3 system

    hi all
    i want to configure SYSTEM LANDSCAPE DIRECTORY for my R/3 system.
    kindly suggest steps for same.
    gud suggestions will b rewarded.
    thanx

    Hi Chetana,
    Refer to the following links:
    http://help.sap.com/saphelp_nw70/helpdata/EN/43/01ea90ab24235de10000000a1553f7/content.htm
    create System in EnterprisePortal
    Thanks n Regards,
    Jhansi Miryala

  • Reg : Initial configuration for SLD

    HI all ,
    In the netweaver administration portal we have a option for deploy and change .when we click on that we have some options for initial configuration.Now the doubt that i have is that we have installed netweaver java stack on a server .We have configured local sld on that .We want to connect to a seperate ECC 6.0 system.That system doesnt have a sld configured for it .So we want to bring that system into our sld.I have configured NWA_01 i.e .configuration for local sld and NWA_03 i.e. create a connection to the SLD and Setting required authorizations for SLD (CIM client settings) in netweaver administrator portal.Do i need to configure only these or anything else other than this .One more thing is that when i enter the netweaver administrator portal i am getting these error messages.
    System Landscape Directory is not accessible
    Only local system can be administered
    Any pointers regarding this.Thanx in advance .

    Hi there,
    The java stack is installed as standalone or ABAP+Java?
    You need to maintian SLD server details in RZ70 on ECC server and test if data is sent successfully. Check for RFCs SLD_UC/SLC_NUC in ECC.
    Also, check if SLD server is running.
    regards, Sean.

  • SLD configuration in already existing Solman system

    Hello,
    We already have dedicated central SLD in our landscape but now we want to configure SLD in already existing SOLMAN and decommission the existing one.
    Can anyone suggest how to configure SLD in already installed SOLMAN (may be high level step by step process)?
    Thanks & Regards,
    NK

    Hi Nitin,
    What will be the purpose of SLD of solution manager ?
    eg. 1631346 - Solution Manager 7.1: SLD configuration for PI monitoring
    You can add this SLD with a higher rank than the older SLD but lower than LMDB in solman_setup.
    Refer:Step By Step Process to configure SLD, MOPZ & EWA in Solution Manager 7.1 SP 8
    https://help.sap.com/saphelp_sm71_sp05/helpdata/en/a5/971735dd184f5c8d943c6cf423d13a/content.htm
    Divyanshu

  • J2EE SLD Configuration (NW04s ABAP+J2EE)

    Hi,
    I have just installed NW04s BI System with ABAP + J2EE (SP13).
    We have a SLD running on SolMan 4.0 (SP13) which is a different host.
    I have configured the ABAP part of the SLD for NW04s BI System and it is working fine.
    I have no idea how to configure the J2EE side of it.
    The only thing I have defined is a Business and Technical system for J2EE in our SolMan SLD for our BI.
    I do not know how to proceed for J2EE of our BI system. I have found few links but kind of confused.
    Can anyone please give me exact steps I need to configure. I do not need detail but just a sequence of steps.
    I will appreciate your help.
    Regards.
    SSingh

    Thank you for the reply. It helped.
    My goal is to creat the BI system as a Application System in SXMB_ADM. I have done the ABAP part including the destinations SAPSLDAPI, LCRSAPRFC and SLD configuration. They are working fine as I said in my message.
    Now from the J2EE side, the only thing which is required is what you said.
    Is that enough to make make the J2EE also a Application System or more needs to be done once J2EE is SLD ready. I know that J2EE should also be craeted as a Business and Technical in SLD. That part is done.
    Please respond.
    Regards.
    SSingh

  • SLD Configuration - Technical System and Business System

    Hello,
    I have installed SAP Solution Manager with local SLD and i want to use this system as Central SLD for my System Landscape. Later on i have installed other SAP Products like ECC,BI,PI etc.
    Some of the systems i registered with previously defined SLD in Solution Manager, but some system i forgot to register with SLD during installation.
    I am not sure or aware what is the difference between SLD configuration during installation and after installation.
    If i have Register the System during installation will it register automatically with SLD or we have to do manually.
    If i have not register system during installation and later on i want to register particular system with SLD what is procedure for that.
    Can some one share knowledge on What is Technical Systems and Business System in SLD Configuration, i tried to do some activity for SLD Configuration but after seeing above both terms i was confused so for time being i stopped this activity.
    Looking forward for kind response.
    Best Regards,
    V.Singh

    Hello
    try to go through these
    http://help.sap.com/saphelp_nwesrce/helpdata/en/45/4208934d7f1193e10000000a1553f7/content.htm
    https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/652b1f46-0a01-0010-25ae-e7cb07b55414

  • Prerequisites to configuration for ABAP Proxy -???

    My scenario is file->XI->R/3(abap server proxy).
    Xi and R/3 are 2 seperate business systems
    -Abap server proxy created on R/3 business system. R/3 client 550
    -Xi client 400.
    -SLD is common for both XI and R/3
    <b>My question is in reference to the below message thread:</b>
    <b>1.I  understand all the below configuartaion has to be done on R/3 business system, tell me am I correct</b>
    <b>2. are these configuartion needed for <u>client proxy as well as server proxy</u> also?</b>
    HTTP_RESP_STATUS_CODE_NOT_OK
    The prerequisites to configuration for ABAP Proxy include: (landscape dependent)
    1. The business systems should be based on SAP Web AS 6.20 and SAP Web AS 6.20 kernel patch level above 1253
    2. You have installed the XI Add-On in each of these business systems as described in the Installation Guide SAP Exchange Infrastructure 3.0
    3. The business systems and your central Integration Server are maintained in the System Landscape Directory (SLD).
    Configuration required on the Business System:
    1. Create HTTP connection in the business system.
    Configuration Details:
    Technical Setting:
    1. Following Inputs are required for technical setting
    1 Connection Type: H
    2 Target Host: System name
    3 Service Number: HTTP Port name
    4 Path Prefix: /sap/XI/engine/?type=entry
    Logon Security
    On the Logon/Security tab page, enter the following logon data:
    1 User: XIAPPLUSER (for example); this user should represent the sending business system (see also the SAP XI Security Guide under Service Users for Message Exchange).
    2 Password: the password you have specified for this user
    3 Client: SAP XI Integration server
    4 Language: Language required
    2. Configuration Business system as local Integration Engine.
    1. Goto Transaction SXMB_ADM
    2. Choose Edit --> Change Global Configuration Data.
    3. Select Role of Business System: Application system
    4. Corresponding Integration server: dest://<HTTPDESTINATION>. Here <HTTPDESTINATION> SAPISU_XID created in step 1. Dest://SAPISU_XID.
    5. Under Specific Configuration Data you can specify additional configuration data
    1.Select the relevant category under Specific Configuration Data.
    2.Choose Change Specific Configuration Data.
    For ABAP Proxies, Add the following configuration:
    1.Category RUNTIME
    2.Parameters: IS_URL
    3.Current Value: dest://SAPISU_XID
    Configuration of the Integration Engine
    3. Connection between Business System and System Landscape Directory
    1. Create RFC destination (TCP/IP) LCRSAPRFC and SAPSLDAPI for the SLD connection.
    1.Execute transaction SM59 in the business system.
    2.Choose Create.
    3.Enter at least the following:
    1.RFC Destination: LCRSAPRFC
    2.Connection Type: T
    3.Description: <your description>
    4.Choose ENTER.
    5.Choose the Technical settings tab page and do the following:
    6.In the Program ID field under Registered Server Program, enter LCRSAPRFC
    7.This program ID must correspond to a program ID specified in the RFC engine settings of the SAP J2EE Engine on the Integration Server host.
    RFC Destination
    2. Maintaining the SAP J2EE Connection Parameters for LCRSAPRFC and SAPSLDAPI in SAP J2EE engine
    1. Goto J2EE Engine
    2. Choose Cluster --> Server --> Services. JCo RFC provider
    3. Under RFC destination specify the following:
    Program ID: LCRSAPRFC
    Gateway Host: <Integration Server host>
    Gateway Service: <Integration Server gateway service>
    Number of process: 3
    4. Under Repository specify the following:
    Application Server: <Integration Server host>
    5. Choose Set.
    3. Maintain SLD access details in Transaction SLDAPICUST
    1. You can reuse this program ID for all Business systems
    2. If there is HTTP error during connection, first run transaction SLDCHECK in the Business system. Also check that HTTP connection is working fine.
    3. In XI Adapter use HTTP connection rather then giving R/3 input details as this is easier to transport and maintenance
    4. One receiver adapter can be used for all Interfaces connecting to a Business system.
    <b>Thanks for your reply in adavnce.</b>
    KK

    2. are these configuartion needed for client proxy as well as server proxy also?
    >>>>
    the configuration is one time thing and your R3 will act as a server or client according to the data being sent or received.
    In R3 a point to be noted is that in SXMB_ADM -> Intg. Engine Confg. -> Role of Business System sud be as a Application System.
    Ref: /people/vijaya.kumari2/blog/2006/01/26/how-do-you-activate-abap-proxies
    Message was edited by: Shabarish Vijayakumar

  • IDoc receiver AEE: Error "Configuration for Sender/Receiver Partner Number/Port is incorrect"

    Hi all,
    We are on PI 7.4 AEX SP 7. We are trying to get the following scenario working: Inhouse warehouse management system (JMS) --> PI --> ECC (IDoc)
    Sender is configured as 3rd party technical system system with business system maintained in SLD
    business system has logical system assigned in SLD
    adapter specific identifiers show logical system in ID / NWDS
    logical system is defined in receiver (ECC system)
    partner profile is created in ecc for this very logical system (inbound parameters)
    No mapping of EDI_DC40 node in ESB (complete node disabled)
    no header mapping in ID / NWDS
    receiver IDoc AEE adapter is configured to not enforce control record (Control Record in IDoc XML = Not Mandatory)
    no Identifiers specified in receiver IDoc AEE adapter
    My guts feeling is that this should work, however, it doesnt't. Failing with "The Configuration for Sender/Receiver Partner Number/Port is incorrect. Enter proper values in Sender/Receiver Component"
    Any thoughts are highly welcome.
    Cheers
    Jens

    Hi,
    The error mentioned by you is not related to the port..but its related to the Application ...
    IDoc 51 means idoc has been received in R/3 client and when it tries to process it ended in error..
    Check with the functional consultant for the error you have received..
    HTH
    Rajesh

  • 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)

  • ALE configuration for Outbound Idoc - Help me

    Hi Experts,
    I am newbee in SAP and XI. I was trying to send MATMAS Idoc from R3 and i was running into some issues. So i would appreciate if someone can help me.
    I am using following link as reference. /people/swaroopa.vishwanath/blog/2007/01/22/ale-configuration-for-pushing-idocs-from-sap-to-xi
    I did all the steps mentioned in the above link ( Creating Logical Systems, Assigning Client and RFC destnations, Creating distribution models ..... etc)
    and then everything went well and i saw success messags in all the steps.
    I used BD10 to send material and it went well. But when i check TRFC queue, i see some error messages; "<i><b>No service for system SAPRDI, client 800 in Integrion Directory</b></i>"
    And all the messages are hanging in the TRFC queue.
    Note: I havent configured anything in XI yet. I wanted to make sure IDoc gets to XI client first.
    Thank you in advance. Pls help me its very urgent.
    Thanks,
    Surya

    I created RFC destination (SM59) and Port (IDX1)
    Then i sent another material (BD10)  and checked tRFC queue. i found bunch of error in the Queue.
    <b>1.connection to host 10.4.23.120, service sapgw00 timed out / CPI-C error C
    No service for system SAPRDI, client 800 in Integration Directory
    partner not reached (host 10.16.176.29, service sapgw00) / CPI-C error CM
    connection to host 10.16.136.127, service sapgw58 timed out / CPI-C error</b>
    Note: i have noticed entries for R3 in SLD as below
                      System Name:  <b>RDI </b>  ( not <b>SAPRDI</b> as mentioned in the error message)
                      System Home:  r3ides
    That might be reason. If so, how to change it in R3 box? Any suggestions?
    Please send me if you guys have any links or docs to address this issue.
    Thanks,
    Surya

  • CTS+ configuration for NWDI - Development configuration error

    Hi All,
    I really need some help on this. we are configuring CTS+ on Solution Manager system for NWDI, EP landscape (EPD, EPQ,EPP) and SLD system.
    we made EPD as development system and trying to use CM Services to configure the NWDI scenario SDA/SDC Deployment.
    I have created all NON-ABAP systems and created the CTSDEPLOY Http connections. I am getting the popup to configure the Development Configuration,"What is the User I have to use here and  of which system?" and what are the authorizations required to configure this.
    As soon as the popup comes, It is asking for the user ID and Password. I am entering Solution Manager (Admin user with all CMS actions also assigned) user then it is giving the following error on the screen. " Could not connect to SLD; contact your System Administrator: User SAPNWDI is not allowed to do this function "
    I have give the SLD url correctly, and the admin user for SLD and Password. I have cross checked the user for password, every thing is fine.
    I really appreciate your help.
    Thanks,
    Ramu J.

    http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/90d3b550-b6fb-2910-0fa5-ece5d61fb9c3
    Hi Ramu,
    Pls answer me for below.
    specified SLQ as my SLD
    1.
    You said SLQ is you SLD, but You configuring CTS on solution manager. but solution manager has its own SLD.
    a. SMG solution manager SLD
    b. SLQ is also SLD
    If there is two sld then you should get error
    " Could not connect to SLD; contact your System Administrator: User SAPNWDI is not allowed to do this function "
    This is becuase you are giving the user which is present in SLQ SLD but CTS is checking the Solution manager SLD.
    For CTS you should have centralied SLD.
    2.
    Can you tell me one more thing, in CTSDEPLOY do I need to give the SMG host and port number or EPD's host and Port number?
    You have to specify the host and port in CTSDEPLOY of the system on which CTS contoller should work i.e EPD or SMG.
    To resolve your all this problem first of all make the SLD as central . i.e Make solution manager ( CLQ ) as SLD or SLD system in you landscape ( SLQ ) as SLD.
    don't keep two different SLD . If you keep Solman as its own SLD then CTS will search component from SMG SLD
    Pls follow the guide
    http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/90d3b550-b6fb-2910-0fa5-ece5d61fb9c3
    3.
    Could not connect to SLD; contact your System Administrator: User SAPNWDI is not allowed to do this function
    Can you tell us in which system this SAPNWDI user is present
    Check the SLD of of system in which SAPNWDI user  i present
    system is whether in SMG SLD or SLQ SLD
    If you are not clear with my above suggestion pls let me know.
    Thanks
    Anil
    Edited by: Anil Bhandary on Oct 24, 2009 10:28 AM

  • Recommended SLD setup for NWDI

    I have been looking at the SLD planning guide and noticed a few scenarios listed there. Does anyone here have recommendations.
    The one that looked good to me was the 2 SLD (1 for DEV and QAS) with NWDI connected, and another (1 for PRD).
    I was wondering if NWDI is only connected to a non prod sld, will this be a problem when you want to migrate objects to production?
    Also from what I gather in this guide, it appears that NWDI can have its own SLD. Are there any advantages/disadvantages to this?
    Thanks

    Hi
    > I was wondering if NWDI is only connected to a non
    > prod sld, will this be a problem when you want to
    > migrate objects to production?
    No this will not pose an issue, the NWDI uses the SLD only during the configuration process. Deployments are done independant of your SLD configuration.
    > Also from what I gather in this guide, it appears
    > that NWDI can have its own SLD. Are there any
    > advantages/disadvantages to this?
    Yes this is an option too. Although this does not remind me of any advantages, other than the ease(to a very samll degree) of configuration.
    > Thanks
    Regards
    Pran

Maybe you are looking for