For a listing of bug fixes and enhancements included in
this release, please visit our bug database.
Explorer is now started automatically
When starting the container manager (ow.bat or ow.csh)
an instance of the Openwings Explorer is now started automatically.
This process is not managed by a container by default; you
can edit the InstallableComponentDescriptorPolicy for the
Explorer to change this.
Running as an NT Service
The Openwings InstallAnywhere installer supports the option
to install Openwings as a Windows NT service. This allows
you to run the Openwings core ("ow.bat") in the
background. You should be aware that there may be additional
steps to enable the service to be run after it is installed.
To check this, bring up the Services panel:
Windows NT: Start->Settings->Control Panel->Services
Windows 2000/XP: Start->Settings->Control Panel->Administrative
Tools->Services
Once the Services panel is open, find the "Openwings
Core" service and select "Edit Properties".
Select the "Log On" tab and make sure the following
settings are enabled:
- Enable it on the hardware profile
- Allow it to interact with desktop
Now the service may be started manually.
We have noticed an issue where a Java window (such as
the Openwings Explorer) must be already open before starting
the Openwings NT service! If not, you will not have success
displaying any Java GUI windows.
Other notes: The Openwings Core (The Container Manager)
generates log files for each process that it runs. These
log files are stored in the temporary directory, which is
identified by the property "java.io.tmpdir". The
setting of this property may change depending on what user
is executing a program. For this reason, when you run Openwings
as an NT service, the log files may end up in a different
location than you expect.
For example, the temp directory for a logged in user might
be:
C:\Temp (NT)
C:\Profiles\<username>\Local Settings\Temp
(2000)
C:\Documents and Settings\<username>\Local Settings\Temp
(XP)
While the Openwings Core service might have one of the
following temp directories since it is run as an administrator:
C:\Temp (NT)
C:\WINNT\Temp (2000)
C:\Windows\Temp (XP)
Note that the LogAccess service is always started by the
Container Manager, so it will always find log files for
the currently executing Openwings core.
Feature History
- 1.1
- Further enhancements to the Openwings Explorer (5865,
6719, 6888, 6893, 6974 in the bug
database)
- CD/ICD Editor interface reworked, defects 6699,
6835 fixed
- Windows setup program now optionally installs shortcuts
to commonly-used Openwings scripts
- Mac OS X is not yet an officially supported platform,
however, we can send a Mac installer to interested
parties. Contact
us if you are interested in testing Openwings
on OS X.
- 1.0
- Added platform support for Windows XP. Windows 98
is no longer supported.
- Java 1.4 or later is required: the security features
in this release won't work without it. Java 1.3 and
earlier are no longer supported.
- 0.9.2
- 0.9.1
- Install Openwings as an NT service on Windows NT/2000.
This option is available when installing Openwings.
- 0.9
- Default "openwings" component - simplifies
building components that depend on the Openwings core
- Diagnostic tool "owdiagnostic" - tests
visibility of core Openwings infrastructure across
platforms
- Java 1.3.1 and 1.4.0 support
- 0.8.x
- Cross platform compilation using Ant
- Platform independent ComponentDescriptors and InstallableComponentDescriptors
- Run tool ( owrun ) that allows ComponentDescriptors
and InstallableComponentDescriptors to be executed
outside a container.
- Platform Support
- Windows 98, Windows NT, Windows 2000
- Sparc Solaris 8
- Linux
- Java Properties (see Context
Services Notes)
- Shell Support (see Context
Services Notes)
- Policy Editors (see Management
Services Notes)
Known Issues
Future Releases
- Deployment Wizard
- Official Mac OS X support
