JMS Message Headers

Hi,
I have a IDOC -> SAP PI -> JMS scenario. JMS service is an External Party.
I have to populate the JMS message Header with Fields like JMSType, Sender and Receiver. These fields will come from the IDOC. How to populate these?
<JMSType>Notification</JMSType>
<Sender>SAPR3</Sender>
<Receiver>JMSService</Receiver>
If I am not wrong, I have to make use of Dynamic Configuration and populate, but if I look at the available JMS ASMA, I am not able to decide how (which fields to use) to populate. Earlier I had done Dynamic Configuration for FILE and SOAP adapters.
Thank you,
Pankaj.
Edited by: Pankaj Sharma XI on Oct 4, 2010 2:38 PM

Hi Raj and Amol,
Thank you for responding.
anyway you can try to use dynamic configuration UDF, it will work.
Yes I will do it using UDF.
Add AF_Modules/DynamicConfigurationBean and set the value of the above
If I use DynamicConfigurationBean, then the value will be static, the one which I fill in the Communication Channel. So I have to make use of UDF.
What I think is:
1) Create a UDF in message mapping with below logic:
DynamicConfiguration conf = (DynamicConfiguration) container.getTransformationParameters().get
(StreamTransformationConstants.DYNAMIC_CONFIGURATION);
DynamicConfigurationKey key1 = DynamicConfigurationKey.create("http://sap.com/xi/XI/System/JMS","DCJMSMessageProperty0"); //also logic for Property1 and Property2.
conf.put(key1,MessageType); //MessageType comes from IDOC.
return ""; //no need to return a value.
2) Create a Receiver JMS channel with below settings:
Specify Additional JMS Message Properties
Name - MsgType Java Type - String
Name - Sender Java Type - String
Name - Receiver Java Type - String
Now with the above settings I should (hopefully) get the headers like:
<MsgType>AbcValidation</MsgType>
<Sender>SAPR3</Sender>
<Receiver>JMSReceiver</Receiver>
I will try with the above configuration and update the thread accordingly. *If you feel that the approach is wrong/ incomplete, then
please do respond.*
Thank you,
Pankaj.

Similar Messages

Trouble using JMS Message Selector and DCJMSMessageProperty0

Hello Experts!
My scenario is Mainframe => MQ => JMS Adapter => XI => SAP
My MQ channel is communicating fine to XI and I've set the JMS adapter to JMS Compliant.
I have multiple message types with consistent headers but varying data layouts that I need to route to different mapping objects. So it seems the best solution for this is JMS Message Selector based on reading a header value from one of the dynamic message properties.
I've read SAP Notes and SAP Library and SDN Wiki articles about this configuration and I think its possible.
http://help.sap.com/saphelp_nw04s/helpdata/en/10/b1b4c8575a6e47954ad63438d303e4/frameset.htm
Note 856346 - J2EE JMS Adapter: Frequently Asked Questions (FAQ)
Note 1086303 - XI JMS Adapter and IBM Websphere MQ: FAQ
https://www.sdn.sap.com/irj/scn/wiki?path=/display/xi/usage%252bof%252bmessage%252bselector%252bfor%252bjms%252bsender%252badapter
My mainframe sends an MQ message that includes some extra header information like
field: ApplType VALUE: 000000002
field: ApplName VALUE: MIS056O
I configured my Communication Channel to set Adapter-Specific Message Attributes and also Additional JMS Message Properties to include ApplType and ApplName.
However, I can only see some of the standard JMS header items such as CorrelationID, none of the additional ones.
In RWB I see "JMS property 'ApplType' that corresponds to dynamic header 'DCJMSMessageProperty0' is missing from JMS message 'ID:f2f0f0f9f0f4f2f1f0f9f1f5f5f3f7f44040404040404040'; consequently it cannot be added to XI message 'e136a6e8-8580-4adc-2007-9ccab93f1ef4' as a dynamic header"
Can anyone with some experience doing this help me see if I'm missing a trick somewhere? How can I see where this information is being dropped? Could it be when MQ is handing to JMS?
Many thanks,
Aaron

After sifting through some IBM documentation I found that the PutApplName field actually maps to JMS name JMSXAppID. So after adding this to my Additional JMS Message Properties list I get the dynamic JMS message property I need for sorting out the messages.
http://publib.boulder.ibm.com/infocenter/wmqv6/v6r0/topic/com.ibm.mq.csqzaw.doc/uj25450_.htm

How to read JMS message properties from BPEL or BPMN process

Hi all,
I have a JMS Adapter that consumes messages from a remote ActiveMQ queue and I don't find the way the get the properties of the JMS message as I would like to map them in BPEL or BPMN process variable. I only manage to get the content of the message.
I've also read that if using a MapMessage, one of the map entry can be mapped directly and that the other map entries go to jca.jms.Map.xxxx where xxxx is key of the map entry.
But how can I map those "jca.jms.Map.xxxx" properties on process variables ? and how to map JMS Properties (that seem to be mapped on jca.jms.JMSProperty.xxxx) to process variables ?
I use SOA Suite version : 11.1.1.4.0
Thanks for your help

SOA Suite 11g - how to set/get JMS headers ?

JMS Message Expiry Period (msecs) in Synchronous JMS scenario

Hi,
I've configured a Proxy->JMS synchronous scenario using Sync/Async Bridges in the Receiver JMS adapter. All is well when the reply queue is working but when the reply queue is down, the waiting time in the JMS receiver adapter is too long. It can be up to a minute or more. We want to shorten the wait time for the reply. On the receiver adapter, I've tried using 'JMS Message Expiry Period (msecs)' in the JMS setting but it doesn't seem to have any effect. Then I tried switching on the 'JMS Message Expiration' under Adapter-Specific Mesage Attribute. However I get the following error:
Dynamic record/records: DCJMSExpiration,DCJMSTimestamp, that correspond to the JMS property/properties: JMSExpiration,JMSTimestamp, respectively is/are either missing from the message: deacb6f9-56e0-3bf1-af90-00145e6880b6, or have invalid types specified in the channel configuration
Message processing failed. Cause: com.sap.engine.interfaces.messaging.api.exception.MessagingException: Dynamic header records are missing/incorrect specified in message: deacb6f9-56e0-3bf1-af90-00145e6880b6. Erroneous/Unspecified headers are:[ DCJMSExpiration DCJMSTimestamp ]
Any one has an idea? Thanks in advance.

Hi,
When queue down normally JMS Receiver Communication channel tries 3 times to send message to Queue,when it tries 3 times the retrievel time its not possible to predict,may be you need to chnage the setting at basis level for retry interval.
check with basis team.
Regards,
Raj

Writing SOAP messages into JMS message

I have a system that has WSDL "contracts" for messaging, and we want to use a JMS infrastructure to send SOAP messages.
From all the clients that I have seen generated they all want to talk HTTP, or use their own way of using JMS.
What I would like to do is generate a client for the WSDL that just generates SOAP messages in a string, which I can then put on a JMS message (with special custom JMS headers setup etc).
Any ideas ?
I guess I am trying to do something similar to what JAXB does with normal schemas.

push

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...

JMS Message Encryption

Does Weblogic Server (any version) provide built-in support for JMS message encryption
using digital certificates etc.?
To be more precise I am asking about that similar encryption options for JMS message
that is provided by Tibco JMS or SonicMQ.

1. Does JMS provide an API call to retrieve the MQ
Header information -- specifically the user id and
password if any? Or does the JMS header hide/override
the MQ header?There is a property defined by JMS called JMSXUserID which will give you the user id. MQSeries does not transmit the password of the user, this would probably be a security violation. If there is a JMS property which is matched in the MQ Message header the property is held there. There are some IBM specific properties to get at other information in the MQ Message header but these should not be used.
2. Does JMS provide an encryption mechanism to encrypt
the message body?JMS doesn't and neither does MQSeries, as far as I am aware. If you wish to encrypt then you can define a security exit on the queue when you bind it into JNDI, but this is an MQSeries feature not a JMS one.
3. What is in the JMS header -- additional security
information?Look in the MQSeries Information Center. There is lots of information on what is in the headers and how to access it.
>
Lastly, can we send binary data using JMS over
MQSeries?Just use a bytes message.
Hope this helps

Saving a JMS Message in a Persistent Store

Hello Friends,
I am going to store a JMS message in a persistent store like a database and then recreate it when needed. What I will be doing is storing the JMS headers individually. Then storing all the properties and then the message body. I just wanted to confirm that with this data I would be able to recreate the entire message.

Not sure of the answer to this (I suspect re-creating the message with exactly the same values as it started with will be a bit more tricky than you would imaging). Why don't you try creating a blank message and setting every single header / property? You'll probably get some exceptions / values being over written when you send.
The real question is are you 100% sure you need to do this? The whole idea smells fishy. Why do you need the JMS Headers? Things would be far easier if the body of the message contained everything you needed. Why do you have to store the message in a database rather than leave it on a persistent queue?

JMS message dump

Can an entire jms message (including headers, properties, etc) be "dumped" into, say, a string? Any suggestions to do this?

Its certainly not in the spec.
Some providers will give you a sensible output from toString(), others will not.
If you just want to dump it to a string for debug its a pretty easy task to dump the header and payload programmatically in some nice format - take you an hour or so to write.
Regards,
Colin
http://hermesjms.com

Need suggestion on implementing JMS message error recovery

Hi,
Our application has a JMS topic where we publish application events. Now, there can be scenarios where the consumers cannot process the message due to some infrastructure issues and would error out. We need a way so that those messages can be reprocessed again later. we are thinking of the following design for JMS message error recovery
1. Use a persistent TOPIC (this would ensure guaranteed delivery)
2. Configure a error destination on JMS topic e.g a jms queue
3. Have an error handling MDB listening to the Error destination. An error handling MDB would dequeue the errored messages from error destination and persist it to a Data base "error" table..
4. Provide a mechanism to republish those messages to topic (e.g a scheduler or admin ui or a command line utility) .. The messages would deleted from database "error" table and published to topic again....
A. Are there any issues with the above design which we need to handle?
B. Are there any additional steps required in a Cluster environment with a distributed topic and distribute error destination? (our error mdb will have one-copy-per-application setting)
B. From a performance angle, Is it OK to use persistent TOPIC ? Or will it better to persist the message to the db table and then publish it as a non persistent message ... ? (But i guess the performance should be more or less the same in both of these approaches)
C. Are there any other recommended design patterns for error recovery of JMS messages
Please advise.
Regards,
Arif

Thanks Tom !
We may not be able to go with the approach of delaying/pausing redelivery of the messsage because
1. Pausing entire MDB approach: Our MDB application consumes messages generated by different producers and our MDB needs to continue processing the messages even if messages corresponding to one producer is erroring out
2. Redelivery delay : This would only delay the retry of an errored message. But there would still be a problem if the message fails during all retries (i.e redelivery limit count). We don't want to lose this message. In our case, It is possible that a particular message cannot be processed due to unavailability of a third party system for hours or may be a day.
Basically, i am looking on approaches for a robust and performant error recovery/retry framework for our application (refer details in my first post on this thread) while fully making use of all features provided by middleware (WLS). Please advise.
Regards,
Arif

Lost (and found) JMS - messages

 Using WLS 6.1 and have experienced that JMS messages has not been delivered to
 its consumer correctly. We are interested in any suggestions to what has happend,
 what can be done to avoid the problem in the future, or perhaps how we can find
 out more about the problem.
 We have a message driven bean A which sends messages to the queue Q, of which
 the message driven bean B is the only consumer.
 What we recently have experienced is that some of the messages delivered by A
 to Q never are delivered to B. But the messages seems to be persisted correctly,
 because after a restart they reappear!
 Following is a more detailed description of the scenario:
 1. A message is sendt with DeliveryMode=PERSISTENT and TimeToLive=0. QueueSender.send
 is invoked and returns normally.
 2. The consumers never gets the message (B.onMessage i never invoked with this
 message).
 3. Point 1-2 is repeated for 13 different messages over a period when ~100 similar
 messages are delivered normally.
 4. The server is then restarted.
 5. In the starup log it is indicated that 44 records are found in the JMSStore.
 6. When the server restarts, the "lost" messages gets delivered to B.
 After the server restart we have not experienced the problem again.
 Logs does not show anything unusual about the previous restart.
 Other details:
 There is always exatly 1 instance of A running, and 5-20 instances of B. A implements
 and uses a pool of javax.jms.XAQueueSession instances, which shares a single instance
 of javax.jms.XAQueueConnection. The aknowledge-mode for B is "Auto-aknowledge".
 We're using Weblogic Server 6.1.3.0 / Red Hat Linux 7.3.
 Any help on this problem is appreciated!


 I believe we've seen just the behaviour you describe on 6.1 SP2, but only on a
 multi-cpu box (Solaris), and only under load. We can't reproduce the problem reliably,
 and get no error messages/warnings anywhere, so very little to send to customer
 support; by the time we notice this, the problem's long passed, so a thread dump's
 of no use.
 We're going to try and see how SP5 (which has loads of JMS fixes) pans out.
 But if you find anything out, could you post here?
 simon.
 "Harald Stendal" <[email protected]> wrote:
 >
 >Using WLS 6.1 and have experienced that JMS messages has not been delivered
 >to
 >its consumer correctly. We are interested in any suggestions to what
 >has happend,
 >what can be done to avoid the problem in the future, or perhaps how we
 >can find
 >out more about the problem.
 >
 >We have a message driven bean A which sends messages to the queue Q,
 >of which
 >the message driven bean B is the only consumer.
 >What we recently have experienced is that some of the messages delivered
 >by A
 >to Q never are delivered to B. But the messages seems to be persisted
 >correctly,
 >because after a restart they reappear!
 >
 >Following is a more detailed description of the scenario:
 >
 >1. A message is sendt with DeliveryMode=PERSISTENT and TimeToLive=0.
 >QueueSender.send
 >is invoked and returns normally.
 >2. The consumers never gets the message (B.onMessage i never invoked
 >with this
 >message).
 >3. Point 1-2 is repeated for 13 different messages over a period when
 >~100 similar
 >messages are delivered normally.
 >4. The server is then restarted.
 >5. In the starup log it is indicated that 44 records are found in the
 >JMSStore.
 >6. When the server restarts, the "lost" messages gets delivered to B.
 >
 >After the server restart we have not experienced the problem again.
 >
 >Logs does not show anything unusual about the previous restart.
 >
 >Other details:
 >There is always exatly 1 instance of A running, and 5-20 instances of
 >B. A implements
 >and uses a pool of javax.jms.XAQueueSession instances, which shares a
 >single instance
 >of javax.jms.XAQueueConnection. The aknowledge-mode for B is "Auto-aknowledge".
 >
 >We're using Weblogic Server 6.1.3.0 / Red Hat Linux 7.3.
 >
 >Any help on this problem is appreciated!
 >

Problem in sending JMS message on remote OC4J

I have two OC4J standalone (10.1.3.0.0 build 041119.0001.2385)
The containers work on Windows2000 in different machines connected by the LAN.
The First container has deployed application from example http://www.oracle.com/technology/tech/java/oc4j/1013/howtos/how-to-jca-intro/doc/how-to-jca-intro.html
The second container has j2ee application (Servlet) that sending JMS messages in the queue of the first container.
Code Servlet in second OC4J:
package mypackage2;
import javax.servlet. *;
import javax.servlet.http. *;
import java.io. PrintWriter;
import java.io. IOException;
import javax.jms. *;
import javax.naming. *;
import java.util. *;
public class Servlet1 extends HttpServlet
private static final String CONTENT_TYPE = "text/html;charset=windows-1251";
public void init (ServletConfig config) throws ServletException
super.init (config);
String QUEUE_NAME = "OracleASjms/MyQueue1";
String QUEUE_CONNECTION_FACTORY = "OracleASjms/MyQCF";
public void doGet (HttpServletRequest request, HttpServletResponse response)
throws ServletException, IOException
response.setContentType (CONTENT_TYPE);
PrintWriter out = response.getWriter ();
out.println (" < html > ");
out.println (" < head > < title > Servlet1 < /title > < /head > ");
out.println (" < body > ");
try
Hashtable env = new Hashtable ();
env.put (Context. INITIAL_CONTEXT_FACTORY, "oracle.j2ee.rmi.RMIInitialContextFactory");
env.put (Context. SECURITY_PRINCIPAL, "admin");
env.put (Context. SECURITY_CREDENTIALS, "admin");
env.put (Context. PROVIDER_URL, "ormi://host_OC4J_1:23791/jcamdb");
env.put ("dedicated.rmicontext", "true");
InitialContext ic = new InitialContext (env);
QueueConnectionFactory connectionFactory = (QueueConnectionFactory)ic.lookup (QUEUE_CONNECTION_FACTORY);
QueueConnection connection = connectionFactory.createQueueConnection ();
connection.start ();
QueueSession queueSession =
connection.createQueueSession (false, Session.AUTO_ACKNOWLEDGE);
Queue queue = (Queue) ic.lookup (QUEUE_NAME);
ic.close ();
System.out.println (" Queue: " + queue);
QueueSender sender = queueSession.createSender (queue);
System.out.println (" creating Message: " + queue);
Message message = queueSession.createMessage ();
System.out.println (" Message created ");
message.setJMSType ("theMessage");
message.setLongProperty ("time", System.currentTimeMillis ());
message.setStringProperty ("id", "11111");
message.setStringProperty ("oamount", "55555");
message.setStringProperty ("message", "77777");
message.setStringProperty ("RECIPIENT", "MDB");
System.out.println (" Sending message... ");
sender.send (message);
System.out.println (" Message sent ");
sender.close ();
queueSession.close ();
connection.close ();
catch (Exception e)
System.out.println (" ** TEST FAILED ** Exception: " + e);
out.println (e.toString ());
e.printStackTrace ();
out.println (" The servlet has received a GET. This is the reply. < /html > ");
out.close ();
Error: This code send message in The First container, and should send in the second OC4J !!!!
Please answer :
As configure (what code it is necessary to write) servlet (any J2EE the application in OC4J) to use a path to OC4J JMS (remote OC4J JMS) through the Resource Adapter (using OracleASjms.rar). ???

I have two OC4J standalone (10.1.3.0.0 build 041119.0001.2385)
The containers work on Windows2000 in different machines connected by the LAN.
The First container has deployed application from example http://www.oracle.com/technology/tech/java/oc4j/1013/howtos/how-to-jca-intro/doc/how-to-jca-intro.html
The second container has j2ee application (Servlet) that sending JMS messages in the queue of the first container.
Code Servlet in second OC4J:
package mypackage2;
import javax.servlet. *;
import javax.servlet.http. *;
import java.io. PrintWriter;
import java.io. IOException;
import javax.jms. *;
import javax.naming. *;
import java.util. *;
public class Servlet1 extends HttpServlet
private static final String CONTENT_TYPE = "text/html;charset=windows-1251";
public void init (ServletConfig config) throws ServletException
super.init (config);
String QUEUE_NAME = "OracleASjms/MyQueue1";
String QUEUE_CONNECTION_FACTORY = "OracleASjms/MyQCF";
public void doGet (HttpServletRequest request, HttpServletResponse response)
throws ServletException, IOException
response.setContentType (CONTENT_TYPE);
PrintWriter out = response.getWriter ();
out.println (" < html > ");
out.println (" < head > < title > Servlet1 < /title > < /head > ");
out.println (" < body > ");
try
Hashtable env = new Hashtable ();
env.put (Context. INITIAL_CONTEXT_FACTORY, "oracle.j2ee.rmi.RMIInitialContextFactory");
env.put (Context. SECURITY_PRINCIPAL, "admin");
env.put (Context. SECURITY_CREDENTIALS, "admin");
env.put (Context. PROVIDER_URL, "ormi://host_OC4J_1:23791/jcamdb");
env.put ("dedicated.rmicontext", "true");
InitialContext ic = new InitialContext (env);
QueueConnectionFactory connectionFactory = (QueueConnectionFactory)ic.lookup (QUEUE_CONNECTION_FACTORY);
QueueConnection connection = connectionFactory.createQueueConnection ();
connection.start ();
QueueSession queueSession =
connection.createQueueSession (false, Session.AUTO_ACKNOWLEDGE);
Queue queue = (Queue) ic.lookup (QUEUE_NAME);
ic.close ();
System.out.println (" Queue: " + queue);
QueueSender sender = queueSession.createSender (queue);
System.out.println (" creating Message: " + queue);
Message message = queueSession.createMessage ();
System.out.println (" Message created ");
message.setJMSType ("theMessage");
message.setLongProperty ("time", System.currentTimeMillis ());
message.setStringProperty ("id", "11111");
message.setStringProperty ("oamount", "55555");
message.setStringProperty ("message", "77777");
message.setStringProperty ("RECIPIENT", "MDB");
System.out.println (" Sending message... ");
sender.send (message);
System.out.println (" Message sent ");
sender.close ();
queueSession.close ();
connection.close ();
catch (Exception e)
System.out.println (" ** TEST FAILED ** Exception: " + e);
out.println (e.toString ());
e.printStackTrace ();
out.println (" The servlet has received a GET. This is the reply. < /html > ");
out.close ();
Error: This code send message in The First container, and should send in the second OC4J !!!!
Please answer :
As configure (what code it is necessary to write) servlet (any J2EE the application in OC4J) to use a path to OC4J JMS (remote OC4J JMS) through the Resource Adapter (using OracleASjms.rar). ???

Specifying additional JMS message attributes in Sender Adapter

Hi,
Iam using sender JMS adapter and I have to use the option " Specify Additional JMS Message Properties" for adding addtionalJMS properties in XI message header.
Once I cselect the option in the below table Iam not able to add new lines to add addtional JMS Message Properties..But In receiver adapter I was able to add the new lines.
Is this option graded in SAP PI 7.3 or relatd to any authorization issue..?
Is anyone faced this issue before.. Please help me out
Thank you

Hi everybody
I'm starting a project where I have to take adptadores JMS and I'm in the same situation kirian, I am need to configure a JMS adapter with version of SAP PI 7.3 and I wonder if anyone can help me or give me manuals leagues where information comes related.
Someone can help me with this information
Regards

How to stop and start MDBs to listen for JMS messages

Hello! This might be more of an architecture question rather than a technical questing, but I post it here, in the lack of a better place...
For several years I have been using Webster and Webster MQ to send messages back and forth to clients. The architecture for the middleware platform has been designed around the functionality of ListenerPorts. Listenerports is a Webster functionality that let you "stop" and start to listen to JMS messages for a given MDB either by admin console, or by JMX.
The arhitecture we used was something like this :
1.Client sends a persistent message to a queue. (order)
2. An MDB pics up the order message, calls a SessionBean that "fronts" the IIOP back end system.
This is quite "out of the box" architecture, but we used the Listenerports to solve a stability problem for our back end system.
The backEnd system was quite unstable, so the EJB threw an exception (typically because of timeout or connection refused) back to the MDB.
The Listenerport was "defined" to handle 3 errors before stopping, so the MDB resent the message twice before the listenerport automatically stopped. The nice thing about this feature was that the client could continue to send orders, and was not bothered when the back end system was down.
When the backEnd system was up and running, we could start the listenerport and it was all back to normal state. We even had a start script that checked the state of the listenerport every 30 minute, and started it automatically if it was stopped, making the admin task of starting the MDB unnecessary..
Now.. Why am I telling this story..
I would like to know how this could be done using "clean" J2EE technologies..That is..Not using any technology that is not portable..
I`m playing with glassfish at home, and it struck me that there is nothing in the J2EE spec that defines the functionality described above ? Am i missing something ?
I Do not want to stop My application because the back end system is down? That is the only way (i know of) that i can "stop" to listen for messages..
I can put all the messages on an error queue when the backbend system is down, but that would lead to more code just to handle the error messages. Maybe the easiest way to solve this is to "move" (programmatically) all messages from the error queue over to the "standard" queue every XX minute, but somehow that sounds "wrong"
Can anyone give me some advice to how this problem situation should be solved ? I`m interested in the solution both from an architectural perspective and from a more technical perspective..
Best regards
Hans-Jacob Melby

Breakpoints, whether normal or conditional, are just meant for debugging of your code. I had the sense from your question that the pausing you want to do is a part of normal operation of your code. I would NOT recommend using a breakpoint for that situation. It would bring up the block diagram showing the breakpoint when it occurs. A user besides the programmer would not know what to do in that case.
Yes, both the inner and outer loops would have shift registers.
Putting a case structure with a small while loop inside the "Pausing Case" is doable. It just depends on what you are doing or waiting for while the program operation is "paused".

I am unable to send JMS message to application which resides in third party

I am able to produce the Message into JMS demoQueue which is available in SOA 10.1.3.3. And also I tried remote server which is available in my office it having the application SchoolMAX with JMS Configuration. So I need to produce the JMS message into SchoolMAX application. But I am unable to pass to the data’s to that SchoolMAX JMS.
for this I have configured the respective queues, queue factory etc in Enterprise Manager , but i am not able to access our application which is in remote server through third party in JDeveloper for BPEL Process.
please i am very new to this JDeveloper & BPEL Console , please help me out in resolving the issue ASAP. please we will be waiting for some reply.

Hi Kathy,
Happy Holidays! Do you have an iPad with cellular service and a text-messaging plan?
Send messages with your iPhone, iPad, or iPod touch - Apple Support
http://support.apple.com/en-us/HT201287
What's the difference between SMS/MMS and iMessage?
SMS/MMS lets you send text messages and photos to other cellular phones or devices. iMessage lets you send text messages and photos to another iOS device over Wi-Fi, without worrying about text-messaging charges (cellular data charges may apply).
What do I need to use SMS/MMS and iMessage?
Here's what you need to use SMS/MMS and iMessage:
SMS/MMS: A text-messaging plan. Contact your carrier for more information.
iMessage: An iPhone, iPad, or iPod touch with iOS 5 or later.
How do I know if my message used SMS/MMS or iMessage?
You can tell which type of message you're sending by the color of the Send button and text bubble.
SMS/MMS: Send button and text bubbles are green.
iMessage: Send button and text bubbles are blue.
How can I link my iPhone number with Messages on my iPad, iPod touch, or Messages for Mac?
When you sign in to Messages with your Apple ID on your iPhone, you link your phone number to your Apple ID. If you then sign in to Messages with the same Apple ID on your iPad, iPod touch, or Mac, Messages will link that device to your phone number as well.
I hope this information helps ....
- Judy

JMS Message Headers

Similar Messages

Maybe you are looking for