Run Mobile

We often say we have to consider differently when building a complex mobile application. But what is complex? In general complexity in a mobile application comes from: Asynchronous communication capabilities. Orchestration of many stateless service calls that are subject to a single transaction semantics. Example: Create a ServiceOrder with its Notifications. On device persistency and in particular keeping object state consistent with the server state. On device business logic such as a Pricing or a Configuration Engine. The ability to handle large data load. Example: equipments, material, products. Pushing data and updates to the mobile application. Support for complex data distribution rules (from server to device). Scalability in number of devices, requests, and data volume.

NetWeaver Gateway  is a middleware for request/response Communication is request/response, stateless, un-buffered, http-based. Gateway exposes OData services for easy consumption. Routes requests 1:1 and changes protocol from http to RFC. Provides Push/Notification/Subscription capabilities for events and workflow. SUP 2.1.x  is a reverse proxy (not a MW) for online applications Connects devices from internet to intranet and routes requests to Gateway. Provides User Handling & Security (guards the Gateway). Leverages Push/Notification/Subscription (scalability of push for high volumes, planned). In contrast to Gateway no content development happens in this layer.