cancel
Showing results for 
Search instead for 
Did you mean: 

Basics of MBO

Former Member
0 Kudos

Dear All,

I am new to MBO's

The following are the questions from my side:

1) Where do we install MBO in the unwired server or the mobile Device ??

2) Suppose there are 10 Android devices, 10 Blackberry devices & 10 Windows Mobile devices registered with the Unwired server, how many MBO's are

      required to communicate with all 30 devices ??

3) If the MBO's are installed on the unwired server, wht type of device applications(i.e if android device than it is .apk file needs to be installed on the

    device) are required ?

3) How to read all the contacts from the mobile devices and store the same in the EIS tier(database), how exactly this is possible ??

Please let me know your inputs

Thanks

Mano

Accepted Solutions (1)

Accepted Solutions (1)

hofmann
Active Contributor
0 Kudos

1) a MBO is a set of scripts for SUP and for the device the generated code. On the device the MBO will be shown as a database and code to access the data, on the server as database tables in the Cache Database (CDB)

2) 1 MBO.

3) see 1)

4) create an MBO for user storage, read the users from the device, save them to the device MBO and sync the data.

Answers (4)

Answers (4)

Former Member
0 Kudos

Yo Mano !!

All of the above are Correct !

rakshit_doshi
Active Contributor
0 Kudos

Hi Mano,

Seems you are very new to SUP.

Starting from the basics an MBO is a mobile business object. We prepare MBO from different backend system like the SAP Backend datasource, Or SQL or Oracle or Webservice etc. If you ever had a change to see the backend data source table its the same as MBO. We pull the table in the workspace with all it input and output parameters, define certain properties for it etc.

Even if you have a 1000 device the structure of MBO doesnt change.

The whole cycle is like Identifying the business case--> Preparing the MBO--> Deploying the MBO on the unwired Server--> Generating the Code (if you want to build a native application) for respective platform.

Only if you are developing a workflow application you need to install the respective HybridWebContainer files on the device. like apk for android etc. which is there in the Sybase installation directory.

Hope this provides some help.

Thanks,

Former Member
0 Kudos

Hi Doshi,

Thanks for the update.......

what i understand from your point there two types of apps can be developed for mobile devices

Workflow applications and native appications of the device.

can u differentiate between the two ??

In what possible situations we recommend the workflow/native apps ??

Thanks

mano

hofmann
Active Contributor
0 Kudos

There is quite some content here on SCN and on the Sybase page explaining MBOs and how you can use SUP for app development, and when to use hybrid or native apps.

Jitendra_Kansal
Product and Topic Expert
Product and Topic Expert
0 Kudos

HI Mano,

for your info::

Device Application Types

Sybase Unwired Platform supports
two mobile business object-based application types:native application and
Hybrid Web Container-based mobile workflow.

Native Application

The native application model enables the developer to generate Object API code from mobile business objects, and write custom code (C#, Java, or Objective-C, depending on the platform) to create a device application.
In native application development, the application is based on
compiled code that is specific to a particular mobile operating system. Native application development provides the most flexibility in terms of leveraging the device services, but each application must be provisioned individually after being compiled, even for minor changes or updates. Native applications support offline capabilities, leveraging synchronization.

Hybrid Web container-based mobile workflow

The Hybrid Web Container offers a fast and simple way to build applications that support

business processes, such as approvals and requests. With the Hybrid Web Container-based

development, the server-side of the application is metadata-driven and the client-side of the application is a fully generated Web application package. This mobile workflow package of platform-independent HTML,JavaScript and CSS resources can be deployed automatically to the Container, a native application on the device, without writing any code. The HybridWeb Container hosts an embedded browser and launches the individual mobile workflow applications. The workflows are assigned to users by administrators. Once assigned, those workflows can be initiated by the user (client-initiated) or automatically triggered as a result of a back-end event that is sent to the Unwired Server as a data change notification request (server-initiated).

hofmann
Active Contributor
0 Kudos

Pointing to the documentation is OK, but copy & pasting entire paragraphs without giving the source as a reference? (http://infocenter.sybase.com/help/index.jsp?topic=/com.sybase.infocenter.dc01283.0213/doc/html/koh13...)

I suggest that Mano Kir first reads the documentation and than comes back in case questions were not answered by the documentation.

former_member184221
Contributor
0 Kudos

Once you have understood the basic MBO concepts as Tobias has explained above i.e.

a) On the server side the MBO consists of a set of scripts and a database table in the Cache Database. if you have a BB, Android and iOS mobile using this server side MBO it does not change.

b) On the Client side (If a replication MBO is built) it consists in a database (Ultralite or SQlite) and code to access this data and synchronise with the SUP server. The code for BB, Android and iOS on the client side will be different but functionally the same.

Here is an excellent video on MBO best practices which gives you more detail on whats going on ...

http://www.youtube.com/watch?v=E3mjk-IAh0Y

Former Member
0 Kudos

Mano,

You can find out more about MBOs from the SUP documentation.

The Fundamentals document gives an overview of the system, and the Mobile Data Models: Using Mobile Business Objects provides additional details and best practices.

The SUP 2.1 ESD#3 documentation is here: http://dcx.sybase.com/index.html#sup0213/en/com.sybase.infocenter.pubs.docset-SUP-2.1.3/doc/html/tit...