RMI Interface - Revision history

Kyle: /* Using Rifidi RMI Utils */

2009-05-18T19:09:49Z

‎Using Rifidi RMI Utils

Kyle: /* Using Rifidi RMI Utils */

2009-05-18T19:04:51Z

‎Using Rifidi RMI Utils

Kyle: /* Using Rifidi RMI Utils */

2009-05-18T18:56:48Z

‎Using Rifidi RMI Utils

Kyle: /* Using Rifidi RMI Utils */

2009-05-18T18:55:14Z

‎Using Rifidi RMI Utils

Kyle: /* Using native RMI */

2009-05-18T18:44:10Z

‎Using native RMI

Kyle: /* Using native RMI */

2009-05-18T18:42:06Z

‎Using native RMI

Kyle: /* Creating a Client */

2009-05-18T18:31:58Z

‎Creating a Client

Kyle at 18:21, 18 May 2009

2009-05-18T18:21:30Z

Kyle: New page: The Rifidi Edge Server exposes its functionality to clients via Remote Method Invocation (RMI). From the RMI homepage:
Java Remote Method Invocation (Java RMI) enables the pr...

2009-05-18T18:16:23Z

New page: The Rifidi Edge Server exposes its functionality to clients via Remote Method Invocation (RMI). From the RMI homepage: <blockquote> Java Remote Method Invocation (Java RMI) enables the pr...

New page

The Rifidi Edge Server exposes its functionality to clients via Remote Method Invocation (RMI). From the RMI homepage:
<blockquote>
Java Remote Method Invocation (Java RMI) enables the programmer to create distributed Java technology-based to Java technology-based applications, in which the methods of remote Java objects can be invoked from other Java virtual machines*, possibly on different hosts. RMI uses object serialization to marshal and unmarshal parameters and does not truncate types, supporting true object-oriented polymorphism.
</blockquote>
=Available RMI Stubs=
RMI stubs are objects that the server creates to handle remote method calls. The Rifidi Edge Server creates three stubs when it starts up, registers them under a given name in the RMI Registry, and registers the objects as services in the OSGi registry.
==EdgeServerStub==
This stub handles global Edge server functionality. It is registered in the RMI registry under the name <tt>ReaderStub</tt>
==ReaderStub==
==CommandStub==
=Creating a Client=
==Using native RMI==
==Using Rifidi RMI Utils==1

@@ Line 59: / Line 59: @@
 ==Using Rifidi RMI Utils==
-This example uses the <tt>org.rifidi.edge.core.rmi.client</tt> and <tt>org.rifidi.rmi.util</tt>, which provide [http://en.wikipedia.org/wiki/Command_pattern | Command Objects] around each available RMI call in the Edge Server's API.  This makes working with the API easier and enables stubs to be cached on the client side for performance reasons.  It is the recommended way of working with the Edge Server.
+This example uses the <tt>org.rifidi.edge.core.rmi.client</tt> and <tt>org.rifidi.rmi.util</tt>, which provide [http://en.wikipedia.org/wiki/Command_pattern Command Objects] around each available RMI call in the Edge Server's API.  This makes working with the API easier and enables stubs to be cached on the client side for performance reasons.  It is the recommended way of working with the Edge Server.
-< pre>
+<pre>
 import org.rifidi.edge.core.rmi.client.edgeserverstub.ESGetStartupTimestamp;
 import org.rifidi.edge.core.rmi.client.edgeserverstub.ESServerDescription;
@@ Line 94: / Line 94: @@
+}
 </pre>

@@ Line 59: / Line 59: @@
 ==Using Rifidi RMI Utils==
-<pre>
+This example uses the <tt>org.rifidi.edge.core.rmi.client</tt> and <tt>org.rifidi.rmi.util</tt>, which provide [http://en.wikipedia.org/wiki/Command_pattern | Command Objects] around each available RMI call in the Edge Server's API.  This makes working with the API easier and enables stubs to be cached on the client side for performance reasons.  It is the recommended way of working with the Edge Server.
 import org.rifidi.edge.core.rmi.client.edgeserverstub.ESGetStartupTimestamp;
 import org.rifidi.edge.core.rmi.client.edgeserverstub.ESServerDescription;

@@ Line 60: / Line 60: @@
 ==Using Rifidi RMI Utils==
 <pre>
 /**
   * Demonstrate how to make an RMI call to the Edge Server using the Command

← Older revision		Revision as of 18:55, 18 May 2009
Line 59:		Line 59:

	==Using Rifidi RMI Utils==		==Using Rifidi RMI Utils==
		+	<pre>
		+	/**
		+	* Demonstrate how to make an RMI call to the Edge Server using the Command
		+	* wrapper around RMI calls
		+	*
		+	* @author Kyle Neumeier - kyle@pramari.com
		+	*
		+	*/
		+	public class RMITestCommandObjects {
		+
		+	/**
		+	* @param args
		+	* - none
		+	*/
		+	public static void main(String[] args) {
		+	// create a new server description object
		+	ESServerDescription serverDescription = new ESServerDescription(
		+	"127.0.0.1", 1098);
		+	// create a new command object
		+	ESGetStartupTimestamp getStartupTimeCall = new ESGetStartupTimestamp(
		+	serverDescription);
		+	try {
		+	// make the RMI call
		+	System.out.println(getStartupTimeCall.makeCall());
		+	} catch (ServerUnavailable e) {
		+	e.printStackTrace();
		+	}
		+	}
		+	}
		+	</pre>

@@ Line 14: / Line 14: @@
 ==Using native RMI==
 <pre>
 import java.rmi.NotBoundException;

← Older revision		Revision as of 18:42, 18 May 2009
Line 14:		Line 14:

	==Using native RMI==		==Using native RMI==
		+	<pre>
		+	import java.rmi.NotBoundException;
		+	import java.rmi.Remote;
		+	import java.rmi.RemoteException;
		+	import java.rmi.registry.LocateRegistry;
		+	import java.rmi.registry.Registry;
		+
		+	import org.rifidi.edge.core.api.rmi.EdgeServerStub;
		+
		+	/**
		+	* An example Edge Server RMI Client
		+	*
		+	* @author Kyle Neumeier - kyle@pramari.com
		+	*
		+	*/
		+	public class RMITest {
		+
		+	/**
		+	* Main method. Looks up stub and makes a call
		+	*
		+	* @param args
		+	* - none
		+	*/
		+	public static void main(String[] args) {
		+	try {
		+	// obtain a reference to the RMI registry
		+	Registry registry = LocateRegistry.getRegistry("127.0.0.1", 1098);
		+	// look up the stub on the regsitry
		+	Remote remoteObject = registry.lookup("EdgeServerStub");
		+	if (remoteObject instanceof EdgeServerStub) {
		+	// if the stub is the correct type, make the call
		+	EdgeServerStub stub = (EdgeServerStub) remoteObject;
		+	System.out.println(stub.getStartupTime());
		+	}
		+	} catch (RemoteException e) {
		+	e.printStackTrace();
		+	} catch (NotBoundException e) {
		+	e.printStackTrace();
		+	}
		+	}
		+	}
		+	</pre>
		+
	==Using Rifidi RMI Utils==		==Using Rifidi RMI Utils==

@@ Line 12: / Line 12: @@
 This stub handles all calls related to commands, such as creating and deleting CommandConfigurations and changing CommandConfiguration properties.  It is registered in the RMI registry under the name <tt>CommandStub</tt>.  For more information see <link to Javadoc>
 =Creating a Client=
 ==Using native RMI==
 ==Using Rifidi RMI Utils==

@@ Line 6: / Line 6: @@
 RMI stubs are objects that the server creates to handle remote method calls.  The Rifidi Edge Server creates three stubs when it starts up, registers them under a given name in the RMI Registry, and registers the objects as services in the OSGi registry.
 ==EdgeServerStub==
-This stub handles global Edge server functionality. It is registered in the RMI registry under the name <tt>ReaderStub</tt>
+This stub handles global Edge server functionality, such as saving configurations. It is registered in the RMI registry under the name <tt>EdgeServerStub</tt>. For more information see <link to Javadoc>
 ==ReaderStub==
 ==CommandStub==
 =Creating a Client=
 ==Using native RMI==
-==Using Rifidi RMI Utils==1
+==Using Rifidi RMI Utils==

RMI Interface - Revision history

Kyle: /* Using Rifidi RMI Utils */

Kyle: /* Using Rifidi RMI Utils */

Kyle: /* Using Rifidi RMI Utils */

Kyle: /* Using Rifidi RMI Utils */

Kyle: /* Using native RMI */

Kyle: /* Using native RMI */

Kyle: /* Creating a Client */

Kyle at 18:21, 18 May 2009

Kyle: New page: The Rifidi Edge Server exposes its functionality to clients via Remote Method Invocation (RMI). From the RMI homepage: Java Remote Method Invocation (Java RMI) enables the pr...

Kyle: New page: The Rifidi Edge Server exposes its functionality to clients via Remote Method Invocation (RMI). From the RMI homepage:
Java Remote Method Invocation (Java RMI) enables the pr...