[CompStrm Wiki] How to run rmiregistry
Status: Beta
Brought to you by:
blaforge
From: Bill la F. <laf...@ya...> - 2006-05-09 00:18:25
|
When running AwServer locally, you MUST first start the rmiregistry with the appropriate classpath. Here we will just focus on the rmiregistry. I never run this program from within NetBeans. It is run in a separate window (I'm assuming windoz.) So, you have downloaded AgileWiki3-alpha21.zip and unzipped it. The top-level directory is AgileWiki3. Now there is a file there that you should delete immediately: AgileWiki.properties. This file will cause the client program(s) to access the remote server--but we want to work with a local server. Now you will see the file startRegistry.bat. It contains the following: set classpath=AwCommon\dist\AwCommon.jar rmiregistry You can run this from a DOS box, double click on it, or even create a shortcut to it. The rmiregistry program is included with java. The important thing here is to first set the classpath. YOU MUST LEAVE RMIREGISTRY RUNNING. The server, at startup, connects to the registry to identify itself. The client(s), at startup, connect to the registry to locate the server. Generally the rmiregistry uses port 1099 by default. You can give a different port number when you start it, but then you must tell the server and clients about this new portnumber. One last thing. The rmiregistry must be running on the same computer as the server. This is a security restriction. Clients are not under such a restriction. Only a client must be able to communicate with the rmiregistry where the server is running and (via a separate port number) with the server. --------------------------------- Yahoo! India Answers: Share what you know. Learn something new. Click here Send instant messages to your online friends - NOW |