WebLogic 12C Administration & Development 1z0-599/133[Part3]

Explore the WebLogic JMS messaging model within a middleware framework, detailing asynchronous loosely coupled architecture, the JMS components, and hands-on configuration, topics, queues, and coding using Eclipse IDE.

Understand how middleware bridges two applications, enabling communication via messaging services and Java Messaging Services (JMS) in WebLogic administration and development. See how configuration and coding work together.

Explore three middleware types: remote RBC, object middleware, and the focus on message oriented middleware, where a Java object is sent as the network message.

Learn how JMS, Java Message Service, a middleware messaging service, enables sending and receiving messages as objects, and supports one-to-one and broadcast communication in enterprise apps.

Learn JMS asynchronous and loosely coupled architecture, contrasting immediate synchronous responses with fire-and-forget messaging where messages are stored for later delivery, temporarily or persistently.

Explore the role of JMS providers as brokers that buffer messages between producers and consumers, and learn how publishers, subscribers, and clients interact within the Java messaging services.

Explore examples of messaging software, including MQ, WebSphere, ActiveMQ, and RabbitMQ. Learn why free, open-source options like RabbitMQ may suit lighter projects.

Explore how a JMS server targets one WebLogic instance within a domain, why it cannot be spread across a cluster, and how multiple JMS servers relate to a single instance.

Learn how JMS server communication works with a connection factory and persistence—storing messages in a file store or database on the same server, via resources from sender to receiver.

Explains the difference between the system module and sub modules, showing the system module as the superset that holds all resources and governs access for sub modules and connections.

Sub deployment groups multiple WebLogic resources, like JMS servers, queues, and connection factories, so you can target a single deployment rather than individual servers, enabling simple clustering and failover.

Explore how a queue supports one-to-one messaging by mapping aliases to real names, and contrast queue delivery with topics, including message deletion after receipt.

Recap the messaging concepts: distinguish provider from client, and producer or publisher from consumer or subscriber, with the message as the object that moves from sender to receiver.

Explore how a local JMS store forwards messages to a file store and how persistence stores them. Learn how queues versus topics affect consumption and monitoring in WebLogic.

Explore point-to-point and pub-sub JMS models. Point-to-point uses a queue delivering a message to one receiver and deleting it; pub-sub broadcasts to multiple subscribers via topic, with messages remaining available.

Compare topic and queue, noting single versus multiple consumers and fifo versus lifo delivery. Explain persistence, its temporary versus permanent nature, and the two options: database store and file store.

Demonstrates a sender and receiver messaging demo in Eclipse, showing how to set up a Java project, run sender and receiver consoles, and monitor queue messages and persistence.

Create a JMS server and a file store within a WebLogic domain, configuring a GM server, server targets, and associated file stores while visualizing the system with a module diagram.

Create and configure a system module and its submodules, set up a connection factory, and apply targeting and subdeployment options across MS1 and MS2 clusters.

Learn to build a JMS communication app from scratch in Java for WebLogic, configuring the initial context, obtaining a connection factory and queue, and sending text messages with a sender.