This guide provides the necessary information for installing Aglets Workbench.
Step 1. System Requirements
Aglets WorkBench requires you to have installed either of
JDK 1.1 or later
JDK 1.0.2 + RMI preBeta2
If you don't have these software installed on your machine, please Download these packages. Aglets Workbench with JDK1.0.2+RMI preBeta2 is qualified for SPARC/Solaris2.5, Windows95/NT. Aglets Workbench with JDK1.1 is qualified for SPARC/Solaris2.5, x86/Solaris(1.1beta4), Windows95/NT, AIX4.1.4(1.1FCS-beta).
For those platforms which have neither of them, like OS/2 or MacOS, Aglets Workbench provides ManualSerialization for temporary solution. To use ManualSerialization on these platforms, please refer to this and follows description for each platform. Aglets Workbench with JDK1.0.2+ManualSerialization is qualified for SPARC/Solaris2.5, x86/Solaris2.5, Windows95/NT, AIX4.1.4 and OS2 Warp4.
Note: If your environment is "JDK1.02 + RMI prebeta2", please make sure that rmi.zip file is specified before classes.zip in CLASSPATH setting.
To run Aglets Workbench, you need to two environment variable (AGLET_HOME and PATH).
(a) AGLET_HOME
The AGLET_HOME variable must be set to "Aglets" directory of the directory where you installed Aglets Workbench. If you unpacked the AWB package on the ROOT directory of drive C:, then it would need to be set as follows:
Example:
C:\> set AGLET_HOME=C:\AWB\Aglets
(b) PATH
Your system PATH variable must include the AWB\Aglets\bin subdirectory of the AWB installation (i.e., AGLET_HOME%\Aglets%\bin) to run.
Example:
C:\> set PATH=%AGLET_HOME%\bin;%PATH%
To develop an aglet program, you need further configuration. You need three additional environment variable (CLASSPATH, AGLET_PATH, AGLET_EXPORT_PATH) to compile your program and run it.
(c) CLASSPATH
The CLASSPATH variable must include the 'lib' directory where the Aglets library was installed.
Example:
C:\> set CLASSPATH=%AGLET_HOME%\lib;%CLASSPATH%
(d) AGLET_PATH
AGLET_PATH is the default look up path for creating the aglet with no codebase. This is used when the null value is passed to createAglet API on the AgletContext class as an codebase argument. For example, If you're going to place your aglet classes at C:\aglets\public, you could set it to this as follows.
Example:
C:\> set AGLET_PATH=C:\aglets\public
(e) AGLET_EXPORT_PATH
The AGLET_EXPORT_PATH is for files which can be fetched from remote site. In most case, this can be same as AGLET_PATH.
Example:
C:> set AGLET_EXPORT_PATH=%AGLET_PATH%
Note: If you are using Windows NT, you can make the changes above in the Control Panel. Start the Control Panel, select System icon, then edit the environment variables and apply.
SPARC/Solaris, x86/Solaris, AIX
To run Aglets Workbench, you need to two environment variable (AGLET_HOME and PATH).
(a) AGLET_HOME
The AGLET_HOME variable must be set to "Aglets" directory of the directory where you installed Aglets Workbench. If you unpacked the AWB package on the your $HOME directory, then it would need to be set as follows
Example:(csh)
% setenv AGLET_HOME=$HOME/AWB/Aglets
Example:(ksh)
% export AGLET_HOME=$HOME/AWB/Aglets
(b) PATH
Your system PATH variable must include the AWB\Aglets\bin subdirectory of the AWB installation (i.e., %AGLET_HOME%\Aglets%\bin) to run
Example: (csh)
% set path = ( $path $AGLET_HOME/bin )
Example: (ksh)
% export PATH=$PATH:$AGLET_HOME/bin
To develop an aglet program, you need further configuration. You need three additional environment variable (CLASSPATH, AGLET_PATH, AGLET_EXPORT_PATH) to compile you program and run it.
(c) CLASSPATH
The CLASSPATH variable must include the 'lib' directory where the Aglets library was installed.
Example:
C:\> set CLASSPATH=%AGLET_HOME%\lib;%CLASSPATH%
(d) AGLET_PATH
AGLET_PATH is the default look up path for creating the aglet with no codebase. This is used when the null value is passed to createAglet API on the AgletContext class as an codebase argument. For example, If you're going to place your aglet classes at C:\aglets\public, you could set it to this as follows.
Example:
C:\> set AGLET_PATH=<the directory where your aglets resides on>
(e) AGLET_EXPORT_PATH
The AGLET_EXPORT_PATH is for files which can be fetched from remote site. In most case, this can be same as AGLET_PATH.
Example:
C:> set AGLET_EXPORT_PATH=%AGLET_PATH%
OS/2
To run Aglets Workbench, you need to two environment variable (AGLET_HOME and PATH).
(a) AGLET_HOME
The AGLET_HOME variable must be set to "Aglets" directory of the directory where you installed Aglets Workbench. If you unpacked the AWB package on the ROOT directory of drive C:, then it would need to be set as follows
Example:
C:\> set AGLET_HOME=C:\AWB\Aglets
(b)PATH
Your system PATH variable must include the AWB\Aglets\bin subdirectory of the AWB installation (i.e., %AGLET_HOME%\Aglets%\bin) to run
Example:
C:\> set PATH=%AGLET_HOME%\bin;%PATH%
To develop an aglet program, you need further configuration. You need three additional environment variable (CLASSPATH, AGLET_PATH, AGLET_EXPORT_PATH) to compile you program and run it.
(c) CLASSPATH
The CLASSPATH variable must include the 'lib' directory where the Aglets library was installed.
Example:
C:\> set CLASSPATH=%AGLET_HOME%\lib;%CLASSPATH%
(d) AGLET_PATH
AGLET_PATH is the default look up path for creating the aglet with no codebase. This is used when the null value is passed to createAglet API on the AgletContext class as an codebase argument. For example, If you're going to place your aglet classes at C:\aglets\public, you could set it to this as follows.
Example:
C:\> set AGLET_PATH=<the directory where your aglets resides on>
(e) AGLET_EXPORT_PATH
The AGLET_EXPORT_PATH is for files which can be fetched from remote site. In most case, this can be same as AGLET_PATH.
Example:
C:> set AGLET_EXPORT_PATH=%AGLET_PATH%
MacOS
T.B.D.
Download JDK and related software
AgletsWorkbench requires JDK(Java Development Kit)1.1 iinstalled on your machine or JDK1.0.2 and RMI package installed on your mahcine. If you have neither of these packages, please download and install these packages by following the corresponding links in the following table. Make sure that these packages are installed properly by running the supplied demos and examples.
Assuming that you've downloaded the correct RMI package. Please unpack RMIpreBeta2 package. There should exists %RMI_HOME%\lib\rmi.zip (Win95/NT) or $RMI_HOMR/lib/rmi.zip file(Unix). Then, you need to modify CLASSPATH environment variable like:
