Abstract: An approach is provided for securing communication between a server computer and a client computer. A first string is sent to the client in response to a request to permit an application being executed by the client computer to access a first function. A second string that includes a parameter of a second function is received. The second string is a result of a conversion of the first string to a command and an execution of the command by the client. A result of an execution of the second function is matched with code information obtained from files of the application. Based on the match to the result of the execution of the second function and without requiring an implementation of native code which checks the authenticity of the application, the server validates the authenticity of the application and permits the application to access the first function.

Abstract: An approach is provided for securing communication between a server computer and a client computer. A first string is sent to the client in response to a request to permit an application being executed by the client computer to access a first function. A second string that includes a parameter of a second function is received. The second string is a result of a conversion of the first string to a command and an execution of the command by the client. A result of an execution of the second function is matched with code information obtained from files of the application. Based on the match to the result of the execution of the second function and without requiring an implementation of native code which checks the authenticity of the application, the server validates the authenticity of the application and permits the application to access the first function.

Abstract: An approach is provided for securing communication between a server computer and a client computer. A first string is sent to the client in response to a request to permit an application being executed by the client computer to access a first function. A second string that includes a parameter of a second function is received. The second string is a result of a conversion of the first string to a command and an execution of the command by the client. The second string is converted into a call to the second function. Using the call, the server executes the second function. Based on a result of the execution of the second function and without requiring an implementation of native code, the server determines whether to (i) permit the application to access the first function or (ii) prevent the application from accessing the first function.

Abstract: An approach is provided for securing communication between a server computer and a client computer. A first string is sent to the client in response to a request to permit an application being executed by the client computer to access a first function. A second string that includes a parameter of a second function is received. The second string is a result of a conversion of the first string to a command and an execution of the command by the client. The second string is converted into a call to the second function. Using the call, the server executes the second function. Based on a result of the execution of the second function and without requiring an implementation of native code, the server determines whether to (i) permit the application to access the first function or (ii) prevent the application from accessing the first function.

Abstract: A method and a corresponding system for managing non-MBeans (250) in the JMX architecture (215) are proposed. In the method of the invention, each non-MBean is supplied to a converter (255) that generates program code for defining a standard MBean (260m) implementing an interface (260i) named after itself. The interface exposes getter/setter methods, which are designed to return/assign corresponding public fields of the non-MBean. Moreover, the interface exposes methods for managing notifications (wrapping corresponding public methods of the non-MBean). Remaining public methods of the non-MBean are associated with corresponding operations of the MBean; support is also provided for relationships between non-MBeans. In this way, the MBean wraps the non-MBean making possible its management in the JMX architecture.

Abstract: A method and a corresponding system for managing non-MBeans (250) in the JMX architecture (215) are proposed. In the method of the invention, each non-MBean is supplied to a converter (255) that generates program code for defining a standard MBean (260m) implementing an interface (260i) named after itself. The interface exposes getter/setter methods, which are designed to return/assign corresponding public fields of the non-MBean. Moreover, the interface exposes methods for managing notifications (wrapping corresponding public methods of the non-MBean). Remaining public methods of the non-MBean are associated with corresponding operations of the MBean; support is also provided for relationships between non-MBeans. In this way, the MBean wraps the non-MBean making possible its management in the JMX architecture.