Installable services

Installable services have formalized interfaces (an API) with multiple entry points.

An implementation of an installable service is called a service component. You can use the components supplied with WebSphere MQ, or you can write your own component to perform the functions that you require.

Currently, the following installable services are provided:

Authorization service
The authorization service allows you to build your own security facility.

The default service component that implements the service is the Object Authority Manager (OAM). By default, the OAM is active, and you do not have to do anything to configure it. You can use the authorization service interface to create other components to replace or augment the OAM. For more information about the OAM, see WebSphere MQ security.

Name service
The name service enables applications to share queues by identifying remote queues as though they were local queues.

You can write your own name service component. You might want to do this if you intend to use the name service with WebSphere MQ Version 6.0, for example. To use the name service you must have either a user-written, or a third party, component. By default, the name service is inactive.

See WebSphere MQ installable services and the API exit for more information about the installable services.