Requirement of JMS

Hi All,
I need the functionality of JMS for my Java application in Swing.
I have onle Java1.2 on my system. What are the other requirements for JMS. Any Server is needed? Please do let me know?
Thanks in advance.
Regards
Ravi

JMS works the same way as JDBC, ie its an interface to an underlying mechanism. In the JDBC case it's an SQL database, in the JMS case it's an implementation of Message Oriented Middleware (MOM).
So in addition to the JMS API itself (which is available in a jar file), you need an actual MOM product. Like SQL databases accessible from JDBC, these come with different characteristics, like some are embeddable, others require an external server, or infrastructure of servers.
Have a look at http://java.sun.com/products/jms/licensees.html for a list of JMS products. In addition, there are Open Source alternatives available, eg. OpenJMS and, in the future, JMS/JBoss.

Similar Messages

JMS Grid, SeeBeyond IQ, Sun JMQ jar files required for JMS Clients

I'm trying to determine the Jar files required to connect to JMS Grid, IQ, and JMQ. I am testing connectivity to each product independently and I think I may have copied over more files than necessary.

I'm trying to determine the Jar files required to connect to JMS Grid, IQ, and JMQ. I am testing connectivity to each product independently and I think I may have copied over more files than necessary.

Is a correlation ID absolut required for JMS communication?

Assume I have a BPEL which creates JMS messages and one or more BPEL processes which retrieve these messages from the JMS queue.
It is however not necessary that exactly one particular BPEL consuming instance should receive one particular JMS message.
All consuming BPEL instances can/are allowed to fetch JMS messages from queue and process them.
Is it necessary in such a scenario that correlation IDs/sets are declared?
Peter

Hi All,
This post has cleared a lot of doubts.It is quite helpful.
I have a few more
1) What is difference between a Oracle AQ and Oracle JMS based queue as we have different adapters for them.
2) Are there any advantages of one over the other or like what are the scenarios when one is preferred over the other.
Thanks in advance.
Lalit

JMS Queue requirements for third party adapter(plsql)

Hi all,
Can any one guide me in the following requirements:
1) JMS Name and Description
2) Parameter Values for Provider Context Factory, Connection Factory, and Default Provider URL.
Please note that the Agile PLM system fills in the fields with server-specific defaults but we must validate they are accurate.
3) User Name and Password to access the queue
1.1) JMS Name : its an queue name
Description : Queue/ Topic with JNDI name
2.1) Context factory : what is it? how to create it and where to create.
2.2)connection factory: connection factory name and JNDI.
2.3) how to get the Default URL from web-logic.
3.2) User name/ password : xxxxxxxxx/abcd00000. this can be set from security realms by creating the user and and assigning that user to the queue and policies.
can any one clarify my doubts in it.
- anil

Hi all,
Can any one guide me in the following requirements:
Hello,
can any one please help me in this issue:
1) JMS Name and Description
2) Parameter Values for Provider Context Factory, Connection Factory, and Default Provider URL.
Please note that the Agile PLM system fills in the fields with server-specific defaults but we must validate they are accurate.
3) User Name and Password to access the queue
1.1) JMS Name : its an queue name
Description : Queue/ Topic with JNDI name
2.1) Context factory :
what is it?
how to create it and where to create.
2.2)connection factory: connection factory name and JNDI.
2.3) how to get the Default URL from web-logic.
3.2) User name/ password : xxxxxxxxx/abcd00000. this can be set from security realms by creating the user and and assigning that user to the queue and policies.
can any one clarify my doubts in it.
Anil

Is there a requirement to restart the JMS/Weblogc Server everytime when the DB goes down?

Question:
When the Database is shutdown gracefully everything was fine.
But when the Database is brought down with shutdown abort the MDB consumer will never consume messages from the topic again. And we need to restart the WebLogic Server in order to get the messages consumed again.
So is there a requirement to restart the JMS/Weblogc Server everytime when the DB goes down? If not, what type of failures will require the JMS/WLS restart?

On a DB failure, a WL JDBC store service will make a brief attempt to reconnect before shutting itself down along with any services that depend on the store.
It isn't necessary to restart the entire WebLogic Server JVM to bring the affected service(s) back if you can use the Automatic Service Migration feature. ASM can automatically restart a failed service on a different WL Server in the same cluster, and/or can try a restart-in-place for the service if the service's original host WL Server JVM is still running. The Automatic Service Migration (pdf) white-paper has a thorough discussion of this area.
In addition to ASM, there's also a "whole server migration" option that can automatically restart or migrate an entire WL server.
Tom

Sender JMS adapter configuration for IBM MQSeries

Dear All,
i am doing a IBM MQSeries 5.2.x Message ->sender JMS adapter -> XI server -> receiver RFC adapter -> R/3.
i have deployed the JMS adapter with the required jar files of IBM MQSeries 5.2.x in XI server.
in Sender JMS adapter configuration for IBM MQSeries 5.2.x, i have put following data:
1. Transport Protocol: Websphere MQ - is it okay?
in JMS provider settings:
2. in channel name - what should be there?
3. Transport Network protocol should be TCP/IP or WebsphereMQ - how to decide this thing.
4. JMS Complaint - whether WebsphereMQ or JMS API.
in JMS Settings:
5. JMS Queue user - is this IBM MQSeries 5.2.x Queue User or someother user?
6. JMS Message Selector - what data to take here.
So if anybody has connected IBM MQSeries 5.2.x to XI via JMS adapter, please answer my above queries.
Regards,
Rajeev Gupta

Hi Swaroop,
you can send me those documents at my gmail-id : [email protected]
Hi All,
one more question - to connect XI server to IBM MQSeries via JMS adapter in ID, do we need to have a MQSeries Client installed on XI server - or - just by configuring JMS adapter, we can send messages from IBM MQSeries to XI server without any MQSeries client on XI server?
Why Channel name is required in JMS configuration data?
Thanks,
Rajeev Gupta

Get Message Notification in BPM 10G from External JMS Provider

Hello,
Can anyone provide me the steps how to get a message from the queue (external JMS provider) in BPM 10G.
I have been looking into this for couple of days now and I'm not able to figure it out. Any input on this would be greatly appreciated.
Thanks
NC

Hi,
Please find the steps below and change the necessary parameter according to your requirement.
JMS Configuration and read the message from queue a
1) Configure a J2EE Configuration in External Resources with the following details.
Where
Name: J2EEConfiguration
Initial Context Factory: weblogic.jndi.WLInitialContextFactory
URL: t3://localhost:7001
Principal: weblogic
Credentials: weblogic
2) Configure a JMS Configuration in External Resources with the following details
Where
Name: JMSConfiguration
J2EE: J2EEConfiguration
Destination Type: Queue
Lookup Name: com.bibhu.queue – Refer to JMS configuration in Weblogic Server
Connection Factory Lookup Name: com.bibhu.cf – Refer to JMS configuration
3) Configure a Java Configuration in External Resources with the following details
Add weblogic.jar, wsclient.jar, and jms.jar files
4) Create a process and add a Global automatic Activity with the following configuration
5) Add the following code for different purpose
// The below code is meant for reading a message/messages from Queue
logMessage("JMS message retrieved from queue: \n" + message.textValue);
// The below code is meant for sending message to the Queue Where,
// JMSConfiguration: is the External Resource Configuration for JMS
// Bibhu: is the message body
String externalResourceId = "JMSConfiguration";
String msgBody = "Bibhu";
JmsMessage jmsMsg = JmsMessage(type : JmsMessageType.TEXT);
jmsMsg.textValue = msgBody;
jmsMsg.expiration = 'now' + '5m'; // expires in 5 minutes
sendMessage(DynamicJMS, configuration : externalResourceId, message : jmsMsg);
hope the above will help you.
Bibhu

Mule, Weblogic and MQ JMS : deadlock problem

Dear Oracle community,
We are hosting our Mule ESB (3.1) application on a Weblogic 10.3 (11g) server and are using IBM Websphere MQ's JMS solution (with libraries version 7.0.1.7).
The problem we are facing is that JMS connections are created by one of Weblogic's worker (thread) and the close() method for those connections are not necessarily called by the same thread.
This is bad because from what I know this behavior is undefined from JMS specification
(see http://docs.oracle.com/cd/E15051_01/wls/docs103/jms/design_best_practices.html#wp1061413 ) and it is a blocker issue in our case because this lead to a deadlock.
Do someone has any idea how to enforce the fact that the same thread do create and close the connection through Weblogic and/or Mule configuration (without re-implementing the connector) ?
Thanks in advance for your help,
Best regards,
Y.
PS : I've already posted this question on Mule ESB's forum : http://forum.mulesoft.org/mulesoft/topics/mule_weblogic_and_mq_jms_deadlock_problem
Edited by: user7428803 on May 14, 2012 2:26 PM

I hope you found a solution by now, but as an FYI:
* The JMS specification specifically requires that JMS providers support the ability to call connection.close() and session.close() from an arbitrary thread even when another thread is making calls on these objects. It furthermore goes into some detail about the expected behavior of these calls. The best practices link you cited alludes to this: "The JMS Specification states that multi-threading a session, producer, consumer, or message method results in undefined behavior +except when calling close().+"
* Depending on your use case, you may not need to use Mule to integrate MQ with WebLogic. WebLogic supports a variety of options for integrating MQ directly without the use of third party tooling. See http://download.oracle.com/docs/cd/E17904_01/web.1111/e13727/interop.htm .
Tom

Crazy JMS pattern

Hi,
I'm trying to implement this:
- JMS queue BS, named QUEUE, is request/response, it has a URI endpoint and a response URI endpoint
I have 3 proxy services working around this JMS queue, but for now I'm only working with two of them:
- PS 1: receives the http message and writes into the queue with transport outbound JMSMessageID = $body/messageid
- PS 3: an external entity now wants to communicate the response, and this PS routes into QUEUE response endpoint with transport outbound JMSCorrelationID = previous JMSMessageID
Is this possible to do?
I'm having an hard time implementing this, cause PS 1 just freezes and never correlates to the response.
I'm testing this using soapUI... making sure $body/messageid is common at all times.
Is there some tool to check messages (and headers) in JMS queues?
Can someone help me with this plz?

atheek1 I guess you are right.
However I still didn't manage to implement the desired correlation pattern.
I'm surely doing it wrong... but kinda running out of options.
I made two new JMS BS: requestQueue_BS and responseQueue_BS
Both are queues and text message type and requestQueue is JMSCorrelationID response pattern with response URI = responseQueue_BS
PS1 is any XML service that simply routes message to requestQueue using, inside routing, an transport header transformation of JMSCorrelationID to $body/id/text() on outbound request direction.
PS3 is any XML service that simply routes message to responseQueue using, inside routing, an transport header transformation of JMSCorrelationID to $body/id/text() on outbound request direction.
message body example is: <id>4324</id>
This doesn't work... what am I doing wrong?
PS1 just waits for the response... it doesn't matter how many times I trigger PS3 with the same JMSCorrelationID, PS1 just waits until it times out... :(
******* CONFIG FILES ************
requestQueue
<?xml version="1.0" encoding="UTF-8"?>
<xml-fragment xmlns:ser="http://www.bea.com/wli/sb/services" xmlns:tran="http://www.bea.com/wli/sb/transports" xmlns:http="http://www.bea.com/wli/sb/transports/http" xmlns:env="http://www.bea.com/wli/config/env" xmlns:jms="http://www.bea.com/wli/sb/transports/jms">
<ser:coreEntry isProxy="false" isEnabled="true">
<ser:binding type="abstract XML"/>
<ser:monitoring isEnabled="false">
<ser:aggregationInterval>10</ser:aggregationInterval>
</ser:monitoring>
<ser:sla-alerting isEnabled="true">
<ser:alertLevel>normal</ser:alertLevel>
</ser:sla-alerting>
</ser:coreEntry>
<ser:endpointConfig>
<tran:provider-id>jms</tran:provider-id>
<tran:inbound>false</tran:inbound>
<tran:URI>
<env:value>jms://localhost:7001/weblogic.jms.XAConnectionFactory/requestQueueRequest</env:value>
</tran:URI>
<tran:outbound-properties>
<tran:load-balancing-algorithm>round-robin</tran:load-balancing-algorithm>
<tran:retry-count>0</tran:retry-count>
<tran:retry-interval>30</tran:retry-interval>
<tran:retry-application-errors>true</tran:retry-application-errors>
</tran:outbound-properties>
<tran:provider-specific>
<jms:is-queue>true</jms:is-queue>
<jms:is-secure>false</jms:is-secure>
<jms:outbound-properties>
<jms:message-type>Text</jms:message-type>
<jms:expiration>0</jms:expiration>
<jms:enable-message-persistence>true</jms:enable-message-persistence>
<jms:response-required>true</jms:response-required>
<jms:response-URI>jms://localhost:7001/weblogic.jms.XAConnectionFactory/responseQueueRequest</jms:response-URI>
<jms:response-timeout>0</jms:response-timeout>
<jms:response-pattern>JMSCorrelationID</jms:response-pattern>
<jms:response-target-map>
<jms:target-pair>
<jms:target>AdminServer</jms:target>
<jms:destination/>
</jms:target-pair>
</jms:response-target-map>
<jms:pass-caller-subject>false</jms:pass-caller-subject>
</jms:outbound-properties>
<jms:request-encoding>UTF-8</jms:request-encoding>
</tran:provider-specific>
</ser:endpointConfig>
</xml-fragment>
and responseQueue
<?xml version="1.0" encoding="UTF-8"?>
<xml-fragment xmlns:ser="http://www.bea.com/wli/sb/services" xmlns:tran="http://www.bea.com/wli/sb/transports" xmlns:http="http://www.bea.com/wli/sb/transports/http" xmlns:env="http://www.bea.com/wli/config/env" xmlns:jms="http://www.bea.com/wli/sb/transports/jms">
<ser:coreEntry isProxy="false" isEnabled="true">
<ser:binding type="abstract XML"/>
<ser:monitoring isEnabled="false">
<ser:aggregationInterval>10</ser:aggregationInterval>
</ser:monitoring>
<ser:sla-alerting isEnabled="true">
<ser:alertLevel>normal</ser:alertLevel>
</ser:sla-alerting>
</ser:coreEntry>
<ser:endpointConfig>
<tran:provider-id>jms</tran:provider-id>
<tran:inbound>false</tran:inbound>
<tran:URI>
<env:value>jms://localhost:7001/weblogic.jms.XAConnectionFactory/responseQueueRequest</env:value>
</tran:URI>
<tran:outbound-properties>
<tran:load-balancing-algorithm>round-robin</tran:load-balancing-algorithm>
<tran:retry-count>0</tran:retry-count>
<tran:retry-interval>30</tran:retry-interval>
<tran:retry-application-errors>true</tran:retry-application-errors>
</tran:outbound-properties>
<tran:provider-specific>
<jms:is-queue>true</jms:is-queue>
<jms:is-secure>false</jms:is-secure>
<jms:outbound-properties>
<jms:message-type>Text</jms:message-type>
<jms:expiration>0</jms:expiration>
<jms:enable-message-persistence>true</jms:enable-message-persistence>
<jms:response-required>false</jms:response-required>
<jms:pass-caller-subject>false</jms:pass-caller-subject>
</jms:outbound-properties>
<jms:request-encoding>UTF-8</jms:request-encoding>
</tran:provider-specific>
</ser:endpointConfig>
</xml-fragment>
PS1
<?xml version="1.0" encoding="UTF-8"?>
<xml-fragment xmlns:ser="http://www.bea.com/wli/sb/services" xmlns:tran="http://www.bea.com/wli/sb/transports" xmlns:env="http://www.bea.com/wli/config/env" xmlns:http="http://www.bea.com/wli/sb/transports/http" xmlns:con="http://www.bea.com/wli/sb/stages/config">
<ser:coreEntry isProxy="true" isEnabled="true">
<ser:binding type="abstract XML"/>
<ser:monitoring isEnabled="false">
<ser:aggregationInterval>10</ser:aggregationInterval>
<ser:pipelineMonitoringLevel>Pipeline</ser:pipelineMonitoringLevel>
</ser:monitoring>
<ser:reporting>true</ser:reporting>
<ser:logging isEnabled="true">
<ser:logLevel>debug</ser:logLevel>
</ser:logging>
<ser:sla-alerting isEnabled="true">
<ser:alertLevel>normal</ser:alertLevel>
</ser:sla-alerting>
<ser:pipeline-alerting isEnabled="true">
<ser:alertLevel>normal</ser:alertLevel>
</ser:pipeline-alerting>
</ser:coreEntry>
<ser:endpointConfig>
<tran:provider-id>http</tran:provider-id>
<tran:inbound>true</tran:inbound>
<tran:URI>
<env:value>/ItevProj/proxy/test/3/ps1</env:value>
</tran:URI>
<tran:inbound-properties/>
<tran:all-headers>false</tran:all-headers>
<tran:provider-specific>
<http:inbound-properties/>
</tran:provider-specific>
</ser:endpointConfig>
<ser:router>
<con:flow xmlns:con="http://www.bea.com/wli/sb/pipeline/config">
<con:route-node name="RouteNode1">
<con:context/>
<con:actions>
<con1:route xmlns:con1="http://www.bea.com/wli/sb/stages/routing/config">
<con2:id xmlns:con2="http://www.bea.com/wli/sb/stages/config">_ActionId-9035043200913057533-78de896f.1287cc7514b.-7faf</con2:id>
<con1:service ref="ItevProj/business/common/jms/test/3/requestQueue" xsi:type="ref:BusinessServiceRef" xmlns:ref="http://www.bea.com/wli/sb/reference" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
<con1:outboundTransform>
<con2:transport-headers xmlns:con2="http://www.bea.com/wli/sb/stages/transform/config">
<con3:id xmlns:con3="http://www.bea.com/wli/sb/stages/config">_ActionId-9035043200913057533-78de896f.1287cc7514b.-7da1</con3:id>
<con2:header-set>outbound-request</con2:header-set>
<con2:header name="JMSCorrelationID" value="expression">
<con3:xqueryText xmlns:con3="http://www.bea.com/wli/sb/stages/config">$body/id/text()</con3:xqueryText>
</con2:header>
</con2:transport-headers>
</con1:outboundTransform>
<con1:responseTransform/>
</con1:route>
</con:actions>
</con:route-node>
</con:flow>
</ser:router>
</xml-fragment>
PS3
<?xml version="1.0" encoding="UTF-8"?>
<xml-fragment xmlns:ser="http://www.bea.com/wli/sb/services" xmlns:tran="http://www.bea.com/wli/sb/transports" xmlns:env="http://www.bea.com/wli/config/env" xmlns:http="http://www.bea.com/wli/sb/transports/http" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:con="http://www.bea.com/wli/sb/pipeline/config" xmlns:con1="http://www.bea.com/wli/sb/stages/routing/config" xmlns:con2="http://www.bea.com/wli/sb/stages/config">
<ser:coreEntry isProxy="true" isEnabled="true">
<ser:binding type="abstract XML" xmlns:con3="http://www.bea.com/wli/sb/services/bindings/config"/>
<ser:monitoring isEnabled="false">
<ser:aggregationInterval>10</ser:aggregationInterval>
<ser:pipelineMonitoringLevel>Pipeline</ser:pipelineMonitoringLevel>
</ser:monitoring>
<ser:reporting>true</ser:reporting>
<ser:logging isEnabled="true">
<ser:logLevel>debug</ser:logLevel>
</ser:logging>
<ser:sla-alerting isEnabled="true">
<ser:alertLevel>normal</ser:alertLevel>
</ser:sla-alerting>
<ser:pipeline-alerting isEnabled="true">
<ser:alertLevel>normal</ser:alertLevel>
</ser:pipeline-alerting>
</ser:coreEntry>
<ser:endpointConfig>
<tran:provider-id>http</tran:provider-id>
<tran:inbound>true</tran:inbound>
<tran:URI>
<env:value>/ItevProj/proxy/test/3/ps3</env:value>
</tran:URI>
<tran:inbound-properties/>
<tran:all-headers>false</tran:all-headers>
<tran:provider-specific>
<http:inbound-properties/>
</tran:provider-specific>
</ser:endpointConfig>
<ser:router>
<con:flow>
<con:route-node name="RouteNode1">
<con:context>
<con2:varNsDecl namespace="http://webservice.chargingstation.itev.criticalsoftware.com" prefix="web"/>
</con:context>
<con:actions>
<con1:route>
<con2:id>_ActionId-9035043200913057533-78de896f.1287cc7514b.-7eb7</con2:id>
<con1:service ref="ItevProj/business/common/jms/test/3/responseQueue" xsi:type="ref:BusinessServiceRef" xmlns:ref="http://www.bea.com/wli/sb/reference"/>
<con1:outboundTransform>
<con3:transport-headers xmlns:con3="http://www.bea.com/wli/sb/stages/transform/config">
<con2:id>_ActionId-9035043200913057533-78de896f.1287cc7514b.-7d69</con2:id>
<con3:header-set>outbound-request</con3:header-set>
<con3:header name="JMSCorrelationID" value="expression">
<con2:xqueryText>$body/id/text()</con2:xqueryText>
</con3:header>
</con3:transport-headers>
</con1:outboundTransform>
<con1:responseTransform/>
</con1:route>
</con:actions>
</con:route-node>
</con:flow>
</ser:router>
</xml-fragment>

Jms queue share

hi, i need some help relation to jms, recently i have a queue in clusterA but i need to share it with clusterB. The problem is that when i change the subdeployment and target to add the clusterB it says that the queue must be in one cluster. How can i resolve this to share it to the other cluster too?
Should i need to use sfa or bridge? Which would be the best to use in this case?
Thanks

Hi,
I was going through this thread and could understand that you have UDQ on cluster-1 (with 4 MS).. also you have 4 JMS-server mapped with 4 managed server instances. The producer application is deployed on cluster-1 which will send messages on UDQ.. which weblogic will distribute using the load balancing algorithms on the underlying JMS system i.e, to the 4 JMS server. Now I understand that you have another cluster-2 on same domain with 4 managed servers. Also cluster-2 hosts the consumer application to access the messages produced by producer. Your consumer application just need to create a JMS connection to the UDQ using connection factory config.. weblogic will itself map your 4 consumers (as app is deployed on cluster with 4 MS) to the 4 JMS servers of cluster1 . I don't see any requirement of pointing your UDQ to cluster-2. For type of consumer application to be used.. as already suggested by others it's best to use MDB which will be listening on all incoming messages on the queue.
As option 2 if you want to go with JMS bridge , then create 1 more UDQ to point it to cluster-2 (u will also require another JMS module which will point on cluster-2). The create a JMS bridge and add UDQ on cluster-1 as source destination and UDQ on cluster-2 as target destination. This way your application deployed on cluster-1 can put messages on source destination of JMS bridge and your say MDB application deployed on cluster-2 can access those messages over target destination of JMS bridge.
Hope this helps.
Thanks,
Ranjan

What is the different between JMS Client for sonicMQ 4.0 and sonicMQ 6.1?

hi everybody,
I'm currently in big crisis and hope somebody out there
can give me some guidance.
We have a JMS client developed by an ex-colleague. The jms client was
developed specifically for SonicMQ 4.0. Recently, we are upgrading to
SonicMQ 6.1 and thus, we re-compile his code. Before re-compiling his
code, we had put sonic_Client.jar and sonic_Crypto.jar in the library
directory. There was no error.
We were able to startup our receiver client without error. The receiver
subscribed to the SonicMQ server 6.1 successfully. We could see it in the
SonicMQ Management console. However, when we send a topic, the
receiver client does not consume. All of us had been working day and night
to find out the answer but no progress until now.
We have a couple of properties file and I think, jmsconnect.properties file is
the one been used. This is the content:
# Must enter value if JNDIURL below, is not specified
BROKER=mssonq:2506
JNDIURL=
MODETYPE=com.sun.jndi.ldap.LdapCtxFactory
TOPICCONNECTIONFACTORY=
QUEUECONNECTIONFACTORY=
The previous version that was developed by my ex-colleague is still running
fine in the current production server.
Please let me know if the jmsconnect.properties is correct or wrong. By the
way, what are the major code changes required for jms client that was
meant for SonicMQ 4.0 to get it upgraded for SonicMQ 6.1.
Any help will really appreciate.
thanks & regards,
Kenny

AT&T is a GSM carrier. Sprint and Verizon are CDMA. The CDMA iPhone 4 has no SIM slot. The CDMA iPhone 4S does but the phones still can't be used on GSM in the U.S. The software versions are the same across carriers at this time.

Basic questions on JMS

Hi, I am in wlp816. I have 3 managed servers in a cluster. How many JMS servers do I need? What is the migratable server? Do I need to create a migratable server? I am looking at the document http://download.oracle.com/docs/cd/E13222_01/wls/docs81/ConsoleHelp/jms_config.html#1105051. It says I need to choose from Target list box and Migratable Target list box. But I only see Target list box in our console. Is there a introduction about how JMS works in WLS? Thanks

The decision about whether to use Migratable Targets and/or Multiple JMS Servers very much depends on the specifics of your application's HA and scalability requirements. A single JMS server may be perfectly adequate for your needs, or you may absolutely require multiple JMS servers.
For good introductions to WL 8.1 JMS, I recommend reading through your documentation (there's a nice doc list at http://download.oracle.com/docs/cd/E13222_01/wls/docs81/messaging.html), and also picking up a copy of "Mastering BEA WebLogic Server: Best Practices for Building and Deploying J2EE Applications", which was written specifically for WebLogic 8.1.
Regards,
Tom Barnes

Using EJB vs Socket : expensive satellite line

We are migrating a bank system from Clipper to Java(J2EE). One of the requisites is to save the bandwidth through the satellite line. Some developers came with a idea to make an object in bank store that talks with the central server through sockets, and in the central server a thread is created to handle that call and call the session bean. Anyone know how big (in bytes) is a EJB call??? (not the jndi lookup neither home finding), just a method to a session bean. How many bytes are added to the parameters data??? It could be a good idea to change from EJB to sockets through the satellite??? Another point is that the satellite has a 1.22 sec delay. Should it be used messages??? And the same question I make for messages, how big would be (in bytes) to send a message using JMS???

Greetings,
We are migrating a bank system from Clipper to
Java(J2EE). One of the requisites is to save the
bandwidth through the satellite line. Some developers
came with a idea to make an object in bank store that
talks with the central server through sockets, and inUltimately, this developer is just "reinventing the wheel". All synchronous network technologies communicate over sockets. This is the job of the object stubs through which EJBs (as well as other component models: CORBA, DCE, DCOM, etc.), communicate. In essence, this developer is suggesting communication client and server "objects" to take the place of a communication "stub" and "skeleton" pair. Only, in this case it would really only add to the complexity of the issue by adding an additional communication framework (aka "point of failure") - over-satellite client/server pair - in front of the framework that must still be used - EJB stub/skeleton pair (additionally, EJB skeletons are optional and may not even be used by your particular vendor). Furthermore, this solution will also require the creation of a new protocol to be communicated over the satellite decorators (an additional maintenance piece; aka "added complexity"). This solution may save some up-front bandwidth (largely depending on the implemented protocol), but the increased latency and maintenance complexity in your application may simply negate it (increased possibility for transmission repeats, session failures, protocol errors, etc.).
the central server a thread is created to handle that
call and call the session bean. Anyone know how big
(in bytes) is a EJB call??? (not the jndi lookup
neither home finding), just a method to a session
bean. How many bytes are added to the parameters
data??? It could be a good idea to change from EJB toAn EJB sits atop a communication layer which may be implemented using a vendor's protocol of choice. Such may be JRMP (RMI), IIOP (CORBA), or proprietary (e.g. WebLogic's 'T3'). The answer to this question, therefore, depends upon the (packet size of) the actual protocol in use.
sockets through the satellite??? Another point is thatDepends... the added complexity of this approach will add the TCO of your application in other ways. The real question is "which is more - maintenance cost, or bandwidth cost?" Some things to keep in mind:
* An effective socket implementation requires: invention of a stable and robust protocol; proper state management; a scalable threading model; and let's not forget - its own full lifecycle of DDTM: design, development, testing, and maintenance.
* Current component models - EJB most certainly included :) - already have, and have undergone, the previous.
the satellite has a 1.22 sec delay. Should it be usedAdjust your server's timeout parameters.
messages??? And the same question I make for messages,Depends if your application needs synchronous or asynchronous communication, and if asynchronous, 1-way or 2-way. If synchronous (response must follow request), then "socket-based" communication is required - whether it's through EJB or direct. If asynchronous 1-way (response not required), then JMS or low-level datagram-based communication may be used; both may also be used for 2-way (anytime response), but both, of course, also have their own sets of pros and cons depending on your application and following many of the same arguments as above...
how big would be (in bytes) to send a message using
JMS???As with EJB, depends on the protocol implementor.
Regards,
Tony "Vee Schade" Cook

OSB Dynamic Routing and Transaction Rollback

Hi,
I have implemented dynamic routing to different jms business services.
That's the flow:
1. I have a proxy service which is invoked via a message delivered to a jms queue(XA connection factory), this queue is configured with
Error Destination, expiration policy redirect, redelivery limit 5 and redelivery delay override 100
2. I use a dynamic routing action
<ctx:route isProxy="false">
<ctx:service>
$businessServiceXXX
</ctx:service>
</ctx:route>
where $businessServiceXXX is a variable to hold my target jms business service, its value depends on some incoming inbound headers.
3. if the endpoint is not correct(business service endpoint is dynamic) I catch the error in a Error handler, I raise an Error but :
THE MESSAGE IS NOT REDIRECTED TO THE ERROR QUEUE.
I know I could solve the issue with another approach like an external table to capture(fix) the endpoints, but it won't be so flexible in terms of deployment capability.
Any Ideas ?
Thanks,
T.

Hi Tony,
Tested this in ALSB 2.5 . Transaction rollbacks fine when error in dynamic routing. I am attaching the test JMS proxy we have used for this.
We had XA enabled CF for JMS proxy service and target JMS BS. The dynamic route was configured in route node with no route error handler or service error handler. The test case was to pause the target JMS queue for production. We could see messages rolling back to the source queue and getting redelivered.
Attaching the Sbconfig for this proxy. Proxy Name: Dynamic Routing
<?xml version="1.0" encoding="UTF-8"?>
<xml-fragment name="DynamicRouting">
<ser:coreEntry isEnabled="true" isProxy="true" name="DynamicRouting" isAutoPublish="false" xmlns:ser="http://www.bea.com/wli/sb/services">
<ser:description/>
<ser:binding type="abstract XML"/>
</ser:coreEntry>
<ser:endpointConfig xmlns:ser="http://www.bea.com/wli/sb/services">
<tran:provider-id xmlns:tran="http://www.bea.com/wli/sb/transports">jms</tran:provider-id>
<tran:inbound xmlns:tran="http://www.bea.com/wli/sb/transports">true</tran:inbound>
<tran:URI xmlns:tran="http://www.bea.com/wli/sb/transports">
<env:value xmlns:env="http://www.bea.com/wli/config/env">jms://localhost:7001/XACF/InputQueue</env:value>
</tran:URI>
<tran:inbound-properties xmlns:tran="http://www.bea.com/wli/sb/transports"/>
<tran:all-headers xmlns:tran="http://www.bea.com/wli/sb/transports">false</tran:all-headers>
<tran:provider-specific xsi:type="jms:JmsEndPointConfiguration" xmlns:jms="http://www.bea.com/wli/sb/transports/jms" xmlns:tran="http://www.bea.com/wli/sb/transports" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<jms:is-queue>true</jms:is-queue>
<jms:is-secure>false</jms:is-secure>
<jms:inbound-properties>
<jms:response-required>false</jms:response-required>
</jms:inbound-properties>
<jms:request-encoding>UTF-8</jms:request-encoding>
</tran:provider-specific>
</ser:endpointConfig>
<ser:router xmlns:ser="http://www.bea.com/wli/sb/services">
<con:pipeline name="PipelinePairNode1_request" type="request" xmlns:con="http://www.bea.com/wli/sb/pipeline/config">
<con:stage name="Configuration">
<con:comment/>
<con:context/>
<con:actions>
<con1:assign varName="input" xmlns:con1="http://www.bea.com/wli/sb/stages/transform/config">
<con1:expr>
<con:xqueryText xmlns:con="http://www.bea.com/wli/sb/stages/config"><![CDATA[<root>
<type value="jms">
          <service>DynamicRouting/BusinessService/JMS</service>
     </type>
     <type value="http">
     <service>DynamicRouting/BusinessService/HTTP</service>
     <operation>Test</operation>
     </type>
</root>]]></con:xqueryText>
</con1:expr>
</con1:assign>
</con:actions>
</con:stage>
</con:pipeline>
<con:pipeline name="PipelinePairNode1_response" type="response" xmlns:con="http://www.bea.com/wli/sb/pipeline/config"/>
<con:flow xmlns:con="http://www.bea.com/wli/sb/pipeline/config">
<con:pipeline-node name="PipelinePairNode1">
<con:request>PipelinePairNode1_request</con:request>
<con:response>PipelinePairNode1_response</con:response>
</con:pipeline-node>
<con:route-node name="DynamicRoute">
<con:comment/>
<con:context/>
<con:actions>
<con1:dynamic-route xmlns:con1="http://www.bea.com/wli/sb/stages/routing/config">
<con1:service>
<con:xqueryText xmlns:con="http://www.bea.com/wli/sb/stages/config"><ctx:route>
     <ctx:service isProxy="false">{data($input/*:type[@value=$body/*:body/*:type/text()]/*:service)}</ctx:service>
          if($input/*:type[@value=$body/*:body/*:type/text()]/*:operation) then
               <ctx:operation>{data($input/*:type[@value=$body/*:body/*:type/text()]/*:operation)}</ctx:operation>
else()
</ctx:route></con:xqueryText>
</con1:service>
<con1:outboundTransform>
<con2:routing-options xmlns:con2="http://www.bea.com/wli/sb/stages/transform/config">
<con2:uriExpr>
<con:xqueryText xmlns:con="http://www.bea.com/wli/sb/stages/config">$body/*:body/*:url/text()</con:xqueryText>
</con2:uriExpr>
</con2:routing-options>
</con1:outboundTransform>
<con1:responseTransform/>
</con1:dynamic-route>
</con:actions>
</con:route-node>
</con:flow>
</ser:router>
</xml-fragment>
Regards,
Atheek
Edited by: atheek1 on 27-Apr-2010 19:48

Unable to resolve 'oracle.j2ee.ws.server.async.DefaultRequestQueue'

Hi
When executing import/export service through FSM we are getting below error on server console. Can someone please help us to resolve this.
<Nov 22, 2012 10:25:14 PM IST> <Error> <oracle.j2ee.ws.common.jaxws.JAXWSMessages> <BEA-000000> <[MessageID: uuid:3eac9f32-ad81-4d96-b5b2-18cf0fd887c0[migRequestId=300100015300332][migObjectId=300100015300326][]] Could not send async request message to the JMS queue.
java.security.PrivilegedActionException: javax.naming.NameNotFoundException: Unable to resolve 'oracle.j2ee.ws.server.async.DefaultRequestQueue'. Resolved 'oracle.j2ee.ws.server.async'; remaining name 'DefaultRequestQueue'
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:373)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:146)
at weblogic.security.Security.runAs(Security.java:61)
at oracle.security.jps.wls.jaas.WlsActionExecutor.execute(WlsActionExecutor.java:51)
at oracle.security.jps.internal.jaas.CascadeActionExecutor.execute(CascadeActionExecutor.java:56)
at oracle.j2ee.ws.server.provider.GenericProviderPlatform.runAs(GenericProviderPlatform.java:365)
at oracle.j2ee.ws.server.jaxws.JMSChannel.getConnection(JMSChannel.java:468)
at oracle.j2ee.ws.server.jaxws.JMSChannel.sendMessage(JMSChannel.java:235)
at oracle.j2ee.ws.server.jaxws.JMSChannel.sendRequest(JMSChannel.java:199)
at oracle.j2ee.ws.server.jaxws.AsyncServiceRuntimeDelegate$JMSMessageQueue.send(AsyncServiceRuntimeDelegate.java:170)
at oracle.j2ee.ws.server.jaxws.AsyncServiceRuntimeDelegate.pro
Caused By: javax.naming.NameNotFoundException: Unable to resolve 'oracle.j2ee.ws.server.async.DefaultRequestQueue'. Resolved 'oracle.j2ee.ws.server.async'; remaining name 'DefaultRequestQueue'
at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:1139)
at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:252)
at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:182)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:206)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:214)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:214)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:214)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:214)
FYI:
The "oracle.jrf.ws.async_template_11.1.1.jar" jar file required for JMS (oracle.j2ee.ws.server.async.) which is present in below directory path of weblogic standalone.
Edited by: user12820425 on Dec 2, 2012 11:56 PM

Are you using Standalone (or) Integrated WLS. It works only on Standalone WLS.
Also for these issues, please put this in Cross Pillar Integration Forum. Contact Ning.Dong

Requirement of JMS

Similar Messages

Maybe you are looking for