The Unwired Server configuration
consists of
Java Virtual
Machine (JVM) startup options and Outbound Enabler Proxy
management,
which are
metadata-based
configuration.
All other components have been deprecated and are now performed on the
cluster.
The
metadata-based configurations have these characteristics:
- Each of these components is represented by ServerComponentVO.
- The properties of ServerComponentVO differentiate these components. See Developer Guide:
Unwired Server Runtime > Unwired Server Management API > Client
Metadata.
- Each instance of SUPServerConfiguration is a local object which holds values of
all metadata-based configurations. All of its methods perform against those
values. The values are refreshed when you call the commit()and refresh() methods.
After you receive an instance of SUPServerConfiguration, call the refresh() method to populate the values, before calling any other
methods.
- Changes made through these methods are cached locally unless the
commit() method is called. Commit() sends all the cached values (whether
changed or not) to the Unwired Server. A server restart may be required for some
changes to take effect.