10.02.2013 Views

Progress Sonic ESB Configuration and Management Guide

Progress Sonic ESB Configuration and Management Guide

Progress Sonic ESB Configuration and Management Guide

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Chapter 2: <strong>ESB</strong> Containers<br />

The following events occur as the <strong>ESB</strong> Container manages message transfer:<br />

1. The <strong>ESB</strong> Container reads configuration information from the Directory Service.<br />

2. The <strong>ESB</strong> Container establishes JMS connections to <strong>Progress</strong> <strong>Sonic</strong>MQ destinations<br />

(topics or queues).<br />

3. The <strong>ESB</strong> Container pools JMS connections.<br />

4. Messages arriving on their <strong>Progress</strong> <strong>Sonic</strong>MQ destinations are allocated to services<br />

that implement the XQService interface by calling their service( ) method, using the<br />

predefined Quality of Service (QoS)—EXACTLY_ONCE, AT_LEAST_ONCE, or BEST_EFFORT.<br />

5. Messages are processed by the services.<br />

6. Output messages are generated by the services <strong>and</strong> placed in an OUTBOX.<br />

7. Messages in the OUTBOX are sent to <strong>Sonic</strong>MQ destinations by the services, or to other<br />

services in the container.<br />

An <strong>ESB</strong> Container is deployed as a component in a management container. The<br />

management container caches all the information that it looks up in its domain manager’s<br />

Directory Service store. If the domain manager is not accessible <strong>and</strong> the management<br />

container is not looking up any new configurations (including resources such as<br />

stylesheets, new services, or endpoints) at that time, then the container can continue<br />

running despite the domain manager failure. However, if a new configuration is necessary<br />

that is not cached, it must wait for the Directory Service to be restarted.<br />

In addition to providing configuration information, a management container also provides<br />

access to a common log file for all of the components it hosts. (For information on<br />

container caching <strong>and</strong> logging, see the “Configuring Containers <strong>and</strong> Collections” <strong>and</strong><br />

“Managing Containers <strong>and</strong> Collections” chapters in the <strong>Progress</strong> <strong>Sonic</strong>MQ <strong>Configuration</strong><br />

<strong>and</strong> <strong>Management</strong> <strong>Guide</strong>.)<br />

The following sections describe how to manage installed <strong>ESB</strong> Containers <strong>and</strong> create new<br />

<strong>ESB</strong> Containers. Use the <strong>Sonic</strong> <strong>Management</strong> Console to add <strong>Progress</strong> <strong>Sonic</strong> <strong>ESB</strong><br />

components to a container.<br />

57 <strong>Progress</strong> <strong>Sonic</strong> <strong>ESB</strong> <strong>Configuration</strong> <strong>and</strong> <strong>Management</strong> <strong>Guide</strong> 8.5

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!