Why installable services?
The main reasons for providing WebSphere MQ installable services are:
- To provide you with the flexibility of choosing whether to use components provided by WebSphere MQ for iSeries, or replace or augment them with others.
- To allow vendors to participate, by providing components that might use new technologies, without making internal changes to WebSphere MQ for iSeries.
- To allow WebSphere MQ to exploit new technologies faster and cheaper, and so provide products earlier and at lower prices.
Installable services and service components are part of the WebSphere MQ product structure. At the center of this structure is the part of the queue manager that implements the function and rules associated with the Message Queue Interface (MQI). This central part requires a number of service functions, called installable services, in order to perform its work. The installable service available in WebSphere MQ for iSeries is the authorization service.
Each installable service is a related set of functions implemented using one or more service components. Each component is invoked using a properly-architected, publicly-available interface. This enables independent software vendors and other third parties to provide installable components to augment or replace those provided by WebSphere MQ for iSeries. Table 13 summarizes support for the authorization service.
Table 13. Authorization service components summary Supplied component Function Requirements Object Authority Manager (OAM) Provides authorization checking on commands and MQI calls. Users can write their own component to augment or replace the OAM. (Appropriate platform authorization facilities are assumed) DCE name service component