This content has been marked as final. Show 1 reply
I don't think you have to use the messaging bridge feature to achieve your goal, although it is an alternative. Remote consumption should work between a client that is running on a newer release and a server that is running on an older release.
Is there any error message or exception on either side? You need to check the server log files. You can also turn on debugging and see if the debugging messages give any clue on what is going on.
Meanwhile there are a couple of things that you can check and try:
1. make sure that all resources (WL server, JMS server and stores) are uniquely named cross the two domains
2. if the resources are secure, make sure the security configuration of the SOA component is correct
3. make sure that you consumer component is up running before your producer sends any messages unless you are using durable subscribers
4. you can run the same application on two domains that both run the same WL release and see if the behavior is different.
The following link contains information about the messaging bridge in case you would like to know it better.