Abstract: Joystick chair is an input device for interaction between the user and computer. It enables the movement of the user in games. The invention is used by placing feet on the platform (3) and sitting or leaning on the seat (23). Command for turning is achieved by rotating the seat (23), either to the left or to the right. Command for forward movement is issued by pulling the left or right controller (36, 41) with fingers, while the command for backward movement is issued by pushing the left or right controller (36, 41) away by palms. Control handles for lateral movement (49, 56) are separated from the forward-back controls that are located on the controllers (36, 41). Other commands are achieved with buttons on the left and right controller and they are accessible with thumbs. The software allows the modifications of all available actions of the invention.

Abstract: This disclosure describes a method of and system for provisioning of shared account credentials to provide authorized access to shared or delegated accounts. Preferably, an enterprise single sign-on (E-SSO) system is used to manage the shared account or control delegation of account access, and preferably the shared or delegated account credential is not exposed to the end user. The described technique enables temporary delegation of account privileges to a member of a shared role. Using the described approach, an information technology (IT) account may be shared so that a user who needs to perform a shared duty can do so in the context of a shared role and without having control over the account itself. The approach facilitates delegating the use of a single account to one of a member of the shared role.

Abstract: A mechanism for the deployment of asynchronous agentless agent functionality in clustered environments. An agentless agent execution node in an agentless agent execution node cluster receives a context message comprising an asynchronous operation request and an execution context from a messaging service. The agent node determines if an entry for the execution context exists in an execution context state table of the agent node. If no entry exists, the agent node creates an execution context entry in the execution context state table of the agent node. The agent node retrieves an asynchronous code module associated with the asynchronous operation from a central repository. The asynchronous code module is then executed on a managed resource to detect asynchronous code events occurring on the managed resource. When asynchronous code events are detected at the managed resource, the agent node sends a message comprising the asynchronous code events to a management server.

Abstract: This disclosure describes a method of and system for provisioning of shared account credentials to provide authorized access to shared or delegated accounts. Preferably, an enterprise single sign-on (E-SSO) system is used to manage the shared account or control delegation of account access, and preferably the shared or delegated account credential is not exposed to the end user. The described technique enables temporary delegation of account privileges to a member of a shared role. Using the described approach, an information technology (IT) account may be shared so that a user who needs to perform a shared duty can do so in the context of a shared role and without having control over the account itself. The approach facilitates delegating the use of a single account to one of a member of the shared role.

Abstract: A method for automatically removing a user from an e-mail thread is provided. An e-mail client receives a reply e-mail message. Responsive to a determination that the reply e-mail message is a message to opt-out of an e-mail thread, the e-mail address of a sender of the reply e-mail message is associated with the e-mail thread to form a listed e-mail address. The listed e-mail address is stored. When a new e-mail message is generated that is part of the e-mail thread, the listed e-mail address is automatically excluded from a list of recipients of the new e-mail.

Abstract: A method for automatically removing a user from an e-mail thread is provided. An e-mail client receives a reply e-mail message. Responsive to a determination that the reply e-mail message is a message to opt-out of an e-mail thread, the e-mail address of a sender of the reply e-mail message is associated with the e-mail thread to form a listed e-mail address. The listed e-mail address is stored. When a new e-mail message is generated that is part of the e-mail thread, the listed e-mail address is automatically excluded from a list of recipients of the new e-mail.

Abstract: In contrast to prior data synchronization processes, provided by aspects of the invention are systems, methods and software programs implementing a data synchronization process that employs a high-level interface of a respective data repository to extract valid information from the data repository in response to low-level changes in the data repository. In specific embodiments of the invention, the synchronization process is implemented within an adaptor interposed between a management system and a database system that serves as a middle-ware operable to link a respective data store interface, within a management system, to a respective managed platform, within the database system, so that the native API's of each can be employed in the operation of the data synchronization process.

Abstract: Embodiments of the present invention provide a method, system and computer program product for de-centralized nodal failover handling in a high availability computing architecture. The system can include multiple different nodes coupled to one another in a cluster over a computer communications network including an initial lead node and remaining auxiliary nodes. The system further can include a messaging service coupled to each of the nodes and nodal failover handling logic coupled to each of the nodes and to the messaging service. The logic can include program code enabled to periodically receive heartbeat messages from the messaging service for the initial lead node and to subsequently detect a lapse in the heartbeat messages, to post within a message to the messaging service a request to become a replacement lead node in response to detecting the lapse in the heartbeat messages, and to periodically post heartbeat messages to the messaging service as the replacement lead node for the initial lead node.

Abstract: A mechanism for the deployment of asynchronous agentless agent functionality in clustered environments. An agentless agent execution node in an agentless agent execution node cluster receives a context message comprising an asynchronous operation request and an execution context from a messaging service. The agent node determines if an entry for the execution context exists in an execution context state table of the agent node. If no entry exists, the agent node creates an execution context entry in the execution context state table of the agent node. The agent node retrieves an asynchronous code module associated with the asynchronous operation from a central repository. The asynchronous code module is then executed on a managed resource to detect asynchronous code events occurring on the managed resource. When asynchronous code events are detected at the managed resource, the agent node sends a message comprising the asynchronous code events to a management server.

Abstract: Identity Management (IdM) systems prevent a user from having to memorize numerous passwords for different resources, while Single Sign-On (SSO) systems allow a user to login to several resources by providing login credentials once. Since IdM systems propagate the same password to numerous resources, a compromised password for one resource would allow unauthorized access to all resources. A system can automatically generate unique passwords for each of a plurality of resources and update login information on each resource to reflect the unique password.

Abstract: Embodiments of the present invention provide a method, system and computer program product for de-centralized nodal failover handling in a high availability computing architecture. The system can include multiple different nodes coupled to one another in a cluster over a computer communications network including an initial lead node and remaining auxiliary nodes. The system further can include a messaging service coupled to each of the nodes and nodal failover handling logic coupled to each of the nodes and to the messaging service. The logic can include program code enabled to periodically receive heartbeat messages from the messaging service for the initial lead node and to subsequently detect a lapse in the heartbeat messages, to post within a message to the messaging service a request to become a replacement lead node in response to detecting the lapse in the heartbeat messages, and to periodically post heartbeat messages to the messaging service as the replacement lead node for the initial lead node.

Abstract: A method for automatically removing a user from an e-mail thread is provided. An e-mail client receives a reply e-mail message. Responsive to a determination that the reply e-mail message is a message to opt-out of an e-mail thread, the e-mail address of a sender of the reply e-mail message is associated with the e-mail thread to form a listed e-mail address. The listed e-mail address is stored. When a new e-mail message is generated that is part of the e-mail thread, the listed e-mail address is automatically excluded from a list of recipients of the new e-mail.

Abstract: In contrast to prior data synchronization processes, provided by aspects of the invention are systems, methods and software programs implementing a data synchronization process that employs a high-level interface of a respective data repository to extract valid information from the data repository in response to low-level changes in the data repository. In specific embodiments of the invention, the synchronization process is implemented within an adaptor interposed between a management system and a database system that serves as a middle-ware operable to link a respective data store interface, within a management system, to a respective managed platform, within the database system, so that the native API's of each can be employed in the operation of the data synchronization process.