 |
|
|
|
| TES Mobile Framework (MFW) |
|
| |
|
Provides an adaptive, user-friendly mobile device user interface, integrated with an easily configurable business services manager, enabling true application mobility for your enterprise business applications.
|
|
|
|
|
|
| TES MFW Client Components |
|
| |
|
- Request/Response Handler - uses standard Http(s) protocol
- Transaction Manager – ensures data synchronization between Smartphone and enterprise business data warehouse
- Dynamic UI – Web 2.0 layout editor,converts XML to J2ME User Interface
- Reporting Service Manager – utilizes native Smartphone browser to render reports in multiple formats (HTML, PDF*, Excel* etc)
- Smartphone Integration Engine – leverages existing smart phone applications for maximum functionality (i.e. calendar, alert notification, GPS, contact management)
- Offline Manager – manages offline data storage and retrieval using RMS
|
|
| |
|
|
|
| TES MFW Server Components |
|
|
|
- Controller - authenticates and calls the relevant service to handle the request
- TES MFW Service Administrator – Data push and synchronization component that retrieves data from TES MFW business service and pushes to the client based on user-defined preferences.
- TES MFW for CRM – converts requests to SOAP/Web Service Request and invokes the web service provided by the CRM /Enterprise Applications
- TES MFW Integration Adapter – converts request to SOAP/Web Service Request and invokes the web service provided by any application business service
- TES MFW Reports – reporting service that converts Web Service response/XML to multiple formats (PNG, HTML, PDF and Excel etc.)
|
|
|
|

|
|
|
|
|
|
| TES MFW Framework Architecture |
|
|
|
 |
|
|
|
| Why TES MFW Framework? |
|
|
|
Offline Support
- Get your Business Critical Functionality offline
- Modify & Add information offline
- Auto-synchronize Offline Data using Offline Manager
- Short-term PDA connectivity loss becomes transparent to the user
- Scheduled or unscheduled updates are supported via Transaction Manager
Rich User Interface
- Keypad Mapping (Use Short cut keys to access functionality)
- Enhanced Navigation
- Web 2.0
Reporting
- Configurable Report Types (Tabular & Charts)
- Multiple Formats Supported (HTML, PDF *, Excel *)
- Scheduled Report execution and distribute via enterprise email service
- Get existing reports on your mobile device
- Print/Save reports directly via mobile device
|
|
|
| What about “browser-based” mobilization solutions? |
|
|
- Offline support not possible. Productivity only possible while mobile device is active on the network.
- Multi-application integration not possible. (i.e. mobile user is utilizing HR application, CRM, and industry-specific application in the field)
- No Integration with the Mobile Applications (i.e. PIM Calendar).
- No Web 2.0 Support (except for iPhone)
- No location awareness
|
|
|
|
| Trend for Rich Client Applications in Smart Phones |
|
|
|
iPhone :
iPhone has the best WEB2.0 implementation which gives the Rich UI and for phone integration they provide plug-ins Blackberry :
Has one of the best Java implementation. Browser is not capable of WEB 2.0 or local processing. Our framework calls the Browser for displaying HTML reports. Blackberry bets on Java environment for all their applications Windows Mobile :
Supports both .NET CF and Java. Browser does not support WEB 2.0 .NET is the preferred platform of choice but has an equally good Java implementation Android :
Android seems to have the best strategy. It bets on the Java environment and allows you to embed a WEB 2.0 browser into your application.
|
|
|
|
| TES MFW Hardware Requirements: |
|
|
|
Client :
RIM OS 4.2 and above Currently porting it to 4.1 Server :
Works with any OS that has a Java Virtual Machine (Linux OS preferred) Recommended Minimum :
Pentium Dual Core/Quad Core Linux OS 2GB RAM 80 GB Hard Disk Open Source Systems Used :
Spring IBatis/Hibernate and Postgres Tomcat/JBOSS Linux Java/RMS Jasper
Current Framework Development
Next Generation UI Components for J2ME
|
|
|
|