Support package stack 11 (Java and ABAP)

Does anybody have any experience with the latest support package stack 11 already? Are there some problems solved, and more important: are there new errors introduced?
Thanks for your help.

Hi Deepu,
Thanks for your reaction. I'm familiar with this OSS note. I'm mainly curious to customer experiences who have already implemented it. This SPS will solve some of our problems, but we're a little scared for the new errors that will be introduced with it.
Guus

Similar Messages

  • JAVA and ABAP stack support pakages

    Hi,
    I am new on installation of solution manager server.
    I just install solution manager server EHP1 on windows 2003. Now I want to patch my server.
    I have abap and java stack on my server. Can I use jspm to upload my new patches for both Java and ABAP stack or I should use SPAM for abap stack and jspm for java.
    Thanks Reza

    Hello Reza,
    Just to clarify, Best practise is to update your kernel to the latest before you start patching in your system.
    So download SAPEXE.SAR (Database independent kernel package), SAPEXEDB (Database dependent kernel package) and IGSEXE.SAR (IGS Package) from the SMP. kernel is dependent on your operating system and database and therefore make sure you download the right package otherwise you'll end up in messing up the system.
    follow SAPnote # 19466 for help.
    Once you are done with the kernel update then patch you Abap stack by SPAM and JAva stack by JSPM.
    I hope that makes things clear.
    Best Regards
    NIraj

  • Update Java Support Package Stack in JSPM

    Hi all,
    When i update Java Support Package Stack in JSPM i can't start the dispatcher
    [Thr 920] JLaunchIExitJava: exit hook is called (rc = -11113)
    [Thr 920] **********************************************************************
    ERROR => The Java VM terminated with a non-zero exit code.
    Please see SAP Note 943602 , section 'J2EE Engine exit codes'
    for additional information and trouble shooting.
    [Thr 920] JLaunchCloseProgram: good bye (exitcode = -11113)
    When i goto the log-file of the dispatcher (server.0.log):
    E:
    usr
    sap
    P01
    DVEBMGS01
    j2ee
    cluster
    dispatcher
    bin
    services
    log_configurator
    log_configurator.jar
    Loading model: {parent,local,references}
    The error occurred while trying to load "com.sap.engine.services.log_configurator.LogInterfaceImpl".
         at com.sap.engine.frame.core.load.ReferencedLoader.loadClass(ReferencedLoader.java:401)
         at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302)
         at com.sap.engine.services.log_configurator.LogConfiguratorServiceFrameImpl.init(LogConfiguratorServiceFrameImpl.java:156)
         at com.sap.engine.services.log_configurator.LogConfiguratorServiceFrameImpl.start(LogConfiguratorServiceFrameImpl.java:127)
         at com.sap.engine.core.service630.container.ServiceRunner.startCommunicationServiceFrame(ServiceRunner.java:228)
         at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:158)
         at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
         at com.sap.engine.core.thread.impl6.SingleThread.execute(SingleThread.java:82)
         at com.sap.engine.core.thread.impl6.SingleThread.run(SingleThread.java:154)
    #1.5 #0050569379EA000A00000004000010880004B40696AFED19#1323840297756#/System/Server##com.sap.engine.core.service630.container.ServiceRunner#######SAPEngine_System_Thread[impl:6]_32##0#0#Error#1#/System/Server#Plain###Core service log_configurator failed. J2EE Engine cannot be started.#
    #1.5 #0050569379EA000A00000006000010880004B40696AFF1F0#1323840297756#/System/Server/Critical##com.sap.engine.core.Framework#######SAPEngine_System_Thread[impl:6]_32##0#0#Fatal#1#com.sap.engine.core.Framework#Plain###Critical shutdown was invoked. Reason is: Core service log_configurator failed. J2EE Engine cannot be started.#
    Somebody know how to solve this problem?
    Thanks in advance,
    Cheung

    defaulttrc.0.trc"
    <!LOGHEADER[START]/>
    <!HELP[Manual modification of the header may cause parsing problem!]/>
    <!LOGGINGVERSION[1.5.3.7185 - 630]/>
    <!NAME[./log/defaultTrace.trc]/>
    <!PATTERN[defaultTrace.trc]/>
    <!FORMATTER[com.sap.tc.logging.ListFormatter]/>
    <!ENCODING[UTF8]/>
    <!FILESET[0, 2, 10485760]/>
    <!PREVIOUSFILE[defaultTrace.1.trc]/>
    <!NEXTFILE[defaultTrace.1.trc]/>
    <!LOGHEADER[END]/>
    #1.5 #0050569379EA001500000D53000016300004B40029F81C09#1323812703907#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###com.sapportals.portal.prt.runtime.PortalRuntimeException: [ApplicationItem.release]: SAPJ2EE::sap.com/tcwd4vccorestdinfoactors#
    #1.5 #0050569379EA001500000D54000016300004B40029F8209A#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sapportals.portal.prt.core.broker.ApplicationItem.release(ApplicationItem.java:506)#
    #1.5 #0050569379EA001500000D55000016300004B40029F82100#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sapportals.portal.prt.core.broker.PortalAppBroker.releaseAllItems(PortalAppBroker.java:590)#
    #1.5 #0050569379EA001500000D56000016300004B40029F82147#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sapportals.portal.prt.core.broker.PortalAppBroker.shutdown(PortalAppBroker.java:672)#
    #1.5 #0050569379EA001500000D57000016300004B40029F8218D#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sapportals.portal.prt.runtime.Portal.shutdown(Portal.java:725)#
    #1.5 #0050569379EA001500000D58000016300004B40029F821D1#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sapportals.portal.prt.core.PortalCoreInitializer.shutdown(PortalCoreInitializer.java:111)#
    #1.5 #0050569379EA001500000D59000016300004B40029F82215#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sapportals.portal.prt.dispatcher.PortalInitializer.shutdown(PortalInitializer.java:164)#
    #1.5 #0050569379EA001500000D5A000016300004B40029F8225A#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sapportals.portal.prt.dispatcher.Dispatcher.destroy(Dispatcher.java:651)#
    #1.5 #0050569379EA001500000D5B000016300004B40029F8229E#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sap.engine.services.servlets_jsp.server.runtime.context.WebComponents.destroyServlets(WebComponents.java:722)#
    #1.5 #0050569379EA001500000D5C000016300004B40029F822E4#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sap.engine.services.servlets_jsp.server.container.ApplicationThreadDestroyer.run(ApplicationThreadDestroyer.java:62)#
    #1.5 #0050569379EA001500000D5D000016300004B40029F82329#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)#
    #1.5 #0050569379EA001500000D5E000016300004B40029F8236C#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at java.security.AccessController.doPrivileged(Native Method)#
    #1.5 #0050569379EA001500000D5F000016300004B40029F823AF#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)#
    #1.5 #0050569379EA001500000D60000016300004B40029F823F3#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)#
    #1.5 #0050569379EA001500000D61000016300004B40029F826A8#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###Caused by: com.sapportals.portal.prt.runtime.PortalRuntimeException: Exception during stop of application: SAPJ2EE::sap.com/tcwd4vccorestdinfoactors#
    #1.5 #0050569379EA001500000D62000016300004B40029F82700#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sapportals.portal.prt.core.broker.SAPJ2EEApplicationItem.releaseResources(SAPJ2EEApplicationItem.java:162)#
    #1.5 #0050569379EA001500000D63000016300004B40029F82747#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sapportals.portal.prt.core.broker.ApplicationItem.release(ApplicationItem.java:479)#
    #1.5 #0050569379EA001500000D64000016300004B40029F8278A#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     ... 12 more#
    #1.5 #0050569379EA001500000D65000016300004B40029F82AA4#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###Caused by: java.lang.NullPointerException#
    #1.5 #0050569379EA001500000D66000016300004B40029F82AF6#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sap.portal.prt.sapj2ee.SAPJ2EEPortalRuntime.getSAPJ2EEApplicationState(SAPJ2EEPortalRuntime.java:630)#
    #1.5 #0050569379EA001500000D67000016300004B40029F82B41#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sapportals.portal.prt.service.sapj2ee.Mediator.getSAPJ2EEApplicationState(Mediator.java:216)#
    #1.5 #0050569379EA001500000D68000016300004B40029F82B87#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sapportals.portal.prt.core.broker.SAPJ2EEApplicationItem.releaseResources(SAPJ2EEApplicationItem.java:121)#
    #1.5 #0050569379EA001500000D69000016300004B40029F82BCB#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     ... 13 more#
    #1.5 #0050569379EA001500000D6A000016300004B40029F82D15#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###com.sapportals.portal.prt.runtime.PortalRuntimeException: [ApplicationItem.release]: SAPJ2EE::sap.com/com.sapportals.connectors.sap#
    #1.5 #0050569379EA001500000D6B000016300004B40029F82FE9#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sapportals.portal.prt.core.broker.ApplicationItem.release(ApplicationItem.java:506)#
    #1.5 #0050569379EA001500000D6C000016300004B40029F8303F#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sapportals.portal.prt.core.broker.PortalAppBroker.releaseAllItems(PortalAppBroker.java:590)#
    #1.5 #0050569379EA001500000D6D000016300004B40029F83085#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sapportals.portal.prt.core.broker.PortalAppBroker.shutdown(PortalAppBroker.java:672)#
    #1.5 #0050569379EA001500000D6E000016300004B40029F830E5#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sapportals.portal.prt.runtime.Portal.shutdown(Portal.java:725)#
    #1.5 #0050569379EA001500000D6F000016300004B40029F8312A#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sapportals.portal.prt.core.PortalCoreInitializer.shutdown(PortalCoreInitializer.java:111)#
    #1.5 #0050569379EA001500000D70000016300004B40029F8316F#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sapportals.portal.prt.dispatcher.PortalInitializer.shutdown(PortalInitializer.java:164)#
    #1.5 #0050569379EA001500000D71000016300004B40029F831B4#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sapportals.portal.prt.dispatcher.Dispatcher.destroy(Dispatcher.java:651)#
    #1.5 #0050569379EA001500000D72000016300004B40029F831F8#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sap.engine.services.servlets_jsp.server.runtime.context.WebComponents.destroyServlets(WebComponents.java:722)#
    #1.5 #0050569379EA001500000D73000016300004B40029F8323E#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sap.engine.services.servlets_jsp.server.container.ApplicationThreadDestroyer.run(ApplicationThreadDestroyer.java:62)#
    #1.5 #0050569379EA001500000D74000016300004B40029F83283#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)#
    #1.5 #0050569379EA001500000D75000016300004B40029F832C9#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at java.security.AccessController.doPrivileged(Native Method)#
    #1.5 #0050569379EA001500000D76000016300004B40029F8330C#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)#
    #1.5 #0050569379EA001500000D77000016300004B40029F83350#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)#
    #1.5 #0050569379EA001500000D78000016300004B40029F835C4#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###Caused by: com.sapportals.portal.prt.runtime.PortalRuntimeException: Exception during stop of application: SAPJ2EE::sap.com/com.sapportals.connectors.sap#
    #1.5 #0050569379EA001500000D79000016300004B40029F8361A#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sapportals.portal.prt.core.broker.SAPJ2EEApplicationItem.releaseResources(SAPJ2EEApplicationItem.java:162)#
    #1.5 #0050569379EA001500000D7A000016300004B40029F83662#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sapportals.portal.prt.core.broker.ApplicationItem.release(ApplicationItem.java:479)#
    #1.5 #0050569379EA001500000D7B000016300004B40029F836AA#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     ... 12 more#
    #1.5 #0050569379EA001500000D7C000016300004B40029F83A09#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###Caused by: java.lang.NullPointerException#
    #1.5 #0050569379EA001500000D7D000016300004B40029F83A67#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sap.portal.prt.sapj2ee.SAPJ2EEPortalRuntime.getSAPJ2EEApplicationState(SAPJ2EEPortalRuntime.java:630)#
    #1.5 #0050569379EA001500000D7E000016300004B40029F83AAF#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sapportals.portal.prt.service.sapj2ee.Mediator.getSAPJ2EEApplicationState(Mediator.java:216)#
    #1.5 #0050569379EA001500000D7F000016300004B40029F83AF5#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     at com.sapportals.portal.prt.core.broker.SAPJ2EEApplicationItem.releaseResources(SAPJ2EEApplicationItem.java:121)#
    #1.5 #0050569379EA001500000D80000016300004B40029F83B3A#1323812703922#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##9e83aed325d311e18905000000f14ae6#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###     ... 13 more#

  • Java and abap stack connection

    Hello,
    how to check connection b/w Java and ABAP stack.
    I am getting below error :
    SAP:Code area="MAPPING">JCO_SYSTEM_FAILURE</SAP:Code>
      <SAP:P1>connection to partner 'localhost:0' broken / CPIC-CALL: 'ThSAPCMRCV' : cmRc=20 t</SAP:P1>
    We did some upgrades of kernel and jvm and started getting this error.
    Please suggest

    Hi,
    Check this threads
    JCO_SYSTEM_FAILURE
    JCO_SYSTEM_FAILURE
    JCO_SYSTEM_FAILURE . Pls help
    Regards
    Ramesh

  • Latest DVDs of Support Package Stack for NW7.0, ERP 6.0, and Sol Man. 4.0

    Hi all,
    I want to request SAP the latest DVDs of Support Package Stack for NW7.0, ERP 6.0, and Sol Man. 4.0, is it possible & how to do it?
    Thanks,
    Toan Do

    Hi Toan,
    It's possible to order them or download them from SAP Marketplace
    http://service.sap.com/swdc
    Regards
    Juan

  • 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

  • Communicate link between Java and ABAP Stack for https

    I have configured https in both the java and abap stacks (we have a double stack configuration).  Due to our future configuration I have changed the hostnames to fully qualified hostnames per SAP instructions. 
    The question I have is does anyone know what RFC destinations or JCo settings I need to change to make https complete?
    I have the problem where when I fire off the Integration Builder from within the ABAP stack (SXMB_IFR) I get a straight hostname (no domain name).  Where is this configured?  Any help is appreciated..

    Check the exchange profile (Administratio tab in /rep/start/index.jsp page; you will have to enter it manually since it is throwing error from SXMB_IFR).
    Regards,
    Henrique.

  • Java and ABAP Stack

    Hi All,
    I am still not clear about role/function of java and abap stack in XI.
    Can anybody explain?

    Sireesha,
    Tha ABAP stack consists of the Integration Server which in turn contains your Integration Engine and Business Process Engine.
    The J2EE stack contains the Adapter Engine and your IR and ID run on the J2EE engine.
    Most of  XI pipelines happens in the ABAP stack.
    All messsages picked by the Adapter Framework running on the J2EE engine are passed to the Integration Engine, which does the routing. The mapping program again gets executed on the Java stack and the rest of the pipeline servies are executed again on the ABAP stack and so on.
    please go through links::
    ABAP and JAVA in Netweaver stack
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/media/uuid/4aa47d27-0a01-0010-5db4-bb62dfc8c069?prtmode=navigate

  • Difference between SAP support releases and SAP support package stacks ?

    Hi,
    Lets take SAP R3 Enterprise 47x200 (my company) as an example.
    Looks like there is SAP R3 Enterprise 47x200 release (from release notes) and SAP R3 Enterprise 47x200 SR1 (support release 1).
    And there are support package stacks for this release.
    What are the differences/similarities between these two ?
    Where can I find some document which explains these things as a whole ?
    There is enchancement packages introduced in SAP ERP 6.0, how EHP's relate to those two above ?
    thanks
    Vilius

    Hi
    Check this link [https://websmp101.sap-ag.de/~form/handler?_APP=00200682500000001303&_EVENT=DISP_NEW&00200682500000002804=01200615320900001087]
    For informations on EHP check this [www.service.sap.com/erp-ehp]
    Regards
    Uday

  • Syntax Error while applying support package stack 8

    I get the following short dump while I was applying support package stack 8.  I'm at the latest saint version 34
    Runtime Errors         SYNTAX_ERROR
    Date and Time          23.07.2009 14:09:27
    Short text
         Syntax error in program "CL_DYNPRO_PROPERTY_BAG========CP ".
    What happened?
         Error in the ABAP application program.
         The current ABAP program "SAPLSCR2" had to be interrupted because it con
         a statement that cannot be executed.
         In the include "CL_DYNPRO_PROPERTY_BAG========CM009 " in the line 176 of
          program "CL_DYNPRO_PROPERTY_BAG========CP " the following syntax
         errors occur:
         "The field "SPROP_C_TAG_CUSTOMPROPERTY" is unknown, but there is a fiel"
         "d with the similar name "SPROP_C_TAG_TOOLTIPTEXT". "SPROP_C_TAG_TOOLTI"
         "PTEXT"."
         Author and last person to change the include are:
         Author "SAP "
         Last changer "SAP "
    Error analysis
         The following syntax error was found in the program
          CL_DYNPRO_PROPERTY_BAG========CP :
         "The field "SPROP_C_TAG_CUSTOMPROPERTY" is unknown, but there is a fiel"
         "d with the similar name "SPROP_C_TAG_TOOLTIPTEXT". "SPROP_C_TAG_TOOLTI"
         "PTEXT"."
    Trigger Location of Runtime Error
         Program                                 SAPLSCR2
         Include                                 LSCR2U47
         Row                                     31
         Module type                             (FUNCTION)
         Module Name                             RS_SCRP_PROP_ADD_TO_PROP_LIST
    1 FUNCTION RS_SCRP_PROP_ADD_TO_PROP_LIST.
    2 *"----
    3 ""Lokale Schnittstelle:
    4 *"  IMPORTING
    5 *"     REFERENCE(P_TEXTFIELD) TYPE  D021S-FNAM OPTIONAL
    6 *"     REFERENCE(P_TOOLTIPTEXT_TEXTELEM) TYPE  CHAR3 OPTIONAL
    7 *"     REFERENCE(P_TOOLTIPTEXT_VARIABLE) TYPE  D021S-FNAM OPTIONAL
    8 *"     REFERENCE(P_KEEPTAB) TYPE  SEU_BOOL OPTIONAL
    9 *"     REFERENCE(P_DISABLEIMPLICITLABELS) TYPE  SEU_BOOL OPTIONAL
    10 *"     REFERENCE(P_BARCODEINPUT) TYPE  SEU_BOOL OPTIONAL
    11 *"  CHANGING
    12 *"     REFERENCE(P_PROP_LIST) TYPE  PROP_LIST
    13 *"----
    14
    15 data: l_prop type prop_line,
    16       l_prop_list type prop_list,
    17       l_string type prop_str.
    18
    19 * Property TextField
    20 * -
    21
    22 if p_textfield is supplied.
    23   clear l_prop_list.
    24   clear l_prop.
    25   l_prop-name   = sprop_c_tag_textfield_name.
    26   l_prop-syntax = sprop_c_syntax_content .
    27   l_prop-value  = p_textfield.
    28   append l_prop to l_prop_list.
    29 * Zusammensetzen eines Strings der Form
    30 * <Name>value_1</Name> ... <Name>value_n</Name>
    >>   call method cl_dynpro_property_bag=>fill_prop_list_into_properties
    32     exporting
    33       prop_list  = l_prop_list
    34     importing
    35       properties = l_string.
    36 * Property-Eintrag zusammensetzen
    37   clear l_prop.
    38   l_prop-name   = sprop_c_tag_textfield.
    39   l_prop-type   = sprop_c_type_string.
    40   l_prop-syntax = sprop_c_syntax_content .
    41   l_prop-value  = l_string.
    42 * Property-Eintrag in PROP_LIST aufnehmen/ersetzen
    43   read table p_prop_list transporting no fields
    44       with key name = l_prop-name.
    45   if sy-subrc = 0.
    46     modify p_prop_list index sy-tabix
    47         from l_prop.
    48   else.
    49     append l_prop to p_prop_list.
    50  endif.
    Can anyone help me?  I now get the same error with executing other transactions as well.

    Hi,
    Please let us know the component which you are trying to apply. Is it BASIS or ABAP or BW and also let us know the version?
    I hope you are applying the BW patch 8, as per SAP's recommendation we need to apply both 8 an 9 patch of BW at the same time. If not we need to apply some notes which you could find in the service market place. Once you apply the notes, you can proceed with the SP application.
    Regards,
    Varadhu

  • Post Processing Steps after Support Package Stack Application

    I'm curious if anyone has any guidelines for post processing steps (or pre-processing) when applying Support Package Stacks to their Development Infrastructure (Developmend Workplace and the Central NWDI Server).  We have just upgraded a couple of developers local engines and developer studio to SP stack 19 from SP stack 14 and are experiencing some problems.  We also applied the J2EE stack and appropriate SCA files to the NWDI server.
    After the support packs it looks like our DTR files are gone (when reimporting configuration via Developer Studio the SC's are there but there are no DC's inside of them).  Additionally, it looks like we have to manually reimport the newest versions of SAP_BUILDT, SAP_JTECHS, and SAP-JEE.  Another thing is that old Local Web Dynpro DC's are now complaining about class path problems and different versions of files.  We followed the documentation for applying SP19 exactly as the documentation says for a Java Development Usage type.  Is there a checklist or something that anyone has for steps to perform after the application of the support packs?

    I think I'm missing something.  Now I see the code and DC's inside the DTR.  However, when I try to import into NWDS no DC's come in (the software components exist, but no DC's in them).  Additionally, the CBS web ui reports that my software components do not contain any DC's even though I see them in the DTR.  What things can I look at to determine what I'm missing here?
    Thought I'd add some more info..after applying the support packs, we imported the new SAPBUILD, SAP_JTECH, and SAP_jee SCA'S into our track as we required some functionality from the newer build SCA.  We also reimported our old archives back into the system by manually checking them in assuming this would fix the problem with us not seeing the source in the NWDS or the DTR.  After the import, the CBS no longer sees our custom DC's, but the DTR does (both in active and inactive ws).  When importing the dev configuration into the NWDS our custom DC's no longer appear, but SAP's standard SCA's do.
    Message was edited by:
            Eric Vota

  • Installing support package 16, 17 and 18 for Netwever 7.0 (ECC 6 EHP 3 )

    Hi I just want to know if we can directly load SP for Netweaver 7.00. I just went through some doc but they said we can upload SP directyl from SPAM tcode. can we install it from SPAM tcode i have component SAP_BASIS SP 16, 17 and 18. i downloaded SP using Solution manager i am at implementation phase in the same. i am bit confused should i proceed with SPAM ( but i tried upload package option is greyed out there).
    any suggestion will be appreciated.
    Mani

    Hi Mani,
    Follow this,
    http://help.sap.com/saphelp_nw70/helpdata/EN/a7/a7a932845c11d2b421006094b9ea64/frameset.htm
    - 000 client
    - modifiable status of client.
    - don't use DDIC/SAP*, use a user with full authorization
    Question on Appying NW Support Package Stack
    Please note that both individual Support Packages and SP Stacks are Non-cumulative. This means that, when you import Support Packages, then you import a gap less series of Support Packages and, if
    you use SP Stacks, you also import these without a gap. The only exception is the Support Package for SPAM itself. & Java support packages which comes in SCA format.
    Uday, Did you try to copy from what I posted?.. the correct procedure would be to direct to the original link.. not CTRLC & CTRLV!
    Regards,
    Debasis.
    Edited by: Debasis Sahoo on Apr 22, 2009 1:04 PM

  • Netweaver Data base instances for Java and ABAP

    Hello Experts,
    Please help me to understand how the two technology stacks of SAP WAS (Java and ABAP) are configured to use underline data base in Netweaver.
    Is it manadatory to have two separate data base schemas, one for ABAP applications and other for Java applications in the Netweaver?
    If yes..the any idea about what are those schema differences??
    - Rajan

    Hello Krishna,
    Thanks for the reply.
    Is there any way I can access these shemas? Are they the same by structure or there are major differences?
    My requirement is to build a common schema out of these two and have the data from these two schemas to be consolidated in the new schema.
    Any help will be greatly appreciated.
    - Rajan

  • Support package stacks: Do we need to import all SP in the stack?

    Hi all.
    We are about to import Support Package Stack 13 into our ERP 6.0 system. The SPS includes a lot of support packages for software components such as IS-OIL, IS-UT and other IS-*  components.
    These components are inactive in our system, and are not used. However, I know that the recommendation is to import the complete stack.
    I am therefore having some doubts if it is wise to import the IS-* related support packages.
    Please advise.
    Regards,
    Thomas

    Thank you for your feedback.
    However, I would like to ask if the only argument is to follow SAP recommendation? What risks are we running if we do not implement the IS component support packages?
    As the IS-* components are not active, I don't see how not importing these support packages will cause "inconsistence" in the system. Also, it would reduce the total number of support packages that needs to be included.
    I am generally positive to following SAP's recommendations, but in this case we are are in a situation where we need to lift the SAP system from SPS 8 to SPS 13 in one operation. That includes a massive amount of support packages, and possibly a lot more time than the timeframe we have available.
    Regards,
    Thomas

  • Need info about Support Package Stack

    Hi,
    Can anyone tel me what are the Support package stack released in XI 3.0 and what are the modification in each SPS.
    Please send the related Docs if anyone has.
    Thanks&Regards
    Sreedivia

    hi,
    check the below link
    http://help.sap.com/saphelp_nw04/helpdata/en/46/e45ab9db8166bfe10000000a1553f7/frameset.htm
    regards
    kummari
    Edited by: kummari on Jul 28, 2008 11:40 AM

Maybe you are looking for

  • What is wrong with my iBook?

    I have a G4 1.xx ghz iBook. It's about 14 months old, and it just stopped working a few days ago. It no longer powers up. I can hear what sounds like the fan when I push the power button, but nothing happens. The display worked just fine right before

  • Windows 7 starter problem

    i recently bought an ipod touch for my son, we tried to install itunes, but we get a message, something about windows installer. is there a way to install itunes on a netbook running windows 7 starter, or do we have to upgrade to windows home premium

  • ITunes 10.5 No Longer Shows App Folders for iPhone

    One day they were there, the next they weren't. The folders are still on my iPhone. Any ideas how I can fix this? Thanks!

  • Link on report returns no value when record containts '&' or '' (space)

    I have created a report based on a sql script. I want to link this report to a form. With the standard LINK, the records that contain a space or '&' sign aren't linked to the form. Is there a way to resolve this? I know that there is a way to add htm

  • Fcp forces me to render Apple Pro Res 4444 files when i drop on timeline

    i shoot with the canon 5d mark ii and i have been having problems making my videos easy to edit. I convert them from h.264 to the apple pro res 4444. when i take the files and then attempt to drag them into the project timeline, i am prompted to chan