Enterprise Mobility

Extending your enterprise business processes, data, and information away from the office entails many technical challenges.

Each challenge presents complexity to the IT organization. These complexities may include, but not be limited to, for example, lack of integrated solutions, heavy upfront costs for large-scale customization requirements, and the lack of repeatable development and deployment models.

Sybase Unwired Platform meets those challenges by hiding system complexity while efficiently and flexibly handling complex mobility issues. Unwired Platform provides many opportunities for productivity gains through a well-defined life cycle, repeatable use of existing investments, and mobility knowledge.

• Data Mobility
  Businesses increasingly need to connect people and data inside and outside the bricks and morter of their corporate offices.
• Administration and Development Coordination
  Developers play an important role in the design of the mobile application. But administrators control other important behaviors after a package is deployed. Understanding the dynamic between these roles is critical in a mobile environment, especially with respects to data updates.
• Data Mobility Patterns
  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.
• Network Availability Models
  Developers and administrators must consider availability of a network connection to device application users when designing and developing mobile applications.
• Synchronization Methods
  Developers can use either replication-based or message-based synchronization to move data and transactions between device application clients and Unwired Server.
• Data Synchronization and Data Refresh
  Since dataset variations occur between multiple clients and the enterprise information system (EIS) data to which mobile business object (MBO) data is bound, synchronization is required to reconcile differences and bring each client into coherence with the working copy of the EIS data maintained in the consolidated database (CDB), before writing updates back to the EIS.