TIBCO EMS & JBoss problem

Hai,
I have configured my jms in jboss with TIBCO EMS. i am able to send Queue messages from client. but my message driven bean is not able to receive the queue.
I found the following error message in Jboss log
Cannot instantiate class: com.tibco.tibjms.naming.TibjmsInitialContextFactory
Why it happens please give me a solution
Thanks in advance

First port of call would be to make sure your tibjms.jar is in your classpath; I've seen this instead of 'class not found' errors a couple of times now.

Similar Messages

TIBCO EMS + JBOSS

Dear All,
I would like some suggestions regarding tracing a bug while using TIBCO EMS as a JMS Provider in JBoss4.0.4 AS.
The requirement is like this -
I have to put a message into a TIBCO EMS REQUEST queue.
This message is processed by another system
A reply message is put into the TIBCO EMS REPLY queue.
I have to receive this message from this queue.
There is a constraint that I require the same request object for another operation based on the success/failure of the first call. In both the cases, I will get back a valid reply using which I will determine if it is a success or failure. Hence I am not using an MDB, instead, I am using a QueueReceiver.
I could succesfully put a message into the queue, but, could not receive the message from the REPLY queue though EAI put it into that queue. Using a queue monitoring tool, I can see that the reply is there, but cannot receive it.
It gets stuck at receiver.receive();
It continuously listens to the queue. We can rule out any mismatches with JMSCorrelationId because it is fine.
What is surprising is the same code worked perfectly fine until yesterday for more than one month now. And still it works fine if the ear file is deployed in the JBoss server of another machine.
I have not made any changes to my notebook either software or hardware...
Any ideas/thoughts? If attaching the code sample would help, I shall do so. Pls let me know.
Best Regards,
murali

First port of call would be to make sure your tibjms.jar is in your classpath; I've seen this instead of 'class not found' errors a couple of times now.

Problems connecting to Tibco EMS JMS

Hi,
We're planning to migrate from Tibco to PI as middleware. We're setting up to Proof of Concept on our PI machine to the Tibco EMS JMS server (decision is to keep using this JMS server).
We're having connection issues. We tested the parameters in a test application on the PI server so we know two things for sure:
- The parameters are correct
- The connection is possible (no firewall limitations, etc.)
The drivers were also uploaded succesfully, we're connecting to a Tibco EMS 4.4.3.
This is the status in the CC:
Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: No transition found from state: ERROR, on event: process_commence for DFA: CC_JMS_Receiver:6460987290a33b73bd1249cec1882d06
Also:
- This JMS Connection needs to work via JNDI, therefore we checked note 1099720 but the CC initialization fails.
- The TIBCO drivers are installed on the SAP PI system.
Any help is appreciated for this critical proof of concept!
Kr,
Frederik-Jan.

Yes, we uploaded less drivers, the problem is that we couldn't upload everything, only a couple of the drivers in the package supplied to us by Tibco (otherwise you overwrite the standard functions of PI and then it dumps ...).
Try poking around and removing all the non vendor specific jars.
Kr,
FJ.

Problem with SDA Deployment for JMS drivers for Tibco EMS

Hi,
I was trying to deploy the latest JMS driver files for TIBCO EMS 6.0.1.
I have followed all the procedure that was given in the note 1138877 and also referred the following article
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/00b4a020-4ae6-2c10-5a95-fed4ad9a4b60?quicklink=index&overridelayout=true and followed the step given in that.
But got the following error
Details Message(s):
Messages for component sap.com/com.sap.aii.adapter.lib:
Deployment of archive /usr/SAP/trans/<XID>/EPS/in/..>/com.sap.aii.adapter.lib.sda for component sap.com/com.sap.aii.adapter.lib aborted
Detailed Message : 1. Required file [tibcrypt.jar] not found in SDA [/usr/SAP/trans/<XID>/EPS/in/..>/com.sap.aii.adapter.lib.sda]
See Deploy controller log
/user/sap/<XID>/DVEBMGS11/j2ee/JSPM/log/log_2011_05_17_14_59_17/deploy_2011-05-17_16-01-45.log for details
As per the error message it is mentioning about a missing jar file, but I have added all the required jar file in the sda and updated the same in the provider.xml.
So just wanted to make sure if I have missed anything.
Other thing what i wanted to mention here is, while adding the jar file to the default com.sap.aii.adapter.lib.sda file, there was a jar file named "com.sap.aii.adapter.lib_api.jar", I deleted this and added the updated Jar files for the EMS 6.0.1 drivers, Is this correct or do we need to have this com.sap.aii.adapter.lib_api.jar file as well in addition to the required driver files.
Please let me know your thoughts and if I have missed anything.
Thanks for the help
Regards

Selvam,
It was long time before I did.. I guess I did added com.sap.aii.adapter.lib_api.jar file as well in addition to the required driver files.
Cheers
Agasthuri

QUESTION Re. Integrating TIBCO EMS with Weblogic 8.1 using MDB

Hi All,
          I am trying to integrate TIBCO EMS 4.3.0 with Weblogic 8.1 SP6.
          I have created a topic "SIMPLE.TOPIC" on the EMS. I have configured the Foreign JMS Server as follows:
          Name: TIBCO JMSServer
          JNDI Initial Context Factory:com.tibco.tibjms.naming.TibjmsInitialContextFactory
          JNDI Connection URL:tibjmsnaming://emshost:emsport
          I have configured the connection factory as follows:
          Name: TIBCO JMSTopicConnectionFactory
          Local JNDI Name: TopicConnectionFactory.Local
          Remote JNDI Name:TopicConnectionFactory
          User Name:username to connect to EMS server
          Password::pssword to connect to EMS server
          My JMS destination is configured as follows:
          Name: Tibco JMS Destination
          Local JNDI Name:SIMPLE.TOPIC.LOCAL
          Remote JNDI Name:SIMPLE.TOPIC
          My weblogic-ejb-jar.xml consists of the following code:
                    <weblogic-ejb-jar>
            <weblogic-enterprise-bean>
              <ejb-name>SimpleTopicListener</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>SIMPLE.TOPIC</destination-jndi-name>
               <connection-factory-jndi-name>TopicConnectionFactory</connection-factory-jndi-name>
              </message-driven-descriptor>
              <enable-call-by-reference>True</enable-call-by-reference>
            </weblogic-enterprise-bean>
          </weblogic-ejb-jar>
                              The problem is, when I try to deploy this mdb, I get the following error:
          The Message-Driven EJB attempted to connect to the JMS destination with the JNDI name: SIMPLE.TOPIC. However, the object with the JNDI name: SIMPLE.TOPIC is not a JMS destination, or the destination found was of the wrong type (Topic or Queue).
          I have checked and double checked to make sure that the topic SIMPLE.TOPIC does exist on the EMS server.
          Does anyone know what is the issue here and how to resolve it?
          Many thanks!
          -Kinshuk
          Edited by kinshukk at 05/14/2007 8:35 AM

(1) Check the standard ejb jar and make sure you've specified a topic destination type (the default is queue). For details, you can reference the WebLogic 9.0 MDB developer guide (the MDB dev guide was revised in 9.0 to include more detail than the 8.1 guide). Also, you might want to take a look at our integration/interop FAQ (again for 9.0 or later).
          (2) Change the weblogic-ejb-jar to reference the foreign local JNDI names - not the remote JNDI names.
          (3) Be careful about using the "." and "/" characters in local JNDI names - these have side-effects in JNDI (they force creation of subcontexts).
          Tom

How to connect SAP XI engine with TIBCO EMS

Hi,
how can I connect SAP XI 3.0 with TIBCO EMS?
If i'm going to use XI provider, Do I need to deply any jar files into XI?
Thanks in advance.

HI,
At this moment I've deployed the TIBCO libraries into my XI and I've created an XI adapter in order to connect with TIBCO system as folows:
Transport protocol                                                  Access JMS Provider Generically
JMS.queue ConnectionFactoryImpl.classname      com.tibco.tibjms.tibjmsQueueConnectionFactory
JMS.QueueConnectionFactoryImpl.constructor     java.lang.String https://hostname:port
JMS.QueueImpl.classname                                     com.tibco.tibjms.tibjmsQueue
JMS.QueueImpl.constructor                                    java.lang.string TibcoQueueName
SecuritySSLOn                                                       True
SecurityKeyName                                                   Name
JMS Settings
JMS Queue User                                                    User
JMS Queue Password                                          UserPassword
I don't know where is the problem, but all the times I've obtained the same error:
MP: Exception caught with cause com.sap.aii.af.ra.ms.api.RecoverableException: No transition found from state: STARTING, on event: process_commence for DFA: JMS_TIBCO_ADAPTER
Thanks in advance.

WLS 9.2 with TIBCO ems integration doesnt seem to be working

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

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"?>
          
          <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"?>
          
          <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>

JMS adapter could not receive message from Tibco EMS topic

I'm trying to consume message from tibco EMS topic using Oracle SOA JMS adapter. Can anyone please let me know the steps to do this. Appreciate your help.
Thanks,
SB

Increase Log level for cube.activation to debug and check the logs by stopping & starting the activation agent(I mean Retire and activate the process) .. It should give a clue on what's happening..

Accessing Tibco-EMS queue from XI(using JMS adapter)

Hi All,
I am currently working on a Tibco Integration scenario with XI thru JMS(Sender) adapter. I have gone through some of our SDN forum threads and come to know that we have to deploy some TIBCO specific jar files to the fetch data from TIBCO-EMS queues. But still have the following query on
1. what are all the JAR files(TIBCO JMS libraries) needed to be installed in SAP J2EE engine? I have got the following JAR files from TIBCO guys...
tibcrypt.jar
tibjms.jar
tibjmsadmin.jar
tibjmsapps.jar
tibrvjms.jar
regards,
Raks

Hi Raks,
Check this note for JNDI configuration..
802754
"If a 3rd party JMS provider should be used then usually the "Name of JNDI initial context factory" must be adjusted. I.e. com.sap.engine.services.jndi.InitialContextFactoryImpl must be replaced by some.other.vendor.jms.jndi.InitialContextFactory In addition it is necessary to deploy the jar that contains the some.other.vendor.jms.jndi.InitialContextFactory with the aii_af_jmsproviderlib.sda SDA file. In addition, you must extend the server/provider.xml deployment descriptor in the relevant way. Refer to Chapter 11 of the XI 3.0 Configuration Guide for more information"
You need to find out class "Name of JNDI initial context factory" for tibco as mentoned in the note and deploy the corresponding JAR file.
Also check this link for JNDI configuration parameters in the JMs adapter..
http://help.sap.com/saphelp_nw04/helpdata/en/c1/739c4186c2a409e10000000a155106/content.htm
Regards
Anand

How to setup Tibco EMS as the JMS Provider

Hi,
Are there anyone know how to setup the app. server to use Tibco EMS (installed in a remote machine) as the JMS service? May I have the setup example?
I put the host name and port of the EMS server on the Configuration JMS page. I ping the setting but I got the following:
An error has occurred.
Operation 'JMSPing' failed in 'resources' Config Mbean. Target exception message: [C4003]: Error occurred on connection creation [10.0.0.104:7222]. - cause: java.lang.NumberFormatException: For input string: "�"Any idea?
Thanks a lot for your help in advance.
Simon

Hi,
Are there anyone know how to setup the app. server to
use Tibco EMS (installed in a remote machine) as the
JMS service? May I have the setup example?The default jms commands [like jms-ping] are designed to be used against Sun Java System Message Queue that is bundled with the appserver. For integrating third party JMS providers like Tibco EMS, could you try out Generic RA for JMS [http://genericjmsra.dev.java.net]
Detailed instructions on getting Sun Java System Application Server to work with Tibco EMS using Generic RA for JMS is available off
https://genericjmsra.dev.java.net/docs/tibco-genericjmsra-integration-sample-doc/Integrating_Sun_Java_System_Application_Server_with_Tibco_JMS_using_the_Generic_Resource_Adapter_for_JMS.html
Thanks
--Siva.

Calling Tibco EMS through Weblogic

We're POCing Oracle SOA as a replacement for Tibco at our company, however, until we fully replace our tibco architecture, for reusabilities sake we want to be able to call tibco ems from applications hosted on weblogic.
So far, we've been unable to get any of our calls to EMS to succeed, as we're missing some unknown, critical peice of understanding required to use the service properly.
Here is what we know works:
We can deploy applications that make successful database calls using the database adapter in JDeveloper.
JDeveloper can see exposed queues on weblogic using the JMS Adapter wizard.
In the console/JNDI tree we can confirm that weblogic can connect to tibco by configuring weblogic through either the /Console/Services/Foreign JNDI Providers or /Console/Services/Messaging/JMS Modules/SomeModules/SomeForeignServer/Destinations
However, we have no idea how to get the Queues in the JNDI tree to apear in the JMS Adapter Wizard in JDeveloper, neither do we know how to get those queues to actually call Tibco, so we can forward calls to Weblogic to Tibco where appropriate.
Any clues at all would be awesomely amazing.
Thanks,
Daniel

Using TIBCO EMS or WebLogic JMS is essentially the same in a SOA Composite application. In both cases, the key step is to configure a new EIS connection resource in the Oracle JMS Adapter. This step is performed in EM Fusion Middleware Control (or scripted using WLST). It's the EIS connection resource that physically points to your TIBCO EMS server endpoints and a specific TIBCO EMS connection factory. Of course, when using TIBCO EMS, you also have to drop tibems.jar into your WebLogic $DOMAIN_HOME/lib directory and restart.
There's a couple variants of how to point the JMS Adapter at TIBCO (so-called direct and indirect) -- tcp:// and tibjmsnaming:// respectively. The latter is better architecturally since you are using TIBCO's JNDI services rather than bypassing them. Examples for TIBCO EIS connection definitions are in the JCA Technical Adapter section of the Fusion Middleware documentation.
From a SOA developer's point of view, their JMS service or reference definition is not provider-specific. The developer points to the JNDI name of the created JMS Adapter EIS connection, and specifies the destination (queue or topic) JNDI name. Remember, with TIBCO EMS, that destination name is TIBCO's JNDI name, not a local WebLogic JNDI name. (Caveat is that you can mash up WebLogic Foreign Server definition with EIS Connection Pool definition - I don't recommend this-- and in that case, the developer is using the local JNDI alias for the "foreign" TIBCO destination).
JDeveloper:
As you noticed, JDeveloper provides a wizard-assist to the developer for selecting a destination (queue or topic) only if the provider is WebLogic JMS or Oracle AQ. If it is a third-party provider, then there is no look-up. The developer just types the correct 3rd-party destination name (hopefully) value in.
Hope this helps. My company uses SOA Suite with both WebLogic JMS and TIBCO EMS.
Todd

ReplyTo is null while forwarding the messages from TIBCO EMS to Weblogic

I have created bridge between TIBCO queue and WL (version 10.3) queue.
And sent message on TIBCO queue with ReplyTo queue value set. Text Message is passed successfully to WL queue but replyTo is null.
All other header values like messageID, correlationID, priority are received correctly.
Any Idea?

Hi,
Check this Doc Id.
How to Configure Weblogic Server with TibCO EMS Server (Doc ID 1343314.1)
regards,
Kal

How to connect tibco ems with sap xi engine?

hi friends,
how to connect tibco ems with sap xi engine?
plz explain me in brief. if possible plz give some link.
thanks & regards
Ruban

Hi Ruban
refr this links
Re: XI 3.0 - Tibco integration
<b>IBCO -> XI SCENARIO -> Web Service</b>
http://dev.systinet.com/doc/ssc-60/primer/html/using.web.services.html
http://www.estrategy.gov/presentations/umd_e-gov_ent_arch/sld015.htm
General disadvantages of using web service
http://www.samspublishing.com/articles/article.asp?p=31555&rl=1
http://www.omg.org/news/whitepapers/CORBA_vs_SOAP1.pdf
Replace TIBCO with XI
Tibco & XI
XI integration with Tibco
<b>
Aslo see the below links</b>
XI Vs Tibco Vs Webmethods
Re: Why XI ??
Differences between Tibco BW and how to do canonical mapping in XI
http://www.sap.com/solutions/netweaver/pdf/BWP_SB_ExchangeInfrastructure.pdf
XI integration with PSFT/Seibel ?
Performance statistics of SAP XI
/thread/154189 [original link is broken]
publish subscribe with XI
XI in SRM, CRM, MDM
XI implementation - xi implementation
Thanks!!

SSIS to Tibco EMS messaging

Is there a way to have SSIS communicate with Tibco EMS.
i.e. write messages to an EMS queue and read messages to an EMS queue

Josh Ash appears to imply that Tibco has a .Net API.
Regardless, you can use COM DLLs in .Net.
Talk to me now on

Integrate Weblogic 11gR1 with Tibco EMS

Hi,
Is there a how-to guide on how to configure Tibco EMS as a JMS foreign server in WLS 11g? Do I need to use Tibco connection factory as JNDI context factory?
Thanks a lot for your help,
Jane

There's no Tibco specific how-to-guide that I'm aware of -- Tibco integrates using the same facilities that are used for other vendors. See the "JMS interop FAQ" in the edocs.
Tom

TIBCO EMS & JBoss problem

Similar Messages

Maybe you are looking for