There are several installation methods
that can be used when you install your component:
-
The Openwings Explorer
- The Openwings shell
-
Hot Install
-
Auto Install
-
Programmatically
The Explorer
A discussion of how to install components in the explorer can
be found in Getting
Started or in the Explorer
tutorial trail.
The Shell
After bringing up the Openwings shell, simply key in the command
“install <componentName.jar>” on the command line.
Of particular note is the opportunity to install a component
from another Openwings enabled platform. Consider the case
where a component installed with the
ServeHint enabled. This is a field in the
InstallableComponentDescriptor. Anyone can then install that
component by simply entering on the command line the install command
and the http URL. An example is given:
install
http://A00-JK0001:8880/install/HelloWorldProvider_im-0.1/HelloWorldProvider_im.jar
Hot Install
Just copy <componentName>.jar into the hotinstall folder
of Openwings. This folder can be found in:
<OW_HOME>/openwings-${VERSION}/hotinstall
The Openwings install service looks for files in that directory,
and when any are found they are installed and then deleted.
Auto Install
Another way is to use the auto-install mechanism in Openwings.
An autoinst.txt file contains a list of components to install.
This feature can be used to make plug and play software service
packs.
To enable autoinstall you must indicate where the file
can be found by making an entry the properties file. The properties
file can be found in the policies directory of Openwings, (<OW_HOME>/openwings-${VERSION}/policies/properties.txt).
The properties file was discussed in the Installation
section of this tutorial. Under “#installer” in the properties.txt
file, assign a value to net.openwings.install.auto_install. For
example, here is a sample entry that would look for installable
jars on removable media on drives d and e of a windows system:
net.openwings.install.auto_install=d:\\ e:\\
Next, you’ll need to create and populate the
contents of autoinst.txt. Below is a sample of how to make auto
install entries. The first entry demonstrates a regular file url
for a component. The second entry represents an installable
component relative to where openwings resides. The last entry
is a component that is on a server.
- file:/<OW_HOME>/openwings-${VERSION}/demos/<componentName>.jar
- <componentName>.jar
- http://<hostname>:<httpport>/<net.openwings.install.inst_http_root>/<componentName>.jar
For example:
file:/d:/openwings-1.0/demos/HelloWorldProvider_im.jar
HelloWorldUser_im.jar
http://SAMPLEHOST:8880/install/HelloWorldServiceSync_im.jar
You can place the autoinst.txt file and installable jars on
removable media and plug them into your system. As soon as
the system detects the media it will install your
components. If you components are marked to run immediately
they will execute also.
Programmatically
A fourth way to install components on to Openwings is to discover
an install service and use it programmatically. The javadocs
for the Install
interface are here. Here
is an example of looking up the install service for a particular
platform.
So now you have installed your component.
What do I do if my component does not resolve?
After a component is installed it should reach a
RESOLVED state. (see
dependency resolution for more details). There are several
reasons why a component may not reach a resolved state:
