About Service Broker

The Service Broker is a mediator of services provided by one or more StreamServers.

Publishing services

A StreamServer can publish services in several Service Brokers. Each service is identified by a name and version. Any type of StreamServer task can be published as a service. For example, conversion of XML input to page formatted output, and delivery of the converted output to a printer. A service can also be configured to respond with processed output.

See Server configuration.

Invoking services

A client invokes a service by requesting the service name from a Service Broker.

Example 1

Invoking a service

1	A client requests the service Service_3 from a Service Broker.

2	The Service Broker finds Service_3 in its list of services.

3	The client accesses the Service_3 and sends input, via the Service Broker, to the appropriate StreamServer.

 

See Client configuration.

Multiple StreamServers publishing the same service

Several StreamServers can publish the same service. When a client requests a service, the Service Broker decides which StreamServer to invoke. The client does not have to know anything about server ID, host, port, etc.

Encryption and authentication

Service providing StreamServers, Service Brokers, and Service Broker clients can be configured as SSL clients and SSL servers that use encryption and authentication for communication over HTTPS channels.

See Encryption and authentication

Web services

StreamServer services can be exposed via web services through the SOAP protocol.

See Web services

Service Broker properties in the Control Center

The Service Broker is automatically added as a 4.x Services node service to the Control Center when you install StreamServe Tools. You can edit the Service Broker properties. See Service Broker settings in the Control Center.