Search Mailing List Archives
[protege-discussion] Collaborative Protege server set up solved (?)
tredmond at stanford.edu
Sun Jul 26 22:47:22 PDT 2009
This is guaranteed not to work outside your LAN. The reason is that,
if a client successfully connects to the rmiregistry then the client
will be told that the server can be found at 192.168.2.2 port 5300.
This address makes no sense on the internet and the connection will
You should know that it is quite possible that you will not be able to
get the server working on both the lan and outside the lan at the same
time. One way that you could succeed would be to use a name rather
than an ip address for the server. Then you can use dns so that on
the internet the address is 18.104.22.168 and on the lan the address
is 192.168.2.2. In other words, if the name
resolves to 22.214.171.124 on the internet but to 192.168.2.2 on the
lan then the hostname parameter
will work both on the lan and on the internet.
> The instructions for connecting to the server are clear either
> localhost (if on the machine where the server is installed) or the
> DNS name. The IP Address is not sufficient and will not connect to
> the server.
I don't know what this means. You can use either a name for the host
or an ip address.
I have drawn a diagram of how I think your network looks like below.
Note that the telnet test to 126.96.36.199 needs to be done outside
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 122473 bytes
Desc: not available
-------------- next part --------------
On Jul 19, 2009, at 6:39 AM, adam at wyner.info wrote:
> I appear to have solved the problems with the set up instructions
> for Collaborative Protege. But test me please.
> The instructions as they are inconsistent and confusing (to me and
> others) with respect to which ports to open and what host name to
> use. I figured it out by trial and error. I am working on a
> machine at home via a NAT router, but likely anyone who wants to use
> this behind a firewall (which would be everyone) will have similar
> issues. The localhost (the machine with Protege installed) is
> 192.168.2.2; the router address (the IP address on the web) is
> 188.8.131.52. Since I'm behind a firewall, I need to port
> forward. To experiment, I opened several ports on my router to port
> forward from the router to the localhost: 1098, 1099, 5200, 5300.
> The first two are defaults for rmiactivation and rmiregistry; I'm
> not sure if the rmiactivation needs to be opened; I'm not sure if I
> need 5200 open either any more. I've made changes in the startup
> script since it is clear from starting the server script that it is
> looking for the registry port of 1099, not 5200 as in some of the
> documentation. Finally, I was not clear what the server.hostname
> should be; now it seems that it should be the localhost address.
> My current run_protege_server.sh file has the following changes:
> PORTOPTS="-Dprotege.rmi.server.port=5300 -
> Running the script goes fine. From within my networ, I can open
> Protege > Open Project > Server > Login as Guest > pick a project
> (newspaper) > the project appears.
> Now the test is whether other people outside my LAN can login to the
> same projects and work with them.
> A crucial note. In order for people to collaborate on a project,
> they MUST HAVE THE SAME BUILD (this point was verified by Timothy
> Redmond). I have Version 3.4.1 (Build 537), which is the current
> build (as far as I know). If you have another build, this might not
> work. Please test it with the same build.
> To access my machine, I believe that you will have to follow the
> instructions on this page:
> At "Connect a Client to the Server", you need to enter the hostname
> for my router 184.108.40.206 (which should then port forward you to
> the network internal machine). Sign in as Guest with the guest
> password. Select newspaper. Let me know what happens. Fingers
> If this works, I'll next try WebProtege, which should avoid some of
> the build compatibility problems.
> protege-discussion mailing list
> protege-discussion at lists.stanford.edu
> Instructions for unsubscribing: http://protege.stanford.edu/doc/faq.html#01a.03
More information about the protege-discussion