System and method for using an RMI activation system daemon with non-Java applications
AssigneeThe MathWorks, Inc.
InventorsMatthew Shawver, Jos Martin
Life of this patent
Estimating the term…
Abstract
An RMI (Remote Method Invocation) service framework that enables a non-Java application to be managed by an RMI activation system daemon is disclosed. The present invention enables the non-Java application to communicate with other Java applications that make use of RMI following a registration process. Additionally, because the non-Java application is managed by the RMI activation system daemon, the non-Java application displays a high degree of persistence and/or reliability ordinarily associated with RMI services. As a result, non-Java applications may be used to perform distributed and parallel computing tasks in a more efficient manner than is possible with conventional methods.
Claims25
In a network including RMI (Remote Method Invocation) services, a method comprising:
- providing a configuration file processed by an RMI activation system daemon, the configuration file identifying at least one non-Java application;
- starting a Java Virtual Machine (JVM) inside the identified non-Java application;
- configuring the non-Java application so that incoming RMI calls are delegated to the non-Java application via a Java Native Interface (JNI);
- and
- registering the non-Java application with the RMI activation system daemon as part of a startup sequence for the non-Java application.
A system in a network providing RMI (Remote Method Invocation) services, the system comprising:
- a configuration file processed by an RMI activation system daemon, the configuration file identifying at least one non-Java application;
- a Java Virtual Machine (JVM), the JVM executing inside the identified non-Java application, the non-Java application configured to accept RMI calls via a JNI (Java Native Interface);
- and
- an RMI activation system daemon, the RMI activation system daemon accepting a registration from the non-Java application as part of a startup sequence for the non-Java application.
In a network including RMI (Remote Method Invocation) services, a medium holding computer-executable steps for a method, comprising:
- providing a configuration file processed by an RMI activation system daemon, the configuration file identifying at least one non-Java application;
- starting a Java Virtual Machine (JVM) inside the identified non-Java application;
- configuring the non-Java application to accept RMI calls via a JNI (Java Native Interface);
- registering the non-Java application with the RMI activation system daemon as part of a startup sequence for the non-Java application.
In a network including remotely accessible services, a method comprising:
- providing a framework for managing distributed server processes written in a first programming language;
- providing a configuration file processed by a system daemon, the configuration file identifying an application written in a second programming language, the second programming language different from the first programming language;
- and
- integrating the application into the framework using the system daemon to register the application with the framework as part of a startup sequence for the application.
Dependencies are inferred from the claim text.