about synchronisation group

[Former Member]

Why we use synchronisation group?

What is the main purpose for it???

Kindly help me for this

[Former Member]

This message was moderated.

[midhun_vp]

If you want to synchronize a particular group of MBOs only at a particular time means you can use this.

Ex: In your project if there is a case where a particular data (MBO) you need to sync to the device DB only when the user click on a particular button in the device means you can keep this MBO in a separate sync group and call the below code wherever needed.

TestDB.synchronize("masterData");

masterData is the new sync group created. Hence while synchronizing other MBOs will be untouched and it will not affect the performance.

Typically in big projects there can be 50-100 MBOs it is not a best practice keeping all the MBO is a single sync group and calling synchronize API all the time that will make a call to all these MBOs.

- Midhun VP

[Former Member]

ok  thanks midhun, For particular mbo if we want to synchronise then we can use synchronise group.

Like cache group change detection interval is also used. But what is the main purpose of it?

[Former Member]

Hi,

If you do not want to download the whole data at once & want to sync according to your data selections, then sync group. It will reduce the sync time & also improves the performance of application.

-Shrikant N

[Jitendra_Kansal]

Cache group plays role btwn sup nd backend whereas sync grp between sup nd device.

Cache interval is time when cache will get refreshed.

E.g. you got an mbo with scheduled cache policy nd 10 mins interval.

So every 10 mins, a request ll be going from sup to backend asking about latest data and would replace existing data in sup cdb.

[midhun_vp]

The change detection interval in the Sync group properties determines how frequently unwired server looks for changes to the MBOs and generate push notifications.

Mainly it will be used in the case of push notifications ( Data change notifications from the SAP system ). It would not make any change if you are not using the feature of the push notifications in your application.

- Midhun VP

[Former Member]

It means that syncronisation group detection interval can only used for dcn purposes,???

[Jitendra_Kansal]

Not always... check this

http://infocenter.sybase.com/help/index.jsp?topic=/com.sybase.infocenter.dc01205.0200/doc/html/aba12...

http://infocenter.sybase.com/help/index.jsp?topic=/com.sybase.infocenter.dc01205.0213/doc/html/aba12...

[midhun_vp]

Practically speaking YES. When MBOs in a synchronization group are updated, users subscribed to those synchronization groups receive either a data update or device notification, depending on the type of application they use.

The change detection interval of a sync group decides how often the messages has to be send to the device. In a DCN based application if you need to get the message immediatly to the device when the data changes in backend you need to keep the interval very less.

- Midhun VP

[Former Member]

it is still not clear in my mind.

Firstly i want to ask that there is no policy in synchronization group , so how can we decide is it dcn or not??

is it link with cache group??

In my application i used all type of cache group and give different time slots in change detection interval in synchronziation group. But really i am not able to find difference.

Can u please help me out and and give me a example in brief

[Jitendra_Kansal]

Hi,

Yes there is nothing like policy with sync grp.

Let me give an brief difference

CG & SG are part of mbo package definition and both define how data is preserved on sup CDB and updated at client side.

CG - Collection of mbos that share the same cache policy,  defines how data in sup cdb is refreshed and validated for same mbos.

Defines data refresh behavior for the same mbos.

Interval for cache group indicates the time after a certain time cache will expire/ refresh.  E.g.

On demand – the cache expires after a certain period of time such as 10 minutes. The cache is not updated until a request is made of the cache and the cache has expired. If a request is made of the cache and it is expired, there may be a delay responding to the request while the cache is refreshed.

Scheduled – the cache is refreshed according to a schedule such as 7:00 am, 1:00 pm, or 6:00 pm.

DCN – the cache never expires. Data refresh is triggered by an enterprise information system (EIS) Data Change Notification.

  SG - a collection of MBOs that defines a unit of synchronization so that data and changes are transmitted as a unit to and from the device. Synchronization determines the amount of data (filter), and under what conditions (timing and triggers), mobile business objects (MBOs) upload data to and download data from Unwired Server.

[Former Member]

hi

I need urgent help for this ..

I hav one cache group ie visit group  ie scheduled for 5 mins:Cache Policy

I hav one synchronisation group ie also visit group ie 15 mins,

Data is reflected after 5 mins in cdb

But we sync after 15 mins data is not updated in mobile. Can u pls tell me why it happens.

[Jitendra_Kansal]

Hi Mousumi,

lets say

you have subscribed data in mobile at 10:00 AM

if you request for sync before 10:15 AM , you wouldnt see any updated data on device. Though your request ll go to SUP and SUP in return wont send the updated data. You ll receive data after 10:15 AM only.

If you have set scheduled cache grp time interval as 5 min, it means after each 5 mins request ll go to backend (from sup) asking for the updated data.

Cache grp is for backend and SUP data flow

sync grp is for device and sup data flow.

Rgrds,

Jitendra

[Former Member]

Hi Jitendra,

In your previous reply you have told that change detection interval is used only for DCN.

Then how does it matter that my change detection time is 10 or 15 is i am not using DCN, moreover i am using Ondemand policy. Please explain i am not getting the use of change detection interval in Synchronization Group.

Regards,

Abhishek

[Jitendra_Kansal]

There will not be any use of Change Detection interval if you are using OnDemand cache policy.

Again, this is the interval in which unwired server looks for any updates/changes in cache database (CDB) for that particular mbo(s) of the SG and sends a sync request to the users.

You may elaborate your requirement. Would be good to understand.

Rgrds,

JK