|
KJAVA
KJAVA is a derivation from JAVA. It defines a subset of limited Java-commands used in low-memory environments as modern i-appli-capable mobile phones and smart phones. It uses only a minimum of memory to create a complex user-interface, therefore offering a better interactivity than i-mode-services today.
go back
LDAP
LDAP (Lightweight Directory Access Protocol) is a hierarchical organisation of data within directories that can be browsed. As an open standard, LDAP offers interoperability among different applications that rely on the same standard inetOrgPerson structure. Therefore, LDAP directories help to integrate various applications using the same datasource. LDAP installations can typically be found in telco and Internet portal environments, dealing with millions of customers.
The weblicon application suite uses an LDAP adaptor which is part of the WebObjects 4.5 application server for user authentication and storage of all user-generated address book contents. The LDAP adaptor itself uses TCP/IP for communication and data exchange with the LDAPv3 directory server.
All basic address information of clients is stored on a LDAPv3-compatible directory server. During development, Oracle Internet Directory (OID), based on Oracle V8.1.6 was used as an LDAP server, but initial tests with Netscape Messaging Server V4.15 have already taken place to ensure LDAP server neutrality.
Access to the LDAP server is implemented via the LDAP adaptor of WebObjects 4.5 based on the EOF system. Since LDAP is fully integrated with EOF, the weblicon applications can establish relations between relational data and LDAP entries. The LDAP system is used for user authentication as well as storage of the user’s address books. Storage is derived from the standard LDAP class „inetOrgPerson”, while weblicon application suite-specific extensions are defined in a subclass.
go back
Location Based Services (LBS)
Location based services include all services, that are made possible with mobile phone subscriber’s geographic data. Taken the geographic position of a subscriber, any relevant information can be sent to the user’s mobile phone. As an example, the best Italian restaurant can be offered via WAP since the WAP gateway and its WAP server application can look for data depending on the subscribers coordinates. Today, some GSM network carriers supports geographic information about their customers and are introducing LBS e.g. for emergency calls in Switzerland or the US.
go back
Multiple-Access-Clients
Weblicon online organizer is currently available with 3 different clients to access centrally stored contact and schedule data via standard HTML browsers, WAP-capable mobile phones and through a high-end JAVA-client. The HTML-client is based on standard HTML 3.2, resulting in high compatibility with browsers, screen-phones or any HTML-capable device. The WAP-client supports any WML 1.1 capable cellular phone and can be accessed on several different models of various vendors.
As a future high-end solution, weblicon offers a highly interactive Java-client through a single applet. The Java-client provides drag and drop, immediate response, highlighting and double-click functionality. It offers modern ease-of-use currently known only to desktop applications. Weblicon’s intrinsic software design follows a highly generalized approach enabling additional front-ends to be added with relative ease.
go back
Multi-Tier-Architecture
The weblicon application suite is based on a multi-tier-architecture ensuring potentially unlimited scalability. In a multi-tier architecture, the clients (e.g. HTML browsers) communicate with a HTTP server layer which dispatches incoming requests towards the application server layer which communicates with multiple database servers. To achieve load balancing on the HTTP layer, usually a DNS round robin mechanism is used. On the application server layer, the WebObjects application server uses a round robin or load based mechanism to dispatch requests to multiple instances of the applications running on multiple application servers. The individual application instances communicate with various database servers (e.g. with Oracle 8i RDBMS for storing schedule and contact information or with a LDAPv3 server for storing hierarchical address or authentication information).
go back
ODBC
Open Database Connectivity (ODBC) is a widely accepted application programming interface (API) for database access. It is based on the Call-Level Interface (CLI) specifications from X/Open and ISO/IEC for database APIs and uses Structured Query Language (SQL) as its database access language.
go back
|
|
|
