WebSphere Message Broker, Version 8.0.0.7
Operating Systems: AIX, HP-Itanium, Linux, Solaris, Windows, z/OS
See information about the latest product version
See information about the latest product version
Resource management overview
WebSphere® Message Broker provides several types of container projects which you can use to organize your message flow development resources.
When you develop message flows in the WebSphere Message Broker Toolkit, you can choose what sort
of project they are contained in, depending on your development style.
- An application can contain related message flows and resources that should be deployed and managed together. Applications provide encapsulation. Resources in an application are packaged and deployed as a single unit, and can be managed as a single unit. For more information, see Applications and libraries.
- A service is a special type of application that has a defined interface and implementation. Services provide assisted development to provide Web Services in a broker. Like applications, Services provide encapsulation and are deployed and managed as a single unit. For more information, see Services.
- A library can contain related flows and resources, which promotes reuse. A library is also packaged and deployed as a single unit, and can be used by applications, Message Broker projects, or by independent message flows.
- A Message Broker project is an unstructured container in which you can develop message flows and related resources. When resources from a Message Broker project are packaged for deployment, you can choose which resources are packaged together. Message Broker projects cannot contain message models. For more information, see Message Broker projects.