WD backend call

Hello! Experts,
I am given a task to write Technical Specs which include Web Dynpro for ABAP (WD4A), since i am new to WD4A i need an expert comment on my below scenario.
My WD4A needs to fetch records from R/3; as in WD for Java we will write a Method to call BAPI; in WD4A how it works.
As it is WD4A MVC i am sure there will be models to call BAPI's. But can i directly execute / read data from R/3 without a BAPI?
FYI, this call will be executed multiple times in different scenarios; so will you suggest to go for a custom BAPI or how?
It will be great if you share and docs where it mentions the best-practices of reading R/3 data in WD4A.
Thanks!
Regards,
Kishore

Hi
You don't find Model in Web Dynpro ABAP, however it is the developers responsibility to make sure your Model is seperated from your View and Controller.
In WDA there is nothing like Model as we have in WDJ and model classes in BSP.
also you can find there is no Model Node in WDA.
Most of the Developers, create seperate classes or function modules to write there business logic and store the busienss data and perform calls to the appropriate methods and function modules to retrieve the data.
As a practice, we should not write data base  statements like Select, Update etc.. in the Controller, the framework will not stop you doing so.
Abhi
Edited by: Abhimanyu Lagishetti on Jun 12, 2008 11:23 AM

Similar Messages

  • Error when running backend call in a thread

    Hi,
    When trying to execute a RFC call from a thread in a webdynpro componennt, I am getting the follwing error.
         Unable to access Task Scope in DynamicRFCModelClass. Either run in Engine, or turn Test mode on in WDModelFactory!
    Thnakd and Regards,
    Aditya

    Hi Aditya
    I think that WebDynpro Java application cannot launch any threads in general. The reason is the WebDynpro application is fully controlled by WebDynpro framework (container), but your custom thread launched is working outside the WebDynpro framework and cannot properly access all the WebDynpro API and services.
    BR, Siarhei

  • Trying to interrupt an RMI call

    We're trying to interrupt a call to a Weblogic RMI stub via
    Thread.interrupt(). Doesn't seem to work. Can someone confirm that
    this will never work, or might we be doing something wrong?
    Why is this posted to the performance newsgroup? We're trying to build
    a web service with a guaranteed response time. The servlet makes a
    backend call via RMI. Before we make the RMI call, the servlet thread
    requests another thread to interrupt it if the call takes too long. If
    we can't interrupt the calling thread, there are only two options I can
    think of. 1) Have the servlet thread pass the request to another thread
    that can block. The servlet thread then waits on a queue for a
    response, and can be interrupted. 2) Don't use weblogic RMI, and build
    our own transport. Yuck.
    Any ideas?
    -Tim

    Tim Harrison wrote:
    Out of curiousity, do you guarantee end to end response time or just the
    time that the request will be processed on your site.Hi Rob. End-to-end, of course! We're using a Reuters network that
    bypasses the internet. :)
    Ok, I'm just kidding. We'll just start with the guaranteed process
    time.
    That's what I thought :>
    >
    I'd be surprised if no one else has run into this issue with RMI. A
    collegue of mine is building a test with Sun RMI to see if that is
    interruptable. It seems that Weblogic might be catching the interrupt
    exception below the stub level. When we interrupt a thread blocked in
    an RMI call, the thread returns normally (after completing), and
    Thread.isInterrupted() is false. I think that means that something in
    the call is reseting the status. A quick glance at the generated stub
    code does not seem to indicate anything, so I'm guessing it's at a lower
    level.
    Well, it depends on what we are doing when you attempt to interrupt our
    thread. Most likely (since it's a stub waiting for a response from the server)
    the RMI thread is blocked in a socket read system call. Depending on the
    operating system and how javasoft implemented it, it may or may not be
    interruptable.
    -- Rob
    Rob Woollen
    Software Engineer
    BEA WebLogic
    [email protected]
    >
    -Tim

  • Remote call function and destination

    Hi all @SAPforums,
    I used to call remotely a custom function, in a report, from many backends:
    CALL FUNCTION ZFOO destination mydest
    where mydest is a string containing the name of an RFC destination.
    My question is: is there a way, on the destination machine, to get the name/id of the "caller" ?
    The question arises from this task: I have to use the caller ID in a WHERE clause of a SELECT statement I have to write in ZFOO. I can - of course - pass the caller ID by adding a new parameter to the function, but this would make necessary a change on the CALL FUNCTION in every backend (quite expensive task, in terms of time). So if it's possible, from the callee, to get the name of the caller, I could just modify the function leaving the calls in every backend as they are.
    Thanks in advance

    >
    Matteo Montalto wrote:
    > Hello Wolfgang,
    > sorry for the stupid question... what does "destination" stands for?
    > Thanks for the help
    Hi ,
    they are two types of RFC calling is ther..
    1......
    CALL FUNCTION "function0module-name' DESTINATION "DEST" 
    --that means you are picking data from another r/3 sytem using detination from 'DEST'..
    2....
    CALL FUNCTION "function0module-name' IN BACKGROUND TASK DESTINATION "DEST" 
    --that means you are sending data to another r/3 sytem or any other sytem XI or and EDI
    using detination from 'DEST'..
    for 1 and 2..
    --go to t-code SM59 and see the DEST what type of connection is and what system it is connected..
    Regards,
    Prabhudas

  • How to call webdynpro applications from outside

    Hi
    I have a requirement where i need to call below webdynpro application from outside (for ex CRM,ISA..) environments
    http://test.com/webdynpro/dispatcher/test/eomp~eompapp/EmpDisp?EmpNo=0500002203.  When i am running this application from
    browser , my application working fine and i am able to see call to the backend BAPI's.  But when I configure this url
    in the configurations of the above environment.  I am unable to run this application.
    Any Idea?
    Thanks
    Prasad

    Hi
    I am not getting any error, but the backend call not hapening.  I put a debugger in the backend BAPI and run the webdynpro application , no input parameters came or call came to the the backend BAPI.
    Thanks
    Prasad

  • Channel.Call.Failed

    Hi All,
         We are using Flex 3 and BlazeDS in my project. I am getting following error when user performs some backend calls. After some time we are not getting any error for the same backend call. It is happening very randomly
    fault = (mx.rpc::Fault)#243
        errorID = 0
        faultCode = "Channel.Call.Failed"
        faultDetail = "NetConnection.Call.Failed: HTTP: Failed"
        faultString = "error"
        message = "faultCode:Channel.Call.Failed faultString:'error' faultDetail:'NetConnection.Call.Failed: HTTP: Failed'"
        name = "Error"
        rootCause = (Object)#244
          code = "NetConnection.Call.Failed"
          description = "HTTP: Failed"
          details = "https://<server>/<context root>/fmb/amfsecure"
          level = "error"
    Kindly suggest me a solution for this.
    Thanks,
    Pradeep.

    After a lots of research, I found following request is send from Flex to Server as:
    03-Feb-11 04:27:03 DEBUG Logger Endpoint.AMF : Deserializing AMF/HTTP request
    Version: 3
      (Message #0 targetURI=null, responseURI=/73)
        (Array #0)
          [0] = (Typed Object #0 'flex.messaging.messages.CommandMessage')
           operation = 12
            correlationId = ""
            body = (Object #1)
            messageId = "1EDDFEEA-C98A-B355-332F-EAD8A753232C"
            clientId = null
            timeToLive = 0
            timestamp = 0
            headers = (Object #2)
              DSId = "19FCCA68-EB08-EFBE-EEDA-4C8582B5A291"
            destination = ""
    Flex sends CommandMessage.DISCONNECT_OPERATION request to Server.
    I want to know exactly why/when this request is send to server.
    Looking forward to a positive response

  • Unable to Synchronize

    I have an MI Server Installed. It worked well for nearly a month. The server version info in brief is WebAS 6.40 with SP20. MI Client's version is SP20.Now I am getting a strange problem. For a new installation of  the Client, when I create a new User in the client (As usual) which is already created in the MiddleWare, and sync for the First time, I am not getting the Device ID generated.The trouble is, it is not showing any synchronizing errors. The screen simply says "Synchronization Completed".
    Attached is the Trace file from the Client (Debugging Mode). There is one entry from where I want you to take careful notice of; I have bolded the same below. Has anybody faced this problem before? I have checked the CCMS monitors for any errors, but to no avail.The trace is where I have got the confusion. Further for your information, all the background jobs are running properly.
    [20070820 13:32:39:825] I [MI/API/Logging ] ***** Current Trace Level: 90 
    [20070820 13:32:39:825] I [MI ] Trace severity: Debug (90) 
    [20070820 13:32:39:825] D [MI/PIOS ] No implementations found. Error Code:(3) 
    [20070820 13:32:39:825] D [MI/API/Runtime/JSP ] AbstractMEHttpServlet:dispatch request to '/jsp/trace/trace.jsp' 
    [20070820 13:32:42:997] D [MI/Core ] Set current application to 'MOBILEENGINE_JSP' 
    [20070820 13:32:42:997] D [MI/API/Runtime/JSP ] AbstractMEHttpServlet:doGet(...) called 
    [20070820 13:32:42:997] D [MI/API/Runtime/JSP ] AbstractMEHttpServlet:getEvent() done with event name = '' 
    [20070820 13:32:42:997] D [MI/API/Runtime/JSP ] AbstractMEHttpServlet:dispatch request to '/jsp/home/home.jsp' 
    [20070820 13:32:44:872] D [MI/Core ] Set current application to 'MOBILEENGINE_JSP' 
    [20070820 13:32:44:872] D [MI/API/Runtime/JSP ] AbstractMEHttpServlet:doGet(...) called 
    [20070820 13:32:44:872] D [MI/API/Runtime/JSP ] AbstractMEHttpServlet:getEvent() done with event name = '' 
    [20070820 13:32:44:872] D [MI/API/Runtime/JSP ] AbstractMEHttpServlet:dispatch request to '/jsp/home/syncpassword.jsp' 
    [20070820 13:32:48:685] D [MI/Core ] Set current application to 'MOBILEENGINE_JSP' 
    [20070820 13:32:48:685] D [MI/API/Runtime/JSP ] AbstractMEHttpServlet:doGet(...) called 
    [20070820 13:32:48:685] D [MI/API/Runtime/JSP ] AbstractMEHttpServlet:getEvent() done with event name = '' 
    [20070820 13:32:48:685] P [MI/Sync ] Notify R3 called 
    [20070820 13:32:48:685] D [MI/Sync ] Successfully added container for method WAF_REGISTRY and user DEVELOPER to the outbound queue 
    [20070820 13:32:48:685] D [MI/Sync ] Opened temporary container file F:\Program Files\SAP Mobile Infrastructure\sync\DEVELOPER\out\t0000007.sync for write (container id = 01148379c2ad4686a00f) 
    [20070820 13:32:48:700] D [MI/Sync ] Write container header to file (container id = 01148379c2ad4686a00f): F:\Program Files\SAP Mobile Infrastructure\sync\DEVELOPER\out\z0000007.sync 
    [20070820 13:32:48:700] D [MI/Sync ] Closed container file (container id = 01148379c2ad4686a00f) and rename container file to F:\Program Files\SAP Mobile Infrastructure\sync\DEVELOPER\out\i0000007.sync 
    [20070820 13:32:48:700] P [MI/Sync ] Created outbound container for user DEVELOPER and method WAF_REGISTRY 
    [20070820 13:32:48:716] I [MI/Sync ] Synchronize with backend called, Thread=Thread-40 
    [20070820 13:32:48:716] I [MI/Sync ] Thread=Thread-40 took lock for synchronization. 
    [20070820 13:32:48:716] D [MI/API/Runtime/JSP ] AbstractMEHttpServlet:dispatch request to '/jsp/home/home.jsp' 
    [20070820 13:32:48:716] P [MI/Sync ] Use following gateway for synchronization: http://psc-pc11741:50000 
    [20070820 13:32:48:716] D [MI/API/Services ] UrlConnectionTest: returning instance for same host psc-pc11741 
    [20070820 13:32:48:716] D [MI/API/Services ] UrlConnectionTest: lastHostChecked was psc-pc11741 
    [20070820 13:32:48:716] D [MI/API/Services ] UrlConnectionTest: lastTimeOfCheck was 1187616670857 
    [20070820 13:32:48:716] D [MI/API/Services ] UrlConnectionTest: last check was 97859 ms ago 
    [20070820 13:32:48:716] D [MI/API/Services ] UrlConnectionTest: try number: 1 
    [20070820 13:32:48:716] D [MI/API/Services ] UrlConnectionTestThread: method run() started... 
    [20070820 13:32:48:716] D [MI/API/Services ] F:\Program Files\SAP Mobile Infrastructure\proxyauth.txt does not exist, therefore no Proxy-Authorization is set. 
    [20070820 13:32:48:716] D [MI/API/Services ] UrlConnectionTestThread: URL protocol is http 
    [20070820 13:32:48:716] D [MI/API/Services ] UrlConnectionTestThread: HTTP responsecode is 200 
    [20070820 13:32:49:216] D [MI/API/Services ] UrlConnectionTest: it took 500 ms to test the connection 
    [20070820 13:32:49:216] P [MI/API/Services ] UrlConnectionTest: Connection could be established!!! 
    [20070820 13:32:49:216] P [MI/API/Services ] URL connection test was successfull!!! 
    [20070820 13:32:49:216] D [MI/Sync ] Synchronisation: Fire SyncEvent 0 
    [20070820 13:32:49:216] D [MI/API/Sync ] SyncEvent com.sap.ip.me.api.sync.SyncEvent[source=com.sap.ip.me.sync.SyncManagerMerger@e1eea8] skipped for User because he has not been installed on MW. 
    [20070820 13:32:49:216] D [MI/API/Sync ] SyncEvent com.sap.ip.me.api.sync.SyncEvent[source=com.sap.ip.me.sync.SyncManagerMerger@e1eea8] skipped for User because he has not been installed on MW. 
    [20070820 13:32:49:216] D [MI/API/Sync ] SyncEvent com.sap.ip.me.api.sync.SyncEvent[source=com.sap.ip.me.sync.SyncManagerMerger@e1eea8] skipped for User because he has not been installed on MW. 
    [20070820 13:32:49:216] I [MI/API/Sync ] Skip performing Sync Event (0) com.sap.ip.me.core.StatusUpdater for conversation id MI4d495f53455256494345 / MI4d495f53455256494345 (User: MI_SERVICE, MSD: Name: / MOBILEENGINE_JSP (V. 252000), Target=, Type=com.sap.ip.me.core.FrameworkApplicationType) 
    <b>[20070820 13:32:49:216] D [MI/API/Sync ] SyncEvent com.sap.ip.me.api.sync.SyncEvent[source=com.sap.ip.me.sync.SyncManagerMerger@e1eea8] skipped for User because he has not been installed on MW.</b> 
    [20070820 13:32:49:216] D [MI/API/Sync ] SyncEvent com.sap.ip.me.api.sync.SyncEvent[source=com.sap.ip.me.sync.SyncManagerMerger@e1eea8] skipped for User because he has not been installed on MW. 
    [20070820 13:32:49:216] D [MI/API/Sync ] SyncEvent com.sap.ip.me.api.sync.SyncEvent[source=com.sap.ip.me.sync.SyncManagerMerger@e1eea8] skipped for User because he has not been installed on MW. 
    [20070820 13:32:49:216] D [MI/API/Sync ] SyncEvent com.sap.ip.me.api.sync.SyncEvent[source=com.sap.ip.me.sync.SyncManagerMerger@e1eea8] skipped for User because he has not been installed on MW. 
    [20070820 13:32:49:216] D [MI/API/Sync ] SyncEvent com.sap.ip.me.api.sync.SyncEvent[source=com.sap.ip.me.sync.SyncManagerMerger@e1eea8] skipped for User because he has not been installed on MW.
    [20070820 13:32:49:216] P [MI/Sync ] Start updating data completeness flag for user all sync relevant users 
    [20070820 13:32:49:216] P [MI/Sync ] Update data completeness flag for user DEVELOPER 
    [20070820 13:32:49:216] P [MI/Sync ] Update data completeness flag for user (SHARED) 
    [20070820 13:32:49:216] P [MI/Sync ] Finished updating data completeness flag for user all sync relevant users 
    [20070820 13:32:49:216] P [MI/Sync ] Repetitive sync is turned off 
    [20070820 13:32:49:216] P [MI/Sync ] Synchronization started for user (SHARED) 
    [20070820 13:32:49:216] D [MI/Sync ] PackageManager: create package with maximum 2147483647 items 
    [20070820 13:32:49:216] D [MI/Sync ] PackageManager: filled package with 1 acknowledge received container(s) 
    [20070820 13:32:49:216] D [MI/Sync ] PackageManager: filled package with 0 acknowledge container(s) 
    [20070820 13:32:49:232] D [MI/Sync ] Opened container file F:\Program Files\SAP Mobile Infrastructure\sync\(SHARED)\out\i0000004.sync for read (container id = 011483784af128f8dfe0) 
    [20070820 13:32:49:232] D [MI/Sync ] Closed container file (container id = 011483784af128f8dfe0) 
    [20070820 13:32:49:232] D [MI/Sync ] PackageManager: filled package with 4 container items or headers 
    [20070820 13:32:49:232] D [MI/Sync ] PackageManager: filled package with 1 notify container(s) 
    [20070820 13:32:49:232] D [MI/Sync ] Package file F:\Program Files\SAP Mobile Infrastructure\sync\(SHARED)\out\package.out exists and can be read 
    [20070820 13:32:49:232] P [MI/Sync ] Synchronisation started 
    [20070820 13:32:49:232] D [MI/Sync ] Begin: Dumping file F:\Program Files\SAP Mobile Infrastructure\sync\(SHARED)\out\package.out 
    <ID>MISYNC</ID><FLAGS>0x1</FLAGS><VERSION>251300</VERSION> 
    <CONTAINER> 
    <HEADER> 
    <CONTAINER_ID>0114837846daf9923158</CONTAINER_ID> 
    <OWNER></OWNER> 
    <CONTAINER_TYPE>C</CONTAINER_TYPE> 
    <METHOD>AGENT_PARAMETERS</METHOD> 
    <CONVERSATION_ID></CONVERSATION_ID> 
    <PARENT_CONTAINER_ID>30A887F746CFE547B6B459C7899D56B8</PARENT_CONTAINER_ID> 
    <MESSAGE_INDEX>-1</MESSAGE_INDEX> 
    <MESSAGE_TYPE> </MESSAGE_TYPE> 
    <SERVER_ID>NEW_PROTOCOL</SERVER_ID> 
    <BODY_TYPE></BODY_TYPE> 
    <BODY_LENGTH>0</BODY_LENGTH> 
    <SUB_CONTAINER_ID>-1</SUB_CONTAINER_ID> 
    <SUB_CONT_MAX>3</SUB_CONT_MAX> 
    <ITEM_FROM>-1</ITEM_FROM> 
    <ITEM_TO>-1</ITEM_TO> 
    </HEADER> 
    </CONTAINER> 
    <CONTAINER> 
    <HEADER> 
    <CONTAINER_ID>011483784af128f8dfe0</CONTAINER_ID> 
    <OWNER></OWNER> 
    <CONTAINER_TYPE>R</CONTAINER_TYPE> 
    <METHOD>AGENT_PARAMETERS</METHOD> 
    <CONVERSATION_ID></CONVERSATION_ID> 
    <PARENT_CONTAINER_ID></PARENT_CONTAINER_ID> 
    <MESSAGE_INDEX>-1</MESSAGE_INDEX> 
    <MESSAGE_TYPE> </MESSAGE_TYPE> 
    <SERVER_ID>NEW_PROTOCOL</SERVER_ID> 
    <BODY_TYPE></BODY_TYPE> 
    <BODY_LENGTH>0</BODY_LENGTH> 
    <SUB_CONTAINER_ID>-1</SUB_CONTAINER_ID> 
    <SUB_CONT_MAX>3</SUB_CONT_MAX> 
    <ITEM_FROM>-1</ITEM_FROM> 
    <ITEM_TO>-1</ITEM_TO> 
    </HEADER> 
    <ITEM> 
    <FIELD_NAME>TIMESTAMP</FIELD_NAME> 
    <LINE_NUMBER>0</LINE_NUMBER> 
    <FIELD_VALUE>000000;19700101 </FIELD_VALUE> 
    </ITEM> 
    <ITEM> 
    <FIELD_NAME>DEVICEID</FIELD_NAME> 
    <LINE_NUMBER>0</LINE_NUMBER> 
    <FIELD_VALUE></FIELD_VALUE> 
    </ITEM> 
    <ITEM> 
    <FIELD_NAME>USER</FIELD_NAME> 
    <LINE_NUMBER>0</LINE_NUMBER> 
    <FIELD_VALUE>DEVELOPER</FIELD_VALUE> 
    </ITEM> 
    </CONTAINER> 
    <CONTAINER> 
    <HEADER> 
    <CONTAINER_ID>01148379c4d0e950ab25</CONTAINER_ID> 
    <OWNER></OWNER> 
    <CONTAINER_TYPE>N</CONTAINER_TYPE> 
    <METHOD></METHOD> 
    <CONVERSATION_ID></CONVERSATION_ID> 
    <PARENT_CONTAINER_ID></PARENT_CONTAINER_ID> 
    <MESSAGE_INDEX>-1</MESSAGE_INDEX> 
    <MESSAGE_TYPE> </MESSAGE_TYPE> 
    <SERVER_ID>NEW_PROTOCOL</SERVER_ID> 
    <BODY_TYPE></BODY_TYPE> 
    <BODY_LENGTH>0</BODY_LENGTH> 
    <SUB_CONTAINER_ID>-1</SUB_CONTAINER_ID> 
    <SUB_CONT_MAX>0</SUB_CONT_MAX> 
    <ITEM_FROM>-1</ITEM_FROM> 
    <ITEM_TO>-1</ITEM_TO> 
    </HEADER> 
    </CONTAINER> 
    [20070820 13:32:49:232] D [MI/Sync ] End: Dumping file F:\Program Files\SAP Mobile Infrastructure\sync\(SHARED)\out\package.out 
    [20070820 13:32:49:232] I [MI/Sync ] Outbound file size for user (SHARED) is 391 
    [20070820 13:32:49:232] P [MI/Sync ] Do not use http proxy (system properties update) 
    [20070820 13:32:49:232] P [MI/Sync ] Use following gateway for synchronization: http://psc-pc11741:50000 
    [20070820 13:32:49:232] I [MI/Sync ] GzipDataCompression: Gzip data compression is switched on 
    [20070820 13:32:49:232] P [MI/Sync ] Sending outbound file compressed to server. 
    [20070820 13:32:49:232] P [MI/Sync ] Outbound file was compressedly sent. 
    [20070820 13:32:49:310] P [MI/Sync ] Receiving inbound file compressed from server. 
    [20070820 13:32:49:310] P [MI/Sync ] Inbound file was compressedly received. 
    [20070820 13:32:49:310] I [MI/Sync ] Inbound file size for user (SHARED) is 487 
    [20070820 13:32:49:310] P [MI/Sync ] Synchronisation successfully connected 
    [20070820 13:32:49:325] D [MI/Sync ] Begin: Dumping file F:\Program Files\SAP Mobile Infrastructure\sync\(SHARED)\in\inbound.sync 
    <ID>MISYNC</ID><FLAGS>0x0</FLAGS><VERSION>251300</VERSION> 
    <PROLOG> 
    <JCO_INFO>JCO-library-version: 1.1.20; Creation time: 2007-08-20 19:02:49</JCO_INFO> 
    <SYNC_STATUS> </SYNC_STATUS> 
    <EXECUTION_TIME>190249</EXECUTION_TIME> 
    <MORE_PACKAGES_WAITING> </MORE_PACKAGES_WAITING> 
    <SYNC_COUNTER>0</SYNC_COUNTER> 
    </PROLOG> 
    <CONTAINER> 
    <HEADER> 
    <CONTAINER_ID>0568D6F4B5FE684D9B26AE5B29CAA508</CONTAINER_ID> 
    <OWNER></OWNER> 
    <CONTAINER_TYPE>R</CONTAINER_TYPE> 
    <METHOD>AGENT_PARAMETERS</METHOD> 
    <CONVERSATION_ID></CONVERSATION_ID> 
    <PARENT_CONTAINER_ID>011483784af128f8dfe0</PARENT_CONTAINER_ID> 
    <MESSAGE_INDEX>1</MESSAGE_INDEX> 
    <MESSAGE_TYPE> </MESSAGE_TYPE> 
    <SERVER_ID>NEW_PROTOCOL</SERVER_ID> 
    <BODY_TYPE></BODY_TYPE> 
    <BODY_LENGTH>0</BODY_LENGTH> 
    <SUB_CONTAINER_ID>-1</SUB_CONTAINER_ID> 
    <SUB_CONT_MAX>1</SUB_CONT_MAX> 
    <ITEM_FROM>0</ITEM_FROM> 
    <ITEM_TO>0</ITEM_TO> 
    <SEND_DATE>2007-08-20</SEND_DATE> 
    <SEND_TIME>19:02:49</SEND_TIME> 
    <EXECUTION_DATE>2007-08-20</EXECUTION_DATE> 
    <EXECUTION_TIME>19:02:49</EXECUTION_TIME> 
    <CONTAINER_STATUS>S</CONTAINER_STATUS> 
    </HEADER> 
    <ITEM> 
    <FIELD_NAME>TIMESTAMP</FIELD_NAME> 
    <LINE_NUMBER>0000000000</LINE_NUMBER> 
    <FIELD_VALUE>000000;19700101 </FIELD_VALUE> 
    </ITEM> 
    </CONTAINER> 
    <CONTAINER> 
    <HEADER> 
    <CONTAINER_ID>1B9A98991CBE674288F0E4C70A1BB258</CONTAINER_ID> 
    <OWNER></OWNER> 
    <CONTAINER_TYPE>A</CONTAINER_TYPE> 
    <METHOD>AGENT_PARAMETERS</METHOD> 
    <CONVERSATION_ID></CONVERSATION_ID> 
    <PARENT_CONTAINER_ID>011483784af128f8dfe0</PARENT_CONTAINER_ID> 
    <MESSAGE_INDEX>0</MESSAGE_INDEX> 
    <MESSAGE_TYPE> </MESSAGE_TYPE> 
    <SERVER_ID>NEW_PROTOCOL</SERVER_ID> 
    <BODY_TYPE></BODY_TYPE> 
    <BODY_LENGTH>0</BODY_LENGTH> 
    <SUB_CONTAINER_ID>-1</SUB_CONTAINER_ID> 
    <SUB_CONT_MAX>3</SUB_CONT_MAX> 
    <ITEM_FROM>0</ITEM_FROM> 
    <ITEM_TO>0</ITEM_TO> 
    <SEND_DATE>0000-00-00</SEND_DATE> 
    <SEND_TIME>00:00:00</SEND_TIME> 
    <EXECUTION_DATE>2007-08-20</EXECUTION_DATE> 
    <EXECUTION_TIME>19:02:49</EXECUTION_TIME> 
    <CONTAINER_STATUS>O</CONTAINER_STATUS> 
    </HEADER> 
    </CONTAINER> 
    [20070820 13:32:49:325] D [MI/Sync ] End: Dumping file F:\Program Files\SAP Mobile Infrastructure\sync\(SHARED)\in\inbound.sync 
    [20070820 13:32:49:325] D [MI/Sync ] Initial buffer size of BinaryReader is 487 
    [20070820 13:32:49:325] P [MI/Sync ] Read current inbound counter from file: 0 
    [20070820 13:32:49:325] P [MI/Sync ] Received sync counter 0 is valid 
    [20070820 13:32:49:325] P [MI/Sync ] Inbound file ready to be parsed 
    [20070820 13:32:49:325] P [MI/Sync ] Number of pending inbound containers before inbound processing = 0 
    [20070820 13:32:49:325] P [MI/Sync ] Synchronisation: Start processing inbound data 
    [20070820 13:32:49:325] I [MI/Sync ] -
    InboundContainer created: Type:R,Id:0568D6F4B5FE684D9B26AE5B29CAA508,SId:-1,Items:0,MaxI:1 
    [20070820 13:32:49:325] P [MI/Sync ] SyncInboundProcessing started for method AGENT_PARAMETERS 
    [20070820 13:32:49:325] W [MI/Sync ] Container Type:R,Id:0568D6F4B5FE684D9B26AE5B29CAA508,SId:-1,Items:0,MaxI:1 does not contain a conversation id, use defaull: MI444556454c4f504552 / MI444556454c4f504552 (User: DEVELOPER, MSD: Name: / MOBILEENGINE_JSP (V. 252000), Target=, Type=com.sap.ip.me.core.FrameworkApplicationType) 
    [20070820 13:32:49:325] P [MI/Core ] Thread Thread-40 switched context to MI444556454c4f504552 / MI444556454c4f504552 (User: DEVELOPER, MSD: Name: / MOBILEENGINE_JSP (V. 252000), Target=, Type=com.sap.ip.me.core.FrameworkApplicationType) (stack level 1) 
    [20070820 13:32:49:325] P [MI/Sync ] Process container: Type:R,Id:0568D6F4B5FE684D9B26AE5B29CAA508,SId:-1,Items:0,MaxI:1 
    [20070820 13:32:49:325] I [MI/Sync ] -
    InboundContainer created: Type:R,Id:0568D6F4B5FE684D9B26AE5B29CAA508,SId:-1,Items:0,MaxI:1 
    [20070820 13:32:49:325] P [MI/Sync ] Container processed without exceptions 
    [20070820 13:32:49:325] P [MI/Core ] original context restored 
    [20070820 13:32:49:325] P [MI/Sync ] SyncInboundProcessing finished successfully for method AGENT_PARAMETERS 
    [20070820 13:32:49:325] D [MI/Sync ] Write container header to file (container id = 01148379c52d5ed4565e): F:\Program Files\SAP Mobile Infrastructure\sync\DEVELOPER\out\a000000i.sync 
    [20070820 13:32:49:341] P [MI/Sync ] Created outbound container for user DEVELOPER and method AGENT_PARAMETERS 
    [20070820 13:32:49:341] P [MI/Sync ] Process acknowledge container: 1B9A98991CBE674288F0E4C70A1BB258 
    [20070820 13:32:49:341] D [MI/Sync ] Write container header to file (container id = 01148379c53d9f62a07d): F:\Program Files\SAP Mobile Infrastructure\sync\(SHARED)\out\c0000004.sync 
    [20070820 13:32:49:341] P [MI/Sync ] Created outbound container for user (SHARED) and method AGENT_PARAMETERS 
    [20070820 13:32:49:341] D [MI/Sync ] Processed 1 not arranged, 0 arranged, 1 acknowledge containers and 0 sub containers 
    [20070820 13:32:49:341] P [MI/Core ] original context restored 
    [20070820 13:32:49:341] P [MI/Sync ] Number of pending inbound containers after inbound processing = 0 
    [20070820 13:32:49:341] P [MI/Sync ] Synchronisation: Processing of inbound data finished 
    [20070820 13:32:49:341] D [MI/Sync ] There are no more packages waiting 
    [20070820 13:32:49:341] D [MI/Sync ] resetting the info which outbound containers are already created for user (SHARED) 
    [20070820 13:32:49:341] P [MI/Core ] original context restored 
    [20070820 13:32:49:341] P [MI/Sync ] Synchronization finished for user (SHARED) 
    [20070820 13:32:49:341] P [MI/Sync ] Synchronization started for user DEVELOPER 
    [20070820 13:32:49:357] D [MI/Sync ] PackageManager: old package file F:\Program Files\SAP Mobile Infrastructure\sync\DEVELOPER\out\package.out was successfully deleted 
    [20070820 13:32:49:357] D [MI/Sync ] PackageManager: create package with maximum 2147483647 items 
    [20070820 13:32:49:357] D [MI/Sync ] PackageManager: filled package with 1 acknowledge received container(s) 
    [20070820 13:32:49:357] D [MI/Sync ] PackageManager: filled package with 2 acknowledge container(s) 
    [20070820 13:32:49:357] D [MI/Sync ] Opened container file F:\Program Files\SAP Mobile Infrastructure\sync\DEVELOPER\out\i0000007.sync for read (container id = 01148379c2ad4686a00f) 
    [20070820 13:32:49:372] D [MI/Sync ] Closed container file (container id = 01148379c2ad4686a00f) 
    [20070820 13:32:49:372] D [MI/Sync ] PackageManager: filled package with 25 container items or headers 
    [20070820 13:32:49:372] D [MI/Sync ] PackageManager: filled package with 1 notify container(s) 
    [20070820 13:32:49:372] D [MI/Sync ] Package file F:\Program Files\SAP Mobile Infrastructure\sync\DEVELOPER\out\package.out exists and can be read 
    [20070820 13:32:49:372] P [MI/Sync ] Synchronisation started 
    [20070820 13:32:49:372] D [MI/Sync ] Begin: Dumping file F:\Program Files\SAP Mobile Infrastructure\sync\DEVELOPER\out\package.out 
    <ID>MISYNC</ID><FLAGS>0x1</FLAGS><VERSION>251300</VERSION> 
    <CONTAINER> 
    <HEADER> 
    <CONTAINER_ID>011483784ae36797f82f</CONTAINER_ID> 
    <OWNER>DEVELOPER</OWNER> 
    <CONTAINER_TYPE>C</CONTAINER_TYPE> 
    <METHOD>WAF_REGISTRY</METHOD> 
    <CONVERSATION_ID></CONVERSATION_ID> 
    <PARENT_CONTAINER_ID>9293A1F34A974341B5B6AD04CEE5478F</PARENT_CONTAINER_ID> 
    <MESSAGE_INDEX>-1</MESSAGE_INDEX> 
    <MESSAGE_TYPE> </MESSAGE_TYPE> 
    <SERVER_ID>NEW_PROTOCOL</SERVER_ID> 
    <BODY_TYPE></BODY_TYPE> 
    <BODY_LENGTH>0</BODY_LENGTH> 
    <SUB_CONTAINER_ID>-1</SUB_CONTAINER_ID> 
    <SUB_CONT_MAX>24</SUB_CONT_MAX> 
    <ITEM_FROM>-1</ITEM_FROM> 
    <ITEM_TO>-1</ITEM_TO> 
    </HEADER> 
    </CONTAINER> 
    <CONTAINER> 
    <HEADER> 
    <CONTAINER_ID>011483784ae2a318c6cc</CONTAINER_ID> 
    <OWNER>DEVELOPER</OWNER> 
    <CONTAINER_TYPE>A</CONTAINER_TYPE> 
    <METHOD>WAF_REGISTRY</METHOD> 
    <CONVERSATION_ID></CONVERSATION_ID> 
    <PARENT_CONTAINER_ID>011483784479cd0fa99b</PARENT_CONTAINER_ID> 
    <MESSAGE_INDEX>-1</MESSAGE_INDEX> 
    <MESSAGE_TYPE> </MESSAGE_TYPE> 
    <SERVER_ID>NEW_PROTOCOL</SERVER_ID> 
    <BODY_TYPE></BODY_TYPE> 
    <BODY_LENGTH>0</BODY_LENGTH> 
    <SUB_CONTAINER_ID>-1</SUB_CONTAINER_ID> 
    <SUB_CONT_MAX>26</SUB_CONT_MAX> 
    <ITEM_FROM>-1</ITEM_FROM> 
    <ITEM_TO>-1</ITEM_TO> 
    </HEADER> 
    </CONTAINER> 
    <CONTAINER> 
    <HEADER> 
    <CONTAINER_ID>01148379c52d5ed4565e</CONTAINER_ID> 
    <OWNER></OWNER> 
    <CONTAINER_TYPE>A</CONTAINER_TYPE> 
    <METHOD>AGENT_PARAMETERS</METHOD> 
    <CONVERSATION_ID></CONVERSATION_ID> 
    <PARENT_CONTAINER_ID>0568D6F4B5FE684D9B26AE5B29CAA508</PARENT_CONTAINER_ID> 
    <MESSAGE_INDEX>1</MESSAGE_INDEX> 
    <MESSAGE_TYPE> </MESSAGE_TYPE> 
    <SERVER_ID>NEW_PROTOCOL</SERVER_ID> 
    <BODY_TYPE></BODY_TYPE> 
    <BODY_LENGTH>0</BODY_LENGTH> 
    <SUB_CONTAINER_ID>-1</SUB_CONTAINER_ID> 
    <SUB_CONT_MAX>1</SUB_CONT_MAX> 
    <ITEM_FROM>-1</ITEM_FROM> 
    <ITEM_TO>-1</ITEM_TO> 
    </HEADER> 
    </CONTAINER> 
    <CONTAINER> 
    <HEADER> 
    <CONTAINER_ID>01148379c2ad4686a00f</CONTAINER_ID> 
    <OWNER>DEVELOPER</OWNER> 
    <CONTAINER_TYPE>R</CONTAINER_TYPE> 
    <METHOD>WAF_REGISTRY</METHOD> 
    <CONVERSATION_ID></CONVERSATION_ID> 
    <PARENT_CONTAINER_ID></PARENT_CONTAINER_ID> 
    <MESSAGE_INDEX>-1</MESSAGE_INDEX> 
    <MESSAGE_TYPE> </MESSAGE_TYPE> 
    <SERVER_ID>NEW_PROTOCOL</SERVER_ID> 
    <BODY_TYPE></BODY_TYPE> 
    <BODY_LENGTH>0</BODY_LENGTH> 
    <SUB_CONTAINER_ID>-1</SUB_CONTAINER_ID> 
    <SUB_CONT_MAX>24</SUB_CONT_MAX> 
    <ITEM_FROM>-1</ITEM_FROM> 
    <ITEM_TO>-1</ITEM_TO> 
    </HEADER> 
    <ITEM> 
    <FIELD_NAME>CONVIDGENERATION</FIELD_NAME> 
    <LINE_NUMBER>0</LINE_NUMBER> 
    <FIELD_VALUE>X</FIELD_VALUE> 
    </ITEM> 
    <ITEM> 
    <FIELD_NAME>DEPLID</FIELD_NAME> 
    <LINE_NUMBER>0</LINE_NUMBER> 
    <FIELD_VALUE></FIELD_VALUE> 
    </ITEM> 
    <ITEM> 
    <FIELD_NAME>DEVICE</FIELD_NAME> 
    <LINE_NUMBER>0</LINE_NUMBER> 
    <FIELD_VALUE>000 DEVELOPER MOBILEENGINE_JSP I252000 </FIELD_VALUE> 
    </ITEM> 
    <ITEM> 
    <FIELD_NAME>DEPLID</FIELD_NAME> 
    <LINE_NUMBER>1</LINE_NUMBER> 
    <FIELD_VALUE></FIELD_VALUE> 
    </ITEM> 
    <ITEM> 
    <FIELD_NAME>DEVICE_OTHERS</FIELD_NAME> 
    <LINE_NUMBER>0</LINE_NUMBER> 
    <FIELD_VALUE>000 MI_SERVICE MOBILEENGINE_JSP I252000 </FIELD_VALUE> 
    </ITEM> 
    <ITEM> 
    <FIELD_NAME>DEVICEPROFILE</FIELD_NAME> 
    <LINE_NUMBER>0</LINE_NUMBER> 
    <FIELD_VALUE>OSNAME:Windows XP</FIELD_VALUE> 
    </ITEM> 
    <ITEM> 
    <FIELD_NAME>DEVICEPROFILE</FIELD_NAME> 
    <LINE_NUMBER>1</LINE_NUMBER> 
    <FIELD_VALUE>OSVERSION:5.1</FIELD_VALUE> 
    </ITEM> 
    <ITEM> 
    <FIELD_NAME>DEVICEPROFILE</FIELD_NAME> 
    <LINE_NUMBER>2</LINE_NUMBER> 
    <FIELD_VALUE>JVM_VENDOR:Sun Microsystems Inc.</FIELD_VALUE> 
    </ITEM> 
    <ITEM> 
    <FIELD_NAME>DEVICEPROFILE</FIELD_NAME> 
    <LINE_NUMBER>3</LINE_NUMBER> 
    <FIELD_VALUE>JAVA_VERSION:1.4.2_11</FIELD_VALUE> 
    </ITEM> 
    <ITEM> 
    <FIELD_NAME>DEVICEPROFILE</FIELD_NAME> 
    <LINE_NUMBER>4</LINE_NUMBER> 
    <FIELD_VALUE>USER_TIMEZONE:Asia/Calcutta</FIELD_VALUE> 
    </ITEM> 
    <ITEM> 
    <FIELD_NAME>DEVICEPROFILE</FIELD_NAME> 
    <LINE_NUMBER>5</LINE_NUMBER> 
    <FIELD_VALUE>PROCESSOR:pentium i486 i386</FIELD_VALUE> 
    </ITEM> 
    <ITEM> 
    <FIELD_NAME>DEVICEPROFILE</FIELD_NAME> 
    <LINE_NUMBER>6</LINE_NUMBER> 
    <FIELD_VALUE>OSARCHITECTURE:x86</FIELD_VALUE> 
    </ITEM> 
    <ITEM> 
    <FIELD_NAME>DEVICEPROFILE</FIELD_NAME> 
    <LINE_NUMBER>7</LINE_NUMBER> 
    <FIELD_VALUE>RUNTIME:TOMCAT</FIELD_VALUE> 
    </ITEM> 
    <ITEM> 
    <FIELD_NAME>DEVICEPROFILE</FIELD_NAME> 
    <LINE_NUMBER>8</LINE_NUMBER> 
    <FIELD_VALUE>MI_FULLNAME:MI 25 SP 20 Patch 00 Build 200703222033</FIELD_VALUE> 
    </ITEM> 
    <ITEM> 
    <FIELD_NAME>DEVICEPROFILE</FIELD_NAME> 
    <LINE_NUMBER>9</LINE_NUMBER> 
    <FIELD_VALUE>USERS_ON_DEVICE:DEVELOPER; MI_SERVICE</FIELD_VALUE> 
    </ITEM> 
    <ITEM> 
    <FIELD_NAME>DEVICEPROFILE</FIELD_NAME> 
    <LINE_NUMBER>10</LINE_NUMBER> 
    <FIELD_VALUE>INSTALLATION_IMAGE:NO</FIELD_VALUE> 
    </ITEM> 
    <ITEM> 
    <FIELD_NAME>DEVICEPROFILE</FIELD_NAME> 
    <LINE_NUMBER>11</LINE_NUMBER> 
    <FIELD_VALUE>DATA_FOLDER_SIZE:1 KB</FIELD_VALUE> 
    </ITEM> 
    <ITEM> 
    <FIELD_NAME>DEVICEPROFILE</FIELD_NAME> 
    <LINE_NUMBER>12</LINE_NUMBER> 
    <FIELD_VALUE>LAST_IP_ADDRESS:172.17.4.142</FIELD_VALUE> 
    </ITEM> 
    <ITEM> 
    <FIELD_NAME>DEVICEPROFILE</FIELD_NAME> 
    <LINE_NUMBER>13</LINE_NUMBER> 
    <FIELD_VALUE>HOSTNAME:psc-pc11741</FIELD_VALUE> 
    </ITEM> 
    <ITEM> 
    <FIELD_NAME>DEVICEPROFILE</FIELD_NAME> 
    <LINE_NUMBER>14</LINE_NUMBER> 
    <FIELD_VALUE>TOTAL_MEMORY:2038 MB</FIELD_VALUE> 
    </ITEM> 
    <ITEM> 
    <FIELD_NAME>DEVICEPROFILE</FIELD_NAME> 
    <LINE_NUMBER>15</LINE_NUMBER> 
    <FIELD_VALUE>VIRTUAL_MACHINE_VERSION:1.4.2_11-b06</FIELD_VALUE> 
    </ITEM> 
    <ITEM> 
    <FIELD_NAME>NATIVE_OS</FIELD_NAME> 
    <LINE_NUMBER>0</LINE_NUMBER> 
    <FIELD_VALUE>1</FIELD_VALUE> 
    </ITEM> 
    <ITEM> 
    <FIELD_NAME>NATIVE_JVM</FIELD_NAME> 
    <LINE_NUMBER>0</LINE_NUMBER> 
    <FIELD_VALUE>1</FIELD_VALUE> 
    </ITEM> 
    <ITEM> 
    <FIELD_NAME>NATIVE_CPU</FIELD_NAME> 
    <LINE_NUMBER>0</LINE_NUMBER> 
    <FIELD_VALUE>1</FIELD_VALUE> 
    </ITEM> 
    </CONTAINER> 
    <CONTAINER> 
    <HEADER> 
    <CONTAINER_ID>01148379c55c1403e712</CONTAINER_ID> 
    <OWNER>DEVELOPER</OWNER> 
    <CONTAINER_TYPE>N</CONTAINER_TYPE> 
    <METHOD></METHOD> 
    <CONVERSATION_ID></CONVERSATION_ID> 
    <PARENT_CONTAINER_ID></PARENT_CONTAINER_ID> 
    <MESSAGE_INDEX>-1</MESSAGE_INDEX> 
    <MESSAGE_TYPE> </MESSAGE_TYPE> 
    <SERVER_ID>NEW_PROTOCOL</SERVER_ID> 
    <BODY_TYPE></BODY_TYPE> 
    <BODY_LENGTH>0</BODY_LENGTH> 
    <SUB_CONTAINER_ID>-1</SUB_CONTAINER_ID> 
    <SUB_CONT_MAX>0</SUB_CONT_MAX> 
    <ITEM_FROM>-1</ITEM_FROM> 
    <ITEM_TO>-1</ITEM_TO> 
    </HEADER> 
    </CONTAINER> 
    [20070820 13:32:49:372] D [MI/Sync ] End: Dumping file F:\Program Files\SAP Mobile Infrastructure\sync\DEVELOPER\out\package.out 
    [20070820 13:32:49:372] I [MI/Sync ] Outbound file size for user DEVELOPER is 1727 
    [20070820 13:32:49:372] P [MI/Sync ] Do not use http proxy (system properties update) 
    [20070820 13:32:49:372] P [MI/Sync ] Use following gateway for synchronization: http://psc-pc11741:50000 
    [20070820 13:32:49:372] I [MI/Sync ] GzipDataCompression: Gzip data compression is switched on 
    [20070820 13:32:49:388] P [MI/Sync ] Sending outbound file compressed to server. 
    [20070820 13:32:49:388] P [MI/Sync ] Outbound file was compressedly sent. 
    [20070820 13:32:49:669] P [MI/Sync ] Receiving inbound file compressed from server. 
    [20070820 13:32:49:669] P [MI/Sync ] Inbound file was compressedly received. 
    [20070820 13:32:49:669] I [MI/Sync ] Inbound file size for user DEVELOPER is 2332 
    [20070820 13:32:49:669] P [MI/Sync ] Synchronisation successfully connected 
    [20070820 13:32:49:669] D [MI/Sync ] Begin: Dumping file F:\Program Files\SAP Mobile Infrastructure\sync\DEVELOPER\in\inbound.sync 
    <ID>MISYNC</ID><FLAGS>0x0</FLAGS><VERSION>251300</VERSION> 
    <PROLOG> 
    <JCO_INFO>JCO-library-version: 1.1.20; Creation time: 2007-08-20 19:02:49</JCO_INFO> 
    <SYNC_STATUS> </SYNC_STATUS> 
    <EXECUTION_TIME>190249</EXECUTION_TIME> 
    <MORE_PACKAGES_WAITING> </MORE_PACKAGES_WAITING> 
    <SYNC_COUNTER>0</SYNC_COUNTER> 
    </PROLOG> 
    <CONTAINER> 
    <HEADER> 
    <CONTAINER_ID>01148379c2ad4686a00f</CONTAINER_ID> 
    <OWNER>DEVELOPER</OWNER> 
    <CONTAINER_TYPE>R</CONTAINER_TYPE> 
    <METHOD>WAF_REGISTRY</METHOD> 
    <CONVERSATION_ID></CONVERSATION_ID> 
    <PARENT_CONTAINER_ID>01148379c2ad4686a00f</PARENT_CONTAINER_ID> 
    <MESSAGE_INDEX>0</MESSAGE_INDEX> 
    <MESSAGE_TYPE> </MESSAGE_TYPE> 
    <SERVER_ID>NEW_PROTOCOL</SERVER_ID> 
    <BODY_TYPE></BODY_TYPE> 
    <BODY_LENGTH>0</BODY_LENGTH> 
    <SUB_CONTAINER_ID>-1</SUB_CONTAINER_ID> 
    <SUB_CONT_MAX>26</SUB_CONT_MAX> 
    <ITEM_FROM>0</ITEM_FROM> 
    <ITEM_TO>0</ITEM_TO> 
    <SEND_DATE>2007-08-20</SEND_DATE> 
    <SEND_TIME>19:02:49</SEND_TIME> 
    <EXECUTION_DATE>2007-08-20</EXECUTION_DATE> 
    <EXECUTION_TIME>19:02:49</EXECUTION_TIME> 
    <CONTAINER_STATUS>E</CONTAINER_STATUS> 
    </HEADER> 
    <ITEM> 
    <FIELD_NAME>CONVIDGENERATION</FIELD_NAME> 
    <LINE_NUMBER>0000000000</LINE_NUMBER> 
    <FIELD_VALUE>X </FIELD_VALUE> 
    </ITEM> 
    <ITEM> 
    <FIELD_NAME>DEPLID</FIELD_NAME> 
    <LINE_NUMBER>0000000000</LINE_NUMBER> 
    <FIELD_VALUE> </FIELD_VALUE> 
    </ITEM> 
    <ITEM> 
    <FIELD_NAME>DEPLID</FIELD_NAME> 
    <LINE_NUMBER>0000000001</LINE_NUMBER> 
    <FIELD_VALUE> </FIELD_VALUE> 
    </ITEM> 
    <ITEM> 
    <FIELD_NAME>DEVICE</FIELD_NAME> 
    <LINE_NUMBER>0000000000</LINE_NUMBER> 
    <FIELD_VALUE>000 DEVELOPER MOBILEENGINE_JSP I252000 </FIELD_VALUE> 
    </ITEM> 
    <ITEM> 
    <FIELD_NAME>DEVICEPROFILE</FIELD_NAME> 
    <LINE_NUMBER>0000000000</LINE_NUMBER> 
    <FIELD_VALUE>OSNAME:Windows XP </FIELD_VALUE> 
    </ITEM> 
    <ITEM> 
    <FIELD_NAME>DEVICEPROFILE</FIELD_NAME> 
    <LINE_NUMBER>0000000001</LINE_NUMBER> 
    <FIELD_VALUE>OSVERSION:5.1 </FIELD_VALUE> 
    </ITEM> 
    <ITEM> 
    <FIELD_NAME>DEVICEPROFILE</FIELD_NAME> 
    <LINE_NUMBER>0000000002</LINE_NUMBER> 
    <FIELD_VALUE>JVM_VENDOR:Sun Microsystems Inc. </FIELD_VALUE> 
    </ITEM> 
    <ITEM> 
    <FIELD_NAME>DEVICEPROFILE</FIELD_NAME> 
    <LINE_NUMBER>0000000003</LINE_NUMBER> 
    <FIELD_VALUE>JAVA_VERSION:1.4.2_11 </FIELD_VALUE> 
    </ITEM> 
    <ITEM> 
    <FIELD_NAME>DEVICEPROFILE</FIELD_NAME> 
    <LINE_NUMBER>0000000004</LINE_NUMBER> 
    <FIELD_VALUE>USER_TIMEZONE:Asia/Calcutta </FIELD_VALUE> 
    </ITEM> 
    <ITEM> 
    <FIELD_NAME>DEVICEPROFILE</FIELD_NAME> 
    <LINE_NUMBER>0000000005</LINE_NUMBER> 
    <FIELD_VALUE>PROCESSOR:pentium i486 i386 </FIELD_VALUE> 
    </ITEM> 
    <ITEM> 
    <FIELD_NAME>DEVICEPROFILE</FIELD_NAME> 
    <LINE_NUMBER>0000000006</LINE_NUMBER> 
    <FIELD_VALUE>OSARCHITECTURE:x86 </FIELD_VALUE> 
    </ITEM> 
    <ITEM> 
    <FIELD_NAME>DEVICEPROFILE</FIELD_NAME> 
    <LINE_NUMBER>0000000007</LINE_NUMBER> 
    <FIELD_VALUE>RUNTIME:TOMCAT </FIELD_VALUE> 
    </ITEM> 
    <ITEM> 
    <FIELD_NAME>DEVICEPROFILE</FIELD_NAME> 
    <LINE_NUMBER>0000000008</LINE_NUMBER> 
    <FIELD_VALUE>MI_FULLNAME:MI 25 SP 20 Patch 00 Build 200703222033 </FIELD_VALUE> 
    </ITEM> 
    <ITEM> 
    <FIELD_NAME>DEVICEPROFILE</FIELD_NAME> 
    <LINE_NUMBER>0000000009</LINE_NUMBER> 
    <FIELD_VALUE>USERS_ON_DEVICE:DEVELOPER; MI_SERVICE </FIELD_VALUE> 
    </ITEM> 
    <ITEM> 
    <FIELD_NAME>DEVICEPROFILE</FIELD_NAME> 
    <LINE_NUMBER>0000000010</LINE_NUMBER> 
    <FIELD_VALUE>INSTALLATION_IMAGE:NO </FIELD_VALUE> 
    </ITEM> 
    <ITEM> 
    <FIELD_NAME>DEVICEPROFILE</FIELD_NAME> 
    <LINE_NUMBER>0000000011</LINE_NUMBER> 
    <FIELD_VALUE>DATA_FOLDER_SIZE:1 KB </FIELD_VALUE> 
    </ITEM> 
    <ITEM> 
    <FIELD_NAME>DEVICEPROFILE</FIELD_NAME> 
    <LINE_NUMBER>0000000012</LINE_NUMBER> 
    <FIELD_VALUE>LAST_IP_ADDRESS:172.17.4.142 </FIELD_VALUE> 
    </ITEM> 
    <ITEM> 
    <FIELD_NAME>DEVICEPROFILE</FIELD_NAME> 
    <LINE_NUMBER>0000000013</LINE_NUMBER> 
    <FIELD_VALUE>HOSTNAME:psc-pc11741 </FIELD_VALUE> 
    </ITEM> 
    <ITEM> 
    <FIELD_NAME>DEVICEPROFILE</FIELD_NAME> 
    <LINE_NUMBER>0000000014</LINE_NUMBER> 
    <FIELD_VALUE>TOTAL_MEMORY:2038 MB </FIELD_VALUE> 
    </ITEM> 
    <ITEM> 
    <FIELD_NAME>DEVICEPROFILE</FIELD_NAME> 
    <LINE_NUMBER>0000000015</LINE_NUMBER> 
    <FIELD_VALUE>VIRTUAL_MACHINE_VERSION:1.4.2_11-b06 </FIELD_VALUE> 
    </ITEM> 
    <ITEM> 
    <FIELD_NAME>DEVICE_OTHERS</FIELD_NAME> 
    <LINE_NUMBER>0000000000</LINE_NUMBER> 
    <FIELD_VALUE>000 MI_SERVICE MOBILEENGINE_JSP I252000 </FIELD_VALUE> 
    </ITEM> 
    <ITEM> 
    <FIELD_NAME>NATIVE_CPU</FIELD_NAME> 
    <LINE_NUMBER>0000000000</LINE_NUMBER> 
    <FIELD_VALUE>1 </FIELD_VALUE> 
    </ITEM> 
    <ITEM> 
    <FIELD_NAME>NATIVE_JVM</FIELD_NAME> 
    <LINE_NUMBER>0000000000</LINE_NUMBER> 
    <FIELD_VALUE>1 </FIELD_VALUE> 
    </ITEM> 
    <ITEM> 
    <FIELD_NAME>NATIVE_OS</FIELD_NAME> 
    <LINE_NUMBER>0000000000</LINE_NUMBER> 
    <FIELD_VALUE>1 </FIELD_VALUE> 
    </ITEM> 
    <ITEM> 
    <FIELD_NAME>RETURN</FIELD_NAME> 
    <LINE_NUMBER>0000000000</LINE_NUMBER> 
    <FIELD_VALUE>EWAF 016Due to a communications error method WAF_REGISTRY could not be executed </FIELD_VALUE> 
    </ITEM> 
    <ITEM> 
    <FIELD_NAME>SYNCUSER</FIELD_NAME> 
    <LINE_NUMBER>0000000000</LINE_NUMBER> 
    <FIELD_VALUE>DEVELOPER </FIELD_VALUE> 
    </ITEM> 
    </CONTAINER> 
    <CONTAINER> 
    <HEADER> 
    <CONTAINER_ID>23033E9E1FEA544486C5B7055A4BEB63</CONTAINER_ID> 
    <OWNER></OWNER> 
    <CONTAINER_TYPE>C</CONTAINER_TYPE> 
    <METHOD>AGENT_PARAMETERS</METHOD> 
    <CONVERSATION_ID></CONVERSATION_ID> 
    <PARENT_CONTAINER_ID>01148379c52d5ed4565e</PARENT_CONTAINER_ID> 
    <MESSAGE_INDEX>1</MESSAGE_INDEX> 
    <MESSAGE_TYPE> </MESSAGE_TYPE> 
    <SERVER_ID>NEW_PROTOCOL</SERVER_ID> 
    <BODY_TYPE></BODY_TYPE> 
    <BODY_LENGTH>0</BODY_LENGTH> 
    <SUB_CONTAINER_ID>-1</SUB_CONTAINER_ID> 
    <SUB_CONT_MAX>1</SUB_CONT_MAX> 
    <ITEM_FROM>0</ITEM_FROM> 
    <ITEM_TO>0</ITEM_TO> 
    <SEND_DATE>0000-00-00</SEND_DATE> 
    <SEND_TIME>00:00:00</SEND_TIME> 
    <EXECUTION_DATE>2007-08-20</EXECUTION_DATE> 
    <EXECUTION_TIME>19:02:49</EXECUTION_TIME> 
    <CONTAINER_STATUS> </CONTAINER_STATUS> 
    </HEADER> 
    </CONTAINER> 
    <CONTAINER> 
    <HEADER> 
    <CONTAINER_ID>7FDA313EFE33F349AB2F24E2B6C9F904</CONTAINER_ID> 
    <OWNER>DEVELOPER</OWNER> 
    <CONTAINER_TYPE>A</CONTAINER_TYPE> 
    <METHOD>WAF_REGISTRY</METHOD> 
    <CONVERSATION_ID></CONVERSATION_ID> 
    <PARENT_CONTAINER_ID>01148379c2ad4686a00f</PARENT_CONTAINER_ID> 
    <MESSAGE_INDEX>0</MESSAGE_INDEX> 
    <MESSAGE_TYPE> </MESSAGE_TYPE> 
    <SERVER_ID>NEW_PROTOCOL</SERVER_ID> 
    <BODY_TYPE></BODY_TYPE> 
    <BODY_LENGTH>0</BODY_LENGTH> 
    <SUB_CONTAINER_ID>-1</SUB_CONTAINER_ID> 
    <SUB_CONT_MAX>24</SUB_CONT_MAX> 
    <ITEM_FROM>0</ITEM_FROM> 
    <ITEM_TO>0</ITEM_TO> 
    <SEND_DATE>0000-00-00</SEND_DATE> 
    <SEND_TIME>00:00:00</SEND_TIME> 
    <EXECUTION_DATE>2007-08-20</EXECUTION_DATE> 
    <EXECUTION_TIME>19:02:49</EXECUTION_TIME> 
    <CONTAINER_STATUS>O</CONTAINER_STATUS> 
    </HEADER> 
    </CONTAINER> 
    <CONTAINER> 
    <HEADER> 
    <CONTAINER_ID>ECD848F604B8B740A8F604BB463D1B8A</CONTAINER_ID> 
    <OWNER>DEVELOPER</OWNER> 
    <CONTAINER_TYPE>C</CONTAINER_TYPE> 
    <METHOD>WAF_REGISTRY</METHOD> 
    <CONVERSATION_ID></CONVERSATION_ID> 
    <PARENT_CONTAINER_ID>011483784ae2a318c6cc</PARENT_CONTAINER_ID> 
    <MESSAGE_INDEX>0</MESSAGE_INDEX> 
    <MESSAGE_TYPE> </MESSAGE_TYPE> 
    <SERVER_ID>NEW_PROTOCOL</SERVER_ID> 
    <BODY_TYPE></BODY_TYPE> 
    <BODY_LENGTH>0</BODY_LENGTH> 
    <SUB_CONTAINER_ID>-1</SUB_CONTAINER_ID> 
    <SUB_CONT_MAX>26</SUB_CONT_MAX> 
    <ITEM_FROM>0</ITEM_FROM> 
    <ITEM_TO>0</ITEM_TO> 
    <SEND_DATE>0000-00-00</SEND_DATE> 
    <SEND_TIME>00:00:00</SEND_TIME> 
    <EXECUTION_DATE>2007-08-20</EXECUTION_DATE> 
    <EXECUTION_TIME>19:02:49</EXECUTION_TIME> 
    <CONTAINER_STATUS> </CONTAINER_STATUS> 
    </HEADER> 
    </CONTAINER> 
    [20070820 13:32:49:669] D [MI/Sync ] End: Dumping file F:\Program Files\SAP Mobile Infrastructure\sync\DEVELOPER\in\inbound.sync 
    [20070820 13:32:49:669] D [MI/Sync ] Initial buffer size of BinaryReader is 2332 
    [20070820 13:32:49:669] P [MI/Sync ] Read current inbound counter from file: 0 
    [20070820 13:32:49:669] P [MI/Sync ] Received sync counter 0 is valid 
    [20070820 13:32:49:669] P [MI/Sync ] Inbound file ready to be parsed 
    [20070820 13:32:49:669] P [MI/Sync ] Number of pending inbound containers before inbound processing = 0 
    [20070820 13:32:49:669] P [MI/Sync ] Synchronisation: Start processing inbound data 
    [20070820 13:32:49:685] I [MI/Sync ] -
    InboundContainer created: Type:R,Id:01148379c2ad4686a00f,SId:-1,Items:0,MaxI:26 
    [20070820 13:32:49:685] P [MI/Sync ] SyncInboundProcessing started for method WAF_REGISTRY 
    [20070820 13:32:49:685] W [MI/Sync ] Container Type:R,Id:01148379c2ad4686a00f,SId:-1,Items:0,MaxI:26 does not contain a conversation id, use defaull: MI444556454c4f504552 / MI444556454c4f504552 (User: DEVELOPER, MSD: Name: / MOBILEENGINE_JSP (V. 252000), Target=, Type=com.sap.ip.me.core.FrameworkApplicationType) 
    [20070820 13:32:49:685] P [MI/Core ] Thread Thread-40 switched context to MI444556454c4f504552 / MI444556454c4f504552 (User: DEVELOPER, MSD: Name: / MOBILEENGINE_JSP (V. 252000), Target=, Type=com.sap.ip.me.core.FrameworkApplicationType) (stack level 1) 
    [20070820 13:32:49:685] P [MI/Sync ] Process container: Type:R,Id:01148379c2ad4686a00f,SId:-1,Items:0,MaxI:26 
    [20070820 13:32:49:685] D [MI/Deployment ] com.sapmarkets.web.liTS.util.reg.RegistrySyncInboundProcessing called 
    [20070820 13:32:49:685] I [MI/Sync ] -
    InboundContainer created: Type:R,Id:01148379c2ad4686a00f,SId:-1,Items:0,MaxI:26 
    [20070820 13:32:49:685] P [MI/Sync ] Container processed without exceptions 
    [20070820 13:32:49:685] P [MI/Core ] original context restored 
    [20070820 13:32:49:685] P [MI/Sync ] SyncInboundProcessing finished successfully for method WAF_REGISTRY 
    [20070820 13:32:49:685] D [MI/Sync ] Write container header to file (container id = 01148379c69585fde8b0): F:\Program Files\SAP Mobile Infrastructure\sync\DEVELOPER\out\a000000j.sync 
    [20070820 13:32:49:685] P [MI/Sync ] Created outbound container for user DEVELOPER and method WAF_REGISTRY 
    [20070820 13:32:49:685] P [MI/Sync ] Process acknowledge container: 23033E9E1FEA544486C5B7055A4BEB63 
    [20070820 13:32:49:685] P [MI/Sync ] Process acknowledge container: 7FDA313EFE33F349AB2F24E2B6C9F904 
    [20070820 13:32:49:685] D [MI/Sync ] GUID generation last time (1187616769685) was >= than current time (1187616769685) --> use this time instead 1187616769686 
    [20070820 13:32:49:685] D [MI/Sync ] Write container header to file (container id = 01148379c696f5cc9649): F:\Program Files\SAP Mobile Infrastructure\sync\DEVELOPER\out\c0000005.sync 
    [20070820 13:32:49:685] P [MI/Sync ] Created outbound container for user DEVELOPER and method WAF_REGISTRY 
    [20070820 13:32:49:685] P [MI/Sync ] Process acknowledge container: ECD848F604B8B740A8F604BB463D1B8A 
    [20070820 13:32:49:685] D [MI/Sync ] Processed 1 not arranged, 0 arranged, 3 acknowledge containers and 0 sub containers 
    [20070820 13:32:49:685] P [MI/Core ] original context restored 
    [20070820 13:32:49:685] P [MI/Sync ] Number of pending inbound containers after inbound processing = 0 
    [20070820 13:32:49:685] P [MI/Sync ] Synchronisation: Processing of inbound data finished 
    [20070820 13:32:49:685] D [MI/Sync ] There are no more packages waiting 
    [20070820 13:32:49:685] D [MI/Sync ] resetting the info which outbound containers are already created for user DEVELOPER 
    [20070820 13:32:49:700] P [MI/Core ] original context restored 
    [20070820 13:32:49:700] P [MI/Sync ] Synchronization finished for user DEVELOPER 
    [20070820 13:32:49:700] D [MI/Sync ] Synchronisation: Fire SyncEvent 10 
    [20070820 13:32:49:700] P [MI/Core ] Thread Thread-40 switched context to MI2853484152454429 / MI2853484152454429 (User: (SHARED), MSD: Name: / MOBILEENGINE_JSP (V. 252000), Target=, Type=com.sap.ip.me.core.FrameworkApplicationType) (stack level 1) 
    [20070820 13:32:49:700] I [MI/API/Sync ] SyncEvent Performing com.sap.ip.me.ccms.remotetracing.RemoteTracingListener on ConversationId MI2853484152454429 
    [20070820 13:32:49:700] P [MI/Core ] original context restored 
    [20070820 13:32:49:700] P [MI/Core ] Thread Thread-40 switched context to MI444556454c4f504552 / MI444556454c4f504552 (User: DEVELOPER, MSD: Name: / MOBILEENGINE_JSP (V. 252000), Target=, Type=com.sap.ip.me.core.FrameworkApplicationType) (stack level 1) 
    [20070820 13:32:49:700] I [MI/API/Sync ] SyncEvent Performing com.sap.ip.me.core.StatusUpdater on ConversationId MI444556454c4f504552 
    [20070820 13:32:49:700] P [MI/Core ] original context restored 
    [20070820 13:32:49:700] P [MI/Core ] Thread Thread-40 switched context to MI2853484152454429 / MI2853484152454429 (User: (SHARED), MSD: Name: / MOBILEENGINE_JSP (V. 252000), Target=, Type=com.sap.ip.me.core.FrameworkApplicationType) (stack level 1) 
    [20070820 13:32:49:700] I [MI/API/Sync ] SyncEvent Performing com.sap.ip.me.ccms.LastSuccessfulSyncAlert on ConversationId MI2853484152454429 
    [20070820 13:32:49:700] P [MI/Core ] original context restored 
    [20070820 13:32:49:700] I [MI/API/Sync ] Skip performing Sync Event (10) com.sap.ip.me.core.StatusUpdater for conversation id MI4d495f53455256494345 / MI4d495f53455256494345 (User: MI_SERVICE, MSD: Name: / MOBILEENGINE_JSP (V. 252000), Target=, Type=com.sap.ip.me.core.FrameworkApplicationType) 
    [20070820 13:32:49:700] P [MI/Core ] Thread Thread-40 switched context to MI2853484152454429 / MI2853484152454429 (User: (SHARED), MSD: Name: / MOBILEENGINE_JSP (V. 252000), Target=, Type=com.sap.ip.me.core.FrameworkApplicationType) (stack level 1) 
    [20070820 13:32:49:700] I [MI/API/Sync ] SyncEvent Performing com.sap.ip.me.ccms.AlertManagerImpl on ConversationId MI2853484152454429 
    [20070820 13:32:49:700] P [MI/Core ] original context restored 
    [20070820 13:32:49:700] P [MI/Core ] Thread Thread-40 switched context to MI2853484152454429 / MI2853484152454429 (User: (SHARED), MSD: Name: / MOBILEENGINE_JSP (V. 252000), Target=, Type=com.sap.ip.me.core.FrameworkApplicationType) (stack level 1) 
    [20070820 13:32:49:700] I [MI/API/Sync ] SyncEvent Performing com.sap.ip.me.sync.LogSender on ConversationId MI2853484152454429 
    [20070820 13:32:49:700] P [MI/Core ] original context restored 
    [20070820 13:32:49:700] P [MI/Core ] Thread Thread-40 switched context to MI2853484152454429 / MI2853484152454429 (User: (SHARED), MSD: Name: / MOBILEENGINE_JSP (V. 252000), Target=, Type=com.sap.ip.me.core.FrameworkApplicationType) (stack level 1) 
    [20070820 13:32:49:700] I [MI/API/Sync ] SyncEvent Performing com.sap.ip.me.services.os.AgentManager$AgentSyncEventListener on ConversationId MI2853484152454429 
    [20070820 13:32:49:700] D [MI/Sync ] Opened temporary container file F:\Program Files\SAP Mobile Infrastructure\sync\(SHARED)\out\t0000005.sync for write (container id = 01148379c6a4d429f356) 
    [20070820 13:32:49:700] D [MI/Sync ] Write container header to file (container id = 01148379c6a4d429f356): F:\Program Files\SAP Mobile Infrastructure\sync\(SHARED)\out\z0000005.sync 
    [20070820 13:32:49:700] D [MI/Sync ] Closed container file (container id = 01148379c6a4d429f356) and rename container file to F:\Program Files\SAP Mobile Infrastructure\sync\(SHARED)\out\i0000005.sync 
    [20070820 13:32:49:700] P [MI/Sync ] Created outbound container for user (SHARED) and method AGENT_PARAMETERS 
    [20070820 13:32:49:716] P [MI/Core ] original context restored 
    [20070820 13:32:49:716] P [MI/Core ] Thread Thread-40 switched context to MI444556454c4f504552 / MI444556454c4f504552 (User: DEVELOPER, MSD: Name: / MOBILEENGINE_JSP (V. 252000), Target=, Type=com.sap.ip.me.core.FrameworkApplicationType) (stack level 1) 
    [20070820 13:32:49:716] I [MI/API/Sync ] SyncEvent Performing com.sap.ip.mi.systemnews.SyncListener on ConversationId MI444556454c4f504552 
    [20070820 13:32:49:716] P [MI/Core ] original context restored 
    [20070820 13:32:49:716] P [MI/Core ] Thread Thread-40 switched context to MI2853484152454429 / MI2853484152454429 (User: (SHARED), MSD: Name: / MOBILEENGINE_JSP (V. 252000), Target=, Type=com.sap.ip.me.core.FrameworkApplicationType) (stack level 1) 
    [20070820 13:32:49:716] I [MI/API/Sync ] SyncEvent Performing com.sap.ip.me.ccms.configinfo.ConfigInfoListener on ConversationId MI2853484152454429 
    [20070820 13:32:49:716] P [MI/Core ] original context restored 
    [20070820 13:32:49:716] P [MI/Sync ] Repetitive sync is turned off 
    [20070820 13:32:49:716] D [MI/Sync ] Synchronisation: Fire SyncEvent 2 
    [20070820 13:32:49:716] P [MI/Core ] Thread Thread-40 switched context to MI2853484152454429 / MI2853484152454429 (User: (SHARED), MSD: Name: / MOBILEENGINE_JSP (V. 252000), Target=, Type=com.sap.ip.me.core.FrameworkApplicationType) (stack level 1) 
    [20070820 13:32:49:716] I [MI/API/Sync ] SyncEvent Performing com.sap.ip.me.ccms.remotetracing.RemoteTracingListener on ConversationId MI2853484152454429 
    [20070820 13:32:49:716] P [MI/Core ] original context restored 
    [20070820 13:32:49:716] P [MI/Core ] Thread Thread-40 switched context to MI444556454c4f504552 / MI444556454c4f504552 (User: DEVELOPER, MSD: Name: / MOBILEENGINE_JSP (V. 252000), Target=, Type=com.sap.ip.me.core.FrameworkApplicationType) (stack level 1) 
    [20070820 13:32:49:716] I [MI/API/Sync ] SyncEvent Performing com.sap.ip.me.core.StatusUpdater on ConversationId MI444556454c4f504552 
    [20070820 13:32:49:716] P [MI/Core ] original context restored 
    [20070820 13:32:49:716] P [MI/Core ] Thread Thread-40 switched context to MI2853484152454429 / MI2853484152454429 (User: (SHARED), MSD: Name: / MOBILEENGINE_JSP (V. 252000), Target=, Type=com.sap.ip.me.core.FrameworkApplicationType) (stack level 1) 
    [20070820 13:32:49:716] I [MI/API/Sync ] SyncEvent Performing com.sap.ip.me.ccms.LastSuccessfulSyncAlert on ConversationId MI2853484152454429 
    [20070820 13:32:49:716] P [MI/Core ] original context restored 
    [20070820 13:32:49:716] I [MI/API/Sync ] Skip performing Sync Event (2) com.sap.ip.me.core.StatusUpdater for conversation id MI4d495f53455256494345 / MI4d495f53455256494345 (User: MI_SERVICE, MSD: Name: / MOBILEENGINE_JSP (V. 252000), Target=, Type=com.sap.ip.me.core.FrameworkApplicationType) 
    [20070820 13:32:49:716] P [MI/Core ] Thread Thread-40 switched context to MI2853484152454429 / MI2853484152454429 (User: (SHARED), MSD: Name: / MOBILEENGINE_JSP (V. 252000), Target=, Type=com.sap.ip.me.core.FrameworkApplicationType) (stack level 1) 
    [20070820 13:32:49:716] I [MI/API/Sync ] SyncEvent Performing com.sap.ip.me.ccms.AlertManagerImpl on ConversationId MI2853484152454429 
    [20070820 13:32:49:716] P [MI/Core ] original context restored 
    [20070820 13:32:49:716] P [MI/Core ] Thread Thread-40 switched context to MI2853484152454429 / MI2853484152454429 (User: (SHARED), MSD: Name: / MOBILEENGINE_JSP (V. 252000), Target=, Type=com.sap.ip.me.core.FrameworkApplicationType) (stack level 1) 
    [20070820 13:32:49:716] I [MI/API/Sync ] SyncEvent Performing com.sap.ip.me.sync.LogSender on ConversationId MI2853484152454429 
    [20070820 13:32:49:716] P [MI/Core ] original context restored 
    [20070820 13:32:49:716] P [MI/Core ] Thread Thread-40 switched context to MI2853484152454429 / MI2853484152454429 (User: (SHARED), MSD: Name: / MOBILEENGINE_JSP (V. 252000), Target=, Type=com.sap.ip.me.core.FrameworkApplicationType) (stack level 1) 
    [20070820 13:32:49:716] I [MI/API/Sync ] SyncEvent Performing com.sap.ip.me.services.os.AgentManager$AgentSyncEventListener on ConversationId MI2853484152454429 
    [20070820 13:32:49:716] P [MI/Core ] original context restored 
    [20070820 13:32:49:716] P [MI/Core ] Thread Thread-40 switched context to MI444556454c4f504552 / MI444556454c4f504552 (User: DEVELOPER, MSD: Name: / MOBILEENGINE_JSP (V. 252000), Target=, Type=com.sap.ip.me.core.FrameworkApplicationType) (stack level 1) 
    [20070820 13:32:49:716] I [MI/API/Sync ] SyncEvent Performing com.sap.ip.mi.systemnews.SyncListener on ConversationId MI444556454c4f504552 
    [20070820 13:32:49:716] P [MI/Core ] original context restored 
    [20070820 13:32:49:716] P [MI/Core ] Thread Thread-40 switched context to MI2853484152454429 / MI2853484152454429 (User: (SHARED), MSD: Name: / MOBILEENGINE_JSP (V. 252000), Target=, Type=com.sap.ip.me.core.FrameworkApplicationType) (stack level 1) 
    [20070820 13:32:49:716] I [MI/API/Sync ] SyncEvent Performing com.sap.ip.me.ccms.configinfo.ConfigInfoListener on ConversationId MI2853484152454429 
    [20070820 13:32:49:716] P [MI/Core ] original context restored 
    [20070820 13:32:49:716] D [MI/Sync ] Synchronisation: Fire SyncEvent 1 
    [20070820 13:32:49:716] P [MI/Core ] Thread Thread-40 switched context to MI2853484152454429 / MI2853484152454429 (User: (SHARED), MSD: Name: / MOBILEENGINE_JSP (V. 252000), Target=, Type=com.sap.ip.me.core.FrameworkApplicationType) (stack level 1) 
    [20070820 13:32:49:716] I [MI/API/Sync ] SyncEvent Performing com.sap.ip.me.ccms.remotetracing.RemoteTracingListener on ConversationId MI2853484152454429 
    [20070820 13:32:49:716] P [MI/Core ] original context restored 
    [20070820 13:32:49:716] P [MI/Core ] Thread Thread-40 switched context to MI444556454c4f504552 / MI444556454c4f504552 (User: DEVELOPER, MSD: Name: / MOBILEENGINE_JSP (V. 252000), Target=, Type=com.sap.ip.me.core.FrameworkApplicationType) (stack level 1) 
    [20070820 13:32:49:716] I [MI/API/Sync ] SyncEvent Performing com.sap.ip.me.core.StatusUpdater on ConversationId MI444556454c4f504552 
    [20070820 13:32:49:716] P [MI/Core ] original context restored 
    [20070820 13:32:49:716] P [MI/Core ] Thread Thread-40 switched context to MI2853484152454429 / MI2853484152454429 (User: (SHARED), MSD: Name: / MOBILEENGINE_JSP (V. 252000), Target=, Type=com.sap.ip.me.core.FrameworkApplicationType) (stack level 1) 
    [20070820 13:32:49:716] I [MI/API/Sync ] SyncEvent Performing com.sap.ip.me.ccms.LastSuccessfulSyncAlert on ConversationId MI2853484152454429 
    [20070820 13:32:49:716] P [MI/Core ] original context restored 
    [20070820 13:32:49:716] I [MI/API/Sync ] Skip performing Sync Event (1) com.sap.ip.me.core.StatusUpdater for conversation id MI4d495f53455256494345 / MI4d495f53455256494345 (User: MI_SERVICE, MSD: Name: / MOBILEENGINE_JSP (V. 252000), Target=, Type=com.sap.ip.me.core.FrameworkApplicationType) 
    [20070820 13:32:49:716] P [MI/Core ] Thread Thread-40 switched context to MI2853484152454429 / MI2853484152454429 (User: (SHARED), MSD: Name: / MOBILEENGINE_JSP (V. 252000), Target=, Type=com.sap.ip.me.core.FrameworkApplicationType) (stack level 1) 
    [20070820 13:32:49:716] I [MI/API/Sync ] SyncEvent Performing com.sap.ip.me.ccms.AlertManagerImpl on ConversationId MI2853484152454429 
    [20070820 13:32:49:716] P [MI/Core ] original context restored 
    [20070820 13:32:49:716] P [MI/Core ] Thread Thread-40 switched context to MI2853484152454429 / MI2853484152454429 (User: (SHARED), MSD: Name: / MOBILEENGINE_JSP (V. 252000), Target=, Type=com.sap.ip.me.core.FrameworkApplicationType) (stack level 1) 
    [20070820 13:32:49:716] I [MI/API/Sync ] SyncEvent Performing com.sap.ip.me.sync.LogSender on ConversationId MI2853484152454429 
    [20070820 13:32:49:716] P [MI/Core ] original context restored 
    [20070820 13:32:49:716] P [MI/Core ] Thread Thread-40 switched context to MI2853484152454429 / MI2853484152454429 (User: (SHARED), MSD: Name: / MOBILEENGINE_JSP (V. 252000), Target=, Type=com.sap.ip.me.core.FrameworkApplicationType) (stack level 1) 
    [20070820 13:32:49:716] I [MI/API/Sync ] SyncEvent Performing com.sap.ip.me.services.os.AgentManager$AgentSyncEventListener on ConversationId MI2853484152454429 
    [20070820 13:32:49:716] P [MI/Core ] original context restored 
    [20070820 13:32:49:716] P [MI/Core ] Thread Thread-40 switched context to MI444556454c4f504552 / MI444556454c4f504552 (User: DEVELOPER, MSD: Name: / MOBILEENGINE_JSP (V. 252000), Target=, Type=com.sap.ip.me.core.FrameworkApplicationType) (stack level 1) 
    [20070820 13:32:49:716] I [MI/API/Sync ] SyncEvent Performing com.sap.ip.mi.systemnews.SyncListener on ConversationId MI444556454c4f504552 
    [20070820 13:32:49:716] P [MI/Core ] original context restored 
    [20070820 13:32:49:716] P [MI/Core ] Thread Thread-40 switched context to MI2853484152454429 / MI2853484152454429 (User: (SHARED), MSD: Name: / MOBILEENGINE_JSP (V. 252000), Target=, Type=com.sap.ip.me.core.FrameworkApplicationType) (stack level 1) 
    [20070820 13:32:49:716] I [MI/API/Sync ] SyncEvent Performing com.sap.ip.me.ccms.configinfo.ConfigInfoListener on ConversationId MI2853484152454429 
    [20070820 13:32:49:716] P [MI/Core ] original context restored 
    [20070820 13:32:49:716] I [MI/Sync ] Synchronization finished, Thread=Thread-40 
    [20070820 13:32:58:732] D [MI/Core ] Set current application to 'MOBILEENGINE_JSP' 
    [20070820 13:32:58:732] D [MI/API/Runtime/JSP ] AbstractMEHttpServlet:doGet(...) called 
    [20070820 13:32:58:732] D [MI/API/Runtime/JSP ] AbstractMEHttpServlet:getEvent() done with event name = '' 
    [20070820 13:32:58:732] D [MI/API/Runtime/JSP ] AbstractMEHttpServlet:dispatch request to '/jsp/home/home.jsp' 
    [20070820 13:33:01:028] D [MI/Core ] Set current application to 'MOBILEENGINE_JSP' 
    [20070820 13:33:01:028] D [MI/API/Runtime/JSP ] AbstractMEHttpServlet:doGet(...) called 
    [20070820 13:33:01:028] D [MI/API/Runtime/JSP ] AbstractMEHttpServlet:getEvent() done with event name = '' 
    [20070820 13:33:01:028] D [MI/API/Runtime/JSP ] AbstractMEHttpServlet:dispatch request to '/jsp/trace/trace.jsp' 
    [20070820 13:33:03:747] D [MI/Core ] Set current application to 'MOBILEENGINE_JSP' 
    [20070820 13:33:03:747] D [MI/API/Runtime/JSP ] AbstractMEHttpServlet:doGet(...) called 
    [20070820 13:33:03:747] D [MI/API/Runtime/JSP ] AbstractMEHttpServlet:getEvent() done with event name = ''

    question closed.

  • Report for update of Material with deletion Flag from R/3 to SRM

    Hi All,
               Is any report for Updating material in SRM with deletion indicator for those  deletion flag set in R/3...

    Check material status
      IF mat_mmsta EQ '--'.
        lv_msgv1 = iv_ordered_prod.
        CALL FUNCTION 'BBP_PD_MSG_ADD'
          EXPORTING
            i_msgty       = c_msgty_e
            i_msgid       = 'BBP_PD'
            i_msgno       = 426
            i_msgv1       = lv_msgv1
          EXCEPTIONS
            log_not_found = 1
            OTHERS        = 2.
        IF sy-subrc <> 0.
          PERFORM abort.
        ENDIF.
        IF c_on = c_off.
          MESSAGE e426(bbp_pd) WITH lv_msgv1.
        ENDIF.
      ENDIF.
      if not mat_lvorm is initial.
        lv_msgv1 = iv_ordered_prod.
        call function 'BBP_PD_MSG_ADD'
    program name LBBP_PDIGPF2R
    Check material in backend
      CALL FUNCTION 'META_MATERIAL_READ'
        EXPORTING
          i_mtcom        = ls_mtcom_eci
          logical_system = iv_log_system
        IMPORTING
          e_mmsta        = mat_mmsta
          e_lvorm        = mat_lvorm
        EXCEPTIONS
          mat_not_found  = 1
          OTHERS         = 2.
      IF sy-subrc <> 0.
        lv_msgv1 = iv_ordered_prod.
        lv_msgv2 = iv_plant.
        CALL FUNCTION 'BBP_PD_MSG_ADD'
          EXPORTING
            i_msgty       = c_msgty_e
            i_msgid       = 'BBP_PD'
            i_msgno       = 275
            i_msgv1       = lv_msgv1
            i_msgv2       = lv_msgv2
          EXCEPTIONS
            log_not_found = 1
            OTHERS        = 2.
        IF sy-subrc <> 0.
          PERFORM abort.
        ENDIF.
        IF c_on = c_off.
          MESSAGE e275(bbp_pd) WITH lv_msgv1 lv_msgv2.
        ENDIF.
      ENDIF.
          EXPORTING
            i_msgty       = c_msgty_e
            i_msgid       = 'BBP_PD'
            i_msgno       = 345
          EXCEPTIONS
            log_not_found = 1
            others        = 2.
        if sy-subrc <> 0.
          perform abort.
        endif.
        if c_on = c_off.
    IN SRM PROGRAM LBBP_PDIGPF2R BBP_PD 345 throws message "product x is designed for deletion"
    but it is validationg from fm 'META_MATERIAL_READ'
    please close this thread
    br
    muthu

  • Report in Designer fast, in Viewer extremely slow

    Hi.
    I have a report which connects to a SQL Server backend, calling 3 stored procs which deliver the data needed for the report. However, when I execute the report in the Designer (the web app uses CR 9, but I'm testing it with CR 2008 that came with VS 2008) it takes approx. 20 seconds to return with the data - yes, the query takes rather long...
    When I run our web application and call up the same report, using the same parameters and connected to the same database, the Viewer sits there for about 10 minutes before finally showing the report. I've been trying to determine the cause of this but have come up empty so far.
    The report itself is a fairly simple report: headers, a parameter overview (the report uses parameterized queries), the data, and no subtotals, no subreports, no formulas.
    Why is this taken so long using the Viewer? Apparently it can be fast(er) since the Designer comes within 20 secs WITH the correct data!
    I've tried a couple of things to see if I could determine the cause of the bad performance, but so far I've had no luck in improving performance whatsoever. The only thing left would be redesigning the underlying stored proc, but this is a rather complex stored proc and rewriting it would be no small task.
    Anybody has any idea on what to do next? Our customers are really annoyed by this (which I can understand) since they sometimes need to run this report a couple of times a day...

    Ludek Uher wrote:>
    >
    > Troubleshooting slow performance
    >
    > First thing to do with slow reports would be consulting the article u201COptimizing Reports for the Webu201D. The article can be downloaded from this location:
    >
    > https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/701c069c-271f-2b10-c780-dacbd90b2dd8
    >
    Interesting article. Unfortunately, trying several of the suggestions made, it didn't improve the report's performance. No noticeable difference in either Designer or Viewer.
    >
    > Next, determine where is the performance hit coming from? With Crystal Reports, there are at least four places in your code where slow downs may occur. These are:
    >
    > Report load
    > Connection to the data source
    > Setting of parameters
    > Actual report output, be it to a viewer, export or printer
    >
    This part is not relevant. Loading the report isn't the problem (first query being executed under 0.5 seconds after starting the report); as I'll explain further at the end of this reply.
    > A number of report design issues, report options and old runtimes may affect report performance. Possible report design issues include:
    >
    > u2022 OLE object inserted into a report is not where the report expects it to be. If this is the case, the report will attempt to locate the object, consuming potentially large amounts of time.
    The only OLE object is a picture with the company logo. It is visible in design time though, so I guess that means it is saved with the report?
    > u2022 The subreport option "Re-import when opening" is enabled (right click the subreport(s), choose format subreport, look at the subreport tab). This is a time consuming process and should be used judiciously.
    The report contains no subreports.
    > u2022 Specific printer is set for the report and the printer does not exist. Try the "No printer" option (File | Page setup). Also, see the following resources regarding printers and Crystal reports;
    Tried that. It was set to the Microsoft XPS Document writer, but checking the 'No printer' option only made a slight difference (roughly 0.4 seconds in Designer).
    > u2022 The number of subreports the report contains and in which section the subreports are located will impact report performance. Minimize the number of subreports used, or avoid using subreports if possible. Subreports are reports within a report, and if there is a subreport in a detail section, the subreport will run as many time as there are records, leading to long report processing times. Incorrect use of subreports is often the biggest factor why a report takes a long time to preview.
    As stated before, the report has no subreports.
    > u2022 Use of "Page N of M", or "TotalPageCount". When the special field "Page N of M" or "TotalPageCount" is used on a report, it will have to generate each page of the report before it displays the first page. This will cause the report to take more time to display the first page of the report
    The report DOES use the TotalPageCount and 'Page N of M' fields. But, since the report only consists of 3 pages, of which only 2 contain database-related (read further below) I think this would not be a problem.
    > u2022 Remove unused tables, unused formulas and unused running totals from the report. Even if these objects are not used in a report, the report engine will attempt to evaluate the objects, thus affecting performance.
    > u2022 Suppress unnecessary report sections. Even if a report section is not used, the report engine will attempt to evaluate the section, thus affecting performance.
    > u2022 If summaries are used in the report, use conditional formulas instead of running totals when ever possible.
    > u2022 Whenever possible, limit records through Record selection Formula, not suppression.
    > u2022 Use SQL expressions to convert fields to be used in record selection instead of using formula functions. For example, if you need to concatenate 2 fields together, instead of doing it in a formula, you can create a SQL Expression Field. It will concatenate the fields on the database server, instead of doing in Crystal Reports. SQL Expression Fields are added to the SELECT clause of the SQL Query send to the database.
    > u2022 Using one command table or Stored Procedure or a Table View as the datasource can be faster if you returns only the desired data set.
    > u2022 Perform grouping on the database server. This applies if you only need to return the summary to your report but not the details. It will be faster as less data will be returned to the reports.
    > u2022 Local client as well as server computer processor speed. Crystal Reports generates temp files in order to process the report. The temp files are used to further filter the data when necessary, as well as to group, sort, process formulas, and so on.
    All of the above points become moot if you know the structure of the report:
    3 pages, no subreports, 3 stored procs used, which each return a dataset.
    - Page 1 is just a summary of the parameters used for the report. This page also includes the TotalPageCount  field;
    - Page 2 uses 2 stored procs. The first one returns a dataset consisting of 1 row containing the headings for the columns of the data returned from stored proc 2. There will always be the same number of columns (only their heading will be different depending on the report), and the dataset is simply displayed as is.
    - The data from stored proc 2 is also displayed on Page 2. The stored proc returns a matrix, always the same number of columns, which is displayed as is. All calculations, groupings, etc. are done on the SQL Server;
    - Page 3 uses the third stored proc to display totals for the matrix from the previous page. This dataset too will always have the same number of columns, and all totaling is done on the database server. Just displaying the dataset as is.
    That's it. All heavy processing is done on the server.
    Because of the simplicity of the report I'm baffled as to why it would take so much more time when using the Viewer than from within the Designer.
    > Report options that may also affect report performance:
    >
    > u2022 u201CVerify on First Refreshu201D option (File | Report Options). This option forces the report to verify that no structural changes were made to the database. There may be instance when this is necessary, but once again, the option should be used only if really needed. Often, disabling this option will improve report performance significantly.
    > u2022 u201CVerify Stored Procedure on First Refreshu201D option (File | Report Options). Essentially the same function as above, however this option will only verify stored procedures.
    Hm. Both options WERE selected, and deselecting them caused the report to run approx. 10 seconds slower (from the Designer)...
    >
    >
    > If at all possible, use the latest runtime, be it with a custom application or the Crystal Reports Designer.
    >
    > u2022 The latest updates for the current versions of Crystal reports can be located on the SAP support download page:
    >
    > https://websmp130.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/bobj_download/main.htm
    >
    I've not done that (yet). Mainly because CR 10.5 came with VS2008, so it was easier to test to see if I can expect an improvement regarding my problem. Up till now, I see no improvement... ;-(
    > u2022 Crystal Report version incompatibility with Microsoft Visual Studio .NET. For details of which version of Crystal Reports is supported in which version of VS .NET, see the following wiki:
    >
    > https://wiki.sdn.sap.com/wiki/display/BOBJ/CrystalReportsassemblyversionsandVisualStudio+.NET
    >
    >
    According to that list I'm using a correct version with VS2008. I might consider upgrading it to CR 12, but I'm not sure what I would gain with that. Because I can't exactly determine the cause of the performance problems I can't tell whether upgrading would resolve the issue.
    > Performance hit is on database connection / data retrieval
    >
    > Database fine tuning, which may include the installation of the latest Service Packs for your database must be considered. Other factors affecting data retrieval:
    >
    > u2022 Network traffic
    > u2022 The number of records returned. If a SQL query returns a large number of records, it will take longer to format and display than if was returning a smaller data set. Ensure you only return the necessary data on the report, by creating a Record Selection Formula, or basing your report off a Stored Procedure, or a Command Object that only returns the desired data set.
    The amount of network traffic is extremely minimal. Two datasets (sp 1 and 3) return only 1 row containing 13 columns. The sp 2 returns the same number of columns, and (in this clients case) a dataset of only 22 rows, mainly numeric data!
    > u2022 The amount of time the database server takes to process the SQL query. Crystal Reports send the SQL query to the database, the database process it, and returns the data set to Crystal Reports.
    Ah. Here we get interesting details. I have been monitoring the queries fired using SQL Profiler and found that:
    - ALL queries are executed twice!
    - The 'data' query (sp 2) which takes the largest amount of time is even executed 3 times.
    For example, this is what SQL profiler shows (not the actual trace, but edited for clarity):
    Query                  Start time         Duration (ms)
    sp 1 (headers)      11:39:31.283     13
    sp 2 (data)            11:39:31.330     23953
    sp 3 (totals)          11:39.55.313     1313
    sp 1 (headers)      11:39:56.720     16
    sp 2 (data)            11:39:56.890     24156
    sp 3 (totals)          11:40:21.063     1266
    sp 2 (data)            11:40:22.487     24013
    Note that in this case I didn't trace the queries for the Viewer, but I have done just that last week. For sp2 the values run up to 9462 seconds!!!
    > u2022 Where is the Record Selection evaluated? Ensure your Record Selection Formula can be translated to SQL, so that the data can be filter down to the server. If a selection formula can not be translated into the correct SQL, the data filtering will be done on the local client computer which in most cases will be much slower. One way to check if a formula function is being translated into a SQL is to look at u201CShow SQL Queryu201D in the CR designer (Database -> Show SQL Query). Many Crystal Reports formula functions cannot be translated into SQL because there may not be a standard SQL for it. For example, control structure like IF THEN ELSE cannot be translated into SQL. It will always be evaluated on the client computer. For more information on IF THEN ELSE statements see note number 1214385 in the notes database:
    >
    > https://www.sdn.sap.com/irj/sdn/businessobjects-notes
    >
    Not applicable in this case I'm afraid. All the report does is fetch the datasets from the various stored procs and display them; no additional processing is taking place. Also, no records are selected as this is done using the parameters which are passed on to the stored procs.
    > u2022 Link tables on indexed fields whenever possible. While linking on non indexed fields is possible, it is not recommended.
    Although the stored procs might not be optimal, that is beside the point here. The point is that performance of a report when run from the Designer is acceptable (roughly 30 seconds for this report) but when viewing the same report from the Viewer the performance drops dramatically, into the range of 'becoming unusable'.
    The report has its dataconnection set at runtime, but it is set to the same values it had at design-time (hence the same DB server). I'm running this report connected to a stand-alone SQL Server which is a copy of the production server of my client, I'm the only user of that server, meaning there are no external disturbing factors I have to deal with. And still I'm experiencing the same problems my client has.
    I really need this problem solved. So far, I've not found a single thing to blame for the bad performance, except maybe that queries are executed multiple times by the CrystalReports engine. If it didn't do that, the time required to show the report would drop by approx. 60%.
    ...Charles...

  • 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.

  • View/Controller best practices

    Hello,
    A coworker and I are in charge of creating the standards for Web Dynpro development at our company.  We've been able to agree on most topics, but we're stuck on one issue.  Should ALL logic be in the controller or is it ok to perform some logic in the views?
    My coworker makes some valid points - we work in a team environment and you can't have two people working on the controller at the same time, if all your logic is in there, it's practically impossible for a group of developers to work on the same application.  In addition, there's often logic that's only applicable to a certain view.  He doesn't like the idea of a controller cluttered with logic from all the views, and doesn't see why we need to add an extra layer to execute something.  For instance, of a model is needed only for one view (say, to look up fields for a dropdown that only exists on that view), why have yet another executeSomeRFC method in the controller when we can do it in the view?
    My opinion is that Web Dynpro follows the MVC paradigm, and therefore all logic should be in the controller.  While it's true that right now a certain model or a certain piece of logic might only be needed for the one view, you never know if it will be needed somewhere else later.  In addition, to make the statement that "logic that's only needed for one view can be done in that view" leaves it open for a lot of interpretation and I think developers can start sneaking more and more code into the view because they think it's easier, when that is not what the view was created for. The exceptions, for me is logic that specifically has to do with the UI - for instance, if you select this checkbox, it will make 4 fields on the table disabled and change the label text of another field.
    We both see the other person's point of view and we can't decide where to move from here.  We're open to the opinions of other Web Dynpro experts.  What do you guys think?
    Thanks,
    Jennifer

    We have had the same discussion at my Company and came to the following conclusion and coding standard. It is preferable to keep all backend model call logic in the Component Controller, for various reasons if you ever drop a view or goto using some other type of UI interface  e.g. PDAs, with the same controller you already have the functionality there in the controller coded and tested.
    What I have seen happen before we adapted this standard with consultants  or less experienced developerrs is that they tend to copy and paste the same functionality from view to new view creating a maintenance headache down the road, even duplicating the code as they can not find the functionality or are too lazy to look for it then try coding their own. It is for this reason our company adapted the best practice of creating all backend call logic even if it is only required by a single view Dynpro View, in the component controller and calling it from the view as <b> wdThis.wdGet.doXXXFunction();</b>
    Also this helps code maintainers and new team members as they know all backend call logic is in the controller. I believe you will also find this practice recommended in the SAP Press WebDynpro Java books.
    Alex

  • XMAM sync never completes

    I have installed xMAM 3.0 (SR4 Patch 0) on a machine and when I click sync 9 out of 10 times sync never completes.
    Our MI server is MI7.0 SP12 patch0.
    Below is the trace file.Can some one point out what may be wrong please? How can I debug this in the middleware?
    Thanks.
    =========================================
    [20080401 15:38:23:382] I [MI/API/Logging           ] ***** LOG / TRACE SWITCHED ON
    [20080401 15:38:23:382] I [MI/API/Logging           ] ***** Mobile Infrastructure version: MI 70 SP 12 Patch 0 Build 200705080758
    [20080401 15:38:23:382] I [MI/API/Logging           ] ***** Current timezone: America/Chicago[20080401 15:38:23:382] I [MI/API/Logging           ] ***** Current Trace Level: 1000
    [20080401 15:38:23:382] I [MI                       ] Trace severity: All (1000)
    [20080401 15:38:23:382] D [MI/PIOS                  ] No implementations found. Error Code:(3)
    [20080401 15:38:23:382] D [MI/API/Runtime/JSP       ] AbstractMEHttpServlet:dispatch request to '/jsp/trace/trace.jsp'
    [20080401 15:38:29:553] D [MI/Core                  ] Set current application to 'MOBILEENGINE_JSP'
    [20080401 15:38:29:553] D [MI/API/Runtime/JSP       ] AbstractMEHttpServlet:doGet(...) called
    [20080401 15:38:29:553] D [MI/API/Runtime/JSP       ] AbstractMEHttpServlet:getEvent() done with event name = ''
    [20080401 15:38:29:553] D [MI/API/Runtime/JSP       ] AbstractMEHttpServlet:dispatch request to '/jsp/home/home.jsp'
    [20080401 15:38:29:569] D [MI/Core                  ] Set current application to 'MOBILEENGINE_JSP'
    [20080401 15:38:29:569] D [MI/API/Runtime/JSP       ] AbstractMEHttpServlet:doGet(...) called
    [20080401 15:38:29:569] D [MI/API/Runtime/JSP       ] AbstractMEHttpServlet:getEvent() done with event name = 'tracechangeTraceLevel'
    [20080401 15:38:29:569] D [MI/API/Runtime/JSP       ] AbstractMEHttpServlet:dispatch request to '/jsp/trace/trace.jsp'
    [20080401 15:38:33:366] D [MI/Core                  ] Set current application to 'MOBILEENGINE_JSP'
    [20080401 15:38:33:366] D [MI/API/Runtime/JSP       ] AbstractMEHttpServlet:doGet(...) called
    [20080401 15:38:33:366] D [MI/API/Runtime/JSP       ] AbstractMEHttpServlet:getEvent() done with event name = ''
    [20080401 15:38:33:366] D [MI/API/Runtime/JSP       ] AbstractMEHttpServlet:dispatch request to '/jsp/home/home.jsp'
    [20080401 15:38:35:553] D [MI/Core                  ] Set current application to 'MOBILEENGINE_JSP'
    [20080401 15:38:35:553] D [MI/API/Runtime/JSP       ] AbstractMEHttpServlet:doGet(...) called
    [20080401 15:38:35:553] D [MI/API/Runtime/JSP       ] AbstractMEHttpServlet:getEvent() done with event name = ''
    [20080401 15:38:35:569] P [MI/Sync                  ] Notify R3 called
    [20080401 15:38:35:569] D [MI/Sync                  ] There is already a container for method WAF_REGISTRY and user ELECT16 in the outbound queue
    [20080401 15:38:35:569] D [MI/API/Runtime/JSP       ] AbstractMEHttpServlet:dispatch request to '/jsp/home/home.jsp'
    [20080401 15:38:35:569] I [MI/Sync                  ] Synchronize with backend called, Thread=Thread-25
    [20080401 15:38:35:569] I [MI/Sync                  ] Thread=Thread-25 took lock for synchronization.
    [20080401 15:38:35:569] P [MI/Sync                  ] Use following gateway for synchronization: http://sppm01.rowancompanies.com:8000
    [20080401 15:38:45:631] D [MI/Core                  ] Set current application to 'MOBILEENGINE_JSP'
    [20080401 15:38:45:631] D [MI/API/Runtime/JSP       ] AbstractMEHttpServlet:doGet(...) called
    [20080401 15:38:45:631] D [MI/API/Runtime/JSP       ] AbstractMEHttpServlet:getEvent() done with event name = ''
    [20080401 15:38:45:631] D [MI/API/Runtime/JSP       ] AbstractMEHttpServlet:dispatch request to '/jsp/home/home.jsp'
    [20080401 15:38:55:709] D [MI/Core                  ] Set current application to 'MOBILEENGINE_JSP'
    [20080401 15:38:55:709] D [MI/API/Runtime/JSP       ] AbstractMEHttpServlet:doGet(...) called
    [20080401 15:38:55:709] D [MI/API/Runtime/JSP       ] AbstractMEHttpServlet:getEvent() done with event name = ''
    [20080401 15:38:55:709] D [MI/API/Runtime/JSP       ] AbstractMEHttpServlet:dispatch request to '/jsp/home/home.jsp'
    [20080401 15:39:05:788] D [MI/Core                  ] Set current application to 'MOBILEENGINE_JSP'
    [20080401 15:39:05:788] D [MI/API/Runtime/JSP       ] AbstractMEHttpServlet:doGet(...) called
    [20080401 15:39:05:788] D [MI/API/Runtime/JSP       ] AbstractMEHttpServlet:getEvent() done with event name = ''
    [20080401 15:39:05:788] D [MI/API/Runtime/JSP       ] AbstractMEHttpServlet:dispatch request to '/jsp/home/home.jsp'
    [20080401 15:39:15:866] D [MI/Core                  ] Set current application to 'MOBILEENGINE_JSP'
    [20080401 15:39:15:866] D [MI/API/Runtime/JSP       ] AbstractMEHttpServlet:doGet(...) called
    [20080401 15:39:15:866] D [MI/API/Runtime/JSP       ] AbstractMEHttpServlet:getEvent() done with event name = ''
    [20080401 15:39:15:866] D [MI/API/Runtime/JSP       ] AbstractMEHttpServlet:dispatch request to '/jsp/home/home.jsp'
    [20080401 15:39:25:944] D [MI/Core                  ] Set current application to 'MOBILEENGINE_JSP'
    [20080401 15:39:25:944] D [MI/API/Runtime/JSP       ] AbstractMEHttpServlet:doGet(...) called
    [20080401 15:39:25:944] D [MI/API/Runtime/JSP       ] AbstractMEHttpServlet:getEvent() done with event name = ''
    [20080401 15:39:25:944] D [MI/API/Runtime/JSP       ] AbstractMEHttpServlet:dispatch request to '/jsp/home/home.jsp'
    [20080401 15:39:36:037] D [MI/Core                  ] Set current application to 'MOBILEENGINE_JSP'
    [20080401 15:39:36:037] D [MI/API/Runtime/JSP       ] AbstractMEHttpServlet:doGet(...) called
    [20080401 15:39:36:037] D [MI/API/Runtime/JSP       ] AbstractMEHttpServlet:getEvent() done with event name = ''
    [20080401 15:39:36:037] D [MI/API/Runtime/JSP       ] AbstractMEHttpServlet:dispatch request to '/jsp/home/home.jsp'
    [20080401 15:39:46:162] D [MI/Core                  ] Set current application to 'MOBILEENGINE_JSP'
    [20080401 15:39:46:162] D [MI/API/Runtime/JSP       ] AbstractMEHttpServlet:doGet(...) called
    [20080401 15:39:46:162] D [MI/API/Runtime/JSP       ] AbstractMEHttpServlet:getEvent() done with event name = ''
    [20080401 15:39:46:162] D [MI/API/Runtime/JSP       ] AbstractMEHttpServlet:dispatch request to '/jsp/home/home.jsp'
    [20080401 15:39:56:225] D [MI/Core                  ] Set current application to 'MOBILEENGINE_JSP'
    [20080401 15:39:56:225] D [MI/API/Runtime/JSP       ] AbstractMEHttpServlet:doGet(...) called
    [20080401 15:39:56:225] D [MI/API/Runtime/JSP       ] AbstractMEHttpServlet:getEvent() done with event name = ''
    [20080401 15:39:56:225] D [MI/API/Runtime/JSP       ] AbstractMEHttpServlet:dispatch request to '/jsp/home/home.jsp'
    [20080401 15:40:06:303] D [MI/Core                  ] Set current application to 'MOBILEENGINE_JSP'
    [20080401 15:40:06:303] D [MI/API/Runtime/JSP       ] AbstractMEHttpServlet:doGet(...) called
    [20080401 15:40:06:303] D [MI/API/Runtime/JSP       ] AbstractMEHttpServlet:getEvent() done with event name = ''
    [20080401 15:40:06:303] D [MI/API/Runtime/JSP       ] AbstractMEHttpServlet:dispatch request to '/jsp/home/home.jsp'
    [20080401 15:40:16:631] P [MI/ComServer             ] Connection to client established
    [20080401 15:40:16:631] D [MI/ComServer             ] Client: received command: shutdownsmooth
    [20080401 15:40:28:209] D [MI/Core                  ] Set current application to 'MOBILEENGINE_JSP'
    [20080401 15:40:28:209] D [MI/API/Runtime/JSP       ] AbstractMEHttpServlet:doGet(...) called
    [20080401 15:40:28:209] D [MI/API/Runtime/JSP       ] AbstractMEHttpServlet:getEvent() done with event name = ''
    [20080401 15:40:28:209] D [MI/API/Runtime/JSP       ] AbstractMEHttpServlet:dispatch request to '/jsp/home/home.jsp'

    Hi,
    you need to find mobileID for your installation and go to monitor - that will give you more details on what is happening with sync process.
    Please refer to this link:
    http://help.sap.com/saphelp_nw70/helpdata/en/43/4411ce2d281bcde10000000a1553f7/frameset.htm
    to get info on monitoring functionlaity of Mobile Infrastructure.
    Regards,
    Larissa Limarova

  • Integrating SRM and Oracle using XI as middle layer

    Hi,
      In our current scenario we are implementing stratagic sourcing,operational procurement in SRM 5.0 with backend as Oracle E-business suite using XI as integration layer.
    As i have seen SAP config guides in all acenario's are there between SRM and SAP system as backend.But in our scenarion we have Oracle as backend system.
    If i follow the config guides EBP part in SPRO defining backend systems i need to give RFC destination of the backend SAP system.Suppose if it is Oracle then how can i define my backend systems with RFC destination.
    How can i define RFC destination,logical system name for my backned Oracle.
    Is there any specific SAP documentation and config guide which says about configuration if my backend is non-sap system(Oracle).
    I went through all the messages in this forum .All are talking about backend as R/3.
    We are implementating SRM 5.0 with Oracle as backend.
    Can you send me any documenation and config guides if any one did this type implementation.
    <b>Note: I have all config guides if R/3 is backend</b>
    regards
    Usman

    Hi Usman,
    to integrate non R/3 backend, you have to define your OA system as a backend in SRM, with the backend type NON SAP SYSTEM 1 to 3, and an RFC destination.
    Between SRM and OA, you will need a gateway, an EAI, that will handle your interfaces. In your case this is XI.
    You can use the XI RFC adapter, with a TCPIP RFC destination, targeting XI via a registered program ID.
    Then depending on your scenario (classic, extended, standalone), you will be more or less integrated with this non SAP backend.
    To communicate with a backend, SRM uses the concept of META BAPIs: each backend call is backend type dependant.
    You will have to work on each META call from SRM (have a look a table BBP_FUNCTION_MAP, with backend type = Non SAP system).
    Each backend RFC call will have to be evaluated and designed (ex: do you enable backend accounting check).
    The more integrated scenario you select, the more integration work you will have.
    Usually, for OA integration, we use a standalone scenario with some specific replication of PO, GR.
    You could use the extended classic scenario, but this will require more integration points.
    Rgds
    Christophe
    PS: please reward points for helpfull answers

  • Message "No Dynpro found" after generating a Dynpro by "GENERATE DYNPRO"

    Hello together,
    after I generate a dynpro in my report by using the GENERTATE DYNPRO-Command; i want to call this dynpro with
    call subscreen sub including sub-repid sub-dynnr.
    but SAP shows the message "DYNPRO_NOT_FOUND" although the SY-SUBRC is 0 after the GENERATE-Statement.
    Can anybody help on that?
    Kind regards
    Udo

    The website you're visiting runs using a "backend" called Web Dynpro.
    Web Dynpro does not support Firefox 5, and, "renders improperly in any browser but Internet Explorer (not compatible with Explorer 9)" (quoted from [http://en.wikipedia.org/wiki/Web_Dynpro here] ).
    Web Dynpro is proprietary software developed by SAP AG, and if this company decided to not create a website platform compatible with our browser, there's not much that we can do.
    You can use [https://addons.mozilla.org/en-US/firefox/addon/user-agent-switcher/ this addon] to fake the browser's name and version given to the website, or you may try using Internet Explorer inside Firefox by installing [https://addons.mozilla.org/en-US/firefox/addon/ie-tab-plus-self-hosted-versio/ this addon] .
    '''Attention''' : Addons aren't developed by Mozilla, so we can't provide full support to them, since every addon has a different creator, developer and code.

  • Error on Syncronize

    <b>Hi all,</b>
    An error is happening in my application. my net is unstable and nor always I obtain to complete to the synchronization. When I sending one solicitation and happens error, suggests the user to restart the process again. What it happens is that when it executes and complete the transaction, the MI submits 2 times to r/3.
    <b>att.,
    Douglas</b>

    hi Sandeep
    here is the trace code with a try lose and other try sucessful..
    Página inicial  
    Rastrear   
    I ***** LOG / TRACE SWITCHED ON 
    I ***** Mobile Engine version: MI 25 SP 13 Patch 00 Build 200507282032 
    I ***** Current timezone: America/Sao_Paulo 
    I Trace severity: All (1000) 
    D AbstractMEHttpServlet:dispatch request to '/jsp/trace/trace.jsp' 
    D Set current application to 'MOBILEENGINE_JSP' 
    D AbstractMEHttpServlet:doGetThreadSafe() called Thread = " Thread-8". 
    D AbstractMEHttpServlet:getEvent() done with event name = '' 
    D AbstractMEHttpServlet:dispatch request to '/jsp/home/home.jsp' 
    D Set current application to 'MOBILEENGINE_JSP' 
    D AbstractMEHttpServlet:doGetThreadSafe() called Thread = " Thread-10". 
    D AbstractMEHttpServlet:getEvent() done with event name = '' 
    D AbstractMEHttpServlet:dispatch request to 'http://127.0.0.1:4444/ZMDKRECEBIMENTO/start' 
    D Deactivated application MOBILEENGINE_JSP 
    D Set current application to 'ZMDKRECEBIMENTO' 
    P Activate application ZMDKRECEBIMENTO 
    D Smart Sync framework: entering new context :5E7C57A41716D64A9329B1C062141786 - FEB7E3AAF420D445AFD89B03E390359B 
    D AbstractMEHttpServlet:doGetThreadSafe() called Thread = " Thread-8". 
    D AbstractMEHttpServlet:getEvent() done with event name = '' 
    D AbstractMEHttpServlet:dispatch request to '/recebimento.jsp' 
    D Set current application to 'ZMDKRECEBIMENTO' 
    D AbstractMEHttpServlet:doGetThreadSafe() called Thread = " Thread-8". 
    D AbstractMEHttpServlet:getEvent() done with event name = 'boxorigem' 
    D AbstractMEHttpServlet:dispatch request to '/jsp/recboxorigem.jsp' 
    D Set current application to 'ZMDKRECEBIMENTO' 
    D AbstractMEHttpServlet:doGetThreadSafe() called Thread = " Thread-10". 
    D AbstractMEHttpServlet:getEvent() done with event name = '' 
    D AbstractMEHttpServlet:dispatch request to '/jsp/recebimentmaterial.jsp' 
    D Set current application to 'ZMDKRECEBIMENTO' 
    D AbstractMEHttpServlet:doGetThreadSafe() called Thread = " Thread-8". 
    D AbstractMEHttpServlet:getEvent() done with event name = '' 
    D AbstractMEHttpServlet:dispatch request to '/jsp/recebimentmaterial.jsp' 
    D Set current application to 'ZMDKRECEBIMENTO' 
    D AbstractMEHttpServlet:doGetThreadSafe() called Thread = " Thread-10". 
    D AbstractMEHttpServlet:getEvent() done with event name = 'boxdestino' 
    D AbstractMEHttpServlet:dispatch request to '/jsp/recboxdestino.jsp' 
    D Set current application to 'ZMDKRECEBIMENTO' 
    D AbstractMEHttpServlet:doGetThreadSafe() called Thread = " Thread-8". 
    D AbstractMEHttpServlet:getEvent() done with event name = '' 
    D Opened temporary container file E:Arquivos de programasSAP Mobile Infrastructuresync(SHARED)out     000000h.sync for write (container id = 01131aa6d1046f5c286c) 
    D Write container header to file (container id = 01131aa6d1046f5c286c): E:Arquivos de programasSAP Mobile Infrastructuresync(SHARED)outz000003r.sync 
    D Closed container file (container id = 01131aa6d1046f5c286c) and rename container file to E:Arquivos de programasSAP Mobile Infrastructuresync(SHARED)outi000003r.sync 
    P Created outbound container for user (SHARED) and method ZMDK_WRP_REC_CREATE 
    P Created outbound container for conversationId FEB7E3AAF420D445AFD89B03E390359B / FEB7E3AAF420D445AFD89B03E390359B (User: (SHARED), MSD: Name: / ZMDKRECEBIMENTO (V. 2.01), Target=, Type=com.sap.ip.me.core.JspApplicationType) 
    I Synchronize with backend called, Thread=Thread-8 
    I Thread=Thread-8 took lock for synchronization. 
    P Use following gateway for synchronization: http://wasaepd01:8001 
    D UrlConnectionTest: returning instance for same host wasaepd01 
    D UrlConnectionTest: lastHostChecked was wasaepd01 
    D UrlConnectionTest: lastTimeOfCheck was 1181562673062 
    D UrlConnectionTest: last check was 473484 ms ago 
    D UrlConnectionTest: try number: 1 
    D UrlConnectionTestThread: method run() started... 
    D E:Arquivos de programasSAP Mobile Infrastructureproxyauth.txt does not exist, therefore no Proxy-Authorization is set. 
    D UrlConnectionTest: try number: 2 
    D UrlConnectionTest: try number: 3 
    D UrlConnectionTest: try number: 4 
    D UrlConnectionTest: try number: 5 
    D UrlConnectionTest: try number: 6 
    D UrlConnectionTest: try number: 7 
    D UrlConnectionTest: try number: 8 
    D UrlConnectionTest: try number: 9 
    D UrlConnectionTest: try number: 10 
    D UrlConnectionTest: try number: 11 
    D UrlConnectionTest: try number: 12 
    D UrlConnectionTest: it took 6000 ms to test the connection 
    P UrlConnectionTest: Connection could not be established!!! 
    W Cannot connect to gateway 
    com.sap.ip.me.api.services.HttpConnectionException: URL connection test timeout 
    at com.sap.ip.me.api.services.IOUtils.isConnectable(IOUtils.java:664) 
    at com.sap.ip.me.sync.SyncManagerImpl.doConnectionTest(SyncManagerImpl.java:532) 
    at com.sap.ip.me.sync.SyncManagerImpl.synchronizeWithBackend(SyncManagerImpl.java:383) 
    at com.sap.ip.me.sync.SyncManagerImpl.synchronizeWithBackend(SyncManagerImpl.java:285) 
    at com.sap.ip.me.api.sync.SyncManager.synchronizeWithBackend(SyncManager.java:79) 
    at br.com.gerdau.rec.rfc.ZMOB_WRP_REC_CREATE.confirmaRecebimento(ZMOB_WRP_REC_CREATE.java:175) 
    at br.com.gerdau.rec.RecebimentoServlet.confirmaRecebimento(RecebimentoServlet.java:676) 
    at br.com.gerdau.rec.RecebimentoServlet.doHandleEvent(RecebimentoServlet.java:454) 
    at com.sap.ip.me.api.runtime.jsp.AbstractMEHttpServlet.doGetThreadSafe(AbstractMEHttpServlet.java:412) 
    at com.sap.ip.me.api.runtime.jsp.AbstractMEHttpServlet.doGet(AbstractMEHttpServlet.java:675) 
    at com.sap.ip.me.api.runtime.jsp.AbstractMEHttpServlet.doPost(AbstractMEHttpServlet.java:695) 
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:760) 
    at com.sap.ip.me.api.runtime.jsp.AbstractMEHttpServlet.service(AbstractMEHttpServlet.java:326) 
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) 
    at org.apache.tomcat.core.ServletWrapper.doService(ServletWrapper.java:405) 
    at org.apache.tomcat.core.Handler.service(Handler.java:287) 
    at org.apache.tomcat.core.ServletWrapper.service(ServletWrapper.java:372) 
    at org.apache.tomcat.core.ContextManager.internalService(ContextManager.java:806) 
    at org.apache.tomcat.core.ContextManager.service(ContextManager.java:752) 
    at org.apache.tomcat.service.http.HttpConnectionHandler.processConnection(HttpConnectionHandler.java:213) 
    at org.apache.tomcat.service.TcpWorkerThread.runIt(PoolTcpEndpoint.java:416) 
    at org.apache.tomcat.util.ThreadPool$ControlRunnable.run(ThreadPool.java:501) 
    at java.lang.Thread.run(Thread.java:534) 
    I Synchronization finished, Thread=Thread-8 
    D AbstractMEHttpServlet:dispatch request to '/jsp/message.jsp' 
    A URLConnectionThread: caught exception java.net.ConnectException: Connection timed out: connect 
    java.net.ConnectException: Connection timed out: connect 
    at java.net.PlainSocketImpl.socketConnect(Native Method) 
    at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:305) 
    at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:171) 
    at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:158) 
    at java.net.Socket.connect(Socket.java:452) 
    at java.net.Socket.connect(Socket.java:402) 
    at sun.net.NetworkClient.doConnect(NetworkClient.java:139) 
    at sun.net.www.http.HttpClient.openServer(HttpClient.java:402) 
    at sun.net.www.http.HttpClient.openServer(HttpClient.java:618) 
    at sun.net.www.http.HttpClient.(HttpClient.java:306) 
    at sun.net.www.http.HttpClient.(HttpClient.java:267) 
    at sun.net.www.http.HttpClient.New(HttpClient.java:339) 
    at sun.net.www.http.HttpClient.New(HttpClient.java:320) 
    at sun.net.www.http.HttpClient.New(HttpClient.java:315) 
    at sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:521) 
    at sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection.java:498) 
    at com.sap.ip.me.api.services.UrlConnectionTest$UrlConnectionTestThread.run(UrlConnectionTest.java:332) 
    D Set current application to 'ZMDKRECEBIMENTO' 
    D AbstractMEHttpServlet:doGetThreadSafe() called Thread = " Thread-10". 
    D AbstractMEHttpServlet:getEvent() done with event name = 'boxorigem' 
    D AbstractMEHttpServlet:dispatch request to '/jsp/recboxorigem.jsp' 
    D Set current application to 'ZMDKRECEBIMENTO' 
    D AbstractMEHttpServlet:doGetThreadSafe() called Thread = " Thread-8". 
    D AbstractMEHttpServlet:getEvent() done with event name = '' 
    D AbstractMEHttpServlet:dispatch request to '/jsp/recebimentmaterial.jsp' 
    D Set current application to 'ZMDKRECEBIMENTO' 
    D AbstractMEHttpServlet:doGetThreadSafe() called Thread = " Thread-10". 
    D AbstractMEHttpServlet:getEvent() done with event name = '' 
    D AbstractMEHttpServlet:dispatch request to '/jsp/recebimentmaterial.jsp' 
    D Set current application to 'ZMDKRECEBIMENTO' 
    D AbstractMEHttpServlet:doGetThreadSafe() called Thread = " Thread-8". 
    D AbstractMEHttpServlet:getEvent() done with event name = 'boxdestino' 
    D AbstractMEHttpServlet:dispatch request to '/jsp/recboxdestino.jsp' 
    D Set current application to 'ZMDKRECEBIMENTO' 
    D AbstractMEHttpServlet:doGetThreadSafe() called Thread = " Thread-10". 
    D AbstractMEHttpServlet:getEvent() done with event name = '' 
    D Opened temporary container file E:Arquivos de programasSAP Mobile Infrastructuresync(SHARED)out     000000i.sync for write (container id = 01131aa74b73790e8280) 
    D Write container header to file (container id = 01131aa74b73790e8280): E:Arquivos de programasSAP Mobile Infrastructuresync(SHARED)outz000003s.sync 
    D Closed container file (container id = 01131aa74b73790e8280) and rename container file to E:Arquivos de programasSAP Mobile Infrastructuresync(SHARED)outi000003s.sync 
    P Created outbound container for user (SHARED) and method ZMDK_WRP_REC_CREATE 
    P Created outbound container for conversationId FEB7E3AAF420D445AFD89B03E390359B / FEB7E3AAF420D445AFD89B03E390359B (User: (SHARED), MSD: Name: / ZMDKRECEBIMENTO (V. 2.01), Target=, Type=com.sap.ip.me.core.JspApplicationType) 
    I Synchronize with backend called, Thread=Thread-10 
    I Thread=Thread-10 took lock for synchronization. 
    P Use following gateway for synchronization: http://wasaepd01:8001 
    D UrlConnectionTest: returning instance for same host wasaepd01 
    D UrlConnectionTest: lastHostChecked was wasaepd01 
    D UrlConnectionTest: lastTimeOfCheck was 1181563146546 
    D UrlConnectionTest: last check was 31297 ms ago 
    D UrlConnectionTest: try number: 1 
    D UrlConnectionTestThread: method run() started... 
    D E:Arquivos de programasSAP Mobile Infrastructureproxyauth.txt does not exist, therefore no Proxy-Authorization is set. 
    D UrlConnectionTest: try number: 2 
    D UrlConnectionTestThread: URL protocol is http 
    D UrlConnectionTestThread: HTTP responsecode is 200 
    D UrlConnectionTest: it took 1000 ms to test the connection 
    P UrlConnectionTest: Connection could be established!!! 
    P URL connection test was successfull!!! 
    D Synchronisation: Fire SyncEvent 0 
    P Thread Thread-10 switched context to MI4558444649475545 / 890A084C789BD242BE0EF4CCA2A4B74E (User: EXDFIGUE, MSD: Name: / MOBILEENGINE_JSP (V. 251300), Target=, Type=com.sap.ip.me.core.FrameworkApplicationType) (stack level 1) 
    I SyncEvent Performing com.sap.ip.me.core.StatusUpdater on ConversationId MI4558444649475545 
    D Smart Sync framework: entering new context :MI2853484152454429 - MI2853484152454429 
    D Get IPersistenceManager for ConversationID: MI2853484152454429 
    D beginTransaction() called with doWait=false for instance 16706762 
    D PersistenceManagerImpl.beginTransaction():false 
    D PersistenceManagerImpl.get(IQuery):(Type: (IClassDescriptor(Name: meta_topRow)))(Condition: (ALWAYS TRUE))(Order: ((IAttributeDescriptor(Name: downloadOrder)) asc))(Start index: 0)(Max results: -1) 
    D commit() called on instance 16706762 
    D PersistenceManagerImpl.commit() 
    P original context restored 
    D Smart Sync framework: entering new context :5E7C57A41716D64A9329B1C062141786 - FEB7E3AAF420D445AFD89B03E390359B 
    P Thread Thread-10 switched context to MI2853484152454429 / 05DFF40679CABF458D250847C70D06EA (User: (SHARED), MSD: Name: / MOBILEENGINE_JSP (V. 251300), Target=, Type=com.sap.ip.me.core.FrameworkApplicationType) (stack level 1) 
    I SyncEvent Performing com.sap.ip.me.services.os.AgentManager$AgentSyncEventListener on ConversationId MI2853484152454429 
    D Smart Sync framework: entering new context :MI2853484152454429 - MI2853484152454429 
    D Get IPersistenceManager for ConversationID: MI2853484152454429 
    D beginTransaction() called with doWait=false for instance 7068128 
    D PersistenceManagerImpl.beginTransaction():false 
    D PersistenceManagerImpl.get(IQuery):(Type: (IClassDescriptor(Name: meta_topRow)))(Condition: (ALWAYS TRUE))(Order: ((IAttributeDescriptor(Name: downloadOrder)) asc))(Start index: 0)(Max results: -1) 
    D commit() called on instance 7068128 
    D PersistenceManagerImpl.commit() 
    D Opened temporary container file E:Arquivos de programasSAP Mobile Infrastructuresync(SHARED)out     000000j.sync for write (container id = 01131aa74f5ba6c7507e) 
    D Write container header to file (container id = 01131aa74f5ba6c7507e): E:Arquivos de programasSAP Mobile Infrastructuresync(SHARED)outz000003t.sync 
    D Closed container file (container id = 01131aa74f5ba6c7507e) and rename container file to E:Arquivos de programasSAP Mobile Infrastructuresync(SHARED)outi000003t.sync 
    P Created outbound container for user (SHARED) and method AGENT_PARAMETERS 
    P Created outbound container for conversationId MI2853484152454429 / 05DFF40679CABF458D250847C70D06EA (User: (SHARED), MSD: Name: / MOBILEENGINE_JSP (V. 251300), Target=, Type=com.sap.ip.me.core.FrameworkApplicationType) 
    P original context restored 
    D Smart Sync framework: entering new context :5E7C57A41716D64A9329B1C062141786 - FEB7E3AAF420D445AFD89B03E390359B 
    P Thread Thread-10 switched context to MI2853484152454429 / 05DFF40679CABF458D250847C70D06EA (User: (SHARED), MSD: Name: / MOBILEENGINE_JSP (V. 251300), Target=, Type=com.sap.ip.me.core.FrameworkApplicationType) (stack level 1) 
    I SyncEvent Performing com.sap.ip.me.sync.LogSender on ConversationId MI2853484152454429 
    D Smart Sync framework: entering new context :MI2853484152454429 - MI2853484152454429 
    D Get IPersistenceManager for ConversationID: MI2853484152454429 
    D beginTransaction() called with doWait=false for instance 11350939 
    D PersistenceManagerImpl.beginTransaction():false 
    D PersistenceManagerImpl.get(IQuery):(Type: (IClassDescriptor(Name: meta_topRow)))(Condition: (ALWAYS TRUE))(Order: ((IAttributeDescriptor(Name: downloadOrder)) asc))(Start index: 0)(Max results: -1) 
    D commit() called on instance 11350939 
    D PersistenceManagerImpl.commit() 
    D Opened temporary container file E:Arquivos de programasSAP Mobile Infrastructuresync(SHARED)out     000000k.sync for write (container id = 01131aa74f6b6bad7ce5) 
    D Write container header to file (container id = 01131aa74f6b6bad7ce5): E:Arquivos de programasSAP Mobile Infrastructuresync(SHARED)outz000003u.sync 
    D Closed container file (container id = 01131aa74f6b6bad7ce5) and rename container file to E:Arquivos de programasSAP Mobile Infrastructuresync(SHARED)outi000003u.sync 
    P Created outbound container for user (SHARED) and method CENTRAL_TRACING 
    P Created outbound container for conversationId MI2853484152454429 / 05DFF40679CABF458D250847C70D06EA (User: (SHARED), MSD: Name: / MOBILEENGINE_JSP (V. 251300), Target=, Type=com.sap.ip.me.core.FrameworkApplicationType) 
    I AppLog severity: Warning (60) 
    P original context restored 
    D Smart Sync framework: entering new context :5E7C57A41716D64A9329B1C062141786 - FEB7E3AAF420D445AFD89B03E390359B 
    P Thread Thread-10 switched context to MI2853484152454429 / 05DFF40679CABF458D250847C70D06EA (User: (SHARED), MSD: Name: / MOBILEENGINE_JSP (V. 251300), Target=, Type=com.sap.ip.me.core.FrameworkApplicationType) (stack level 1) 
    I SyncEvent Performing com.sap.ip.me.core.RegistryInboundProcessingLog$RegistryInboundProcessingLogSyncEventListener on ConversationId MI2853484152454429 
    D Smart Sync framework: entering new context :MI2853484152454429 - MI2853484152454429 
    D Get IPersistenceManager for ConversationID: MI2853484152454429 
    D beginTransaction() called with doWait=false for instance 3791498 
    D PersistenceManagerImpl.beginTransaction():false 
    D PersistenceManagerImpl.get(IQuery):(Type: (IClassDescriptor(Name: meta_topRow)))(Condition: (ALWAYS TRUE))(Order: ((IAttributeDescriptor(Name: downloadOrder)) asc))(Start index: 0)(Max results: -1) 
    D commit() called on instance 3791498 
    D PersistenceManagerImpl.commit() 
    P original context restored 
    D Smart Sync framework: entering new context :5E7C57A41716D64A9329B1C062141786 - FEB7E3AAF420D445AFD89B03E390359B 
    P Thread Thread-10 switched context to MI2853484152454429 / 05DFF40679CABF458D250847C70D06EA (User: (SHARED), MSD: Name: / MOBILEENGINE_JSP (V. 251300), Target=, Type=com.sap.ip.me.core.FrameworkApplicationType) (stack level 1) 
    I SyncEvent Performing com.sap.ip.me.ccms.LastSuccessfulSyncAlert on ConversationId MI2853484152454429 
    D Smart Sync framework: entering new context :MI2853484152454429 - MI2853484152454429 
    D Get IPersistenceManager for ConversationID: MI2853484152454429 
    D beginTransaction() called with doWait=false for instance 3853415 
    D PersistenceManagerImpl.beginTransaction():false 
    D PersistenceManagerImpl.get(IQuery):(Type: (IClassDescriptor(Name: meta_topRow)))(Condition: (ALWAYS TRUE))(Order: ((IAttributeDescriptor(Name: downloadOrder)) asc))(Start index: 0)(Max results: -1) 
    D commit() called on instance 3853415 
    D PersistenceManagerImpl.commit() 
    P original context restored 
    D Smart Sync framework: entering new context :5E7C57A41716D64A9329B1C062141786 - FEB7E3AAF420D445AFD89B03E390359B 
    P Thread Thread-10 switched context to MI2853484152454429 / 05DFF40679CABF458D250847C70D06EA (User: (SHARED), MSD: Name: / MOBILEENGINE_JSP (V. 251300), Target=, Type=com.sap.ip.me.core.FrameworkApplicationType) (stack level 1) 
    I SyncEvent Performing com.sap.ip.me.smartsync.core.SyncAdapter on ConversationId MI2853484152454429 
    D Smart Sync framework: entering new context :MI2853484152454429 - MI2853484152454429 
    D Get IPersistenceManager for ConversationID: MI2853484152454429 
    D beginTransaction() called with doWait=false for instance 4301103 
    D PersistenceManagerImpl.beginTransaction():false 
    D PersistenceManagerImpl.get(IQuery):(Type: (IClassDescriptor(Name: meta_topRow)))(Condition: (ALWAYS TRUE))(Order: ((IAttributeDescriptor(Name: downloadOrder)) asc))(Start index: 0)(Max results: -1) 
    D commit() called on instance 4301103 
    D PersistenceManagerImpl.commit() 
    D Smart Sync received SyncEvent of type 0 for ConvId MI2853484152454429 
    D Get IPersistenceManager for ConversationID: MI2853484152454429 
    D beginTransaction() called with doWait=false for instance 12406332 
    D PersistenceManagerImpl.beginTransaction():false 
    D Performing Smart Sync outbound processing for Context com.sap.ip.me.smartsync.core.Context:  
    P Begin transaction for outbound containers 
    D GlobalResetProcessing was set to DEFAULT 
    D Conversation id is complete (serverCommunicationId=05DFF40679CABF458D250847C70D06EA clientId=MI2853484152454429) 
    D Added 0 download requests to Generic Sync outbound queue. 
    P Commit transaction for outbound containers 
    P Move containers from transactional outbound folder to outbound folder 
    P Save conversation ids 
    D commit() called on instance 12406332 
    D PersistenceManagerImpl.commit() 
    P original context restored 
    D Smart Sync framework: entering new context :5E7C57A41716D64A9329B1C062141786 - FEB7E3AAF420D445AFD89B03E390359B 
    P Thread Thread-10 switched context to MI2853484152454429 / 05DFF40679CABF458D250847C70D06EA (User: (SHARED), MSD: Name: / MOBILEENGINE_JSP (V. 251300), Target=, Type=com.sap.ip.me.core.FrameworkApplicationType) (stack level 1) 
    I SyncEvent Performing com.sap.ip.me.ccms.AlertManagerImpl on ConversationId MI2853484152454429 
    D Smart Sync framework: entering new context :MI2853484152454429 - MI2853484152454429 
    D Get IPersistenceManager for ConversationID: MI2853484152454429 
    D beginTransaction() called with doWait=false for instance 5994703 
    D PersistenceManagerImpl.beginTransaction():false 
    D PersistenceManagerImpl.get(IQuery):(Type: (IClassDescriptor(Name: meta_topRow)))(Condition: (ALWAYS TRUE))(Order: ((IAttributeDescriptor(Name: downloadOrder)) asc))(Start index: 0)(Max results: -1) 
    D commit() called on instance 5994703 
    D PersistenceManagerImpl.commit() 
    P original context restored 
    D Smart Sync framework: entering new context :5E7C57A41716D64A9329B1C062141786 - FEB7E3AAF420D445AFD89B03E390359B 
    P Repetitive sync is turned off 
    P Synchronization started for user (SHARED) 
    D PackageManager: create package with maximum 2147483647 items 
    A Deletion of outbound container file E:Arquivos de programasSAP Mobile Infrastructuresync(SHARED)outc000000b.sync was successful 
    A Deletion of outbound container file E:Arquivos de programasSAP Mobile Infrastructuresync(SHARED)outc000000c.sync was successful 
    A Deletion of outbound container file E:Arquivos de programasSAP Mobile Infrastructuresync(SHARED)outc000000d.sync was successful 
    A Deletion of outbound container file E:Arquivos de programasSAP Mobile Infrastructuresync(SHARED)outc000000e.sync was successful 
    A Deletion of outbound container file E:Arquivos de programasSAP Mobile Infrastructuresync(SHARED)outc000000f.sync was successful 
    A Deletion of outbound container file E:Arquivos de programasSAP Mobile Infrastructuresync(SHARED)outc000000g.sync was successful 
    D PackageManager: filled package with 6 acknowledge received container(s) 
    D PackageManager: filled package with 6 acknowledge container(s) 
    D Opened container file E:Arquivos de programasSAP Mobile Infrastructuresync(SHARED)outi000003p.sync for read (container id = 01131aa1bb70ee1d19ab) 
    D Closed container file (container id = 01131aa1bb70ee1d19ab) 
    D Opened container file E:Arquivos de programasSAP Mobile Infrastructuresync(SHARED)outi000003q.sync for read (container id = 01131aa1bb9f9e55ab34) 
    D Closed container file (container id = 01131aa1bb9f9e55ab34) 
    D Opened container file E:Arquivos de programasSAP Mobile Infrastructuresync(SHARED)outi000003r.sync for read (container id = 01131aa6d1046f5c286c) 
    D Closed container file (container id = 01131aa6d1046f5c286c) 
    D Opened container file E:Arquivos de programasSAP Mobile Infrastructuresync(SHARED)outi000003s.sync for read (container id = 01131aa74b73790e8280) 
    D Closed container file (container id = 01131aa74b73790e8280) 
    D Opened container file E:Arquivos de programasSAP Mobile Infrastructuresync(SHARED)outi000003t.sync for read (container id = 01131aa74f5ba6c7507e) 
    D Closed container file (container id = 01131aa74f5ba6c7507e) 
    D Opened container file E:Arquivos de programasSAP Mobile Infrastructuresync(SHARED)outi000003u.sync for read (container id = 01131aa74f6b6bad7ce5) 
    D Closed container file (container id = 01131aa74f6b6bad7ce5) 
    D PackageManager: filled package with 25 container items or headers 
    D PackageManager: filled package with 2 notify container(s) 
    D Package file E:Arquivos de programasSAP Mobile Infrastructuresync(SHARED)outpackage.out exists and can be read 
    P Synchronisation started 
    D Begin: Dumping file E:Arquivos de programasSAP Mobile Infrastructuresync(SHARED)outpackage.out 
    MISYNC0x1251300 
    01131a9facc4f3ff1c1c 

    ZMDK_WRP_REC_CREATE 
    FEB7E3AAF420D445AFD89B03E390359B 
    4B4165423827F44A84F8929D1B266450 
    -1 
    NEW_PROTOCOL 

    -1 

    -1 
    -1 
    01131a9facd4138718de 

    CLIENT_ALERT 
    05DFF40679CABF458D250847C70D06EA 
    5EFFDB676600DD4989425DC6908C1FD7 
    -1 
    NEW_PROTOCOL 

    -1 

    -1 
    -1 
    01131a9facd579f88088 

    CENTRAL_TRACING 
    05DFF40679CABF458D250847C70D06EA 
    8345BDCD53425A4598F0D5EB3934A21A 
    -1 
    NEW_PROTOCOL 

    -1 

    -1 
    -1 
    01131a9face47d585e77 

    ZMDK_WRP_REC_CREATE 
    FEB7E3AAF420D445AFD89B03E390359B 
    961D2FDAB8DB0645B0FCE79079D68445 
    -1 
    NEW_PROTOCOL 

    -1 

    -1 
    -1 
    01131a9face58b26dece 

    AGENT_PARAMETERS 
    05DFF40679CABF458D250847C70D06EA 
    F58DAD4DF92CE849B342D8E5DB5D40FF 
    -1 
    NEW_PROTOCOL 

    -1 

    -1 
    -1 
    01131a9face63b9bdf5b 

    AGENT_PARAMETERS 
    05DFF40679CABF458D250847C70D06EA 
    F7F04E8E9AD555499B1A9BD47A39911A 
    -1 
    NEW_PROTOCOL 

    -1 

    -1 
    -1 
    01131a9facf355f91f5e 

    AGENT_PARAMETERS 
    05DFF40679CABF458D250847C70D06EA 
    9545A37371963C4F835A8C6D9959E8F4 
    -1 
    NEW_PROTOCOL 

    -1 

    -1 
    -1 
    01131a9facf49662a55c 

    CLIENT_ALERT 
    05DFF40679CABF458D250847C70D06EA 
    B8148A49CF7FFB43B0F9E9FA37581D04 
    -1 
    NEW_PROTOCOL 

    -1 

    -1 
    -1 
    01131a9fad03c92af324 

    AGENT_PARAMETERS 
    05DFF40679CABF458D250847C70D06EA 
    0A617CC745BFD04C8136916A2F3BB58F 
    -1 
    NEW_PROTOCOL 

    -1 

    -1 
    -1 
    01131a9fad041f058af5 

    CENTRAL_TRACING 
    05DFF40679CABF458D250847C70D06EA 
    887A95CE631C9340B8F3016315862553 
    -1 
    NEW_PROTOCOL 

    -1 

    -1 
    -1 
    01131aa05681e12770d9 

    ZMDK_WRP_REC_CREATE 
    FEB7E3AAF420D445AFD89B03E390359B 
    865529B17C652F4FB0301E4C4FE16D54 
    -1 
    NEW_PROTOCOL 

    -1 

    -1 
    -1 
    01131aa1b6fc736e9b65 

    ZMDK_WRP_REC_CREATE 
    FEB7E3AAF420D445AFD89B03E390359B 
    D31056299A69274CBAB4D4ECD817AD0F 
    -1 
    NEW_PROTOCOL 

    -1 

    -1 
    -1 
     

Maybe you are looking for