The
Sybase Unwired Platform DOE option consolidates all mobile data from back-end SAP systems,
then uses rules to determine mobile distribution. This approach allows distribution rules to
evolve separately from the content model and for different distribution rule sets to be used
with the same content model.
The
Sybase Unwired Platform DOE deployment option allows the system designer to model and
consolidate SAP mobile content in the middle tier and separately layer distribution
rules over this content. This approach allows distribution rules to evolve separately
from the content model and for different distribution rule sets to be used with the same
content model. Even customers can change the rules without rewriting client or back-end
code, after actively deploying
applications.
The technology to enable this behavior is built directly into the
NetWeaver stack and is therefore best suited to SAP-only implementations or where
third-party back-end integration is already provided through NetWeaver. This method
specifies BAPI CRUD interfaces to adapt back-end suite datasources to the middleware
data consolidation area.
The Sybase Unwired Platform DOE option consolidates all mobile data from
the back-end SAP system, then uses rules to determine mobile distribution. The rules are
fired on these events:
- New device is registered – initial receiver determination
- Back-end data or client data changes because of user updates or
batch updates – staging are update
- Business change resulting in change of user subscriptions, for
example, moving from region A to region B – device realignment
DOE-based applications are well suited to
these situations:
- The SAP back end cannot directly support mobile queries, or
mobile queries place an unacceptable load on the back end.
- The design dictates that the data distribution take place in the
middleware.
- A scenario requires flexibility in adapting to different
back-end interfaces or versions without changing the mobile model.
- A scenario requires flexibility in changing the distribution
rules without changing the mobile model and mobile application.
- A scenario requires a centralized in-box for error resolution by
an administrator.
- Multiple customized SAP back ends must work with the same mobile
application, for example, if the same mobile application is resold to multiple
customers who use different distribution rules.
- A mobile solution is working primarily against the SAP back
end.
- Customized conflict resolution is required within the mobile
middleware, rather than in the back end.