Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Published by Scroll Versions from space WBRIDGE and version 7.5.0

Otp

JMS Domains

Messaging products can be classified broadly as either point-to-point (PTP) or publish-subscribe (Pub/Sub) systems. These two messaging styles are often referred to as messaging domains.

...

Figure: Concept of Public-Subscribe-Messaging

The E2E Bridge only supports nondurable non-durable subscribers. That implies that subscribers to a topic receive messages only when they are active listening on that topic. Messages sent during inactivity of the subscriber will never get delivered.

When using JMS API version 1.1, a developer can use interfaces and methods that support both models of messaging. The E2E Bridge JMS adapter supports both messaging styles.

...

A JMS provider is an entity that implements JMS for a messaging product, e.g. WebSphere TM MQ from IBM.

Noteinfo
iconfalse

The E2E Bridge JMS adapter requires JMS providers to be JMS 1.1-compliant.

...

Expand
titleClick here to see a snapshot of a JMS component diagram used in E2E Builder before version 6.0

Deprecated since Builder 6.0

JMS Client

All users of JMS are referred to generically as clients. These clients use the JMS implementations supplied by their JMS provider.

...

A JMS session is strongly coupled to an E2E xUML Runtime session (see also Fast-running ACID Transactions). In every E2E Runtime session exists exactly one JMS session connected to a JMS Provider.