SLD in a central insance

Hello experts, my question is about where to direct the SLD when you are configuring the Solman, right now we are doing the initial configuration (in a DEV instance), and we are ponting the SLD to the Netwaver Portal (DEV) but for some problems we got to reintall the Portal so I would like to know what is better for an organization? pointing the SLD to the Portal (DEV)?, Portal (PRD)? or to the Solman itself?.
(Some time ago a SAP consultant told us to point the SLD to the Portal)
Thanks for your answer,
Paul Hurtado

Hello there
What Mateus says is correct where you point and locate your SLD depends on the landscape
and how the SLD will be used
The SLD that is used by Solution Manager or is on the Solution Manager J2EE is traditionally the central SLD
- containing all systems from all sources (data suppliers, other SLDs etc)
You should be careful doubling up SLD useage - i.e have more than one client like Solution Manager and XI using
the same SLD - some applications like XI require the SLD for runtime (at least this is generally the thinking although
it could also be that clients have specific requirements that may conflict with each other) and thefore need a local
dedicated SLD. To give you an example -->
Solution Manager J2EE might be allowed to be brought down or restarted whenever required - there is maybe only a small user group notified or affected if however you using Solution Manager J2EE SLD for XI purpose - the consequences of this flexible downtime policy for XI could be severe
Best wishes
Stuart

Similar Messages

  • Migrate local SLDs to a centralized SLD

    We are in a big SAP project with one full landscape for each new SAP product (e.g. SRM, ECC, EP, BI, etc.)
    We have a centralized SLD on a SM7.0.
    We have 2 options when installing each system:
    1) use the centralized SLD for each new install
    2) use the local SLD for each new install, then change all local SLDs to the centralized SLD.
    What will be the pros and cons of each option?
    Thanks!

    Hello Linda,
    Eventually ,you want to register your systems to the central SLD.
    You can do it in both ways,but during installation when you select the option of Configure a Local SLD SAPinst says that it will take longer time ,thats it no other issues.
    So best is that you register your systems to Cenral/Remote SLD.The remote SLD should be running and available at that time.
    Have a look at this blog /people/boris.zarske/blog/2008/03/21/sld-general-recommendation-how-to-set-up-the-system-landscape-directory , it will give you more wider view of planning the SLD.
    Regards
    Ajay

  • Local sld pull from central sld

    We are in the process of configuring a brand new sp19 solution manager server. We have a central sld on a dedicated server with several systems already registered on it  I created a local sld on the new solution manager server. I want to pull the systems from this central sld server into the solution manager server, but cant' seem to find any documentation on how to do it.
    I've read the SLD planning guide, the sld post-installation guide,, and the sld user guide. If there are any steps that document how to do this, I've missed them.
    Can anybody help?
    --Carl

    On your central SLD: Administration -> Data Suppliers -> Add SLD...
    Type in URL, valid user and pass and that should be it. It works this way on SLD based on NW70.

  • SLD Local to Central

    Hi,
    We are planning to install a NW2004s system for the use of EP. During installation we had configured the system to use "Local SLD". How do we configure this system to use our "Central SLD" ? Please point to some documentation.
    Cheers!!

    Hi Rao
    I have already replied to r question in NEtweaver Platform forum.Kindly do not put same question in different forums:
    Below was my reply:
    I will tell you few steps to hook ur EP system to Centrel SLD.
    1.Go to visual administrator of EP( java system)--instance-serverservices-----SLD data supplier
    2.Put the details of ur centrel SLD there in http settings.I mean the server name,user who has admin rights for ur central sld.
    3.Click on the save button.
    4.Perform the same steps in CIM client generation settings
    5.You can check ur configuration by clicking on CIMClient Test.
    6.If everything is correct ,you will get successfull pop up window.
    7.Then trigger the data transfer by clicking a blue colour arrow.This will trigger ur EP data to the central SLD.I mean they both can talk now.
    8.Then you can also go to ur central SLD,and search for your EP instance,it will be listed there.
    In case you face any issues let me know.
    Reward with suiatble points

  • Local SLD and Central SLD

    Hi,
    Can we still change Local SLD to Central SLD after the installation has been done?
    Rgds,
    Hapizorr Rozi Alias

    Hello Rozi/Naveen,
    Yes u can change the SLD configuration from central to local or a vice versa...
    Please check the following SAP Note for u r ready reference
    Note 720717 - Reduce the number of System Landscape Directories (SLD)
    If usefull then give  reward point..
    Thanks

  • Central SLD Configuration

    Dears,
    Recently we installed PI DEV and PI QAS server.At time of configuration we choose local SLD option for configuration.
    But now we are getting requirement to configure central SLD.
    So please confirm which strategy is good between them and if it is central SLD,Please suggest the
    procedure to change local SLD configuration to central SLD.
    Shivam

    Hi Shivam
    The SLD planning guide provided previously is the key source to plan, implement and run an SLD landscape
    However what it may not deal with specifically is changing an existing SLD landscape to accomodate a local PI specific
    SLD and a new Central SLD for Solution Manager (or other purposes)
    Some things to consider when selecting Sync options
    1) 1 Dual purpose SLD is not recommended - a central SLD might have different administration requirements than a PI specific SLD
    2) Where possible do not change established import or export lines in either SLD
    3) Keep all SLDs involved in the sync at the same J2EE version, SP landscape and CIM model/content
    As the PI SLD can be productive critical - full consideration has to be given to this SLD as you can
    still maintain systems manually in a central SLD manually - or indeed in Solution Manager itself (both manually and automatically via RFC) - therefore I would recommend a unidirectional sync from local PI SLD to Central SLD of PI landscape data only - either manually or automatically or indeed explore any available options to have data suppliers update both SLDs (there was some options similiar to this in older SLD versions - but I am not completely familiar with the latest SLD builds)
    I would not however encourage full sync or CIM based sync as there maybe established CIM import lines on either SLD nor would I specifically encourage the Central SLD to influence data on the Local existing PI SLD
    Best wishes
    Stuart

  • Non Central adapter engine error

    Hi All, Here is my Scenario: Trying implement /configure Non-central adapter engine hosted separate (J2EE) server. This will be connected to XI server(Integration engine and SLD) from where messages are sent/received. When I try to post message from XI to Non_central adapter engine following is the message u201CThe requested protocol u201CXIu201D is currently unavailableu201D Then I realized there is a problem in Non-central adapter engine configuration, which will be connected to SLD and Integration engine. I can see technical system and business system in SLD for Non-central adapter engine. Following is the findings in NWA of same host where non-central adapter engine. 1) I see all J2EE services are running 2) Application u201Ccom.sap.aii.adapter.soap.libu201D is no started and status is u201Cfailed to startu201D. Later I tried to restart and following are the 4 error messages in sequence from trace file. a) Message: Access to XI AF MS resource failed. Date: 2010-07-02 Time: 22:05:15:273 Category: com.sap.aii.adapter.soap.ra.SPIManagedConnectionFactory Location: com.sap.aii.adapter.soap.ra.SPIManagedConnectionFactory.SPIManagedConnectionFactory() Application: Thread: Deploy Start Application Thread Data Source: j2ee\cluster\server0\log\defaultTrace_00.trc B) [ERROR CODE DPL.DS.5029] Exception in operation [startApp] with application [sap.com/com.sap.aii.adapter.soap.lib]. [EXCEPTION] com.sap.engine.services.deploy.exceptions.ServerDeploymentException: [ERROR CODE DPL.DS.5029] Exception in operation [startApp] with application [sap.com/com.sap.aii.adapter.soap.lib]. at com.sap.engine.services.deploy.server.application.ApplicationTransaction.rollbackPart(ApplicationTransaction.java:619) at com.sap.engine.services.deploy.server.application.StartTransaction.rollbackPart(StartTransaction.java:653) at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:506) at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesImpl(ParallelAdapter.java:483) at com.sap.engine.services.deploy.server.application.StartTransaction.makeAllPhasesImpl(StartTransaction.java:584) at com.sap.engine.services.deploy.server.application.ParallelAdapter.runMe(ParallelAdapter.java:180) at com.sap.engine.services.deploy.server.application.ParallelAdapter.access$000(ParallelAdapter.java:43) at com.sap.engine.services.deploy.server.application.ParallelAdapter$1.run(ParallelAdapter.java:340) at com.sap.engine.frame.core.thread.Task.run(Task.java:73) at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:175) at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:274) Caused by: com.sap.engine.services.connector.exceptions.BaseDeploymentException: Cannot bind "com.sap.aii.adapter.soap.lib";. at com.sap.engine.services.connector.deploy.util.ResourceAdapterStarter.instantiateMCF(ResourceAdapterStarter.java:393) at com.sap.engine.services.connector.deploy.util.ResourceAdapterStarter.initResourceAdapter(ResourceAdapterStarter.java:122) at com.sap.engine.services.connector.deploy.ConnectorContainerImpl.prepareStart(ConnectorContainerImpl.java:303) at com.sap.engine.services.deploy.server.utils.container.ContainerWrapper.prepareStart(ContainerWrapper.java:363) at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:251) at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:209) at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:502) ... 8 more Caused by: com.sap.engine.services.jndi.persistent.exceptions.NameAlreadyBoundException: Object with name com.sap.aii.adapter.soap.lib is already bound. at com.sap.engine.services.jndi.implserver.ServerContextImpl.bind(ServerContextImpl.java:343) at com.sap.engine.services.jndi.implclient.ClientContext.bind(ClientContext.java:850) at com.sap.engine.services.jndi.implclient.ClientContext.bind(ClientContext.java:695) at com.sap.engine.services.jndi.implclient.ClientContext.bind(ClientContext.java:912) at com.sap.engine.services.connector.deploy.util.ResourceAdapterStarter.bind(ResourceAdapterStarter.java:487) at com.sap.engine.services.connector.deploy.util.ResourceAdapterStarter.instantiateMCF(ResourceAdapterStarter.java:375) C) Cannot bind "com.sap.aii.adapter.soap.lib";. [EXCEPTION] com.sap.engine.services.connector.exceptions.BaseDeploymentException: Cannot bind "com.sap.aii.adapter.soap.lib";. at com.sap.engine.services.connector.deploy.util.ResourceAdapterStarter.instantiateMCF(ResourceAdapterStarter.java:393) at com.sap.engine.services.connector.deploy.util.ResourceAdapterStarter.initResourceAdapter(ResourceAdapterStarter.java:122) at com.sap.engine.services.connector.deploy.ConnectorContainerImpl.prepareStart(ConnectorContainerImpl.java:303) at com.sap.engine.services.deploy.server.utils.container.ContainerWrapper.prepareStart(ContainerWrapper.java:363) at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:251) at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:209) at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:502) at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesImpl(ParallelAdapter.java:483) at com.sap.engine.services.deploy.server.application.StartTransaction.makeAllPhasesImpl(StartTransaction.java:584) at com.sap.engine.services.deploy.server.application.ParallelAdapter.runMe(ParallelAdapter.java:180) at com.sap.engine.services.deploy.server.application.ParallelAdapter.access$000(ParallelAdapter.java:43) at com.sap.engine.services.deploy.server.application.ParallelAdapter$1.run(ParallelAdapter.java:340) at com.sap.engine.frame.core.thread.Task.run(Task.java:73) at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:175) at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:274) Caused by: com.sap.engine.services.jndi.persistent.exceptions.NameAlreadyBoundException: Object with name com.sap.aii.adapter.soap.lib is already bound. at com.sap.engine.services.jndi.implserver.ServerContextImpl.bind(ServerContextImpl.java:343) at com.sap.engine.services.jndi.implclient.ClientContext.bind(ClientContext.java:850) at com.sap.engine.services.jndi.implclient.ClientContext.bind(ClientContext.java:695) at com.sap.engine.services.jndi.implclient.ClientContext.bind(ClientContext.java:912) at com.sap.engine.services.connector.deploy.util.ResourceAdapterStarter.bind(ResourceAdapterStarter.java:487) at com.sap.engine.services.connector.deploy.util.ResourceAdapterStarter.instantiateMCF(ResourceAdapterStarter.java:375) d) Global operation [startApp] over [application] [sap.com/com.sap.aii.adapter.soap.lib] finished with errors for [16]ms on server [4796750 >>> without warnings << >> Errors <<< 1). Cannot bind "com.sap.aii.adapter.soap.lib";. -> Object with name com.sap.aii.adapter.soap.lib is already bound. 2). com.sap.engine.services.connector.exceptions.BaseDeploymentException: Cannot bind "com.sap.aii.adapter.soap.lib";. at com.sap.engine.services.connector.deploy.util.ResourceAdapterStarter.instantiateMCF(ResourceAdapterStarter.java:393) at com.sap.engine.services.connector.deploy.util.ResourceAdapterStarter.initResourceAdapter(ResourceAdapterStarter.java:122) at com.sap.engine.services.connector.deploy.ConnectorContainerImpl.prepareStart(ConnectorContainerImpl.java:303) at com.sap.engine.services.deploy.server.utils.container.ContainerWrapper.prepareStart(ContainerWrapper.java:363) at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:251) at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:209) at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:502) at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesImpl(ParallelAdapter.java:483) at com.sap.engine.services.deploy.server.application.StartTransaction.makeAllPhasesImpl(StartTransaction.java:584) at com.sap.engine.services.deploy.server.application.ParallelAdapter.runMe(ParallelAdapter.java:180) at com.sap.engine.services.deploy.server.application.ParallelAdapter.access$000(ParallelAdapter.java:43) at com.sap.engine.services.deploy.server.application.ParallelAdapter$1.run(ParallelAdapter.java:340) at com.sap.engine.frame.core.thread.Task.run(Task.java:73) at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:175) at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:274) Caused by: com.sap.engine.services.jndi.persistent.exceptions.NameAlreadyBoundException: Object with name com.sap.aii.adapter.soap.lib is already bound. at com.sap.engine.services.jndi.implserver.ServerContextImpl.bind(ServerContextImpl.java:343) at com.sap.engine.services.jndi.implclient.ClientContext.bind(ClientContext.java:850) at com.sap.engine.services.jndi.implclient.ClientContext.bind(ClientContext.java:695) at com.sap.engine.services.jndi.implclient.ClientContext.bind(ClientContext.java:912) at com.sap.engine.services.connector.deploy.util.ResourceAdapterStarter.bind(ResourceAdapterStarter.java:487) at com.sap.engine.services.connector.deploy.util.ResourceAdapterStarter.instantiateMCF(ResourceAdapterStarter.java:375) Any of you have seen this kind of problem. Thanks Sam Edited by: sam robert on Jul 2, 2010 10:24 PM

    Hi Sam,
    1- What is your PI version?
    2- Do you use a High Availability system?
    3- Can you describe your scenario?
    From the 503 error, here is a generic description:
    The error message 503 Service unavailable Application stopped! is displayed.
    Description:The server is currently unable to handle the request due to a temporary overloading or maintenance of the server. The implication is that this is a temporary condition which will be alleviated after some delay. If known, the length of the delay MAY be indicated in a Retry-After header. If no Retry-After is given, the client SHOULD handle the response as it would for a 500 response.
    Note: The existence of the 503 status code does not imply that a server must use it when becoming overloaded. Some servers may wish to simply refuse the connection.
    Possible Tips: Because of J2EE application com.sap.aii.af.ms.app not active
    u2022 Try to (re)start the application using the Visual Administrator Choose Server --> Services --> Deploy --> View on Application or restart the J2EE engine
    u2022 The problem is that not all J2EE services can be started by the J2EE. i.e Start the Visual Administrator and select Server->Services->Deploy in the tree on the left. On the right-hand side, choose the Runtime tab page. You see a tree in the right window with all applications if you select the APPLICATION radio button. Check if they are running, otherwise choose Start. Usually the J2EE engine starts all services automatically.
    u2022 Refer SAP Note 803145,807000,791655
    Regards,
    Caio Cagnani

  • Non Central adapter error

    Hi All,
    Here is my Scenario:
    Trying implement /configure Non-central adapter engine hosted separate (J2EE) server. This will be connected to XI server(Integration engine and SLD) from where messages are sent/received.
    When I try to post message from XI to Non_central adapter engine following is the message
    u201CThe requested protocol u201CXIu201D is currently unavailableu201D
    Then I realized there is a problem in Non-central adapter engine configuration, which will be connected to SLD and Integration engine. I can see technical system and business system in SLD for Non-central adapter engine.
    Following is the findings in NWA of same host where non-central adapter engine.
    1) I see all J2EE services are running
    2) Application u201Ccom.sap.aii.adapter.soap.libu201D is no started and status is u201Cfailed to startu201D.  Later I tried to restart and following are the 4 error messages in sequence from trace file.
    a)
    Message: Access to XI AF MS resource failed.
    Date: 2010-07-02
    Time: 22:05:15:273
    Category: com.sap.aii.adapter.soap.ra.SPIManagedConnectionFactory
    Location: com.sap.aii.adapter.soap.ra.SPIManagedConnectionFactory.SPIManagedConnectionFactory()
    Application:
    Thread: Deploy Start Application Thread
    Data Source: j2ee\cluster\server0\log\defaultTrace_00.trc
    B)
    [ERROR CODE DPL.DS.5029] Exception in operation [startApp] with application [sap.com/com.sap.aii.adapter.soap.lib].
    [EXCEPTION]
    com.sap.engine.services.deploy.exceptions.ServerDeploymentException: [ERROR CODE DPL.DS.5029] Exception in operation [startApp] with application [sap.com/com.sap.aii.adapter.soap.lib].
    at com.sap.engine.services.deploy.server.application.ApplicationTransaction.rollbackPart(ApplicationTransaction.java:619)
    at com.sap.engine.services.deploy.server.application.StartTransaction.rollbackPart(StartTransaction.java:653)
    at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:506)
    at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesImpl(ParallelAdapter.java:483)
    at com.sap.engine.services.deploy.server.application.StartTransaction.makeAllPhasesImpl(StartTransaction.java:584)
    at com.sap.engine.services.deploy.server.application.ParallelAdapter.runMe(ParallelAdapter.java:180)
    at com.sap.engine.services.deploy.server.application.ParallelAdapter.access$000(ParallelAdapter.java:43)
    at com.sap.engine.services.deploy.server.application.ParallelAdapter$1.run(ParallelAdapter.java:340)
    at com.sap.engine.frame.core.thread.Task.run(Task.java:73)
    at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:175)
    at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:274)
    Caused by: com.sap.engine.services.connector.exceptions.BaseDeploymentException: Cannot bind "com.sap.aii.adapter.soap.lib";.
    at com.sap.engine.services.connector.deploy.util.ResourceAdapterStarter.instantiateMCF(ResourceAdapterStarter.java:393)
    at com.sap.engine.services.connector.deploy.util.ResourceAdapterStarter.initResourceAdapter(ResourceAdapterStarter.java:122)
    at com.sap.engine.services.connector.deploy.ConnectorContainerImpl.prepareStart(ConnectorContainerImpl.java:303)
    at com.sap.engine.services.deploy.server.utils.container.ContainerWrapper.prepareStart(ContainerWrapper.java:363)
    at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:251)
    at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:209)
    at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:502)
    ... 8 more
    Caused by: com.sap.engine.services.jndi.persistent.exceptions.NameAlreadyBoundException: Object with name com.sap.aii.adapter.soap.lib is already bound.
    at com.sap.engine.services.jndi.implserver.ServerContextImpl.bind(ServerContextImpl.java:343)
    at com.sap.engine.services.jndi.implclient.ClientContext.bind(ClientContext.java:850)
    at com.sap.engine.services.jndi.implclient.ClientContext.bind(ClientContext.java:695)
    at com.sap.engine.services.jndi.implclient.ClientContext.bind(ClientContext.java:912)
    at com.sap.engine.services.connector.deploy.util.ResourceAdapterStarter.bind(ResourceAdapterStarter.java:487)
    at com.sap.engine.services.connector.deploy.util.ResourceAdapterStarter.instantiateMCF(ResourceAdapterStarter.java:375)
    C)
    Cannot bind "com.sap.aii.adapter.soap.lib";.
    [EXCEPTION]
    com.sap.engine.services.connector.exceptions.BaseDeploymentException: Cannot bind "com.sap.aii.adapter.soap.lib";.
    at com.sap.engine.services.connector.deploy.util.ResourceAdapterStarter.instantiateMCF(ResourceAdapterStarter.java:393)
    at com.sap.engine.services.connector.deploy.util.ResourceAdapterStarter.initResourceAdapter(ResourceAdapterStarter.java:122)
    at com.sap.engine.services.connector.deploy.ConnectorContainerImpl.prepareStart(ConnectorContainerImpl.java:303)
    at com.sap.engine.services.deploy.server.utils.container.ContainerWrapper.prepareStart(ContainerWrapper.java:363)
    at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:251)
    at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:209)
    at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:502)
    at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesImpl(ParallelAdapter.java:483)
    at com.sap.engine.services.deploy.server.application.StartTransaction.makeAllPhasesImpl(StartTransaction.java:584)
    at com.sap.engine.services.deploy.server.application.ParallelAdapter.runMe(ParallelAdapter.java:180)
    at com.sap.engine.services.deploy.server.application.ParallelAdapter.access$000(ParallelAdapter.java:43)
    at com.sap.engine.services.deploy.server.application.ParallelAdapter$1.run(ParallelAdapter.java:340)
    at com.sap.engine.frame.core.thread.Task.run(Task.java:73)
    at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:175)
    at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:274)
    Caused by: com.sap.engine.services.jndi.persistent.exceptions.NameAlreadyBoundException: Object with name com.sap.aii.adapter.soap.lib is already bound.
    at com.sap.engine.services.jndi.implserver.ServerContextImpl.bind(ServerContextImpl.java:343)
    at com.sap.engine.services.jndi.implclient.ClientContext.bind(ClientContext.java:850)
    at com.sap.engine.services.jndi.implclient.ClientContext.bind(ClientContext.java:695)
    at com.sap.engine.services.jndi.implclient.ClientContext.bind(ClientContext.java:912)
    at com.sap.engine.services.connector.deploy.util.ResourceAdapterStarter.bind(ResourceAdapterStarter.java:487)
    at com.sap.engine.services.connector.deploy.util.ResourceAdapterStarter.instantiateMCF(ResourceAdapterStarter.java:375)
    d)
    Global operation [startApp] over [application] [sap.com/com.sap.aii.adapter.soap.lib] finished with errors for [16]ms on server [4796750
    >>> without warnings <<<
    >>> Errors <<<
    1). Cannot bind "com.sap.aii.adapter.soap.lib";.
    -> Object with name com.sap.aii.adapter.soap.lib is already bound.
    2). com.sap.engine.services.connector.exceptions.BaseDeploymentException: Cannot bind "com.sap.aii.adapter.soap.lib";.
    at com.sap.engine.services.connector.deploy.util.ResourceAdapterStarter.instantiateMCF(ResourceAdapterStarter.java:393)
    at com.sap.engine.services.connector.deploy.util.ResourceAdapterStarter.initResourceAdapter(ResourceAdapterStarter.java:122)
    at com.sap.engine.services.connector.deploy.ConnectorContainerImpl.prepareStart(ConnectorContainerImpl.java:303)
    at com.sap.engine.services.deploy.server.utils.container.ContainerWrapper.prepareStart(ContainerWrapper.java:363)
    at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:251)
    at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:209)
    at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:502)
    at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesImpl(ParallelAdapter.java:483)
    at com.sap.engine.services.deploy.server.application.StartTransaction.makeAllPhasesImpl(StartTransaction.java:584)
    at com.sap.engine.services.deploy.server.application.ParallelAdapter.runMe(ParallelAdapter.java:180)
    at com.sap.engine.services.deploy.server.application.ParallelAdapter.access$000(ParallelAdapter.java:43)
    at com.sap.engine.services.deploy.server.application.ParallelAdapter$1.run(ParallelAdapter.java:340)
    at com.sap.engine.frame.core.thread.Task.run(Task.java:73)
    at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:175)
    at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:274)
    Caused by: com.sap.engine.services.jndi.persistent.exceptions.NameAlreadyBoundException: Object with name com.sap.aii.adapter.soap.lib is already bound.
    at com.sap.engine.services.jndi.implserver.ServerContextImpl.bind(ServerContextImpl.java:343)
    at com.sap.engine.services.jndi.implclient.ClientContext.bind(ClientContext.java:850)
    at com.sap.engine.services.jndi.implclient.ClientContext.bind(ClientContext.java:695)
    at com.sap.engine.services.jndi.implclient.ClientContext.bind(ClientContext.java:912)
    at com.sap.engine.services.connector.deploy.util.ResourceAdapterStarter.bind(ResourceAdapterStarter.java:487)
    at com.sap.engine.services.connector.deploy.util.ResourceAdapterStarter.instantiateMCF(ResourceAdapterStarter.java:375)
    Any of you have seen this kind of problem.
    Thanks
    Sam
    Edited by: sam robert on Jul 2, 2010 10:24 PM

    Hi Sam,
    1- What is your PI version?
    2- Do you use a High Availability system?
    3- Can you describe your scenario?
    From the 503 error, here is a generic description:
    The error message 503 Service unavailable Application stopped! is displayed.
    Description:The server is currently unable to handle the request due to a temporary overloading or maintenance of the server. The implication is that this is a temporary condition which will be alleviated after some delay. If known, the length of the delay MAY be indicated in a Retry-After header. If no Retry-After is given, the client SHOULD handle the response as it would for a 500 response.
    Note: The existence of the 503 status code does not imply that a server must use it when becoming overloaded. Some servers may wish to simply refuse the connection.
    Possible Tips: Because of J2EE application com.sap.aii.af.ms.app not active
    u2022 Try to (re)start the application using the Visual Administrator Choose Server --> Services --> Deploy --> View on Application or restart the J2EE engine
    u2022 The problem is that not all J2EE services can be started by the J2EE. i.e Start the Visual Administrator and select Server->Services->Deploy in the tree on the left. On the right-hand side, choose the Runtime tab page. You see a tree in the right window with all applications if you select the APPLICATION radio button. Check if they are running, otherwise choose Start. Usually the J2EE engine starts all services automatically.
    u2022 Refer SAP Note 803145,807000,791655
    Regards,
    Caio Cagnani

  • Template Installer SLD Local only

    I have installed EP and have not configured SLD. I went to the NWA url and noticed a meesage stating Local SLD can only be configured (or something like that).
    Can I run the template installer for NWA Configure SLD to point to the central SLD? If not what do I have to do to point to a central SLD.
    Thanks
    Mikie

    Hi,
    See this
    Note 939592 - PI Usage Configuration versus Central SLD
    You can run Template installer for NWA to configure SLD to point Central SLD, but there are constraints.
    923359 - Collective Note: Template Installer (CTC)
    Br,
    Amit Lal
    Reward pts if suitable answer.

  • SLD and Management console

    Hello,
    It seems that both System landscape directory and SAP management console have some overlapping features. The services can be started or stopped in both. Is it true? Does anyone know the difference between these 2 and where does Solution manager fit in?
    Thanks
    Shailik

    hi
    its not true,you can not start and stop services using SLD.
    SLD is the central information provider where all your software components,products etc are maintained.
    it also contains information about all installed systems like Business systems etc .
    Where as SAP MMC,
    it will perform administrative tasks.
    it is used mainly for starting and stopping the servers and to monitor log files etc..
    Regards
    sowmya

  • Difference between SAP SLD and SAP Management console

    Hello,
    It seems that both System landscape directory and SAP management console have some overlapping features. The services can be started or stopped in both. Is it true? Does anyone know the difference between these 2 and where does Solution manager fit in?
    Thanks
    Shailik

    Hi,
    SAP SLD  is the central information provider in a system landscape.this contains both Component information and Landscape description.COMPONENT Info in sense all the sap products and components along with their versions, And also third party products also.LANDSCAPE desc in sense the description of all the systems in particular landscape.
    Example:This can shows exact idea for you.Components like CAF,Webdynpo(WD-java),BPM etc info.And the host names,Message server ports etc.Here we dont have start/stop functionality.
    SAP MC provides a common framework for centralized system management. It allows you to monitor and perform basic administration tasks on the SAP system centrally, thus simplifying system administration. Using the SAP MC you can
    1.Monitor and control (start, stop, or restart) the SAP system and its instances with a single tool
    2.Monitor system alerts
    3.Display the list of all access points to an SAP system etc.
    We can see difference by looking into http://<host name>:<port>/index.html
    Look and feel are also differ.
    For more info you can go through these links of sap help.
    For SAP SLD:http://help.sap.com/saphelp_nw04/helpdata/en/fe/39ae3d47afd652e10000000a114084/frameset.htm
    For SAP MC:http://help.sap.com/saphelp_nwce10/helpdata/en/44/c707c053550f2ce10000000a1553f7/frameset.htm
    Thanks,
    Murthy.

  • Synchronzing single SLDs

    We plan to use Solution Manager 4.0 as our main SLD (it is configured for that now).  As it stands, only Enterprise Portal was pointed to this SLD during installation.  We have other systems (XI/PI 7.0 and BI 7.03) that have been configured with their own local SLDs.  I have found this note (which is not current in English and is for NetWeaver 2004) that refers to how to synchronize the local SLDs with the central SLD, 764393 Configuration of the SAP System Landscape Directory. 
    This note discusses an export/import technique.  I have found nothing on service.sap.com/sld or elsewhere.  Does anyone know how to handle this situation?
    Points awarded.  Thanks!

    Hello Thomas,
    Nota 764393 is already in English.
    Pleae read the SLD Planning Guide PDF from www.service.sap.com/sld   > Media Library, there you can see how to export and import the different contents of SLD.
    Also checks notes:
    935474 -Grouping SLD instances
    954820 - Compatibility of SLD in the system landscape
    764393 - Reduce the number of System Landscape Directories
    Hope this helps,
    Dolores

  • Where has to be defined the SLD? PI/XI or Solution Manager?

    Hello,
    We have a PI production system, already configured and working. Now we are implementing the solution manager system. In both cases we only have productive systems. In which one should we define the SLD?
    Thanks and kind regards,
    Ana

    Hi
    Generally I would not recommend to have a Solution Manager Central SLD also used for Productive PI operations
    although this is possible to do
    We have seen situations whereby issues on the Solution Manager J2EE could affect PI operations generally the Solution Manager J2EE will be used for different purposes and may require different system administration. The dual purpose may also
    have performance or sizing implications - technically any sizing done would have been for separate purposes.
    The SLD for PI is needed for productive runtime (although there is a XI cache - even so I have seen situations whereby
    this cache has limitations)
    Customers often opt for the following
    Central SLD running on the Solution Manager J2EE stack
    Local PI SLD running on a PI J2EE stack
    This is because the SLD service is available on any J2EE installation
    You can then sync the local PI SLD  to the Central SLD  in order to build a full system list of all systems in the landscape
    see the SLD planning guide at System Landscape Directory (SLD) for details
    Best wishes
    Stuart

  • NWDI 7.01 setup with PI 7.11 SLD

    Hi there,
    At our company we are using PI System's SLD as single Central SLD.  We have like DEV  We just installed NWDI 7.01 (NetWeaver 7.0 EHP 1.0), where as DI also SLD driven system like PI. Since we have higher version PI 7.11 SLD which is the next version of NetWeaver, I am wondering if I can configure the NWDI to talk to Higher version of SLD System? Would this work without any problem?
    Let me know what you guys think.
    Thanks In Advance.
    Kumar

    Hi
    It will work without problem.
    thanks
    Arun

  • Transport SLD components

    Hello,
    We are planning to move the SLD objects from local SLD  to Central SLD ( Production ) .
    Kindly suggest if I need to create product and swcv directly in central SLD or how can I move from local SLD.
    Kindly suggest the steps to deploy the local sld to central sld.
    Thanks

    Hi ,
    in order to move the local SLD existing on PI System to another SLD(central) follow the below steps have to do the following steps.
    1- Install Central SLD on the
    2- Apply note 939592 for movement of local SLD Configurations to CENTRAL SLD System, installed in the above step 1.
    The note 720717 talks about reduction of SLDs, but does not speak about how to install Central SLD and then move the local SLD to this newly installed Central SLD.
    you will probably need to export the SLD content from the source SLD to import into your target central SLD....
    Exporting and Backing Up Your SLD Information check the link below
    http://help.sap.com/saphelp_nw70ehp1/helpdata/en/48/b7bbe3e2c0356be10000000a421937/frameset.htm
    Regards,
    Naveen

Maybe you are looking for