SQL Trace in SAP Manufacturing Execution Logging Configuration disappear

Dears,
We set it to trace the sql log, but it often disappear suddently.
The log may as below for your referenct.
Thanks!
#2.0 #2011 04 01 16:15:13:836#+0800#Info#com.sap.me.trace#
##sap.com/meear#68B5996B863C332900000000000010A8#1859650000000004#sap.com/meear#com.sap.me.trace.VM#UMEUser#5922#SAP J2EE Engine JTA Transaction : [01c604207ffffffd85f]#FC6254555C3711E081A10000001C6042#24ac39ef5c3811e0bd410000001c6042#24ac39ef5c3811e0bd410000001c6042#0#Thread[HTTP Worker [@1423449306],5,Dedicated_Application_Thread]#Plain##
[0] SELECT MODIFIED_DATE_TIME from WORKSTATION where HANDLE='WorkstationBO:FXM,S,POD_CARY' #
#2.0 #2011 04 01 16:15:46:695#+0800#Error#com.sap.engine.services.webservices.espbase.server.runtime.RuntimeProcessingEnvironment#
#BC-ESI-WS-JAV-RT#webservices_lib#68B5996B863C332A00000001000010A8#1859650000000005#sap.com/me~ear#com.sap.engine.services.webservices.espbase.server.runtime.RuntimeProcessingEnvironment#Guest#0##3975C02C5C3811E0A21E0000001C6042#3975c02c5c3811e0a21e0000001c6042#3975c02c5c3811e0a21e0000001c6042#0#Thread[HTTP Worker [@2101874070],5,Dedicated_Application_Thread]#Plain##
process()
[EXCEPTION]
com.sap.engine.interfaces.webservices.runtime.ProtocolException: Authentication failed. For details see log entry logID=68B5996B863C332A00000000000010A8 in security log.
     at com.sap.engine.services.wssec.srt.protocols.ProviderSecurityProtocol.logThrowable(ProviderSecurityProtocol.java:1103)
     at com.sap.engine.services.wssec.srt.protocols.ProviderSecurityProtocol.afterDeserialization(ProviderSecurityProtocol.java:719)
     at com.sap.engine.services.webservices.espbase.server.runtime.ProtocolProcessor.protocolsAfterDeserialization(ProtocolProcessor.java:156)
     at com.sap.engine.services.webservices.espbase.server.runtime.RuntimeProcessingEnvironment.preProcess(RuntimeProcessingEnvironment.java:439)
     at com.sap.engine.services.webservices.espbase.server.runtime.RuntimeProcessingEnvironment.process(RuntimeProcessingEnvironment.java:260)
     at com.sap.engine.services.webservices.runtime.servlet.ServletDispatcherImpl.doPostWOLogging(ServletDispatcherImpl.java:178)
     at com.sap.engine.services.webservices.runtime.servlet.ServletDispatcherImpl.doPostWithLogging(ServletDispatcherImpl.java:114)
     at com.sap.engine.services.webservices.runtime.servlet.ServletDispatcherImpl.doPost(ServletDispatcherImpl.java:72)
     at com.sap.engine.services.webservices.servlet.SOAPServletExt.doPost(SOAPServletExt.java:90)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:754)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
     at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.runServlet(FilterChainImpl.java:162)
     at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:81)
     at com.sap.me.webservice.ClearServiceContextFilter.doFilter(ClearServiceContextFilter.java:28)
     at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:73)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:461)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:298)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:397)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
     at com.sap.engine.services.servlets_jsp.filters.DSRWebContainerFilter.process(DSRWebContainerFilter.java:48)
     at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
     at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:83)
     at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
     at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:243)
     at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
     at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:78)
     at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
     at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
     at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)
     at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
     at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
     at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)
     at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
     at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
     at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)
     at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
     at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
     at com.sap.engine.services.httpserver.filters.MemoryStatisticFilter.process(MemoryStatisticFilter.java:43)
     at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
     at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
     at com.sap.engine.services.httpserver.filters.DSRHttpFilter.process(DSRHttpFilter.java:42)
     at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
     at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
     at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:428)
     at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.process(Processor.java:247)
     at com.sap.engine.services.httpserver.server.rcm.RequestProcessorThread.run(RequestProcessorThread.java:45)
     at com.sap.engine.core.thread.execution.Executable.run(Executable.java:122)
     at com.sap.engine.core.thread.execution.Executable.run(Executable.java:101)
     at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:327)
Caused by: com.sap.engine.services.wssec.policy.exception.VerifyException: [ASJ.wssec.020441] Authentication failed. For details see log entry logID=68B5996B863C332A00000000000010A8 in security log.
     at com.sap.engine.services.wssec.srt.protocols.ProviderSecurityProtocol.authenticate(ProviderSecurityProtocol.java:258)
     at com.sap.engine.services.wssec.srt.protocols.ProviderSecurityProtocol.afterDeserialization(ProviderSecurityProtocol.java:687)
     ... 47 more
#2.0 #2011 04 01 16:15:46:773#+0800#Error#com.sap.engine.services.webservices.espbase.server.runtime.RuntimeProcessingEnvironment#
#BC-ESI-WS-JAV-RT#webservices_lib#68B5996B863C332C00000001000010A8#1859650000000005#sap.com/me~ear#com.sap.engine.services.webservices.espbase.server.runtime.RuntimeProcessingEnvironment#Guest#0##3A404CDE5C3811E0CD230000001C6042#3a404cde5c3811e0cd230000001c6042#3a404cde5c3811e0cd230000001c6042#0#Thread[HTTP Worker [@909268645],5,Dedicated_Application_Thread]#Plain##
process()
[EXCEPTION]
com.sap.engine.interfaces.webservices.runtime.ProtocolException: Authentication failed. For details see log entry logID=68B5996B863C332C00000000000010A8 in security log.
     at com.sap.engine.services.wssec.srt.protocols.ProviderSecurityProtocol.logThrowable(ProviderSecurityProtocol.java:1103)
     at com.sap.engine.services.wssec.srt.protocols.ProviderSecurityProtocol.afterDeserialization(ProviderSecurityProtocol.java:719)
     at com.sap.engine.services.webservices.espbase.server.runtime.ProtocolProcessor.protocolsAfterDeserialization(ProtocolProcessor.java:156)
     at com.sap.engine.services.webservices.espbase.server.runtime.RuntimeProcessingEnvironment.preProcess(RuntimeProcessingEnvironment.java:439)
     at com.sap.engine.services.webservices.espbase.server.runtime.RuntimeProcessingEnvironment.process(RuntimeProcessingEnvironment.java:260)
     at com.sap.engine.services.webservices.runtime.servlet.ServletDispatcherImpl.doPostWOLogging(ServletDispatcherImpl.java:178)
     at com.sap.engine.services.webservices.runtime.servlet.ServletDispatcherImpl.doPostWithLogging(ServletDispatcherImpl.java:114)
     at com.sap.engine.services.webservices.runtime.servlet.ServletDispatcherImpl.doPost(ServletDispatcherImpl.java:72)
     at com.sap.engine.services.webservices.servlet.SOAPServletExt.doPost(SOAPServletExt.java:90)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:754)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
     at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.runServlet(FilterChainImpl.java:162)
     at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:81)
     at com.sap.me.webservice.ClearServiceContextFilter.doFilter(ClearServiceContextFilter.java:28)
     at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:73)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:461)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:298)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:397)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
     at com.sap.engine.services.servlets_jsp.filters.DSRWebContainerFilter.process(DSRWebContainerFilter.java:48)
     at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
     at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:83)
     at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
     at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:243)
     at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
     at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:78)
     at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
     at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
     at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)
     at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
     at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
     at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)
     at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
     at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
     at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)
     at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
     at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
     at com.sap.engine.services.httpserver.filters.MemoryStatisticFilter.process(MemoryStatisticFilter.java:43)
     at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
     at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
     at com.sap.engine.services.httpserver.filters.DSRHttpFilter.process(DSRHttpFilter.java:42)
     at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
     at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
     at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:428)
     at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.process(Processor.java:247)
     at com.sap.engine.services.httpserver.server.rcm.RequestProcessorThread.run(RequestProcessorThread.java:45)
     at com.sap.engine.core.thread.execution.Executable.run(Executable.java:122)
     at com.sap.engine.core.thread.execution.Executable.run(Executable.java:101)
     at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:327)
Caused by: com.sap.engine.services.wssec.policy.exception.VerifyException: [ASJ.wssec.020441] Authentication failed. For details see log entry logID=68B5996B863C332C00000000000010A8 in security log.
     at com.sap.engine.services.wssec.srt.protocols.ProviderSecurityProtocol.authenticate(ProviderSecurityProtocol.java:258)
     at com.sap.engine.services.wssec.srt.protocols.ProviderSecurityProtocol.afterDeserialization(ProviderSecurityProtocol.java:687)
     ... 47 more
#2.0 #2011 04 01 16:15:46:836#+0800#Error#com.sap.engine.services.webservices.espbase.server.runtime.RuntimeProcessingEnvironment#
#BC-ESI-WS-JAV-RT#webservices_lib#68B5996B863C332E00000001000010A8#1859650000000005#sap.com/me~ear#com.sap.engine.services.webservices.espbase.server.runtime.RuntimeProcessingEnvironment#Guest#0##3A5373A25C3811E0BEB70000001C6042#3a5373a25c3811e0beb70000001c6042#3a5373a25c3811e0beb70000001c6042#0#Thread[HTTP Worker [@1423449306],5,Dedicated_Application_Thread]#Plain##
process()
[EXCEPTION]
com.sap.engine.interfaces.webservices.runtime.ProtocolException: Authentication failed. For details see log entry logID=68B5996B863C332E00000000000010A8 in security log.
     at com.sap.engine.services.wssec.srt.protocols.ProviderSecurityProtocol.logThrowable(ProviderSecurityProtocol.java:1103)
     at com.sap.engine.services.wssec.srt.protocols.ProviderSecurityProtocol.afterDeserialization(ProviderSecurityProtocol.java:719)
     at com.sap.engine.services.webservices.espbase.server.runtime.ProtocolProcessor.protocolsAfterDeserialization(ProtocolProcessor.java:156)
     at com.sap.engine.services.webservices.espbase.server.runtime.RuntimeProcessingEnvironment.preProcess(RuntimeProcessingEnvironment.java:439)
     at com.sap.engine.services.webservices.espbase.server.runtime.RuntimeProcessingEnvironment.process(RuntimeProcessingEnvironment.java:260)
     at com.sap.engine.services.webservices.runtime.servlet.ServletDispatcherImpl.doPostWOLogging(ServletDispatcherImpl.java:178)
     at com.sap.engine.services.webservices.runtime.servlet.ServletDispatcherImpl.doPostWithLogging(ServletDispatcherImpl.java:114)
     at com.sap.engine.services.webservices.runtime.servlet.ServletDispatcherImpl.doPost(ServletDispatcherImpl.java:72)
     at com.sap.engine.services.webservices.servlet.SOAPServletExt.doPost(SOAPServletExt.java:90)
Edited by: Ivan_liu_tw on Apr 1, 2011 10:30 AM

Hello.
I experienced initial version of WSRM but as I know.....
Basically FSCM data is based on PI and WSRM is just kind of cover using web service.
So you can see sync, async messages in tcode SXI_MONITOR even if WSRM configured.
As you see when set up in SOAMANAGER, WSRM just cover web service on existing PI interface and it's transfered through bgRFC, scheduler, ICM etc... but PI interface architecture is still used and only PI server is not used.
Hope it helps.

Similar Messages

Need information on Reports execution Log..

Hi All,
Need help regarding SAP Report execution log. Here Client wants to develop a report, which displays the information about reports Usage (ABAP Report, ABAP Query and Report Painter).
The report requires the following information.
1. Users who has run the report
2. T-codes of reports
3. Type of report (ABAP Report, ABAP Query and Report Painter)
4. Run times for each instance that the report was run
5. Dates for each instance that the report was run.
Requesting to share the information about the tables or function modules, where I can get the data.
Thanks in advance.
Chanda.

Hi Chanda,
The log can be seen using STAT transaction.
TXN:STAT
Give the date: The required date.
Read Time: 23:59:59
Start Time: 00:00:00 (or ur required time)
User: username/      * (for all users)
Transaction: SE38/      * (For all transactions)
Program:      ztest/
In tools option:
You have further options:
there
Wait time for collection of data (via RFC): 99999
Maximum runtime: 23:59:59
And Execute.
It displays a log of all the details required.
There are few sample programs in this link. Also check out them:
http://www.kabai.com/abaps/q.htm
Programs: 072, 065, 021, 015, 012
http://www.kabai.com/abaps/z72.htm
Best Regards,
Anjali

Finding SQL trace and Log trace in SAP ME

Dear Experts,
I am new to SAP ME SDK 2.0 development. After depolying the ME with changes.If an error occurs as "An internal error occurred; contact technical support". Where should I check for the traces like SQL trace or og trace.
Thanks in advance,
Eswaraiah M.

Hello,
Log records are written to NW log and can be viewed in NW log viewer.
Konstantin

Java.lang.NoClassDefFoundError: com/sap/tc/logging/Configurator

I have installed this NWDS 2.0.12. When I click on the icon from desktop, I see a splash screen for a second and then immediately an error message saying 'Problem during startup. Check the .log file in .metadata folder of your workspace.'
Following is the log file
!SESSION -
!ENTRY org.eclipse.core.launcher 4 0 Jun 29, 2006 16:09:37.302
!MESSAGE Exception launching the Eclipse Platform:
!STACK
java.lang.NoClassDefFoundError: com/sap/tc/logging/Configurator
 at java.lang.Class.getDeclaredConstructors0(Native Method)
 at java.lang.Class.privateGetDeclaredConstructors(Class.java:1618)
 at java.lang.Class.getConstructor0(Class.java:1930)
 at java.lang.Class.getConstructor(Class.java:1027)
 at org.eclipse.core.internal.plugins.PluginDescriptor.internalDoPluginActivation(PluginDescriptor.java:709)
 at org.eclipse.core.internal.plugins.PluginDescriptor.doPluginActivation(PluginDescriptor.java:188)
 at org.eclipse.core.internal.plugins.PluginClassLoader.activatePlugin(PluginClassLoader.java:112)
 at org.eclipse.core.internal.plugins.PluginClassLoader.internalFindClassParentsSelf(PluginClassLoader.java:185)
 at org.eclipse.core.internal.boot.DelegatingURLClassLoader.findClassParentsSelf(DelegatingURLClassLoader.java:485)
 at org.eclipse.core.internal.boot.DelegatingURLClassLoader.loadClass(DelegatingURLClassLoader.java:882)
 at org.eclipse.core.internal.boot.DelegatingURLClassLoader.loadClass(DelegatingURLClassLoader.java:862)
 at java.lang.ClassLoader.loadClass(ClassLoader.java:235)
 at org.eclipse.core.internal.plugins.PluginDescriptor.createExecutableExtension(PluginDescriptor.java:130)
 at org.eclipse.core.internal.plugins.PluginDescriptor.createExecutableExtension(PluginDescriptor.java:167)
 at org.eclipse.core.internal.plugins.ConfigurationElement.createExecutableExtension(ConfigurationElement.java:103)
 at org.eclipse.core.internal.runtime.InternalPlatform.loaderGetRunnable(InternalPlatform.java:578)
 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:324)
 at org.eclipse.core.internal.boot.InternalBootLoader.getRunnable(InternalBootLoader.java:471)
 at org.eclipse.core.internal.boot.InternalBootLoader.run(InternalBootLoader.java:854)
 at org.eclipse.core.boot.BootLoader.run(BootLoader.java:461)
 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:324)
 at com.sap.ide.eclipse.startup.Main.basicRun(Main.java:286)
 at com.sap.ide.eclipse.startup.Main.run(Main.java:784)
 at com.sap.ide.eclipse.startup.Main.main(Main.java:602)
Can somebody help me to resolve this? What should be the potential cause for the error?

java.lang.NoClassDefFoundError: com/sap/tc/logging/Configurator
Either a missing jar or the classpath is not defined right.

SAP Logging- Confuguring log-configuration.xml

Hi,
I am implementing saplogging, my log-configuration.xml looks like this.
<log-formatters>
 <log-formatter
 name="DefaultFormatter"
 type="ListFormatter"/>
</log-formatters>
<log-destinations>
<log-destination
 count="5"
 effective-severity="ALL"
 limit="80000"
 name="MyLog4Log"
 pattern="./log/applications/MyLog.%g.log" type="FileLog"/>
<log-controllers>
 <log-controller
 effective-severity="ALL"
 maximum-severity="ALL"
 minimum-severity="ALL"
 name="/Applications/myLogAP">
<associated-destinations>
 <destination-ref association-type="LOG" name="MyLog4Log"/>
</associated-destinations>
 </log-controller>
and in my class I am implementing like this.
private static Category catLogger = null;
catLogge=Category.getCategoryCategory.APPS_COMMON, "myLogAP");
catLogger.errorT(...,...,...);
It is not creating any file by name MyLog.0.log
But if I use
catLogger.addLog(new FileLog("./log/applications/MyLog.%g.log"));
it is creating file and puttion logs into it. i dont think its a good practice to use the second one.
I want to get name only from log-configuration.xml.
Please put your suggession and comments
Regards
Abhijith YS

HI,
Try,
turn off 'ForceSingleTraceFile' in visual admin
visual admin->global configuration->kernal->log manager.
but second method of yours is also good

Reg : SQL Trace and ECAT

Hi Floks ,
Any body knowing The SQL trace analysis and Ecat tool .send me how to work on this issues .Please send me with snap shot it's will help to who don't know how to utilize this tools.
thanks,
suresh

Hi suresh,
Check these links.
SQL trace
http://www.sapdevelopment.co.uk/perform/perform_sqltrace.htm
Go to st05 and activate trace, go back and run your transaction or report again go to st05 deactivate trace and click display trace here you can find information with this you can performence analysis, database tables, fields etc.
ECAT
eCATT stands for extended Computer Aided Test Tool (eCATT) which is built is testing tool to test SAP system. By using testing tool we can test the entire business process, and we can also use this tool with a third party testing tool (I am not covering this topic). Execution of every test script ends with a log, which explains the results of the test script.
By using eCATT we can do following operations,
·        Test transactions, reports, and scenarios
·        Call BAPIs and function modules
·        Test remote systems
·        Check authorizations (user profiles)
·        Test updates (database, applications, GUI)
·        Test the effect of changes to customizing settings
·        Check system messages
For more information go to
http://help.sap.com/saphelp_erp2004/helpdata/en/2a/121e3bd711bb04e10000000a114084/frameset.htm
To develop a test script in eCATT we need to follow the following steps,
1. Creating Test Scripts.
2. Creating Test Data Containers[16] .
3. Understanding System Data Containers[17] .
4. Executing Test Configurations.
There is a very good web blog on eCATT in sdn.com which explains eCATT with necessary screen shots.
To read document click here Blog on eCATT
http://www.sapdevelopment.co.uk/testing/ecatt.htm

SQL Trace(ST05) and Run Time Analysys(SE30)

Hi ABAP Experts,
Can any one explain what is the use of
1) ST05 and
2) SE30
ponits will be given for clear cut explanation
Thanks and Regards
Vijaya

Hi,
The SQL Trace part of the Performance Trace tool allows you to see how the OPEN SQL statements that you use in ABAP programs are converted to standard SQL statements (see Embedded SQL) and the parameters with which the embedded SQL statements are passed to the database system.
Overview
From the time you turn on the trace function to the time you turn it off again, all database activity occurring either for a specific user or for an entire system is recorded. The SAP System takes OPEN SQL statements and converts them in to embedded SQL statements that it passes to the database and makes the results available. The embedded SQL statement and its parameters are recorded in the SQL Trace file. The results of the SQL statement, like return code, number of entries retrieved, inserted, or deleted by the database are recorded in the SQL Trace file as well. The log file also contains the runtime of the statement and the place in the application program, respectively transaction, from which it was called which enables additional analyses (supported by the SQL Trace function).
From the recorded SQL trace you can deduce:
·        which SQL statements your application carries out
·        which values the system uses for specific database accesses and changes
·        how the system translates ABAP OPEN SQL commands (such as SELECT) into standard SQL commands
·        where your application positions COMMIT statements
·        where your application makes repeated database accesses
·        what database accesses or changes occur in the update section of your application
Create a Trace (SQL Server Profiler)
To create a trace
On the File menu, click New Trace, and connect to an instance of SQL Server.
The Trace Properties dialog box appears.
Note:
The Trace Properties dialog box fails to appear, and the trace begins instead, if Start tracing immediately after making connection is selected. To turn off this setting, on the Tools menu, click Options, and clear the Start tracing immediately after making connection check box.
In the Trace name box, type a name for the trace.
In the Use the template list, select a trace template on which to base the trace, or select Blank if you do not want to use a template.
To save the trace results, do one of the following:
Click Save to file to capture the trace to a file. Specify a value for Set maximum file size. The default value is 5 megabytes (MB).
Optionally, select Enable file rollover to automatically create new files when the maximum file size is reached. You can also optionally select Server processes trace data, which causes the service that is running the trace to process trace data instead of the client application. When the server processes trace data, no events are skipped even under stress conditions, but server performance may be affected.
Click Save to table to capture the trace to a database table.
Optionally, click Set maximum rows, and specify a value.
Caution:
When you do not save the trace results to a file or table, you can view the trace while SQL Server Profiler is open. However, you lose the trace results after you stop the trace and close SQL Server Profiler. To avoid losing the trace results in this way, click Save on the File menu to save the results before you close SQL Server Profiler.
Optionally, select the Enable trace stop time check box, and specify a stop date and time.
To add or remove events, data columns or filters, click the Events Selection tab. For more information, see: How to: Specify Events and Data Columns for a Trace File (SQL Server Profiler)
Click Run to start the trace.
Runtime analysis:
se30 is the tcode for run time analysis, is a tool it
display report based on lps for abap pragram execution
time , data base load, system load. these are all will
display in micro seconds.this tool will use for Transaction
code, function modules , abap progrmes
In Transaction SE30, fill in the transaction name or the program name which needs to be analyzed for performance tuning.
For our case, let this be ZABAP_PERF_TUNING
After giving the required inputs to the program, execute it. After the final output list has been displayed, PRESS the BACK button.
On the original SE30 screen, now click on ANALYZE button.
The percentage across each of the areas ABAP/ Database/System shows the percentage of total time used for those areas and load on these areas while running the program . The lesser the database load faster the program runs.
SQL trace:
/people/siegfried.boes/blog/2007/09/05/the-sql-trace-st05-150-quick-and-easy
SE30
/people/siegfried.boes/blog/2007/11/13/the-abap-runtime-trace-se30--quick-and-easy
regards,
vasavi.
kindly reward if helpful.

Com.sap.xmii.Illuminator.logging.LHException: java.lang.NoClassDefFoundErro

Hello,
Intermittently users get the following error when logging into the application which is built upon xmii:
com.microsoft.sqlserver.jdbc.SQLServerResource
At this point in the application it is trying to read information which is stored in a SQLServer database.
We see the following errors in trace files:
application [XMII] Processing HTTP request to servlet [Illuminator] finished with error.
The error is: com.sap.xmii.Illuminator.logging.LHException: com.sap.xmii.Illuminator.logging.LHException: java.lang.NoClassDefFoundError: com.microsoft.sqlserver.jdbc.SQLServerResource
Exception id: [00145E4D6... [see details]
This is running on a NW JavaAs 7.0 SP18, MII 12.0 SP8.
We've replaced the JDBC driver with one which SAP support told us would work, but that did not fix the problem either.
We can get the problem to go away for a period of time by simply disabling and then re-enabling the Data Server connection. It is using the IDBC Connector with a SQL connector type. STATUS shows No. Connections Used 0, No. Connections Available 1, Max No. Connections Used 2. Max. Wait Time 0.0.
Ideas?

Hi John,
Before connecting SQL server with SAP MII, try connecting SQL server independently.
It helps to narrow down the problem.
If the independent connection works fine, try connecting with SAP MII with proper JDBC drivers
Go through the SAP Note 1109274 & forum MII 12.1 - connection to MS SQL2005 database
for more information on JDBC drivers.
Thanks
Rajesh Sivaprakasam.

Urgent : How to do the SQL trace analysis

Hi Floks,
How to do the SQL Trace analysis and any another tools is there to test abap programming then this tools runtime analysis,extended Programming Checking,Code inspector .How to utilize that tools .please forward me
thanks
suresh

HI,
SQL Trace Use:
The SQL Trace function is an on-demand log of selected SQL statements that are issued against the database through the Open SQL Engine. The SQL Trace can be switched on or off dynamically. The log format is database independent. Besides the SQL statement text, each log record contains information about the point in time when the statement was executed, its duration, its input parameters and results (where applicable) as well as context information.

Features
The SQL Trace is especially useful for:
Development
SQL Trace can help JDO, enterprise beans, servlet and JSP developers to learn which kind of database accesses their code produces.
1. Performance analysis
Typically, performance issues are caused by inefficient database accesses. In this case SQL Trace can be used to show the issued SQL statements and their duration, thus helping to identify inefficient SQL statements.
Activities
Typically, you should use the SQL Trace when you need to check the behavior of a particular application. This is the following scenario:
Look at the below links, you will get the idea
http://help.sap.com/saphelp_erp2005/helpdata/en/d1/801f89454211d189710000e8322d00/content.htm
Re: Runtime Analysis vs SQL Trace
http://www.sapbrain.com/TOOLS/SQLTRACE/SQL_TRACE.html

SQL Connection to SAP Reset

Any idea why SAP would keep "forgetting" the location of a company database (SQL) and then prompt the user to provide credentials to a "local" database that does not exist?
This just started happening on a client workstation this week. Every time the user logs out of SAP, SAP can no longer see the SQL database it was attached to when it is opened each time so an administrator needs to keep manually enter the server name and credentials.
Any thoughts on this?
Thanks in advance!

Hi,
Refer this note:1156461
User profile not saved with roaming profile
Symptom
Sap Business one user settings are not saved under the user's
Local Settings folder.
When you use roaming profiles, SAP Business One user settings are
not being saved after logout from the server.
Other terms
Citrix, roaming profile, user profile
Reason and Prerequisites
Application error
Solution
SAP plans to fix this issue in a patch for 2007 A. Please refer to the info.txt file on SAP Service Marketplace to confirm that the fix was included. After the fix user setting path will be loaded from unicode configuration file.
From SAP business One 2007A SP00 PL35, edit the SAP Business One client configuration on the terminal server in
..\SAP Business One\Conf\b1-config-path.txt
Open the file and set the path to
%USERPROFILE%\Application Data\SAP\SAP Business One
Save the file. The setting will now be saved in the roaming profile.
In case of a load balancing environment including several terminal servers another issue might occur:
The profile path on one server might be "C:\Documents and Settings\USERNAME", on another server it might be "C:\Documents and Settings\USERNAME.DOMAIN". This is Windows behaviour.
This leads to incorrect entries in the "b1-current-user.xml", which is written to the profile. The "b1-current-user.xml" uses absolute path names, therefore when being directed to a server with a different profile path the information cannot be retrieved.
In this case please use the following workaround:
Create a logon script mapping the profile path to a drive, for example "S:". In the "b1-config-path.txt" use "S:\Application Data\SAP\SAP Business One". This will direct SAP Business One to the correct folder.

How to use the transaction STO5 (SQL Trace)

Hi,
I want to check the performance of program using the ST05 transaction. Please send me the step by step procedure to trace my program.
Thanks & Regards,
Santhosh Kumar.R

Hi,
following explanation clearly you abt ST05
Hi,
SQL trace(ST05) provides the developer with the ability to analyse database select statements. Simply execute ST05 to turn on SQL trace, then execute the statement/program you want to analyse. Now turn off SQL trace using ST05
and click on list trace to view the details.
You can also perform traces on other items such as authorisation objects.
The trace list has many lines that are not related to the SELECT statement in the ABAP program. This is because the execution of any ABAP program requires additional administrative SQL calls. To restrict the list output, use the filter introducing the trace list.
The trace list contains different SQL statements simultaneously related to the one SELECT statement in the ABAP program. This is because the R/3 Database Interface - a sophisticated component of the R/3 Application Server - maps every Open SQL statement to one or a series of physical database calls and brings it to execution. This mapping, crucial to R/3s performance, depends on the particular call and database system. For example, the SELECT-ENDSELECT loop on the SPFLI table in our test program is mapped to a sequence PREPARE-OPEN-FETCH of physical calls in an Oracle environment.
The WHERE clause in the trace list's SQL statement is different from the WHERE clause in the ABAP statement. This is because in an R/3 system, a client is a self-contained unit with separate master records and its own set of table data (in commercial, organizational, and technical terms). With ABAP, every Open SQL statement automatically executes within the correct client environment. For this reason, a condition with the actual client code is added to every WHERE clause if a client field is a component of the searched table.
To see a statement's execution plan, just position the cursor on the PREPARE statement and choose Explain SQL. A detailed explanation of the execution plan depends on the database system in use.
Performance Tuning is useful mainly reducing load on database. It is very important aspect while writing the programs/FM etc.....
SQL Trace
Use
The SQL Trace function is an on-demand log of selected SQL statements that are issued against the database through the Open SQL Engine. The SQL Trace can be switched on or off dynamically. The log format is database independent. Besides the SQL statement text, each log record contains information about the point in time when the statement was executed, its duration, its input parameters and results (where applicable) as well as context information.
Features
The SQL Trace is especially useful for:
Development:
SQL Trace can help JDO, enterprise beans, servlet and JSP developers to learn which kind of database accesses their code produces.
 Performance analysis
Typically, performance issues are caused by inefficient database accesses. In this case SQL Trace can be used to show the issued SQL statements and their duration, thus helping to identify inefficient SQL statements.
Functions
The following functions are available on the initial screen:
Select trace:
Select the trace mode SQL Trace, Enqueue Trace, RFC Trace, or Table Buffer Trace. You can select mutliple trace modes simultaneously.
Select trace function:
Start the trace recording.
Stop the trace recording.
Branch to trace list, detailed list, or time-sorted list.
Branch to Explain SQL to analyze an SQL statement without an explicit trace file.
Trace files are managed by the system. Thus they can be saved, like any other object;
saved trace files can be displayed and deleted.
Trace Status
A trace can only be activated once on any application server. The Trace Status display informs you whether another user in the system has already activated a particular trace.
Starting the Trace
Prerequisites
You can only switch on the Performance Trace for a single instance. You should already have decided the scope and targets of your performance analysis.
Procedure
To analyze a trace file, do the following:
... 1. Choose the menu path Test  Performance Trace in the ABAP Workbench.
The initial screen of the test tool appears. In the lower part of the screen, the status of the Performance Trace is displayed. This provides you with information as to whether any of the Performance Traces are switched on and the users for which they are enabled. It also tells you which user has switched the trace on.
2. Using the selection buttons provided, set which trace functions you wish to have switched on (SWL trace, enqueue trace, RFC trace, table buffer trace).
3. If you want to switch on the trace under your user name, choose Trace on.
If you want to pass on values for one or several filter criteria, choose Trace with Filter.
Typical filter criteria are: the name of the user, transaction name, process name, and program name.
4. Now run the program to be analyzed.
You will normally analyze the performance trace file immediately. In this case, it is a good idea to use a separate session to start, stop, and analyze the Performance Trace
If you are shown trace kernel errors on the initial screen (for example, not enough storage space available), you must first remove the errors or have them removed by your system administrator.
The selected trace types can be changed as required during a performance trace interval (time between switching on and off the trace). The user (user group) must remain unchanged.
Result
The results of the trace recording are written to a trace file. If trace records are overwritten during the trace interval, the system displays a message to inform you when you analyze the trace file.
The results of the trace recording are stored to ten trace files. Overwriting trace records, however, cannot be entirely excluded in this case either.
The Performance Trace records all database access calls, table buffer calls, remote calls, or calls for user lock activity. These measurements can affect the performance of the application server where the trace is running. To preserve system performance, you should therefore turn off the trace as soon as you finish recording your application.
Stopping the Trace
Prerequisites
You have started the trace and finished running the program that you want to analyze.
For performance reasons, you should switch off the traces as soon as you have finished recording.
Procedure
To deactivate the trace:
... 1. Choose Test Performance Trace in the ABAP Workbench.
The initial screen of the test tool appears. It contains a status line displaying the traces that are active, the users for whom they are active, and the user who activated them.
2. Select the trace functions that you want to switch off.
3. Choose Deactivate Trace.
If you started the trace yourself, you can now switch it off immediately. If the performance trace was started by a different user, a confirmation prompt appears before deactivation-
Result
The results of the trace are stored in one or more trace files. You can then analyze the performance data stored in the trace file. See also, Analyzing Performance Data.
Look at the below link
http://www.sapbrainsonline.com/TOOLS/SQLTRACE/SQL_TRACE.html
Reward with points if helpful.
Regards,
Vijay

Log configuration for CRM ISA Application.

Hi all,
I have setup the log configurations using the following SAP Note:1017756
But, the following information which is mentioned in the attached file is not clear. Can any one clarify this. what is the meaning of this.
"After making the required settings, note that you still have to start the session log in the Internet
Sales application by setting the request parameter appinfo to true, or by using the u201CSingle Session
Traceu201D link on the start.jsp"
Advance Thanks

Hi
After making the required settings, note that you still have to start the session log in the Internet
Sales application by setting the request parameter appinfo to true, or by using the u201CSingle Session
Traceu201D link on the start.jsp
--> Session log requires to take a trace from the ADMIN XCM, through which you can trace the errors within your web shop application.
The session log can be taken from the link -
http://applicaiton name:port/b2b/admin/index.jsp
Once you login to the above link (the application name and the port is applicable to your project), on the left hand menu, you will find the option for "Session Trace"
--> Also, from the XCM application (such as B2B,B2C etc), (XCM Settings), you need to set Single Session Trace = True.
Hope this will help
Regards

Problem loading log-configuration.xml

Dear Experts!
I am developing J2EE application. I created file log-configuration.xml using SAP NetWeaver Developer Studio and put it into META-INF directory in ear file. If I use SDM to deploy ear, it displays message that deployment is successful. But Logging categories and trace locations are not created (I checked it using Visual Administrator -> Log Configurator). When I run my application it writes messages to defaultTrace instead of destination described in log-configuration.xml.
I checked logs of J2EE server and logs of SDM. No error messages.
Where is my mistake? Any ideas are welcome.
WBR,
Anton

Hi Anton,
Last week I was trying to explore more on the Logging and Tracing concept and I followed these documents.
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f361cbea-0c01-0010-a3a0-8948bebb0a23
/people/sap.user72/blog/2004/11/10/log-configuration-for-a-web-dynpro-application
The Logging categories and trace locations are created and I was able to see the application specific logs in the specified location.
Also try to create a blank .log file on the server and then try running your application.
Regards,
Rekha Malavathu

How does log-configuration.xml work?

Hi,
Anyone has an idea how the "log-configuration.xml" works in Enterprise Application Project? If this properties file is configured properly, what is to be done in the code so that the log/trace messages can be written to a designated destination?
I have been trying to find a appropriate documentation, but have not been successful so far.
Appreciate if someone can share his/her experience with me.
- Teecheu

Hello,
I can not tell how the files works, but the documentation about this topic can be seen here:
Portal Developer Guide -> Portal Runtime Technology -> Portal Application Archives ->
Defining a Logger Configuration.
(http://help.sap.com/saphelp_nw04/helpdata/en/b1/441e40777cdd5fe10000000a155106/frameset.htm)
Hope that helps,
Jordan

Can not find Save botton in log configure.

Hi,
I want to change the log severity level from some application. I went to log configuration and I clicked the button for "change on selected node". However, I could not find any "Save" or "Apply" button. When I exit the page, system showed me "you will lost the unsaved data". Does anybody know how to save it? Thank you.

Hi,
Which SP level you are on? If you are on NW04 SPS12 or NW04s SPS02 or below upgrade that to NW04 SP 13 of the J2EE Engine 6.40 or NW04s SPS 03 of the J2EE Engine 6.40s or higher level.
If it is not possible due to any reason apply sap.com_tclmwebadminlog_configwd.sda
by following the note 656711.
Reward points for useful answers
Regards,
Phani

SQL Trace in SAP Manufacturing Execution Logging Configuration disappear

Similar Messages

Maybe you are looking for