Configure services and components on IBM i

Configure service components using the queue manager configuration files. Each service used must have a Service stanza, which defines the service to the queue manager.

For each component within a service, there must be a ServiceComponent stanza. This identifies the name and path of the module containing the code for that component.

The authorization service component, known as the object authority manager (OAM), is supplied with the product. When creating a queue manager, the queue manager configuration file is automatically updated to include the appropriate stanzas for the authorization service and for the default component (the OAM).

The code for each service component is loaded into the queue manager when the queue manager is started, using dynamic binding, where this is supported on the platform.

Service stanza format

  Service:
    Name=service_name
    EntryPoints=entries

service_name

The name of the service. This is defined by the service.

entries

The number of entry points defined for the service. This includes the initialization and termination entry points.

Service component stanza format

  ServiceComponent:
    Service=service_name
    Name=component_name
    Module=module_name
    ComponentDataSize=size

service_name

The name of the service. This must match the Name specified in a service stanza.

component_name

A descriptive name of the service component. This must be unique, and contain only the characters that are valid for the names of IBM MQ objects (for example, queue names). This name occurs in operator messages generated by the service. We recommend that we use a name starting with a company trademark or similar distinguishing string.

module_name

The name of the module to contain the code for this component. Specify a full path name.

size

The size in bytes of the component data area passed to the component on each call. Specify zero if no component data is required.

These two stanzas can occur in any order and the stanza keys under them can also occur in any order. For either of these stanzas, all the stanza keys must be present. If a stanza key is duplicated, the last one is used.

At startup time, the queue manager processes each service component entry in the configuration file in turn. It then loads the specified component module, invoking the entry-point of the component (which must be the entry-point for initialization of the component), passing it a configuration handle.