Book Image

Getting Started with Oracle WebLogic Server 12c: Developer's Guide

Book Image

Getting Started with Oracle WebLogic Server 12c: Developer's Guide

Overview of this book

Oracle WebLogic server has long been the most important, and most innovative, application server on the market. The updates in the 12c release have seen changes to the Java EE runtime and JDK version, providing developers and administrators more powerful and feature-packed functionalities. Getting Started with Oracle WebLogic Server 12c: Developer's Guide provides a practical, hands-on, introduction to the application server, helping beginners and intermediate users alike get up to speed with Java EE development, using the Oracle application server. Starting with an overview of the new features of JDK 7 and Java EE 6, Getting Started with Oracle WebLogic Server 12c quickly moves on to showing you how to set up a WebLogic development environment, by creating a domain and setting it up to deploy the application. Once set up, we then explain how to use the key components of WebLogic Server, showing you how to apply them using a sample application that is continually developed throughout the chapters. On the way, we'll also be exploring Java EE 6 features such as context injection, persistence layer and transactions. After the application has been built, you will then learn how to tune its performance with some expert WebLogic Server tips.
Table of Contents (18 chapters)
Getting Started with Oracle WebLogic Server 12c: Developer's Guide
Credits
About the Authors
About the Reviewers
www.PacktPub.com
Preface
Index

Java Messaging Service (JMS) and WebLogic


Now that we are familiar with some of the most common ways to connect to a WebLogic Server, let's take a look at one of the features enabled by them, the Java Message Service (JMS) module.

JMS is a Java API that makes the sharing of information between systems or modules possible by sending and receiving messages in an asynchronous way.

WebLogic Server's JMS implementation is compliant with JMS 1.1, and its provider exposes both the message models that are defined by the specification, point-to-point and publish/subscribe, which translate to queue and topic components. The basic difference between them is that a message sent to a queue is consumed by only one listener, no matter how many of them are attached to the queue. By contrast, a topic delivers a message to all its subscribers (the clients attached to it) whether they are online or not, depending on their configuration.

When using WebLogic's JMS, you must first create the destination queue...