WLS 9.2 with TIBCO ems integration doesnt seem to be working

Question

Hi, I followed the steps provided by Tibco doc on how to integrate with WLS 8 and they worked fine with my app, the messages were getting in to the Tibco queues, but I didnt find any steps on how to integrate TIBCO with WLS 9.2.
          Still I managed to extrapolate the below steps from the WLS 9.2 JMS foreign server config instructions to have them work with TIBCO, but my App fails with errors saying... "Failed to send message using the connection..."
          Anyone has the correct working instructions to integrate TIBCO with WLS 9.2?
          ---------- In Tibco ems --------------------
          Created 2 queues:
          OrderJMSQueue
          ShippingMDBQueue
          Created 2 connection factories:
          ShippingMDBQueueCF
          OrderJMSQueueCF
          ---------- end In Tibco ems --------------------
          ---------- In WLS 9.2 server --------------------
          1. In C:\WLS92\user_projects\domains\pqedomain\bin\startweblogic.bat
          Add:
               set CLASSPATH=C:\Tibco\ems\clients\java\tibjms.jar;%CLASSPATH%
               (assuming that Tibco is installed under C:\)
          2. Start the WLS 9.2 Server
          3. Open the WLS 9.2 admin page: http://localhost:7080/console
          4. Select Services -> Messaging -> JMS Modules
          5. Click New
               a. Set Name: "jms-mod"
          6. Click on "jms-mod"
          7. Create a Resource "Foreign JMs server"
               Name: PurchasingAppJMSServer
               JNDI Initial Context Factory: com.tibco.tibjms.naming.TibjmsInitialContextFactory
               JNDI Connection URL : tibjmsnaming://localhost:7222
          8. Under PurchasingAppJMSServer
               a. Click on Destinations -> New
                    i. Name: OrderJMSQueue
                    ii. Local JNDI Name: OrderJMSQueue
                    iii. Remote JNDI Name: OrderJMSQueue
               b. Click on Save
          9. Again under PurchasingAppJMSServer
          a. Click on Destinations -> New
          i. Name: ShippingMDBQueue
          ii. Local JNDI Name: ShippingMDBQueue
          iii. Remote JNDI Name: ShippingMDBQueue
          b. Click on Save
          10. Again under PurchasingAppJMSServer
               a. Click on Connection Factories -> New
          i. Name: OrderJMSQueueCF
          ii. Local JNDI Name: OrderJMSQueueCF
          iii. Remote JNDI Name: OrderJMSQueueCF
          b. Click on Save
          11. Again under PurchasingAppJMSServer
          a. Click on Connection Factories -> New
          i. Name: ShippingMDBQueueCF
          ii. Local JNDI Name: ShippingMDBQueueCF
          iii. Remote JNDI Name: ShippingMDBQueueCF
          b. Click on Save
          12. Come up to the Home page
          13. Click on Services -> Foreign JNDI Providers
          14. Click on New
          15. Enter Name: PurchasingAppJMSServer
          16. Click Save
          17. Click on "PurchasingAppJMSServer" under the "Summary of Foreign JNDI Servers"
               a. Set Initial Context Factory: com.tibco.tibjms.naming.TibjmsInitialContextFactory
               b. Set Provider URL: tibjmsnaming://localhost:7222
               c. Set User: admin
               d. Click Save

Answer 1

I have tried this succesfully with 8.2 and 9.2. No patch was required though it is not a bad idea to apply patch.
          As mentioned above, On weblogic side, I configured:
          1) Foreign JMS Server
          2) Foreign JMS Destination
          3) Foreign JMS Connection Factory
          I did not configure foreign jms provider.
          On EMS side, I created a Queue. That's it.
          I used default connection factory in EMS (QueueConnectionFactory)
          This is how my MDB class looks like:
          import javax.jms.JMSException;
          import javax.jms.Message;
          import javax.jms.TextMessage;
          import weblogic.ejbgen.MessageDriven;
          import weblogic.ejbgen.ForeignJmsProvider;
          @MessageDriven(ejbName = "SubscriberMessageDrivenBean",
                    destinationJndiName = "subscriberNotificationQueue",
                    destinationType = "javax.jms.Queue",
                    maxBeansInFreePool = "200",
                    initialBeansInFreePool = "20",
                    transTimeoutSeconds = "180",
                    defaultTransaction = MessageDriven.DefaultTransaction.NOT_SUPPORTED
          @ForeignJmsProvider(connectionFactoryJndiName="QueueConnectionFactoryLocal")
          public class SubscriberMessageDrivenBean extends JMSInterface {     
               public void OnMessage(Message inMessage) {
          try {
               System.out.println("Reached onMessage");
          } catch (JMSException exp) {
          e.printStackTrace();
          and ejb-jar.xml like this......
          <?xml version="1.0" encoding="UTF-8"?>
          <!--
          ** This file was automatically generated by
          ** EJBGen WebLogic Server 9.2 SP1 Sun Jan 7 00:56:31 EST 2007 883308
          -->
          <ejb-jar
          xmlns="http://java.sun.com/xml/ns/j2ee"
          xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
          xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/ejb-jar_2_1.xsd"
          version="2.1">
          <enterprise-beans>
          <message-driven>
          <ejb-name>SubscriberMessageDrivenBean</ejb-name>
          <ejb-class>com.att.cpni.common.interfaces.jms.atlas.SubscriberMessageDrivenBean</ejb-class>
          <transaction-type>Container</transaction-type>
          <activation-config>
          <activation-config-property>
          <activation-config-property-name>destinationType</activation-config-property-name>
          <activation-config-property-value>javax.jms.Queue</activation-config-property-value>
          </activation-config-property>
          </activation-config>
          </message-driven>
          </enterprise-beans>
          <assembly-descriptor>
          <container-transaction>
          <method>
          <ejb-name>AccountMessageDrivenBean</ejb-name>
          <method-name>*</method-name>
          </method>
          <trans-attribute>NotSupported</trans-attribute>
          </container-transaction>
          <container-transaction>
          <method>
          <ejb-name>SubscriberMessageDrivenBean</ejb-name>
          <method-name>*</method-name>
          </method>
          <trans-attribute>NotSupported</trans-attribute>
          </container-transaction>
          </assembly-descriptor>
          </ejb-jar>
          and weblogic-ejb-jar.xml like this.......
          <?xml version="1.0" encoding="UTF-8"?>
          <!--
          ** This file was automatically generated by
          ** EJBGen WebLogic Server 9.2 SP1 Sun Jan 7 00:56:31 EST 2007 883308
          -->
          <weblogic-ejb-jar
          xmlns="http://www.bea.com/ns/weblogic/90" xmlns:j2ee="http://java.sun.com/xml/ns/j2ee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.bea.com/ns/weblogic/90 http://www.bea.com/ns/weblogic/90/weblogic-ejb-jar.xsd">
          <weblogic-enterprise-bean>
          <ejb-name>SubscriberMessageDrivenBean</ejb-name>
          <message-driven-descriptor>
          <pool>
          <max-beans-in-free-pool>200</max-beans-in-free-pool>
          <initial-beans-in-free-pool>20</initial-beans-in-free-pool>
          </pool>
          <destination-jndi-name>subscriberNotificationQueue</destination-jndi-name>
          <connection-factory-jndi-name>QueueConnectionFactoryLocal</connection-factory-jndi-name>
          </message-driven-descriptor>
          <transaction-descriptor>
          <trans-timeout-seconds>180</trans-timeout-seconds>
          </transaction-descriptor>
          </weblogic-enterprise-bean>
          </weblogic-ejb-jar>