cancel
Showing results for 
Search instead for 
Did you mean: 

Mobile Gateway 1.0 Architecture

Former Member
0 Kudos

All,

I am interested to understand the Mobile Gateway 1.0 Architecture as to how it enables PUSH Protocol for BES.

As per my understanding we need to PUSH data to a BES for it being able to distribute the same to blackberry devices. However the normal SAP Windows Client does a pull from the DOE Queue. So I would assume Mobile Gateway as a middleware that will extract data from DOE queue and push it to the BES by calling its Web Service.

If anyone can send me links/document OR explain how it works and the development around the same, it will be really helpful.

Regards,

Shubham

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi,

Mobile gateway 1.0 mainly constitutes 2 components , a webservices channel over DOE and the CRM contents (design time objects required for mobilizing CRM Sales application modeled in DOE).

Basically this makes complete use of the multi channel access capability exposed by DOE and is an effort to remove the tight coupling of DOE with the default mobile client shipped from SAP.

The CFS channel (Used by Mobile client shipped from SAP) could be seen as default channel from DOE.

With Mobile gateway 1.0 add-on over DOE, a new webservices eventing channel is shipped that exposes the data objects as webservices for easy consumption by mobile clients.

This involves a designtime that is used to model design time objects called Entity Set Definition for Mobile Applications(ESDMA) in other words collection of data objects and generate services around ESDMA and data objects involved part of ESDMA.

WSDLs will be generated per dataobject / ESDMA with services like read operations, CRUD operations etc .These bundles could be downloaded and become the base for application development that consumes these web services.

In summary DOE is the middleware (BE>DOE>Mobile client/ another server )and normal message processing happens as usual in DOE but instead of default channel processing(push till outbound queue), it is pushed to the device endpoint (url of the receiver) via the webservices channel as notifications from DOE. Sameway inbound messages reaches DOE and in turn BE via the webservices exposed in this channel.

For CRM Mobile sales application, there is a blackberry sales client that is already in rampup mode.

Regards,

Liji

Former Member
0 Kudos

Hi Liji,

Thanks for a prompt response. I need to understand this point

"it is pushed to the device endpoint (url of the receiver) via the webservices channel as notifications from DOE"

Does this mean that the DOE triggers an event to some external Device/Server that data is ready for download and the device calls the DOE WebService to download the same?

Regards,

Shubham

Former Member
0 Kudos

Basically the payload (data) itself is pushed to the endpoint (url of the device/ receiving server) in the form of notification services. In other words DOE will be the service consumer incase of push of data.The generated WSDLs contains all the details of these notification services as well so that client application can use these details inorder to consume this payload.

Device creation for the first time is initiated by the receiver by invoking a subscribe service exposed.

From then on the payload eligible for that receiver is pushed till the url that is specified during the subscribe request from that device.

In case of BB sales client, payload is pushed till BES and BES takes care of forwarding the payload to actual blackberry devices.

Regards,

Liji

Former Member
0 Kudos

Plainly put things are as follows:

there is a native implementation for webservices where in both the DOE and BES can act as consumer and producer. There are some operation where DOE will act as consumer and BES as producer; and others where DOE act as producer and BES as consumer. The technical contract is identified by the wsdls.

The cases where DOE pushes content to BES, DOE acts as webservice consumer for the operations implemented on BES.

The case when device uploads some changes or make some other request; BES acts as web service consumer and DOE as service provider.

At the payload level, its soap payload with soap action identifying what operation to serve or request.

regards

pradeep

rohith_deraje
Employee
Employee
0 Kudos

One simple example in addition to Pradeeps explanation.

Consider the below two operations.

-->Operations:Device Registration

Provider: DOE

Import: Physical ID and ESDMA details.

Return: Registration status with device details

-->Operation: BulkMessage( To process the data sent from DOE)

Provider: BES

Import: Bulk data

Return: None

1.BES --> Calls the registration Operation with physical ID and ESDMA details

2.DOE --> In response to above call, creates a new Device, register it and assign ESDMA. Reply to BES with the registration status.

3.DOE --> Data calculation for the device is triggered. Once the data is ready it calls the Bulk message operation pushing the data.

4.BES --> Process the data and distributes the data to the Black berry devices.

Regards

Rohith

Former Member
0 Kudos

Hi,

Does anyone know if this Mobile Gateway will be available for non CRM scenarios?

As far as I know, the only way to get it right now is to use SAP CRM 2007/7.0.

Regards,

Pierre

Former Member
0 Kudos

Hi,

Interesting question. From my understanding there's no reason why you couldn't write your own BAPI wrappers for non-SAP scenarios and expose these on MGW. Does anyone disagree?

Regards,

John

VikasLamba
Advisor
Advisor
0 Kudos

Yes, I disagree.

Reason being, just publishing a set of BAPI's and developing data objects and ESDMA on top of it is not sufficient to build the application. The WSDL files that are generated are operations exposed by DOE on top of the data objects and there are strict semantics which one needs to follow in order to use these operations affectively.

What RIM or Sybase do is essentially abstract this semntic logic and expose only the business layer APIs for application building. But as of now neither RIM or Sybase or any other ISV provides a platform where you can import an ESDMA bundle in the deveopment environment and it provides you with a library that can allow you to code your own business layer logic.

Thus essentially you will need to write the application + DOE to device communication piece (which is ideally common for all apps) together and then deploy it on the devices.

Such applications would also not have any support from any middleware for deployment or device administration too.

Regards,

Vikas

VikasLamba
Advisor
Advisor
0 Kudos

Hi Pierre,

SAP is also delivering some applications in ERP domain for Mobile Time and Travel and and workflow management. But they will be available in a couple of months. Right now it is a little difficult to develop applications from scracth as we do not have any client side framework available which can host the business applications on the mobile devices and provide a runtime to communicate to DOE and allowing the ISV to write their own applications that can be deployed on this framework on any platform.

Sybase is in the process of developing such framework and release a few applications like CRM Sales, MIB etc in near future. Then hopefully it will open up avenues for 3rd party integraters to deveop their own apps too.

Regards,

Vikas Lamba

Answers (1)

Answers (1)

sivasatyaprasad_yerra
Active Contributor
0 Kudos

Check this URL:

[https://websmp209.sap-ag.de/~sapidb/011000358700000450552009E]