Weblogic Authors: Yeshim Deniz, Elizabeth White, Michael Meiner, Michael Bushong, Avi Rosenthal

Related Topics: Weblogic

Weblogic: Article

JMSML: XML-Based Mark-Up Language

JMSML: XML-Based Mark-Up Language

JMSML is a mark-up language designed and developed to make Java Message Service (JMS) and Java Management Extensions (JMX) programming easy by hiding all the JMS and JMX Java API complexity behind a few easy-to-use XML tags.

JMS Applications: A Background
A typical JMS application development process involves configuring and managing the JMS server components, like JMSConnectionFactory and JMSDestination, on the JMS Provider application server, writing JMS application clients that will make use of these administered server-side objects to do the Java messaging.

JMS application clients are written in Java using the JMS API, and are categorized into two types of programs:

  • Producers: For creating various JMS Message types (like Text, XML, Object, Stream, Bytes) and sending them to the JMS destinations (Queues and Topics)
  • Consumers: For receiving messages from the JMS destinations (Queues and Topics), both synchronously and asynchronously

    The JMS API enables both producers and consumers to utilize various qualities of services (QOS) that are provided by the underlying JMS implementation and by the JMS providers (like transaction and acknowledgment).

    Writing producers and consumers involves following some specific steps, in a specific order, while using the JMS API. This process has to be repeated for every single producer and consumer that is written to do Java messaging.

    The JMSML Approach
    The JMSML approach to writing JMS application clients is accomplished without writing Java code. Instead, JMS API complexity is abstracted into a few XML tags that are easy to use and remember. Using JMSML, you can create simple reusable JMS components, like a "Sender", "Receiver", "Publisher", and "Subscriber". In addition, JMSML makes administration of a JMS server very simple by using XML tags, thus eliminating the JMX Java API complexity. JMSML supports all the JMX operations that are needed to do dynamic configuration, management, and runtime monitoring of a JMS server.

    Finally, JMSML simplifies testing by automating verification of operation and monitoring output (see Figure 1).

    What Does a Java JMS Program Look Like?
    Listing 1 shows a Java program using the JMS API to send a text message, "Hello World", to a JMS queue named "exampleQueue", using a JMSConnectionFactory named "QueueConnectionFactory" via a nontransacted, autoacknowledge JMSSession.

    What Does a JMSML Program Look Like?
    The following 9 lines of a similar XML program, QueueSend.xml, are equivalent to the 74 lines of QueueSend.java in Listing 1. Note that all other Java JMS API details are taken care by JMSML by means of having default attribute values.

    1 <?xml version="1.0" encoding="UTF-8"?>
    2 <!DOCTYPE jmsml PUBLIC "-//BEA Systems Inc//DTD JMSML Version 1.0 JMSML//EN"
    3 <jmsml>
    4 <operation Class="message" Type="Text" Name="MyQueueSender"
    5 Factory="QueueConnectionFactory"
    6 Queue="exampleQueue"
    7 Body="Hello World"
    8 >Send</operation>
    9 </jmsml>

    In this case, JMSML will create QueueSender with a nontransacted and autoacknowledge JMSSession. Once this operation is executed, then the "MyQueueSender" object is still available for reuse later, until the end of the program execution. That is, "MyQueueSender" can be reused to send different messages to different queues.

    JMSML Applications
    From the previous code comparison, you can easily figure out that JMSML is simple to learn and use yet very powerful in terms of its functionality. JMSML can be used to do the following tasks in the WebLogic JMS subsystem.

  • As an administration and monitoring tool for the WebLogic JMS subsystem
  • As a prototyping tool for WebLogic JMS applications
  • As a testing tool for the WebLogic JMS Subsystem

    Using JMSML as a Testing Tool
    Once JMS testing scenarios are identified, they can easily be translated into JMSML operations and then grouped as testing scenarios using <scenario> with the Verify attribute set to "false". This test program can be executed using one of the JMSML execution models. After successful execution, an output file is created with the same name as the input JMSML program and with a .out extension. It is verified manually for correctness and then saved as a benchmark file (again in the same name as the input JMSML program but with a .bmk extension).

    Later, whenever the same JMSML program is executed, with the Verify attribute of the <scenario> element set to "true", JMSML treats that input JMSML program as a test, and the output file is automatically compared with the corresponding benchmark file for test verification. If the benchmark and the output file matches, then the test is declared as passed. Otherwise, it will be declared as failed.

    Test the dynamic creation, management, and monitoring of the JMS administered objects and the message send, receive features of JMS.

    Testing Scenario: Create a JMSServer named "Warehouse" with all the default attribute values and deploy it on a WebLogic Server instance named "examplesServer". Create a queue destination named "orderqueue" with all the attribute values explicitly defined, add it to the JMSServer named "Warehouse", into JNDI as "jms.queue.order", send/receive messages to this queue, and at the end delete both the queue "orderqueue" destination and the "Warehouse" JMSServer.

    Listing 2 is the JMSML representation of the Testing Scenario defined above.

    Once a JMSML program is written, it can be run against a WebLogic Server instance. Currently, JMSML provides three different ways to execute a program they are;
    1.   Stand-alone commandline client
    2.   Web browser interface for remote execution
    3.   IDE (prototype)

    java com.bea.jmsml.commandline.JMSMLClient \
    -protocol t3 \
    -host localhost \
    -port 7001 \
    -username weblogic \
    -password weblogic \
    -filename jmstest.xml

    This command line assumes the following about the execution environment:

  • An instance of WebLogic Server named "examplesServer" is running on "localhost" and is listening on the port '7001" with the "t3" protocol enabled.
  • WebLogic security is set up such that a user named "weblogic" with a password of "weblogic" is configured with permissions for creating and accessing JMS server components.
  • A valid JMS connection factory is deployed on the "examplesServer" and is bound to JNDI as "weblogic.examples.jms.QueueConnectionFactory".
  • The test program shown in Listing 3 is saved in the current directory along with the "jmsml.dtd" file.

    After the successful execution of the command, the following message will be printed out to the stdout.

    *** jmstest processed *** \n***
    Please see ./jmstest.out for the results ***

    At this time, an output file named "jmstest.out" will exist in the current directory, containing all the operations execution results, as shown in Listing 3. In this output sample, the contents are color-coded to identify the operation category, as follows:

  • Brown: JMS Receive (successful Send has no output in normal mode)
  • Red: JMX Add, Remove
  • Blue: JMX List (config information)
  • Green: JMX List (runtime statistics)

    Once this output is manually verified for correctness, you can easily make it a valid, reusable WebLogic JMS test case by doing two things:
    1.   Rename the "jmstest.out" file to "jmstest.bmk"
    2.   Edit the "jmstest.xml" file by changing the Verify attribute value to "true" in the <scenario> element.

    The next time the same command line is executed, JMSML treats the "jmstest.xml" as a test case and prints out the test pass/fail result to the stdout.

    That's it! Without writing a Java program, we have quickly written a complete test case for BEA WebLogic JMS and JMX features using JMSML. This is a working example and is packaged with JMSML download.

    The JMSML product binary, along with the technical white paper, can be downloaded from: http://dev2dev.bea.com/resourcelibrary/ whitepapers/JMSML_WhitePaper.jsp

  • More Stories By Kathiravan Sengodan

    Kathiravan Sengodan has more than 11 years of experience in the software industry and is currently a sofware engineer on the BEA WebLogic JMS/Messaging team.

    Comments (0)

    Share your thoughts on this story.

    Add your comment
    You must be signed in to add a comment. Sign-in | Register

    In accordance with our Comment Policy, we encourage comments that are on topic, relevant and to-the-point. We will remove comments that include profanity, personal attacks, racial slurs, threats of violence, or other inappropriate material that violates our Terms and Conditions, and will block users who make repeated violations. We ask all readers to expect diversity of opinion and to treat one another with dignity and respect.

    IoT & Smart Cities Stories
    CloudEXPO | DevOpsSUMMIT | DXWorldEXPO are the world's most influential, independent events where Cloud Computing was coined and where technology buyers and vendors meet to experience and discuss the big picture of Digital Transformation and all of the strategies, tactics, and tools they need to realize their goals. Sponsors of DXWorldEXPO | CloudEXPO benefit from unmatched branding, profile building and lead generation opportunities.
    DXWorldEXPO LLC announced today that Big Data Federation to Exhibit at the 22nd International CloudEXPO, colocated with DevOpsSUMMIT and DXWorldEXPO, November 12-13, 2018 in New York City. Big Data Federation, Inc. develops and applies artificial intelligence to predict financial and economic events that matter. The company uncovers patterns and precise drivers of performance and outcomes with the aid of machine-learning algorithms, big data, and fundamental analysis. Their products are deployed...
    All in Mobile is a place where we continually maximize their impact by fostering understanding, empathy, insights, creativity and joy. They believe that a truly useful and desirable mobile app doesn't need the brightest idea or the most advanced technology. A great product begins with understanding people. It's easy to think that customers will love your app, but can you justify it? They make sure your final app is something that users truly want and need. The only way to do this is by ...
    Digital Transformation and Disruption, Amazon Style - What You Can Learn. Chris Kocher is a co-founder of Grey Heron, a management and strategic marketing consulting firm. He has 25+ years in both strategic and hands-on operating experience helping executives and investors build revenues and shareholder value. He has consulted with over 130 companies on innovating with new business models, product strategies and monetization. Chris has held management positions at HP and Symantec in addition to ...
    Dynatrace is an application performance management software company with products for the information technology departments and digital business owners of medium and large businesses. Building the Future of Monitoring with Artificial Intelligence. Today we can collect lots and lots of performance data. We build beautiful dashboards and even have fancy query languages to access and transform the data. Still performance data is a secret language only a couple of people understand. The more busine...
    The challenges of aggregating data from consumer-oriented devices, such as wearable technologies and smart thermostats, are fairly well-understood. However, there are a new set of challenges for IoT devices that generate megabytes or gigabytes of data per second. Certainly, the infrastructure will have to change, as those volumes of data will likely overwhelm the available bandwidth for aggregating the data into a central repository. Ochandarena discusses a whole new way to think about your next...
    Cell networks have the advantage of long-range communications, reaching an estimated 90% of the world. But cell networks such as 2G, 3G and LTE consume lots of power and were designed for connecting people. They are not optimized for low- or battery-powered devices or for IoT applications with infrequently transmitted data. Cell IoT modules that support narrow-band IoT and 4G cell networks will enable cell connectivity, device management, and app enablement for low-power wide-area network IoT. B...
    The hierarchical architecture that distributes "compute" within the network specially at the edge can enable new services by harnessing emerging technologies. But Edge-Compute comes at increased cost that needs to be managed and potentially augmented by creative architecture solutions as there will always a catching-up with the capacity demands. Processing power in smartphones has enhanced YoY and there is increasingly spare compute capacity that can be potentially pooled. Uber has successfully ...
    SYS-CON Events announced today that CrowdReviews.com has been named “Media Sponsor” of SYS-CON's 22nd International Cloud Expo, which will take place on June 5–7, 2018, at the Javits Center in New York City, NY. CrowdReviews.com is a transparent online platform for determining which products and services are the best based on the opinion of the crowd. The crowd consists of Internet users that have experienced products and services first-hand and have an interest in letting other potential buye...
    When talking IoT we often focus on the devices, the sensors, the hardware itself. The new smart appliances, the new smart or self-driving cars (which are amalgamations of many ‘things'). When we are looking at the world of IoT, we should take a step back, look at the big picture. What value are these devices providing. IoT is not about the devices, its about the data consumed and generated. The devices are tools, mechanisms, conduits. This paper discusses the considerations when dealing with the...