Administrators of an Unwired Platform environment have the unique goal of configuring either a development environment or a production environment, so that it supports the mobility pattern being used by the organization.
Unwired Platform currently can use any combination of the following:
- Data Virtualization
– sometimes referred to as Information-as-a-Service or Data-as-a-Service. Data virtualization eases the impediments to enterprise-level data integration by decoupling data from EIS servers or applications and storing it in the Unwired Server cache in the consolidated database (CDB) on the middleware layer of the network architecture. This allows device client users to have "a single source of truth", by allowing multiple applications to interact with the same virtualized layer, which helps to ensure data consistency.
For this pattern, system management goals include:
- Normalizing multiple back-end EIS data sources as relational data
in the Unwired Server CDB cache.
- Configuring and injecting security provider services device to control client access to those data sources.
- Data Publication
–
is the pattern that is used to define how the EIS data that is made available to device clients. To allow device applications to synchronize a slice or subset of data, administrators can create a synchronization group. A synchronization group identifies data that is to be synchronized.
For this pattern, system management goals include:
- Making enterprise data available in the most appropriate form for device applications.
- Data Subscription – is the mechanism that links the client with a publication and a registered Unwired Platform user that allows the data described by the publication to be synchronized.
For this pattern, system management goals include:
- Planning the subscriptions
design to create subset of enterprise data.
- Creating notifications for high-value data changes to increase data currency on the device.
- State Replication
–
In Unwired Platform, only the metadata table is replicated directly from device database to the Unwired Server CDB.
For this pattern, system management goals include:
- Maintaining the integrity of Create-Update-Delete operations by supporting the development approach used. There are two: either set up data as read only and create an application that never changes data programmatically on the device (thereby allowing data only to be updated by a synchronization download); or, allows only user-specific remote data to be modified (for example, a customer’s contact information update should be visible immediately on device even though an operation replay to the enterprise is still pending).
- Operation Replay – Used with the data virtualization pattern, operation replay pattern support both service oriented architectures and ad hoc application integration techniques. In this approach, the mobile application executes an operation on the client side; the mobile infrastructure relays the operation back to the enterprise, and executes the server portion on behalf of the mobile application.
For this pattern, system management goals include:
- Ensuring that developers are able to propagate actions to enterprise for execution in the MBO by maintaining a pool of datasource connections.
- Supporting conflict resolution during synchronization uploads.