Network Deployment (Distributed operating systems), v8.0 > Applications
This page provides a starting point for finding information about service integration.
Service integration provides asynchronous messaging services. In asynchronous messaging, producing applications do not send messages directly to consuming applications. Instead, they send messages to destinations. Consuming applications receive messages from these destinations. A producing application can send a message and then continue processing without waiting until a consuming application receives the message. If necessary, the destination stores the message until the consuming application is ready to receive it.
- Service integration technologies
Service integration is a set of technologies that provides asynchronous messaging services. Use this topic to learn about the technologies on which WAS service integration applications are developed and implemented.
- Service integration buses
A service integration bus is a group of one or more application servers or server clusters in a WAS cell that cooperate to provide asynchronous messaging services. The application servers or server clusters in a bus are known as bus members. In the simplest case, a service integration bus consists of a single bus member, which is one application server.
- Bus members
The members of a service integration bus can be application servers, server clusters, or WebSphere MQ servers. Bus members that are application servers or server clusters contain messaging engines, which are the application server components that provide asynchronous messaging services. Bus members that are WebSphere MQ servers provide a direct client connection between a service integration bus and queues on a WebSphere MQ queue manager.
- Messaging engines
Each service integration server or cluster bus member contains a component called a messaging engine that processes messaging send and receive requests and that can host destinations.
- Bus destinations
Service integration has the following types of bus destinations each with a different purpose: queue, topic space, foreign, and alias.
- Message stores
Message stores are important in the operation of messaging engines.
To host queue-type destinations, a messaging engine includes a message store where, if necessary, it can hold messages until consuming applications are ready to receive them, or preserve messages in case the messaging engine fails. Each messaging engine has one and only one message store. This can either be a file store or a data store.
- Service integration security
Messaging security ensures that service integration bus users are authenticated, resources are protected by security checks, and messages are secured when they are in transit. Use these topics to learn how to secure the service integration bus and protect messages that are sent and received.
- High availability and workload sharing
Use these topics to learn about high availability and workload sharing.
A mediation is a Java program that extends the messaging capabilities of WAS. Mediations can be used to simplify connecting systems, services, applications, or components that use messaging.
- Service integration configurations
A service integration configuration can range from a single host running two connected applications to a globally-dispersed set of hundreds or thousands of communicating applications running over the bus.
- Service integration notification events
We can monitor your service integration environment by using notification events.
- Message reliability levels - JMS delivery mode and service integration quality of service
Messages have a quality of service attribute that you can use to specify how reliable message delivery will be. JMS applications send messages with a JMS delivery mode (persistent or nonpersistent), then service integration uses JMS connection factory settings to map the JMS delivery mode to a service integration message reliability setting. Additional settings on bus destinations (including foreign destinations and alias destinations) can override this message reliability.
- Dynamic reloading of configuration files
Updates to configuration information are dynamically passed to the server if you use dynamic reloading of configuration files. These updates are available to a messaging engine even if it is not started.
- Service integration backup
You should back up your service integration setup on a regular basis so that it can be restored in the event of an unrecoverable failure.
Migrate Service integration
Administer Service integration
Scripting for Service integration
Establishing high availability for Service integration
Secure Service integration
Develop Service integration
Tune Service integration
Troubleshoot Service integration