Skip to Content

Why allow Custom Clients to Integrate with SAP NetWeaver Mobile?

A lot of mobile devices are available in the market; devices based on numerous platforms such as Windows Mobile, RIM, Symbian, Linux, Palm, iPhone, Android, and so on which provide a rich native user experience. In the field of business, customers and partners must be able to choose any device, and be able to access their enterprise data.

SAP NetWeaver Mobile is the platform for SAP’s enterprise mobility. And to allow customers and partners to choose any client technology that suits their business requirements, we have opened-up the DOE, so allowing you to integrate any client technology with SAP NetWeaver Mobile. This enables any client technology to leverage middleware capabilities such as data distribution, data integrity, device management, scalability and so on. 

Ways to Integrate a Custom Client

There are two ways you can integrate your custom client:

  1. Using SAP’s Sync Layer – We have developed a sync layer on the DOE that is used by the standard SAP NetWeaver Mobile client. The same sync layer can be consumed by the custom client. In this case, the custom client must communicate with the standards required by the DOE.
  2. Using your custom channel – If you want to communicate using your own standards, then you can create your own “channel” in the DOE. Early April, we shall release a document that describes steps to create a custom channel.

All the APIs that you require to communicate with SAP’s Sync Layer are exposed for the developers. This is what you have to do to integrate the custom client:

  1. Create an HTTP interface on the DOE. An HTTP URL is then available for your custom client to communicate with the DOE.
  2. In the interface, you must process the messages from the client and call the corresponding APIs. For example, if you get a request from the client to download messages from the DOE, you have to call the GET_MESSAGE API of the DOE.

Documentation

The document that describes how to use the Sync Layer is now available in SDN. You can download the guide here.

(A special thanks to Rajeswara S Rao, Gunashekar M, and Vikas Lamba of the SAP NetWeaver Mobile team for their efforts towards preparing the guide)

So, try creating your own custom client – using J2ME, Microsoft .NET, or any client technology and try communicating with SAP NetWeaver Mobile.

In early April, we shall provide you documentation for creating a custom channel.

To report this post you need to login first.

2 Comments

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

  1. Ludovic Fernandez
    Thanks to SAP for your blog and especially this documentation. However, could you please let me know if I am right or not? implementing the synch layer within a custom client consists of exchanging all information with the DOE then managing locally the SQL Lite Database and not, exchanging events with the synch layer in order to let the DB both on server and client sides to synchronize themselves.
    (0) 
    1. Sujit Hemachandran Post author
      Hi Ludovic,

      Yes, you are right. Implementing the sync layer here means exchanging data between the custom client and the DOE. There are no events that “automatically” synchronize your client database and the server database.

      The custom client database (eg, SQL Lite) must be managed by your own logic. Whenever you exchange data, you must ensure that the messages (C/U/D) are in the format expected by the DOE.

      How you create the messages from the local database depends totally upon your logic. So, in short – local database management must be handled by the custom client.

      (0) 

Leave a Reply