LibraryToggle FramesPrintFeedback

A single routing rule base that defines the context for configuring routes, and specifies which policies to use during message exchanges between endpoints.

child container

A container that is created by a container on the same host. Child containers are run on the same host as their parent container, but each child runs in a separate JVM.

When created using the console's admin:create-container, a child container inherits the features, feature repositories, and configuration from its parent. When a child container is created using the fabric:container-create command, the fabric:contaier-create-child, command, or Fuse Management Console, it does not inherit any configuration from its parent.

Regardless of how they are created, child containers can be started and shutdown from their parent container's console without using SSH.

choice complex type

An XML Schema construct defined using the choice element to constrain the possible elements in a complex data type. When using a choice complex type, only one of the elements defined in the complex type can be present at a time.


An application or process that requests services from other applications known as servers. The server processes may be running on the same or a different machine. In the context of a SOA network, a client process is called a consumer or service consumer.

messaging—An application that uses the message broker to communicate with other applications. These applications use one of the broker's client API to connect to and interact with the broker.


A collection of clustered services.

See Also clustered service.

clustered service

A service that can be discovered via Fuse Fabric and has master/slave support.


A factory that creates a routing endpoint that connects to a particular message source or message sink.

composite destination

A virtual destination that serves as a proxy for multiple destinations. Producers can send messages to the composite destination an it will be automatically sent to all of the physical destinations that make up the composite destination.

See Also virtual destination.

concrete contract

See physical contract.


A bridge between a client and a broker connector.

See Also transport connector, network connector, network of brokers.

connection factory

An object that a client uses to create a connection to a broker. A factory supports attributes that configure the quality of service for the connections it creates.


An object that connects clients to a broker.


services—The end user of a service, also called a client for that service. The more exact term in the context of a service-oriented network is service consumer.

messaging—An application that consumes messages from a messaging destination.

routing—The source of messages in a route.


A description of the messages and formats accepted and generated by a service. A service's contract is specified in a WSDL document that defines the interface and all connection-related information for that interface. A WSDL contract contains two sets of components: logical (or abstract) and physical (or concrete).

The logical components of the contract are those that describe the data types, message formats, operations, and interfaces for the services defined in the contract. Logical components are specified with the WSDL elements types, message, portType, and operation.

Comments powered by Disqus