on 09-18-2006 8:40 AM
Hi!
I want to know the Diff between Java sync service and ABAP sync servlet. In suggesting a solution to one of the recent forum topics
It has been asked which sync servie the user is using.I checked my mobileengine.config file and came to know that I am using Java sync servlet.
I want to know what diff it makes if we use ABAp sync servie and what
are the conditions when we need to use it?How dat ais processed in of the service calls
Thank you
hello veera,
functionality-wise they don't differ. they are the same
service gateway for your client and middleware data exchange.
theoritically, synching with the abap sync service would be
more faster that using the java sync servlet. with the
abap sync service, rewrapping of data from i.e. (from http
to rfc via jco) is NOT necessary anymore since the data is
directly sent to the abap stack. (data exchange between
the processes might be done in pipes though).
>How dat ais processed in of the service calls
your client posts or upload the data by calling the abap
sync service and this is performed using the HTTP/s protocol.
this service is responsible for receiving the packages and
concatenating them if necessary then passing them to the
real data processor i.e. the generic sync layer; then from
the generic sync layer to the smartsync layer if the data
is for smartsync...
to enable your client to use the abap sync service you have
to add a parameter into your client's mobile config file.
(please see the help doc for the proper parameter name)
you need to have configured this service prior to using it.
regards
jo
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
the ABAP Sync Service is officially released with MI 25 SP18.
Acutally for a mobile app it is transparent which sync service is used as its just a matter of transport (its also invisible for your apps if WLAN or LAN is used). But as the ABAP stack comes with a bit more stability in terms on memory mgmt etc. you should switch to the ABAP Sync. An other thing is that you ommit another component during your sync cycle (the Java Stack and its RFC call to ABAP) and so an other point of failure. As well Sync Servlet will not be available in upcoming MI Releases (say > NW04 etc.).
Hope this helps...
Rgds THomas
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
84 | |
25 | |
12 | |
9 | |
6 | |
6 | |
5 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.