Where should the interface be? (extending the Remote interface)?

Question

Hello,
I've created a simple rmi server on one machine, sonsisting of two files:
OkServer.java:
import java.rmi.Remote;
import java.rmi.RemoteException;
public interface OkServer extends Remote {
public String getOk() throws RemoteException;
}OkServerImpl.java:
import java.rmi.Remote;
import java.rmi.RemoteException;
public interface OkServer extends Remote {
public String getOk() throws RemoteException;
}and on another machine, I've created a client:
import java.rmi.RMISecurityManager;
import java.rmi.Naming;
public class OkClient {
public static void main (String args[]) throws Exception {
     if (args.length != 1)
     throw new RuntimeException("Syntax: OkClient <hostname>");
     System.setSecurityManager(new RMISecurityManager());
     OkServer OkSvr = (OkServer)Naming.lookup("rmi://" +
                              args[0] + "/OkServer");
     String when = OkSvr.getOk();
     System.out.println(when);
}Now the problem is, when I try to compile the client (only consisting the file above),
it says of course:
OkClient.java:36: cannot find symbol
symbol : class OkServer
}This is normal, right?
Then, I should copy the interface (that is also at the server) to the client machine?
So the interface file HAS TO BE on both the server and the client????

Answer 1

If you want to install OVM with the production option then you will basically need three distinct hosts:
a) the database host, where you install SE/EE on (XE is not for production use and not supported for production use!)
b) install OVM Manager on any computer running OEL 5 (or later)
c) install OVM Server on a bare metal host who's hardware is supported
As far as the SE/EE license goes: Oracle always allows anyone to download and install their software to try it out. If you are putting your setup into production, that is not covered and demands an support contract with Oracle. And from using Oracle for many years, there will come the day when you will need it… ;)
So long story short: grab the Oracle SE/EE installation and be familiar with it - Oracle DB that is, otherwise you'll be sitting there pulling your hair out and yell at your computer.
Or, try the not yet released 3.2.x version of OVMM with runs against MySQL - most likely the easy way to go.