Download Openwings from here.
Select the installer appropriate for your platform and follow
the on-screen directions (If you encounter difficulties, download
the zip file and follow the manual installation instructions here).
During the install process, you will be asked to choose one
of four installation sets: Runtime, Development,
Runtime-Secure, or Development-Secure.
Runtime. The runtime installation provides the essentials
needed to run Openwings and Openwings components. Choose this
install set if you want Openwings to use a minimal amount of disk
space. To use the runtime installation, only the Java JRE is required
(the full SDK is fine too).
Development. The development installation provides everything
the runtime installation does, plus the tools a developer would
need to build new Openwings components. A build tool (Ant) is
included, as well as additional documentation for Openwings and
the bundled third-party tools. To use the development installation,
the full Java SDK is required.
Runtime-Secure and Development-Secure. To install Openwings
with secure connectors, choose one of these two installations.
Read this
tutorial trail for more detailed information on security features
in Openwings.
If you wish to make the Openwings core a boot time process on
your platform, and you are running Windows NT, 2000, or XP, you
will have the option of installing the core as a system service.
You must be the administrator of the machine for this option to
work.
Once the installation has completed, be sure to log out of your
system to allow environment variable changes to take effect.
 What's
There?
The installer will create a main Openwings home directory
(for example, C:\openwings or /usr/local/openwings). Each
subdirectory under this home directory represents a component.
Several bundled core components are installed statically,
such as jini. Later in the tutorial, we'll install
some additional components into the Openwings home directory.
|
Initially, Openwings home (also known as ${OW_HOME}) contains
the following:
- jakarta-ant - A cross-platform, open-source
compile tool from the Apache organization.
- jakarta-tomcat - A cross-platform, open-source
web server from the Apache organization. The root directory
for served documents is ./webapps/ROOT. The default port
used for this web server is 8880.
- jini - An open-source discovery mechanism
from Sun Microsystems.
- openwings-${VERSION} - This is where the
Openwings core resides.
The openwings-${VERSION}/ directory
contains the following:
- bin - This directory holds batch files and
shell scripts for running Openwings services. Once the core
is running, everything else can be started using platform-independent
policies (see Running
Your Component). This directory contains the following
important scripts:
- ow.bat, ow.csh - runs the Openwings core
services (container manager, install service, etc). If you're
running on a Windows platform, use the bat file. Use the
csh file on Unix platforms.
- owexplorer.bat, owexplorer.csh
- runs the Openwings explorer, a graphical tool that helps
you manage container managers, components, processes, and
contexts.
- owsh.bat, owsh.csh -
runs the Openwings shell, a legacy command-line tool that
allows many of the same operations as the Openwings explorer.
- owrun.bat, owrun.csh - Runs a component
outside of a container, based on its component descriptor.
- demos - This directory contains installable
jar files for the demo applications discussed in this tutorial.
- docs - This directory contains release notes,
javadocs, specifications, white papers, as well as this tutorial.
- hotinstall - This directory can be used to
install components in the Openwings core. Place install
Jars in this directory and they will be installed anytime the
install service is running.
- http - This directory contains files that
must be served from the local web server for the core.
- lib - This directory contains all of the
jar files that make up the core.
- policies - This directory contains policies
and properties for the core.
- src - This directory holds a jar file containing
the interface source code for the
net.openwings
packages.
Running
the Openwings Core
To run the Openwings core, execute the ow.bat
or ow.csh script in the bin directory.
|
Running
the Openwings Explorer
The Openwings Explorer is a graphical tool that is very
useful for installing and running components on Openwings.
Beginning in Openwings 1.1, the Explorer will start automatically
when the core is started. (To run the Openwings Explorer
separately, open a command-line window and execute the owexplorer.bat
or owexplorer.csh script in the bin directory).
|
Next: Running the
Demo Applications
