Make jms queue forward messages to a proxy service

Greetings!
Here's my task. I have a pretty complex proxy service that routes the message to different web services. This proxy has a conditional branch. Now, what I needed to do was implement a JMS queue and fuse it with my proxy. I have successfully created a proxy and a business service that send messages to the JMS queue. However, the queue doesn't forward the messages to my routing proxy. My guess is that when the queue tries to send the message to my proxy, it encounters a conditional branch and doesn't know which branch to use. I have tried to put a log action in the default branch to determine if the message ends up there, but it doesn't.
If anyone knows a way to forward messages from a JMS queue to a proxy with a conditional branch, please advise a solution.
Thanks in advance,
Andrew

Hello Andrew,
To communicate with JMS (either to poll JMS for dequing messages or to connect to JMS to enqueue a message), you have to use JMS transport in Oracle Service Bus.
I am still not sure if this would have worked had I left the conditional branch in my Message Flow.It will work. You may try configuring it.
Could you please be more specific as to where I can enable message tracking for my proxy service?You may enable message tracing in "Operational Settings" of a particular proxy/business service. Please refer sections "Configuring Operational Settings for Proxy Services" and "Configuring Operational Settings for Business Services" on below link to know more -
http://download.oracle.com/docs/cd/E13159_01/osb/docs10gr3/consolehelp/monitoring.html#wp1028056
Should it be enabled for a specific proxy service or for all of them?You may enable it for all or for a particular service. It depends on requirement.
Regards,
Anuj

Similar Messages

Publishing message to JMS Queue on Weblogic from OSB proxy service

Hi,
1. I have created a JMS module: testModule and a JMS queue: testQueue in the weblogic admin console.
2. Created a business service with the above queue as endpoint.
3. Created a proxy service which publishes the message to the queue using the business service. I have used Publish activity to publish the message to the business service.
When i run the proxy service with the request message, then, no error is coming but, in the admin console when i click on JMS module->testModule->testQueue->Monitoring tab, i see nothing. There are no entries in the table so, how can i check if the message is properly published to the queue or not.
The queue is not listened by any service for consuming the messages.
Kindly help me in figuring out this issue.
Thanks in advance.

If the destination was a topic, the behavior would be expected. Messages only stays on a topic and are delivered to consumers if there are consumers or durable subscribers.
Did you check the server logs and see if there are any exceptions or warnings?
You can also turn on jms debugging by adding the following to your server startup script.
-Dweblogic.debug.DebugJMSFrontEnd=true
-Dweblogic.debug.DebugJMSBackEnd=true
The debugging messages wiill show up in the server log.

Consume JMS Unit-Of-Work message through OSB proxy service

Hi,
Anyone know how to consume a JMS Unit-Of-Work (UOW) message using an OSB Proxy Service of JMS type?
I can submit a unit-of-work JMS message (which consists of multiple constituent messages) using an OSB proxy & business service combination and setting the UOW transport headers appropriately. I can also separately produce and consume Java objects via a JMS queue where the consumption is done via OSB proxy (of java request message type), but these aren't UOW messages.
Apparently as soon as it is a UOW message then the message consumed is an ObjectMessage ArrayList and one has to use the "Java" request message type for the JMS consumer proxy, but I'm unsure of how to create the concurrent client jar to use it in the same proxy service's JMS transport configuration in order to output the ObjectMessage ArrayList (UOW message).
Ideally I'd like to consume a single UOW XML message via an OSB JMS proxy service.
Any pointers would be appreciated.
R

Finally got this working!!
For posterity: Needed to insert Java Object JMS messages on the OSB JMS producer (Business Service) side with correct UOW jms transport header set in route node. Then consume the Unit-Of-Work message on the other side via jms proxy service with "java" request message type, with appropriate jar containing the Object class as the "Client jar" in the JMS Transport configuration. In the same JMS consumer proxy I had to do a java callout, passing the contents of $body, using java.util.ArrayList and javax.jms.ObjectMessage, as input into a method (.. decodeJavaMessage(ArrayList<ObjectMessage> ...)). In this java callout class you can get to each individual ObjectMessage via typecasting the get() method on the Arraylist to (ObjectMessage) and then just typecast the getObject() on this Objectmessage into your original Java Class (same as what you inserted onto queue originally).
Hope this saves someone some time in future!

JMS Queue loosing messages on Server restart

Hi ,
We are having a problem with a queue that is loosing pending messages if the server is restarted.
We have following setup of Oracle Weblogic version 9.2 mp1.
The JMS Server is backed up by a DB based persistent store.we are having a message driven bean that process the message in the queue asynchronously.
the message that is delivered to the queue has Delivery Mode 'persistent'
and the mdb using transactionType=MessageDriven.MessageDrivenTransactionType.CONTAINER.
What is strange that we are loosing pending message in the queue , when server is restarted .even checking in the xxx'_WLSSTORE table in db i can see the message
was persisted.
If anyone of you have seen this situation kindly let me know.
thanks in advance.
Rgds
roy

You can follow this article to troubleshoot pending message issues.
http://weblogic-wonders.com/weblogic/2011/01/10/working-with-jms-and-the-standard-issues-in-jms/
-Faisal

Cleanup JMS queue/topic messages

          how do I clean up all messages left on a queue/topic ? thx.


There is no purge command.
          In 8.1, delete and recreate the destination via the console,
          JMX, or extensions.JMSHelper, the JMS
          server doesn't even need to be booted. A timestamp
          in the destination configuration is automatically set to
          let JMS detect that the destination is a new version.
          In 7.0, delete the queue, shutdown the JMS server,
          reboot the JMS server, and then recreate the destination.
          In any version, shutting down the JMS server will delete
          non-persistent messages.
          You can delete topic subscriptions via the console.
          You can write a simple JMS client to drain the destination
          by consuming messages. (Multi-thread multiple consumers to
          speed this up considerably.)
          Queen Tsao wrote:
          > how do I clean up all messages left on a queue/topic ? thx.

JMS Unit-Of-Work in OSB Proxy Service

I'm trying to create a JMS Unit-of-Work OSB Service by populating the JMS transport user properties:
JMS_BEA_UnitOfWork
JMS_BEA_UnitOfWorkSequenceNumber
JMS_BEA_IsUnitOfWorkEnd
However, after publishing all of the messages to the Queue, JMS is not recognizing the end of the UOW.
When I publish the last message in the UOW, I set 'JMS_BEA_IsUnitOfWorkEnd' in the transport header properties to true(). However, when I look at the last message in the queue, it shows correctly that the JMS Properties Key is 'JMS_BEA_IsUnitOfWorkEnd', the Value is 'true', but the type is 'java.lang.String.' I believe the problem could be that the type is incorrect - it should be a java.lang.Boolean. However, I cannot figure out how to make it a boolean. Can you help? Do I need a boolean here? How do I assign a boolen to the transport header? I've tried 'true', 'true()', and xs:boolean('true') and they all wind up be java.lang.String!
Thanks.

string value for JMS_BEA_IsUnitOfWorkEnd should work just fine.
Make sure all messages in the same group has the same JMS_BEA_UnitOfWork value.
you can use OSB to produce unit of work messages.
for the consumer, you need to create a jms proxy using java type, then use a java callout to convert the message array list into xml that you can then process in a for loop.
Edited by: jerry.sy on May 13, 2011 1:38 PM
Edited by: jerry.sy on May 13, 2011 1:40 PM

Retry count JMS message on Proxy Service

I have a proxy service listening to a JMS Queue.
It is a task service. I need to try some functionality. If an error occurs (probably because of an offline external service/ business service) I need to rollback and retry). I want to do this for example 5 times. If this fails I want to send it to an error queue
I see the JMSXDeliveryCount going up. I though I could set this with the retry count field. But I see now it is for the response queue.
The only way I can solve it is to put an error handler and look at the JMSXDeliveryCount . If it is above the number of retries I stop reraising.
Is there another way?

If you choose the service type as WSDL based or Any SOAP service, then OSB engine will deconstruct the incoming SOAP Envelope and populate the parts of envelope (Header, Body etc) to correct context variables automatically. This happens before the message flow of proxy service is initiated, so you can not do anything about it. In the proxy service you will receive the deconstructed SOAP message only.
If you do however want to log the exact message which was received by OSB, then change the service type to (or create another proxy service in front of the existing proxy) Messaging type with binary or text content. Or you can also choose AnyXML service type, in which case the incoming SOAP Envelope will be available inside $body variable in message flow.

Issue in Synchronous OSB using Jms Queues in OSB11g

Hi,
I am working on building a synchronous OSB using the following steps.
1)     Creating the Synchronous OSB Proxy Service which routes the message to the business service which in turn places a message in the Queue(inqueue) by populating the JMSCorrelationId and waits for the response message to consume from another queue.
2)     A Composite(SOA) will consume the message from this Queue
3)     It will do necessary transformation and Places it in another Queue (Say Response Queue).
4)     OSB Business service waiting in Step 1 will receive the response from this response Queue.
I used a sample Wsdl which has both request and response message types.
I observed that the correlation ID is maintained properly from inqueue to response queue. But the message is not getting picked up by OSB from the response Queue
Twist: It is working absolutely fine in OSB 10g but it is not working in OSB 11g.
I tried using Messaging service as well as using the sample WSDL i.e keepiing the soap message in the queue. Both the cases are working absolutely fine OSB 10g but not in OSB 11g.
Can anyone faced a similar issue or any pointers will be great help in this regard.
Regards,
Ashok

To debug this further can you check if the response Q has any active consumers. ? When you use response by correlation ID business service, OSB actually creates MDB's with message selectors under the hood.
This is a sample of the ejb-jar.xml of the MDB created for a business service with response by Correlation ID pattern.
<?xml version='1.0' encoding='UTF-8'?>
<jav:ejb-jar xmlns:jav="http://java.sun.com/xml/ns/javaee">
<jav:display-name>BEA ALSB JMS Outbound Sync-Async Endpoint</jav:display-name>
<jav:enterprise-beans>
<jav:message-driven>
<jav:ejb-name>ResponseEJB-6577847719916437493-3893eeb7.1287d30ba4f.-7fe1</jav:ejb-name>
<jav:ejb-class>com.bea.wli.sb.transports.jms.JmsAsyncResponseMDB</jav:ejb-class>
<jav:transaction-type>Container</jav:transaction-type>
<jav:message-destination-type>javax.jms.Queue</jav:message-destination-type>
<jav:activation-config>
*<jav:activation-config-property>*
*<jav:activation-config-property-name>messageSelector</jav:activation-config-property-name>*
*<jav:activation-config-property-value>JMSCorrelationID LIKE 'ID:424541534594cf52%'</jav:activation-config-property-value>*
*</jav:activation-config-property>*
</jav:activation-config>
<jav:env-entry>
<jav:env-entry-name>service-ref</jav:env-entry-name>
<jav:env-entry-type>java.lang.String</jav:env-entry-type>
<jav:env-entry-value>BusinessService$Test$RequestQ</jav:env-entry-value>
</jav:env-entry>
As you can see the message selector is based on JMSCorrelationID LIKE 'ID:424541534594cf52%'. This means the business service will pick only those messages which has its correlation ID starting with ID:424541534594cf52.
You can see the message selector for your MDB from admin console --> deployments.
Check and confirm if the correlation ID created in the request also starts with this value and the same is send back from the server. Also try deleting and recreating the business service or rename the business service which will create a new MDB under the hood and check the above.

Defining/Creating a JMS Queue in XI

Scenario: Third party system would post messages in XI Jms queue, the messages would ultimately be sent to SAP.
Need to create this JMS queue in XI which receives Jms messages from third party.
Steps done:
1) Defined Sender Communication Channel 'CC_JMS'
JNDILookup name:jmsfactory/default/QueueConnectionFactory
JMSQueue:jmsqueues/default/JMS_queue
initialcontextfactory:com.sap.engine.services.jndi.InitialContextFactoryImpl
JNDIServerAddress:<<serverIP>>:50004
2)Defined sender ID for the outbound interface in SXMSIF
3) Added job(I've given the name, is it right?) in SXMb_Adm and Defined message filter for that job. activated.
4)configured message filter for the above sender ID. Queue name XBT1
5)when checked in adapter monitor for JMS_queue.Shows the following error message
CC_JMS : Sender channel. Details: Object not found in lookup of JMS_Queue.
Questions:
1)Is that the right approach i am following
2)How do i assign CC_JMS to JMS_queue
3)How do i know if JMS_queue is up and running
thnx
sunil

Hi Sunil,
Please take a look at these..
http://help.sap.com/saphelp_erp2005/helpdata/en/bc/996b908db7485fabbacb9930714d7e/frameset.htm -- Queue sender and reciever
http://help.sap.com/saphelp_erp2005/helpdata/en/f4/2d6189f0e27a4894ad517961762db7/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/90/57849e5e3e45d784afc4e3bfa8136f/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/c1/739c4186c2a409e10000000a155106/frameset.htm
Hope they help!
cheers,
Prashanth
P.S Please mark helpful answers

Access to original message inside proxy service

I have proxy service (serviceType=WSDL Web Service) which is available to endpoint to customer and I want to save incoming message to file on disk. However I want to persist whole incoming message exectly (at byte level) as it was sent by sender (so together with Envelope).
Inside proxy service I have access to variables like header, body etc. However they are not good for my purpose because they differ from corresponding parts of original message. E.g. xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" namespace in original message in
defined only on Envelope level and not on Header or Body level. But in variables header and body available inside proxy service they (namespaces) are visible. Mayby there are more differences but this one is visible at once.
So is it possible to access (to be able to save it) original message somehow? Any magic variable? Or mayby there is a way to say osb to persist it (incoming request) to file? (it would be enough for me (of course I need filename). I would manage file by myself further).
Any hints appreciated

If you choose the service type as WSDL based or Any SOAP service, then OSB engine will deconstruct the incoming SOAP Envelope and populate the parts of envelope (Header, Body etc) to correct context variables automatically. This happens before the message flow of proxy service is initiated, so you can not do anything about it. In the proxy service you will receive the deconstructed SOAP message only.
If you do however want to log the exact message which was received by OSB, then change the service type to (or create another proxy service in front of the existing proxy) Messaging type with binary or text content. Or you can also choose AnyXML service type, in which case the incoming SOAP Envelope will be available inside $body variable in message flow.

Error while invoking web services from Proxy services in OSB

I have a Proxy Service of message type in Oracel Service Bus 10gR3 and it passes the incoming messages from a JMS Queue to Business Service of Web Services type. This Web Service is hosted in Glass Fish v3 and it's binding style is RPC. The JRE used in both the servers are 1.6.0_20. The JMS message is of Text type. The Web Services at the Glass Fish throws MessageCreationException for any content of the JMS message. However, it works fine if Business Service's test client is invoked from the OSB'S Admin Console. However, the same will not work if Proxy Service's test client is called.
The detailed exception stack is given below :
Thanks for the help.
- Raj
com.sun.xml.ws.protocol.soap.MessageCreationException: Couldn't create SOAP message due to exception: XML reader error: com.ctc.wstx.exc.WstxEOFException: Unexpected EOF in prolog
at [row,col {unknown-source}]: [1,0]
     at com.sun.xml.ws.encoding.SOAPBindingCodec.decode(SOAPBindingCodec.java:359)
     at com.sun.xml.ws.transport.http.HttpAdapter.decodePacket(HttpAdapter.java:318)
     at com.sun.xml.ws.transport.http.HttpAdapter.access$500(HttpAdapter.java:92)
     at com.sun.xml.ws.transport.http.HttpAdapter$HttpToolkit.handle(HttpAdapter.java:501)
     at com.sun.xml.ws.transport.http.HttpAdapter.handle(HttpAdapter.java:285)
     at com.sun.xml.ws.transport.http.servlet.ServletAdapter.handle(ServletAdapter.java:143)
     at org.glassfish.webservices.Ejb3MessageDispatcher.handlePost(Ejb3MessageDispatcher.java:116)
     at org.glassfish.webservices.Ejb3MessageDispatcher.invoke(Ejb3MessageDispatcher.java:87)
     at org.glassfish.webservices.EjbWebServiceServlet.dispatchToEjbEndpoint(EjbWebServiceServlet.java:196)
     at org.glassfish.webservices.EjbWebServiceServlet.service(EjbWebServiceServlet.java:127)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
     at com.sun.grizzly.http.servlet.FilterChainImpl.doFilter(FilterChainImpl.java:195)
     at com.sun.grizzly.http.servlet.FilterChainImpl.invokeFilterChain(FilterChainImpl.java:139)
     at com.sun.grizzly.http.servlet.ServletAdapter.doService(ServletAdapter.java:376)
     at com.sun.grizzly.http.servlet.ServletAdapter.service(ServletAdapter.java:329)
     at com.sun.grizzly.tcp.http11.GrizzlyAdapter.service(GrizzlyAdapter.java:166)
     at com.sun.enterprise.v3.server.HK2Dispatcher.dispath(HK2Dispatcher.java:100)
     at com.sun.enterprise.v3.services.impl.ContainerMapper.service(ContainerMapper.java:245)
     at com.sun.grizzly.http.ProcessorTask.invokeAdapter(ProcessorTask.java:791)
     at com.sun.grizzly.http.ProcessorTask.doProcess(ProcessorTask.java:693)
     at com.sun.grizzly.http.ProcessorTask.process(ProcessorTask.java:954)
     at com.sun.grizzly.http.DefaultProtocolFilter.execute(DefaultProtocolFilter.java:170)
     at com.sun.grizzly.DefaultProtocolChain.executeProtocolFilter(DefaultProtocolChain.java:135)
     at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:102)
     at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:88)
     at com.sun.grizzly.http.HttpProtocolChain.execute(HttpProtocolChain.java:76)
     at com.sun.grizzly.ProtocolChainContextTask.doCall(ProtocolChainContextTask.java:53)
     at com.sun.grizzly.SelectionKeyContextTask.call(SelectionKeyContextTask.java:57)
     at com.sun.grizzly.ContextTask.run(ContextTask.java:69)
     at com.sun.grizzly.util.AbstractThreadPool$Worker.doWork(AbstractThreadPool.java:330)
     at com.sun.grizzly.util.AbstractThreadPool$Worker.run(AbstractThreadPool.java:309)
     at java.lang.Thread.run(Thread.java:619)
Caused by: com.sun.xml.ws.streaming.XMLStreamReaderException: XML reader error: com.ctc.wstx.exc.WstxEOFException: Unexpected EOF in prolog
at [row,col {unknown-source}]: [1,0]
     at com.sun.xml.ws.streaming.XMLStreamReaderUtil.wrapException(XMLStreamReaderUtil.java:267)
     at com.sun.xml.ws.streaming.XMLStreamReaderUtil.next(XMLStreamReaderUtil.java:95)
     at com.sun.xml.ws.streaming.XMLStreamReaderUtil.nextContent(XMLStreamReaderUtil.java:110)
     at com.sun.xml.ws.streaming.XMLStreamReaderUtil.nextElementContent(XMLStreamReaderUtil.java:100)
     at com.sun.xml.ws.encoding.StreamSOAPCodec.decode(StreamSOAPCodec.java:175)
     at com.sun.xml.ws.encoding.StreamSOAPCodec.decode(StreamSOAPCodec.java:303)
     at com.sun.xml.ws.encoding.StreamSOAPCodec.decode(StreamSOAPCodec.java:129)
     at com.sun.xml.ws.encoding.SOAPBindingCodec.decode(SOAPBindingCodec.java:354)

Let me explain what I am trying to achieve. Our application receives data from multiple sources - from mainframe using FTP, JMS Queue and BPM application using Web Services. The data from all these sources are sending to a Web Service running in GlassFish V3. To handle this I have created three Proxy Services and one Business Service on OSB. The Business Service is of type Web Service using the same WSDL from the target Web Service.
The Proxy Services are configured as follows:
Proxy 1 (type - Messaging service) listens to the JMS Queue and receives JMS Text Message -> Business Service(B1) (Web Service).
Proxy 2 (type - Messaging service Polls files from the FTP Server -> Business Service(B1) (Web Service).
Proxy 3 (type - Web service) is invoked by the BPM application and sends a String -> Business Service(B1) (Web Service).
All the Proxies route to the same Business Service - B1 which calls the Web Service in GlassFish. The only Proxy that works fine is Proxy 3 which is created using the same WSDL of the Web Service. In the other two proxies it thows the same exception in GlassFish as I mentioned before.
com.sun.xml.ws.protocol.soap.MessageCreationException: Couldn't create SOAP message due to exception: XML reader error: com.ctc.wstx.exc.WstxEOFException: Unexpected EOF in prolog at [row,col {unknown-source}]: [1,0] at com.sun.xml.ws.encoding.SOAPBindingCodec.decode(SOAPBindingCodec.java:359)
Is this configuration correct to achieve my requirements?
Once again thanks for the help.
- Raj

Single OSB Proxy Service Listening to multiple MQs

Hi All,
I am using OSB 11.1.1.5 and Websphere MQ version 6.
I have a requirement to make a single proxy service to listen to multiple MQs. Is this possible?
If yes, please help. If no, what is the work around?
Regards,
Karthik

One proxy service can listen and consume messages from one MQ only as you can mention only one Endpoing URI with MQ transport in OSB.
Work around is to create as many proxy services as you have MQ queues and create one common proxy service with local transport and let all MQ proxies call the common proxy service over local transport.

OSB Proxy Service routing

Hi,
I have a simple Proxy Service which consumes messages from a remote endpoint queue (source queue). The Proxy Service simply routes consumed messages to a Business Service which puts messages into another remote endpoint queue (destination queue).
When I test passing a message to the Proxy Service using the OSB's Test Console, the Proxy Service routes the message to the Business Service okay where the message is then placed into the remote endpoint queue (destination queue) as expected. But, if I put a message into the remote source queue, I can see that the message gets consumed by the Proxy Service but the message remains as 'pending' and, either the Proxy Service does not route the message to the Business Service or, the Business Service does not put the message into the remote destination queue. What could the problem be?
Thanks in advance for any help on this.

Hello,
Still looking for an answer to this.
Scenario:
When enabled, OSB Proxy Service removes any messages placed in remote endpoint URI queue, but it seems the messages do not flow within the Proxy Service's message flow itself. When the Proxy Service is enabled, the messages in the remote queue get removed but are seen to stay in a 'pending' state. When the Proxy Service is disabled, the messages get put back in the queue. What are the possible reasons as to why messages would not get processed within the Proxy Service's message flow? All the message flow does is, route the messages to a Business service which then sends the messages to another remote endpoint URI queue.
PS: When a message is injected into the Proxy Service via the Test Console, the message flows/routes to Business Service okay without problems so I assume that the problem must lie in the inital remote queue/Proxy Service interface somewhere. Maybe permissions or transaction related issue? But I can't see any hints to anything wrong in configurations or server(s) logs...
Thanks in advance for any help on this.

How to forward message to two different queue using jms proxy service

Hi all,
In my project I need to listen to one jms queue then forward the messages to two different queue.
Now I already made one proxy for listening to the queue then pass it to another queue using business service, It works.
But how to forward the messages to two different queue in same flow process using one proxy and bs??
or any other way?
Really thanks in advance.
Regards,
Kahlil

Hi,
I have a MQ queue and i created a Proxy to listen to the queue , but i dont see any activity in OSB logs ..how do i knw if OSB proxy is polling that MQ ( mq is the transport protocol that i am using ) .
Thanks
Prarthana.

Posting message to JMS queue from Proxy in OSB 10.3

I am posting a message to a JMS queue using a business service. Is there a way of getting a response from the business service to retrieve the newly generated JMSMessageID?

I am posting a message to a JMS queue using a business service. Is there a way of getting a response from the business service to retrieve the newly generated JMSMessageID?Yes JMS BS can be configured to get Response though from Different Q.
Request-JMSBS----->JMS Request Q------your logic outside of BS----->JMS Response Q----->JMSBS-Response. You can use JMSCorrelationID or JMSMessageID for the response correlation.
http://download.oracle.com/docs/cd/E13159_01/osb/docs10gr3/interopjms/transport.html#wp1097863
Cheers
Manoj

Make jms queue forward messages to a proxy service

Similar Messages

Maybe you are looking for