SAP WebConsole and RF Devices

We have embarked on implementing SAP WebConsole in our main distribution centres using Intermec RF devices. Following our testing we have an issue when logging off SAP WebConsole were we recieve an error of "connection broken". This same condition is experienced when using Internet Explorer. The detailed information from explorer is as follows;
<html>
 <head>
 <title>SAPConsole Offline Page</title>
 </head>
 <body>
 Connection broken
 </body>
</html>
I appreciate that this may be standard behaviour when using this functionality, however, logic states that this is simply a logging out procedure therefore there should be no "error" condition experienced by the business.
Is there a way that when logging out of SAP WebConsole we can redirect the page with the default SAP WebConsole logon page and eliminate the "Connection Broken Error"
Any assistance would be appreciated, we are using SAPWEBCONSOLE 6.40, currently SAPGUI 6.40 patch level 17

No, absolutly not. I did nothing with j2ee when I install with SAPconsole/Webconsole. Also, I helped someone in the ABAP forum a couple weeks ago with this, and I told him to skip that part in the instructions, he got it working.
I have mine setup to run with IIS.
Regards,
Rich Heilman

Similar Messages

User ID has sap* rights and I get this...

Synchronization started.
Connection set up (without proxy) to: http://ap-ccms-d01:50000/meSync/servlet/meSync?~sysid=DMI&
Successfully connected with server.
Processing of inbound data began.
Server logon failed.
Not experienced with SAP MI and I do not understand why it fails to log me on. I also have S_ME_SYNC and S_RFC authorizations. Has anyone encounter this issue? Please let me know how it can be solved.
Besides creating the roles, service users is there anyting else that needs to be done on the server side?
thanks,
.adrian

Hi,
This si the trace file:
[20050512 18:19:17:248] I [MI/API/Logging ] ***** LOG / TRACE SWITCHED ON
[20050512 18:19:17:248] I [MI/API/Logging ] ***** Mobile Engine version: MI 25 SP 09 Patch 00 Build 200409101427
[20050512 18:19:17:248] I [MI/API/Logging ] ***** Current timezone: America/Los_Angeles
[20050512 18:19:17:248] I [MI ] Trace severity: All (1000)
[20050512 18:19:17:248] D [MI/API/Runtime/JSP ] AbstractMEHttpServlet:dispatch request to '/jsp/trace/trace.jsp'
[20050512 18:19:23:248] D [MI/Core ] Set current application to 'MOBILEENGINE_JSP'
[20050512 18:19:23:248] D [MI/API/Runtime/JSP ] AbstractMEHttpServlet:doPost(...) called
[20050512 18:19:23:248] D [MI/API/Runtime/JSP ] AbstractMEHttpServlet:getEvent() done with event name = 'tracesendToR3'
[20050512 18:19:23:248] D [MI/API/Runtime/JSP ] AbstractMEHttpServlet:dispatch request to '/jsp/trace/trace.jsp'
[20050512 18:19:33:201] D [MI/Core ] Set current application to 'MOBILEENGINE_JSP'
[20050512 18:19:33:201] D [MI/API/Runtime/JSP ] AbstractMEHttpServlet:doGet(...) called
[20050512 18:19:33:201] D [MI/API/Runtime/JSP ] AbstractMEHttpServlet:getEvent() done with event name = ''
[20050512 18:19:33:201] D [MI/API/Runtime/JSP ] AbstractMEHttpServlet:dispatch request to '/jsp/home/home.jsp'
[20050512 18:19:34:123] D [MI/Core ] Set current application to 'MOBILEENGINE_JSP'
[20050512 18:19:34:123] D [MI/API/Runtime/JSP ] AbstractMEHttpServlet:doGet(...) called
[20050512 18:19:34:123] D [MI/API/Runtime/JSP ] AbstractMEHttpServlet:getEvent() done with event name = ''
[20050512 18:19:34:154] D [MI/API/Runtime/JSP ] AbstractMEHttpServlet:dispatch request to '/jsp/home/syncpassword.jsp'
[20050512 18:19:38:233] D [MI/Core ] Set current application to 'MOBILEENGINE_JSP'
[20050512 18:19:38:233] D [MI/API/Runtime/JSP ] AbstractMEHttpServlet:doPost(...) called
[20050512 18:19:38:233] D [MI/API/Runtime/JSP ] AbstractMEHttpServlet:getEvent() done with event name = ''
[20050512 18:19:38:264] P [MI/Sync ] Notify R3 called
[20050512 18:19:38:264] D [MI/Sync ] There is already a container for method WAF_REGISTRY and user ABERTISA in the outbound queue
[20050512 18:19:38:264] D [MI/API/Services ] MEResourceBundle:Constructor: Create MEResourceBundle(com/sap/ip/me/awtapps/home/mobile_engine, en_US, (null))
[20050512 18:19:38:264] D [MI/API/Services ] MEResourceBundle:Constructor: Use classloader com.sap.ip.me.core.Startup@1004901
[20050512 18:19:38:264] D [MI/API/Services ] CREATED MEPropertyResourceBundle com.sap.ip.me.api.services.MEResourceBundle$MEPropertyResourceBundle@1a85d38 for bundleName: com/sap/ip/me/awtapps/home/mobile_engine with Locale: _en
[20050512 18:19:38:264] I [MI/Sync ] Synchronize with backend called, Thread=Thread-28
[20050512 18:19:38:264] I [MI/Sync ] Thread=Thread-28 took lock for synchronizeation.
[20050512 18:19:38:264] D [MI/Sync ] Synchronisation: Fire SyncEvent 0
[20050512 18:19:38:264] P [MI/Core ] Thread Thread-28 switched context to MI2853484152454429 / MI2853484152454429 (User: (SHARED), MSD: Name: / MOBILEENGINE_JSP (V. 250900), Target=, Type=com.sap.ip.me.core.FrameworkApplicationType) (stack level 1)
[20050512 18:19:38:264] I [MI/API/Sync ] SyncEvent Performing com.sap.ip.me.sync.LogSender
[20050512 18:19:38:264] P [MI/Core ] original context restored
[20050512 18:19:38:264] P [MI/Core ] Thread Thread-28 switched context to MI4142455254495341 / MI4142455254495341 (User: ABERTISA, MSD: Name: / MOBILEENGINE_JSP (V. 250900), Target=, Type=com.sap.ip.me.core.FrameworkApplicationType) (stack level 1)
[20050512 18:19:38:264] I [MI/API/Sync ] SyncEvent Performing com.sap.ip.me.apps.jsp.SyncStatus
[20050512 18:19:38:264] P [MI/Core ] original context restored
[20050512 18:19:38:264] P [MI/Core ] Thread Thread-28 switched context to MI2853484152454429 / MI2853484152454429 (User: (SHARED), MSD: Name: / MOBILEENGINE_JSP (V. 250900), Target=, Type=com.sap.ip.me.core.FrameworkApplicationType) (stack level 1)
[20050512 18:19:38:264] I [MI/API/Sync ] SyncEvent Performing com.sap.ip.me.ccms.LastSuccessfulSyncAlert
[20050512 18:19:38:264] P [MI/Core ] original context restored
[20050512 18:19:38:264] P [MI/Core ] Thread Thread-28 switched context to MI2853484152454429 / MI2853484152454429 (User: (SHARED), MSD: Name: / MOBILEENGINE_JSP (V. 250900), Target=, Type=com.sap.ip.me.core.FrameworkApplicationType) (stack level 1)
[20050512 18:19:38:264] I [MI/API/Sync ] SyncEvent Performing com.sap.ip.me.services.os.AgentManager
[20050512 18:19:38:279] D [MI/API/Services ] CREATED parent MEPropertyResourceBundle for child bundle: com.sap.ip.me.api.services.MEResourceBundle$MEPropertyResourceBundle@1a85d38 using bundle name: com/sap/ip/me/awtapps/home/mobile_engine
[20050512 18:19:38:279] D [MI/API/Runtime/JSP ] AbstractMEHttpServlet:dispatch request to '/jsp/home/home.jsp'
[20050512 18:19:38:279] P [MI/Sync ] Created outbound container for user (SHARED) and method AGENT_PARAMETERS
[20050512 18:19:38:279] P [MI/Core ] original context restored
[20050512 18:19:38:279] P [MI/Core ] Thread Thread-28 switched context to MI2853484152454429 / MI2853484152454429 (User: (SHARED), MSD: Name: / MOBILEENGINE_JSP (V. 250900), Target=, Type=com.sap.ip.me.core.FrameworkApplicationType) (stack level 1)
[20050512 18:19:38:279] I [MI/API/Sync ] SyncEvent Performing com.sap.ip.me.core.StatusUpdater
[20050512 18:19:38:279] P [MI/Core ] original context restored
[20050512 18:19:38:279] P [MI/Core ] Thread Thread-28 switched context to MI4142455254495341 / MI4142455254495341 (User: ABERTISA, MSD: Name: / MOBILEENGINE_JSP (V. 250900), Target=, Type=com.sap.ip.me.core.FrameworkApplicationType) (stack level 1)
[20050512 18:19:38:279] I [MI/API/Sync ] SyncEvent Performing com.sap.ip.me.smartsync.core.SmartSyncRuntimeManager
[20050512 18:19:38:279] D [MI/Smartsync ] User has not been installed on MW, it is not ready for sync :ABERTISA
[20050512 18:19:38:279] P [MI/Core ] original context restored
[20050512 18:19:38:279] P [MI/Core ] Thread Thread-28 switched context to MI2853484152454429 / MI2853484152454429 (User: (SHARED), MSD: Name: / MOBILEENGINE_JSP (V. 250900), Target=, Type=com.sap.ip.me.core.FrameworkApplicationType) (stack level 1)
[20050512 18:19:38:279] I [MI/API/Sync ] SyncEvent Performing com.sap.ip.me.ccms.AlertManager
[20050512 18:19:38:279] P [MI/Core ] original context restored
[20050512 18:19:38:279] P [MI/Sync ] Synchronization started for user (SHARED)
[20050512 18:19:38:279] D [MI/Sync ] PackageManager: old package file C:\Program Files\SAP Mobile Infrastructure\sync\(SHARED)\out\package.out could not be deleted
[20050512 18:19:38:279] D [MI/Sync ] PackageManager: create package with maximum 2147483647 items
[20050512 18:19:38:311] D [MI/Sync ] PackageManager: filled package with 0 acknowledge received container(s)
[20050512 18:19:38:311] D [MI/Sync ] PackageManager: filled package with 0 acknowledge container(s)
[20050512 18:19:38:342] D [MI/Sync ] PackageManager: filled package with 72 container items or headers
[20050512 18:19:38:342] D [MI/Sync ] PackageManager: filled package with 1 notify container(s)
[20050512 18:19:38:342] D [MI/Sync ] Package file C:\Program Files\SAP Mobile Infrastructure\sync\(SHARED)\out\package.out exists and can be read
[20050512 18:19:38:342] P [MI/Sync ] Synchronisation started
[20050512 18:19:38:342] D [MI/Sync ] Dumping file 'C:\Program Files\SAP Mobile Infrastructure\sync\(SHARED)\out\package.out'
INH-H[1]=0103ccd845dc23221935;;R;AGENT_PARAMETERS;;;;;NEW_PROTOCOL;;0;;3;;&INB-B[1]=0103ccd845dc23221935;TIMESTAMP;0;000000;19700101&INB-B[2]=0103ccd845dc23221935;DEVICEID;0;&INB-B[3]=0103ccd845dc23221935;USER;0;ABERTISA&INH-H[2]=0103ccdaa04bda7b4f1e;;R;AGENT_PARAMETERS;;;;;NEW_PROTOCOL;;0;;3;;&INB-B[4]=0103ccdaa04bda7b4f1e;TIMESTAMP;0;000000;19700101&INB-B[5]=0103ccdaa04bda7b4f1e;DEVICEID;0;&INB-B[6]=0103ccdaa04bda7b4f1e;USER;0;ABERTISA&INH-H[3]=0103ccde64db45e939f9;;R;AGENT_PARAMETERS;;;;;NEW_PROTOCOL;;0;;3;;&INB-B[7]=0103ccde64db45e939f9;TIMESTAMP;0;000000;19700101&INB-B[8]=0103ccde64db45e939f9;DEVICEID;0;&INB-B[9]=0103ccde64db45e939f9;USER;0;ABERTISA&INH-H[4]=0103ccdf0487191e79ad;;R;AGENT_PARAMETERS;;;;;NEW_PROTOCOL;;0;;3;;&INB-B[10]=0103ccdf0487191e79ad;TIMESTAMP;0;000000;19700101&INB-B[11]=0103ccdf0487191e79ad;DEVICEID;0;&INB-B[12]=0103ccdf0487191e79ad;USER;0;ABERTISA&INH-H[5]=0103ccdfce6f7d45e0d3;;R;AGENT_PARAMETERS;;;;;NEW_PROTOCOL;;0;;3;;&INB-B[13]=0103ccdfce6f7d45e0d3;TIMESTAMP;0;000000;19700101&INB-B[14]=0103ccdfce6f7d45e0d3;DEVICEID;0;&INB-B[15]=0103ccdfce6f7d45e0d3;USER;0;ABERTISA&INH-H[6]=0103cce33f5e86b3c61f;;R;AGENT_PARAMETERS;;;;;NEW_PROTOCOL;;0;;3;;&INB-B[16]=0103cce33f5e86b3c61f;TIMESTAMP;0;000000;19700101&INB-B[17]=0103cce33f5e86b3c61f;DEVICEID;0;&INB-B[18]=0103cce33f5e86b3c61f;USER;0;ABERTISA&INH-H[7]=0103cce46b0db12ad014;;R;AGENT_PARAMETERS;;;;;NEW_PROTOCOL;;0;;3;;&INB-B[19]=0103cce46b0db12ad014;TIMESTAMP;0;000000;19700101&INB-B[20]=0103cce46b0db12ad014;DEVICEID;0;&INB-B[21]=0103cce46b0db12ad014;USER;0;ABERTISA&INH-H[8]=0103cce58d75c6d58d46;;R;AGENT_PARAMETERS;;;;;NEW_PROTOCOL;;0;;3;;&INB-B[22]=0103cce58d75c6d58d46;TIMESTAMP;0;000000;19700101&INB-B[23]=0103cce58d75c6d58d46;DEVICEID;0;&INB-B[24]=0103cce58d75c6d58d46;USER;0;ABERTISA&INH-H[9]=0103cce82371b7e5b68e;;R;AGENT_PARAMETERS;;;;;NEW_PROTOCOL;;0;;3;;&INB-B[25]=0103cce82371b7e5b68e;TIMESTAMP;0;000000;19700101&INB-B[26]=0103cce82371b7e5b68e;DEVICEID;0;&INB-B[27]=0103cce82371b7e5b68e;USER;0;ABERTISA&INH-H[10]=0103ccea96fa4a3b9652;;R;AGENT_PARAMETERS;;;;;NEW_PROTOCOL;;0;;3;;&INB-B[28]=0103ccea96fa4a3b9652;TIMESTAMP;0;000000;19700101&INB-B[29]=0103ccea96fa4a3b9652;DEVICEID;0;&INB-B[30]=0103ccea96fa4a3b9652;USER;0;ABERTISA&INH-H[11]=0103ccec012ca062e298;;R;AGENT_PARAMETERS;;;;;NEW_PROTOCOL;;0;;3;;&INB-B[31]=0103ccec012ca062e298;TIMESTAMP;0;000000;19700101&INB-B[32]=0103ccec012ca062e298;DEVICEID;0;&INB-B[33]=0103ccec012ca062e298;USER;0;ABERTISA&INH-H[12]=0103ccf565d51f7bd8f7;;R;AGENT_PARAMETERS;;;;;NEW_PROTOCOL;;0;;3;;&INB-B[34]=0103ccf565d51f7bd8f7;TIMESTAMP;0;000000;19700101&INB-B[35]=0103ccf565d51f7bd8f7;DEVICEID;0;&INB-B[36]=0103ccf565d51f7bd8f7;USER;0;ABERTISA&INH-H[13]=0103cdf4e3416d40815c;;R;AGENT_PARAMETERS;;;;;NEW_PROTOCOL;;0;;3;;&INB-B[37]=0103cdf4e3416d40815c;TIMESTAMP;0;000000;19700101&INB-B[38]=0103cdf4e3416d40815c;DEVICEID;0;&INB-B[39]=0103cdf4e3416d40815c;USER;0;ABERTISA&INH-H[14]=0103d16e551570169713;;R;AGENT_PARAMETERS;;;;;NEW_PROTOCOL;;0;;3;;&INB-B[40]=0103d16e551570169713;TIMESTAMP;0;000000;19700101&INB-B[41]=0103d16e551570169713;DEVICEID;0;&INB-B[42]=0103d16e551570169713;USER;0;ABERTISA&INH-H[15]=0103d192e748e435f81c;;R;AGENT_PARAMETERS;;;;;NEW_PROTOCOL;;0;;3;;&INB-B[43]=0103d192e748e435f81c;TIMESTAMP;0;000000;19700101&INB-B[44]=0103d192e748e435f81c;DEVICEID;0;&INB-B[45]=0103d192e748e435f81c;USER;0;ABERTISA&INH-H[16]=0103d193f55fbd794439;;R;AGENT_PARAMETERS;;;;;NEW_PROTOCOL;;0;;3;;&INB-B[46]=0103d193f55fbd794439;TIMESTAMP;0;000000;19700101&INB-B[47]=0103d193f55fbd794439;DEVICEID;0;&INB-B[48]=0103d193f55fbd794439;USER;0;ABERTISA&INH-H[17]=0103d22044f095f427f4;;R;AGENT_PARAMETERS;;;;;NEW_PROTOCOL;;0;;3;;&INB-B[49]=0103d22044f095f427f4;TIMESTAMP;0;000000;19700101&INB-B[50]=0103d22044f095f427f4;DEVICEID;0;&INB-B[51]=0103d22044f095f427f4;USER;0;ABERTISA&INH-H[18]=0103d22213987cabb3b4;;R;AGENT_PARAMETERS;;;;;NEW_PROTOCOL;;0;;3;;&INB-B[52]=0103d22213987cabb3b4;TIMESTAMP;0;000000;19700101&INB-B[53]=0103d22213987cabb3b4;DEVICEID;0;&INB-B[54]=0103d22213987cabb3b4;USER;0;ABERTISA&INH-H[19]=0103d22213e6f159009f;;N;;;;;;NEW_PROTOCOL;;0;;0;;&
[20050512 18:19:38:342] D [MI/Sync ] End of content of file 'C:\Program Files\SAP Mobile Infrastructure\sync\(SHARED)\out\package.out'
[20050512 18:19:38:342] P [MI/Sync ] Do not use http proxy (system properties update)
[20050512 18:19:38:342] I [MI/Sync ] GzipDataCompression: Gzip data compression is switched off
[20050512 18:19:38:342] P [MI/Sync ] Sending outbound file to server.
[20050512 18:19:38:358] P [MI/Sync ] Outbound file was sent.
[20050512 18:19:38:389] P [MI/Sync ] Receiving inbound file from server.
[20050512 18:19:38:389] P [MI/Sync ] Inbound file was received.
[20050512 18:19:38:389] P [MI/Sync ] Synchronisation successfully connected
[20050512 18:19:38:389] D [MI/Sync ] Number of pending inbound containers before inbound processing = 0
[20050512 18:19:38:389] D [MI/Sync ] SyncInboundContainer: closing reader for inbound file / stream
[20050512 18:19:38:389] D [MI/Sync ] Dumping file 'C:\Program Files\SAP Mobile Infrastructure\sync\(SHARED)\inbound.sync'
&WAF_SYNC&EXCEPTION_INFO_CODE=7&
[20050512 18:19:38:389] D [MI/Sync ] End of content of file 'C:\Program Files\SAP Mobile Infrastructure\sync\(SHARED)\inbound.sync'
[20050512 18:19:38:389] P [MI/Core ] original context restored
[20050512 18:19:38:389] D [MI/Sync ] Synchronisation: Fire SyncEvent 1
[20050512 18:19:38:389] P [MI/Core ] Thread Thread-28 switched context to MI2853484152454429 / MI2853484152454429 (User: (SHARED), MSD: Name: / MOBILEENGINE_JSP (V. 250900), Target=, Type=com.sap.ip.me.core.FrameworkApplicationType) (stack level 1)
[20050512 18:19:38:389] I [MI/API/Sync ] SyncEvent Performing com.sap.ip.me.sync.LogSender
[20050512 18:19:38:389] P [MI/Core ] original context restored
[20050512 18:19:38:389] P [MI/Core ] Thread Thread-28 switched context to MI4142455254495341 / MI4142455254495341 (User: ABERTISA, MSD: Name: / MOBILEENGINE_JSP (V. 250900), Target=, Type=com.sap.ip.me.core.FrameworkApplicationType) (stack level 1)
[20050512 18:19:38:389] I [MI/API/Sync ] SyncEvent Performing com.sap.ip.me.apps.jsp.SyncStatus
[20050512 18:19:38:389] P [MI/Core ] original context restored
[20050512 18:19:38:389] P [MI/Core ] Thread Thread-28 switched context to MI2853484152454429 / MI2853484152454429 (User: (SHARED), MSD: Name: / MOBILEENGINE_JSP (V. 250900), Target=, Type=com.sap.ip.me.core.FrameworkApplicationType) (stack level 1)
[20050512 18:19:38:389] I [MI/API/Sync ] SyncEvent Performing com.sap.ip.me.ccms.LastSuccessfulSyncAlert
[20050512 18:19:38:389] P [MI/Core ] original context restored
[20050512 18:19:38:389] P [MI/Core ] Thread Thread-28 switched context to MI2853484152454429 / MI2853484152454429 (User: (SHARED), MSD: Name: / MOBILEENGINE_JSP (V. 250900), Target=, Type=com.sap.ip.me.core.FrameworkApplicationType) (stack level 1)
[20050512 18:19:38:389] I [MI/API/Sync ] SyncEvent Performing com.sap.ip.me.services.os.AgentManager
[20050512 18:19:38:389] P [MI/Core ] original context restored
[20050512 18:19:38:389] P [MI/Core ] Thread Thread-28 switched context to MI2853484152454429 / MI2853484152454429 (User: (SHARED), MSD: Name: / MOBILEENGINE_JSP (V. 250900), Target=, Type=com.sap.ip.me.core.FrameworkApplicationType) (stack level 1)
[20050512 18:19:38:389] I [MI/API/Sync ] SyncEvent Performing com.sap.ip.me.core.StatusUpdater
[20050512 18:19:38:389] P [MI/Core ] original context restored
[20050512 18:19:38:389] P [MI/Core ] Thread Thread-28 switched context to MI4142455254495341 / MI4142455254495341 (User: ABERTISA, MSD: Name: / MOBILEENGINE_JSP (V. 250900), Target=, Type=com.sap.ip.me.core.FrameworkApplicationType) (stack level 1)
[20050512 18:19:38:389] I [MI/API/Sync ] SyncEvent Performing com.sap.ip.me.smartsync.core.SmartSyncRuntimeManager
[20050512 18:19:38:389] D [MI/Smartsync ] User has not been installed on MW, it is not ready for sync :ABERTISA
[20050512 18:19:38:389] P [MI/Core ] original context restored
[20050512 18:19:38:389] P [MI/Core ] Thread Thread-28 switched context to MI2853484152454429 / MI2853484152454429 (User: (SHARED), MSD: Name: / MOBILEENGINE_JSP (V. 250900), Target=, Type=com.sap.ip.me.core.FrameworkApplicationType) (stack level 1)
[20050512 18:19:38:389] I [MI/API/Sync ] SyncEvent Performing com.sap.ip.me.ccms.AlertManager
[20050512 18:19:38:389] P [MI/Core ] original context restored
[20050512 18:19:38:389] I [MI/Sync ] Synchronization finished, Thread=Thread-28
[20050512 18:19:48:326] D [MI/Core ] Set current application to 'MOBILEENGINE_JSP'
[20050512 18:19:48:326] D [MI/API/Runtime/JSP ] AbstractMEHttpServlet:doGet(...) called
[20050512 18:19:48:326] D [MI/API/Runtime/JSP ] AbstractMEHttpServlet:getEvent() done with event name = ''
[20050512 18:19:48:326] D [MI/API/Runtime/JSP ] AbstractMEHttpServlet:dispatch request to '/jsp/home/synclog.jsp'
[20050512 18:21:04:484] D [MI/Core ] Set current application to 'MOBILEENGINE_JSP'
[20050512 18:21:04:484] D [MI/API/Runtime/JSP ] AbstractMEHttpServlet:doGet(...) called
[20050512 18:21:04:484] D [MI/API/Runtime/JSP ] AbstractMEHttpServlet:getEvent() done with event name = ''
[20050512 18:21:04:484] D [MI/API/Runtime/JSP ] AbstractMEHttpServlet:dispatch request to '/jsp/home/home.jsp'
[20050512 18:21:05:531] D [MI/Core ] Set current application to 'MOBILEENGINE_JSP'
[20050512 18:21:05:531] D [MI/API/Runtime/JSP ] AbstractMEHttpServlet:doGet(...) called
[20050512 18:21:05:531] D [MI/API/Runtime/JSP ] AbstractMEHttpServlet:getEvent() done with event name = ''
[20050512 18:21:05:531] D [MI/API/Runtime/JSP ] AbstractMEHttpServlet:dispatch request to '/jsp/trace/trace.jsp'
[20050512 18:21:07:031] D [MI/Core ] Set current application to 'MOBILEENGINE_JSP'
[20050512 18:21:07:031] D [MI/API/Runtime/JSP ] AbstractMEHttpServlet:doGet(...) called
[20050512 18:21:07:031] D [MI/API/Runtime/JSP ] AbstractMEHttpServlet:getEvent() done with event name = ''
At some point is says:
User has not been installed on MW, it is not ready for sync :ABERTISA .
What is MW?
And I think that i will need to patch the instalation since I have Mobile Engine 09 but when I look in MI through the WebConsole (http://ap-ccms-d01.corp.se.sempra.com:50000/me/WebConsole/add) I do not see version 250900 for MOBILEENGINE_JSP. I only have version 250000 and 250400.
Is this a SP issue?
thanks for your help.

SAP SCRIPT and the report

Hi Peers,
I am working on the report which calling the Form from SAP Script and displaying the form.
I wanted a selection screen in which if the user enters some value it should automatically preview in the form.
I am really new to the ABAP Pls some help on this .
Any code is appreciated.
Every answers will be rewarded.
Pls peers help on this.
Seema.

Hi,
where is a simple example:
PARAMETERS: KUNNR(10).
PARAMETERS: PREVI AS CHECKBOX DEFAULT 'X'.
START-OF-SELECTION.
PERFORM OPEN_FORM.
PERFORM START_FORM.
PERFORM PRINT_DATA.
PERFORM END_FORM.
PERFORM CLOSE_FORM.
*&      Form OPEN_FORM
FORM OPEN_FORM.
CLEAR ITCPO.
ITCPO-TDCOPIES = 1.
ITCPO-TDDEST = PRINTER.
IF PREVI = 'X'.
    ITCPO-TDPREVIEW = 'X'.
ENDIF.
ITCPO-TDNEWID = 'X'.
ITCPO-TDDATASET = 'test'.
ITCPO-TDSUFFIX1 = PRINTER.
ITCPO-TDSUFFIX2 = 'test'.
ITCPO-TDDELETE = ' '.                " Não eliminar imediatamente
CALL FUNCTION 'OPEN_FORM'
       EXPORTING
            DEVICE   = 'PRINTER'
            DIALOG   = ' '
            FORM     = 'YOUR_FORM_NAME'
            LANGUAGE = SY-LANGU
            OPTIONS = ITCPO
       EXCEPTIONS
            CANCELED = 1
            DEVICE   = 2
            FORM     = 3
            OPTIONS = 4
            UNCLOSED = 5
            OTHERS   = 6.
ENDFORM.                    " OPEN_FORM
*&      Form START_FORM
FORM START_FORM.
CALL FUNCTION 'START_FORM'
       EXPORTING
            LANGUAGE = SY-LANGU.
ENDFORM.                    " START_FORM
*&      Form PRINT_DATA
FORM PRINT_DATA.
SELECT * FROM KNA1 WHERE KUNNR EQ KUNNR.
    CALL FUNCTION 'WRITE_FORM'
         EXPORTING
              ELEMENT = 'TEST'
              WINDOW = 'MAIN'.
ENDFORM.                    " PRINT_DATA
*&      Form END_FORM
FORM END_FORM.
CALL FUNCTION 'END_FORM'.
ENDFORM.                    " END_FORM
*&      Form CLOSE_FORM
FORM CLOSE_FORM.
CALL FUNCTION 'CLOSE_FORM'
       EXCEPTIONS
            UNOPENED = 1
            OTHERS   = 2.
ENDFORM.                    " CLOSE_FORM
Then, you must create your SapScript in order to print some information.
Regards,

SAP - SYCLO and MAM(2.5/ 3.0) Direction....?

All,
We have a couple of core business process(Coal yard operator rounds, Fueling applications) running very successfuly using MAM2.5 and MI 7.0.
Quite recently, SAP entered into an agreement with Syclo to offer field service management on mobile devices , which will include functionality for work order execution, operator rounds, time entry and material management. Does anyone have more info and details into this and how this impacts the roadmap of MAM and whether migration of MAM 2.5 /MAM3.0 would be a option?
Any additional insights would greatly be appreciated.
Best Regards
Narasimhan

Hi Narasimhan
With more and more Mobile devices flooding the market and each device coming with its own OS and support for different technologies, SAP's mobile strategy is now focused more providing its customers and field users with native and richer UI experience, on demand data (Push from server), better device management & administration and so on. Starting NetWeaver Mobile 7.1, SAP has entered into tie ups with different partners like RIM, Sybase, Syclo etc to provide customers the advantage of two worlds - SAPs know how of core business processes and partners know how of instant push, device management and so on.
With regard to MAM, you would be aware that currently none of the versions of MAM is supported on the latest Mobile 7.1 platform and these versions MAM 2.5/3.0 work perfectly only on MI 2.5 and 7.0. All versions of SAP standard applications will continue to be supported only on MI 2.5 and 7.0 and you can continue to use/upgrade on this platform. But the same cannot be said with Mobile 7.1. The Syclo partnership could be the future of MAM / MAU on the newer platform with partner based co-innovation.
Best Regards
Sivakumar
PS: This is only my personal thought and does not in any way reflect SAP's roadmap or strategy on Mobile

MII GUI's on smartphone and Android devices

Hi,
I would like to make MII GUI's capabale to run on smartphones and Android devices. Could you please help on this?
I am using MII 14.0 version.
Any help on this very much appreciated
Thanks
Shaji Chandran

Hi Saji
Any HTML content will work on smartphones. If you mean Applets as MII GUI then you might have a tougher proposition. However as you are already on MII 14.0 why don't you try out the HTML5 based Grid and Charts. You would need SP04 for that. These charts and grids would work perfectly with smartphones.
See this link for more details
SAP UI5 - SAP Manufacturing Integration and Intelligence - SAP Library
Best regards
Partha

RFID support in SAP WM and EWM

Hello,
I have a question regarding the RFID support in SAP WM and EWM.
Which functions and processes are supported by WM and which are supported by EWM?
What are the benefits in EWM regarding RFID compared to WM?
Thanks,
Dennis

Dear Sridharan,
There are many Third party RFID addons available for SAP B1. You would be able to find them on the following locations :
For a complete list of certified partners proficient in auto-ID device and device controller technology (as known as device middleware),
please visit [http://www.sap.com/partners/directories/SearchSolution.epx|http://www.sap.com/partners/directories/SearchSolution.epx] and look under AII-DC-RFID 1.0 u2013 Auto ID Infrastr. Device Controller 1.0.
OR
http://www.sap.com/ecosystem/customers/directories/ProductSearchResults.epx?context=21B87D61C0F646A22B2A6DB254A010CA8C9C141B7529F02972463D54EC8217D707ADFB1B61328B27A6200891D1824987C4A2286C415FA5583A680E633FB258D6F702338D4AE86843C5ADEB30E7160581899BB4603C9793EC%7c340236E25FA0CB7D55B412C7D619D9145637D00350BF5E7252AE3D635139EE29F2E773C21D61F3C628E6641C68D965A961E924180F425F3FB48176F04101324CE205C8C3C132479A49D11318234269D36908F39C6F4B37B6A9C80DB2F7715F8677923A8F9F1BEBC61512000CAE2C5C98
PS: Any Addon that can work on B1 SDK 2005A, should be able to work on B1 2005B also, but there might be some specific localization scenarios that need to be taken care off. For that I would recommend you either to contact the manufacturer of the Addon or you can also create the Addon yourself.
Regards
Arshdeep

SAP Auto-ID Infrastructure Device Controller Interface

Hi,
Could you please explain the use of SAP Auto-ID Infrastructure Device Controller Interface?
Thanks & Regards
Sara

Hi Sara,
SAP Device Controller Interface is the interface that will be used by device controller softwares to send data to SAP AII and vice versa. Device controllers filter the RFID reads and send a unique read event to SAP AII. SAP AII on receiving this message processes it. It can be the case that as part of processing we also require to send data back to devices/controller or send a command such as tag commissioning. At this time also the same interface is used.
Regards,
Yogesh Bhatia..

Is MI WebConsole and NetWeaver Administrator- Mobile Administrator SAME ?

Hi
I am trying to access MI - WebConsole but could not make it.
I have SAP Web AS 7.0 with MI 2.5 installed with latest service packs. After all configuration (SAP MI 2.5 SP17 Standard install/config guide), I could not get SAP MI WebConsole. Getting 404 error.
After reading few documents I have an assumption/suspection that
MI WebConsole is for SAP Web AS 6.4 and
NetWeaver Administrator -> Mobile Administrator for SAP Web AS 7.0
to do the same functionality.
So the question is...
is MI WebConsole (http://<server:port>/me/WebConsole/login
will not work in SAP Web AS 7.0 as it has been replaced by NetWeaver Administrator -> Mobile Administration ?
(http://<server:port>/nwa
If not, do we still need MI WebConsole inorder to make communication between R/3 (ABAP stack) and MI 2.5 Client(laptop)
Even http://<server>:50100/me is not working. Always getting 404 Error.
I have http and https configured successfully.
Please advice.
Here is my system landscape for the reference:
SAP MI 2.5 (middleware) -> installed in a separate server with ABAB+JAVA stack and SAP Web AS 7.0.
SAP ERP 2005 (backend) -> installed in a separate server with ABAB stack only and SAP Web AS 6.40
SAP MI 2.5 (client) -> installed in a laptop with Windows XP Pro.

hello sri,
java sync servlet and MI WebConsole will still be supported
for awhile when the Mobile NWA gets matured...
MI WebConsole is only an administration tool, the MI Sync
Servlet is the one responsible for data transfers from
your MI client to MW. In 7.0, the Mobile NWA will become
the primary tool instead of the MI WebConsole and java
sync servlet will also be substituted by the ABAP sync
service. you can easily configure you MI using templates.
your errors might be some configuration problems.
try tracing for exceptions in your J2EE visual admin.
regards
jo

SAP Fiori and Afaria

Hi everyone
I am not familiar with Afaria besides the fact that its a mobile device management tool. What I want to know is how does does Afaria work with SAP Fiori and what are the pros and cons of deploying SAP Fiori with/on Afaria and do I need Fiori client if I decide to use Afaria?
Kind regards

Hi Eli,
You could use Afaria to configure Fiori Client - pre-configure Fiori URL, deploy app to device remotely, install certificate in device for authentication in the case of HTTPS.
Regards,Midhun
SAP Technology RIG

Is this possible: SNC connection from SAP GUI to SAP Router, and ...

Hi,
I have (stupid perhaps) question.
Is this scenario possible:
SNC connection from SAP GUI to SAP Router, and non-SNC connection from SAP Router to SAP System.
I know how to set up scenario like this:
SAP System --- (non-SNC conn) --- saprouter1 --- (SNC conn) --- saprouter2 --- (non-SNC conn) --- SAP GUI.
Best regards,
Marek Majchrowski

Wolfgang,
To be sure myself and Marek understand, can you confirm the different scenarios supported:
Scenario 1:
SAP GUI --- (non SNC conn) --- saprouter1 --- (SNC conn) --- saprouter2 --- (non-SNC conn) --- SAP System
With this scenario, it would be possible for a user to logon using SAP GUI onto the SAP System, but without SAP GUI SNC.
Scenario 2:
SAP GUI --- (SNC conn) --- saprouter1 --- (non SNC conn) --- saprouter2 --- (SNC conn) --- SAP System
With this scenario it would be possible to logon to the SAP System using SAP GUI, and using SNC authentication.
Also, with this scenario the SAP GUI software and SAP System software would consider this to be similar to:
SAP GUI -- (SNC conn) -- SAP System
Scenario 3:
This is the scenario mentioned by Marek in his initial question:
SAP GUI -- (SNC conn) -- saprouter1 -- (non SNC conn) -- SAP System
With this scenario it will not be possible to logon to SAP System using SNC, and only possible if the SAP GUI is configured to not use SNC. In other words the SNC connection between SAP GUI and saprouter1 is available, but cannot be used.
Thanks,
Tim
Edited by: Tim Alsop on Feb 25, 2008 5:24 PM

Re: what is difference between sap locking and database locking

hi,
    what is difference between sap locking and database locking. Iam locked the table mara by using lock objects.
But iam unable to unlock the mara table. I give u the coding. Please check it.
REPORT zlock .
CALL FUNCTION 'ENQUEUE_EZTEST3'
EXPORTING
   MODE_MARA            = 'S'
   MANDT                = SY-MANDT
   MATNR                = 'SOU-1'.
call transaction 'MM02'.
CALL FUNCTION 'DEQUEUE_EZTEST3'
     EXPORTING
          mode_mara = 'E'
          mandt     = sy-mandt
          matnr     = 'SOU-1'.
IF sy-subrc = 0.
WRITE: 'IT IS unlocked'.
ENDIF.

Hi Paluri
Here is the difference between SAP locks and Database locks, i will try to find the solution to your code.
Regards
Ashish
Database Locks: The database system automatically sets database locks when it receives change statements (INSERT, UPDATE, MODIFY, DELETE) from a program. Database locks are physical locks on the database entries affected by these statements. You can only set a lock for an existing database entry, since the lock mechanism uses a lock flag in the entry. These flags are automatically deleted in each database commit. This means that database locks can never be set for longer than a single database LUW; in other words, a single dialog step in an R/3 application program.
Physical locks in the database system are therefore insufficient for the requirements of an R/3 transaction. Locks in the R/3 System must remain set for the duration of a whole SAP LUW, that is, over several dialog steps. They must also be capable of being handled by different work processes and even different application servers. Consequently, each lock must apply on all servers in that R/3 System.
SAP Locks:
To complement the SAP LUW concept, in which bundled database changes are made in a single database LUW, the R/3 System also contains a lock mechanism, fully independent of database locks, that allows you to set a lock that spans several dialog steps. These locks are known as SAP locks.
The SAP lock concept is based on lock objects. Lock objects allow you to set an SAP lock for an entire application object. An application object consists of one or more entries in a database table, or entries from more than one database table that are linked using foreign key relationships.
Before you can set an SAP lock in an ABAP program, you must first create a lock object in the ABAP Dictionary.

What is difference between SAP R3 And SAP IS Mills Product

HI Friends
What is difference between SAP R3 And SAP IS Mills Product
What are the futures are availables in IS MIlls
Regards

Hi,
SAP R/3 is the central enterprise version. It is not specifically designed for any inducstry sectors and it can cater many of the industry types.
Is is developed for specific industries an for SMB's (small and medium business). It will have components specifically for the industry.
The SAP Mill Products component adds sector-specific functionality to an ERP system to satisfy the complex requirements of mill industries (e.g. metal, wood, paper, textiles, construction materials, and cable sectors).
These industry segments differ from others primarily in that the materials used have a large number of characteristics and variants. The materials in the segments listed above are also predominantly area-based (e.g. paper, textiles, plastic film) or length-based (e.g. cables, piping). Account must be taken of these material characteristics throughout the entire supply chain.
To cater for the particularities of these industry segments, SAP Mill Products features processes and functions that cover the entire supply-chain cycle from product design and configuration, through planning, order processing, capacity planning and production, to final delivery. Additional functions are available in costing and inventory management. SAP Mill Products are also integrated into Quality Management, Financial Accounting, and Controlling.
Prase

Diff b/w SAP LUW and DB LUW?

2. what is the diff b/w SAP LUW and DB LUW?

Database LUW : <a href="http://help.sap.com/saphelp_nw04/helpdata/en/41/7af4bca79e11d1950f0000e82de14a/frameset.htm">LInk</a>
Sap LUW : <a href="http://help.sap.com/saphelp_nw04/helpdata/en/41/7af4bca79e11d1950f0000e82de14a/frameset.htm">Link</a>
Thanks
Mahesh

What is the diff b/w Sap Scripts and Smart Forms

Hi,
Whats the diff b/w SAP Scripts and Smart Forms..
I need the internal explanation for both Smart Forms and SAP Scripts mean when we execute what happens whether Print Program r Forms starts execution 1st and SIMILARLY FOR SMARTFORMS WHETHER FM'S R FORMS.
Thanks & Regards,
Gopi.

Hi
Difference with SMARTFORMS vs. SapScript(SE71)
The Following are the differences :-
a) Multiple page formats are possible in smartforms which is not the case in SAPScripts
b) It is possible to have a smartform without a main window .
c) Labels cannot be created in smartforms.
d) Routines can be written in smartforms tool.
e) Smartforms generates a function module when activated.
f) Unlike sapscripts (RSTXSCRP), you cannot upload/download Smartform to your local harddisk.
It was said that it was provided in CRM 3.0 version, but not available in R/3. You can download smartforms into Local PC in a XML format. In the same way you can upload this XML format into Smartform. From the smartform editor itself you can call download option, if you are working in CRM 3.0 environment.
In R3 also, you can download into XML format. However, it's not sure about uploading. Refer to the program 'SF_XSF_DEMO'.
In 4.7 Enterprise, other have seen this utlity which is completey missing in 4.6c. There is functionality to downlaod a complete form or only a particular node. (Utilities -> Download form). It will create a XML file and save it in the hard disk.
For others, if you want to download/upload the Smartforms source, you will need the help from the Basis people. What you can do is to create a Transport and then FTP down to your local harddisk. When you need the Smartform source in another system, you have FTP up the Smartforms file back to the SAP server. Finally, the Basis team, will tp it into your system.
g) The protect and endprotect command in sapscript doesn't work with smartforms. For example on a invoice: First data of position no 80. is printed on page one, other data of position no 80 is printed on page 2. And there's nothing you can do about it. Actually, there is something you can do about it. By using a folder node and checking the 'protect' checkbox, everything in that folder will be page protected.
check out this link:
http://www.sap-img.com/smartforms/sap-smart-forms.htm
Reward points if helpful.
Regards,
Swathi.

What is the diffrence between sap events and application events

Hi all,
what is the diffrence between sap events and application events.Can any one tell me with examples.
regards,

Hi,
Look at this,
System Events (Default)
The event is passed to the application server, but does not trigger the PAI. If you have registered an event handler method in your ABAP program for the event (using the SET HANDLER statement), this method is executed on the application server.
Within the event handler method, you can use the static method SET_NEW_OK_CODE of the global class CL_GUI_CFW to set a function code and trigger the PAI event yourself. After the PAI has been processed, the PBO event of the next screen is triggered.
The advantage of using this technique is that the event handler method is executed automatically and there are no conflicts with the automatic input checks associated with the screen. The disadvantage is that the contents of the screen fields are not transported to the program, which means that obsolete values could appear on the next screen. You can work around this by using the SET_NEW_OK_CODE method to trigger field transport and the PAI event after the event handler has finished.
Application Events
The event is passed to the application server, and triggers the PAI. The function code that you pass contains an internal identifier. You do not have to evaluate this in your ABAP program. Instead, if you want to handle the event, you must include a method call in a PAI dialog module for the static method DISPATCH of the global class CL_GUI_CFW. If you have defined an event handler method in your ABAP program for the event (using the SET HANDLER statement), the DISPATCH method calls it. After the event handler has been processed, control returns to the PAI event after the DISPATCH statement and PAI processing continues.
The advantage of this is that you can specify yourself the point at which the event is handled, and the contents of the screen fields are transported to the application server beforehand. The disadvantage is that this kind of event handling can lead to conflicts with the automatic input checks on the screen, causing events to be lost.
Hope u understood.
Thanks&Regards,
Ruthra.R

SAP WebConsole and RF Devices

Similar Messages

Maybe you are looking for