JMS message id as JMS correlation ?

I read this document: "How to Correlate JMS Messages"
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/5059f110-0d01-0010-7c8b-fdc983be70c0
My scenario is AP1 -> XI -> SAP -> XI -> AP1, because AP1 sends lots of messages at the same time, so I need to use correlation. Current plan is we want to use JMS message id. But this document only describe to use the "XI message id", not "JMS message id".
I found in sender communication channel configuration, I can use JMS message id as the XI message id. But because I have a mapping before the BPM, it means the message received by BPM is not the message received by XI.
(detail scenario is AP1 -> XI -> mapping to another message -> BPM -> AP1.)

I got it, I can set the conversation id to the context object "ConversationID" of "http://sap.com/xi/XI/System", it's ok.

Similar Messages

Jms message id in jms sender channel

Hi
Is it working for you remove id from jmsmessageid in a jms sender channel?
I can see still in the logs that my message id is starting with ID:
Florin

Hi Florin !
You mean this:
"If you have selected JMSMessageID, JMSCorrelationID, or JMSProperty and entered a JMS message ID in these fields, you should see the Remove 'ID:' Marker from JMSMessageIDindicator. Set the indicator.
This is necessary because the JMS specification stipulates that each JMS message ID starts with 'ID'. However, this conflicts with ISO-11578."
Maybe you need to reactivate your sender comm channel to force the update of cache and try again. To reactivate, just edit your adapter, make any dummy changes (e.g. change description) and reactivate again.
Then try scenario once more and check if it is working.
Regards,
Matias.

JMS Message Property in JMS Receiver

Hi there,
I need to set a JMS String property of a message I send. This message is fixed for one channel.
We use XI 3.0 SP 20. I went through the documentation and saw that I can give up-tp 10 properties.
But only the name and the type.
But where can I get a value from.
Documentation sys that the technical name was DCJMSMessageProperty0, ...1 a.s.o.
Is that sth. for the adapter module? Is this a field that needs to have this name in the message? I do not get it.
Could you please lighten a bit the usage of this (strange) mechanism?
Thanks in advance,
Helge

Hi there,
there is a way (and a section somewhere in the help) to set adapter specific attributes in java mappings.
The java doc for that can be found here:
https://help.sap.com/javadocs/NW04/current/pi/index.html
Hope that helps sbd who also has that prob.
Cheers,
Helge

How to set message id for JMS

Hi All,
I set up the JMS connection with JBoss, and send the message asynchrously to JBoss successfully.
But right now, Jboss need to use the incoming message ID as correlation ID in Jboss.
How could i set the message id from payload (not PI message ID, not PI Conversation ID) for JMS receiver adapter?
thanks a lot
already check the following links:
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/5059f110-0d01-0010-7c8b-fdc983be70c0
Re: jms message id in jms sender channel
JMS Correlation ID
XI JMS mq series correlation id
cannot find any about set JMS Message ID from payload
Edited by: Lawrence on Dec 24, 2009 2:21 PM

Hi Lawrence,
I am not sure how jboss will store message,But i had done similar requirement but my system is MQ,Standard JMS adapter not supports to chnage the value or set mesage id in MQ,we can change the PI Message ID Value but not JBOSS/MQ Message ID.
Writng module is the one option.
Regards,
Raj

Setting JMS Selector as JMS Message ID

Does anyone knows how to set the JMS Selector as JMS Message id, i tried using JMSMessageID=P<720374.1242857046478.0> but i keep getting exception stating
javax.jms.InvalidSelectorException: weblogic.messaging.kernel.InvalidExpressionException: Expression : "JMSMessageID=P<720374.1242857046478.0>"
at weblogic.rjvm.BasicOutboundRequest.sendReceive(BasicOutboundRequest.java:108)
at weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:164)

Hi Tom,
Do you know any general solution for the situation you mentioned in your last post on this thread? Unfortunatelly one of our customers have an architecture which mixes a weblogic 8 domain with a weblogic 10 one. The JMS server is in the weblogic 10 domain but they have an OOB IGW application which runs on weblogic 8 and uses the JMS API of it. The IGW application applies the JMS Message Id model for correlating the request and response messages, but the consumer, on the weblogic 10 side, cannot find the response message because the JMS Message Id changed. The JMS of webloigc 8 - I guess - put an 'N' char after 'ID:' into the msgId and paste the whole id into the correlationId field. But on the weblogic 10 side, the consumer have the original msgId without 'N' and, of course, it doesn't find the response msg.
So do you have any general solution to convert between these different msgId formats?
Thanks in advance,
Andras

JMS Message Queue - stuck in

I am on SOA SUITE 11.1.17
I have a jms queue set up and am able to successfully send messages to it using the SOA JMS Adapter. I am able to succesfully listen to a queue using a JMS adapter in a different project.
However, here when I try to "listen" to the queue using a java program, the message is "received" in my java program and processed as it should be. The java program is running in a while loop, so it stays running.
On the queue, when the java program reads it, the message is moved to the "Messages Pending" column. When I kill the java program, the message is returned to the "Messages Current"
Would anyone have any ideas about this? We have an existing java based program isn't properly "closing" the message.
I tried:
1. placing msg.acknowledge() in the code, since the documentation states that messages that are in "Messages Pending" have been read, but not acknowledged or committed -- but this does nothing.
2. Setting the expiration on the message to 1, but that is a hack. I would rather fix the problem than use a hack.
Anyone have any ideas what is wrong?
Thank you,
Stuart
import java.io.IOException;
import java.io.InputStreamReader;
import javax.jms.Connection;
import javax.jms.JMSException;
import javax.jms.Message;
import javax.jms.MessageConsumer;
import javax.jms.MessageListener;
import javax.jms.Session;
import javax.jms.TextMessage;
public class JMSListenAndRespond extends JMSQueueHandler implements MessageListener {
private Session jmsSession = null;
private MessageConsumer jmsMessageConsumer = null;
private Connection jmsConnection = null;
int counter = 1 ;
public static void main(String[] args) throws Exception {
    InputStreamReader commandBuffer = null;
    char command = '\0';
      // first listen for any messages
      JmsDataObject q = new JmsDataObject();
      q.setJmsCF("jms/TestConnectionFactory");
      q.setJmsQueue("jms/TestJMSQueue");
      q.setServerPwd("welcome1");
      q.setServerLogin("weblogic");
      q.setUrl("t3://localhost:7101");
      q.setJmsMsg("na -- we are listinging...");
    JMSListenAndRespond lis = new JMSListenAndRespond();
     lis.consumeMessage(q);
    System.out.println("(type q to exit at any time...)\n");
    try {
      // Now just loop, waiting for messages until user types 'q' to quit
      commandBuffer = new InputStreamReader(System.in);
    while (!(command == 'q')) {
       try {
          command = (char)commandBuffer.read();
          System.out.println("Command: "+command);
          lis.stopListening();
        } catch (IOException e) {
          System.err.println("I/O Exception: ");
          e.printStackTrace();
       } //while
    } finally {
            lis.stopListening();
      lis.stopListening();
   public void stopListening() {
    try {
      if (jmsMessageConsumer != null) {
        jmsMessageConsumer.close();
      if (jmsSession != null) {
        jmsSession.close();
      if (jmsConnection != null) {
        jmsConnection.close();
    } catch (JMSException e) {
      System.err.println("Couldn't properly close all resources.\n");
      e.printStackTrace();
private void prepareToConsumeMessage() {
    // create JMS connection, session, consumer and register listener - then start session
        try {
      // create connection
      jmsConnection = getJmsConnectionFactory().createConnection();
      // create session
      jmsSession =   jmsConnection.createSession(false, javax.jms.Session.AUTO_ACKNOWLEDGE);
      jmsMessageConsumer = jmsSession.createConsumer(getJmsDestination());
      // register a message listener (onMessage)
      jmsMessageConsumer.setMessageListener(this);
      // initiate connection - make sure to register your listener first or you might lose messages
      jmsConnection.start();
      System.out.println("\n...listening for message!\n");
    } catch (JMSException e) {
      System.err.println("Problem initializing JMS session");
      e.printStackTrace();
      System.exit(-1);
     * onMessage
     * The callback function invoked upon message reception
public void onMessage(Message msg) {
    try {
      String msgText;
      if (msg instanceof TextMessage) {
        msgText = ((TextMessage)msg).getText();
        // this method expects a CSV string with the following makeup:
        // firstName,lastName,gender,birthdate,address,city,zipcode,state,insurancePolicyId
        String messageId = msg.getJMSMessageID();
      // code to process goes here.....
      } else {
        // if message is not a TextMessage, attempt a conversion to string
        System.out.println("\n** NEW MESSAGE (" + msg.getClass().getName() +
                           "):\n" +
            msg.toString());
    } catch (JMSException e) {
      e.printStackTrace();
public void consumeMessage(JmsDataObject q ) {
    initializeJndiProperties(q);
    initializeJNDIandCF(q.getJmsQueue());
    prepareToConsumeMessage();
import java.util.Properties;
import javax.jms.Connection;
import javax.jms.ConnectionFactory;
import javax.jms.Destination;
import javax.naming.InitialContext;
import javax.naming.NamingException;
public abstract class JMSQueueHandler {
protected void initializeJNDIandCF(String destinationQueueName) {
    // initialize JNDI context and lookup connection factory and destination
    try {
      // Initialize JNDI context
      jndiContext = new InitialContext(jndiProperties);
    } catch (NamingException e) {
      e.printStackTrace();
    try {
      // lookup JMS connection factory in JNDI
      jmsConnectionFactory =
          (ConnectionFactory)jndiContext.lookup(jndiProperties.getProperty("factory.name"));
      // lookup JMS destination in JNDI
      jmsDestination = (Destination)jndiContext.lookup(destinationQueueName);
    } catch (NamingException e) {
      System.err.println("Problem during the JNDI lookup\n");
      e.printStackTrace();
      System.exit(-1);
public void initializeJndiProperties(JmsDataObject qdo ) {
    // set JNDI properties
    jndiProperties.put("java.naming.factory.initial","weblogic.jndi.WLInitialContextFactory");
    jndiProperties.put("java.naming.provider.url", qdo.getUrl() );
   // jndiProperties.put("java.naming.security.principal", NAMING_PRINCIPAL);
    jndiProperties.put("java.naming.security.principal", qdo.getServerLogin() ) ;
    // jndiProperties.put("java.naming.security.credentials", NAMING_CREDENTIAL);
    jndiProperties.put("java.naming.security.credentials", qdo.getServerPwd() );
    //jndiProperties.put("factory.name", JMS_CONNECTION_FACTORY);
    jndiProperties.put("factory.name", qdo.getJmsCF() );
//protected static final String NAMING_PROVIDER_URL = "t3://localhost:7101";
//protected static final String NAMING_PRINCIPAL = "weblogic";
// protected static final String NAMING_CREDENTIAL = "welcome1";
// protected static final String JMS_CONNECTION_FACTORY = "jms/patientsJmsCF";
// protected static final String JMS_CONNECTION_FACTORY = "jms/TestConnectionFactory";
ConnectionFactory jmsConnectionFactory = null;
Destination jmsDestination = null;
InitialContext jndiContext = null;
Properties jndiProperties = new Properties();
public void setJmsConnectionFactory(ConnectionFactory jmsConnectionFactory) {
    this.jmsConnectionFactory = jmsConnectionFactory;
public ConnectionFactory getJmsConnectionFactory() {
    return jmsConnectionFactory;
public void setJmsDestination(Destination jmsDestination) {
    this.jmsDestination = jmsDestination;
public Destination getJmsDestination() {
    return jmsDestination;

Thanks for the reply. There are no errors what so ever regarding MDB issues. Not in the weblogic / console logging, nor in the logging of the component itself.
The MDB itself is setup to have 16 concurrent beans per component deployment. The component is clustered over 4 server instances. So there are quite some concurrent MDBs running. However since the messages get stuck for weeks eventhough the component only has bursts of messages to process, one would think that the the stuck messages would be processed whenever the component has some spare time (which it has a lot between the bursts).
Therefor i doubt it has anything to do with too little MDBs running. But frankly I have no idea what's wrong.

10 million messages in one jms-queue

Hi all,
          we want to put about 10 million jms-messages in a jms-queue with a jdbc
          persistent store on oracle database.
          Does anyone of you made experiences with that much messages in one
          queue? Are there any known limitations concerning the number of
          messages, e.g. according managing overhead, etc?
          Thanks for any comment,
          Klaas

The $ is not a valid character for an element NAME per W3C standards. In short you can only use letters, numbers and the underscore ( _ )..
You need to correct this message / data and reprocess the message.
Setup an Error Queue so these messages get thrown some where that will not cause issues in your system. Then use error handling in something like AIA to report back to your support staff that a bad message was encountered, needs to be fixed and reprocessed.
You will see that if you do a google search for how to escape a dollar sign in xpath, there are no good results....
Hope that helps!
-Luke

Valid JMS Message status

Hello All,
I have two WLS domains. One WLS 10.3.X, another is WLS 8.1.X
Each domain have one queue each (e.g. 10.3.X => Q1 & 8.1.X => Q2) and the 10.3.X domain have been configured with a MessageBridge to deliver the messages from Q1 to Q2
Each domain have ConnectionFactories XA enabled and the Bridge adapter is also set to "eis.jms.WLSConnectionFactoryJNDIXA"
Now the Bridge is showing active, but if we put a test message in Q1, it is taking long to be delivered to Q2. There is no error in the logs (Debug Flgs have also been enabled).
Sometimes it is also not being delivered at all.
During this, the status of the message in the Q1 is showing "receive transaction".
So can anyone tell me :
1> what are the valid status of any message in wls jms queues and what are the meaning of them.
2> what is the lifecycle of a message.
Thanks in advance

http://docs.oracle.com/cd/E24329_01/apirefs.1211/e24391/weblogic/jms/extensions/JMSMessageInfo.html#JMSMessageInfo(long,%20int,%20java.lang.String,%20long,%20java.lang.String,%20weblogic.jms.extensions.WLMessage,%20java.lang.String,%20boolean)
"visible - The message is visible on the destination and may be consumed.
send - The message is pending because it is associated with an in progress send operation.
receive - The message is pending because it has been received by a consumer but not yet acknowledged.
transaction - The message is associated with a transactional “send” or “receive” operation that is in progress.
ordered - The message belongs to a Unit-of-Order (UOO).
delayed - The message is pending because it has a scheduled delivery time or is otherwise delayed.
expired - The message has expired and is no longer available for consumption.
redelivery-count-exceeded - The message has exceeded the redelivery count set for the destination and is no longer available for consumption.
paused - The message is pending because of a destination pause operation .
sequenced - The message that is part of a SAF sequence.
unit-of-work-component - The message is part of an Unit-of-Work (UOW).
deleted - The message is marked for deletion."
You can enable message life cycle logging
- http://docs.oracle.com/cd/E24329_01/web.1211/e24385/troubleshoot.htm#i1128815
"The message life cycle is an external view of the events that a JMS message traverses through once it has been accepted by the JMS server, either through the JMS APIs or the JMS Message Management APIs. Message life cycle logging provides an administrator with easy access to information about the existence and status of JMS messages from the JMS server viewpoint. In particular, each message log contains information about basic life cycle events such as message production, consumption, and removal."
There is also a WLST script provided here (Re: Example using of getMessage(s) with JMS error queues? for browsing messages on a given destination.

Why are my JMS messages automatically dequeued without consumer?

I created a simple in-memory JMS queue.
Now I wrote a BPEL process which writes (successfully ?) JMS message to this JMS queue.
Another consuming BPEL process is deployed but not started.
However I cannot see them in MBean JMSDestinationResource on the OC4J Enterprise Manager Web page.
When I tell the AppServer to browse all currently existing (and waiting) JMS message then there are none.
However the statistics for this queue show 17 messagesEnqueued and 17 messagesDequeued Messages.
It seems to me that my JMS messages are automatically dequeued. But why?
Are in-memory JMS messages not persistent (as long as the AppServer is up and running) ?
Do I have to set a certain preference to let JMS live in the Queue as long as they are not retrieved by another BPEL process?
Furthermore I tried the following:
I started a consuming BPEL process. Yes, he is waiting at the JMS adapter until a new JMS message arrive.
Then I send from the first BPEL process a JMS message. But even when consumption is possible the JMS message is dequeued and not forwarded to the consumer.
Why?
Peter

It seems to me that my JMS messages are automatically dequeued. But why?
This is how BPEL PM is designed; The activation-agent is running that belongs to the BPEL process. When a message arrives in a Queue or Table or File it is read into the dehydration store. Then an instance of the appropriate BPEL process is started. This functionality makes the system more stabel and reliable when something is goingin wrong in quees/files/db or any adapter that is used for polling.Are in-memory JMS messages not persistent (as long as the AppServer is up and running) ?
As you desribed: in-memory messages are only persistent in memory, if you restart the server, the messages are gone.Do I have to set a certain preference to let JMS live in the Queue as long as they are not retrieved by another BPEL process?
No you can not.Marc
http://orasoa.blogspot.com

WAS and JMS Message Server

Does WAS provide a JMS messaging server (as distinct to just the JMS J2EE interface)? If I want to use WAS and JMS do I need to provide my own server or is it part of WAS?

Hi Rick,
Yes, SAP Web AS comes with a JMS messaging server (called JMS provider). For more information please refer to the <a href="http://help.sap.com/saphelp_nw04/helpdata/en/a3/63af1bbf09469fa1615c05f0daff6f/frameset.htm">Development Manual</a> or <a href="http://help.sap.com/saphelp_nw04/helpdata/en/90/57849e5e3e45d784afc4e3bfa8136f/frameset.htm">Administration Manual</a>
Hope that helps!
Vladimir

Correlation for JMS Messages possible? JMSCorrID in JMSHeader not accepted

Is Correlation for communication over JMS messages possible?
If I define the JMSHeader field "JMSCorrelationID" in a correlation set ("as usual") then I get
compiler errors:
Error ORABPEL-10036: invalid correlation set
BPEL seems not to accept JMSHeader fields for correlation but only fields from the actual payload msg.
Is this true?
Is there soemwhere a guide on how to correlate JMS messages?
Thank you
Michael

you can use the "Message Selector" on the JMS adapter to filter to achieve that;
here is extract from oracle help document
Message Selector
Specify filtering logic that enables you to receive messages that match a certain criteria. Enter an expression between 1 and 255 characters in length. Use SQL92 syntax in this field. The JMS server uses this criteria to filter messages received by this consumer. The message selector works with variables defined in standard JMS headers and user-defined properties. You cannot use variables or elements that are in the payload of the message.
For example, you can enter logic such as: JMSPriority > 3. Based on this, messages with a priority greater than 3 are consumed; all other messages are rejected. JMSType = 'car' AND color = 'blue' AND weight > 2500 Country in ('UK', 'US', 'France')
it's got some limitations but works fine for our requirements so far...

Adapter Status Error : Error in creating message ID map for JMS message:

Currently in the SAP XI 3.0 JMS Adapter, I am receiving the following error
Error in creating message ID map for JMS message:
ie. Error while processing message 'de8265f6-c864-4479-1137-9bab17b78b3b'; detailed error description: com.sap.aii.adapter.jms.api.channel.filter.MessageFilterException: Error in creating message ID map for JMS message: ID:c3e2d840d8d4d7f14040404040404040c44f8e2213630b01 at com.sap.aii.adapter.jms.core.channel.filter.InboundDuplicateCheckFilter.filter(InboundDuplicateCheckFilter.java:103)
Although I am receivng this error, when I check the details of the message processing, all steps are successful and the message is set to status : DLVD
Audit Log for Message: de8265f6-c864-4479-1137-9bab17b78b3b
Time Stamp     Status     Description
09.06.2009 13:27:24     Success     New JMS message with JMS message ID ID:c3e2d840d8d4d7f14040404040404040c44f8e2213630b01 received. The XI message ID for this message is de8265f6-c864-4479-1137-9bab17b78b3b
09.06.2009 13:27:24     Success     JMS message converted to XI message format successfully
09.06.2009 13:27:24     Success     RRB: entering RequestResponseBean
09.06.2009 13:27:24     Success     RRB: suspending the transaction
09.06.2009 13:27:24     Success     RRB: passing through ...
09.06.2009 13:27:24     Success     RRB: leaving RequestResponseBean
09.06.2009 13:27:24     Success     Transform: using Transform.Class: com.sap.aii.messaging.adapter.Conversion
09.06.2009 13:27:24     Success     Transform: transforming the payload ...
09.06.2009 13:27:24     Success     Transform: successfully transformed
09.06.2009 13:27:24     Success     Application attempting to send an XI message synchronously using connection JMS_http://sap.com/xi/XI/System.
09.06.2009 13:27:24     Success     Trying to put the message into the call queue.
09.06.2009 13:27:24     Success     Message successfully put into the queue.
09.06.2009 13:27:24     Success     The message was successfully retrieved from the call queue.
09.06.2009 13:27:24     Success     The message status set to DLNG.
09.06.2009 13:27:25     Success     The application sent the message synchronously using connection JMS_http://sap.com/xi/XI/System. Returning to application.
09.06.2009 13:27:25     Success     The message was successfully transmitted to endpoint http://sapxia.swets.nl:8000/sap/xi/engine?type=entry using connection JMS_http://sap.com/xi/XI/System.
09.06.2009 13:27:25     Success     The message status set to DLVD.
Not sure why this is occurring.......

No, not using correlation id.
I was able to resolve the issue on this queue by changing the following setting
Under the PROCESSING tab, under XI SETTINGS
Time period for Duplicate Check for EO(IO) (secs) it was set to 86400
I have changed this to 300 seconds and the adapter has now gone green.
BUT......
That said, I have the exact scenario on another sender JMS channel set to 300 seconds and it exhibits the same issue.
correlation settings:
Set XI message id to = GUID
Set Xi conversation

How To Set JMS Message ID

Hi,
I am working for a client that uses a MQ Series as their interface routing infrastructure. They have written some custom tools that log MQ messages. Their tools expect the MQ message ID to be in a specific format YYYY_MM_DD_HHMMSS_AAAAAA where AAAAAA is a unique set of characters based on the millisecond.
Is it possible to set the JMS message ID on a JMS receiver adapter?
Thanks in advance for your help,
Craig

Hi Craig,
as it looks you have to set the Message Id in a special format. I am not sure if this is possible at all. I didn't find a way to influence how XI sets the JMS Message Id.
Maybe you could work with the JMS Correlation ID instead and have your client adapt his tools. You can use either a User-Defined Function or a Java Mapping, setting the so-called Adapter-specific attribute DCJMSCorreleationId
Here you can find an example how to do this in the User-Defined Function:
http://help.sap.com/saphelp_nw04/helpdata/en/43/03612cdecc6e76e10000000a422035/frameset.htm
In a Java Mapping it is similar:
http://help.sap.com/saphelp_nw04/helpdata/en/43/09b16006526e72e10000000a422035/frameset.htm
This example uses the File Adapter, but the same applies for the JMS Adapter.
The JMS Adapter has the namespace http://sap.com/xi/XI/System/JMS
Have a look at this one to find out more about the Adapter-specific attributes of the Receiver JMS Adapter:
http://help.sap.com/saphelp_nw04/helpdata/en/10/b1b4c8575a6e47954ad63438d303e4/frameset.htm
I hope that this information is of some help for you.
regards,
Peter

Format of "JMS Message Destination Parameter" for JMS Sender Adapter

Hi,
I am trying to use the JMS Sender Communication Channel for several Interfaces by using the "JMS Message Destination Parameter". Currently, the Comm.Channel is reading the message and puts it back on the queue with the following error:
Fehler bei der XI-Eingangsverarbeitung für Message am bzw. um 2007-07-25|09:34:12.057+0200. JMS- und XI-Identifikatoren für die Message sind ID:414d512051535749515441302020202046a4e892201c4d04 bzw. 701ec850-3a81-11dc-8176-00306e2c36a3. Der JMS-Adapter führt einen Rollback der Datenbank und der JMS-Sitzungtransaktionen durch. Wird die Sitzung ausgeführt, geht die Message nicht verloren und wird später erneut durchgeführt. Der Ausnahme-Stack-Trace ist java.lang.RuntimeException: MQJMS0003: Destination not understood or no longer valid: UserCreateRequest
at com.ibm.mq.jms.MQDestination.createDestination(MQDestination.java:790)
at com.ibm.mq.jms.MQSession.createDestination(MQSession.java:1092)
at com.ibm.jms.JMSMessage.getJMSDestination(JMSMessage.java:4127)
What is the format I will have to fill this parameter with in order for XI to understand it? I have tried the following so far which did not work:
1. (as in error message above)
Help much appreciated.
KR,
Colin.

One option in BPEL is to have a mid process receive, but this would require you to handle the Correlation of the message with BPEL process instance.
Please refer the following section in SOA Guide for the same.
Using Correlation Sets and Message Aggregation - 11g Release 1 (11.1.1.7)
Please note the example is with File adapter but the same can be achieved for Any Adapter.

JMS/AQ: Setting properties for JMS message using PL/SQL

I have created a procedure in PL/SQL that uses JMS messages, and now I need to include a property so that the subscriber can use a message selector to filter out unwanted messages. Is this possible using PL/SQL?
A previous post said: "... But you can have properties in the message payload itself and also define selectors on the message content ...". But I looked at Sun's tutorial and there it said: "A message selector cannot select messages on the basis of the content of the message body."
I have 300 different screens and messages apply only to one screen at a time. When the user is looking at screen 'A' I want him to only recieve messages that apply to screen 'A'. I thought I would do this with message selector, but is there any other way?
Here is my code(borrowed from an earlier post)
PROCEDURE ENQUEUE_JMS_MESSAGE AS
BEGIN
DECLARE
Enqueue_options DBMS_AQ.enqueue_options_t;
Message_properties DBMS_AQ.message_properties_t;
Message_handle RAW(16);
User_prop_array SYS.AQ$_JMS_USERPROPARRAY;
Agent SYS.AQ$_AGENT;
Header SYS.AQ$_JMS_HEADER;
Message SYS.AQ$_JMS_TEXT_MESSAGE;
Message_text VARCHAR2(100);
BEGIN
Agent := SYS.AQ$_AGENT('',NULL,0);
User_prop_array := SYS.AQ$_JMS_USERPROPARRAY();
Header := SYS.AQ$_JMS_HEADER( Agent, '', 'aq1', '', '', '', User_prop_array);
Message_text := 'Message 1 from PL/SQL';
Message := SYS.AQ$_JMS_TEXT_MESSAGE(Header, LENGTH(Message_text), Message_text, NULL);
DBMS_AQ.ENQUEUE(queue_name => 'tstopic',
Enqueue_options => enqueue_options,
Message_properties => message_properties,
Payload => message,
Msgid => message_handle);
END;
END;
-Christer

Thanks for the answer. I managed to set the Correlation id and retrieve it using getJMSCorrelationID(). But I did not manage to use the MessageSelector on it. I have used the Topicbrowser which is not part of the JMS standard? I tried to enqueue the messages using Java too and tried to use the topicbrowser on both JMSCorrelationID and user defined properties withou success. Is there some special requirements of the TopicBrowser?
Enumeration messages;
oracle.jms.TopicBrowser browser =tsess.createBrowser(topic, "TS", "JMSCorrelationID = 'TST'");
int count = 0;
messages = browser.getEnumeration();
if(messages.hasMoreElements())
System.out.println("message"); //never executed
dtxtmsg = (TextMessage)(tsub1.receiveNoWait()) ; //returns a message
String corrID = dtxtmsg.getJMSCorrelationID(); //returns: TST
Thanks for your help so far...it would really save my day if you have some ideas on this too!
-Christer

JMS message id as JMS correlation ?

Similar Messages

Maybe you are looking for