The admin Object

2 min read

2 min read

2 min read

2 min read

2 min read

2 min read

2 min read

2 min read

2 min read

When the Administrative Facility is enabled, you can configure Ice to host an administrative object in the Ice.Admin object adapter, or you can programmatically host this object in your own object adapter.

In this documentation, we refer to the administrative object as the adminobject.

You can retrieve a proxy to the admin object associated with your communicator, if any, by calling getAdmin on this communicator.

An Ice object is a collection of sub-objects known as facets whose types are not related. Although facets are typically used for extending and versioning types, they also allow a group of interfaces with a common purpose to be consolidated into a single Ice object with an established interface for navigation. These qualities make facets an excellent match for the requirements of the administrative facility.

Each facet of the admin object represents a distinct administrative capability. The object does not have a default facet (that is, a facet with an empty name). However, the Ice runtime implements several built-in facets that it adds to the admin object:

An application can control which facets are installed with a configuration property. An application can also install its own facets if necessary. Administrative facets don’t inherit from a common Slice interface.