Issue in registering ABAP stack into SLD

Hi all
The issue is as shown below. I appreciate your help.
Environment: SLD host-Windows Server 2003, Oracle 10g, WAS JAVA 640 SP19
CRM ABAP+JAVA 640 host - unix, Oracle
I was able to register CRM JAVA stack in SLD from Visual Administrator>SLD Data Supplier. The CIM Client Test was successfull.
When i try to register the CRM ABAP stack from tcode RZ70, i get an error as below:
SLD DS start program
    0: sapsrm_CRM_05                             : Execute program: SLDAPPL_SERV
    0: sapsrm_CRM_05                             : Execute program: SLDBCSYS
    0: sapsrm_CRM_05                             : Execute program: SLDCLIENT
    0: sapsrm_CRM_05                             : Execute program: SLDCOMPSYS
    0: sapsrm_CRM_05                             : Execute program: SLDDBSYS
    0: sapsrm_CRM_05                             : Execute program: SLDGWSRV
    0: sapsrm_CRM_05                             : Execute program: SLDINSTSC
    0: sapsrm_CRM_05                             : Execute program: SLDINSTSP
    0: sapsrm_CRM_05                             : Execute program: SLDIPSERV
    0: sapsrm_CRM_05                             : Execute program: SLDMSGSRV
    0: sapsrm_CRM_05                             : Execute program: SLDASSOC
    0: sapsrm_CRM_05                             : Collection of SLD data finished
    0: sapsrm_CRM_05                             : Data collected successfully
    0: sapsrm_CRM_05                             : RFC data prepared
    0: sapsrm_CRM_05                             : Used RFC destination: SLD_UC
    0: sapsrm_CRM_05                             : RFC call failed: / CPIC-CALL: 'ThSAPECMINIT' : cmRc=17 thRc=236#SAP gateway connection failed. Is SAP gateway started?
    0: sapsrm_CRM_05                             : Existing periodic jobs removed. Number: 1
    0: sapsrm_CRM_05                             : Program scheduled: 20080506 222324
    1: sapsrm_CRM_05                             : Event-controlled job already exists; scheduling not necessary
I came to know from other forums in sdn that we need to install/configure separate gateway if the SLD is on a standalone JAVA engine.
Also, in SM59 SLD_UC, SLD_NUC, SAPSLDAPI are failing with the same error of "RFC call failed: / CPIC-CALL: 'ThSAPECMINIT' : cmRc=17 thRc=236#SAP gateway connection failed. Is SAP gateway started?"
Please suggest how to resolve this. Please let me know if you need more details.
Thanks already
Edited by: Rahul Paul Patchigondla on May 6, 2008 9:57 AM

Rahul,
as RK already stated: the SLD has to connect to an SAP gateway, such is running on an ABAP system.
You may initially try to use the SAP gateway from the CRM ABAP stack. Therefore you will have to adjust the SLD to use that SAP gateway. On 6.40 SLD: Administration / Data supplier bridge / RFC gateway: Server (host name) and Service (combination of sapgw and instance number of CRM ABAP system).
After that, in CRM SM59 SLD_UC, SLD_NUC, SAPSLDAPI will have to be adjusted accordingly.
Regards, Boris

Similar Messages

  • Do I really need to install ABAP stack for SLD

    As far as I know, the SLD runs on the Java stack.  We're planning to install the standalone SLD server as the central SLD, to which later all the systems (ABAP, JAVA) will be connected.  I wonder if it's really necessary to install the ABAP+JAVA stack for it.  If I only install Java stack, will there be any concern in the future if however the ABAP stack become required?
    Thanks,
    Jerry

    Jerry,
    SLD only need the J2EE engine. Usually you'll see SLD attached to a Solution Manager 4.0, SAP PI/XI,  BI 7.0 (BI JAVA)  or EP. These are the systems that really need a SLD to run.
    Honestly I can't see any advantage in installing a standalone SLD, unless you have several SAP environments and a complex architecture.
    Anyway I think you should see  these links...
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/e0a1a8fb-0527-2a10-f781-8b67eab16582
    /people/boris.zarske/blog/2007/06/13/sizing-a-system-for-the-system-landscape-directory-of-sap-netweaver
    /people/boris.zarske/blog/2007/06/10/planning-a-strategy-for-the-system-landscape-directory-sld-of-sap-netweaver
    Cheers

  • Registering ABAP system with SLD Web AS JAVA

    Hello,
    I'm trying to register an ABAP only system with an SLD that resides on a JAVA-only system. When registering the ABAP system in RZ70, I enter the gateway host of the JAVA-only system and the gateway service as "sapgw<instance>". However, when looking at the java-only system, I don't see that the gateway is even running.
    The JAVA only system is running on Windows 2008.
    A couple questions:
    1) Is "sapgw<instance>" the gateway service on a java-only system?
    2) If the gateway is running, does it show in the services or in the SAP MMC?
    3) I've tried starting the gateway manually using "gwrd -force pf=<start profile>" and the dev_rd log says"***LOG S00=> GwInitReader, gateway started ( 2980) [gwxxrd.c     1757]
    ERROR => [CreateOsShm] CreateFileMapping(5,4 KB) failed with Err=5
                  EIO*: Input/output error OR: Access is denied. [shmnt.c      2174]
    ERROR => ShmCreate: Create (5,4096,1) failed [shmnt.c      506]
    Is this the right way to start the gateway?
    Any help would be greatly appreciated.
    Thanks,
    Dale Dingmann

    Hi Dale,
    could you please tell us which Release your AS Java is? I have an AS Java 7.01(UsageType EP) on an AIX machine with a local SLD to which an AS ABAP 7.01 should register. I am not sure whether I can use the solution mentioned above or whether I have to install a standalone gateway.
    System Landscape Directory Planning Guide (March 2010, page 43) quotes quite a similar solution but without Information concerning the release. This information also belongs to a standalone SLD. The last three scentences of SAP Note 1057720 quotes that for releases up to and including Release 7.0 one has to install a standalone gateway. In higher releases however "the SCS of the AS Java installs an RFC gateway and configures it as the default in the SLD". Is AS Java 7.01 a higher release than 7.00 and how can I check wheter there is an installed Gateway on SCS instance or not?
    Can someone clarify that point?
    Best Regards

  • Register ABAP Add-On in SLD

    We have developed an ABAP add-on (AAK/Saint).
    Our add-on is supposed to register itself in the SLD, but we do not know what this means. Is there some metainformation we need to provide along with the add-on, or even some interface we need to implement to provide this information.
    Our systems are coupled with the SLD but we do not find our add-on when we install our product.
    Any idea?
    Edited by: Frank Torst on Jan 8, 2008 6:11 PM

    We have used another library for delpoying it, with this it is working.

  • Sld runs on abap stack

    Plz correct me if I am wrong
    SLD runs on abap stack ??
    thanks
    kumar

    Kumar,
    SLD Runs on java stack, to be confirmed please read the Page 30 & 31 of the below document.
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/29b1f3ea-0c01-0010-2dae-cc64bb381c97
    They haven't mentioned explicitly , but if you read that page you will  get an idea.
    Best regards,
    raj.

  • Issue in portal after abap stack upgrade

    Hi,
    Except travel and expenditure, everything is working fine after abap stack upgrade.  we have restarted abap and portal 3-4 times, we use abap ume. we are  getting error:
    Portal runtime error.
    An exception occurred while processing your request. Send the exception ID to your portal administrator.
    Exception ID: 18:57_27/02/12_0004_16184750
    defaulttrace:
    \#39;&lt;System.Access.WAS.protocol&gt;://&lt;System.Access.WAS.hostname&gt;/sap/bc/webdynpro/&lt;WebDynproNamespace&gt;/&lt;WebDynproApplication&gt;/;sap-ext-sid=&lt;ESID[url_ENCODE]&gt;?sap-ep-iviewhandle=007&lt;ESID[HASH]&gt;&amp;sap-wd-configId=&lt;WebDynproConfiguration&gt;&amp;sap-ep-iviewid=&lt;IView.ShortID&gt;&amp;sap-ep-pcdunit=&lt;IView.PCDUnit.ShortID&gt;&amp;sap-client=&lt;System.client&gt;&amp;sap-language=&lt;Request.Language&gt;&amp;sap-accessibility=&lt;User.Accessibility[SAP_BOOL]&gt;&amp;sap-rtl=&lt;LAF.RightToLeft[SAP_BOOL]&gt;&amp;sap-ep-version=&lt;Portal.Version[url_ENCODE]&gt;&amp;sap-wd-tstamp=&lt;$TimeStamp&gt;&amp;&lt;FPNInfo[IF_false PROCESS_RECURSIVE]&gt;&amp;sap-explanation=&lt;User.Explanation[SAP_BOOL]&gt;&amp;&lt;StylesheetIntegration[IF_true PROCESS_RECURSIVE]&gt;&amp;&lt;Authentication&gt;&amp;&lt;DynamicParameter[PARAMETER_MAPPING PROCESS_RECURSIVE]&gt;&amp;&lt;ForwardParameters[QUERYSTRING]&gt;&amp;&lt;ApplicationParameter[PROCESS_RECURSIVE]&gt;&\#39;; the problem occured at position 310. Cannot process expression &lt;System.client&gt; because Invalid System Attribute:
    System:    &amp;\#39;SAP_LocalSystem&amp;\#39;,
    Attribute: &amp;\#39;client&amp;\#39;.
         at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doContentPass(AbstractIntegratorComponent.java:125)
         at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doContent(AbstractIntegratorComponent.java:98)
         at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
         at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
         at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
         ... 29 more
    #1.5 #00144FF922BF006B00000028000021AF0004B9F256577D3A#1330350388639#com.sap.portal.prt.runtime#sap.com/irj#com.sap.portal.prt.runtime#J2EE_ADM_EDJ#73##ERPDEV_EDJ_16184750#J2EE_ADM_EDJ#d2df5090614511e1cbb100144ff922bf#SAPEngine_Application_Thread[impl:3]_20##0#0#Error##Java###07:16_27/02/12_0004_16184750
    [EXCEPTION]
    #1#com.sapportals.portal.prt.runtime.PortalRuntimeException: Exception in SAP Application Integrator occured: Unable to parse template &\#39;&lt;System.Access.WAS.protocol&gt;://&lt;System.Access.WAS.hostname&gt;/sap/bc/webdynpro/&lt;WebDynproNamespace&gt;/&lt;WebDynproApplication&gt;/;sap-ext-sid=&lt;ESID[url_ENCODE]&gt;?sap-ep-iviewhandle=007&lt;ESID[HASH]&gt;&amp;sap-wd-configId=&lt;WebDynproConfiguration&gt;&amp;sap-ep-iviewid=&lt;IView.ShortID&gt;&amp;sap-ep-pcdunit=&lt;IView.PCDUnit.ShortID&gt;&amp;sap-client=&lt;System.client&gt;&amp;sap-language=&lt;Request.Language&gt;&amp;sap-accessibility=&lt;User.Accessibility[SAP_BOOL]&gt;&amp;sap-rtl=&lt;LAF.RightToLeft[SAP_BOOL]&gt;&amp;sap-ep-version=&lt;Portal.Version[url_ENCODE]&gt;&amp;sap-wd-tstamp=&lt;$TimeStamp&gt;&amp;&lt;FPNInfo[IF_false PROCESS_RECURSIVE]&gt;&amp;sap-explanation=&lt;User.Explanation[SAP_BOOL]&gt;&amp;&lt;StylesheetIntegration[IF_true PROCESS_RECURSIVE]&gt;&amp;&lt;Authentication&gt;&amp;&lt;DynamicParameter[PARAMETER_MAPPING PROCESS_RECURSIVE]&gt;&amp;&lt;ForwardParameters[QUERYSTRING]&gt;&amp;&lt;ApplicationParameter[PROCESS_RECURSIVE]&gt;&\#39;; the problem occured at position 310. Cannot process expression &lt;System.client&gt; because Invalid System Attribute:
    System:    &amp;\#39;SAP_LocalSystem&amp;\#39;,
    Attribute: &amp;\#39;client&amp;\#39;.
         at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doContentPass(AbstractIntegratorComponent.java:125)
         at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doContent(AbstractIntegratorComponent.java:98)
         at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
         at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
         at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
         at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215)
         at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:645)
         at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
         at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:753)
         at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:235)
         at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:541)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:430)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
    #1.5 #00144FF922BF006A0000001E000021AF0004B9F25959F274#1330350439133#com.sap.mw.jco#sap.com/tcwddispwda#com.sap.mw.jco#ESSEMP2#288##ERPDEV_EDJ_16184750#ESSEMP2#907dd803614911e1968500144ff922bf#SAPEngine_Application_Thread[impl:3]_6##0#0#Info##Plain###[WD JCO API] WebDynproExtension.addClientPool(SAP_R3_SelfServiceGenerics_ESSEMP2_EN_useSSO_(J2EE16184700)ID1578814350DB10044082816827940554End_9513223) with lang 'EN' and languages vector {EN,EN}#
    #1.5 #00144FF922BF0062000016D7000021AF0004B9F26C7D264E#1330350760207#com.sap.tc.cbs.server.proc.RequestHandler##com.sap.tc.cbs.server.proc.RequestHandler####n/a##eed5c7ef614411e1996800144ff922bf#Thread[SAPEngine_System_Thread[impl:5]_Group - 207,10,SAPEngine_System_Thread[impl:5]_Group]##0#0#Error#1#/Applications/CBSRequestLog/RequestProcessing/id1736980#Plain###Error! The following problem(s) occurred  during request processing:#
    #1.5 #00144FF922BF0062000016D9000021AF0004B9F26C7D286A#1330350760208#com.sap.tc.cbs.server.proc.RequestHandler##com.sap.tc.cbs.server.proc.RequestHandler####n/a##eed5c7ef614411e1996800144ff922bf#Thread[SAPEngine_System_Thread[impl:5]_Group - 207,10,SAPEngine_System_Thread[impl:5]_Group]##0#0#Error#1#/Applications/CBSRequestLog/RequestProcessing/id1736980#Java###Error! Request failed due to failure of child requests#1#Request failed due to failure of child requests#
    #1.5 #00144FF922BF0062000016DB000021AF0004B9F26C7D2DAC#1330350760209#com.sap.tc.cbs.server.proc.RequestHandler##com.sap.tc.cbs.server.proc.RequestHandler####n/a##eed5c7ef614411e1996800144ff922bf#Thread[SAPEngine_System_Thread[impl:5]_Group - 207,10,SAPEngine_System_Thread[impl:5]_Group]##0#0#Error#1#/Applications/CBS/Service#Java###Request failed due to failure of child requests
    [EXCEPTION]
    #1#Request failed due to failure of child requests
         at com.sap.tc.cbs.server.dao.impl.Request.checkForFailedChildRequests(Request.java:494)
         at com.sap.tc.cbs.server.dao.impl.Request.capture(Request.java:398)
         at com.sap.tc.cbs.server.proc.RequestHandler.process(RequestHandler.java:138)
         at com.sap.tc.cbs.server.proc.RequestHandler.run(RequestHandler.java:121)
         at com.sap.tc.cbs.server.rt.threads.PerpetualRunnable.run(PerpetualRunnable.java:109)
    #1.5 #00144FF922BF006200001777000021AF0004B9F26FD235FC#1330350816114#com.sap.tc.cbs.server.proc.RequestHandler##com.sap.tc.cbs.server.proc.RequestHandler####n/a##eed5c7ef614411e1996800144ff922bf#Thread[SAPEngine_System_Thread[impl:5]_Group - 207,10,SAPEngine_System_Thread[impl:5]_Group]##0#0#Error#1#/Applications/CBSRequestLog/RequestProcessing/id1736988#Plain###            Error! The following problem(s) occurred  during request processing:#
    #1.5 #00144FF922BF006200001779000021AF0004B9F26FD23863#1330350816114#com.sap.tc.cbs.server.proc.RequestHandler##com.sap.tc.cbs.server.proc.RequestHandler####n/a##eed5c7ef614411e1996800144ff922bf#Thread[SAPEngine_System_Thread[impl:5]_Group - 207,10,SAPEngine_System_Thread[impl:5]_Group]##0#0#Error#1#/Applications/CBSRequestLog/RequestProcessing/id1736988#Plain###            Error! The following error occurred during request processing:The build failed due to wrong or incomplete arguments, passed to the build tool.
    Please check CBS service parameters against manual.#
    #1.5 #00144FF922BF006600001720000021AF0004B9F26FFE4EC5#1330350819004#com.sap.tc.cbs.server.proc.RequestHandler##com.sap.tc.cbs.server.proc.RequestHandler####n/a##f556c50a614411e19dc200144ff922bf#Thread[SAPEngine_System_Thread[impl:5]_Group - 208,10,SAPEngine_System_Thread[impl:5]_Group]##0#0#Error#1#/Applications/CBSRequestLog/RequestProcessing/id1736987#Plain###            Error! The following problem(s) occurred  during request processing:#
    #1.5 #00144FF922BF006600001722000021AF0004B9F26FFE50DC#1330350819004#com.sap.tc.cbs.server.proc.RequestHandler##com.sap.tc.cbs.server.proc.RequestHandler####n/a##f556c50a614411e19dc200144ff922bf#Thread[SAPEngine_System_Thread[impl:5]_Group - 208,10,SAPEngine_System_Thread[impl:5]_Group]##0#0#Error#1#/Applications/CBSRequestLog/RequestProcessing/id1736987#Plain###            Error! The following error occurred during request processing:The build failed due to wrong or incomplete arguments, passed to the build tool.
    Please check CBS service parameters against manual.#
    #1.5 #00144FF922BF005F0000179B000021AF0004B9F2714FA0E9#1330350841110#com.sap.tc.cbs.server.proc.RequestHandler##com.sap.tc.cbs.server.proc.RequestHandler####n/a##eeb712eb614411e1926f00144ff922bf#Thread[SAPEngine_System_Thread[impl:5]_Group - 206,10,SAPEngine_System_Thread[impl:5]_Group]##0#0#Error#1#/Applications/CBSRequestLog/RequestProcessing/id1736989#Plain###Error! The following problem(s) occurred  during request processing:#
    #1.5 #00144FF922BF005F0000179D000021AF0004B9F2714FA2FC#1330350841111#com.sap.tc.cbs.server.proc.RequestHandler##com.sap.tc.cbs.server.proc.RequestHandler####n/a##eeb712eb614411e1926f00144ff922bf#Thread[SAPEngine_System_Thread[impl:5]_Group - 206,10,SAPEngine_System_Thread[impl:5]_Group]##0#0#Error#1#/Applications/CBSRequestLog/RequestProcessing/id1736989#Java###Error! Request failed due to failure of child requests#1#Request failed due to failure of child requests#
    #1.5 #00144FF922BF005F0000179F000021AF0004B9F2714FA854#1330350841111#com.sap.tc.cbs.server.proc.RequestHandler##com.sap.tc.cbs.server.proc.RequestHandler####n/a##eeb712eb614411e1926f00144ff922bf#Thread[SAPEngine_System_Thread[impl:5]_Group - 206,10,SAPEngine_System_Thread[impl:5]_Group]##0#0#Error#1#/Applications/CBS/Service#Java###Request failed due to failure of child requests
    [EXCEPTION]
    #1#Request failed due to failure of child requests
         at com.sap.tc.cbs.server.dao.impl.Request.checkForFailedChildRequests(Request.java:494)
         at com.sap.tc.cbs.server.dao.impl.Request.capture(Request.java:398)
         at com.sap.tc.cbs.server.proc.RequestHandler.process(RequestHandler.java:138)
         at com.sap.tc.cbs.server.proc.RequestHandler.run(RequestHandler.java:121)
         at com.sap.tc.cbs.server.rt.threads.PerpetualRunnable.run(PerpetualRunnable.java:109)
    cbs.5:
    #1.5 #00144FF922BF006E00009D0900000EEE0004B9E196C2E0E9#1330278454976#/Applications/CBS/Service##com.sap.tc.cbs.server.rt.sync.AccessOrc####n/a##446ca3fd5c7b11e195a000144ff922bf#Thread[CBS AccessQueue Orchestrator,10,SAPEngine_System_Thread[impl:5]_Group]##0#0#Error#1#/Applications/CBS/Service#Plain###Access orchestrator failure#
    #1.5 #00144FF922BF006E00009D1100000EEE0004B9E196C49580#1330278455088#/Applications/CBS/Service##com.sap.tc.cbs.server.rt.sync.AccessOrc####n/a##446ca3fd5c7b11e195a000144ff922bf#Thread[CBS AccessQueue Orchestrator,10,SAPEngine_System_Thread[impl:5]_Group]##0#0#Error#1#/Applications/CBS/Service#Plain###Access orchestrator failure#
    #1.5 #00144FF922BF006E00009D1900000EEE0004B9E196C664FD#1330278455207#/Applications/CBS/Service##com.sap.tc.cbs.server.rt.sync.AccessOrc####n/a##446ca3fd5c7b11e195a000144ff922bf#Thread[CBS AccessQueue Orchestrator,10,SAPEngine_System_Thread[impl:5]_Group]##0#0#Error#1#/Applications/CBS/Service#Plain###Access orchestrator failure#
    #1.5 #00144FF922BF006E00009D2100000EEE0004B9E196C81B65#1330278455319#/Applications/CBS/Service##com.sap.tc.cbs.server.rt.sync.AccessOrc####n/a##446ca3fd5c7b11e195a000144ff922bf#Thread[CBS AccessQueue Orchestrator,10,SAPEngine_System_Thread[impl:5]_Group]##0#0#Error#1#/Applications/CBS/Service#Plain###Access orchestrator failure#
    #1.5 #00144FF922BF00310000000000000DA90004B9F0155B9416#1330340708455#/Applications/CBS/Administration##com.sap.tc.cbs.service.CBSFrame#######SAPEngine_System_Thread[impl:5]_82##0#0#Info#1#com.sap.tc.cbs.service.CBSFrame#Java###Starting CBS service on node ...#1#16184750#
    Pls suggest

    Hi James Bond
    From the exception above, it can be seen that the AppIntegrator iView is trying to run on the "SAP_LocalSystem" where it should be running on a "real" backend system.
    Please check what is the System alias in this iView and make sure it points on a backend system which has the same alias in the Portal System landscape.
    Hope that helps,
    Robin Hood.

  • XI with ABAP stack only ?

    Looking at some very annoying problems with the XI Java Stack and applications (stability, memory consumption), following question comes to mind:
    is it technically possible to run an XI system without the Java stack ? How much functionality do we have in there, can we do customers projects with that ?
    In ABAP stack, we have the following functions:
    - Business Process Engine
    - Integration Engine
    - HTTP Adapter
    - IDoc Adapter
    - ABAP-Mapping (XSL or handmade)
    also, we have of course the functionality of using File/FTP,Mail in ABAP. This means the most important adapter types are available in ABAP (without needing the Java adapter engine).
    Of course the Integration Builder is not available then. But do we really need it ?? Same applies for the SLD.
    Are the pipeline objects (receiver determination, interface determination and so on) stored in the ABAP stack ? I assume that is the case. Does ABAP stack contain the XI message type objects ? Or is that stored in Java ?
    Anyone tried that path ? Is it already failing in the installation because some core XI ABAP components require Java parts ? Or would it work ?
    Of course the answer depends on "what do we define to be XI". For me it is the core integration engine with the pipeline architecture plus mapping and proxy extension points. Everything else (e.g. tools) needed can be built around it.
    Customer benefits would be: focus on ABAP only (Java knowhow not needed), easier administration and more stability.
    CSY

    Hello Jaishankar,
    > there is no transaction to replace Visual Admin (NWA from >PI7.1) functionality.
    question: suppose we are not using the J2EE stack of XI, do we need the NWA ? Does NWA also contain important functions which control/configure the ABAP stack ?
    >I would say Java and ABAP stacks are very tightly coupled >to each other and it would take ages to understand how >tightly it is coupled.
    this would be quite bad design then. But you may be right. Current cross-calls from ABAP to Java I know:
    - call Java-Mapping from ABAP pipeline. If we do not need Java mapping, this call is not needed. In ABAP, we have ABAP and XSLT mapping options
    - other ? What else ? I am talking about runtime execution (pipeline), not designer tools
    >For example XI is a client of SLD which runs on Java stack, >how do you think you can replace the functionality of SLD via
    yes. But what does XI need from SLD ? Business systems, target transports, ok. It's a handful of objects types which can easily be maintained in the ABAP stack also. For customers which are using the SAP portal or other Java components (apart from XI), of course, that makes no sense. But for smaller customers which do not use portal: for what do they really need that SLD ? I have seen one customer recently who didnt know about the transport targets and so maintained the IR objects on the productive system manually. More an education issue, but it shows a bit that the SLD for some customers is overkill.
    >improvised and will be done in the future versions. The long >term plan is to make XI a complete Java based tool. All the >developers tools will be accessed via NWDS in future"
    yes, I heard that also, and it is very interesting in fact. We will see what happens
    thanks for your input,
    CSY

  • A failure occured while importing Java SSO ticket certificate in ABAP stack Exception : FOREIGN_ENQUEUE_LOCK

    Dear All,
    We have completed the fresh installation of Soman7.1.
    Now , We are doing the "Configuration of the Solman" and we are in the Step "Basic configuration ".
    SID:        SMI
    Hostname: Solmantrg
    Solman version: 7.1
    The SSO Setup is failing with below error.
    Message :
    A failure occured while connecting to ABAP stack on solmantrg.thetimes.co.in sys=01 client=001 user=null. Details : 'user' missing
    Details of the Log
    Found SID for SSO ACL entry : SMI
    Found login.ticket_client for SSO ACL entry : 000
    The Read entry permission on TicketKeystore/SAPLogonTicketKeypair-cert was given to sap.com/tc~webadministrator~solmandiag/servlet_jsp/smd/root/WEB-INF/lib/SetupLib.jar
    The TicketKeystore/SAPLogonTicketKeypair-cert was succesfully read (619 bytes)
    ABAP SSO ticket certificate of SMI was imported in ABAP PSE of solmantrg.thetimes.co.in (client 001)
    The ABAP SSO ticket certificate was successfully imported in ABAP System PSE, and the ACL updated accordingly (SID=SMI LoginTicketClient=001)
    A failure occured while importing Java SSO ticket certificate in ABAP stack
    !! Exception : FOREIGN_ENQUEUE_LOCK(Abap cause=SOLMAN_ADMINE_TABLEE)
    The ABAP instance profile contains the parameter : login/accept_sso2_ticket=1
    The SSO ticket Certificate <CN=SMI> has been successfully imported into Java Keystore
    The com.sap.security.core.server.jaas.EvaluateTicketLoginModule already contained the entry : trustedsys=SMI, 001 trustediss=CN=SMI trusteddn=CN=SMI
    The Authentication template for component sap.com/SQLTrace*OpenSQLMonitors was already set to ticket
    The Authentication template for component sap.com/SQLTrace*SQLTrace was already set to ticket
    The Authentication template for component sap.com/tc~monitoring~systeminfo*monitoring was already set to ticket
    The Authentication template for component sap.com/tc~monitoring~systeminfo*sap_monitoring was already set to ticket
    The Authentication template for component sap.com/com.sap.security.core.admin*useradmin was already set to ticket
    The Authentication template for component sap.com/tc~webadministrator~solmandiag*smd was already set to ticket
    The Authentication template for component sap.com/tc~smd~e2etraceupload*E2EClientTraceUploadW was already set to ticket
    The com.sap.security.core.server.jaas.EvaluateAssertionTicketLoginModule already contained the entry : trustedsys=SMI, 001 trustediss=CN=SMI trusteddn=CN=SMI
    The Authentication template for component sap.com/tc~smd~EemAdminGateway*EemAdmin_Config1 has been set to evaluate_assertion_ticket
    The Login Module BasicPasswordLoginModule was added to the security component sap.com/tc~smd~EemAdminGateway*EemAdmin_Config1
    A failure occured while connecting to ABAP stack on solmantrg.thetimes.co.in sys=01 client=001 user=null
    !! Exception : 'user' missing
    The ABAP instance profile contains the parameter : login/create_sso2_ticket=2
      Exception
    com.sap.mw.jco.JCO$AbapException: (126) FOREIGN_ENQUEUE_LOCK: FOREIGN_ENQUEUE_LOCK
    at com.sap.mw.jco.MiddlewareJRfc$Client.execute(MiddlewareJRfc.java:1512)
    at com.sap.mw.jco.JCO$Client.execute(JCO.java:3937)
    at com.sap.mw.jco.JCO$Client.execute(JCO.java:3570)
    at com.sap.sup.admin.setup.AbapSysRfcAdapter.addTrustedIssuer(AbapSysRfcAdapter.java:276)
    at com.sap.sup.admin.setup.AbapSysRfcAdapter.addTrustedIssuer(AbapSysRfcAdapter.java:249)
    at com.sap.sup.admin.setup.ManagingServices.setupDualStackSSO(ManagingServices.java:752)
    at com.sap.sup.admin.setup.SetupStep.runExec(SetupStep.java:564)
    at com.sap.sup.admin.setup.SetupStep.execute(SetupStep.java:445)
    at com.sap.smd.agent.plugins.remotesetup.SapInstance.setup(SapInstance.java:674)
    at com.sap.sup.admin.setup.ws.SetupWrapper._diagSetup(SetupWrapper.java:279)
    at com.sap.sup.admin.setup.ws.SetupWrapper.diagSetup(SetupWrapper.java:21)
    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:331)
    at com.sap.engine.services.webservices.runtime.JavaClassImplementationContainer.invokeMethod(JavaClassImplementationContainer.java:76)
    at com.sap.engine.services.webservices.runtime.RuntimeProcessor.process(RuntimeProcessor.java:174)
    at com.sap.engine.services.webservices.runtime.RuntimeProcessor.process(RuntimeProcessor.java:81)
    at com.sap.engine.services.webservices.runtime.servlet.ServletDispatcherImpl.doPost(ServletDispatcherImpl.java:90)
    at SoapServlet.doPost(SoapServlet.java:51)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
    at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1060)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
    at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
    at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
    at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
    at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
    at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
    at java.security.AccessController.doPrivileged(Native Method)
    at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
    at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
    ========================
    com.sap.mw.jco.JCO$Exception: (101) RFC_ERROR_PROGRAM: 'user' missing
    at com.sap.mw.jco.MiddlewareJRfc.generateJCoException(MiddlewareJRfc.java:518)
    at com.sap.mw.jco.MiddlewareJRfc$Client.connect(MiddlewareJRfc.java:1087)
    at com.sap.mw.jco.JCO$Client.connect(JCO.java:3310)
    at com.sap.sup.admin.setup.CommonServices.getJcoClient(CommonServices.java:773)
    at com.sap.sup.admin.setup.CommonServices.getJcoClient(CommonServices.java:722)
    at com.sap.sup.admin.setup.SolManRfcAdapter.getJ2eeSsoSettings(SolManRfcAdapter.java:649)
    at com.sap.sup.admin.setup.ManagingServices.updateSSOfromURLrepository(ManagingServices.java:790)
    at com.sap.sup.admin.setup.ManagingServices.setupDualStackSSO(ManagingServices.java:773)
    at com.sap.sup.admin.setup.SetupStep.runExec(SetupStep.java:564)
    at com.sap.sup.admin.setup.SetupStep.execute(SetupStep.java:445)
    at com.sap.smd.agent.plugins.remotesetup.SapInstance.setup(SapInstance.java:674)
    at com.sap.sup.admin.setup.ws.SetupWrapper._diagSetup(SetupWrapper.java:279)
    at com.sap.sup.admin.setup.ws.SetupWrapper.diagSetup(SetupWrapper.java:21)
    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:331)
    at com.sap.engine.services.webservices.runtime.JavaClassImplementationContainer.invokeMethod(JavaClassImplementationContainer.java:76)
    at com.sap.engine.services.webservices.runtime.RuntimeProcessor.process(RuntimeProcessor.java:174)
    at com.sap.engine.services.webservices.runtime.RuntimeProcessor.process(RuntimeProcessor.java:81)
    at com.sap.engine.services.webservices.runtime.servlet.ServletDispatcherImpl.doPost(ServletDispatcherImpl.java:90)
    at SoapServlet.doPost(SoapServlet.java:51)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
    at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1060)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
    at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
    at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
    at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
    at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
    at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
    at java.security.AccessController.doPrivileged(Native Method)
    at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
    at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
    In strustsso2, cerficate date is valid only.
    kindly help us to fix this SSO_Setup issue
    Thanks and Regards,
    Gayathri.K

    Hi ,
    Thanks for the above reply.
    I have executed the Step 2.3 AND 2.4 and i started the SSO Setup again. Still i am getting below error
    Message
    A failure occured while importing Java SSO ticket certificate in ABAP stack
    Details Of the Log
    Found SID for SSO ACL entry : SMI
    Found login.ticket_client for SSO ACL entry : 000
    The Read entry permission on TicketKeystore/SAPLogonTicketKeypair-cert was given to sap.com/tc~webadministrator~solmandiag/servlet_jsp/smd/root/WEB-INF/lib/SetupLib.jar
    The TicketKeystore/SAPLogonTicketKeypair-cert was succesfully read (619 bytes)
    ABAP SSO ticket certificate of SMI was imported in ABAP PSE of solmantrg (client 001)
    The ABAP SSO ticket certificate was successfully imported in ABAP System PSE, and the ACL updated accordingly (SID=SMI LoginTicketClient=001)
    A failure occured while importing Java SSO ticket certificate in ABAP stack
    !! Exception : FOREIGN_ENQUEUE_LOCK(Abap cause=SOLMAN_ADMINE_TABLEE)
    The ABAP instance profile contains the parameter : login/accept_sso2_ticket=1
    The SSO ticket Certificate <CN=SMI> has been successfully imported into Java Keystore
    The com.sap.security.core.server.jaas.EvaluateTicketLoginModule already contained the entry : trustedsys=SMI, 001 trustediss=CN=SMI trusteddn=CN=SMI
    The Authentication template for component sap.com/SQLTrace*OpenSQLMonitors was already set to ticket
    The Authentication template for component sap.com/SQLTrace*SQLTrace was already set to ticket
    The Authentication template for component sap.com/tc~monitoring~systeminfo*monitoring was already set to ticket
    The Authentication template for component sap.com/tc~monitoring~systeminfo*sap_monitoring was already set to ticket
    The Authentication template for component sap.com/com.sap.security.core.admin*useradmin was already set to ticket
    The Authentication template for component sap.com/tc~webadministrator~solmandiag*smd was already set to ticket
    The Authentication template for component sap.com/tc~smd~e2etraceupload*E2EClientTraceUploadW was already set to ticket
    The com.sap.security.core.server.jaas.EvaluateAssertionTicketLoginModule already contained the entry : trustedsys=SMI, 001 trustediss=CN=SMI trusteddn=CN=SMI
    The Authentication template for component sap.com/tc~smd~EemAdminGateway*EemAdmin_Config1 has been set to evaluate_assertion_ticket
    The Login Module BasicPasswordLoginModule was added to the security component sap.com/tc~smd~EemAdminGateway*EemAdmin_Config1
    The ABAP instance profile contains the parameter : login/create_sso2_ticket=2
    Exception
    com.sap.mw.jco.JCO$AbapException: (126) FOREIGN_ENQUEUE_LOCK: FOREIGN_ENQUEUE_LOCK
    at com.sap.mw.jco.MiddlewareJRfc$Client.execute(MiddlewareJRfc.java:1512)
    at com.sap.mw.jco.JCO$Client.execute(JCO.java:3937)
    at com.sap.mw.jco.JCO$Client.execute(JCO.java:3570)
    at com.sap.sup.admin.setup.AbapSysRfcAdapter.addTrustedIssuer(AbapSysRfcAdapter.java:276)
    at com.sap.sup.admin.setup.AbapSysRfcAdapter.addTrustedIssuer(AbapSysRfcAdapter.java:249)
    at com.sap.sup.admin.setup.ManagingServices.setupDualStackSSO(ManagingServices.java:752)
    at com.sap.sup.admin.setup.SetupStep.runExec(SetupStep.java:564)
    at com.sap.sup.admin.setup.SetupStep.execute(SetupStep.java:445)
    at com.sap.smd.agent.plugins.remotesetup.SapInstance.setup(SapInstance.java:674)
    at com.sap.sup.admin.setup.ws.SetupWrapper._diagSetup(SetupWrapper.java:279)
    at com.sap.sup.admin.setup.ws.SetupWrapper.diagSetup(SetupWrapper.java:21)
    at sun.reflect.GeneratedMethodAccessor2202.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:331)
    at com.sap.engine.services.webservices.runtime.JavaClassImplementationContainer.invokeMethod(JavaClassImplementationContainer.java:76)
    at com.sap.engine.services.webservices.runtime.RuntimeProcessor.process(RuntimeProcessor.java:174)
    at com.sap.engine.services.webservices.runtime.RuntimeProcessor.process(RuntimeProcessor.java:81)
    at com.sap.engine.services.webservices.runtime.servlet.ServletDispatcherImpl.doPost(ServletDispatcherImpl.java:90)
    at SoapServlet.doPost(SoapServlet.java:51)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
    at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1060)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
    at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
    at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
    at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
    at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
    at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
    at java.security.AccessController.doPrivileged(Native Method)
    at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
    at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
    Also , i have checked the note # 1008474   Diagnostics Setup Wizard uses wrong ABAP client.
    As mentioned in above note, i have checked in visual admin all settings are maintained correctly.
    RFC destination WEBADMIN & SOLMANDIAG is also working fine.
    please tel why i am getting Foreign Enquelock
    Regards,
    Gayathri.K

  • Communication between UME on the Java Stack and ABAP Stack

    Please look for the thread
    Unable to log on to IR, ID, SLD....
    before going any further. This thread follows.
    The prob in brief is that,
    On XI homepage, I am not able to get into anything after I entered the user name and pw.
    I have some roles SAP_XI_ADMINISTRATOR for my user. I have checked in SU01 on ABAP Stack.
    I thought that the error could be that the UME on the Java Stack is not able to communicate with the ABAP stack.
    Any direction on this would really help me.
    Regards,
    -Naveen.

    Can any one help me in this.
    -Naveen.

  • SMSY for ERP JAVA and ABAP Stack

    Hi Folks - I have installed SAP ERP 6.0 EHP5 in one database called T12. Now there is a need for a Java stack and I have installed the Java stack in another database called J12.
    I was able to define the ABAP stack on system landscape and MOPZ is working fine. However, I am not sure how I should go about the Java (J12) instance definidstion on SMSY.
    I am using Somlam 7.1 on Oracle Linux system.
    ABAP stack is on ERL 6.0 EHP5 and Java stack is Netweaver 7.0 EHP2.
    J12 and T12 systems are connected via JCO.
    SLD has been defined for both stacks and they are using the local SLD for the SolMan.
    Your help is much appriciated.

    Sunny - I checked the SLD and It is working fine. There were couple of issues that I fixed. Since I defined the Java system manually I delete it. Hopefully SLD will populate the definition.
    In same note, Would it be possible that installing ERP java and ABAP stack on different hosts (stand alone) is causing this issue, especially they are using different Sid's?
    I was reading SAP Note 1344564, It states
    III.Some Main Instances include other Main Instances (E.g., in SAP
    ERP 6.0, Main Instance SAP NW - Enterprise Portal includes SAP NW -
    EP Core.). If the including Main Instance is installed, it's not
    necessary to mark the included Main Instance(s) for relevance.
    Is this mean in SMSY I do not have to define any product for the Java engine? When installing the Java, I had to create the product manually to be able to generate the installation key.
    Your input is appreciated.
    Edited by: kourosh Ghouchkhani on Nov 22, 2011 1:20 AM

  • Register MOSS system in SLD

    Hello Experts,
    I'd like to know if there is some way I could register a MOSS system (defined as far as I know as a 3rd party system) as a technical system into the SLD?
    As for now, any ABAP or J2EE system is registered automatically to the SLD during installation. What is the case regarding a MOSS system? can it be defined as a Data_Supplier to a SLD_Client?
    Thanks,
    Tomer

    Hello Tomer,
    Its possible.
    Please check https://websmp101.sap-ag.de/~sapidb/011000358700000315592008E
    Regards,
    Abhay

  • How to read ABAP STACK of another report

    Hi,
    I wish to read the ABAP STACK of another report which may or may not be running in debugging mode.
    First of all is it possible. if yes then pls reply.
    Thanks

    Hhhmm, ok, then I really didn't understand your request. Here's something that might come closer, but is actually of questionable value due to timing issues: Assuming that you know already the debugging takes place on the same application server you could call function module TH_GET_WPINFO and check for any processes with WP_WAITING = 'Debug'. For those take the work process number WP_NO and get the details via TH_WP_DETAIL_INFO (feeding the work process number into WP_INDEX and evaluating the parameter DIAREC-REPORT. However, this doesn't give you call stack and I'm pretty sure it always just contains the current main program that's running. Not to mention the fact that between the calls the debugging might have ended... (though in the second call it seems that WP_INFO-WP_ISTATUS = 8 seems to indicate that process is in debugging from the few tests that I did).

  • How register the ECC to SLD

    Hi All,
    I know the we could use RZ70 to register the ABAP system to SLD
    but it seems RZ70 only could register it as the technical system in SLD
    but i am wondering is it possible to register the client as the business system in SLD?
    let's say: ECC host is erp, and the client is 100, how to register ERPCLNT100 into SLD automatically???
    thanks a lot

    hello,
    Please go though the Below URL PDF file ..
    It will surely Help you...
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/204994f3-0e44-2a10-17b3-808fbd8db4aa
    Regrads,
    Vivekanand Pandey

  • Register MOSS system to SLD

    Hello Experts,
    I'd like to know if there is some way I could register a MOSS system (defined as far as I know as a 3rd party system) as a technical system into the SLD?
    As for now, any ABAP or J2EE system is registered automatically to the SLD during installation. What is the case regarding a MOSS system? can it be defined as a Data_Supplier to a SLD_Client?
    Thanks,
    Tomer

    Maybe you can use sldreg?
    Install saposcol and sldreg on windows machine. Use saposcol to generate Hardware Information XML and then use sldreg to send this information to SLD.
    http://help.sap.com/saphelp_nw70/helpdata/en/42/efba5e93d51bc9e10000000a11466f/content.htm

  • XISUPER can't log into IB and ID but log into SLD ok

    XI 3.0 SR1 is up and running, I can log into RWB and SLD with user XISUPER and password, however when I attempt to log in with XISUPER and password after the webstart kickoff it says "Authorization error username or password incorrect"...however i have proven that it is correct because I can log into SLD and RWB with said user...
    Has anyone seen this before?
    Thanks
    John Ryan

    Hi John,
    pls check the XIsuper has same pswd in SU01(abap stack)
    and exchangeProfile(java stack) for IR and ID services. It you have changed the pswd at any said places you will face this kind of problem. First set the pswd in su01 and than in exchangeProfile.
    have a great time
    Satish

Maybe you are looking for