System and method for using an RMI activation system daemon with non-JAVA applications

A system in a network providing remote invocation services supporting a first programming language, the system comprising:

• a remote invocation service activation system daemon, the remote invocation service activation system daemon providing persistence to a plurality of remote invocation services;
• a non-native application implemented in a second programming language, the second programming language being a programming language not supported by the remote invocation services, the non-native application including a startup sequence that is executed by the non-native application when the non-native application is started;
• a configuration file that is processed by the remote invocation service activation system daemon, the configuration file identifying the non-native application implemented in the second programming language;
• a virtual machine for the first programming language, the virtual machine started as part of the startup sequence of the identified non-native application and executed inside the identified non-native application, the identified non-native application configured to accept remote invocation service calls via a programming interface that enables code written in the first programming language to integrate with native applications;
• and
• a remote invocation service registry, the remote invocation service activation system daemon registering the identified non-native application in the remote invocation service registry as part of the startup sequence for the identified non-native application.

One or more computer-readable media holding computer-executable instructions for providing remote invocation services supporting a first programming language, the media holding one or more instructions for:

• providing a configuration file that is processed by a remote invocation service activation system daemon, the remote invocation service activation system daemon providing persistence to a plurality of remote invocation services, the configuration file identifying at least one non-native application implemented in a second programming language, the second programming language being a programming language not supported by the remote invocation services;
• as part of a startup sequence executed by the identified non-native application when the identified non-native application is started, starting a virtual machine for the first programming language inside the identified non-native application;
• configuring the identified non-native application to accept remote invocation service calls via a programming interface that enables code written in the first programming language running in the virtual machine to integrate with native applications;
• registering the identified non-native application in an remote invocation service registry with the remote invocation service activation system daemon as part of the startup sequence for the identified non-native 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 in a service registry that is processed by a system daemon that is part of the framework, the system daemon providing persistence to a plurality of services, the configuration file identifying a non-native application written in a second programming language, the second programming language different from the first programming language;
• and
• integrating the non-native application into the framework using the system daemon to register the non-native application with the framework as part of a startup sequence executed by the non-native application.