Correlation of JMS and PI

Hello.
I have the following scenario: an external system sends a messages via IBM websphere MQ to PI.
PI takes the message - and sends an IDOC to an ECC system.
The ECC system than creates an ALEAUD and sends it back to the PI.
Now I need to send the ALEAUD into a different MQ queue.
The problem is - I need somehow to correlate the ALEAUD to the first message.
It will be better not to use BPM for this scenario if possible.
Points will be given to anyone who will provide good information.
P.S. I know that in order to use ALEAUD - I have to use IDX_ALEREQUEST

there are 2 options ...
1. without BPM...
call the reciever IDOC in a receiver Proxy .......then after the idoc is posted OK or with error.. call another proxy and send the status back to PI and PI will send it to MQ
2. with BPM.
use a aysnc send step with application ack...and then divert the ack that comes to the MQ

Similar Messages

Correlation for JMS Queue

Hi,
I have following scenario :
Queue1
Bpel1 -> Writes Schema A to Queue1
Bpel2 -> Writes Schema B to Queue1
Bpel3 -> Reads from Queue1
I need that Bpel3 should read only Schema A from Queue and not Schema B.
So how will i define the correlation between Bpel1 & Bpel 3.
I tried fetching the processId in Bpel 1 and add it to Invoke property jca.jms.JmsCorrelation_id, but was not able to set the same in Bpel3.
Any help/spec in setting up correlation for JMS Queues is highly apreciated.
Thanks !!

In standard JMS, an application can specify a correlation-id on per message basis using the javax.jms.Message API, and then specify a filter (a "selector") when creating a consumer via the javax.jms.Session API, but, in general, it is usually better to use a separate dedicated queue per business process (simplifies management, simplifies coding, improves perf, etc), or, if that's not an attractive option, to use a single MDB to dispatch messages from the same queue to different business processes. I don't know the specific steps to do the same in BPEL.
You might want to try posting to the BPEL forum at BPEL
Hope this helps,
Tom

Difference Between JMS and RMI

Difference Between JMS and RMI in J2EE Technologies

STFW
JMS - http://www.google.co.za/search?hl=en&q=what+is+jms&meta=
RMI - http://www.google.co.za/search?hl=en&q=what+is+rmi&meta=

JMS and Java EE 5 Tutorial

Hello,
I'm new to JMS and have been following Suns JMS tutorial here....
[http://java.sun.com/javaee/5/docs/tutorial/doc/bncfa.html#bncfc|http://java.sun.com/javaee/5/docs/tutorial/doc/bncfa.html#bncfc]
I followed the example for the Producer / SynchConsumer programs.
I also created my resources using Sun Java Application Server.
The code example uses annotations only (@Resource) and does not use JNDI lookup.
My problem is that the annotations only solution, as described in the tutorial,
    @Resource(mappedName = "jms/ConnectionFactory")
    private static ConnectionFactory connectionFactory;
    @Resource(mappedName = "jms/Queue")
    private static Queue queue;
    @Resource(mappedName = "jms/Topic")
    private static Topic topic;give me a NullPointerException error when this code is run...
connection = connectionFactory.createConnection();I've added JNDI lookup ....
        System.setProperty("java.naming.factory.initial", "com.sun.appserv.naming.S1ASCtxFactory");
     System.setProperty("java.naming.provider.url", "iiop://111.222.333.109:3700");
     InitialContext ic = new InitialContext();
     connectionFactory = (ConnectionFactory)ic.lookup("jms/ConnectionFactory");
     queue = (Queue)ic.lookup("jms/Queue");
     topic = (Topic)ic.lookup("jms/Topic");and it seems to work now....
Anyone come accross this before?
What am I missing from the annotations only solution?
Thanks,
Jon

Hi,
Previously I was trying to run this using Eclipse.
I tried this using NetBeans IDE and the annotations worked fine.
Problem solved.
/Jon

What is correlation ? when and how to use it in BPEL process?

Hi,
What is correlation ? when and how to use it in BPEL process?
Thanks

Hi:
Take a look at this entry http://blog.andrade.inf.br/2010/03/oracle-bpel-11g-correlation-sets.html
thx
best

Pros and Cons of using REST over JMS (and other technologies)

Hey all,
I am working on a project where we were using JMS initially to send messages between servers. Our front end servers have a RESTful API and use JEE6, with EJB 3.1 entity beans connected to a mysql database and so forth. The back end servers are more like "agents" so to speak.. we send some work for them to do, they do it. They are deployed in GlassFish 3.1 as well, but initially I was using JMS to listen to messages. I learned that JMS onMessage() is not threaded, so in order to facilitate handling of potentially hundreds of messages at once, I had to implement my own threading framework. Basically I used the Executor class. I could have used MDBs, but they are a lot more heavyweight than I needed, as the code within the onMessage was not using any of the container services.
We ran into other issues, such as deploying our app in a distributed architecture in the cloud like EC2 was painful at best. Currently the cloud services we found don't support multi-cast so the nice "discover" feature for clustering JMS and other applications wasn't going to work. For some odd reason there seems to be little info on building out a scalable JEE application in the cloud. Even the EC2 techs, and RackSpace and two others had nobody that understood how to do it.
So in light of this, plus the data we were sending via JMS was a number of different types that had to all be together in a group to be processed.. I started looking at using REST. Java/Jersey (JAX-RS) is so easy to implement and has thus far had wide industry adoption. The fact that our API is already using it on the front end meant I could re-use some of the representations on the back end servers, while a few had to be modified as our public API was not quite needed in full on the back end. Replacing JMS took about a day or so to put the "onmessage" handler into a REST form on the back end servers. Being able to submit an object (via JAXB) from the front servers to the back servers was much nicer to work with than building up a MapMessage object full of Map objects to contain the variety of data elements we needed to send as a group to our back end servers. Since it goes as XML, I am looking at using gzip as well, which should compress it by about 90% or so, making it use much less bandwidth and thus be faster. I don't know how JMS handles large messages. We were using HornetQ server and client.
So I am curious what anyone thinks.. especially anyone that is knowledgeable with JMS and may understand REST as well. What benefits do we lose out on via JMS. Mind you, we were using a single queue and not broadcasting messages.. we wanted to make sure that one and only one end server got the message and handled it.
Thanks..look forward to anyone's thoughts on this.

851827 wrote:
Thank you for the reply. One of the main reasons to switch to REST was JMS is strongly tied to Java. While I believe it can work with other message brokers that other platforms/languages can also use, we didn't want to spend more time researching all those paths. REST is very simple, works very well and is easy to implement in almost any language and platform. Our architecture is basically a front end rest API consumed by clients, and the back end servers are more like worker threads. We apply a set of rules, validations, and such on the front end, then send the work to be done to the back end. We could do it all in one server tier, but we also want to allow other 3rd parties to implement the "worker" server pieces in their own domains with their own language/platform of choice. Now, with this model, they simply provide a URL to send some REST calls to, and send some REST calls back to our servers.well, this sounds like this would be one of those requirements which might make jms not a good fit. as ejp mentioned, message brokers usually have bindings in multiple languages, so jms does not necessarily restrict you from using other languages/platforms as the worker nodes. using a REST based api certainly makes that more simple, though.
As for load balancing, I am not entirely sure how glassfish or JBoss does it. Last time I did anything with scaling, it involved load balancers in front of servers that were session/cookie aware for stateful needs, and could round robin or based on some load factor on each server send requests to appropriate servers in a cluster. If you're saying that JBoss and/or GlassFish no longer need that.. then how is it done? I read up on HornetQ where a request sent to one ip/hornetq server could "discover" other servers in a cluster and balance the load by sending requests to other hornetq servers. I assume this is how the JEE containers are now doing it? The problem with that to me is.. you have one server that is loaded with all incoming traffic and then has to resend it on to other servers in the cluster. With enough load, it seems that the glassfish or jboss server become a load balancer and not doing what they were designed to do.. be a JEE container. I don't recall now if load balancing is in the spec or not..I would think it would not be required to be part of a container though, including session replication and such? Is that part of the spec now?you are confusing many different types of scaling. different layers of the jee stack scale in different ways. you usually scale/load balance at the web layer by putting a load balancer in front of your servers. at the ejb layer, however, you don't necessarily need that. in jboss, the client-side stub for invoking remote ejbs in a cluster will actually include the addresses for all the boxes and do some sort of work distribution itself. so, no given ejb server would be receiving all the incoming load. for jms, again, there are various points of work to consider. you have the message broker itself which is scaled/load balanced in whatever fashion it supports (don't know many details on actual message broker impls). but, for the mdbs themselves, each jee server is pretty independent. each jee server in the cluster will start a pool of mdbs and setup a connection to the relevant queue. then, the incoming messages will be distributed to the various servers and mdbs accordingly. again, no single box will be more loaded than any other.
load balancing/clustering is not part of the jee "spec", but it is one of the many features that a decent jee server will handle for you. the point of jee was to specify patterns for doing work which, if followed, allow the app server to do all the "hard" parts. some of those features are required (transactions, authentication, etc), and some of those features are not (clustering, load-balancing, other robustness features).
I still would think dedicated load balancers, whether physical hardware or virtual software running in a cloud/VM setup would be a better solution for handling load to different tiers?like i said, that depends on the tier. makes sense in some situations, not others. (for one thing, load-balancers tend to be http based, so they don't work so well for non-http protocols.)

I don't understand correlation between ACL and dACL. If dACL is downloaded to the Catalyst switch what is the status of the ACL

Understanding ISE and dACL.
I don't understand correlation between ACL and dACL.
If dACL is downloaded to the Catalyst switch what is the status of the ACL attached to physical port. Is dACL appended to the existing ACL? When I typed ‘sh ip access-list int fa0/1’ I can see only dACL for access domain and dACL for voice domain appended to the previous dACL and no ACL lines.
Regards,
Vice

Hi,
Downloadable ACLs (dACL) are applied from your RADIUS server based on authentication and authorization policies. It overrides any standard interface ACL.
Standard interface ACLs are in place to limit traffic on the port before 802.1x or MAB authentication.
When an authenticated session terminates on the interface the standard ACL will be re-applied until the next authentication.

JMS and JDBC Adapter in PI7.1

Hi All,
Kindly tell me about the blogs for JMS and JDBC adapter.
Please tell me about the Message Types in JMS adapter.
Thanks in advance.

Hi Shwetambari,
Thanks for the reply.
We need to mention the Adapter Modules while configuring the communiucation channels in JMS
e.g. Adapter/ConvertJMSMessageToBinary,Adapter/ConvertBinaryToXMBMessage etc.
So please tell me whether we need to write the cide for the same in JAVA or it is already there ?If it is there then whre can we get it?Do we need to decompile the archeve ?If so, then how to do it?
Can you give me the Adaqpter Modules for which the code is already there?
The JMS adapter (Java Message Service) enables you to connect messaging systems to the Integration Engine or the PCK.
What are the different types of Messaging Systems?Or what is meant by the Messaging System in JMS?
What are the different types of Messages used?
Thanks in advance.
Edited by: Shweta Kullkarni on Sep 4, 2009 5:22 AM

JMSML - XML Based Mark-Up Language for BEA WebLogic JMS and JMX

          JMSML is a Mark-Up language designed and developed to make Java Messaging Service
          (JMS) and Java Management Extensions (JMX) programming easy by hiding all the
          JMS and JMX Java API complexity behind a few, simple, easy to use XML tags.
          Both the White Paper and the binary download are available in dev2dev.beasys.com
          at the link below:
          http://dev2dev.beasys.com/resourcelibrary/whitepapers.jsp?highlight=whitepapers
          Regards
          [email protected]


Hi,
I finally managed to post a message to ActiveMQ 5.4.2 from WLS 10.3. I created a foreign JMS Server in WLS. I am not sure if you still have this issue, but I was facing this problem and managed to resolve it so posting the reply!
I placed the activemq-all-5.4.2.jar file in WLS server classpath.
The settings I used for the Foreign Server are:
General tab
JNDI Initial Context Factory: org.apache.activemq.jndi.ActiveMQInitialContextFactory
JNDI Connection URL: tcp://localhost:61616
Destinations Tab
Name: TestQueue
Local JNDI Name: TestQueue
Remote JNDI Name: dynamicQueues/TestQueue (I tried with a normal queue, but it didn't work. So used dynamicQueues here. Will try with other queue also)
Connection Factories Tab
Name: AMQConnectionFactory (
Local JNDI Name: AMQConnectionFactory
Remote JNDI Name: ConnectionFactory (This is default name given by Active MQ, you can change by adding names in jndi.properties file and placing it in config folder of ActiveMQ installation. Please check here: http://activemq.apache.org/jndi-support.html)
Using this configuration I was able to post message to ActiveMQ queue from Oracle Service Bus. One more issue to be taken care is that if the message type is not "Text" then the message body was coming as blank in ActiveMQ. So set the message type as "Text" explicitly.

WebLogic JMS and MQ JMS Mix

          I am writing a bean that reads a message from MQ (using MQJMS) and then write it
          onto a WebLogic JMS ( something lika a bridge). However I don't want to use bridge.
          Question/Problem Statement:
          Once I include mq jms jar files in class path. Would that in conflict with WebLogic
          JMS. How do in my program I make sure that it is using the MQ or WLS JMS implementation.
          I can have InitialContext() setup for mq in File and for WebLogic it is WebLogic's
          Initial Context. Thats is the only thing that I can tell in the program.
          Basically, I am trying to see what will make it ( fully qualified JMS Objects
          or what) decide which implmenatation to use.
          Chris


The WebLogic JMS and MQSeries JMS classes won't conflict. Each JMS provider
          provides different classes that implement the same interfaces, so you can
          have a whole bunch of providers in your classpath and things should be OK.
          Most code that's written to the JMS API (including the code inside WLS that
          receives messages for MDBs) gets the JMS "ConnectionFactory" via JNDI, and
          uses that to create the other objects. (It also has to look up the
          "Destination" objects from JNDI.) When you code to the JMS standard only,
          then the only thing that "tells" your program which provider is being used
          is the ConnectionFactory class that you create or get out of JNDI.
          Below is my usual plug for the white paper that helps explain some of this
          stuff:
          http://dev2dev.bea.com/resourcelibrary/whitepapers.jsp?highlight=whitepapers
          Look for "Using foreign JMS provdiesr with WLS".
          greg
          "Chris" <[email protected]> wrote in message
          news:[email protected]...
          >
          > I am writing a bean that reads a message from MQ (using MQJMS) and then
          write it
          > onto a WebLogic JMS ( something lika a bridge). However I don't want to
          use bridge.
          >
          > Question/Problem Statement:
          > Once I include mq jms jar files in class path. Would that in conflict with
          WebLogic
          > JMS. How do in my program I make sure that it is using the MQ or WLS JMS
          implementation.
          > I can have InitialContext() setup for mq in File and for WebLogic it is
          WebLogic's
          > Initial Context. Thats is the only thing that I can tell in the program.
          >
          > Basically, I am trying to see what will make it ( fully qualified JMS
          Objects
          > or what) decide which implmenatation to use.
          >
          > Chris

Is it a complex task to translate between JMS and MQ?

Hello!
I wonder if it is a complex task to translate a JMS message (javax.jms.Message) to a MQ message (com.xxx.MQMessage)?
xxx=I do not remember the package name for MQMessage
Right now I participate in a project where we need to do this translation.
(I must admit that I thougt there was no need for a translation. I thought that JMS was transparent to MQ and vice versa. But I guess I was wrong)
I would love to hear some experiance and perhaps if there is some "best practice", please let me know!
Best regards
Fredrik

antsbull wrote:
I'm happy for you that you use WebLogic - however WebSphere MQ is the leading messaging technology in the industry. If it is configured correctly it guarantees 100% message retention. You may beg to differ, but you have nothing to back it up with so far - maybe IBM should be sued for false advertising if it is impossible (as you say)?Not really. IBM isn't a very important software company, IMO. They're huge in global services, but they passed leadership in hardware and software off to others decades ago. Or maybe you're one of those people who still lives in the 80s and thinks of IBM as a "leader".
There's a lot of IBM legacy out there. Banks are still running DB2, but nobody thinks it's a leader in the relational database space. There's a lot of Cobol code with CICS running on mainframes, but surely you're not going to cite that as cutting edge, are you?
Just curious - do you work for IBM?
All I know is that MQ is the industry standard, as you can easily discover on google or wikipedia or whatever you want. Wikipedia? Is that your best source? LOL!
Let's look at Wikipedia, shall we? Your own source tells me that WebSphere is ~40% of the market:
http://en.wikipedia.org/wiki/MQSeries
I'm even suspicious of these numbers, because I think they leave out the open source parts of the market. How do you quantify that? # downloads? # of systems in production? I'll bet that survey doesn't exist. And it looks different depending on whether we're talking about large or small companies.
Why don't you find some links to support your claim? You've done nothing but say "industry leading" and "guarantees 100%". Your "because I said so" isn't convincing, either.
Come back in a month - I have time.
Maybe if you are such a messaging expert you would have some reasons why the majority of the industry use MQ and not WebLogic even though WebLogic is supposedly better? Because the entire world isn't IBM anymore.
I worked on a Ministry of Justice project that used WebLogic application server and its JMS queues for a critical messaging component - and at least once every two weeks the queues would go down and there would be a mad rush to get them back up - this was probably a poorly configured installation of WebLogic, and is only one example, but it left me with a pretty poor opinion of the product.That's fair. I don't know anything about the version or the admins or the servers or even you. But if that's what your experience has been, I can't question it. Maybe I can question the competence of a Ministry of Justice (which country?) that doesn't seem to train their WebLogic and server admins properly. Maybe it's an organizational problem.
I can say that we have farms of WebLogic running on Solaris servers that are very reliable. I developed one app that faces out to the Internet that uses JMS, and that app hasn't had to come down in almost three years. Reliable enough?
WebSphere and WebLogic have been neck and neck in the Java EE app server space for a long time, each controlling 35-40% of the market. I think JBOSS and Glassfish are making some inroads there. Spring is making it possible to write enterprise apps that can be deployed on servlet/JSP engines.
And all of this discussion leaves out Microsoft, .NET, and MSMQ.
I would believe that MQ series has the lion's share of the middleware/messaging market, but I'd bet that it has less to do with the clear superiority of the product and more to do with the large legacy base that IBM has out there. It's a very old mainframe/COBOL/CICS kind of technology, and the organizations that brought it in tend to be large and conservative.
You didn't ask any questions about the OP's organization. I think that ought to factor into the discussion.
Oh, and by the way more than 80% of the companies on the Fortune 100 use WebSphere MQ - maybe you should inform them how rubbish it is?And 76.273% of all statistics are made up on the spot.
I'm not interested in convincing anybody of anything. It's my opinion that if I had a Java EE app server with JMS on it that I wouldn't bring in IBM's MQ Series just for the sake of having it. If there was a legacy system that I needed to integrate with that demanded I use MQ Series there'd be no question.
But why does it seem sensible to bring in yet another moving part, another expense, another separate piece to be configured and maintained and upgraded? Applications are hard enough to develop. I wouldn't use MQ Series for its own sake, and I'd challenge anybody who brought it in because "they said so".
%

Any kind of integration experience with Weblogic JMS and Oracle AQ?

Hi,
In my company I work with java developers who believe in some kind of "holly" database independence I don't understand and as a result my life as a database developer is hell on earth.. Yesterday we again started to discuss, this time where to log, they believe database is slow and prefer logging to filesystem, after some hours finally I could convince them for some operational and reporting needs to use the database and will do this in an asyncronous way whiich they won't get slow. After all I believe the reason for a database is data, this is the place where data lives, and with the correct desing and implementation logging to database would perform better.
I love Oracle features, and know that we paid a lot for this software, so today I started investigating this promised solution. And quickly I found AQ and JMS topics in the documentation :)
After this introduction here is my problem; my company use BEA Weblogic as application server and the java guys want AQ to automatically (but of course with some delay) take their JMS log requests into database tables. Does any one have similar application experience, or any kind of integration experience with Weblogic JMS and Oracle AQ?
Any comments, references, documentation, sample code, url will be most welcomed :)
Thank you very much!
Tonguc
[email protected]
References I found upto now;
Oracle® Streams Advanced Queuing Java API Reference 10g Release 2 (10.2) http://download-uk.oracle.com/docs/cd/B19306_01/server.102/b14291/toc.htm
(Packages; javax.jms & oracle.jms)
Oracle® Streams Advanced Queuing User's Guide and Reference 10g Release 2 (10.2) http://download-uk.oracle.com/docs/cd/B19306_01/server.102/b14257/toc.htm
Part IV
Using Oracle JMS and Oracle Streams AQPart V describes how to use Oracle JMS and Oracle Streams Advanced Queuing (AQ).
Chapter 11, "Introducing Oracle JMS"
Chapter 12, "Oracle JMS Basic Operations"
Chapter 13, "Oracle JMS Point-to-Point"
Chapter 14, "Oracle JMS Publish/Subscribe"
Chapter 15, "Oracle JMS Shared Interfaces"
Chapter 16, "Oracle JMS Types Examples"
A Sample Code from Otn
http://www.oracle.com/technology/sample_code/tech/java/web_services/jmsws/NewsQueueEJB.java.html

I wouldn't go as far to say Oracle AQ is out-dated today. However, it is indeed a proprietary technology that did not found much main-stream adoption in the earlier years after its introduction. The advent of JMS made it somewhat more useful (or should I say intriguing, because more people are trying to tie it together with other J2EE technologies), but the Oracle's JMS wrapper classes in aqapi.jar were not feature complete for a long while, so using it outside Oracle's application server was painful, if not impossible. I do agree that the info at the dev2dev's JMS newsgroup or in this forum is highly fragmented, as neither Oracle nor BEA provides an official solution to integrate AQ with WebLogic, so people like us have to learn the technology through experimentation and in a piecemeal fashion.
3 years ago I was literally "playing around" - we had a polling mechanism set up to use triggers to write Oracle data changes into an event table, and had a Java-based daemon to scan that table and publish events as JMS messages to the WebLogic JMS server. This continues to work reliably till today, but I was looking for a solution that has few parts - I wanted to hook up my WebLogic MDB directly to AQ as a foreign JMS provider. Although I was able to get it to work (including XA), there were a few hoops I had to jump through, such as decompiling the Oracle AQjms classes to make them bind to the WebLogic JNDI tree.
One year after that Diptanshu Parui took what I did a giant step further - he extended the Oracle AQjms classes to allow them to be bound to the WebLogic JNDI tree naturally, and he figured out how to use WebLogic JMS messging bridge to re-send single-threaded AQ JMS messages to clustered JMS queues, which allow concurrent message assumption by multiple instances of MDB's. My impression is that he is using that setup in a production environment.
I am sure you are aware of it but I would like to make it clear - in order to use AQ as a foreign JMS provider to WebLogic-hosted MDB's, you don't need to update your database to Oracle 10g - Oracle 8i is good enough (although I recommend at least 9i Release 2). It is not the database engine, but rather the aqapi.jar JMS wrapper on top of AQ that matters. I do recommend that you use aqapi.jar from Oracle Application Server 10.0.3 or up for better XA support, among other things. Again, you don't have to replace WebLogic with Oracle AS - you only need a single jar file from it and put it in your WebLogic's classpath. However, I don't know what this means from a licensing point of view if you ever go to production - do you have to pay the full price of OracleAS or OC4J just to use the aqapi.jar?
In the coming days I will test the latest aqapi.jar to see how much progress Oracle has made in terms of making their J2EE products more spec-compliant :-).
Hope the above gives you a different perspective.
Eric

Using correlation names :new and :old in ODBC

Does anyone know how to use correlation names :new and :old through an ODBC connection?
EG:
CREATE TRIGGER Print_Cust_changes
BEFORE INSERT ON CUST_tab
FOR EACH ROW
BEGIN
dbms_output.put('Adding: ' || :new.custid);
END;
When I try to do that using ODBC, I get this error:
Server Msg: 24344, State: HY000, [Oracle][ODBC][Ora]
Trigger, procedure or function created with PL/SQL compilation error(s).
And if I try and Insert I get:
Server Msg: 4098, State: HY000, [Oracle][ODBC][Ora]
ORA-04098: trigger 'BCL.PRINT_CUST_CHANGES' is invalid and failed re-validation
The same code works perfectly in SQL*Plus.

The plot thickens...
I just tried this code:
CREATE OR REPLACE TRIGGER Print_Cust_changes
BEFORE INSERT ON CUST_tab
FOR EACH ROW
BEGIN
INSERT INTO CUST_LOG VALUES('X');
END;
And received the same error:
Server Msg: 24344, State: HY000, [Oracle][ODBC][Ora]
Trigger, procedure or function created with PL/SQL compilation error(s).
Again, using the same code (Cut & Paste) in SQL*Plus, it works without any problems.
The ODBC function being used is: SQLExecuteDirect(), ODBC driver is SQLORA32.dll v9.02.00.00
CREATE TABLE, VIEW, INDEX etc, all work fine, but not a trigger. If I read the code back from ALL_TRIGGERS after using SQL*Plus or the console application to create the trigger, it is exactly the same code...

Is there a problem with JMS and Weblogic?

          Hi,
          I am using JMS and Weblogic (Not Message Driven bean).
          My problem is that after some time my listeners disappears.
          I am sending them a message and instead of 6 listeners
          I get only 4 messages.
          So, My question is: Is there any problem working with JMS
          and Weblogic???
          Thanks,
          Tal.


Too little information and a very vague question. Need more info.
          "Tal" <[email protected]> wrote in message
          news:[email protected]..
          >
          > Hi,
          > I am using JMS and Weblogic (Not Message Driven bean).
          > My problem is that after some time my listeners disappears.
          > I am sending them a message and instead of 6 listeners
          > I get only 4 messages.
          > So, My question is: Is there any problem working with JMS
          > and Weblogic???
          > Thanks,
          > Tal.

To use JMS and JNDI in JDev 9.0.3.4

Do I need to add additional librararies in order to use JMS and JNDI along with EJB's in the enterprise application I'm creating?

No the article is not applicable for 9.0.3 I've never tested the compatibility of the 9.0.3 + Struts integration - obviously it does not work.
What does work is the ADF bindings used in 9.0.5 and above which can be safely used with newer versions of Struts.

Correlation of JMS and PI

Similar Messages

Maybe you are looking for