Please Note: The GUI provided with this example is not a supported
product. It is a tool to assist you in the successful execution of
this example by limiting the amount of typing you have to do.
This GUI may or may not be included in future releases.
StartService
is a utility for launching the available services,
without having to use the
command-line documentation. As you launch each service,
the complete command-line invocation is printed out
in the window or shell from which the tool was started.
Start the GUI using the following command:
% java -cp /files/jini1_0/lib/jini-examples.jar com.sun.jini.example.service.StartService
Where /files
is the directory into which you extracted
the JiniTM software. The
-cp
option to the java
command specifies a
class path to search for class files. For more information on options
to the java
command, click here.
Note: If you get a stack trace
while trying to start the services, it could be the result of:
- The directories created by certain services are
still around from an unusual termination of the process. These
directories can be a result of having run any of the following
services:
- The RMI activation daemon,
rmid
- Reggie (Sun's Jini Lookup service implementation)
- Mahalo (Sun's Jini Transaction service implementation)
- Outrigger (Sun's JavaSpacesTM technology implementation )
- The services were started in the wrong order.
The correct order is:
- The RMI activation daemon,
rmid
- Reggie and/or the RMI registry
- Mahalo
- Outrigger
- The any clients wishing to use these services
- The services were started too quickly.
Depending on your system, some services will take some time to start
up. Try stopping any running services and starting over again, but
wait a few seconds in between each service invocation.
Jini Jar Files Tabbed Panel
This panel allows you to specify the location of the jar files
for the service(s) that you want to start.
- Path to Jar Files:
If you installed all the jar files in one location you can
specify the absolute path to that directory in this field.
There is no need then to type out the absolute path for each of
the services you will be starting.
If this field is not filled in, you can specify different
absolute paths to each jar file.
- URL to Client Jar Files:
If you installed all the jar files in one location you can
specify the URL to those jar files here.
There is no need to then type out the full URL for each
of the services that you will be starting.
If this field is not filled in, you can specify different
URLs for each jar file.
- Reggie Server Jar File:
Type in the path to the reggie.jar
file.
- Reggie Client Jar File URL:
Type in the path to the reggie-dl.jar
file.
- Mahalo Server Jar File:
Type in the path to the mahalo.jar
file.
- Mahalo Client Jar File URL:
Type in the path to the mahalo-dl.jar
file.
- Outrigger Server Jar File:
Type in the path to outrigger.jar
file if you want
to start a FrontEndSpace.
- Transient Outrigger Server Jar File:
Type in the path to the transient-outrigger.jar
file if you want to start a TransientSpace
.
- Outrigger Client Jar File URL:
Type in the path to the outrigger-dl.jar
file.
- Tools Jar File:
Type in the path to the tools.jar
file.
Note: You will not be able to start a JavaSpaces service unless
you have also downloaded and installed the 1.0 release of the
JavaSpacesTM Technology Kit (JSTK).
The files outrigger.jar
, outrigger-dl.jar
and
transient-outrigger.jar
are only available as part of the
JSTK.
Web Server Tabbed Panel
This panel allows you to configure a simple
HTTP server to be used for code downloading.
- Port:
The default httpd port is 8080. If you change this value in this
field don't forget to update the URL value(s) in the Jini Jar
Files panel.
- Top Level Web Document area:
This field represents the root directory of your web documents.
The default value is /vob/jive/jars.
- Download Files in Jars:
Selecting this checkbox specifies to the HTTP server that if it
gets a request for a specific class, rather than a jar file, it
should look for that class in all of the jar files in the web
document root directory. If it finds a jar file that contains
the requested class file, the server will make it available.
- Log downloads:
Selecting this checkbox will specify tothe HTTP server that it
should print out what gets served up to the window or shell from
which the tool was started.
Policy Files Tabbed Panel
This panel allows you to specify the location of the security policy file
for the service being started. Each of these policy files can
be different.
- Location of Txn Policy File:
This field allows you to specify the security policy file that
the transaction manager should use.
- Location of Spaces Policy File:
This field allows you to specify the security policy file that
the JavaSpaces service should use.
- Location of Lookup Policy File:
This field allows you to specify the security policy file that
the Jini Lookup service should use.
RMI Activation Tabbed Panel
This panel allows you to specify any optional
arguments to rmid
prior to start up.
- Optional switches:
This field can be used to pass any properties or options to
rmid
. For these examples, you should not have to
fill in this field.
Registry Services Tabbed Panel
This panel allows you to specify what type of registry service to use.
Currently, you can use either the RMI Registry or the Jini Lookup
service for Mahalo and Outrigger services.
- RMI Registry:
This button must be selected to
use the RMI registry.
- Registry Port:
This field allows you to
specify the port that should be used for RMI registry
lookup requests. If no port is specified, the value
defaults to 1099.
- Lookup Services:
This button must be selected to
use Jini Lookup services.
- Log Directory:
This field may be modified to
specify the absolute path to the log directory that
should be used by the Jini Lookup service.
- Lookup Groups:
This field allows you to specify
one or more lookup groups for the lookup service,
transaction manager and space to join. The default
value is "public"
.
- NONE:
This button allows you to deselect RMI registry
and Jini Lookup services. Note that the example code
will not work properly without running at least one of these
services.
Txn Manager Tabbed Panel
- Location of Txn LOG directory:
The absolute path to the directory that the transaction manager
should use for logging.
JavaSpaces Tabbed Panel
- JavaSpace Name:
The value in this field will be the name that will be used to
identify this space for client lookup requests. The default
value is JavaSpaces
.
- Space Type:
This choice button allows you to select either
"FrontEnd
", for a persistent space implementation,
or
"Transient
" a non-persistent space
implementation.
- Location of Persistent Dir:
This field may be modified to represent the location of a
persistence directory. If you are starting a
FrontEndSpace
then the absolute path
to the persistence directory is needed.
Note: You will not be able to start a JavaSpaces service unless
you have also downloaded and installed the 1.0 release of the JavaSpacesTM Technology Kit (JSTK).
Run it All Tabbed Panel
- Start Httpd Deamon and Stop Httpd Deamon
The "Start Httpd Deamon" button starts a simple web server. Make
sure the Web Server panel has been filled out.
- Start RMID and stop RMID
The "Start RMID" button starts the rmid
daemon.
- Start RMI Registry and Stop RMI Registry
The "Start RMI Registry" button starts an
rmiregistry
. These buttons will only be visible if the
registry has been selected in the Registry Services
panel.
- Start Lookup Service and Stop Lookup Service
The "Start Lookup Service" button starts a Jini Lookup service.
These buttons will only be visible if the Jini Lookup service has
been selected in the Registry Services panel. This
service needs rmid
up and running before it starts.
Information needed in order to start this service is also taken
from the Jini Jar Files panel.
- Start Txn Manager and Stop Txn Manager
Starts a Mahalo transaction manager. This service needs the following
support services running before it can be started:
- A wWeb server for code downloading
- An RMI Activation daemon,
rmid
- A registry service, either
rmiregistry
or a
Jini Lookup service
- Start Space and Stop Space
Starts a JavaSpaces service. This service needs the following
support services running before it can be started:
- A web server for code downloading
- An RMI Activation daemon,
rmid
- A registry service, either
rmiregistry
or a
Jini Lookup service
- A transaction manager
Note: You will not be able to start a JavaSpaces service unless
you have also downloaded and installed the 1.0 release of the
JavaSpacesTM Technology Kit (JSTK).
The files outrigger.jar
, outrigger-dl.jar
and
transient-outrigger.jar
are only available as part of the
JSTK.
Copyright © 1999 Sun
Microsystems, Inc. All Rights Reserved.
|