Innovation World 2013 presentation. A first-class Mobile Enterprise Application Platform (MEAP) needs to address everyone from expert coders to non-programmers. Learn about a new feature set, designed to ease the way mobile apps are developed. Features include a wizard-guided project initiation, an easy-to-use drag-and-drop interface and a native-like preview in the Phoney simulator, among other enhancements. The session also covers integration challenges and explains why APIs are the best practice to securely expose back-end data to enterprise mobile apps. Get the latest information on the webMethods Mobile Suite strategy and the long-term mobile strategy of Software AG.
Speakers: Matt Green VP, Product Management & Product Marketing, Software AG
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Development Environment: Develop Mobile Apps for multiple platforms at one
...
Cross-platform build and test environment
Central App Store for internal and external users
Central Device Management and custom policies deployment
Statistics on usage of services and applications
Secure mobile app access into corporate systems (e.g. CRM, ERP)
Innovation World 2013 : Mobile Suite
Presenter
Presentation Notes
Mobile Administrator added to Mobile Designer = became a MEAP: covering the mobile app lifecycle, from developing, to deploying, integrating and managing mobile apps
Now we would like to show you how a typical mobile customer architecture looks like. Usually a mobile customer architecture consists of two different stages: The Runtime environment and the Designtime environment. The strengths of our mobile suite lies within the design-time environment. With the development tool Mobile Designer, developers can generate applications that run cross-platform, which means these are applications which are not designed for one specific application but for many at the same time. This development place in an Ecplise environment with Java. For a mature Java developer (who is new to mobile) it will be pretty easy to get into mobile development in this familiar environment. One problem in developing mobile apps is usually to build apps for multiple mobile platforms (like iOS, Windows Phone, Android etc). This is a problem because building an app for iOS for example, the developer needs an apple hardware. Not everyone has apple iphone at hand. Therefore developers can use Mobile Administrator, which helps with its “Mobile Build + Test Management” component to build applications for a specific platform. This means, the developer can tell Mobile Administrator to build a new version of the application for the following platforms: iOS; Android, Win, BES. Mobile Administrator then consults its build nodes. A Build Node is a machine that can build an application for a specific platform. So there can be an apple machine that can build an IOS application or a PC that can build for win / android. As these build notes are known to Mobile Administrator, Mobile Administrator exactly know which build node to ask for building the app for the needed target- platform. Mobile Administrator Build Node generates the build and sends the results back to Mobile Administrator. From here, the build application can be deployed to the mobile devices, which is then done via the mobile application management. Mobile Application Management manages all apps that are available in my company. As Mobile Administrator also knows all mobile devices via Mobile Device Management, the overall mobile lifecycle of design, build, deploy and test can be handles with Mobile Administrator’s design time component. In the runtime environment all managed mobile devices are accessible. The cross-compiled application runs on the mobile device, including its different versions. The runtime environment secures Mobile Access Management, together with mobile gateways, the runtime environment makes sure that accessing backend systems runs securely. Of course we recommend to access to use our enterprise service bus (ESB) to receive a clear governance which application and which device get granted access to my systems and devices,