|
|
|
| -iBus//Mobile |
Introduction
Mobilising an application could not be made
easier. iBus//Mobile uses Java standards based
technology from the back end application right
through to the device. The end user benefits from
reliable, secure and optimised communicatons, under
adverse networking conditions. In the wireless
world, disconnections, bandwidth fluctuations and
client application mobility are all commonplace,
this is in stark contrast to the fixed wire-line
world of e-commerce and the Internet. When
targeting this environment a developer must take
into account the worse case networking scenarios;
iBus//Mobile handles this.
Overview
The
core of the iBus//Mobile infrastructure is both the
Gateway and the JMS Provider (iBus//MessageServer).
The Gateway acts as a proxy on behalf of mobile
devices and controls the end-to-end connection. The
Gateway is also, responsible for the transformation
of the messages between the mobile clients and the
JMS Provider.
Architecture
The
JMS Provider is a backend JEE(formerly J2EE) component that
implements the JMS API and manages the messages
between the Gateway and the backend system. The JMS
Provider controls the message transfer, the Gateway
acts as a "proxy" to the mobile clients.
iBus//Mobile provides a JMS client library and a
Mobile Gateway that can run on a wide range of
platforms, as well as comprehensive
documentation.
For work force automation and many other enterprise
segments iBus//Mobile is the perfect soluton.
Allowing a backend application to address the whole
spectrum of devices from low end SMS devices to
programmable J2ME, Blackberry, .NET CF, Android devices, as well as high
end laptops and workstations.
Guaranteed Wireless Data Delivery, Any Network, Any
Device, Anywhere,
Everytime.
|
| -Technical
Details |
Product Feature
Set
 Lite-weight Wireless JMS
client library |
Applet
Support |
| For J2ME, J2SE,
.NET, .NET CF and Android |
Over-the-air JMS client
provisioning |
| Intermittent
communication
support |
Reliable messaging
protocol stack |
| Transparent
online/offline
operation |
JMS-SMS, JMS-MMS,
JMS-SOAP |
| Store-forward support
right on the device |
SMSC and MMSC
connectivity |
| Guaranteed end-to-end
message delivery |
Queued invocation of Web
Services |
| Message types: Text,
Image, Binary, XML |
J2EE and third-party JMS
connectivity |
| Message fragmentation
and reassembly |
Administration
GUI |
| Message
encryption |
Comprehensive logging
facility |
|
Transactions |
Extendibility |
| JMS over TCP, UDP, HTTP,
HTTPS, SOAP |
Gateway Clustering, Scaling, Loadbalancing and Failover |
On the server side, iBus//Mobile plugs
directly into various stand-alone JMS providers as
well as into various J2EE application servers (e.g.
BEA WebLogic, SUN, JBOSS, SAP WebAS, Oracle AS).
iBus//Mobile provides a native JMS client library
for Microsoft .NET and .NET CF, which means you can use the
full power of the JMS API inside C#, VisualBasic,
and other .NET programming languages. This allows
you to have the added benefit of using disconnected
operation and full security in the .NET
environment.
Your mobile applications become highly interactive
(push, pull, broadcast, multicast, transactions),
fully reliable, the guaranteed delivery of
application data.
Disconnected operation when your device loses
network coverage, transparent synchronization of
on-device message queues.
Hardware/Software
Support
Client
| HTC QTek 8310, 910 for .NET CF and MIDP over HTTP and TCP |
| Nokia 6600 MIDP over TCP,
UDP, HTTP |
| Sony Ericsson P800,
P900, P910i |
| Siemens SL Series, using
MIDP over HTTP |
| Palm Treo 650, 750v using MIDP, CLDC
over TCP, UDP, HTTP |
| HP iPaq 4700, 6300
Series, 6500 Series using WinCE over TCP, UDP and
HTTP |
| MS Pocket PC using WinCE
over TCP, UDP and
HTTP |
| Nokia 6210, SMS and
WAP |
| RIM Blackberry 7290, 7730+
using MIDP,CLDC over TCP, UDP,
HTTP |
| Symbol MC70 Windows Mobile 5.0 [.NET CF] over HTTP and TCP |
|
HTC Dream for Android over TCP, UDP and HTTP
|
| Laptops and
Desktops |
Gateway
| Platform iBus//Mobile
Gateway: Workstation running Windows, Linux,
Solaris, using Sun JDK 1.3 or higher
(J2SE) |
Networks/Protocols
| SMS, WAP, UDP, HTTP,
HTTPS, GPRS, WiFi, GSM, MMS and many
more |
|
|