Functions and components
Each service consists of a set of related functions. For example, the name service contains function for:
- Looking up a queue name and returning the name of the queue manager where the queue is defined
- Inserting a queue name into the service’s directory
- Delete a queue name from the service’s directory
It also contains initialization and termination functions.
An installable service is provided by one or more service components. Each component can perform some or all of the functions that are defined for that service. For example, in WebSphere MQ for AIX, the supplied authorization service component, the OAM, performs all the available functions. See Authorization service interface for more information. The component is also responsible for managing any underlying resources or software (for example, an LDAP directory) that it needs to implement the service. Configuration files provide a standard way of loading the component and determining the addresses of the functional routines that it provides.
Figure 1 shows how services and components are related:
- A service is defined to a queue manager by stanzas in a configuration file.
- Each service is supported by supplied code in the queue manager. Users cannot change this code and therefore cannot create their own services.
- Each service is implemented by one or more components; these can be supplied with the product or user-written. Multiple components for a service can be invoked, each supporting different facilities within the service.
- Entry points connect the service components to the supporting code in the queue manager.
Figure 1. Understanding services, components, and entry points
Parent topic:
Installable services and components
fa16210_
Home
