|
Getting Started with RMI
This tutorial shows you the steps to follow to create a distributed version of the classic Hello World program using JavaTM Remote Method Invocation (RMI). While you work through this example, you will probably come up with a number of related questions.
|
|
Java RMI Tutorial
This is a brief introduction to Java Remote Method Invocation (RMI). Java RMI is a mechanism that allows one to invoke a method on an object that exists in another address space. The other address space could be on the same machine or a different one. The RMI mechanism is basically an object-oriented RPC mechanism.
|
|
Introduction to RMI
The Remote Method Invocation (RMI) application programming interface (API) enables client and server communications over the net between programs written in the JavaTM programming language. The Enterprise JavaBeansTM server transparently implements the necessary Remote Method Invocation (RMI) code so the client program can reference the Enterprise Beans running on the server and access them as if they are running locally to the client program.
|
|
Fundamentals of RMI
Remote Method Invocation (RMI) technology, first introduced in JDKTM 1.1, elevates network programming to a higher plane. Although RMI is relatively easy to use, it is a remarkably powerful technology and exposes the average Java developer to an entirely new paradigm--the world of distributed object computing
|
|
Creating a Custom RMI Socket Factory
This page shows you the steps to follow to create and install a custom RMI socket factory. A custom RMI socket factory is useful if (1) you want your RMI client and server to talk across sockets that encrypt or compress your data, or (2) you want to use different types of sockets for different connections.
|
|
The Remote Method Invocation (slides presentation )
|
|
JSR 000076
RMI Security
JSR Not Approved
Define a high-level API for network security in JavaTM 2 Standard Edition RMI, covering basic security mechanisms: authentication (including delegation), confidentiality, and integrity.
|
|
JSR-000066 J2METM RMI Profile
(Public Review closed November 6, 2000)
This draft is available for Public Review as per Section 3.1 of the Java Community ProcessSM Program.
|
|
Cape ClearTM Launches CapeConnectTM Two for J2EETM Early Access Program
6 March 2001, USA] Cape Clear Software announced today the availability of the alpha release of CapeConnect Two for J2EE through an Early Access Program (EAP). CapeConnect Two is the world's first Web Services Platform for Java™ 2 Platform, Enterprise Edition (J2EE) and Enterprise JavaBeans (EJB™). A Web Services Platform enables the creation, customization, and hosting of Simple Object Access Protocol (SOAP)-based services on the Internet.
|
|
Fundamentals of RMI
Short Course
By IGuru
This short course covers the fundamentals of the Remote Method Invocation (RMI) technology, as found in the Java 2™ platform.
|
|
Writing Advanced Applications
Chapter 4: Remote Method Invocation
The Remote Method Invocation (RMI) application programming interface (API) enables client and server communications over the net between programs written in the JavaTM programming language. The Enterprise JavaBeansTM server transparently implements the necessary Remote Method Invocation (RMI) code so the client program can reference the Enterprise Beans running on the server and access them as if they are running locally to the client program.
|
|
JAVATM REMOTE METHOD INVOCATION
The "Write Once, Run Anywheretm" Javatm Platform is a safe, flexible and complete cross-platform solution for developing robust Java applications for the Internet and corporate intranets. The Java language has distinguished itself from all previous object-oriented languages by providing unparalleled "ease-of-use" and portable code.
|
|
A New Approach to Distributed Computed
Provide a general framework in JavaTM 2 Standard Edition RMI for customizing remote invocation behavior.
|
|
JAVA REMOTE METHOD INVOCATION - DISTRIBUTED COMPUTING FOR JAVA
Java Remote Method Invocation (RMI) allows you to write distributed objects using Java. This paper describes the benefits of RMI, and how you can connect it to existing and legacy systems as well as to components written in Java.
|
|
Distributed Computing with Java Remote Method Invocation
J. Waldo: Good morning. My name is Jim Waldo. I'm an engineer with JavaSoft and I'm going to do the first half of a talk today about distributed computing, and in particular distributed computing with the Java Remote Method Invocation System. Actually, it really is two talks. The first is about distributed computing; the second is about remove method invocation. I'll do the distributed computing part. Ann Wollrath, who is the engineer who led the group that did the remote method invocation implementation, will do the second half of the talk.
|
|
Introduction to Java Remote Method Invocation (RMI)
This is a two-part series on the topic of Java's Remote Method Invocation (RMI). In this article I am going to discuss the basics of Java RMI (e.g., layers, rmic, registry, etc.) and how to apply and use it to develop distributed computing applications through examples. The second article discusses more advanced topics on Java RMI (e.g., CORBA IIOP and IDL, datagram packaging of Remote objects, distributed garbage collector, etc.).
|
|
A Detailed Comparison of CORBA, DCOM and Java/RMI
Distributed object computing extends an object-oriented programming system by allowing objects to be distributed across a heterogeneous network, so that each of these distributed object components interoperate as a unified whole. These objects may be distributed on different computers throughout a network, living within their own address space outside of an application, and yet appear as though they were local to an application.
|
|
JAVA REMOTE METHOD INVOCATION - DISTRIBUTED COMPUTING FOR JAVA
Java Remote Method Invocation (RMI) allows you to write distributed objects using Java. This paper describes the benefits of RMI, and how you can connect it to existing and legacy systems as well as to components written in Java.
|
|
Design networked applications in RMI using the Adapter design pattern
Creating a networked application is easy using Java's Remote Method Invocation. However, taking a non-networked class and jazzing it up for the network is definitely not the way to go. This will just lead to mess -- slow, hard to read, and difficult to maintain. Author Dan Becker demonstrates the proper way to adapt a local Java class for use over a network using the Adapter design pattern. This design technique creates an easy-to-maintain application that works extremely well
|
|
WEB-BASED SIMULATION IN SIMJAVA USING REMOTE METHOD INVOCATION
An investigation is underway regarding technologies to support the design, development and use of distributed, web-based simulations. As part of this investigation the Simjava simulation-support package has been extended to utilize the Remote Method Invocation facilities of the Java Development Kit (JDK) 1.1. Current efforts with Simjava are described and future research directions are outlined.
|
|
Java Servlets and Serialization with RMI
JavaTM RMI (remote method invocation) technology makes it very easy to create web-based applets that perform powerful server-side operations, such as accessing a database or communicating with remote server applications. However, a number of RMI limitations make its use in Internet-based applets impractical. This article describes a way to work around these limitations by using Java servlets and object serialization for applet/server communication, and demonstrates several ways to use this technique. The focus of this article is on converting an existing application, but the same design can used when creating new applications.
|
|
Write high-performance RMI servers and Swing clients
Learn how to supercharge your RMI servers by reducing the use of thread synchronization and implementing asynchronous callbacks via a configurable thread pool. Andy also demonstrates how to implement an efficient asynchronous logging facility and how to handle RMI callbacks to a Swing-based client application.
|
|
Write high-performance RMI servers and Swing clients
Behavior objects are among the most powerful, least known, and most underutilized RMI features. They represent the revolutionary capability to effortlessly pass true objects (data and code) between virtual machines without having to distribute the supporting class files. RMI makes this possible through dynamic class loading. This article examines RMI's built-in capability to dynamically load class files from remote machines to support passing behavior objects as RMI method parameters. Along the way, we'll develop a distributed Swing-based application that uses dynamic class loading to implement a distributed, multiuser drawing program
|
|
Subject-oriented programming through RMI
The move is on toward a kind of software that gives people in different locations the sense of being together in the same place. The notion of virtual community began in chat worlds and games, but is now becoming essential to many types of software that have traditionally isolated users from each other. As the network becomes the universe and the computer becomes the portal, we're beginning to view Net-unaware software as the strangely mute artifacts of another age. This article describes a straightforward design pattern based on Java's Remote Method Invocation (RMI). This pattern easily and generically facilitates building software for the shared experience
|
|
How to eliminate debugging problems for RMI-based applications
Debugging RMI-based programs -- a painful chore -- can be made vastly easier through the use of an in-process server mechanism that allows us to use any JDK 1.1-compatible debugger to develop RMI-based client/server code. This tip shows you how!
|
|
RMI and object serialization
Use Remote Method Invocation (RMI) to let applets store and retrieve objects on local disks
|
|
The RMI Activation Framework
To meet the OMG CORBA and Microsoft DCOM (Distributed Component Object Model) challenge, Sun Microsystems introduced RMI (Remote Method Invocation) in Java 1.1. Although it is easy to create, develop, and deploy distributed Internet applications using the Java RMI architecture, several shortcomings in RMI have been identified and debated since its introduction. One such shortcoming is that an RMI server has to be up and running at all times. There is no way to activate the RMI server when needed and on demand. However, such mechanisms have been available in both CORBA and DCOM.
|
|
Distributed Objects Programming
Using Java RMI
Developing Client/Server applications using sockets involves the design of a protocol that consists of a language agreed upon by the client and server. The design of protocols is hard and error-prone. One issue, for example, is deadlock. In a deadlock, processes never finish executing; these processes may be holding system resources, preventing other processes from accessing these resources.
|
|
Write high-performance RMI servers and Swing clients
Behavior objects are among the most powerful, least known, and most underutilized RMI features. They represent the revolutionary capability to effortlessly pass true objects (data and code) between virtual machines without having to distribute the supporting class files. RMI makes this possible through dynamic class loading. This article examines RMI's built-in capability to dynamically load class files from remote machines to support passing behavior objects as RMI method parameters. Along the way, we'll develop a distributed Swing-based application that uses dynamic class loading to implement a distributed, multiuser drawing program
|
|
Using WebLogic RMI over IIOP
WebLogic RMI over IIOP extends the RMI programming model by providing the ability for clients to access RMI remote objects using the Internet Inter-ORB Protocol (IIOP). This exposes RMI remote objects to a new class of client -- the Common Object Request Broker Architecture (CORBA) client. CORBA clients can be written in a variety of languages including C++ and Java.
|
|
RMI and Java Distributed Computing
The prospect of leveraging JavaTM technology for development of distributed applications has generated a great deal of attention among developers. This is not surprising, because the combination of the virtual machine (VM), portable secure bytecodes, and developer-friendly language semantics make the Java environment powerful and productive for distributed programming.
|
|
RMI , IIOP, and EJB
When Java first met CORBA, the outcome proved advantageous for both communities. The OMG/ CORBA community pounced on Java as a cleaner, more tractable, and ultimately more cost-eVective way to build many more CORBA applications than C++; it oVered Java programmers a robust distributed object infrastructure that leveraged battle-tested investments in CORBA technology and a clean way to exploit non-Java legacy assets.
|
|
Introduction to Java RMI
Remote method invocation allows applications to call object methods located remotely, sharing resources and processing load across systems. Unlike other systems for remote execution which require that only simple data types or defined structures be passed to and from methods, RMI allows any Java object type to be used - even if the client or server has never encountered it before. RMI allows both client and server to dynamically load new object types as required. In this article, you'll learn more about RMI.
|
|
Add persistence and peer-to-peer computing to Java applets hosted by Netscape 3.0.1
Learn how to use RMI as an alternative to cookies, CGI scripts, LiveScript, and hidden fields to add state to your Java applets
|
|
Battle Droids and RMI
A friend of mine was kind enough to get me a ticket to the premiere of The Phantom Menace, George Lucas' latest meal ticket. A big part of the plot, and of the movie's computer animation budget, went towards armies of robots (battle droids) that invade the peaceful green world of Naboo
|
|
Battle Droids and RMI
Design networked applications in RMI using the Adapter design pattern
|
|
Grinding Java
Distributed Java
When I first started writing for EDM I wrote to promote the usage of Java. I am a big Java advocate (DAH), and back then I felt that many people did not learn Java simply because there were very little "hands on" real world Java examples out there.
|
|
Java 1.2 extends Java's distributed object capabilities
The Java 1.2 platform allows you to build distributed object applications using two different methods -- the existing RMI and a new technology called Java IDL, which is a component of the Java Enterprise specification
|
|
RMI callbacks
Here's the short answer to your question. It isn't correct to say that the client method executes on the server. When using RMI to do callbacks to an application client, the client code doesn't execute on the application server.
|
|
Deciding Whether to Use RMI or IDL
Because they have similar purposes, RMI and Java IDL have some similar features and capabilities--as well as some differences. This section summarizes several of these similarities and differences to help you understand these technologies better and make choosing between them easier.
|
|
RMI over IIOP
With RMI and CORBA, programmers face a cruel choice: they must decide between RMI, with its easy programming features, and CORBA, with its broad interoperability. IBM and Sun, with the cooperation of the Object Management Group (OMG), jointly developed RMI over IIOP (RMI-IIOP) to solve this dilemma. With RMI-IIOP, programmers can create applications in RMI that include CORBA connections -- a big improvement. This article outlines the design elements of RMI-IIOP, its limitations, and how it can be used in real-world applications.
|
|
Beyond Java: Merging Corba-based Mobile Agents and WWW
The W3 is a very popular and still rapidly growing information system, but, strictly limited to client-server interaction, there are areas which are unsuitable to the current web techniques. "Mobile code" approaches like Java or the "interacting distributed objects" model of CORBA try to solve some of the disadvantages of the existing web, but they either lack a more general interaction and communication model (Java) or the possibilities to transfer code and the right distribution granularity (CORBA).
|
|
ActiveX/DCOM and Java/CORBA on the Web
This report from the Comparison and Evaluation Laboratory (CEL) of the Computer and Information Science department at Temple University compares distributed systems development approaches. The focus is on comparing the Microsoft DCOM (Distributed Component Object Model) with the Java + CORBA (Common Object Request Broker Architecture) approach in the context of web development.
|