integrating openedge ® applications with sonicmq ® pat bonser

Integrating OpenEdgeIntegrating OpenEdge®® Applications with Applications with SonicMQSonicMQ®®

Pat Bonser

2 Integrating OpenEdge Applications with SonicMQ © 2005 Progress Software Corporation

Agenda

JMS (Java™ Messaging Service) concepts & SonicMQ

OpenEdge Adapter for SonicMQ– What is it?

– How do I install and configure? Show me examples! Futures, what’s planned for OpenEdge

10.1A Adapter for SonicMQ


What is Messaging?

A mechanism enabling autonomous applications to communicate

Messages - units of information composed of– Payload– Header

Destinations Priority Ordering Expiration Time-to-Live And more …


Application A

JMS Broker

Destination

Application B

How Does It Work?

Message Oriented Middleware

Bind todestination

Bind todestination

Producer Consumer

Sendmessage

Consumemessage

Read message


JMS Messaging Models

Point to Point (1 to 1)

Publish and Subscribe (1 to Many)

QueueSender

Potential Receiver

TopicPublisher

Subscriber

Subscriber

Potential Receiver


Connections and Sessions

A connection connects to a message broker

You can create one or more sessions within a connection

JMS Client

Connection

Queue Session

Topic Session


Unified Domain (JMS 1.1)ConnectionFactory

Connection

Session

MessageConsumerMessageProducer

Destination(Queue or Topic)

MessageSends Messages To Receives Messages From

Destination(Queue or Topic)

CreatesCreates

Creates

Creates

Creates


So what is SonicMQ?

A Standards-Based Enterprise Messaging Server– A full functional implementation of JMS 1.1

specification

– J2EE Compatibility 1.3 - 1.4

– Distributed Management Framework

– Innovative Deployment Architectures User Benefits

– Enterprise-class reliability, scalability, performance using standards-based infrastructure

– Distributed management simplifies and reduces cost of deployment, configuration, monitoring


SonicMQ Domain Manager

Agent Manager

Directory Service

Domain Manager

SonicMQManagement

Broker

Start →Programs → Sonic Software → SonicMQ → SonicMQ Domain Manager


Sonic Management ConsoleStart →Programs → Sonic Software → SonicMQ → Management Console


Queues Must Be Predefined


Sonic JMS Test Client

Allows you to use messaging concepts without having to write Java code

Start →Programs → Sonic Software → SonicMQ → JMS Test Client


Demonstration SonicMQ

Demonstrate– Tool - Management Console

Create a queue

– Tool - JMS Test Client PTP demo using new Queue Pub/Sub demo creating a Topic


OpenEdge Adapter for SonicMQ

JMS concepts & SonicMQ OpenEdge Adapter for SonicMQ

– What is it?





OpenEdge Adapter for SonicMQ– Connects Progress 4GL app with SonicMQ

Seamless integration with existing 4GL– Development tools and Methodologies

Uses direct access from the 4GL to SonicMQ– Specific procedures for the Sonic API

Enterprise Integration for OpenEdge Applications



Direct access from 4GL to SonicMQ– GUI applications

– Character applications (UNIX)

– AppServer

– Webspeed agents

– Batch jobs Connection between

– 4GL applications

– 4GL and non 4GL applications


OpenEdge Adapter for SonicMQ Architecture

PROGRESS 4GL

*.w, *.p

4GL

A

dap

ter

bro

ker

4GL

cli

ent

OpenEdge Database SonicMQ


Progress Adapter Programs

Supplied .r files with API– For point to point

Install-dir/jms/ptpsession.r

– For publish and subscribe Install-dir/jms/pubsubsession.r


Leverage SonicMQ jars

Copy – from SonicMQ install to Progress directory

install-dir\java\sonicMQ\lib

Alternatively– Point your lib directory to

install-dir\java\sonicMQ\lib


Environment Variables

Environment Variable

Used By

Description

SONIC_HOME Sonic The installation directory for SonicMQ. Typically, this is C:\Sonic\MQ6.1

JAVA_HOME Sonic &Progress

Can use the files installed with Sonic, Progress or a compatible jre directory

PATH Progress You should include SONIC_HOME\bin and JDK_HOME\bin in your PATH environment variable


Progress Components

•AdminServer

•OpenEdge Adapter for SonicMQ

•NameServer (Optional)




– What is it?




PTP - Example

SonicMQ

OpenEdge Application

OpenEdge

Application


PTP - Basic Steps

1. Requires a Queue

2. Connect to a SonicMQ Broker

3. Create a Message Consumer

4. Prepare to Receive Message From Queue

5. Send Message to Queue

6. Receive message from Queue

7. Delete message


PTP – Requires a Queue

Sonic Management Console


PTP - Connect to SonicMQ Broker

RUN jms/ptpsession.p PERSISTENT SET ptpsession

("-H localhost -S 5162 ").

RUN setBrokerURL IN ptpsession (“tcp//machinename:2506").

RUN beginSession IN ptpsession.

5162Broker2506



PTP – Create Message to Send/* Create a Text Message */

RUN createTextMessage IN ptpsession

(OUTPUT messageH)./* Handles the messages */

RUN setText IN MessageH (“Your Message”).

SonicBroker


5162


5162


PTP - Send Message to Queue/* Send Message to the “desired” Queue */

RUN sendToQueue IN ptpsession (“YourQueue",

messageH, /* message handle */

?, /* priority, ? = system default */

?, /* timeToLive, ? = system default */

?). /* deliveryMode, ? = system default */

Sonic

Broker


PTP – Receive Message from Queue- Java/* Create Receiver Queues to receive messages */

javax.jms.Queue receiveQueue = receiveSession.createQueue(rQueue);

javax.jms.MessageConsumer qReceiver = receiveSession.createConsumer(receiveQueue);

qReceiver.setMessageListener(this);

connect.start();

Sonic

Broker

5162



OpenEdge

Application

PTP – Receive Message from Queue – 4GL/* Receive Message to the “desired” Queue */

RUN receiveFromQueue IN ptpsession

(“YourQueue", /* Name of the Queue */

?, /* No message selector */

consumerH, /* Handle incoming message default */

Sonic

Broker



PTP Demonstration


Pub/Sub - Example

SonicMQ


OpenEdge

Application


Pub\Sub - Basic Steps

1. Connect to a SonicMQ broker Topics can be set on at run time

2. Create a message subscriber

3. Subscribe to Topic

4. Publish message to Topic

5. Consume message from a Topic

6. Delete message


Pub\Sub - Connect to SonicMQ Broker

5162

5162

Broker2506

RUN jms/pubsubsession.p PERSISTENT SET pubsubsession ("-H localhost -S 5162 ").

RUN setBrokerURL

IN pubsubsession ("tcp://machinename:2506").

RUN beginSession IN pubsubsession.


OpenEdge

Application


Pub\Sub - Create Message Consumer – 4GL/* receives requests from the Topic */

RUN createMessageConsumer IN pubsubsession

(THIS-PROCEDURE, /* This proc handles it */

“YourHandler", /* name of internal proc. */

OUTPUT consumerH).

SonicBroker


OpenEdge

Application

5162

5162


Pub\Sub - Create Message Consumer - Java/* receives requests from the Topic */

subSession = connect.createSession(false,javax.jms.Session.AUTO_ACKNOWLEDGE)

javax.jms.MessageConsumer subscriber =

subsession.createConsumer(topic);

Subscriber.setMessageListener(this);

SonicBroker


OpenEdge

Application

5162

5162


Pub\Sub – Subscribe to TopicRUN SUBSCRIBE IN pubsubsession

("Topic", /* topic name */ ?,

/* Subscription durable */

?, /* No message selector */ NO, /* want my own messages to */ consumerH). /* Handles the messages */

/* Start receiving requests */

RUN startReceiveMessages IN pubsubsession.

SonicBroker

OpenEdge

Application


5162



Pub\Sub - Publish Message to Topic/* In Bytes Message use mptr to store the XML*/

RUN setMemptr IN msgH (memFile, ?, ?).

RUN publish IN pubsubsession

("Topic", /* Topic name */ msgH, /* message handle */ ?, /* priority, ? = system default */ ?, /* timeToLive, ? = system default */ ?). /* deliverymode, ? = system default */

Sonic Broker

5162

OpenEdge

Application


OpenEdge

Application

Pub\Sub – Consumer Message from Topic/* From chargeHandler internal procedure */

memptrDoc = DYNAMIC-FUNCTION ('getMemptr':U IN msgH).

hDoc:LOAD("memptr", memptrDoc, FALSE).

hDoc:GET-DOCUMENT-ELEMENT(hRoot).

hRoot:GET-CHILD(hTable, 1).

… /* All your standard business logic */

SonicBroker


5162


Pub/Sub Demonstration


Integrating OpenEdge Applications with SonicMQ


– What is it?




D I S C L A I M E R

Under Development

This talk includes information about potential future products and/or product enhancements.

What I am going to say reflects our current thinking, but the information contained herein is preliminary and subject to change. Any future products we ultimately deliver may be materially different from what is described here.

D I S C L A I M E R


Installation

Prior to 10.1A – Users had to manually move jar files to

appropriate directories

In 10.1A – Sonic “Silent Install” will move files to

appropriate locations without user interaction


Architecture

Prior to 10.1A, only one option– OpenEdge Adapter for SonicMQ

In 10.1A, two additional options – OpenEdge Adapter for SonicMQ ClientConnect

– OpenEdge Adapter for SonicMQ ServerConnect


Prior to 10.1AOpenEdge Adapter for SonicMQ

RUN jms/ptpsession.p PERSISTENT SET hptpsession

("-H myAdminServerMachine -S 5162 ").

RUN setBrokerURL IN hptpsession (“tcp//mySonicMachine:2506").

RUN beginSession IN hptpsession.

AdminServer

NameServer

MQAdapter

SonicMQ Broker 2506

Thread 1

Thread 2

Thread 3

myAdminServerMachinemySonicMachine

QUEUEJMS

API-JMS

API-JMS


OpenEdge Adapter for SonicMQ ClientConnect

RUN jms/ptpsession.p PERSISTENT SET hptpsession

(“-SMQConnect").

RUN setBrokerURL IN hptpsession (“tcp//mySonicMachine:2506").

RUN beginSession IN hptpsession.

SonicMQ Broker 2506

mySonicMachine

QUEUE

API-JMS

Thread 2

Thread 1

Thread 2

Thread 1

API-JMS


OpenEdge Adapter for SonicMQ ServerConnect

AdminServer

NameServer

AppServer

SonicMQ Broker 2506

Thread 1

Thread 1

Thread 1

mySonicMachine

QUEUEAPI-JMS

X


Combination of PTP and Pub/Sub

Prior to 10.1A– Two different session

RUN jms/ptpsession.p.. RUN jms/pubsubsession.p…

In 10.1A– Parent containing all API

RUN jms/jmssession.p…


Functionalities and Upgraded APIs

Client Persistence Enhanced XML support Temp Table messages ProDataSet messages Fault Tolerance Serialized Connection Objects …


In Summary

The adapter allows 4GL programmers to use JMS messaging techniques from 4GL code

It is easy to install and run examples

Customers are successfully using this technology in Progress V9 and OpenEdge 10

WebSpeed

Web Client

Java

Any

.NET

4GL

SonicBroker



– What is it?

– How do I install and configure? Show me examples! Futures

– OpenEdge 10.1A Adapter for SonicMQ

Questions

integrating openedge ® applications with sonicmq ® pat bonser

Documents

sonicmq slide

sonicmq demonstration

openedge applications

sonicmq application

progress software corporation

sonicmq connections

sonicmq queues

sessions n