SLD Downtime

In our prod, SLD in local to XI or in other words SLD using XI java engine.
I installed the De-Central Adapter Engine and some of our important interfaces goes through it.
If XI java goes out of memory, it is going to be restarted by its own, till that XI java comes up. SLD will be down
because it uses XI java engine. It takes usually 6 minutes to come up. In mean time will effect my interfaces running through
De-central adapter engine? my understanding  for every 3 to 5 minutes XI runs reports to update the cache ? in this time it communicates with SLD and not for every single interface execution.
Can my De-Central adapter will able to manage this SLD downtime ?? If not sure ? is there any way to avoid this ?? by installing another SLD and making a bridge between this SLD and  that SLD ?? or like that ?? I'm not sure if this possible ?
Please share your knowledge and thoughts.
Thanks
Sagar

May be you can employ a backup SLD strategy -  refer to -
/people/wolf.hengevoss/blog/2010/01/28/sld-topology-how-to-gather-and-distribute-sld-data-in-your-it-landscape
VJ

Similar Messages

  • Mail or File Adapter are not running without SLD

    Hi,
    is it correct, that all adapters on java stack are not running while where is no connection to SLD? (Idoc and http are working because they run in abap stack)
    We have just one SLD (no replicated SLD) for our PI 7.0 and we can see, that mail or file adapter are getting errors if the sld instance is down.
    What can we do to avoid this behaviour because the admins wanna patch the SolMan and the SLD is running there.
    Is it possible to run the integration engine without SLD?
    Thanx a lot
    Wolfgang

    We have just one SLD (no replicated SLD) for our PI 7.0 and we can see, that mail or file adapter are getting errors if the sld instance is down.
    SLD lookups are made at various levels of message excution. When message pass from Adapter Engine to Inetgration Engine, SLD lookups helps in identifying the correct address of IE. Therefore it will always affect the java (AE) based adapters.
    What can we do to avoid this behaviour because the admins wanna patch the SolMan and the SLD is running there.
    Its better not to try avoiding this standard behavior.
    For your patching requirement, you must perform it when the message traffic is low e.g. during weekends. Usually everywhere such patching and upgrade are done on weekends as the downtime is acceptable in that duration.
    Regards,
    Prateek

  • Migration of local SLD to Central SLD on different host.

    Hello Experts,
    We have migrate the local SLD existing on the SAP PI System to a new Central SLD on a different host on SAP Solution Manager system.
    I followed the OSS Note 720717, which contains the description of the changes that have to be exectued in the SAP XI/PI Environment, during the SLD Migration. This note does not give any details of the description of changes for the other SAP Systems such as SAP ECC, BI etc registered in the SLD.
    Can anyone provide the OSS Notes, SAP Doc URL or the steps on how to migrate the local SLD existing on SAP XI/PI System to the new Central SLD on the SAP Solution Manager system.
    Thanks for help in advance.
    Best Regards,
    Haleem

    Firstly
    I recommend to avoid having 1 SLD for multiple clients - like Solution Manager, BI, ECC
    This is because clients may end up having conflicting requirements for the same SLD
    - for example the small user group for Solution Manager may have a flexible and easy going policy on J2EE downtime
    - but if you take down the Solution Manager J2EE that houses the SLD and PI uses this SLD - then you could have a severe affect on PI useage
    Secondly
    Although you can migrate content - this still does not guarantee the target landscape will work
    - you may still need to manually re-implement target landscape configuration
    let me give you an example
    SLD 1 is being moved to SLD 2
    Portal 1 is pointing to SLD 1
    Even if you migrate the content of SLD 1 - including the ECC and Portal technical system landscape information
    Portal 1 is still pointing to SLD 1 - this then needs to be manually re-pointed to SLD2
    and that might not be all the complete steps either !
    The complete steps of migration from the client side may not be available  (I have found only steps to
    migrate SLD content not migrate client use of the SLD)
    - they may only be available as the documentation for the original configuration steps required to step SLD and the client
    - therefore when migrating SLD you must go through the client setup documentation for SLD and check your
    target landscape is consistent
    Lastly - other considerations include
    Lets say you also export model and CIM content from SLD 1 to SLD 2 - this means SLD 2 has an import line from SLD 1
    - if you decomission SLD1 then you need to switch the import line which is not recommended - this could cause severe problems and may require you to create a new import line to upload content from SAP /swdc (which you need to keep the SLD bug free and latest definitions)
    Just a few thoughts on issues you may encounter
    Best wishes
    Stuart

  • Patching a Central SLD System

    Hi
    we use a central SLD (system landscape directory) in our XI landscape.
    the disadvantage is, that the XI system is not running well, when patching the central sld system.
    is there a guideline from sap, to minimize downtime of the XI system, when patching the central sld system ? or do you have good ideas, to keep the XI system running, when patching the sld system ?
    Thanks in advance,
    peter

    Hi Peter,
         Go though the files for help on minimize downtime:
    <a href="http://help.sap.com/saphelp_nw2004s/helpdata/en/12/5ec33a6e386436e10000000a11402f/frameset.htm">http://help.sap.com/saphelp_nw2004s/helpdata/en/12/5ec33a6e386436e10000000a11402f/frameset.htm</a>
    <a href="http://help.sap.com/saphelp_nw2004s/helpdata/en/42/2da73a0e547d22e10000000a114084/frameset.htm">http://help.sap.com/saphelp_nw2004s/helpdata/en/42/2da73a0e547d22e10000000a114084/frameset.htm</a>
    <a href="http://help.sap.com/saphelp_nw2004s/helpdata/en/b1/8c8838754ebb10e10000009b38f8cf/frameset.htm">http://help.sap.com/saphelp_nw2004s/helpdata/en/b1/8c8838754ebb10e10000009b38f8cf/frameset.htm</a>
    <a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/a02397f9-0d8d-2910-e5a0-b8241bbc9381">https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/a02397f9-0d8d-2910-e5a0-b8241bbc9381</a>
    Regards,
    Subhasha Ranjan

  • Central SLD and Webdynpro

    Dear all,
    I have a new EP 6.0 installation running ESS/MSS and BW reporting and implemented central SLD.The SLD server was the CEN Solution Manager system. Because of some issues with support pack application in the solution manager system, the solution manager system was unavailable for a week. As the Webdynpro JCOs that are used in ESS/MSS use SLD, ESS/MSS in my portal systems became unavailable for my users. I had to configure local SLDs for each portal system to avoid the application downtime
    I am wondering what people are doing out there to avoid what happened to me: High Availability? Seems a bit over the top as we do not have HA for our mySAP ERP production system which is the most important system of the landscape. Any other thoughts or SAP recommendations would be very much appreciated
    Many thanks
    Andreas

    Hi,
    Ofcourse HA should be one of the strategies you should think about. But now that you don't have it in place and cause for downtime is something like upgrade or maintenance, which is unavoidable, you can maintain the ECC system (HCM System) in your SLD, point the JCo Connections to your ECC system and thereby you should be able to use ESS-MSS. This won't take more that an hour, trust me.
    Would also like to know what's your User Management Strategy ? If you are using the solution manager as your datasource for user management on portal, then you can hardly do anything.
    Cheers,
    Sunil
    PS: Reward points for helpful answers.

  • 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

  • Live SLD Content Imports

    Does anyone know if CR and CIM imports have to be done during system outages or can it be run safely during business hours while EP and XI systems are using the SLD?  I have noticed in the logs that it appears to load up a "shadow" schema and then delete it when it is done, leading me to believe that the actual impact to live systems would be minimal or none.  The other alternative I have considered is moving live systems over to a copy of the SLD and then reconfiguring when the original SLD is updated, but this also creates some impact if the SLD is required during configuration move.
    Any thoughts or documentation on this question would be appreciated.
    Phil

    I think it's not neccesar to do it downtime
    1) Import of CR might take few hours, for example mission critical XI system usually doesn't have few hours for the downtime.
    2) CIM and CR content update should be delta content, it shouldn't effect the part which is already in use.
    The wiki page mentioned above didn't talk about the outage for the SLD CIM and CR update.
    Cheers,
    Denny

  • A Doubt in Creation of Tech. System for a BW Server in SLD

    Hi Experts,
    I want to access BI Queries in a BW System in VC 7.1.
    When I am trying to create a New Technical System in SLD of CE 7.1 Server, it is giving me the options, to Select the System Types as
    1. AS ABAP
    2. AS Java
    3. Standalone
    4. Third Party
    So, Whether we need to Select the System AS ABAP or we need to Install anyother thing to get a Systems Option as ABAP.
    Also, I read in a SAP Note, That we have to define the System as AS SAP_BW.
    Note: BI Kit is installed in my CE 7.1 Server
    Please help me to solve this issue.
    Thanks in Advance.
    Regards,
    Palani

    Hi Palani,
    you don't need an SLD for configuring Bi connections. Please have a look at
    http://help.sap.com/saphelp_nwce10/helpdata/en/7e/6dbcea3700452195e3bddaa47c5906/frameset.htm
    how to define a BI connection for Visual Composer 7.1
    Best regards
    Hartmut

  • NWDI in the XI Scenario - SLD

    Experts,
    I have created a track to transport the XI content.
    We have two SLD servers in the landscape. The first is used by XI and contains all the required XI business systems and the second is used only by NWDI and contains only the SC definitions.
    My question-
    DOes the SLD for NWDI need XI system details???? According to my understanding, NWDI needs only the component information from the SLD.
    Bascially, do i need to import the business system data into the SLD that is being used by NWDI???
    thanks,
    Vineeth

    Did a little research and found that the SC information is sufficient for NWDI.

  • Logical system name in business system (SLD)

    Hi,
    While creating business system in SLD what should give for the logical system name?
    Should the logical system name exists in ABAP stack or the new one?
    Thanks.

    Hi,
    If you are creating the BS for SAP R/3 in SLD means we have to give the LS name which we had in SAP R/3( goto SALE and take the LS from there)
    Goto Assign LS-----take the client which you are using for SAP R/3 and take the LS name assigned to that Client
    Regards
    Seshagiri

  • Best practice to reduce downtime  for fulllaod in Production system

    Hi Guys ,
    we have  options like "Initialize without data transfer  ", Initialization with data transfer"
    To reduce downtime of production system for load setup tables , first I will trigger info package for  Initialization without data transfer so that pointer will be set on table , from that point onwards any record added as delta record , I will trigger Info package for Delta , to get delta records in BW , once delta successful, I will trigger info package for  the repair full request to  get all historical data into setup tables , so that downtime of production system will be reduced.
    Please let me know your thoughts and correct me if I am wrong .
    Please let me know about "Early delta Initialization" option .
    Kind regards.
    hari

    Hi,
    You got some wrong information.
    Info pack - just loads data from setup tables to PSA only.
    Setup tables - need to fill by manual by using related t codes.
    Assuming as your using LO Data source.
    In this case source system lock is mandatory. other wise you need to go with early delta init option.
    Early delta init - its useful to load data into bw without down time at source.
    Means at same time it set delta pointer and will load into as your settings(init with or without).
    if source system not able lock as per client needs then better to go with early delta init options.
    Thanks

  • Problem with business systems in SLD

    Hey guys
    i m doing a IDOC to file scenario and m creating two business systems in SLD
    the first one uses the logical system name of the R/3 server and has been configured as WAS ABAP.
    when i try to create the second one as a third party using the logical system name i defined in BD54(on R/3 server),i get the error sayin that a business system already exist with the logical system name.
    i do have one businees system which is using the same logical system but that has been configured as WAS ABAP.
    cant i assign two different business names to same logical systems?
    thanx
    ahmad
    Message was edited by:
            Ahmad

    Hey
    thanx ,now when i try to use the same business system name for the R/3 server in the second scenaario,i dont see the business system in ID,i did cache refresh,
    also just want to make sure
    i have configured my SLD as under for the first scenario
    created two business system,first one is using the logical system name of the R/3 server configured as WAS ABAP and the second one is configured as third paarty and using the logical system name created in BD54.
    do these setting looks good to u?
    now can i use both these business system in my second IDOC to File scenariio?
    thanx
    ahmad

  • How to create Business Services in SLD

    Hi Experts,
    I'm working on SAP background and wanted to learn SAP-XI.
    I'm interesting to work in XI and for this need your support.
    I installed XI in my PC and wanted to start learning.
    But there are no Business Services (or) Systems configured in the SLD.
    I want to start with a simple FILE to FILE scenario.
    Could anyone please tell me how to create services in SLD and carry on from there.
    Thanks,
    Prajwal

    Hi,
    please look at the bleow links
    http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/4013f6bb-7ec3-2b10-62b5-e5be01e498f7
    Blogs
    /people/srinivas.vanamala2/blog/2007/02/05/step-by-step-guide-xml-file-2-xml-file-scenario-part-i  - Step by Step Guide: XML File 2 XML File Scenario: Part I
    /people/srinivas.vanamala2/blog/2007/02/05/step-by-step-guide-xml-file-2-xml-file-scenario-part-ii - Step by Step Guide: XML File 2 XML File Scenario: Part 2
    Regards,
    Pradeep A.
    Edited by: Pradeep Amisagadda on Apr 16, 2010 9:39 AM

  • Setting Business Systems in SLD

    Hi,
    In our SLD, we have two different Business Systems associated with the same ABAP Technical System and same client too. One BS is related to one Integration Server (XI) -this BS was imported in SLD- whereas another BS is related to another one (PI).
    When we run a soap interface in XI, we see the request reaches the correct BS (XI BS). However, the response is sent by the PI BS through the XI interface, getting an error.
    We need to have both Business Systems due to we are using the same SLD for XI and PI.
    Any idea?
    Thanks in advance,
    Samantha.

    Hi Luqman,
    Their names are different. Each BS is related to a different Integration Server, but their ABAP TS and client are equal.
    XI interfaces should use the XI BS, whereas PI interfaces should the PI BS, but this is not so.
    Is there any option that selects by default a particular BS in SLD when both BS using the same TS?
    Thanks,
    Samantha.

  • PI 7.11 Post Installation - Template initial SLD configuration ERROR

    Hi All,
    I was installed SAP PI 7.11 on Widows2003 with Max DB  and when i am trying to run the initial SLD confuguration Template we are getting error at 70% as below. An the same ii have tried in different Browsers lke IE8.0, IE6.0 and Firefox
    During the configuration Step: SAP BASIS Product and component.
    ERROR: CIM_ERR_FAILED: HTTP Response Code: 400 Bad Request.
    And i am posting the default trace log.
    "Severity","Date","Time","Message","Category","Location","Application",
    "Error","2010-12-08","16:43:45:296","Warning: validation was turned on but an org.xml.sax.ErrorHandler was not set, which is probably not what is desired.  Parser will use a default ErrorHandler to print the first 10  errors.  Please call the setErrorHandler method to fix this.","System.err","System.err","sap.com/tclmitsamuimainframe~wd",
    "Error","2010-12-08","16:43:45:296","Error: URI = 'null', Line = '2', : Document is invalid: no grammar found.","System.err","System.err","sap.com/tclmitsamuimainframe~wd",
    "Error","2010-12-08","16:43:45:296","Error: URI = 'null', Line = '2', : Document root element 'wsdl:definitions', must match DOCTYPE root 'null'.","System.err","System.err","sap.com/tclmitsamuimainframe~wd",
    "Error","2010-12-08","16:43:45:625","Unexpected exception catched and will be rethrown:","com.sap.ctc.util.pi.services.SystemLandscapeSetup","com.sap.ctc.util.pi.services.SystemLandscapeSetup.maintainInstalledProduct(String productName, String productVersionName, String vendor, String version, String[] componentNames, String componentVersion, String hostName, String systemName)","sap.com/tclmitsamuimainframe~wd",
    "","","","com.sap.sld.api.wbem.exception.CIMCommunicationException: CIM_ERR_FAILED: HTTP response code: 400 Bad Request","","","",
    "","","","[EXCEPTION]","","","",
    "","","","com.sap.sld.api.wbem.exception.CIMCommunicationException: CIM_ERR_FAILED: HTTP response code: 400 Bad Request","","","",
    "","","","at com.sap.sld.api.wbem.client.WBEMHttpRequestSender.newCommunicationException(WBEMHttpRequestSender.java:511)","","","",
    "","","","at com.sap.sld.api.wbem.client.WBEMHttpRequestSender.processResponse(WBEMHttpRequestSender.java:400)","","","",
    "","","","at com.sap.sld.api.wbem.client.WBEMHttpRequestSender.sendImpl(WBEMHttpRequestSender.java:206)","","","",
    "","","","at com.sap.sld.api.wbem.client.WBEMHttpRequestSender.retryOnUnsupportedMediaType(WBEMHttpRequestSender.java:585)","","","",
    "","","","at com.sap.sld.api.wbem.client.WBEMHttpRequestSender.processResponse(WBEMHttpRequestSender.java:396)","","","",
    "","","","at com.sap.sld.api.wbem.client.WBEMHttpRequestSender.sendImpl(WBEMHttpRequestSender.java:206)","","","",
    "","","","at com.sap.sld.api.wbem.client.WBEMRequestSender.send(WBEMRequestSender.java:205)","","","",
    "","","","at com.sap.sld.api.wbem.client.WBEMRequestSender.send(WBEMRequestSender.java:175)","","","",
    "","","","at com.sap.sld.api.wbem.client.WBEMRequestSender.send(WBEMRequestSender.java:238)","","","",
    "","","","at com.sap.sld.api.wbem.client.WBEMRequestSender.send(WBEMRequestSender.java:268)","","","",
    "","","","at com.sap.sld.api.wbem.client.WBEMRemoteClient.sendAndCast(WBEMRemoteClient.java:936)","","","",
    "","","","at com.sap.sld.api.wbem.client.WBEMRemoteClient.enumerateInstanceNamesImpl(WBEMRemoteClient.java:463)","","","",
    "","","","at com.sap.sld.api.wbem.client.WBEMAbstractClient.enumerateInstanceNames(WBEMAbstractClient.java:480)","","","",
    "","","","at com.sap.sld.api.std.impl.BaseSystem.getAllInstances(BaseSystem.java:312)","","","",
    "","","","at com.sap.sld.api.std.tech.SLD_ABAPSystem.getABAPSystem(SLD_ABAPSystem.java:661)","","","",
    "","","","at com.sap.ctc.util.pi.services.SystemLandscapeSetup.maintainInstalledProduct(SystemLandscapeSetup.java:280)","","","",
    "","","","at com.sap.ctc.util.pi.services.SystemLandscapeSetup.maintainInstalledProduct(SystemLandscapeSetup.java:1479)","","","",
    "","","","at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)","","","",
    "","","","at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)","","","",
    "","","","at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)","","","",
    "","","","at java.lang.reflect.Method.invoke(Method.java:585)","","","",
    "","","","at com.sap.tc.lm.ctc.provider.javaServiceProvider.JavaMethodExecuter.invoke(JavaMethodExecuter.java:221)","","","",
    "","","","at com.sap.tc.lm.ctc.provider.javaServiceProvider.JavaServiceExecuter.executeService(JavaServiceExecuter.java:98)","","","",
    "","","","at com.sap.tc.lm.ctc.cul.broker.BrokerServiceExecuter.executeService(BrokerServiceExecuter.java:54)","","","",
    "","","","at com.sap.tc.lm.ctc.cul.serviceimpl.executor.CULServiceExecutor.executeService(CULServiceExecutor.java:51)","","","",
    "","","","at com.sap.tc.lm.ctc.cul.serviceimpl.process.InvokeServiceControllerDefault.execute(InvokeServiceControllerDefault.java:170)","","","",
    "","","","at com.sap.tc.lm.ctc.metamodel.process.controller.ProcessControllerImpl.execute(ProcessControllerImpl.java:233)","","","",
    "","","","at com.sap.tc.lm.ctc.metamodel.process.controller.ProcessControllerImpl.execute(ProcessControllerImpl.java:233)","","","",
    "","","","at com.sap.tc.lm.ctc.metamodel.process.controller.ProcessControllerImpl.execute(ProcessControllerImpl.java:233)","","","",
    "","","","at com.sap.tc.lm.ctc.metamodel.process.controller.ProcessControllerImpl.execute(ProcessControllerImpl.java:233)","","","",
    "","","","at com.sap.tc.lm.ctc.metamodel.process.controller.ProcessControllerImpl.execute(ProcessControllerImpl.java:233)","","","",
    "","","","at com.sap.tc.lm.ctc.metamodel.process.controller.ProcessControllerImpl.execute(ProcessControllerImpl.java:233)","","","",
    "","","","at com.sap.tc.lm.ctc.metamodel.process.controller.ProcessControllerImpl.execute(ProcessControllerImpl.java:233)","","","",
    "","","","at com.sap.tc.lm.ctc.metamodel.process.controller.ProcessExecuter.run(ProcessExecuter.java:158)","","","",
    "","","","at java.lang.Thread.run(Thread.java:725)","","","",
    "Error","2010-12-
    "Error","2010-12-08","16:43:45:625","","com.sap.tc.lm.ctc.provider.javaServiceProvider.JavaMethodExecuter","com.sap.tc.lm.ctc.provider.javaServiceProvider.JavaMethodExecuter","sap.com/tclmitsamuimainframe~wd",
    "Error","2010-12-08","16:43:45:625","Service execution error. Invocation target error when call method maintainInstalledProduct in class com.sap.ctc.util.pi.services.SystemLandscapeSetup of component sap.com/com.sap.xi.ctc.app (error message = CIM_ERR_FAILED: HTTP response code: 400 Bad Request)","com.sap.tc.lm.ctc.cul.serviceimpl.process.InvokeServiceControllerDefault","com.sap.tc.lm.ctc.cul.serviceimpl.process.InvokeServiceControllerDefault","sap.com/tclmitsamuimainframe~wd",
    "","","","[EXCEPTION]","","","",
    "","","","com.sap.tc.lm.ctc.cul.api.CULServiceException: Service execution error. Invocation target error when call method maintainInstalledProduct in class com.sap.ctc.util.pi.services.SystemLandscapeSetup of component sap.com/com.sap.xi.ctc.app (error message = CIM_ERR_FAILED: HTTP response code: 400 Bad Request)","","","",
    "","","","at com.sap.tc.lm.ctc.cul.broker.BrokerServiceExecuter.executeService(BrokerServiceExecuter.java:56)","","","",
    "","","","at com.sap.tc.lm.ctc.cul.serviceimpl.executor.CULServiceExecutor.executeService(CULServiceExecutor.java:51)","","","",
    "","","","at com.sap.tc.lm.ctc.cul.serviceimpl.process.InvokeServiceControllerDefault.execute(InvokeServiceControllerDefault.java:170)","","","",
    "","","","at com.sap.tc.lm.ctc.metamodel.process.controller.ProcessControllerImpl.execute(ProcessControllerImpl.java:233)","","","",
    "","","","at com.sap.tc.lm.ctc.metamodel.process.controller.ProcessControllerImpl.execute(ProcessControllerImpl.java:233)","","","",
    "","","","at com.sap.tc.lm.ctc.metamodel.process.controller.ProcessControllerImpl.execute(ProcessControllerImpl.java:233)","","","",
    "","","","at com.sap.tc.lm.ctc.metamodel.process.controller.ProcessControllerImpl.execute(ProcessControllerImpl.java:233)","","","",
    "","","","at com.sap.tc.lm.ctc.metamodel.process.controller.ProcessControllerImpl.execute(ProcessControllerImpl.java:233)","","","",
    "","","","at com.sap.tc.lm.ctc.metamodel.process.controller.ProcessControllerImpl.execute(ProcessControllerImpl.java:233)","","","",
    "","","","at com.sap.tc.lm.ctc.metamodel.process.controller.ProcessControllerImpl.execute(ProcessControllerImpl.java:233)","","","",
    "","","","at com.sap.tc.lm.ctc.metamodel.process.controller.ProcessExecuter.run(ProcessExecuter.java:158)","","","",
    "","","","at java.lang.Thread.run(Thread.java:725)","","","",
    "","","","Caused by: com.sap.tc.lm.ctc.provider.javaServiceProvider.exceptions.CPIServiceExecutionException: Service execution error. Invocation target error when call method maintainInstalledProduct in class com.sap.ctc.util.pi.services.SystemLandscapeSetup of component sap.com/com.sap.xi.ctc.app (error message = CIM_ERR_FAILED: HTTP response code: 400 Bad Request)","","","",
    "","","","at com.sap.tc.lm.ctc.provider.javaServiceProvider.JavaMethodExecuter.invoke(JavaMethodExecuter.java:255)","","","",
    "","","","at com.sap.tc.lm.ctc.provider.javaServiceProvider.JavaServiceExecuter.executeService(JavaServiceExecuter.java:98)","","","",
    "","","","at com.sap.tc.lm.ctc.cul.broker.BrokerServiceExecuter.executeService(BrokerServiceExecuter.java:54)","","","",
    "","","","... 11 more","","","",
    "","","","Caused by: java.lang.reflect.InvocationTargetException","","","",
    "","","","at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)","","","",
    "","","","at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)","","","",
    "","","","at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)","","","",
    "","","","at java.lang.reflect.Method.invoke(Method.java:585)","","","",
    "","","","at com.sap.tc.lm.ctc.provider.javaServiceProvider.JavaMethodExecuter.invoke(JavaMethodExecuter.java:221)","","","",
    "","","","... 13 more","","","",
    "","","","Caused by: com.sap.sld.api.wbem.exception.CIMCommunicationException: CIM_ERR_FAILED: HTTP response code: 400 Bad Request","","","",
    "","","","at com.sap.ctc.util.infra.BaseConfig.dispatchException(BaseConfig.java:242)","","","",
    "","","","at com.sap.ctc.util.pi.services.SystemLandscapeSetup.maintainInstalledProduct(SystemLandscapeSetup.java:361)","","","",
    "","","","at com.sap.ctc.util.pi.services.SystemLandscapeSetup.maintainInstalledProduct(SystemLandscapeSetup.java:1479)","","","",
    "","","","... 18 more","","","",
    "","","","Caused by: com.sap.sld.api.wbem.exception.CIMCommunicationException: CIM_ERR_FAILED: HTTP response code: 400 Bad Request","","","",
    "","","","at com.sap.sld.api.wbem.client.WBEMHttpRequestSender.newCommunicationException(WBEMHttpRequestSender.java:511)","","","",
    "","","","at com.sap.sld.api.wbem.client.WBEMHttpRequestSender.processResponse(WBEMHttpRequestSender.java:400)","","","",
    "","","","at com.sap.sld.api.wbem.client.WBEMHttpRequestSender.sendImpl(WBEMHttpRequestSender.java:206)","","","",
    "","","","at com.sap.sld.api.wbem.client.WBEMHttpRequestSender.retryOnUnsupportedMediaType(WBEMHttpRequestSender.java:585)","","","",
    "","","","at com.sap.sld.api.wbem.client.WBEMHttpRequestSender.processResponse(WBEMHttpRequestSender.java:396)","","","",
    "","","","at com.sap.sld.api.wbem.client.WBEMHttpRequestSender.sendImpl(WBEMHttpRequestSender.java:206)","","","",
    "","","","at com.sap.sld.api.wbem.client.WBEMRequestSender.send(WBEMRequestSender.java:205)","","","",
    "","","","at com.sap.sld.api.wbem.client.WBEMRequestSender.send(WBEMRequestSender.java:175)","","","",
    "","","","at com.sap.sld.api.wbem.client.WBEMRequestSender.send(WBEMRequestSender.java:238)","","","",
    "","","","at com.sap.sld.api.wbem.client.WBEMRequestSender.send(WBEMRequestSender.java:268)","","","",
    "","","","at com.sap.sld.api.wbem.client.WBEMRemoteClient.sendAndCast(WBEMRemoteClient.java:936)","","","",
    "","","","at com.sap.sld.api.wbem.client.WBEMRemoteClient.enumerateInstanceNamesImpl(WBEMRemoteClient.java:463)","","","",
    "","","","at com.sap.sld.api.wbem.client.WBEMAbstractClient.enumerateInstanceNames(WBEMAbstractClient.java:480)","","","",
    "","","","at com.sap.sld.api.std.impl.BaseSystem.getAllInstances(BaseSystem.java:312)","","","",
    "","","","at com.sap.sld.api.std.tech.SLD_ABAPSystem.getABAPSystem(SLD_ABAPSystem.java:661)","","","",
    "","","","at com.sap.ctc.util.pi.services.SystemLandscapeSetup.maintainInstalledProduct(SystemLandscapeSetup.java:280)","","","",
    "","","","... 19 more","","","",
    "Error","2010-12-08","16:43:45:625","","com.sap.tc.lm.ctc.cul.serviceimpl.process.InvokeServiceControllerDefault","com.sap.tc.lm.ctc.cul.serviceimpl.process.InvokeServiceControllerDefault","sap.com/tclmitsamuimainframe~wd",
    Thanks & Regards,
    Sreekanth

    we have installed PI7.11 agian
    thanks

Maybe you are looking for