Abstract: The present invention describes a method for downloading application components, so-called on-card application components, from a server via a client to a chipcard, wherein the server and the client communicate with each other via a distributed system, in particular an Intranet or the Internet. The advantages of the present invention lie in the fact that downloading of the application components is divided into two stages: The first stage occurs on the server only, and ensures that not every command to download the application component is sent individually over the network. This is effected by means of a broadband-optimized protocol which bundles the individual commands to download the application component into a command sequence and sends it as a complete data packet over the network. This reduces the time required for downloading application components over the network. Each command within the command sequence is assigned a digital signature and, where appropriate, encrypted.

Abstract: The present invention provides a system and method for developing a Portal Application by creating a Portal Application Archive, and automatically deploying the Portal Application Archive into a Portal Server Application by using a Portal Application Archive specific deployment mechanism. The Portal Application Archive represents an entity which includes an assembly of all required application components forming a coherent Portal Application, and an application component assembly descriptor which specifies how the single application components need to be assembled to provide the complete Portal Application on the Portal Server Application.

Abstract: The present invention provides a method and system for allowing use of a Portal by Mobile Devices in a disconnected mode. The inventive system and method provide means to automatically create a Mobile Device specific content topology at the server side based on an existing user-defined connected content topology, user selectable options as well as dynamically changeable technical parameters, e.g. bandwidth, time, location, type of the target Mobile Device, downloads this Mobile Device specific content topology including its associated data to a target Mobile Device, and uses that Mobile Device specific content topology with its data by a local disconnected Portal frame work of a target Mobile Device in a disconnected mode. The Mobile Device specific content topology will be updated by a synchronization mechanism during connecting mode.

Abstract: The present discloses a framework that allows a synchronization engine to synchronize data between a mobile device and Back End data stores independently from the architecture and data formats of that Back End data store. The framework introduces content adapters, which access synchronization data from backend data systems. These adapters convert the data into a Back End data store independent representation, which can be used by all applications or modules which need to access different back-ends in a generic manner. A generic synchronization engine for the purpose of conflict detection and resolution is one example for a module of this kind. Other applications that could use the content adapter are Notification Frameworks or Portals and all other applications aggregating data.

Abstract: The present invention discloses a new synchronization architecture for synchronization of data between different clients by using a central synchronization server linked to a Back End data store which additionally provides a cache for permanently buffering incoming updates into a permanent store by assigning an unique cache identifier (ID). Write conflicts between the synchronization server writing new entries to the cache and updates replicated from backend to cache are solved using a blocking mechanism based on the cache IDs, so that the backend updates are blocked as long as incoming updates from the clients having the same cache ID are not completely written into the cache during a synchronization session. The present invention is preferably suited for a synchronization architecture having a high number of clients connected with the central synchronization server as blocking of the Back End data store, and the connection and the transport to the Back End data store are minimized.