The Unwired Server configuration consists of the following components, which are all metadata-based configurations, except for Apple Push Notification Service:
- Communication
- Administration Listener
- HTTP / HTTPS Listener
- SSL Security Profile
- Key Store
- Trust Store
- Messaging
- Server
- Apple Push Notification
- Replication
- Server
- Push Notification
- Push Notification Gateway
- Pull Notification
- Consolidated DB
- Java Virtual Machine (JVM) startup options
- Apple Push Notification Service
The SUPServerConfiguration interface provides different methods for these components.
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 for 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.