Abstract: Methods, computing devices and computer programs are disclosed. A method comprises assembling an executable image file, for execution as a software container element, from a plurality of predefined modular image files, each predefined modular image file comprising at least one layer defining executable instructions.

Abstract: A method, a computing device and a computer program is disclosed. A method comprises, by at least one software container element that contains executable software that is executable on one or more processors of a computing device, receiving, from a kernel of the computing device, first data that is indicative of at least one active driver installed on the kernel, comparing the first data with second data that is indicative of at least one predetermined target driver that should be installed on the kernel, and responsive to the comparing, determining if at least one of the predetermined target drivers is not installed on the kernel.

Abstract: A method, a computing device and a computer program is disclosed. A method comprises receiving, from a module comprising first executable software that is executable on one or more processors of a computing device, first data indicative of at least one class of peripheral device connectable to the computing device, whereby each class is associated with a plurality of predetermined peripheral devices and providing a software container element that contains second executable software that is executable on said one or more processors of the computing device, whereby the software container element is associated with peripheral device connection data that enables the software container element to have access to and communicate with each peripheral device of the plurality of predetermined peripheral devices associated with each class.

Abstract: A virtualized transaction terminal platform is provided. A transaction terminal is configured as a thin-client terminal. A virtualized transaction terminal (Virtual Machine (VM)) is instantiated remotely on a cloud or a server over a network connection. Peripherals connected to the thin-client terminal are mapped to virtual peripheral device drivers on the cloud or the server. Physical peripherals connected to the thin-client terminal are mapped inside the VM to the corresponding virtual peripheral device drivers. As transactions are initiated and physical peripherals are operated at the thin-client terminal, the transactions are processed by the VM and inputs/outputs from the physical peripherals are forwarded for processing by the corresponding virtual peripheral device drivers. A remote desktop (RD) agent on the thin-client terminal keeps states of the VM and virtual peripheral device drivers in synchronization with a peripheral display of the thin-client terminal.

Abstract: Workload Images comprising one or more artifacts are managed in a decentralized and centralized manner. Local management comprises breaking any image/artifact into blocks, encrypting each block with a key known and available only to the local processing environment, and uniquely signing each encrypted block. Published versions of the images/artifacts are retained remotely in a cloud/server in encrypted and signed block format. When retrieval, modification, addition, deletion, and deployment of any given image/artifact is needed, the target device/server that is to receive the image/artifact provides a listing of encrypted blocks with the corresponding signatures that are already present on that device/server and a centralized cloud/server schedules and manages download of just those encrypted blocks that are missing to the target device/server.

Abstract: A virtualized transaction terminal platform is provided. A transaction terminal is configured as a thin-client terminal. A virtualized transaction terminal (Virtual Machine (VM)) is instantiated remotely on a cloud or a server over a network connection. Peripherals connected to the thin-client terminal are mapped to virtual peripheral device drivers on the cloud or the server. Physical peripherals connected to the thin-client terminal are mapped inside the VM to the corresponding virtual peripheral device drivers. As transactions are initiated and physical peripherals are operated at the thin-client terminal, the transactions are processed by the VM and inputs/outputs from the physical peripherals are forwarded for processing by the corresponding virtual peripheral device drivers. A remote desktop (RD) agent on the thin-client terminal keeps states of the VM and virtual peripheral device drivers in synchronization with a peripheral display of the thin-client terminal.

Abstract: A virtualized transaction terminal platform is provided. A transaction terminal is configured as a thin-client terminal. A virtualized transaction terminal (Virtual Machine (VM)) is instantiated remotely on a cloud or a server over a network connection. Peripherals connected to the thin-client terminal are mapped to virtual peripheral device drivers on the cloud or the server. Physical peripherals connected to the thin-client terminal are mapped inside the VM to the corresponding virtual peripheral device drivers. As transactions are initiated and physical peripherals are operated at the thin-client terminal, the transactions are processed by the VM and inputs/outputs from the physical peripherals are forwarded for processing by the corresponding virtual peripheral device drivers. A remote desktop (RD) agent on the thin-client terminal keeps states of the VM and virtual peripheral device drivers in synchronization with a peripheral display of the thin-client terminal.

Abstract: Workload Images comprising one or more artifacts are managed in a decentralized and centralized manner. Local management comprises breaking any image/artifact into blocks, encrypting each block with a key known and available only to the local processing environment, and uniquely signing each encrypted block. Published versions of the images/artifacts are retained remotely in a cloud/server in encrypted and signed block format. When retrieval, modification, addition, deletion, and deployment of any given image/artifact is needed, the target device/server that is to receive the image/artifact provides a listing of encrypted blocks with the corresponding signatures that are already present on that device/server and a centralized cloud/server schedules and manages download of just those encrypted blocks that are missing to the target device/server.

Abstract: A virtualized transaction terminal platform is provided. A transaction terminal is configured as a thin-client terminal. A virtualized transaction terminal (Virtual Machine (VM)) is instantiated remotely on a cloud or a server over a network connection. Peripherals connected to the thin-client terminal are mapped to virtual peripheral device drivers on the cloud or the server. Physical peripherals connected to the thin-client terminal are mapped inside the VM to the corresponding virtual peripheral device drivers. As transactions are initiated and physical peripherals are operated at the thin-client terminal, the transactions are processed by the VM and inputs/outputs from the physical peripherals are forwarded for processing by the corresponding virtual peripheral device drivers. A remote desktop (RD) agent on the thin-client terminal keeps states of the VM and virtual peripheral device drivers in synchronization with a peripheral display of the thin-client terminal.

Abstract: Disclosed is a method of updating software in a computer system using virtualization software, wherein one or more virtual machines are arranged to run respective software modules for providing respective set of software services. A software update relating to a first software module running in a first virtual machine is received. The first software module is stored on a first storage entity associated with the first virtual machine. A copy of the first storage entity is updated in accordance with the received software update to produce a second storage entity containing an updated version of the first software module. A second virtual machine is created within the virtualization environment. The second virtual machine is associated with the second storage entity and arranged to run the updated version of the software module from the second storage entity. The first virtual machine remains operational during the updating step.