Technology

The Lekane solution consists of a Mobility Server and mobile Client Containers. The Mobility Server communicates with a contact center software solution and any other necessary third party applications. The Client Containers communicate with the Mobility Server.

Mobility Server

Lekane Mobility Server is a Java application that runs inside a J2EE compliant servlet container. It has been certified against Tomcat 5.5, but commercially available servlet containers such as BEA WebLogic Server, IBM WebSphere and Oracle Application Server also can be used. Tested operating system platforms are Windows XP/2003 and Red Hat Enterprise Linux. Further operating system platforms will be tested as needed. Out of the box integration with Genesys Integration Server has been implemented using the Genesys Java Interaction SDK. Additional integration points can be added using an Apache Axis based mechanism. Mobility Server uses a JMS based messaging mechanism internally. The implementation is based on an open source JMS provider.

Client Container

Lekane Client Container is a J2ME application that runs on MIDP 2.0 / CLDC 1.1 compliant mobile devices. Typically mid-to-high end mobile phones as well as PDA’s support these specifications. The technology has been tested on various Nokia and Motorola models and testing is ongoing for Samsung and SonyEricsson. The container utilizes a cross-platform toolkit to make it easy to support a wide range of devices.

The Client Container communicates with the Mobility Server using HTTP over TCP/IP on a cellular transport. The transport can be e.g. EDGE, 3G or WiFi. Communications between the Client Container and Mobility Server are encrypted using an open source based strong encryption library. Messages from the client container are passed on to a JMS based messaging layer that the Mobility Server subscribes to.

Applications

Applications that run in the Client Container are defined with the help of an application flow, a number of screens and resources. Flow and screen definitions are plain text files that describe the logical flow, interaction with the user and functionality of the application as well as the layout and elements of the various displays that the application uses. Resources are images, sounds and video elements that the application screens and flow use. The definition files and resources are provisioned to the Client Containers using a server side management interface. Application or screen definitions and resources can be pushed to the client and changed dynamically without end user intervention using an over-the-air provisioning tool. This makes application updates painless. Applications can be personalized down to a single client.