May 29, 2013 3 minute read

Introduction to MobiLink Synchronization

Dear All,

OBJECTIVE:

This Document explains how we can access MobiLink Server and do monitoring using it. what are the synchronization properties.

REQUIREMENT:

Tool: SUP 2.2 SP 02

Procedure:

MobiLink Synchronization.

This MobiLink Synchronization is a component of SQL Anywhere. MobiLink system is a synchronization based system which allows two ways synchronizations. This happens between CDB (Consolodated database) and many remote databases.(client/device local database).

where CDB: can be one of the ODBC databases. holds the master copy of all the data.

and Remote database: could be ULDB (UltraLite database)

MobiLink Monitor:

this is a tool that provides details about sync performance. After connecting to MobiLink server, MobiLink Monitor starts to gather information about all sync that occur in a particular session.

we can view data in graphical or tabular form in the MobiLink Monitor Interface.

Connecting To MobiLink Server:

Steps:

Open Command prompt.
go to c:\sybase\unwiredPlatform\Servers\SQLAnywhere12\BIN64
Run mluser -c “DSN=default-cdb;uid=dba;pwd=sql” -u testuser -p password

Where DSN = Database Source name

uid = database user id (by default it is “dba”)

pwd = password (by default it is “sql”)

-u testuser = MoblLink Monitoring user that we are creating (could be anything)

-p password = MoblLink Monitoring password that we are creating (could be anything)

you would be see a message saying Inserted User: testuser (see below snapshot)

/wp-content/uploads/2013/05/1_223360.png

4. Run cd..

5. cd BIN32

6. mlmon.exe

provide required information. select Protocol as HTTP and port as 2480 Click on OK.

whenever there is any sync request from remote database (device), you will see few flowing lines of different color segments. Double click in between.

a new window will pop up.

this window will provide you every information for that particular sync for a particular user.

Following columns appear by default:

Overall Synchronization Statistics:

Sync: this is an identity for each sync request assigned by MobiLink server.
Remote ID: identity of device database. (remote DB)
User: name of user who has requested for the sync (e.g. user@Domain)
Version: domain_packagename
Start time: this is the duration (date and time) when MobiLink server started Sync.
End time: time taken to complete that sync
Active: sync status
Download ack:type of download ack (could be none, blocking or non-blocking)

Synchronization Phase Statistics:

Synchronization Request: total time (in sec) for MobiLink to receive the data from device.
Receive Upload: this is the time between creating n/w connection (between device and mobiLink server), upto receiving the first bytes of the upload stream.
Get DB Worker: time taken for acquiring a free database worker for that particualr sync request.
Connect: time taken by a DB worker to make a database connection.
Authenticate User: time (sec) taken by MobiLink to validate sync request, authenticate user and its password.
Begin Synchronization: time in sec to run begin_sync script
Apply Upload: time taken to apply the upload to CDB. this is time between begin_upload script and end_upload script.
Prepare for download: time in sec to run prepare_for_download script
Fetch Download: time taken to download the data. time between begin_download script and end_download script
End Synchronization: time taken to run end_synchronization script.

Disconnecting From MobiLink Server:

if you want to disconnect from MobiLink Server, you just need to run below commnand.

cd c:\sybase\unwiredplatform\Servers\SQLAnywhere12\BIN64>

mluser -c “DSN=default-cdb;uid=dba;pwd=sql” -d -u testuser -p password

I hope this blog will help you to understand different terms related to MobiLink Monitoing.

Your comments/suggestions are most welcome.

Regards,

Jitendra

14 Comments

You must be Logged on to comment or reply to a post.

Former Member

May 30, 2013 at 11:21 am

Another good one.

John Kalaiyarasan

July 18, 2013 at 5:32 am

Hi jitendra kumar kansal

Actually i worked on Core-ABAP now after gone through your post i'm very interesting to learn something about new technologies. I'm totally new for this so can you please advise me or share the document on related to mobi apps.

Thanks & Regards,

John.

Jitendra Kansal

Blog Post Author

July 19, 2013 at 4:47 am

Hi John,

i suggest you to follow http://scn.sap.com/community/developer-center/mobility-platform

http://scn.sap.com/community/mobile

Former Member

December 17, 2014 at 9:37 am

Hi Jitendra,

Could you please suggestr how to work on SQL Monitor in SMP 2.3.3 version?

SQL Anywhere is not installed seperately and we are unable to start that.

-Mandar k.

Jitendra Kansal

Blog Post Author

December 17, 2014 at 10:24 am

Kulkarni Mandar

If you have not installed it separately then it has got installed along with SMP 2.3

Are you not able to find this path c:\sybase\unwiredPlatform\Servers\SQLAnywhere12\BIN64 ?

Regards,

Former Member

December 17, 2014 at 10:39 am

Hi,

Thanks you forthe reply. I could locate the path but not the "mlmon" application.

What shall we use to monitor the SQL Anywhere 16.0 database?

-Mandar K.

Former Member

January 15, 2015 at 9:56 am

We are trying to replicate 16 x Sybase Anywhere (9.2) Databases to one IQ (16) Database ..

Is it possible ? Attempt were shut down by the development team because of the the (Version) matters .."Don't even wanted to try "

We are unable to Upgrade these DataBases as they are legacy to be replace .. Soon

HANA Remote Source Only support IQ / ASE from 15.4 ..

Warmest Regards

Ian S

Antonio Rodriguez

May 13, 2016 at 8:14 am

Hi Jitendra,

could clarify me which is the task where sup send to sap the operatio, or instance create sales order.

i understand that the task is Fetch Download, is it correct? and also fetch download is when sup process query to get data to send ipad?

Synchronization Request: total time (in sec) for MobiLink to receive the data from device.
Receive Upload: this is the time between creating n/w connection (between device and mobiLink server), upto receiving the first bytes of the upload stream.
Get DB Worker: time taken for acquiring a free database worker for that particualr sync request.
Connect: time taken by a DB worker to make a database connection.
Authenticate User: time (sec) taken by MobiLink to validate sync request, authenticate user and its password.
Begin Synchronization: time in sec to run begin_sync script
Apply Upload: time taken to apply the upload to CDB. this is time between begin_upload script and end_upload script.
Prepare for download: time in sec to run prepare_for_download script
Fetch Download: time taken to download the data. time between begin_download script and end_download script
End Synchronization: time taken to run end_synchronization script.

thanks.

Antonio

Andy Silvey

April 4, 2018 at 12:49 pm

Hi Jitendra,

great blog.

Do you know does SAP have any RoadMap where they are showing for example the RoadMap for MobiLink, and the comparison of the RoadMap for SAP Mobile Platform compared to MobiLink ?

We are looking at the two and I want to make sure the one we choose is in harmony with SAP's plans.

Thanks and best regards,

Andy.

Jitendra Kansal

Blog Post Author

April 9, 2018 at 8:58 am

Andy Silvey

There is no roadmap as such for MobiLink . For SMP roadmap, you may have already checked out future plan https://www.sap.com/products/roadmaps.html?sort=title_asc#pdf-asset=82cb5e0d-e77c-0010-82c7-eda71af511fa&page=23

On other side, I would also suggest you to check https://blogs.sap.com/2018/01/31/the-future-of-sap-mobile-platform/ if not done already.

Regards

Andy Silvey

April 11, 2018 at 2:25 pm

Hi Jitendra,

thanks, that's the point the RoadMap for SMP is clear, but what about MobiLink, have SAP published the RoadMap for Mobilink anywhere ?

If we consider to implement Mobilink how can be sure it won't be retired next year ?

Any ideas.

Best regards,

Andy.

Jitendra Kansal

Blog Post Author

April 11, 2018 at 3:21 pm

Andy Silvey

Hi Andy,

I totally understand what you ask for. I have reached out to another colleague for your query, will update you once i hear back.

Regards

Tom Slee

April 11, 2018 at 3:40 pm

Hi Andy Silvey ,

I have a few data points: I hope they help.

MobiLink is a component of the SAP SQL Anywhere product. The SQL Anywhere roadmap is available at the public roadmaps page: enter "SQL Anywhere" into the search field.
If you are looking for guarantees, you can go to the SAP Product Availability Matrix and search for SQL Anywhere 17 (the most recent version): you will see the current "end of mainstream maintenance" for that release is 31.12.2025.
Finally, MobiLink is a mature technology, but it is being used as infrastructure for newer SAP products that build on it. The SAP Mobile Platform is one such product, which uses MobiLink for its offline capabilities. Another is SAP Edge Services, which bases its edge persistence service on MobiLink.

Andy Silvey

April 12, 2018 at 9:29 am

Hi Tom,

thank you that's helpful to me and I am sure others.

That has answered most of the question, the other part is the classic crystal ball question, for how many years are SAP planning to commit to using Mobilink in the SMP, and if we implement it will we be in a situation this time next year where SAP announce a new technology direction for SMP.

Best regards,

Andy.

Introduction to MobiLink Synchronization

Assigned Tags