Throttling the JMS Transport in OSB

Hi All,
I have a requirement if i have 10 messages in the JMS Queue .
If i create a proxy service it should read one message at a time . How will i configure this in JMSTransport .
I know how to do this JMSAdapter .
Thanks
Phani

Apart from assigning a single thread work manager, also make sure that you change the Maximum Messages per Session setting to 1 in Connection Factory Client tab.

Similar Messages

Problem Connecting to SFTP server using the SFTP Transport in OSB 11gr1

Hi,
I have a proxy service that polls for files from an SFTP server. But there seems to be some problem with the handshake between the both.
Below is the error that is logged:
<Error> <WliSbTransports> <tshvm03x> <OSB_AdminServer1a> <pool-14-thread-1> <weblogic> <> <11d1def534ea1be0:-2e6486ae:130dafcd1ef:-8000-0000000000615cf8> <1309358912109> <BEA-381602> <Error encountered while polling the resource for the service endpoint ProxyService$XXWMMPROJECTS$DF155_INBOUND_ASN$Proxy_Services$PS_PO_DF002_SFTP_01: com.bea.wli.sb.transports.TransportException
com.bea.wli.sb.transports.TransportException
at com.bea.wli.sb.transports.sftp.connector.SFTPWorkPartitioningAgent.execute(SFTPWorkPartitioningAgent.java:125)
at com.bea.wli.sb.transports.poller.TransportTimerListener.run(TransportTimerListener.java:74)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:98)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:206)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
Caused By: java.util.NoSuchElementException
at java.util.StringTokenizer.nextToken(StringTokenizer.java:332)
at java.util.StringTokenizer.nextElement(StringTokenizer.java:390)
at com.bea.wli.sb.transports.sftp.client.KnownHostVerifier.validateKnownHosts(KnownHostVerifier.java:65)
at com.bea.wli.sb.transports.sftp.client.SFTPClient.authenticate(SFTPClient.java:104)
at com.bea.wli.sb.transports.sftp.connector.SFTPResource.<init>(SFTPResource.java:77)
at com.bea.wli.sb.transports.sftp.resource.SFTPUtils.createSFTPResource(SFTPUtils.java:170)
at com.bea.wli.sb.transports.sftp.connector.SFTPWorkPartitioningAgent.getSftpResource(SFTPWorkPartitioningAgent.java:148)
at com.bea.wli.sb.transports.sftp.connector.SFTPWorkPartitioningAgent.execute(SFTPWorkPartitioningAgent.java:58)
at com.bea.wli.sb.transports.poller.TransportTimerListener.run(TransportTimerListener.java:74)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:98)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:206)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
>
I could see the same error mentioned in a couple of posts; but couldn't find any resolution to it. Any Pointers on this would really help.
Settings Done:
I have configured a service key provider.
Placed the Known_hosts file at Domain_Home/config/osb/transports/sftp with all the necessary details.
Thanks,
Manoj

Hi Manoj,
It may be an issue with Known_hosts file. Make sure that it is properly formed and it has no space/newline character at the starting of the file.
Regards,
Anuj

Webservice + secured jms (Web Service over the JMS trans).

Apologize since this post is in the webservice forum as well but since it is related to jms as well i put it here as well.
I have a web service that is using JMS (@WLJmsTransport Web Service over the JMS transport)
and everything seems to be ok BUt i do not know how to use this if the JMS is secured .
By Adding security on JMS queue what other things i need to do in order for the webservice to access the queue ?
(where i specify the credentials ?)
@WebService(serviceName = "ASyncService", targetNamespace = "http://axyz.org/notification/v1", endpointInterface = "
axyz.notification.ASyncPort")
@WLJmsTransport(contextPath = "notify", serviceUri = "async_event", portName = "ASyncServicePort", queue = "events", connectionFactory = "cnfct_receiver")
Thank you !

The annotation you gave is for accessing the webservice but in this case it seems the webservice has to access a secured jms
However having your response lead me to @RunAs which solved my problem.
Very hard to find this information.
Thank you very much for your answer !
Nice blog as well !
Edited by: user630775 on Jan 28, 2010 2:02 AM

Read message synchronously from JMS queue using OSB

Hi,
Is it possible to read message from the JMS queue using OSB based on the request invocation. I know messages can be read from the queue but it will be polling based.
The requirement is to have an OSB proxy service (HTTP service ) an an interface to the client application. Client application invokes the proxy service and the proxy service need to read message from the JMS queue and provide the message as response to the client.
Let me know if there are any pointers.
Thanks
Sandeep

Hi,
I spent some time trying to do this and apart from creating custom database tables etc. I was not able to achieve this.
We wanted to use in memory JMS queues in our situation.
In the end we developed a Java Web Service which preformed the on-demand read from the queue (using a particular message selector)
This is working for us without a problem
Robert

MQ Transport within OSB - Put to remote Q?

Hi Guys,
We're working on a project down under that is targeted at an environment that makes heavy use of IBM's MQ transport.
In developing with the MQ Transport available from Oracle we've found certain limitations in it's use, specifically:
1) unable to put to a remote queue definition on the local queue manager.
2) unable to put a message to a queue existing on a remote queue manager which is defined on the local queue manager.
These examples are connecting to the local queue manager in tcp (client) mode. Putting to local queues on the local queue manager, or clustered queues visible from the local queue manager work fine.
Surely there is a way the MQ Transport within OSB can facilitate the above 2 scenarios?
FWIW, we're using Weblogic version 10.3.0.0 and OSB version 10gR3
Edited by: user12006489 on Dec 20, 2009 4:09 PM
Edited by: user12006489 on Dec 20, 2009 4:10 PM

I should further elaborate on my initial question:
On the local queue manager is a remote queue manager definition to another queue manager. Using the MQ Transport, how can I send a message to a queue that exists on that remote queue manager?
In the MQ URI string ends up looking something like mq://REMOTE_QMGER/REMOTE_QUEUE, but this format violates the MQ Transport URI field formatting.
Has anyone had any experience with this?
Edited by: user12006489 on Dec 20, 2009 4:57 PM

Specifying the filename for outbound FTP transport in OSB

I want an OSB based service that will send via FTP a file with a specific name to a remote ftp location.
It appears OSB can't do this because the FTP transport on a business service only allows you to specify the prefix and suffix and then generates a big long file name for the midlle parts.
Does someone know how to override this and specify the name that you want teh remote file name to be called?

mdsrobbins wrote:
Your response was helpful but being new to OSB I'm still not quite there because I want to pass a "variable" to the file name. Now given I want to ftp a CSV file I've specified a proxy messaging service in an MFL format behind a jms queue. The business service underlying this is the ftp service again using the MFL format. This all works but in the message flow I for the proxy I can't seem to get access to a user defined property which contains the filename which I could then pull out and stuff into the "filename" header as suggested above.
Doe anyone have any ideas how I can get access to a filename property from a JMS message?From what i understand
JMSQ--- JMS PRoxy (MFL)----Pipeline ----->BS (MFL/FTP)---FTP server
So you would like to set the filename that is contained the JMS message custom headers?. While creating your JMS Proxy you have to follow these steps
1) While creating JMS Proxy in Transport Configuration page select Get All Headers =Yes
2) If file name is set as user defined property in JMS message then use $Header in you pipeline/message flow. This variable will hold your user defined properties. If the user defined property is part of JMS message then use $body.
thanks
Manoj

Java client for OSB proxy with JMS Transport

Hi,
I am trying to call OSB proxy with JMS Transport. I am generating the client through ant task clientgen and following this article
http://www.oracle.com/technetwork/articles/murphy-soa-jms-092653.html
The osb proxy is req-response and is simply routing to BS which return a string value.
When I run my client, it get stuck and does not return at all. Has any one trying java client in such scenario?
What I may be missing?
Below is snipped of client code:
String url = "http://localhost:7021/sbresource?PROXY/MySample/MyJMSProxyService";
CreditLoanApprovalServiceSoapBindingQSService service = new CreditLoanApprovalServiceSoapBindingQSService_Impl(url);
MyPortType port = service.getCreditLoanApprovalServiceSoapBindingQSPort();
LoanStruct in = new LoanStruct(); //populated the data structure
String loanResult = port.processLoanApp(in); // Stuck here without any error
System.out.println("LoanResult--> " + loanResult);
Thx
/Ashwani

http://localhost:7021/sbresource?PROXY/MySample/MyJMSProxyService is the WSDL URL of the proxy.
Transport is is picked by the client from wsdl.
As far as the documentation of client generation is there, there is no change.
But meanwhile I have started working on sending the message directly to queue. JMSProxy is getting called. May be I will first run the proxy this way and then try troubleshooting the java client.
Regards
Ashwani

Is Message debatching in OSB using JMS transport possible

hi
I have message on JMS queue with multiple message(s) in it.
Now my requirement is to read this JMS message as multiple internal message(s) from queue using OSB JMS transport.
Is this possible from OSB JMS transport?
Thanks in advance.
-Ramakrishna Gilla

No.. JMS transport wont automatically do it for you .. You will have to write a jms proxy service and have your logic to do the debatching.. alternatively you can use jms proxy as a pass thru service writing to the file system and then have the JCA file adapter to do the debatching..

OSB JMS Transport configuration

I have a need to pass a reply-to destination from one external process (the producer) to a second external process (the consumer), with the design supporting flexibility for changing destinations within the OSB pipeline at a future time. To enable this functionality, the following jms transport was designed on the OSB 10gR3:
external producer--->|---q1--->jmsTransProxy---->q2---|--->external consumer
The jmsTransProxy is configured with request/response text message types, jms protocol, Get All Headers yes, Is Response Required enabled, and Response Correlation Pattern CorrelationID.
In the Request pipeline of jmsTransProxy, a single stage is configured to Pass All Headers through Pipeline.
In the Response pipeline of jmsTransProxy, a single stage is configured to Pass All Headers through Pipeline.
When the external producer sets the JMSReplyTo header, I expected that this header would be passed from q1 to q2 so that the external consumer would receive it. The message payload is correctly received by the external consumer along with the JMSCorrelationID, but not the JMSReplyTo header information. By examining the logs, I can see the header information is received correctly in the request pipeline, but is not available from q2.
What is the correct solution to have the JMSReplyTo information pass through to the external consumer?

Thank-you for your tips.
I have revised the pipeline as you indicated and more of the headers pass through, but not the JMSReplyTo header. Because the user headers are passed through, I can use get/setObjectProperty on the message to realize the functionality required (though this is a workaround).
current configuration:
external producer--->q1--->jmsProxy--->jmsBusiness--->q2---> external consumer
jmsProxy parameters:
service type: messaging service
request message type: text
response message type: none
protocol: jms
endpoint uri: q1
get all headers: yes
destination type: queue
is reposnse required: disabled
etc.
jmsProxy request pipeline:
publish to [ jmsBusiness ]
request actions: set transport headers for [ outbound request ] (pass all headers)
jmsBusiness parameters:
service type: messaging service
request message type: text
response message type: none
protocol: jms
endpoint uri: q2
destination type: queue
is reposnse required: disabled
etc.

OSB : Alert Destination not alerting on the JMS destination Topic

Hi,
I am using OSB alert destination to alert on an SLA alert of a proxy service.
The alert destnation configuration has a JMS destination of Topic type. Syntax which i followed is jms://localhost:8011/weblogic.JmsConnectionFactory/weblogic.ReportingTopic
I am able to see the alerts on the dashboard but then i cannot get the alert on topic.
I could see the below exception in log file:
Alert Rule Name: test.
com.bea.wli.sb.transports.TransportException: [JMSClientExceptions:055091]Destination JmsModule!ReportingTopic must be a queue
     at com.bea.wli.sb.transports.jms.JmsOutboundMessageContext.send(JmsOutboundMessageContext.java:570)
     at com.bea.wli.sb.transports.jms.JmsTransportProvider.sendMessageAsync(JmsTransportProvider.java:681)
     at sun.reflect.GeneratedMethodAccessor1206.invoke(Unknown Source)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:597)
     at com.bea.wli.sb.transports.Util$1.invoke(Util.java:83)
     at $Proxy123.sendMessageAsync(Unknown Source)
     at com.bea.wli.sb.transports.TransportManagerImpl.sendMessageWithoutService(TransportManagerImpl.java:490)
     at com.bea.wli.sb.transports.TransportManagerImpl.sendMessageAsync(TransportManagerImpl.java:417)
     at com.bea.wli.sb.init.FrameworkStarter$TransportServiceImpl.sendMessageAsync(FrameworkStarter.java:391)
     at com.bea.alsb.alert.action.jms.JmsActionProvider.executeAction(JmsActionProvider.java:346)
     at com.bea.alsb.alert.AlertDestinationHandlerImpl.sendAlertToDestination(AlertDestinationHandlerImpl.java:105)
     at com.bea.alsb.alert.AlertDestinationHandlerImpl.sendAlertToDestination(AlertDestinationHandlerImpl.java:67)
     at com.bea.alsb.alert.sla.SlaAlertManager.generateAlert(SlaAlertManager.java:149)
     at com.bea.alsb.alert.sla.SlaAlertManager.access$100(SlaAlertManager.java:33)
     at com.bea.alsb.alert.sla.SlaAlertManager$RuleListenerForAlertGeneration.onRuleTrue(SlaAlertManager.java:227)
     at com.bea.alsb.rule.RuleEngine$ListenerInvocation.invokeListener(RuleEngine.java:76)
     at com.bea.alsb.rule.RuleEngine$ListenerInvocation.access$000(RuleEngine.java:61)
     at com.bea.alsb.rule.RuleEngine.addFact(RuleEngine.java:115)
     at com.bea.alsb.alert.sla.SlaAlertManager.intervalCompleted(SlaAlertManager.java:202)
     at com.bea.alsb.alert.sla.TaskCollector$RuleEvaluationTask.run(TaskCollector.java:177)
     at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:442)
     at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
     at java.util.concurrent.FutureTask.run(FutureTask.java:139)
     at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
     at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:909)
     at java.lang.Thread.run(Thread.java:619)
In the alert destination i selected the destination type as topic. Is there anything i am missing. I checked the documentation it says that the jms destination in alert destination can be Queue/Topic. Please suggest. Thanks in advance

A topic wont persist the message, unlike a queue, if there are no subscribers attached to it currently or if there are no durable subscriptions. Create a proxy service to consume the alert from the topic and see whether you are getting it within the proxy's pipeline.

OSB: JMS Transport URL for cluster

Hi,
I am trying to configure OSB JMS Transport business service. I have 3 JMS servers in my cluster and I am trying to understand how to configure my business service URI. Can I use all three uri's in my business service? If we configure multiple URI's how will they be used? The load balanced algorithm(round robin) we specify is for these uris?
Thank you
Matt

maybe this one helps a bit :
https://blogs.oracle.com/MarkSmith/entry/osb_and_jms_business_service_c

Using socket and JMS protocol in the same logic for OSB

Hi frnds,
In my organization...the only communication protocol used is "socket" protocol. However, I want to use JMS protocol to process incoming messages. Can somebody help me figuring out how to go about it.
Using some nice OSB blogs, I am able to create the JMS connection factory and JMS queues in weblogic. And that works fine when I select the communication protocol as JMS while creating the BS and PS.
What should be my message flow when the communication protocol used is "socket" for both BS and PS.
salil

Hi,
Make the BS as JMS and the PS as socket, in the PS's flow do a route for the BS... Then if an external call is made to the PS via socket, it will send a messages to a JMS queue...
Hope this helps...
Cheers,
Vlad

How to do service callout with the incoming JMS message in OSB 11g

Hello All,
I have a specific requirement for which I am creating a kind of POC where I need some help in OSB, however am new to OSB.
My Environment:
1> I have a request queue (deployed on a WLS domain) - WFReq_WS
2> I have a response queue (deployed on a WLS domain) - WFRes_WS
3> I have created a ProxyService (request/response type) in OSB 11g which is simply mapping the incoming message in WFReq_WS to WFRes_WS
4> I have a WebService (it is currently a simple hello WebService for testing) which takes a string and returns the same string with an added 'Hi' in front of it (e.g. If you send Jack, it will return 'Hi Jack')
My Requirement:
1> I have to do some mechanism in OSB, by which while mapping the message from WFReq_WS to WFRes_WS (through the proxy service I have), it will pick the JMS message (which will be a string/text) and will make a service callout to the Webservice I mentioned using the message as the input parameter of the WebService.
2>Now when the response of the WebService will come, OSB should send this response as the message in the response queue (WFRes_WS) I mentioned above.
To simplify the requirement using an example:
A> I will send a text/String message (say Jack) to the request queue (WFReq_WS)
B> OSB should pick the message (Jack) and make a service callout to the webservice
C> webservice will return 'Hi Jack'
D> OSB should send this to the response queue (WFRes_WS)
I know the above might look very basic question to the PROs, but please elaborate (step by step) what need to be done, since I do not know OSB.
Thanks a lot for your help !

Your example points A and D are easily done by having a "Proxy Service" which has the following details:
Service Type = Messaging Service
Request and Response type = Text
Protocol = jms
Endpoint URI = your request queue (format like 'jms://localhost:7013/weblogic.jms.XAConnectionFactory/QueueJNDIName')
Checkmark "response" so that the proxy service automatically delivers the response to another queue - your response queue
Response URI = jms://localhost:7013/weblogic.jms.XAConnectionFactory/QueueResponse
Now since your "Hello" webservice is (probably) a SOAP xml service you need to "convert" your text based JMS message to xml before sending it on to the "Hello" service.
Your JMS proxy can do that by just doing a "Assign <whom>{$body/text()}</whom>" to a variable (lets call it 'reqHello')
Now your JMS proxy should actually call the Hello service and since your JMS proxy is text and the Hello service is SOAP you cannot just "pass" on to the Hello service in a "Route to". Instead you can do a Service Callout where you can specify your "reqHello" variable as payload and a "respHello" as response variable.
Now you have the "<whom>Hi jack</whom>" in the response variable and since the JMS response needs to be text format you can "extract" the text value into the body variable of the JMS proxy (use "replace /* in body with $respHello/text()" - replace node contents)
The actual Hello service is a simple "SOAP" based Proxy Service. Add a pipeline and add a stage in the reponse pipeline. Do a ...
Assign fn:concat("Hi ",$body/whom/text()) to $whomVar
Replace whom in body with $whomVar (replace node contents)

How to specify the JMS Client ID in Proxy Service of OSB 11.1.1.5 version ?

Hi All,
I am looking for an option to set the JMS clientID for a JMS Proxy services in OSB. Can this feature available in OSB 11.1.1.5 version?
Thank you,
Ram.

These links will helpful for you.
http://jdevadf.oracle.com/adf-richclient-demo/docs/tagdoc/af_train.html
http://download.oracle.com/docs/cd/E15523_01/apirefs.1111/e12419/tagdoc/af_train.html

FTP Transport in OSB 10gR3

Hi,
I've just created a Business Service in OSB to send a message using the FTP transport. Although OSB connects with the FTP server but gets a 500 code response from it and the PUT command fails. This is the console output:
+<29-ene-2009 16H35' CET> <Error> <WliSbTransports> <BEA-381105> <Error occured for the service endpoint: com.bea.wli.sb.transports.TransportException: Received error response (500) from FTP server [http://ftp.telefonica.net] IP [http://213.4.130.43] port [21|http://forums.oracle.com/forums/] status connected upon executing command [port 10,10,10,10,6,6 |http://forums.oracle.com/forums/]+
+com.bea.wli.sb.transports.TransportException: Received error response (500) from FTP server [http://ftp.telefonica.net] IP [http://213.4.130.43] port [21|http://forums.oracle.com/forums/] status connected upon executing command [port 10,10,10,10,6,6 |http://forums.oracle.com/forums/]+
at com.bea.wli.sb.transports.ftp.connector.FTPTransportProvider.sendMessage(FTPTransportProvider.java:405)
at com.bea.wli.sb.transports.ftp.connector.FTPTransportProvider.sendMessageAsync(FTPTransportProvider.java:289)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
Truncated. see log file for complete stacktrace
I belive that this response from the FTP server means that a reconnection to a higher port is required. Anyone knows if this functionality is managed by the FTP transport implementation used by OSB10gR3?
Thanks

mdsrobbins wrote:
Your response was helpful but being new to OSB I'm still not quite there because I want to pass a "variable" to the file name. Now given I want to ftp a CSV file I've specified a proxy messaging service in an MFL format behind a jms queue. The business service underlying this is the ftp service again using the MFL format. This all works but in the message flow I for the proxy I can't seem to get access to a user defined property which contains the filename which I could then pull out and stuff into the "filename" header as suggested above.
Doe anyone have any ideas how I can get access to a filename property from a JMS message?From what i understand
JMSQ--- JMS PRoxy (MFL)----Pipeline ----->BS (MFL/FTP)---FTP server
So you would like to set the filename that is contained the JMS message custom headers?. While creating your JMS Proxy you have to follow these steps
1) While creating JMS Proxy in Transport Configuration page select Get All Headers =Yes
2) If file name is set as user defined property in JMS message then use $Header in you pipeline/message flow. This variable will hold your user defined properties. If the user defined property is part of JMS message then use $body.
thanks
Manoj

Throttling the JMS Transport in OSB

Similar Messages

Maybe you are looking for