Portal Debug Mode :(

Recently, I've turned ON the Debug mode on my server(port:50021).Since then i cudn't start my portal.In MMC, it remains 'starting application' forever!
I tried to Turn OFF the Mode but when i do so, iam unable to save the settings after i hit the Save button in Visual Administrator.Status bar shows, applying changes..but it remains forever there too.
Any ideas, on how to get back my portal up n running?
Thanks a lot!

Hey Rasmus,
Somehow i was able to uncheck it but my MMC still shows Debug is ON..How to get back my portal ..Help:
I right clicked the server in the MMC and hit the Developer Trace: iam pasting it here:
trc file: "C:\usr\sap\J2E\JC00\work\dev_server0", trc level: 1, release: "640"
node name   : ID5626050
pid         : 2304
system name : J2E
system nr.  : 00
started at  : Mon Dec 19 18:37:36 2005
arguments   :
    arg[00] : C:\usr\sap\J2E\JC00/j2ee/os_libs/jlaunch.exe
    arg[01] : pf=C:\usr\sap\J2E\SYS\profile\J2E_JC00_epserver
    arg[02] : -DSAPINFO=J2E_00_server
    arg[03] : pf=C:\usr\sap\J2E\SYS\profile\J2E_JC00_epserver
[Thr 6104] Mon Dec 19 18:37:36 2005
[Thr 6104] *** ERROR => Invalid property value [box.number/J2EJC00epserver] [jstartxx.c   789]
[Thr 6104] *** ERROR => Invalid property value [system.id/0] [jstartxx.c   789]
JStartupReadInstanceProperties: read instance properties [C:\usr\sap\J2E\JC00\j2ee\cluster\instance.properties]
-> ms host    : epserver
-> ms port    : 3601
-> OS libs    : C:\usr\sap\J2E\JC00\j2ee\os_libs
-> Admin URL  :
-> run mode   : NORMAL
-> run action : NONE
-> enabled    : yes
Used property files
-> files [00] : C:\usr\sap\J2E\JC00\j2ee\cluster\instance.properties
Instance properties
-> ms host    : epserver
-> ms port    : 3601
-> os libs    : C:\usr\sap\J2E\JC00\j2ee\os_libs
-> admin URL  :
-> run mode   : NORMAL
-> run action : NONE
-> enabled    : yes
Bootstrap nodes
-> [00] bootstrap            : C:\usr\sap\J2E\JC00\j2ee\cluster\instance.properties
-> [01] bootstrap_ID5626000  : C:\usr\sap\J2E\JC00\j2ee\cluster\instance.properties
-> [02] bootstrap_ID5626050  : C:\usr\sap\J2E\JC00\j2ee\cluster\instance.properties
Worker nodes
-> [00] ID5626000            : C:\usr\sap\J2E\JC00\j2ee\cluster\instance.properties
-> [01] ID5626050            : C:\usr\sap\J2E\JC00\j2ee\cluster\instance.properties
[Thr 6104] JLaunchRequestQueueInit: create named pipe for ipc
[Thr 6104] JLaunchRequestQueueInit: create pipe listener thread
[Thr 1260] JLaunchRequestFunc: Thread 1260 started as listener thread for np messages.
[Thr 4904] WaitSyncSemThread: Thread 4904 started as semaphore monitor thread.
[Thr 6104] Mon Dec 19 18:37:37 2005
[Thr 6104] INFO: Invalid property value [JLaunchParameters/]
[Thr 6104] JStartupIReadSection: debug mode is specified by program arguments
[Thr 6104] [Node: server0] java home is set by profile parameter
     Java Home: C:\j2sdk1.4.2_08
JStartupIReadSection: read node properties [ID5626050]
-> node name       : server0
-> node type       : server
-> java path       : C:\j2sdk1.4.2_08
-> java parameters : -Djava.security.policy=./java.policy -Djava.security.egd=file:/dev/urandom -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy -Dorg.omg.PortableInterceptor.ORBInitializerClass.com.sap.engine.services.ts.jts.ots.PortableInterceptor.JTSInitializer -Djco.jarm=1 -Dsun.io.useCanonCaches=false -Djava.awt.headless=true -verbose:gc -Drdbms.driverLocation=c:/sapdb/programs/runtime/jar/sapdbc.jar -Dsys.global.dir=C:/usr/sap/J2E/SYS/global -XX:NewSize=85m -XX:MaxNewSize=85m -XX:MaxPermSize=192m -XX:PermSize=192m -XX:DisableExplicitGC -XX:UseParNewGC -XX:PrintGCDetails -XX:PrintGCTimeStamps -XX:SurvivorRatio=2 -XX:TargetSurvivorRatio=90 -XX:SoftRefLRUPolicyMSPerMB=1 -verbose:gc
-> java vm version : 1.4.2_08-b03
-> java vm vendor  : Java HotSpot(TM) Server VM (Sun Microsystems Inc.)
-> java vm type    : server
-> java vm cpu     : x86
-> heap size       : 512M
-> init heap size  : 512M
-> root path       : C:\usr\sap\J2E\JC00\j2ee\cluster\server0
-> class path      : .\bin\boot\boot.jar;.\bin\boot\jaas.jar;.\bin\system\bytecode.jar;.
-> OS libs path    : C:\usr\sap\J2E\JC00\j2ee\os_libs
-> main class      : com.sap.engine.boot.Start
-> framework class : com.sap.bc.proj.jstartup.JStartupFramework
-> registr. class  : com.sap.bc.proj.jstartup.JStartupNatives
-> framework path  : C:\usr\sap\J2E\JC00\j2ee\os_libs\jstartup.jar
-> shutdown class  : com.sap.engine.boot.Start
-> parameters      :
-> debuggable      : yes
-> debug mode      : yes
-> debug port      : 50021
-> shutdown timeout: 120000
[Thr 6104] JLaunchISetDebugMode: set debug mode [yes]
[Thr 4800] JLaunchIStartFunc: Thread 4800 started as Java VM thread.
JHVM_LoadJavaVM: VM Arguments of node [server0]
-> stack   : 262144 Bytes
-> arg[  0]: exit
-> arg[  1]: abort
-> arg[  2]: -Denv.class.path=C:\Program Files\Java\j2re1.4.2_08\lib\ext\QTJava.zip
-> arg[  3]: -Djava.security.policy=./java.policy
-> arg[  4]: -Djava.security.egd=file:/dev/urandom
-> arg[  5]: -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy
-> arg[  6]: -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy
-> arg[  7]: -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy
-> arg[  8]: -Dorg.omg.PortableInterceptor.ORBInitializerClass.com.sap.engine.services.ts.jts.ots.PortableInterceptor.JTSInitializer
-> arg[  9]: -Djco.jarm=1
-> arg[ 10]: -Dsun.io.useCanonCaches=false
-> arg[ 11]: -Djava.awt.headless=true
-> arg[ 12]: -verbose:gc
-> arg[ 13]: -Drdbms.driverLocation=c:/sapdb/programs/runtime/jar/sapdbc.jar
-> arg[ 14]: -Dsys.global.dir=C:/usr/sap/J2E/SYS/global
-> arg[ 15]: -XX:NewSize=85m
-> arg[ 16]: -XX:MaxNewSize=85m
-> arg[ 17]: -XX:MaxPermSize=192m
-> arg[ 18]: -XX:PermSize=192m
-> arg[ 19]: -XX:+DisableExplicitGC
-> arg[ 20]: -XX:+UseParNewGC
-> arg[ 21]: -XX:+PrintGCDetails
-> arg[ 22]: -XX:+PrintGCTimeStamps
-> arg[ 23]: -XX:SurvivorRatio=2
-> arg[ 24]: -XX:TargetSurvivorRatio=90
-> arg[ 25]: -XX:SoftRefLRUPolicyMSPerMB=1
-> arg[ 26]: -verbose:gc
-> arg[ 27]: -Dsys.global.dir=C:\usr\sap\J2E\SYS\global
-> arg[ 28]: -Dapplication.home=C:\usr\sap\J2E\JC00\j2ee\os_libs
-> arg[ 29]: -Djava.class.path=C:\usr\sap\J2E\JC00\j2ee\os_libs\jstartup.jar;.\bin\boot\boot.jar;.\bin\boot\jaas.jar;.\bin\system\bytecode.jar;.
-> arg[ 30]: -Djava.library.path=C:\j2sdk1.4.2_08\jre\bin\server;C:\j2sdk1.4.2_08\jre\bin;C:\j2sdk1.4.2_08\bin;C:\usr\sap\J2E\JC00\j2ee\os_libs;c:\sapdb\programs\bin;c:\sapdb\programs\pgm;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\QuickTime\QTSystem\;C:\usr\sap\J2E\SCS01\exe;C:\usr\sap\J2E\JC00\exe;C:\usr\sap\J2E\SYS\exe\run
-> arg[ 31]: -Xdebug
-> arg[ 32]: -Xnoagent
-> arg[ 33]: -Djava.compiler=NONE
-> arg[ 34]: -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=50021
-> arg[ 35]: -Dmemory.manager=512M
-> arg[ 36]: -Xmx512M
-> arg[ 37]: -Xms512M
-> arg[ 38]: -DLoadBalanceRestricted=no
-> arg[ 39]: -Djstartup.mode=JCONTROL
-> arg[ 40]: -Djstartup.ownProcessId=2304
-> arg[ 41]: -Djstartup.ownHardwareId=S0415048418
-> arg[ 42]: -Djstartup.whoami=server
-> arg[ 43]: -Djstartup.debuggable=yes
-> arg[ 44]: -DSAPINFO=J2E_00_server
-> arg[ 45]: -DSAPSTARTUP=1
-> arg[ 46]: -DSAPSYSTEM=00
-> arg[ 47]: -DSAPSYSTEMNAME=J2E
-> arg[ 48]: -DSAPMYNAME=epserver_J2E_00
-> arg[ 49]: -DSAPDBHOST=
-> arg[ 50]: -Dj2ee.dbhost=epserver
[Thr 4800] Mon Dec 19 18:37:39 2005
[Thr 4800] JHVM_LoadJavaVM: Java VM created OK.
JHVM_BuildArgumentList: main method arguments of node [server0]
[Thr 2440] Mon Dec 19 18:38:11 2005
[Thr 2440] JHVM_RegisterNatives: registering methods in com.sap.bc.proj.jstartup.JStartupFramework
[Thr 2440] JLaunchISetClusterId: set cluster id 5626050
[Thr 2440] JLaunchISetState: change state from [Initial (0)] to [Waiting for start (1)]
[Thr 2440] JLaunchISetState: change state from [Waiting for start (1)] to [Starting (2)]
[Thr 3940] Mon Dec 19 18:38:33 2005
[Thr 3940] JHVM_RegisterNatives: registering methods in com.sap.security.core.server.vsi.service.jni.VirusScanInterface
[Thr 3940] *** ERROR => JHVM_RegisterNatives: registration for class com.sap.security.core.server.vsi.service.jni.VirusScanInterface failed. [jhvmxx.c     338]
[Thr 2440] Mon Dec 19 18:43:24 2005
[Thr 2440] JLaunchISetState: change state from [Starting (2)] to [Starting applications (10)]

Similar Messages

  • Portal down after starting Server in debug mode

    I have started my AS Java in Debug Mode. Now, the Portal is down, shing the following error message:
    503 Service not available
    Error:     -6
    Version:     7010
    Component:     ICM Java
    Date/Time:     Mon May 26 11:39:28 2008
    Module:     http_j2ee2.c
    Line:     1136
    Server:     SV-SAP-5_CES_01
    Error Tag:     {00000a45}
    Detail:     ICM running but no server with HTTP connected - Load Balancing failed
    Why is that?
    Thanks, JJJ

    It takes time till the server is running again. Wait a few minutes and try again!

  • SRM 7.0 - Unable / How to get into DEBUGGING mode in BADI

    Hello SAPions,
    I am unable to get into debugging mode from WebDynpro Portal screen to R/3 BADI in SRM 7.0 .
    I placed a breakpoint in the BADI, and logged into the portal screen.
    However, in SRM5.0, to get into debugging mode from ITS, we place a break point in the BADI, when we browse the ITS link from the IE browser, we will be able to get into debuggin mode.
    Any other way ?
    Regards,
    Ashwin.

    Hello,
    Please check the following:
    1. Application server name, the SAP GUI and the portal should be logged into the same application server.
    2. You should be logged in with the same User in both SAP GUI and the Portal.
    3. External debugging should be enabled for the User in SAP GUI.
    4. Also try checking the check box , IP Matching . This can be done as below:
    Utilities -> Settings ->  ABAP Editor -> Debugging ->  IP Matching.
    Also please check the following in the above link , if you have the same user name here with which you have logged onto Portal and the New Debugger Radio Button is Selected.
    Hope this helps.
    Best Regards,
    Sapna

  • Remote Debug mode while starting Weblogic server using my eclipse plugin

    Hi
    When am starting the Weblogic server via my eclipse it is opening in Remote Debug mode. Can anyone tell me how do I change the preferences/configure so that it doesnt run in debug mode.
    NOTE:I have deployed the application and ran number of times, till yesterday it wasn't starting in this mode, though I haven't changed any settings since then, it is starting in Remote Debug mode.
    Thanks,

    The above issue is resolved by adding this to setDomainEnv.sh :
    ALTERNATE_TYPES_DIRECTORY="${WLPORTAL_HOME}/portal/lib/security"
    export ALTERNATE_TYPES_DIRECTORY
    JAVA_OPTIONS="${JAVA_OPTIONS} -Dweblogic.alternateTypesDirectory=${ALTERNATE_TYPES_DIRECTORY}"
    # weblogic extension directories (system jars)
    if [ "${WEBLOGIC_EXTENSION_DIRS}" != "" ] ; then
    WEBLOGIC_EXTENSION_DIRS="${WEBLOGIC_EXTENSION_DIRS}${CLASSPATHSEP}${WLPORTAL_HOME}/p13n/lib/system"
    export WEBLOGIC_EXTENSION_DIRS
    else
    WEBLOGIC_EXTENSION_DIRS="${WLPORTAL_HOME}/p13n/lib/system"
    export WEBLOGIC_EXTENSION_DIRS
    fi
    WEBLOGIC_EXTENSION_DIRS="${WEBLOGIC_EXTENSION_DIRS}${CLASSPATHSEP}${WLPORTAL_HOME}/light-portal/lib/system${CLASSPATHSEP}${WLPORTAL_HOME}/portal/lib/system${
    CLASSPATHSEP}${WLPORTAL_HOME}/info-mgmt/lib/system${CLASSPATHSEP}${WLPORTAL_HOME}/analytics/lib/system${CLASSPATHSEP}${WLPORTAL_HOME}/apps/lib/system${CLASSP
    ATHSEP}${WLPORTAL_HOME}/info-mgmt/deprecated/lib/system"
    export WEBLOGIC_EXTENSION_DIRS
    WEBLOGIC_EXTENSION_DIRS="${WEBLOGIC_EXTENSION_DIRS}${CLASSPATHSEP}${WLPORTAL_HOME}/content-mgmt/lib/system"
    export WEBLOGIC_EXTENSION_DIRS
    if [ "${WEBLOGIC_EXTENSION_DIRS}" != "" ] ; then
    JAVA_OPTIONS="${JAVA_OPTIONS} -Dweblogic.ext.dirs=${WEBLOGIC_EXTENSION_DIRS}"
    export JAVA_OPTIONS
    fi

  • Debug mode (EP6 SP 2) crashs from time to time

    hi folks,
    we got a very well running portal ep6 sp2 which
    we use for iview development. the developers use
    pdk and eclipse and we start the portal in debug
    mode.
    what happens is that from time to time it gets
    unpossible to connect to the debug port. it is not
    possbible to debug an iview from eclipse. the
    connection to the debug port is not possible anymore.
    the only solutions i got is a portal restart to ensure
    that our developer can use the debug port. but that
    takes too much time. does anybody know what leads to that
    phenomenon? and how can we reanimate the portal to be
    debugged without a complete restart?
    i really appreciate any help,
    maik

    Hi Tracy,
    Has it ever been shut off from AC power for any length of time?
    I'm thinking a dead or weak PRAM Battery may cause the boot mode to change.
    Unless of course it might be a sticky Shift key.
       1. Access the command line by either opening Terminal remotely, or by logging into the computer from another via SSH.
       2. Execute the following command in Terminal or on the command line:
          sudo nvram boot-args="-x"
          (If you want to start in Verbose mode as well, use sudo nvram boot-args="-x -v" instead )
       3. After using Safe Boot, to return to a normal startup, execute this command in Terminal or the command line:
          sudo nvram boot-args=""

  • WebLogic Server Times  OUT during DEBUG mode startup

    Hi,
    I am having a issue where my WebLogic Server 10.3 times out when I try to run it in debug mode in my workshop. Below is the error I get.
    "Timeout waiting for Oracle WebLogic Server v10.3 at localhost to start. Server did not start after 480s. "
    Do anyone have any idea why this is happening? I have reinstalled workshop but still same error.
    Thanks

    I have also seen this error when the debug mode does not start.
    starting weblogic with Java version:
    FATAL ERROR in native method: JDWP No transports initialized, jvmtiError=AGENT_ERROR_TRANSPORT_INIT(197)
    ERROR: transport error 202: bind failed: Address already in use
    ERROR: JDWP Transport dt_socket failed to initialize, TRANSPORT_INIT(510)
    JDWP exit error AGENT_ERROR_TRANSPORT_INIT(197): No transports initialized [../../../src/share/back/debugInit.c:690]
    Starting WLS with line:
    C:\bea103\JDK160~1\bin\java -client -Debug -Xnoagent -Xrunjdwp:transport=dt_socket,address=8453,server=y,suspend=n -Djava.compiler=NONE -Xms1200m -Xmx1200m -XX:CompileThreshold=8000 -XX:PermSize=192m -XX:MaxPermSize=192m -Xverify:none -ea -da:com.bea... -da:javelin... -da:weblogic... -ea:com.bea.wli... -ea:com.bea.broker... -ea:com.bea.sbconsole... -Dplatform.home=C:\bea103\WLSERV~1.3 -Dwls.home=C:\bea103\WLSERV~1.3\server -Dweblogic.home=C:\bea103\WLSERV~1.3\server -Dweblogic.wsee.bind.suppressDeployErrorMessage=true -Dweblogic.wsee.skip.async.response=true -Dweblogic.management.discover=true -Dweblogic.security.SSL.ignoreHostnameVerify=false -Dwlw.iterativeDev=true -Dwlw.testConsole=true -Dwlw.logErrorsToConsole=true -DKS_URL=rmi://10.87.40.196:1188/KS -Dweblogic.ext.dirs=C:\bea103\patch_wlw1030\profiles\default\sysext_manifest_classpath;C:\bea103\patch_wls1030\profiles\default\sysext_manifest_classpath;C:\bea103\patch_wlp1030\profiles\default\sysext_manifest_classpath;C:\bea103\patch_cie670\profiles\default\sysext_manifest_classpath;C:\bea103\wlportal_10.3\p13n\lib\system;C:\bea103\wlportal_10.3\light-portal\lib\system;C:\bea103\wlportal_10.3\portal\lib\system;C:\bea103\wlportal_10.3\info-mgmt\lib\system;C:\bea103\wlportal_10.3\analytics\lib\system;C:\bea103\wlportal_10.3\apps\lib\system;C:\bea103\wlportal_10.3\info-mgmt\deprecated\lib\system;C:\bea103\wlportal_10.3\content-mgmt\lib\system -Dweblogic.alternateTypesDirectory=C:\bea103\wlportal_10.3\portal\lib\security -Dweblogic.Name=AdminServer -Djava.security.policy=C:\bea103\WLSERV~1.3\server\lib\weblogic.policy weblogic.Server
    FATAL ERROR in native method: JDWP No transports initialized, jvmtiError=AGENT_ERROR_TRANSPORT_INIT(197)
    ERROR: transport error 202: bind failed: Address already in use
    ERROR: JDWP Transport dt_socket failed to initialize, TRANSPORT_INIT(510)
    JDWP exit error AGENT_ERROR_TRANSPORT_INIT(197): No transports initialized [../../../src/share/back/debugInit.c:690]

  • Debug mode:  attach to running process

    Hi all,
    Is there anything different in how one might remotely attach to a running
    portal server? I've added the following line
    (-Xdebug -Xnoagent -Djava.compiler=NONE -Xrunjdwp:transport=dt_socket,server
    =y,suspend=n,address=8999) which worked well under WLS 7.0 and a separate
    app not related to Portal 7.0 in any way.
    While I am able to connect/attach to the remote VM under IntelliJ, none of
    my breakpoints actually break. I am able to view output to the console, so
    I know the line in question is getting executed. I assuming that setting up
    the Portal server to operate in debug mode is exactly the same as setting up
    WLS 7.0 to operate in debug mode, but so far it doesn't seem to be the case.
    TIA
    Michael.

    i haven't done this in awhile, but i have notes that use some of these options...
    transport=dt_shmem,address=localhost,server=n,suspend=y
    transport=dt_shmem,address=ebcc,server=y,suspend=y
    transport=dt_socket,address=localhost:8000,server=y,suspend=y
    good luck!
    -tanya
    "Michael Morett" <[email protected]> wrote:
    Hi all,
    Is there anything different in how one might remotely attach to a running
    portal server? I've added the following line
    (-Xdebug -Xnoagent -Djava.compiler=NONE -Xrunjdwp:transport=dt_socket,server
    =y,suspend=n,address=8999) which worked well under WLS 7.0 and a separate
    app not related to Portal 7.0 in any way.
    While I am able to connect/attach to the remote VM under IntelliJ, none
    of
    my breakpoints actually break. I am able to view output to the console,
    so
    I know the line in question is getting executed. I assuming that setting
    up
    the Portal server to operate in debug mode is exactly the same as setting
    up
    WLS 7.0 to operate in debug mode, but so far it doesn't seem to be the
    case.
    TIA
    Michael.

  • Default debug mode of tcode in transaction iview

    Hi experts,
    I create a transaction iview for tcode se38 and everything is ok except that iView does not show se38 in normal way but in debug mode. Does anyone encounter this problem, please give me the solution? I guess that the some settings concerning to debug mode turned on in system, but i don't know how to disable it. Please help.
    Thanks.

    Hi Kebab
    You can deactivate external debugging in the menu under by logging in R/3 System and navigate to Utilities -> Settings... -> ABAP Editor -> Debugging in the External Debugging field and remove the check point for your userid.
    Else if that is not an external Debugging then Utilities -> Breakpoints... -> Display and from there select delete selected object.
    And now you login into portal and see the difference.
    Regards
    Basha

  • How to determine if the server is in debug mode or Running in Java Code

    Hi ,
    I have a WebDynpro Applcation in which i have to display foll things in Table:
    Engine Name; Engine Version: Debug Mode; Reserved by;
    Now i could display list of servers but i have hardcoded the Debug Mode as "Disabled"
    My Question is:
    If i know the Server, can we find if the server is in debugmode in application code???
    I have OS access to my Engine. Pls let me in which property file can i find Debug Status??
    Also i am not sure if i have posted the Query in RIght Component. DO let e know if this Q is posted in wrong Forum
    Kindly help me solve this problem
    Thanks n Regards,
    Archana

    Hi Archana,
    If u can't start the server in debugging mode thru NWDS then u can try this
    Config Tool:
    U can enable the debuggine mode from the Config Tool as well. Just browse to following
    C:usrsap<SID>JC<SYS_NO>j2eeconfigtoolconfigtool.bat
    Click on the your instance. Then under the tab VM Environment, Set the DebugMode = true.
    Restart the engine now. This will open the J2EE server again in the Debug Mode.
    Please check the [Debugging Portal Applications or WebDynpro Applciation|http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/907751e5-f717-2a10-f3b4-de4431d4722d?quicklink=index&overridelayout=true] and search for SDN
    Just hope this helps you!
    Regards
    Vijay

  • Running Tomcat server in Debug mode?

    Hi..
    I am using Eclipse IDE to develop a Portal project.. I am also using Tomcat server for the same without using the default servers provided by eclipse..
    My question is how do I run the Tomcat server in the "debug" mode?
    Please help me..

    Take a look at these links: http://plato.acadiau.ca/courses/comp/dsilver/2513/EclipseAndTomcatTutorial/
    http://www.keyboardsamurais.de/2004/01/15/tomcat_tutorial_helloworld_for_complete_fools_-_english/
    http://www-128.ibm.com/developerworks/opensource/library/os-ectom/?ca=dgr-lnxw16EclipsTomcat
    I've found going through tutorials is a proven, quick way of getting up to speed with new tools and configurations.
    HTH,
    James

  • Running applications in debug mode in JDeveloper

    Hi All,
    I have created a simple spring portlet and have consumed it on a webcenter application. The portlet throws an exception. Now I want to run my portlet in debug mode.
    Both webcenter application and portlet producer are running on the jdeveloper integrated server.
    Can any one help me out mentioning steps to run the portlet and the portal app in debug mode.

    Some info can be found in this thread in JDev forum: JDeveloper remote debugging OC4J
    However, it is based on 10g and OC4J. Still, I believe, the overall concept can be used.

  • ESS in debugging mode

    Hi All,
    When an employee logs in to ESS portal, need to know how this logging on takes place in the background (ABAP code, FM etc). Need to know what FMs/BAPIs are called right from the first step where it checks the userid info in infotype 0105.
    In other words, the need is to see in debugging mode while the employee logs on.
    Need to know what FMs are used and where to put the breakpoints etc.
    Any help will be highly appreciated.
    Thanks,
    Mark.

    Wow! You're really asking for it eh? haha You actually will have lots going on and not sure a trace will help you make sense of it all. Just from a high-level...
    (1) login into portal => userid/pword are authenticated against whatever the portal uses as a source (ldap server, portal db, R3/ system, etc). If it passes this authentication, the portal then locates the user in it's own db to find what PORTAL roles to assign to build out the user's portal specific to them.
    (2) Assuming single sign-on is set up, the portal issues a SAP Logonticket that is passed to the backend systems. This Logonticket is just a fancy non-persistent, encrypted cookie that contains (a) the userid (b) the portal's "key".
    (3) when the user (via the portal) makes a request to the backend system, the portal "hands" the Logonticket to the other system. The other system checks the "key" and says "ok, yep this is the portal...I trust the portal...no need to check the userfurther such as password". The backend system then will take the userid (again, no password needed) and check that that userid actually exists. Let's assume it does. As with the portal, the backend system can now determine what security authorizations and roles (don't confuse with a portal role!) the user has.
    (4) Now...that gets us to the "login" part of the backend. In the case of your ESS needs, we now could be playing with any number of possibilities.
       -ITS service which in turn is really running a SAP transaction (most common for ESS)
       -Webdynpro which is a Java app that calls SAP via BAPIs/RFCs
       -direct GUI access (via SAP WINGUI launched from portal)
       -other (custom apps that call RFCs/BAPIs)
       With all of the above there is usually some code in there that right off the bat will take the userid and try to find what employee it matches. Userid (ie. a system user record) is linked to employee records via infotype (kind of a HR table) 0105 (communication), subtype 0001 (SAP Userid). Given the current date, it will try to find which employee record has this userid assigned to IT0105 ST0001 (lots/most of HR records are date driven). If no employee record is found for the userid, you typically get an error that states something to the effect of "this userid does not match an employee record for this period".
    From this point, all of the "what's going on" largely depends on what ESS service you are trying to perform (address change, benefits enrollment, etc).
    Hope this helps.

  • Debug mode of j2ee Process table??

    Hello All,
                   In j2ee Process Table,3 processes are running.
    SDM-Debug(Switched off)--SDM Server
    Dispatcher-Disable---J2ee Dispatcher     
    Server0-Swiched off ---J2ee server
    Why SDM server & server0 are swiched off & dispacher is disabled in the Debug mode??When we need to enable it??

    Hi,
    Refer these links.
    https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/558e9ae5-0601-0010-40a0-a1d35a13047d?overridelayout=true
    https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/3a83c242-0801-0010-dc95-d496cf6dba9d?overridelayout=true
    let us know if u have any issues,
    Regards,
    Ravi

  • Debug Mode -WebDynpro

    Hi,
    I configured everything for debugging. I set a breakpoint and it works but where can i go and see returned values?.
    Also when the breakpoint hits while debugging how do i step line by line or resume or move onto next line. When my debugger hits the breakpoint i cannot resume it is stuck.

    Hi zxcheng,
    [Start Server in Debug Mode|How to start server in debug mode by default;
    [Web Dynpro for Experts|https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/media/uuid/3178ae74-0701-0010-ba8d-e3ca9f1edc1e]
    I guess the above links will also help you.
    Regards
    Sid

  • How to enable debug mode?

    Hi
    We are doing some web dynpro development.
    Can anyone tell me ho to enable debug mode in the server
    Thanks
    Vijay

    Hi,
    Check this blog, for some idea how to use configtool to set debug mode:
    NetWeaver Portal Debugging
    How to enable debug mode?
    I see that you are new to this forum, first of all welcome to SDN.
    I see that you have posted alot of questions today, really appreciate your interest in learning new stuff.
    SDN is a great forum to start with but my suggestion is to first search the forum for answers to your questions before posting them, this way you will help yourself instead of waiting for people to help you out.
    Greetings,
    Praveen Gudapati
    [Points are always welcome for helpful answers]

Maybe you are looking for