Movilizer Detail Presentation UnderstandIT V17

The Movilizer in detail Understanding It

Alberto Zamora, Consultant Oktober 2013

MOVILIZER

IN DETAIL

6 Capabilities to RUN mobile apps

5 Capabilities to DEPLOY mobile apps

4 Capabilities to BUILD mobile apps

3 Movilizer components & architecture

2 Movilizer capabilities overview

7 Build or use Out of the box apps

8 Embracing standard and openess

1 Understanding the requirements

MOVILIZER

IN DETAIL









Understanding the requirements Top technology drivers

INNOVATION

Become more Agile

REDUCE COSTS

Total Cost of Ownership

INCREASE REVENUE

Adoption of enterprise systems

Understanding the requirements The Movilizer Solution

BUILD

FASTER

DEPLOY

FASTER

RUN

FASTER

INNOVATION

Become more Agile

REDUCE COSTS

Total Cost of Ownership

INCREASE USER

Adoption of enterprise systems

MOVILIZER

IN DETAIL









Movilizer capabilities overview The platform to build, deploy and run enterprise apps faster

Movilizer capabilities overview Key question

What type of mobile apps can I

build, deploy and run with the

Movilizer?

Movilizer capabilities overview Key question

The Movilizer Enterprise Mobility Platform

combines the most powerful tools and

techniques currently available to build,

deploy and run any kind of enterprise

mobile apps.

by mobile architecture

by development approach

Movilizer capabilities overview type of mobile apps that you can build with the Movilizer

HTML5 Data Centric Template based

hybrid apps web apps native apps

The different types of mobile apps that you can build with the Movilizer can be classified as follow:

by business scenario

Movilizer capabilities overview Supporting various types of apps by business scenario

Movilizer capabilities overview Supporting various types of apps by backend integration(II)

HTML5

Data centric

Template based

Movilizer capabilities overview Supporting various types of apps by backend integration(III)

2007 Movilizer was born as a

pure template based

approach

2010 Introduction of the

master data concept

which adds a Data

Centric approach.

2011 Introduction of the Web

Viewer smart container

to support HTML5 and

Hybrid apps approach.

Low TCO

Multi-device

User experienceFast to build

Easy to integrate

Movilizer capabilities overview Supporting various types of apps by backend integration(IV)

Movilizer today = HTML5 + Data Centric + Template based

Today

Movilizer supports all

advantages of those

three development

approaches, and all

using a single

technology platform

with a uniform

architecture.

Native Hybrid HTML 5

*Native Movelets are

always cross-platform

(not like usual native

code)

Movilizer App today = Native +

Hybrid + HTML5 screens

Movilizer capabilities overview Supporting various types of apps by type of code on device

MOVILIZER

IN DETAIL









Movilizer Components & Architecture 0 new infrastructure Architecture Components

No middleware required

No mobile VPNs or firewalls

Plug & Play your business connector of choice

Up and running in your landscape in hours.

You can download and test all our connectors for free at movilizer.com.

Movilizer Components & Architecture The Movilizer Client App

The Movilizer Client acts as a Secure App Container.

On installation the Movilizer Client is empty

After registration, the user gets all the assigned Movelets

The Movilizer Client works offline and online. It can

also work completely offline (user synchronising only at

the beginning and the end of the day)

The Movilizer Client is available for 9 different platforms: iOS, Android, Blackberry,

Windows Mobile, Windows Phone 8, Windows 8 (including RT), Laptop (Win32, Linux and

MacOS), J2ME (for feature phones) and web browser client.

The Movilizer Client behaves the same for any device. Movelets are built once and run

without change in all clients.

Movilizer Movelets are run as native code on each of the 9 platforms and support also

HTML5.

The Movilizer Client supports common functionality such as sync, encryption of

passwords, resetting apps these are the client framework settings and can be controlled dynamically using the Movilizer Expression Language

Movilizer Components & Architecture The Movilizer Cloud (I)

1. The Movilizer Cloud provides a security layer to

enable any device, known or unknown, (e.g. BYoD)

to connect securely with your business systems.

Users and Movilizer Clients are identified,

authenticated and monitored. Any exchanged data

structures are validated, virus checked, obfuscated,

encrypted and decrypted. Business (source) systems

are authenticated, certificates verified, and any

unexpected behaviours in the web service monitored

External attack patterns are automatically identified

and neutralized

The Movilizer Cloud is a multi-tenant and hosted middleware reachable via Web

Services which fulfils 7 vital for enterprise grade mobile apps:

2. In the Movilizer Cloud you find the SmartSync engine, which ensures that the app can

run offline / online (via smart queue management), master data is replicated, assigned

Movelets are pushed and that data is transformed from XML into compressed binaries to

adapt to low bandwidth environments.

Movilizer Components & Architecture The Movilizer Cloud (II)

3. The Movilizer Cloud provides an orchestration layer to ensure that Movelets and

master data coming from different systems can be mashed up into the Movilizer Client.

This includes recognising Movelet and Inter-Movelet dependencies and packaging the

relevant data for each mobile user, thus ensuring data consistency at any time on the

Movilizer Client.

4. The Movilizer Cloud provides Movelet and user monitoring, analytics and error

handling across many heterogeneous back-end systems connected to your apps.

5. The Movilizer Cloud Portal provides a Backend as a Service (BaaS) which is typically

used to gain agility and include in your mobile apps functionalities which do not exist in

your backend systems. (e.g. defining mobile forms, uploading multi-media contents

etc.).

6. The Movilizer Cloud ensures out of the box and instantaneous massive scalability of your mobile apps, so that thousands of concurrent users and peak usage can be

handled without stressing your existing backend systems and without any new

infrastructure on the customer side. This is guaranteed thanks to asynchronous

processing of transactions, guaranteed delivery of containers and the underlying no SQL

database in the Movilizer Cloud.

7. The Movilizer Cloud has a built-in disaster recovery engine for your entire mobile apps. Even after data has been delivered (guaranteed delivery), should you lose any

data in your backend system, any data can be recovered from the Movilizer Cloud for a

timeframe of 3 months.

Movilizer Components & Architecture The Movilizer Connectors

1. The Movilizer Connectors are tools provided by with the Movilizer Platform in order to

speed up system integration. Thanks to the Movilizer Connectors, our partners and customers

can build Movelets in their language of choice (e.g. ABAP, Java, .NET) and in their

environment of choice (e.g. ABAP workbench, Eclipse, Visual Studio).

2. Many Movilizer Connectors exist today. Some are built by Movilizer GmbH (like the SAP,

the JAVA, the .NET or the Salesforce.com connectors) and some by Movilizer partners (like

the PHP connector, the SharePoint connector, the Excel Connector, the Access Connector,

the AS/400 connector, the Planon Connector, the Seeburger Connector etc.). Every month

new connectors are being built.

3. Any partners or customers using Movilizer can build new Movilizer Connectors from scratch

or extend the existing Movilizer Connectors (you can download the source codes). Building

new connectors is a simple task for any backend developer with an understanding of XML and

web services.

You translate your

business process into

Movelets

Movelets are physically

XML files that contain a

business process

description and that can

contain binary objects

(pictures, videos),

HTML5 web pages and

references as well as

the required metadata

A Movilizer App is then

composed of one or

many Movelets

Movilizer Components & Architecture How does Movelets work?

1 APP = 1 or N MOVELETS running on the Movilizer Client

1 MOVELET = 1 mobile process, a sequence of screens

Movilizer Components & Architecture The Movelet Lifecycle

Movelets are normally

built in your backend

system via the Movilizer

Connectors

Movelets are deployed

via the Movilizer Cloud

Movelets are run on the Movilizer Client

which acts as a secure app container

Movilizer Components & Architecture Architecture components and The Movelet concept

1 APP = 1 or N MOVELETS running on the Movilizer Client

1 MOVELET = 1 mobile process, a sequence of screens

Movilizer Components & Architecture The Movelet - What is it?

a building block that contains a mobile business process,

including the required data and metadata. Physically a

MOVELET is an XML file

MOVELETS are device and technology agnostic. The

MOVELET FRAMEWORK allows a business process to be

described in terms of configurable pre-defined controls, business

rules and business logic

MOVELETS can be self-contained or combined to create a

personalised mobile app. A Movilizer app contains 1 or more

MOVELETS

a MOVELET is built in your backend system or the Movelet

Studio in the cloud, and deployed via the Movilizer Cloud to the

Movilizer Client (a secure app container)

+

Movilizer Components & Architecture What can be packed into a Movelet?

MOVELETS typically contain business process templates where

screens, business logic and relevant data are defined

MOVELETS can be used for Master Data shared across multiple

business processes

HTML5 (and all related resources like CSS and JavaScript) can be embedded in a

MOVELET to give full control over the user interface for a single

screen or an entire process.

Movilizer Components & Architecture Templates for speed, HTML5 for UI power

a single MOVELET can

support any combination

of modes giving speed,

agility, flexibility and

control

+

+

+ Movilizer-App

Movilizer Components & Architecture The MOVELET- reuse skills, reuse software logistics

Site survey

Work orders

Timesheet

MOVELETS are built in your backend system, using

your existing development environment and skills

Movilizer Components & Architecture Dynamic Movelets, device native features and MEL

MEL = Movilizer Expression Language

XML structures are static by definition. The Movilizer

Expression language (MEL) allows Movelets to be dynamic.

MEL is a Movilizer specific scripting language that behaves

like JavaScript. In fact 80% of MEL is JavaScript and only

20% is specific to Movilizer.

With MEL you can dynamically change screens, screen

elements, flow control, etc and you can also access external

programs, access any of the device native features, access

file system, access peripheral drivers (e.g. RFID), establish

https connections , call web services, receive JSON strings

etc.

THIS SLIDE SHOULD NOT GO IN THE WEB I

BELIEVE, AND NEEDS TO BE PRESENTED ONLY

THERE WHERE REAL TECHNICAL AUDIENCES ARE

PRESENT

The 3 key advantages of MEL are:

Similar to JavaScript, easy to learn for any experienced developer in hours

Much faster than classic JavaScript because it is precompiled

Optimised for its use on mobile devices

MOVILIZER

IN DETAIL









Movilizer capabilities overview The Platform to build, deploy and run enterprise apps faster

Capabilities to build mobile apps The build phase lifecycle

Building enterprise mobile apps faster will considerably reduce your Total Cost of

Ownership and at the same time will make your enterprise more agile, but an enterprise

mobility platform must also:

Provide tools to your business user to enable them design their mobile app

Business users need to be empowered to translate ideas/requirements into apps

IT people need tools to ensure no misunderstandings of the requirements

An app is the result of collaboration, so IT and business need to be sharing work in

progress and mobile app versions

Provide tools to business users and IT experts to jointly test,

release faster and achieve better quality and no surprises

Automation of technical testing as much as possible

Ensuring stress test of mobile app before go live

Tools to debug and analyse on device performance across

different platforms before going live

Provide tools to your IT experts to build the mobile app as fast

as possible

Reuse existing skills and knowledge

Choose their preferred programming language

Use their preferred developer environment

Avoid large and fragmented IT team building the apps from two

ends

Movilizer capabilities overview

Design your enterprise Mobile Apps faster

Capabilities to build mobile apps Design (I)

The Movelet Designer runs in the Movilizer Cloud and can be accessed via any standard

web browser. All you need is a Movilizer Platform User, which can be created using the

Movilizer Platform Admin Portal. The Movelet Designer allows your business to define and

design mobile apps

The Movelet designer: it

empowers your business

to design Movelets

theirselves

Capabilities to build mobile apps Design (II)

With the Movelet Designer you can design Movelets quickly and simply


Develop your enterprise Mobile Apps crossplatform

Capabilities to build mobile apps Develop (I)

Build Movelets once and run everywhere 2

Movelets are normally built in your backend

system via the Movilizer Connectors. No

development on the app/device and no

development on the cloud.

1

Movelets are normally built in your backend system of choice via the Movilizer Connectors

are always cross-platform

Capabilities to build mobile apps Develop (II) the Movilizer ABAP Connector

For example in case of the SAP Connector, you build Movelets in ABAP in the SE 80

transaction

If you prefer to build your Movelets in .NET, download the .NET connector and import the

library into the Microsoft Developer Studio to build your Movelets inside the IDE.

Capabilities to build mobile apps Develop (II) the .NET Connector

Java developers can build Movelets in Eclipse by importing the Movilizer JAVA Connector

Capabilities to build mobile apps Develop (III) the JAVA Connector

You can always build your own Movilizer Connector from scratch. Any system capable of

sending an XML file via web service to the Movilizer Cloud can be connected with the

Movilizer Platform

Capabilities to build mobile apps Develop (IV) Building your own connector from scratch


Test your enterprise Mobile Apps faster and better

Capabilities to build mobile apps Test (I)

The Movilizer Platform testing tools help you to release new versions faster, with higher quality while

avoiding any surprises around app and landscape scalability.

For this purpose the Movilizer Platform provides three tools:

Stress test tool On-device debugger

Test automation

1. Stress test tool: a stress test utility to simulate thousands of concurrent

users

2. On-device debugger: with code analyser and live editing of variables

and app flow

3. Test automation: With Movilizer Expression Language you can build auto-executable Movelets that can run fully automated integration and

functional tests.

Capabilities to build mobile apps Test (II) Stress Test Tool

1) MOVILIZER STRESS TEST TOOL

The Movilizer stress test tool allows you

simulate thousands of concurrent users

running the exact Movelet and data that

you will be running in production

Command to the Movilizer Stress Test

Client:

1. Load Movelet XY 2. Send Movelet XY, 20,000 times and wait for replays

Capabilities to build mobile apps Test (III) - On Device Debugger

2) ON DEVICE DEBUGGER

The Movilizer Platform on device debugger allows you to change any variable, set break

points and analyse the persistence layer in real-time on the mobile device. Being able to

edit variables allows you to change the mobile app flow and the mobile app user interface

in real time.

3) TEST AUTOMATION

With Movilizer Expression Language (MEL) you can build auto-executable Movelets that can run fully automated integration and functional tests. Running automated Movelets in a

variety of platforms is a simple and quick, a single tester can run hundreds of automated

tests in multiple platforms in hours or even minutes.

Capabilities to build mobile apps Test (IV) Test automation

MOVILIZER

IN DETAIL









Capabilities to Deploy mobile apps The challenges of deploying enterprise mobile apps faster

Deploying enterprise mobile apps faster will make your enterprise much more agile, your

enterprise mobility platform must also:

Be manageable, monitored, and provide the relevant statistics and analytics

Centralised monitoring (crucial when various back-ends are mashed-up)

App distribution and user enrolment

App updates and version management

Centralised user management (crucial when various backends are mashed-up)

Be scalable and robust

Scaling to handle thousands of concurrent users without stressing back-end systems

Asynchronous processes of transactions

Load balancing

High availability and high performance, with low TCO

Disaster recovery and business contingency

Be secure

Data confidentiality - end to end encryption

User authentication

User authorisation and rights management

Attack detection and secure backend integration

Data centre security

Movilizer capabilities overview The Platform to DEPLOY enterprise mobile apps faster

Analytics and app management

Capabilities to DEPLOY mobile apps Monitoring, Analytics, App and User Management

When running an enterprise mobile application, the following capabilities are must have features for any

Enterprise Mobility Platform. In the Movilizer Platform, Monitoring, Analytics, App and User management

capabilities are part of the Movilizer Cloud and are accessible via the Movilizer Platform Cloud Portal or

within the back-end systems via the Movilizer Connector. System administrators can choose to work in

the back-end system that they know or use the Movilizer Cloud to manage multiple back-end systems

from a single place.

Centralised monitoring (multiple backends)

Analytics and usage statistics



Centralised user management (multiple

backends)

Monitoring (single-backend)



User management (single-backend)

Monitoring, Analytics, App and User Mngt. Central Monitoring in the Movilizer Cloud (I)

A central monitoring capability is crucial when managing mobile apps that mash-up

functionalities from several back-end systems in a single app.

Monitoring, Analytics, App and User Mngt. Central Monitoring in the Movilizer Cloud (II)

A central monitoring capability is crucial when managing mobile apps that mash-up

functionalities from several back-end systems in a single app.

Monitoring, Analytics, App and User Mngt. Monitoring in the Connector - Example SAP Connector (I)

For mobile apps using a single backend it can be preferable to run the monitoring in the

corresponding Movilizer Connector, so that the system admin can administrate the entire

mobile application out of the backend system. Our powerful connectors (e.g. the Movilizer

SAP Connector) beyond simple monitoring, allowing customers to see error logs, edit data

(when posting failed) and reprocess messages.

Monitoring, Analytics, App and User Mngt. Monitoring in the Connector - Example SAP Connector (II)

Monitoring, Analytics, App and User Mngt. Monitoring in the Connector - Example SAP Connector (III)

Monitoring, Analytics, App and User Mngt. Analytics

Mobile App usage statistics, analytics and the ability to recognise usage patterns and

implement the corresponding measures are increasingly important as mobile becomes

increasingly business critical. The Movilizer Platform provides centralised, detailed analytics

via the Movilizer Platform Admin Portal in the cloud.

Monitoring, Analytics, App and User Mngt. App Distribution and User Enrolment (I)

Movilizer Client distribution can be done via the public app stores for the various mobile

platforms or can be distributed directly. Once downloaded the generic Movilizer Client can be

customised remotely OTA For platforms where no app store exists (e.g. Desktop Client or

Windows Mobile Client for PDAs) the Movilizer Client is distributed directly using the Movilizer

Distribution Service (http://demo.movilizer.com/mds )

Movilizer Client available in the Apple App Store, Google Play,

Microsoft marketplace and Blackberry world.

Movilizer deployment URL

Monitoring, Analytics, App and User Mngt. App Distribution and User Enrolment (II)

Movilizer Users can be created in the Movilizer Cloud using the Movilizer Platform Admin

Portal or in the backend system via the Movilizer Connector

User credentials are an identifier and secret, the identifier can be a Participant ID,

mobile phone number, virtual mobile phone number, or email address

User credentials can be automatically distributed via a trusted channel such as SMS or

email based on the type of user identifier

Users can be reset remotely by the Movilizer Platform Admin Portal in the Movilizer

Cloud, which will resend user credentials via the appropriate trusted channel

All user enrolment features are available in the Movilizer Cloud or in the backend system

via the Movilizer Web Service.

Monitoring, Analytics, App and User Mngt. App Updates and Version Management (I)

MOVELET UPDATES AND VERSIONS The abstraction of the business process from the

mobile device means that the Movelet can be used to update the entire app without changing

anything on the device or in the Movilizer Client. This means that the Movilizer Client is only

uploaded once on a public app store, but you can change the versions of the Movelets as

many times of you wish. Any Movelet updates are included in the standard synchronisation

so that the update process takes seconds and is a pure background process for the end

user. To manage versions of Movelets you can use Movelets versions which are built in into

the Movilizer Protocol.

Movilizer

Client

2.0

Movelet Version 1

Movelet Version 2

Movelets can

be updated

without any

changes on

the device.

Movilizer guarantees that old protocols will be supported on newer

Movilizer Client versions, which means that existing Movelets will

remain compatible with new mobile OS versions supported by newer

Movilizer Client versions.

Monitoring, Analytics, App and User Mngt. App Updates and Version Management (II)

Any Movilizer Client updates are automatically announced to users via the corresponding

app store (if the Movilizer Client was distributed via that channel). New versions of the

Movilizer Client will be automatically updated, but backwards compatibility is guaranteed so

existing Movelets will always run on newer version. Alternatively, the customer can manage

the distribution and updates for the Movilizer Client directly.

Movilizer

Client

2.1

Movilizer

Client

2.0 Movelet built with

Client Version 2.0

Client

Release 2.1

Connector

Release 1.9 Cloud

Release 2.1

Monitoring, Analytics, App and User Mngt. App Updates and Version Management (III)

MOVILIZER CLOUD UPDATES are automatically done by the Movilizer team and do not

require any testing or actions by customers. Customers using the multi-tenant Movilizer

Public Cloud are given a minimum of 14 days notice about any cloud upgrades, which are

normally run over the weekend. Typically no downtime is required, but if required, the

planned maintenance timeframe is always below 2 hours.

This second scenario is not possible as all customers using the multi-tenant cloud are always on the latest

cloud version

Client Release 2.0 Connector

Release 2.0 Cloud

Release 2.1

X Client Release 2.1 Connector

Release 1.9 Cloud

Release 2.0

Monitoring, Analytics, App and User Mngt. App Updates and Version Management (III)

MOVILIZER CONNECTOR UPDATES are in full control of the customer. It is up to the

customer when to upgrade the Movilizer Connector to the latest version. Older Movilizer

Connectors can always work with newer versions of the Movilizer Cloud.

Client Release 2.0 Connector

Release 2.0 Cloud

Release 2.1

X Client Release 2.1 Connector

Release 1.9 Cloud

Release 2.0

This second scenario is not possible as all customers using the multi-tenant cloud are always on the latest

cloud version

Connector

Release 2.1

Mobile users, as well as customers can be managed centrally from the Movilizer Cloud. This

is especially important when managing several apps consuming data from several data

sources. User management can also be done in the back-end system via the Movilizer

Connector.

Monitoring, Analytics, App and User Mngt. Centralised user management (I)

Monitoring, Analytics, App and User Mngt. Centralised user management (II)

Monitoring, Analytics, App and User Mngt. Centralised user management (III)


Scalability

Capabilities to deploy mobile apps Scalability

Scaling up a mobile service with the Movilizer Platform does not require any new servers nor

any new infrastructure. The Movilizer Cloud is massively scalable with high availability and

high performance which means scaling from a handful of users to 1000s takes hours or even

minutes . The following are key features of scalability in the Movilizer Platform:

An endless scalable middleware capable of

supporting thousands of concurrent users

Asynchronous processes of transactions

Load balancing

High availability

Disaster recovery and business

contingency

Scalability An endless scalable middleware (I)

The entire Movilizer Platform has been developed and optimised for usage with a

big data database (as used by Twitter, Netflix, eBay and many others). Linear scalability is a key characteristic of the Movilizer Cloud architecture:

The example above is based on Netflix experiences using the same big data

database used by the Movilizer Cloud.

Scalability Load balancing

Movilizer cloud offers built-in load balancing over a large number of persistence

clusters

SCALABILITY High availability(I)

The Movilizer Clouds, thanks to is underlying big data

persistence layer does not offer high availability via fail-over) but Continuous Availability.

There is no such a thing like standby infrastructure. There is stuff you always use and stuff that wont work when you need it Ben Black

The biggest problem with failover is that you are almost never using it until it really hurts. It is like backups that you never test Rick Branson

Scalability High availability (II)

The standard Movilizer SLA guarantees 99.5% Movilizer Cloud availability over

365 * 24.

This is possible because:

There are no single points of failure. There are no network bottlenecks. Every

node in the cluster is identical (multi-master).

Data is automatically replicated to multiple nodes for fault-tolerance.

Replication across multiple data centers is supported. Failed nodes can be

replaced with no downtime.

Adding capacity is application-transparent and requires no downtime.

It tolerates node failure. It never needs to start replication from scratch. Smart

replication avoids correlated failures.

Scalability Disaster recovery and business contingency

Disaster recovery

The Movilizer Cloud never loses any

data, even when an entire data centre

goes down thanks to its durable

capability.

Data in the Movilizer Cloud is

automatically replicated to multiple

nodes for fault-tolerance. Replication

across multiple data centers is

supported. Failed nodes can be

replaced with no downtime

Business contingency is built in via

remote nodes and geographic

redundancy


Security

Capabilities to DEPLOY mobile apps Security

Be secure

End to end encryption

User Authentication, authorisations and

rights management

Attack detection and Cloud security

Backend integration

Physical security of data centres

When running a mobile service, the entire landscape needs to be appropriately secured,

end to end. Preservation of confidentiality, integrity, authenticity, non-repudiation and

reliability is very important. The Movilizer Platform offers the following capabilities across all

components in the architecture (Movilizer Connectors, Movilizer Cloud and Movilizer

Clients) :

Security User Authentication, authorisations and rights (I)

The Movilizer Platform supports 2 layers of mobile user authentication, Movilizer Client

Authentication and Business Scenario Authentication or Movelet Authentication:

Movilizer Client Authentication authenticates the Movilizer Client with the Movilizer Platform. It is triggered by the initial registration of the Movilizer Client

Movelet Authentication - authenticates the user with the business

scenario and customer system. This authentication layer is

implemented using Movelets and the cross-platform/front-end

development capabilities of the Movilizer Platform, and therefore

provides a customer with complete control over the authentication.

Security User Authentication, authorisations and rights (II)

User authorisations and rights are typically implemented in the Movelets

itself, according to the relevant backend rules.

In order to implement authorisations and rights, you normally use the

visibility expression of the relevant Movelets and MEL.

Security Attack detection and cloud security

All information inside the Movilizer system is stored in conjunction with a client specification

in the multi-tenant Cloud . Access to data is only granted for assigned client ids. On all

channels, authorized access to client specific information is only possible via defined

interfaces. Direct access to the database is not possible at any time.

The Movilizer Cloud implements tools and routines to identify attacks and malware which can

automatically block backend and client systems from sending any data requests. For

confidentiality reasons no further details can be disclosed.

Security Back-en Integration

The authentication of a customers backend system at the Movilizer Cloud can be achieved through one of the following two security levels:

Combination of System ID/Secret

Initialization of an X509 certificate out of the customers backend system.

MOVILIZER

IN DETAIL









Capabilities to RUN mobile apps The challenges of deploying enterprise mobile apps faster

Running enterprise mobile apps faster hugely increases the end user adoption but it also

means that your mobile app needs to:

Mash-up functions and data from source systems into a single app

Multiple data sources on a single app

Exchanging data from one system to the other in the app

Jumping from one system to the other within a process

Unified look & feel and navigation patterns

Single sign on, User authentication and authorisations

Centralised User and App monitoring across all systems

Work always, with best in class response times (Smart-Sync)

Ensure that your users can work offline as well as online

Push information to your users when required

Handle large offline master data sets and offline multi-media files

Master data offline and search handling

Adapt your mobile app to the connectivity environment

Run everywhere (Multi-channel access)

Build once run everywhere and combine is a must, especially

considering the increasing variety of possible consumption channels

for mobile apps (PCs, laptops, PDAs, smartphones, tablets,

glassware, smart watches etc.).


Mash-up all your backend systems in a single app

Capabilities to RUN mobile apps System Mash-Ups (I)

You can run mobile apps faster with the Movilizer, because you can Mash up all relevant

source systems on a single app and so save time. The user just gets an app that does what

they need - the complexity of managing multiple back-end systems is hidden. This means

that you can :

Use multiple data sources on a single app

Exchange data from one system to the other in the app

Jump from one system to the other within a process

Have a Unified look & feel and navigation patterns

Single sign on, User authentication and authorisations

Centralised User and App monitoring across all systems

Capabilities to RUN mobile apps System Mash-Ups (II) Run 2 or more systems in 1 app

The Movilizer Platform can support any number of customer source systems, internal or

external, in a single mobile app. The user just sees gets a consistent user experience from a

single app but in reality each Movelet can come from a different source systems.

Capabilities to RUN mobile apps System Mash-Ups (III) Exchange data between systems

Movelets sourcing from different systems can share data by simply exchanging global

variables. Global variables can be of many different types e.g. numeric, boolean, arrays,

multidimensional arrays etc.

Oracle Movelet

Writes variable worked

times = 8

$global:oracletimes = 8

SAP Movelet

Reads variable worked

times = 8

$local:saptimes =

$global:oracletimes

Please check the relevant documentation under:

https://devtools.movilizer.com/confluence/display/DOC/MEL+Syntax#MELSyntax-

GlobalVariables

Capabilities to RUN mobile apps System Mash-Ups (IV) screen jump in between systems

Inter-Movelets allow one Movelet to jump to another. If the Movelets are source from

different backend systems then the user seamlessly transfers from one system to the other,

while maintaining a consistent user experience a single process.

For example, screen 1 from Movelet 1 can drive the user to the screen 1 of Movelet 2 and

then back again to screen 2 of Movelet 1.

The Movilizer Inter-Movelet is a special function which also supports the use of reusable sub

processes (Child Movelets). For the user the transition between the parent Movelet and the

child Movelet is seamless, it appears as a continuous process.

Please check the relevant documentation under:

https://devtools.movilizer.com/confluence/display/DOC/Intermovelet+Screen

Capabilities to RUN mobile apps System Mash-Ups (V) SSO, aut. and authorisations

Authentication Movelets can be used to implement Single Sign On, role based

authorisations, complex authentication rules, 2 factor authentication using simple PIN, or

any other form of access control

For example, user authentication could include userID and

password, or barcode/NFC scanner, location information, integration

with LDAP, integration with SAP, etc.) This user authentication can

also be applied at any point within the business scenario, from

securing access to the entire scenario or only securing access to a

specific function.

Capabilities to RUN mobile apps System Mash-Ups (VI) centralised monitoring

If you are mashing up different systems in a single app, it is very important to have a

centralised administration and monitoring capability in order to ensure the mobile service

remains manageable. The Movilizer Platform Admin Portal provides this centralised

function, in which the mobile app admin user can monitor across all systems, all logs,

usage statistics, assigned movelets etc.


SmartSync inside for an optimal app performance

Capabilities to RUN mobile apps Smart Sync (I)

One of the Movilizer Platforms key capabilities which guarantees that Movilizer users run

mobile apps faster is SmartSync. This capability includes a wide range of functions that

improve the user experience.

Offline / online / mixed mode

Push Synchronisation

Offline handling of large amounts of master data

Offline handling of large multimedia files

Context aware data sync

Capabilities to RUN mobile apps Smart Sync (II) Offline/Online Operation

The Movilizer Platform allows users to work entirely offline with occasional synchronisation,

online, offline with regular synchronisation, or any combination. The Movilizer Platform

supports a number of synchronisation options which can be trigger manually or automatically.

During a Full Synchronization replies will be uploaded, and Movelets and Master Data will be

downloaded. In addition any Movilizer Client error messages will be uploaded to the Movilizer

Cloud.

Fullsync

Fullsyncsilent

Uploadonly

Uploadonlysilent

Downloadonly

Downloadonlysilent

Autosync

Online Sync

Relevant links in the documentation:

https://devtools.movilizer.com/confluence/display/DOC/Online+Sync

https://devtools.movilizer.com/confluence/display/DOC/Client+Sync

Capabilities to RUN mobile apps SmartSync (III) Push synchronisation

The Movilizer Platform offers different Movelet Push functions, which support notifications

and can trigger actions, such as a synchronisatio . On the mobile device either a notification

is shown in the Movilizer or in the notification center of the device.

The SyncPriority can be configured in every Movelet and can have the following values:

None: (default) / no push is executed

Notify: a notification is shown in the Movilizer title bar or in the notification center of the

device if notifications are activated in the OS settings

LazySync: the Movelet name of the pushed Movelet is shown in the Movilizer Main

Menu. By clicking on the Movelet the Movilizer Client synchronizes and downloads the

Movelet

Online: a Movelet sync in case a backend answers to online call from the Movilizer

Client as answer to an call of the function.

TriggerSyncMovelet: a Movelet sync will be triggered, only this push Movelet will be

synchronized. No further uploads and downloads are executed

TriggerSync: a fullsync will be executed

Capabilities to RUN mobile apps Smart Sync (IV) Offline Handling of large master data sets

The Movilizer Platform provides offline handling of large amounts of master data. The Master Data

feature allows mobile apps to be built in a data centric model. For example, some customers are

managing over 500,000 master records in a pure offline operation. The Master Data feature manages the

download, search and data updates.

The following are features of the master data framework:

Relevant links in the documentation:

https://devtools.movilizer.com/confluence/display/DOC/Masterdata

Replicating master data: master data is

replicated to the cloud (encrypted) via json ws.

Downloading master data: master data is

downloaded in a compressed binary format

Progressive download: large sets of master

data can be downloaded in multiple syncs

Searching master data on the app: search

on the mobile app is ultrafast. A set of 100,000

records offline can be searches in seconds in

the mobile device

Delta sync of changed records: only changes

in master data are replicated, not the entire set,

so that the synchronised data volumes are

always optimised.

Capabilities to RUN mobile apps Smart Sync (V) Offline Handling of multimedia documents

Replicating master data: master data is

replicated to the cloud (encrypted) via json

ws.

Downloading master data: master data is

downloaded in a compressed binary format

Progressive download: large sets of

master data can be downloaded in multiple

syncs

Searching master data on the app:

search on the mobile app is ultrafast. A set

of 100,000 records offline can be searches

in seconds in the mobile device

Delta sync of changed records: only

changes in master data are replicated, not

the entire set, so that the the synchronised

data volumes are always optimised.

Capabilities to RUN mobile apps Smart Sync (V) Context aware data sync

Context aware data Sync allows Movelets to trigger different types of Sync depending on

the current connectivity status.

Types of connectivity could be:

WiFi, GPRS, 3G, 4G/LTE

Types of Sync could be:

Fullsync

Fullsyncsilent

Uploadonly

Uploadonlysilent

Downloadonly

Downloadonlysilent

Autosync

Online Sync

Master data Sync / Multimedia Document Sync

Although this feature can be implemented in Movelts already

from 2.1 onwards, the exact query of device bandwidth via MEL

will only available in release 2.2 (beta status)


Multi-channel access for best user experience

Capabilities to RUN mobile apps Multi-channel Access (I)

Today the Movilizer Client runs on 8 different platforms natively with HTML5 support inside

native containers on 5 of these 8 platforms. Our R&D teams are working on supporting future

channels already, so that in 2014 you will be able to run your Movelets on smart watches,

glassware and car systems.

*Beta release in Q1 2014

**In R&D currently

Movilizer Clients available:

iOS

Android

Windows Phone

Blackberry OS

Desktop Clients for Windows , Linux

and Mac OS

Windows Mobile

J2ME

Web Browser Client *

Google Glass **

SmartWatches **

Capabilities to RUN mobile apps Multi-channel Access (II) - The Movilizer iOS Client

The Movilizer iOS Client can run on iPhone, iPod Touch, and iPad and still make use of the

full resolution and device features of each platform (e.g. barcode scanning via device

camera). The Movilizer iOS Client can be downloaded from Apple App Store. The Movilizer

iOS Client supports iOS4.3 or higher (in Movilizer version 2.1).

Capabilities to RUN mobile apps Multi-channel Access (III) - The Movilizer Android Client

The Movilizer Android Client can run on Android phones, as well as Android Tablets and will

make use of the full resolution and device features of each platform (e.g. barcode scanning

via device camera).

The Movilizer Android Client can be downloaded from Google Play or from the Movilizer url:

from http://movilizer.com/mds.

The Movilizer Android Client supports Android 2.2 or higher (in version 2.1)

Capabilities to RUN mobile apps Multi-channel Access (IV) - The Movilizer Win. Mobile Client

The Movilizer Windows Mobile Client can

run on Windows Mobile 5,0 or higher

operating systems and is delivered via the

movilizer mds service as a cab file

(downloadable from

http://movilizer.com/mds). This is the client

you normally use when running on

ruggedised devices, specially for

warehouse , materials management or

track & trace. On request Movilizer can be

also run on Windows CE (needs to be

tested on each specific hardware as each

build is different). Movilizer also runs on the

new OS Windows Mobile Embedded.

The Movilizer Windows Mobile Client

supports Windows Mobile 5.0 or higher (in

version 2.0)

Capabilities to RUN mobile apps Multi-channel Access (V) - The Movilizer Win. Phone Client

The Movilizer Windows Mobile Client can run on Windows Mobile 5,0 or higher operating

systems and is delivered via the Microsoft marketplace. The Movilizer Windows Phone 8 Client

supports Windows Phone 8.0 or higher (in version 1.9).

Capabilities to RUN mobile apps Multi-channel Access (VI) - The Movilizer Desktop Client

The Movilizer Desktop Client is delivered in different installable files depending on your PC

or Laptop and supports on Windows 8, Win32 (e.g XP, Vista), MacOS as well as Linux.

The Movilizer Laptop/PC App is downloadable from:

http://movilizer.com/mds

The Movilizer Desktop Client supports any operating system capable of running java 1.6 (in

version 2.1).

Capabilities to RUN mobile apps Multi-channel Access (VII) - The Movilizer Blackberry Client

The Movilizer Blackberry Client is delivered via the deployment url or can be downloaded

from the Blackberry world. The Movilizer Blackberry Client supports Blackberry 5.0 or higher

(in version 2.0) . Blackberry 10 is not jet supported by Movilizer.

Capabilities to RUN mobile apps Multi-channel Access (VIII) The Movilizer J2ME Client

The Movilizer J2ME Client supports any feature mobile phone supporting J2ME MIDP

(e.g. Nokias, Sony Ericson etc.).

The Movilizer J2ME Client is a jar file downloadable from:

http://movilizer.com/mds.

The Movilizer J2ME Client runs on any device supporting java J2ME with the profile CLDC1.1.

Capabilities to RUN mobile apps Multi-channel Access (IX) The Movilizer Web Client

The Movilizer Web Client does not require any local installation because it runs on any

modern web browser (Internet Explorer, Firefox, Chrome, Safari, Opera).

You can reach the Movilizer Web Client under the following url:

http://demo.movilizer.com/OnlineClient/

* The Movilizer Web Client today is under Beta status and will be out of beta by Q2 2014.

Capabilities to RUN mobile apps Multi-channel Access (X) The killer questions

Question 1: Are all screen types and features supported by all 8 Movilizer Clients?

No. Some platforms like the J2ME or Windows Mobile are really limited, so that some features

and screen types of Movilizer would only run on some Movilizer Clients .

For a detail overview of which features / screen types run on which platforms, please

check our documentation:

https://devtools.movilizer.com/confluence/display/DOC/Screens

Capabilities to RUN mobile apps Multi-channel Access (XI) The killer questions

Question 2: build once run everywhere is great, but how do we make sure that despite of running on 8

platforms, Movilizer is still getting the

most of each platform adapting to

screen resolution and format?

Movilizer comes with a feature called

Complex UI which allows you to adapt your Movelets to the target device format

and resolution. Complex User Interface is

used to combine multiple screens into a

single screen declaratively.

For more details check the documentation under:

https://devtools.movilizer.com/confluence/display/DOC/Complex+UI

Capabilities to RUN mobile apps Multi-channel Access (XII) The killer questions

Question 3: How do we make sure that despite of being able to build Movelets

regardless of the OS, we can still make use of device features and native drivers from

any attached peripherals (e.g. barcode scanners, Bluetooth printers)?

With MEL (Movilizer Expression Language) which offers a function called the MEL Module

SPI: The Module SPI connection functions cover everything you need to create Bluetooth,

socket, http(s), IR, Com connections via the Movilizer Client application. This allows you to call

3rd party systems directly via an internet or a wireless connection. Also you allow the Movilizer

Client application to communicate with other software on the end user's device.

For a complete reference on how this work, please find the docu under:

https://devtools.movilizer.com/confluence/display/DOC/Module+SPI+Connection+Functions

Capabilities to RUN mobile apps Multi-channel Access (XIII) The killer questions

Question 4: can I use Movilizer for Machine to Machine communication as wel, (M2M)?

It requires enhancements but yes (not "out of the box"). In order to run Movilizer in a M2M

environment you typically use the Movilizer stress test client (a non-UI Movilizer client) and

extend it in order to access the machine commands.

Question 5: when will I find a Movilizer for smart watches (e.g. Samsung Gear) and for

Google Glasses?

Our Movilizer R&D department is working on this already. WE will be launching new Movilizer

clients to run on those platforms along 2014.

MOVILIZER

IN DETAIL









Build or use Out of the Box apps build Movelets in your language of choice, in your backend

The Movilizer Platform manages the

mobile technology

You focus on your mobile requirements

Build Mobile business processes

(Movelets) in your own business system

You choose the development tool and

programming-language

The Movelets are then combined to

create personalised mobile apps for

each user optimised for their device

Movilize SAP Movilizer Connector for ABAP

Movilize Microsoft Movilizer Connector for .NET

Movilize Oracle Movilizer Connector for java

Movilize any System Build your own connectors

Movilize Salesforce.com Movilizer Connector for Salesforce

Build apps within your system in ABAP, java, .NET, etc.

Rapidly mobilize your business.

Benefit of established best-practice

solutions integrated into your business

systems.

Configurable and customizable to

meet your specific requirements.

Build or use Out of the Box apps Every month our collection of Connectors and Apps grows

MOVILIZER

IN DETAIL









Movilizer Components & Architecture The Movilizer openness and how we embrace standards (I)

Movilizer is the most open enterprise mobility platform available on the market today. The

facts:

1. The entire Movilizer documentation is available for anonymous users (no registration

required) in the Internet.

2. Movilizer Connectors are generally open source and can be downloaded for free from the

Internet. Even the Movilizer SAP Connector for SAP (the only exception), is open source

(in the sense that you can access the source codes and modify it).

3. All Movilizer customers can access and modify the source codes of any of the Movilizer

Out of the Box apps at no additional costs.

4. The Movilizer Cloud Portal is accessible and free for the public and includes a 3 months

free trial period, and even after 3 months only support fees are charged (no licenses).

5. Movilizer GmbH does not charge any licenses fees upfront for the usage of any of our

software, but only support fees. Support is mandatory after the initial 3 months free trail.

6. Since Movilizer apps are based on Movelets based on the backend (no UI needs to be

built) its portability is always higher than for any other types of apps and most of the

backed work done for the Movilizer can be migrated to other frameworks (with exception

of the Movelet mapping layer).

Movilizer Components & Architecture The Movilizer openness and how we embrace standards (II)

Movilizer embraces standards wherever standard exists and wherever the use of

standards do not compromise the SPEED of build, deploying and running mobile

apps.

We follow the following standards:

For data transfer and communications Movilizer embraces:

XML

Wed Services and Soap

JSON

For Application development Movilizer provides full support HTML5, Javascript

and CSSS via two different ways:

Wrapped within the Movilizer app via the HTML5 Screen Template

Running on the browser via the Movilzer Web Client

MOVILIZER

IN DETAIL

5 Some Enterprise app samples

4 Why the Movilizer

3 How we do it

2 What we do

1 Who we are

Phone +49 621 150 204 22

E-Mail

Internet www.movilizer.com

Movilizer GmbH

Julius-Hatry-Strae 1

D-68163 Mannheim, Gemany

The contents of this presentation are the intellectual property of Movilizer GmbH. Any other use as well as disclosure to third

parties in the original, in a copy, in part, electronically or by similar content requires the approval of the company.

Alberto Zamora Consultant

[email protected]

Documents

Movilizer Detail Presentation UnderstandIT V17