After following the previous steps you should have an installable
image of your component, <componentName>.jar. There are
several ways to install your component in Openwings. Before continuing,
make sure the Openwings core is running (start it using ow.bat
or ow.csh) and bring up an explorer window (using owexplorer.bat
or owexplorer.csh).
One way you can install <componentName>.jar is to use the
install command in the explorer. You've already seen this method
in the Running the Demos section
of this tutorial.
Another way is to use Openwings' hotinstall feature. Copy <componentName>.jar
into the hotinstall folder inside the openwings-${VERSION}/ folder.
Openwings uses a detection mechanism that will detect the file
automatically and install it.
A third way to install components is to use the auto-install
mechanism in Openwings. Auto-install uses a file called autoinst.txt
to tell it what to install. If this file doesn't exist, you must
create it. It is a simple text file in which you list the installable
jar files that you want to install. This installation method was
provided should there exist a need to install many components
at one time.
To use autoinst.txt, indicate where the file can be found by
making an entry in the properties.txt file. (The properties.txt
file can be found in the policies folder in the openwings-${VERSION}/
folder. The location of the properties file was mentioned in the
Installation section of this
tutorial). Under the "#installer" heading, assign a
value to net.openwings.install.auto_install. For example, here
is a sample entry where the user chose to put autoinst.txt in
the policies directory of Openwings:
net.openwings.install.auto_install=${net.openwings.openwingshome}/policies
Next, you'll need to create and populate the contents of autoinst.txt.
Below are three examples of how to make entries in this file.
The first entry demonstrates a regular file URLfor a component.
The second entry represents an installable component relative
to where autoinst.txt resides. The last entry points to a component
that resides on a server.
file:/<installed openwings-${VERSION}>/demos/<componentName>.jar<componentName>.jarhttp://<http host>:<http port>/<net.openwings.install.inst_http_root>/<componentName>.jar
For example:
Once you have your autoinst.txt saved and have indicated its
location in the properties.txt file, Openwings will detect each
jar listed in the file and install it.
A fourth way to install components in Openwings is to write your
own Install Service. Most users won't need to consider this option.
Next: Running
Your Component
