SOA

What is Middleware

A software that helps disparate and distributed applications to collaborate with each otherSOA is the hottest middleware strategy till date.SOA Not a technology or product, more a design approach

Oracle SOA Suite

Provides “components” for designing, deploying, and managing “composite applications”.

“Composites”

enable you to easily assemble multiple technology components into one SOA composite application

“Components”

BPEL

OSB

Mediator

Human Workflow

Business rules

Adapters (FTP, DB, AQ, JMS, MQ, Apps, Siebel, PSFT…)

BAM

ODI

Introduction to WSDL

Web Services Description Language is an XML-based language used to define Web services and describe how to access them.

Working with a Mediator : Echo Pattern







This blog shows you how to work with a Mediator component in Oracle SOA Suite 11g.


This example uses the Echo pattern of the Mediator. An Echo is a simple "reply to the caller" pattern where the requestor immediately gets back a response.


This is typically used in use cases where a certain message has to be enriched, or some filtering to be done, etc.






Creating a Mediator


Create a new SOA Project, name it MediatorEchoPattern, select empty template













Defining the Schema


To begin with, define the message structures that will be used in the example.


In this tutorial, we will send in a message {firstName, lastName} and get back {fullName}. Based on this, define the xsd file


Rt click on xsd folder --> new --> All technologies --> xml schema --> name itEchoPatternSchema















Define the schema as shown below

















Creating the Mediator


Open composite.xml, drag and drop the Mediator component from the component palette to the components swimlane of the composite.xml


Name it EchoMediator, template as Define Interface Later. This interface will be created when we create a WebService and wire it to this, later.








This step creates an empty mediator.






Create a service endpoint


Mediator exists in the Components swimlane which is not directly exposed to the external world. In order to access it, we need to create a service endpoint through which external clients can access this component.


Here, we create a WebService with request and response types as defined in the schema earlier


To create a WebService, drag and drop the Web Service from the component palette to theExposed Services swimlane of the composite.xml


Name it EchoMediatorClient


In the WSDL url, select the second option Generate WSDL from Schema.


This will open a WSDL generation wizard where we need to select the Interface type and the message types for input and output. Select them as shown below
















This will create a WebService in the composite.xml


Now, wire the Webservice to the mediator as shown










Creating the Echo Pattern


Now that the wiring is done, the only thing remaining is to define the message flow


In this example which is an echo pattern, the request comes from the WebService, goes to the mediator, undergoes some transformation in the mediator, and finally is routed back to the WebService.


Hence, we need to create a routing rule in the mediator with an Echo Pattern






Double click on the mediator component in the composite.xml which will open a .mplan file which is the heart of the mediator component where all the operations of the mediator as defined in the other blog are to be defined.


For this tutorial which is more like a HelloWorld example, just a transformation file would be sufficient.






Click on the + icon of the Routing Rules --> Static Routing Rule --> Echo















This will add a Routing rule section in the file.


Here, we add a transformation file to transform the input message to the output message. Transformation file is mandatory for any type of mediator as that is the link that connects the input to the output within the mediator.


Click on the button at the end of the Transform Using, create a new mapper file and accept the default name

















This will open up a new wizard, where we can do all the transformations.


In this example, we need to concatenate the firstName & lastName, append hello to it, and assign it to the output


Concat function is available in the component palette at the right when you open the transformation file. Drag and drop this function to the middle section of the wizard,


then drag a line from each of the inputs to it, then double click on the concat function to addhello, and finally map it to the fullName at the right, as shown below
















Thats it, you're done!






Deploy this project. How to deploy is mentioned in this blog


EM URL : http://<host>:<adminPort>/em


Select the project under SOA-->soa_infra, click on test


















This is main logic behind Alarm

==========================================================================

SOA:JMS Queue Guide

==========================================================================

Java Messaging Service is an API that provides reliable, asynchronous communication between applications in a distributed computing environment. It enables a Java applications that share a messaging system to exchange messages and Simplifies application development by providing a standard interface for creating, sending, and receiving messages.

To Know about JMS Topic Please refer to: Basic JMS Demo using WebLogic Topic
What are major components of JMS system?

A). JMSServer: JMS server is an environment-related configuration entity that acts as management container for JMS queue and topic resources defined within JMS modules that are targeted to specific that JMS server.
B). JMS Modules: JMS modules contain configuration resources, such as standalone queue and topic destinations, distributed destinations, and connection factories. In WebLogic Server these Configurations can be seen inside “<DOMAIN_HOME>/config/jms” Directory.
C). JMS Client: A JMS is a JMS applications that either produce messages to destinations or consume messages from destinations.
D). JNDI : Java Naming And Directory interface,It is a Java API for a directory service that allows Java software clients to discover and look up data and objects via a name.
E). Persistent Store: It can be a UserDefined Persistent Store or a Default Persistent store. It is used for storing the Data (Messages).

Here we are going to see how we can configure WebLogic JMS Server, JMS Modules (Queue/ConnectionFactory) how to Target them and then How to test it using a Simpel Java Programs.

Step1). Start your WebLogic Server an Login to the AdminConsole.

Step2). Create a JMS Server…

Creating JMS Server

Creating JMS Server-2

Selecting JMS Server Store Type

Configuring JMS Store

Choosing JMS Store for JMSSErver

Targeting to the JMSServer

Activating the JMS Server Configuration

Step3). Configuring JMS Module:

Creating JMS Module

Entering JMS Module Name

Targetting JMS Module

Finishing the Module Creation

Step4). Creating Connection Factory:

Creating JMS Connection Factory

Selecting JMS Module to be Created

Providing Name/JNDIName to Connection Factory

Targeting the CnnectionFactory

Step5).Creating JMS Queue:

Selecting JMSQueue to be Created

Queue Selection

Assigning Name/JNDIName to Queue

Creating SubDeployment

Assigning Name to the SubDeployment

Targeting the JMS Queue

Activating the Final Changes

Step6). Now Write a Simple Java Program to send the Messages to this JMS Queue…like following:

“QueueSend.java”

01	import java.io.*;

02	import java.util.Hashtable;

03	import javax.jms.JMSException;

04	import javax.jms.Queue;

05	import javax.jms.QueueConnection;

06	import javax.jms.QueueConnectionFactory;

07	import javax.jms.QueueSender;

08	import javax.jms.QueueSession;

09	import javax.jms.Session;

10	import javax.jms.TextMessage;

11	import javax.naming.Context;

12	import javax.naming.InitialContext;

13	import javax.naming.NamingException;

14

15	public class QueueSend

16

{

17	public final static String JNDI_FACTORY="weblogic.jndi.WLInitialContextFactory";

18	public final static String JMS_FACTORY="QCF";

19	public final static String QUEUE="TestQ";

20

21	private QueueConnectionFactory qconFactory;

22	private QueueConnection qcon;

23	private QueueSession qsession;

24	private QueueSender qsender;

25	private Queue queue;

26	private TextMessage msg;

27

28	public void init(Context ctx, String queueName)

29	throws NamingException, JMSException

30

{

31	qconFactory = (QueueConnectionFactory) ctx.lookup(JMS_FACTORY);

32	qcon = qconFactory.createQueueConnection();

33	qsession = qcon.createQueueSession(false, Session.AUTO_ACKNOWLEDGE);

34	queue = (Queue) ctx.lookup(queueName);

35	qsender = qsession.createSender(queue);

36	msg = qsession.createTextMessage();

37	qcon.start();

38

}

39

40	public void send(String message) throws JMSException {

41	msg.setText(message);

42	qsender.send(msg);

43

}

44

45	public void close() throws JMSException {

46	qsender.close();

47	qsession.close();

48	qcon.close();

49

}

50

51	public static void main(String[] args) throws Exception {

52	if (args.length != 1) {

53	System.out.println("Usage: java QueueSend WebLogicURL");

54

return;

55

}

56	InitialContext ic = getInitialContext(args[0]);

57	QueueSend qs = new QueueSend();

58	qs.init(ic, QUEUE);

59	readAndSend(qs);

60	qs.close();

61

}

62

63	private static void readAndSend(QueueSend qs) throws IOException, JMSException

64

{

65	String line="Test Message Body with counter = ";

66	BufferedReader br=new BufferedReader(new InputStreamReader(System.in));

67	boolean readFlag=true;

68	System.out.println("\n\tStart Sending Messages (Enter QUIT to Stop):\n");

69	while(readFlag)

70

{

71	System.out.print("<Msg_Sender> ");

72	String msg=br.readLine();

73	if(msg.equals("QUIT") || msg.equals("quit"))

74

{

75	qs.send(msg);

76	System.exit(0);

77

}

78	qs.send(msg);

79	System.out.println();

80

}

81	br.close();

82

}

83

84	private static InitialContext getInitialContext(String url) throws NamingException

85

{

86	Hashtable env = new Hashtable();

87	env.put(Context.INITIAL_CONTEXT_FACTORY, JNDI_FACTORY);

88	env.put(Context.PROVIDER_URL, url);

89	return new InitialContext(env);

90

}

91

}

Step7). Now run the “setWLSEnv.cmd” and then compile and Run the QueueSend program.

java QueueSend t3://localhost:7001

Step8). Now Login to AdminConsole to check that the Message is arrived in the JMS Queue or Not?

home—> Services–> Messaging–> JMS Modules–> MySystemModule–>MyQueue–> Monitoring–> MySystemModule –> MyQueue (Check the CheckBox)–> Show Messages(Click This Button)

Monitoring JMS Queue Message In AdminConsole

Step9). Now write the following “QueueReceive.java” program to read JMS Messages from the JMS Queue.

“QueueReceive.java”

01	import java.util.Hashtable;

02	import javax.jms.*;

03	import javax.naming.Context;

04	import javax.naming.InitialContext;

05	import javax.naming.NamingException;

06

07	public class QueueReceive implements MessageListener

08

{

09	public final static String JNDI_FACTORY="weblogic.jndi.WLInitialContextFactory";

10	public final static String JMS_FACTORY="QCF";

11	public final static String QUEUE="TestQ";

12	private QueueConnectionFactory qconFactory;

13	private QueueConnection qcon;

14	private QueueSession qsession;

15	private QueueReceiver qreceiver;

16	private Queue queue;

17	private boolean quit = false;

18

19	public void onMessage(Message msg)

20

{

21

try {

22	String msgText;

23	if (msg instanceof TextMessage)

24

{

25	msgText = ((TextMessage)msg).getText();

26

}

27

else

28

{

29	msgText = msg.toString();

30

}

31	System.out.println("\n\t<Msg_Receiver> "+ msgText );

32	if (msgText.equalsIgnoreCase("quit"))

33

{

34	synchronized(this)

35

{

36	quit = true;

37	this.notifyAll(); // Notify main thread to quit

38

}

39

}

40

}

41	catch (JMSException jmse)

42

{

43	jmse.printStackTrace();

44

}

45

}

46	public void init(Context ctx, String queueName) throws NamingException, JMSException

47

{

48	qconFactory = (QueueConnectionFactory) ctx.lookup(JMS_FACTORY);

49	qcon = qconFactory.createQueueConnection();

50	qsession = qcon.createQueueSession(false, Session.AUTO_ACKNOWLEDGE);

51	queue = (Queue) ctx.lookup(queueName);

52	qreceiver = qsession.createReceiver(queue);

53	qreceiver.setMessageListener(this);

54	qcon.start();

55

}

56

57	public void close()throws JMSException

58

{

59	qreceiver.close();

60	qsession.close();

61	qcon.close();

62

}

63

64	public static void main(String[] args) throws Exception

65

{

66	if (args.length != 1)

67

{

68	System.out.println("Usage: java QueueReceive WebLogicURL");

69

return;

70

}

71	InitialContext ic = getInitialContext(args[0]);

72	QueueReceive qr = new QueueReceive();

73	qr.init(ic, QUEUE);

74	System.out.println("JMS Ready To Receive Messages (To quit, send a \"quit\" message from QueueSender.class).");

75	// Wait until a "quit" message has been received.

76	synchronized(qr)

77

{

78	while (! qr.quit)

79

{

80

try

81

{

82	qr.wait();

83

}

84	catch (InterruptedException ie)

85

{}

86

}

87

}

88	qr.close();

89

}

90

91	private static InitialContext getInitialContext(String url) throws NamingException

92

{

93	Hashtable env = new Hashtable();

94	env.put(Context.INITIAL_CONTEXT_FACTORY, JNDI_FACTORY);

95	env.put(Context.PROVIDER_URL, url);

96	return new InitialContext(env);

97

}

98

}

Step10). Now compile and run the QueueRecieve.java program to read the messages from WebLogic JMS Queue.

java QueueReceive t3://localhost:7001
Reference:http://middlewaremagic.com/weblogic/?p=1987