02 jms @ sap netweaver 04

5/28/2018 02 Jms @ Sap Netweaver 04

1/10

1

JMS @ SAP NetWeaver 04

Daniel Stollenwerk


2/10

2

SAP AG 2004 / Daniel Stollenwerk / Java Message Service & Message Driven Beans /JMS @ SAP NetWeaver 04

Af ter completing th is sess ion, you will be able to:

state the special features regarding the Java

Message Service in SAP NetWeaver

create a Message Driven Bean with the SAP

NetWeaver Developer Studio

JMS @ SAP NetWeaver 04: Topic Objectives


3/10

3


Overview

Full implementation of JMS 1.0.2b

Integrated in SAP NetWeavers Securi ty concepts Accessing the central user store you can determine who

is allowed to administrate JMS objects.

For all destinations (Queues & Topics) it can be definedwho is allowed to send to or receive from them.

Failover Capability

JMS Connector

IDE Support


4/10

4

If the cluster node hosting the JMS service crashes, another node will start the

service.

So if a crash occurs some messages may be lost, but nevertheless the service

will be available again soon after.

This functionality does not contain a session failover, i.e. the applications have to

initialize again after a crash, but the down time is minimized.


Failover capability

Cluster

JMS

If the node with the JMS Service running on it crashes, another

node wil l host i t.

Cluster

JMS

Cluster

JMS


5/10

5

In a customers system landscape the JMS Provider can easily be exchanged

without touching the existing applications. The applications still communicate with

the JMS Connector which has to be configured to map to another provider.

There are two files which contain the information for mapping the JMS Connector

names to the objects of the JMS Provider

j ms- dest i nat i ons. xml

j ms- f act or i es. xml


JMS Connector / 1

Through the JMS Connector i t gets transparent for the application

which JMS Provider is used.

JMS App JMS App JMS App

JMS Provider

JMS ConnectorXML


6/10

6

The example above shows how a factory object is mapped in thej ms-f act or i es. xml file.

For destinations, the procedure is slightly different; the name registered at the

JMS Provider has to be the same like the one at the JMS Connector. So you

provide this name and the name of the ConnectionFactory with which the

destination shall work.


JMS Connector / 2

jms/QConnFactory

QueueConnectionFactory

QueueConnectionFactory

...

jmsfactory/default/QueueConnectionFactory

Vendordeployment

descriptor

JMS Connector

deployment

descriptor

JMS Provider /

JNDI

[Source code / standard deployment descriptor]

1

2


7/10

7

You can create new MDBs via the context menu of your project as shown in the

screenshot.

Note: If you do not have a package you probably will have to create one first.


IDE SupportCreating a new MDB / 1


8/10

8

After supplying a name the following happens:

The MDB will be declared in the deployment descriptor.

The MDB class will be created.


IDE SupportCreating a new MDB / 2

Deployment

descriptor

MDB class Business Logic


9/10

9

The SAP NetWeaver Developer Studio offers bidirectional editing capabilites; you

can edit the deployment descriptors both with graphical UIs and directly in their

source code. Changes made in the GUI will reflect in the source code and vice

versa


IDE SupportBidirectional Editing


10/10

10


You should now be able to:

state the special features regarding the Java

Message Service in SAP NetWeaver

create a Message Driven Bean with the SAP

NetWeaver Developer Studio

JMS @ SAP NetWeaver 04: Topic Summary

02 jms @ sap netweaver 04

Documents