Collective Controller
The collective controller feature allows a server to become the controller for a management collective. The collective controller acts as a command and control mechanism for administrative functions for the collective, and serves as a storage and collaboration mechanism for the collective and cluster members.
Enabling this feature
To enable the Collective Controller feature, add the following element declaration inside the featureManager element in your
server.xml file:
<feature>collectiveController-1.0</feature>
Developing a feature that depends on this feature
If you are developing a feature that depends on the Collective Controller feature, include the following item in the Subsystem-Content header in the feature manifest file for your new feature:
com.ibm.websphere.appserver.collectiveController-1.0; type="osgi.subsystem.feature"
Features that this feature enables
- collectiveMember-1.0 - Collective Member
- distributedMap-1.0 - Distributed Map interface for Dynamic Caching
- json-1.0 - JavaScript Object Notation for Java
- restConnector-1.0 - JMX REST Connector 1.0
- restConnector-2.0 - JMX REST Connector 2.0
- servlet-3.0 - Java Servlets 3.0
- servlet-3.1 - Java Servlets 3.1
- ssl-1.0 - Secure Socket Layer
IBM API packages provided by this feature
Feature configuration elements
You can use the following elements in your server.xml file to configure the Collective Controller feature:
- administrator-role
- authCache
- authentication
- authorization-roles
- basicRegistry
- channelfw
- classloading
- clusterPluginConfig
- collectiveController
- collectiveRepository
- deployManager
- deployRule
- deployVariable
- hostAccess
- httpAccessLogging
- httpDispatcher
- httpEncoding
- httpEndpoint
- httpOptions
- httpProxyRedirect
- jaasLoginContextEntry
- jaasLoginModule
- library
- ltpa
- mimeTypes
- quickStartSecurity
- serverCommands
- tcpOptions
- trustAssociation
- virtualHost