9iAs / 10 g cmopatibility with TIBCO JMS 4.0.1

Is it possible to integrate Tibco JMS server with Oracle 9i Application Server? Has anyone tried integrating third party JMS servers with oracle 9i Application server, TIBCO JMS in particular.
Compatibility information for the following are required:
a) Oracle 9i Application server Or Oracle 10g application server
b) TIBCO Enterprise Messaging Service (JMS) 4.0.1
c) Platform : Sun unix Machines

Dear gurus,
i have solved my problem, i re-run ssoreg.sh and re-configure mod_osso.conf, now it's working.
Regards

Similar Messages

Deploying MDB on WebLogic server 8.1 (SP2) with Tibco JMS

Hi,
 I am currently facing problems to deploy and run my MDB on weblogic connecting it to Tibco JMS as the foreign jms server.
 
 My ejb-jar.xml:
 
 <message-driven>
 <ejb-name>DeAMMsgFactors</ejb-name>
 <ejb-class>com.db.deam.mdb.DeAMMsgFactors</ejb-class>
 <transaction-type>Container</transaction-type>
 <message-driven-destination>
 <destination-type>javax.jms.Topic</destination-type>
 </message-driven-destination>
 </message-driven>
 </enterprise-beans>
 <assembly-descriptor>
 <security-role>
 <role-name>soiadmin</role-name>
 </security-role>
 </assembly-descriptor>
 
 weblogic-ejb-jar.xml:
 
 <weblogic-enterprise-bean>
 <ejb-name>DeAMMsgFactors</ejb-name>
 <message-driven-descriptor>
 <pool>
 <max-beans-in-free-pool>20</max-beans-in-free-pool>
 <initial-beans-in-free-pool>10</initial-beans-in-free-pool>
 </pool>
 <destination-jndi-name>WLFactorsTopic</destination-jndi-name>
 <connection-factory-jndi-name>WLFactorsCF</connection-factory-jndi-name>
 <jms-polling-interval-seconds>10</jms-polling-interval-seconds>
 </message-driven-descriptor>
 <transaction-descriptor>
 <trans-timeout-seconds>100000</trans-timeout-seconds>
 </transaction-descriptor>
 </weblogic-enterprise-bean>
 <security-role-assignment>
 <role-name>soiadmin</role-name>
 <principal-name>jmsusername</principal-name>
 </security-role-assignment>
 
 Error:
 weblogic.ejb20.WLDeploymentException: [EJB:011014]The Message-Driven EJB failed while creating a JMS Connection. The err
 or was:
 javax.jms.JMSSecurityException: invalid name or password.
 javax.jms.JMSSecurityException: invalid name or password
 at com.tibco.tibjms.Tibjmsx.buildException(Tibjmsx.java:395)
 at com.tibco.tibjms.TibjmsConnection._create(TibjmsConnection.java:581)
 at com.tibco.tibjms.TibjmsConnection.<init>(TibjmsConnection.java:1743)
 at com.tibco.tibjms.TibjmsTopicConnection.<init>(TibjmsTopicConnection.java:35)
 at com.tibco.tibjms.TibjmsxCFImpl._createImpl(TibjmsxCFImpl.java:92)
 at com.tibco.tibjms.TibjmsxCFImpl._createConnection(TibjmsxCFImpl.java:121)
 at com.tibco.tibjms.TibjmsTopicConnectionFactory.createTopicConnection(TibjmsTopicConnectionFactory.java:66)
 at weblogic.ejb20.internal.JMSConnectionPoller.getConnection(JMSConnectionPoller.java:607)
 at weblogic.ejb20.internal.JMSConnectionPoller.createJMSConnection(JMSConnectionPoller.java:1783)
 at weblogic.ejb20.internal.JMSConnectionPoller.connectToJMS(JMSConnectionPoller.java:1087)
 at weblogic.ejb20.internal.JMSConnectionPoller.trigger(JMSConnectionPoller.java:970)
 at weblogic.time.common.internal.ScheduledTrigger.run(ScheduledTrigger.java:243)
 at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
 at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
 at weblogic.time.common.internal.ScheduledTrigger.executeLocally(ScheduledTrigger.java:229)
 at weblogic.time.common.internal.ScheduledTrigger.execute(ScheduledTrigger.java:223)
 at weblogic.time.server.ScheduledTrigger.execute(ScheduledTrigger.java:50)
 at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
 at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
 at weblogic.ejb20.internal.JMSConnectionPoller.getConnection(JMSConnectionPoller.java:638)
 at weblogic.ejb20.internal.JMSConnectionPoller.createJMSConnection(JMSConnectionPoller.java:1783)
 at weblogic.ejb20.internal.JMSConnectionPoller.connectToJMS(JMSConnectionPoller.java:1087)
 at weblogic.ejb20.internal.JMSConnectionPoller.trigger(JMSConnectionPoller.java:970)
 at weblogic.time.common.internal.ScheduledTrigger.run(ScheduledTrigger.java:243)
 at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
 at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
 at weblogic.time.common.internal.ScheduledTrigger.executeLocally(ScheduledTrigger.java:229)
 at weblogic.time.common.internal.ScheduledTrigger.execute(ScheduledTrigger.java:223)
 at weblogic.time.server.ScheduledTrigger.execute(ScheduledTrigger.java:50)
 at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
 at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
 [JMSConnectionPoller] : ** Connect attempt for: WLFactorsTopic was: unsuccessful
 
 Any help would be appreciated.
 
 Thanks, 
 Kiran Kumar MV.

I was able to use MDB to receive msg from a Tibco JMS queue. This is what you have to do: using WL console,
 - set up a foreign JMS Server. Make sure you specify the following correctly: jndi initial context factory (tibjms class), tibjms server url, username/password
 - create a foreign connection factory (if you are using CMT, make sure you create a XA compliant connection factory in Tibco JMS server). It seems that you have to specify URL again when creating XA connection factory in Tibjms.
 - create a foreign destination (queue/topic)
 In ejb-jar.xml and weblogic-ejb-jar.xml,
 - use resource-ref (wrapper) to specify the foreign connection factory
 - use resource-env-ref to specify the foreign destination.
 - In MDB ejb-jar.xml, specify destination-jndi-name and connection-factory-jndi-name.
 See Message Driven Beans chapter in Programming WebLogic EJB doc.
 Good luck.

How to Configure and Use Oracle's JMS Connector with Tibco EMS

Jeff,
I am getting the below exception while try to do the deployment of the sample provided on 'How to Configure and Use Oracle's JMS Connector with Tibco Enterprise for JMS'
While deployment not able to get the 'TibcoJMSReference',
As I understand in the 'orion-application.xml for the below, unable to get the instance. Could you adivce how I can enable the trace more?
<resource-provider class="com.evermind.server.deployment.ContextScanningResourceProvider" name="TibcoJMSReference">
could you help to resolve the issue?
Error
Operation failed with error: No resource named 'TibcoJMSReference/TibcoXACF'found

Hi,
I'm also looking for the same 'Configure and Use Oracle's JMS Connector with Tibco JMS to consume message'. If you have already implemented and working fine, please let me know the steps and some documents.

How to Integrate Oracle 10g with TIBCO Enterprise for JMS

Will it be possible to provide a document that will instruct on how to integrate oracle10g with TIBCO Enterprise for JMS
I needed to Integrate oracle 10g with TIBCO Enterprise for JMS.
When i searched on internet about how to do it, i found a document on oracle's site which has instructions (in the HOW-TO section) related to integration with OC4J (and not Oracle 10g)
I have been successfully able to integrate OC4J developer preview edition 10.1.3 with TIBCO enterprise for JMS.
when i tried with the same instructions to integrate oracle 10g with TIBCO Enterprise for JMS, i could not succeed. The i understood that the standalone OC4J is different from the embedded OC4J in Oracle 10g
Will it be possible to provide a document that will instruct on how to integrate oracle10g with TIBCO Enterprise for JMS
Your help will be really appreciated
Thanks,

There are how-to documents here: http://www.oracle.com/technology/tech/java/oc4j/1013/how_to/index.html#JMS
with separate instructions for:
IBM WebSphere MQ JMS
Tibco Enterprise for JMS
SonicMQ JMS

How to Configure and Use Oracle's JMS Connector with Tibco Enterprise

Following the advice here: http://www.oracle.com/technology/tech/java/oc4j/1013/how_to/how-to-connect-to-tibco/doc/how-to-connect-to-tibco.html
I believe I need to provide a username and password for the Tibco JMS provider, and would like to know the correct way. Is this right, in orion-application.xml
 <resource-provider class="com.evermind.server.deployment.ContextScanningResourceProvider" name="TibcoJMSReference">
 <property
 name="java.naming.factory.initial"
 value="com.tibco.tibjms.naming.TibjmsInitialContextFactory">
 </property>
 <property
 name="java.naming.provider.url"
 value="tibjmsnaming://jleinawe-sun:7222">
 </property>
<property name="java.naming.security.principal" value="user" />
<property name="java.naming.security.credentials" value="password" />
 </resource-provider>

This is kind of up to Tibco...
When you add properties to the resource-provider element, you are just adding entries to a Map which gets passed to the initial context factory, which in this case is implemented by Tibco (TibjmsInitialContextFactory), so you may want to check their docs.
It's possible they only use that for username/password for JNDI access purposes and not for JMS. If so, you can explicitly set username/password for outbound connections in the oc4j-ra.xml file, and using ResUser/ResPassword in the MDB's activation-spec to set username/password for inbound connections.
-Jeff

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>

MDB with foreign JMS : WLS 9.23

For the love of _____ (fill in your own muse of desperation here), is there some categorical statement of whether WLS9.23 actually ***works*** with MDB's and foreign JMS providers? Whereever I search/find, people have trouble with this.
          Some kind BEA sould - please. Please, please please : publish a canonical example of MDB with secured foreign-JNDI provided connx factory, and either a queue or a topic.
          I'm beginning to wonder if this works at all.

Good morning!
          Categorical Statement: WLS supports JMS spec compliant foreign providers for MDBs, bridges, resource-references, foreign providers. We also support sending a foreign providers message using a WebLogic JMS client.
          For general Tibco integration questions, I recall that the Tibco docs themselves contain WebLogic integration examples. There's also some much mention of Tibco in the out-dated "Using Foreign JMS Providers with WebLogic Server" white-paper on dev2dev.
          That said, there have been definitely been problems with Tibco and MQ's latest release, as they both recently released semi-non-JMS compliant clients that our wrapper code was unprepared to deal with. In short, we were caught unawares when these clients stopped supporting the 1.0.2 APIs even though 1.1 specification clearly requires both 1.1 and 1.0.2 support. Rather than ask Tibco and MQ teams to have them patch their code (an approach we've sometimes taken over the years), we chose this time to enhance our code.
          I think the problems were all fixed by 9.23 - but you may want to contact customer support to see if there are any additional patches required. Alternatively, you can try use a slightly older Tibco client, as presumably their older clients are still able to interoperate with their latest server version (this approach works with MQ).
          Tom

Need help to connect tibco jms queues from OSB

Hi,
We have a requirement in our project "to connect tibco JMS Queues from OSB".
The Queres are created by some othes in remote system, they provided us the details to connect the Queue. the detail are:
Queue Name :EXT_WEALTHHUB.TO_EXT.SYNC.REQ
Jndi Factory :SSLQueueConnectionFactory
and hostName , PORT
Credentails are provided.
We entered the same details in Business service in transport page by choosing 'jms' as protocol and EndpointURI as.
"jms://100.10.XX.YY:1234/SSLQueueConnectionFactory/EXT_WEALTHHUB.TO_EXT.SYNC.REQ"
And we created a service account to maintain the credentials and browsed the same at service account in the business service.
In JMS Transport Page we selected
Response Queue : One for all Request URI's
Response Pattern : JMS CorrelaltionID
Response UI :jms://100.10.XX.YY:1234/SSLQueueConnectionFactory/EXT_WEALTHHUB.TO_EXT.SYNC.RESP
when we are trying to establish a connection with the above queue getting
javax.naming.CommunicationException [Root exception is weblogic.socket.UnrecoverableConnectException: [Login failed for an unknown reason: er.deployer.MessageDrivenBeanInfoImpl.getInitialContext(MessageDrivenBeanInfoImpl.java:733)
 at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl.getInitialContext(MessageDrivenBeanInfoImpl.java:689)
 at weblogic.jms.common.CDS$DD2Listener$1.run(CDS.java:1018)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
 at weblogic.jms.common.CrossDomainSecurityManager.runAs(CrossDomainSecurityManager.java:130)
 at weblogic.jms.common.CDS$DD2Listener.getInitialContextFromListener(CDS.java:1012)
 at weblogic.jms.common.CDS$DD2Listener.getInitialContext(CDS.java:984)
 at weblogic.jms.common.CDS$1.run(CDS.java:436)
 at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
 at weblogic.jms.common.CrossDomainSecurityManager.runAs(CrossDomainSecurityManager.java:130)
 at weblogic.jms.common.CDS.createInitialContext(CDS.java:431)
 at weblogic.jms.common.CDS.getDDMembershipInformation(CDS.java:270)
 at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl.createMDManagers(MessageDrivenBeanInfoImpl.java:1455)
 at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl.activate(MessageDrivenBeanInfoImpl.java:1252)
 at weblogic.ejb.container.deployer.EJBDeployer.activate(EJBDeployer.java:1320)
 at weblogic.ejb.container.deployer.EJBModule.activate(EJBModule.java:493)
 at weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:227)
 at weblogic.application.internal.flow.DeploymentCallbackFlow$2.next(DeploymentCallbackFlow.java:531)
 at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
 at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:165)
 at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:157)
 at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:1267)
 at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
 at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:409)
 at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:58)
 at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
 at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
 at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569)
 at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:150)
 at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:116)
 at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323)
 at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:844)
 at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1253)
 at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:440)
 at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:163)
 at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
 at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:13)
 at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:68)
 at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
 at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
 at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused by: weblogic.socket.UnrecoverableConnectException: [Login failed for an unknown reason: in.checkLoginSuccess(Login.java:131)
 at weblogic.rjvm.t3.MuxableSocketT3.connect(MuxableSocketT3.java:403)
 at weblogic.rjvm.t3.ConnectionFactoryT3.createConnection(ConnectionFactoryT3.java:34)
 at weblogic.rjvm.ConnectionManager.createConnection(ConnectionManager.java:1777)
 at weblogic.rjvm.ConnectionManager.findOrCreateConnection(ConnectionManager.java:1417)
 at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:437)
 at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:316)
 at weblogic.rjvm.RJVMManager.findOrCreateRemoteInternal(RJVMManager.java:254)
 at weblogic.rjvm.RJVMManager.findOrCreate(RJVMManager.java:197)
 at weblogic.rjvm.RJVMFinder.findOrCreateRemoteServer(RJVMFinder.java:238)
 at weblogic.rjvm.RJVMFinder.findOrCreateInternal(RJVMFinder.java:200)
 at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:170)
 at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:153)
 at weblogic.jndi.WLInitialContextFactoryDelegate$1.run(WLInitialContextFactoryDelegate.java:345)
 at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
 at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
 at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:340)
 at weblogic.jndi.Environment.getContext(Environment.java:315)
 at weblogic.jndi.Environment.getContext(Environment.java:285)
 at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:117)
 at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
 at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
 at javax.naming.InitialContext.init(InitialContext.java:223)
 at javax.naming.InitialContext.<init>(InitialContext.java:198)
 at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl$2.run(MessageDrivenBeanInfoImpl.java:748)
 at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
 at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl.doPrivilagedAction(MessageDrivenBeanInfoImpl.java:2238)
 at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl.getInitialContext(MessageDrivenBeanInfoImpl.java:733)
 at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl.getInitialContext(MessageDrivenBeanInfoImpl.java:689)
 at weblogic.jms.common.CDS$DD2Listener$1.run(CDS.java:1018)
 at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
 at weblogic.jms.common.CrossDomainSecurityManager.runAs(CrossDomainSecurityManager.java:130)
 at weblogic.jms.common.CDS$DD2Listener.getInitialContextFromListener(CDS.java:1012)
 at weblogic.jms.common.CDS$DD2Listener.getInitialContext(CDS.java:984)
 at weblogic.jms.common.CDS$1.run(CDS.java:436)
 at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
 at weblogic.jms.common.CrossDomainSecurityManager.runAs(CrossDomainSecurityManager.java:130)
 at weblogic.jms.common.CDS.createInitialContext(CDS.java:431)
 at weblogic.jms.common.CDS.getDDMembershipInformation(CDS.java:270)
 at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl.createMDManagers(MessageDrivenBeanInfoImpl.java:1455)
 at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl.activate(MessageDrivenBeanInfoImpl.java:1252)
 at weblogic.ejb.container.deployer.EJBDeployer.activate(EJBDeployer.java:1320)
 at weblogic.ejb.container.deployer.EJBModule.activate(EJBModule.java:493)
 at weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:227)
 at weblogic.application.internal.flow.DeploymentCallbackFlow$2.next(DeploymentCallbackFlow.java:532)
 at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
 at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:165)
 at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:158)
 at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:1269)
 at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
 at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:409)
 at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:58)
 at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
 at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
 at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569)
 at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:150)
 at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:116)
 at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323)
 at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:844)
 at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1253)
 at weblogic.deploy.internal.targetserver.DeploymentM
Any pointers on how to resolve the above issue will be a greate help to us.
Thanks in Advance

Wrong forum, please ask this on dedicated weblogic or soa forums

Setting the JMS client-id on a Tibco JMS server

Dear,
We're running quite a bit of interfaces that connect to a Tibco JMS server.
The Tibco team is suggesting we use client-id's to identify ourselves as the consumer of a particular queue. However I fail to find the parameters I require to send the client-id with my call in the JMS Sender/Receiver Adapter .
Has anyone had any experience with this?
Kr,
Frederik-Jan.

Dear,
I don't see how this is relevant to connecting
- From PI
- To Tibco EMS
I don't need a tool for viewing a queue. When I view the queue, I see that the client-id is left empty. What I need is a parameter/setting for my adapter/communication channel so that I can set the client-id.
Kr,
Frederik-Jan.

MDB on Tibco JMS Queue

Hy, I'm writing about a technical problem with BeaWebLogicServer 6.1 sp5.
I've a MessageDrivenBean in the BeaWebLogic Container that must be connected to
a remote Tibco JMS queue.
When the remote Tibco queue is not protected by a password this works fine (my
MDB receives the message from Tibco queue), instead if the remote queue is password
protected, i've this Bea Weblogic server error log:
<Jun 18, 2004 3:06:06 PM CEST> <Warning> <EJB> <The Message-Driven EJB: BuyResponseConsumer
is unable to connect to the JMS destination: TELECOMIT.IPBILLING.SVIL.PI.PORTALE.ORDER.BUYRESP.
Connection failed after 850 attempts. The MDB will attempt to reconnect every
10 seconds, this log message will repeat every 600 seconds until the condition
clears.>
How may I resolve this problem?
These are my xml descriptors:
EJB-JAR.XML:
<!DOCTYPE ejb-jar PUBLIC "-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans
2.0//EN" "http://java.sun.com/dtd/ejb-jar_2_0.dtd">
<ejb-jar>
<enterprise-beans>
<message-driven>
<ejb-name>BuyResponseConsumer</ejb-name> <ejb-class>it.telecomitalia.wonderland.ipbilling.buyresponse.BuyResponseConsumer</ejb-class>
<transaction-type>Container</transaction-type> <acknowledge-mode>auto-acknowledge</acknowledge-mode>
<message-driven-destination> <destination-type>javax.jms.Queue</destination-type>
</message-driven-destination>
<security-identity>
<use-caller-identity id="XXXXX" />
</security-identity>
</message-driven>
</enterprise-beans>
<assembly-descriptor>
<security-role>
<role-name>XXXXX</role-name>
</security-role>
</assembly-descriptor>
</ejb-jar>
WEBLOGIC-EJB-JAR.XML
<?xml version="1.0"?> <!DOCTYPE weblogic-ejb-jar PUBLIC "-//BEA Systems, Inc.//DTD
WebLogic 6.0.0 EJB//EN" "http://www.bea.com/servers/wls600/dtd/weblogic-ejb-jar.dtd">
<weblogic-ejb-jar>
<weblogic-enterprise-bean> <ejb-name>BuyResponseConsumer</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>REMOTE-MESSAGE-QUEUE-NAME</destination-jndi-name>
<initial-context-factory>com.tibco.tibjms.naming.TibjmsInitialContextFactory</initial-context-factory>
<provider-url>tcp://XXX.XXX.XXX.XXX:YYY</provider-url> <connection-factory-jndi-name>QueueConnectionFactory</connection-factory-jndi-name>
</message-driven-descriptor> <jndi-name>BuyResponseConsumer</jndi-name> </weblogic-enterprise-bean>
<security-role-assignment>
<role-name>XXXXX</role-name> <principal-name>XXXXX</principal-name> </security-role-assignment>
</weblogic-ejb-jar>
Thanks in advance,
Best Regards
Demis Gallisto

Hy, I'm writing about a technical problem with BeaWebLogicServer 6.1 sp5.
I've a MessageDrivenBean in the BeaWebLogic Container that must be connected to
a remote Tibco JMS queue.
When the remote Tibco queue is not protected by a password this works fine (my
MDB receives the message from Tibco queue), instead if the remote queue is password
protected, i've this Bea Weblogic server error log:
<Jun 18, 2004 3:06:06 PM CEST> <Warning> <EJB> <The Message-Driven EJB: BuyResponseConsumer
is unable to connect to the JMS destination: TELECOMIT.IPBILLING.SVIL.PI.PORTALE.ORDER.BUYRESP.
Connection failed after 850 attempts. The MDB will attempt to reconnect every
10 seconds, this log message will repeat every 600 seconds until the condition
clears.>
How may I resolve this problem?
These are my xml descriptors:
EJB-JAR.XML:
<!DOCTYPE ejb-jar PUBLIC "-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans
2.0//EN" "http://java.sun.com/dtd/ejb-jar_2_0.dtd">
<ejb-jar>
<enterprise-beans>
<message-driven>
<ejb-name>BuyResponseConsumer</ejb-name> <ejb-class>it.telecomitalia.wonderland.ipbilling.buyresponse.BuyResponseConsumer</ejb-class>
<transaction-type>Container</transaction-type> <acknowledge-mode>auto-acknowledge</acknowledge-mode>
<message-driven-destination> <destination-type>javax.jms.Queue</destination-type>
</message-driven-destination>
<security-identity>
<use-caller-identity id="XXXXX" />
</security-identity>
</message-driven>
</enterprise-beans>
<assembly-descriptor>
<security-role>
<role-name>XXXXX</role-name>
</security-role>
</assembly-descriptor>
</ejb-jar>
WEBLOGIC-EJB-JAR.XML
<?xml version="1.0"?> <!DOCTYPE weblogic-ejb-jar PUBLIC "-//BEA Systems, Inc.//DTD
WebLogic 6.0.0 EJB//EN" "http://www.bea.com/servers/wls600/dtd/weblogic-ejb-jar.dtd">
<weblogic-ejb-jar>
<weblogic-enterprise-bean> <ejb-name>BuyResponseConsumer</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>REMOTE-MESSAGE-QUEUE-NAME</destination-jndi-name>
<initial-context-factory>com.tibco.tibjms.naming.TibjmsInitialContextFactory</initial-context-factory>
<provider-url>tcp://XXX.XXX.XXX.XXX:YYY</provider-url> <connection-factory-jndi-name>QueueConnectionFactory</connection-factory-jndi-name>
</message-driven-descriptor> <jndi-name>BuyResponseConsumer</jndi-name> </weblogic-enterprise-bean>
<security-role-assignment>
<role-name>XXXXX</role-name> <principal-name>XXXXX</principal-name> </security-role-assignment>
</weblogic-ejb-jar>
Thanks in advance,
Best Regards
Demis Gallisto

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.

Losing connection to TIBCO JMS Server

I'm having a very strange problem with a Message Driven Bean in WebLogic. We're using a TIBCO JMS Server so I setup a Foreign JMS Server in Weblogic for my MDB. Seems to work fine and receive messages for awhile but then every morning at about the same time, I lose the connection. There are a number of other people connected to that TIBCO server for days/weeks with no problem, just me!
          I thought maybe the problem was with WebLogic so I wrote a main() method for my MDB which manually connects to the server/queue and calls setMessageListener(this). Same behavior: works overnight just fine and then disconnects at about 9:00am. No exception from JMS or anything, it just disconnects. I even set a JMS ExceptionListener but it never gets called.
          Has anyone had this bizarre problem?
          Thanks,
          - Ian

Did you tried running that main program on the same machine where Tibco is running ?

How to connect to Tibco JMS

Hi
I am looking for sample appliction, where a JSP tries to post a request to remote TIBCO JMS destination.
An application tier MDB consumes the message and prints the payload information.
We will we be configuring the remote destination name. Note the application is to be deployed in OC4J.
Pointers in this regard will be great.
Thanks
sunder

Don't have a sample application, but I can point you at the documentation for the Generic JMS Resource Adapter, which is our JCA1.5 adapter for interoperating with 3rd party JMS providers.
http://download.oracle.com/docs/cd/B32110_01/web.1013/b28958/jms.htm#CHDJDHCA
-steve-

Report and Alert don't executed in the error handler with a JMS proxy service

Hi,
I'm working with OSB 11.1.1.4.0 and I'm facing a problem with the error handler of my JMS proxy service.
My error handler contains two main elements :
- a Report action
- an Alert with a JMS destination defined
When the business service failed the message remain in the queue. It's the expected behavior.
The problem is :
- the report is missing
- the alert is raised but missing in the JMS destination defined in the Alert setting.
I've noticed if I add a Reply with Failure or Success, Report and Alert are successfully executed.
Unfortunately the message don't remain in the JMS queue.
What can I do in order to have my report/alert done and the JMS transaction rollback in order to keep the message in the queue ?
I've already met this problem in the past with alsb v3 and my solution was to add Service Callout in the error handler in order to externalize these actions.
This solution is not convenient and I hope another solution is possible.

Inventorying workgroups can be difficult, especially when it comes to remote access and network security. Because workgroups are not centrally managed, some of the items discussed in this
wiki article on preparing your workgroup environment may require you to visit each machine individually.
For non-domain credentials, you do not use the <systemname>\<user> format, you simply enter the user name. Regarding how to enter the credentials, if you have an account that uses the same username and password on all machines and is an administrator
on all of those machines, then you can enter that in the All computers credentials page of the wizard. You can also do this if they are different user names. However, if some machines have an account with the same user name, such as Administrator,
but different passwords on each machine, you will need to use the Manually enter computer names discovery method, and then enter the information for each group or each machine.
As you can tell, workgroup environments can quickly negate any benefit that the agentless inventory nature of MAP provides.
Please remember to click "Mark as Answer" on the post that helps you, and to click
"Unmark as Answer" if a marked post does not actually answer your question. Please
VOTE as HELPFUL if the post helps you. This can be beneficial to other community members reading the thread.

How toset JMS_TIBCO_COMPRESS to true ,connecting to tibco jms queue frmBPEl

Hi ,
I m tryingto connect to tibco jms queue from BPEL .How can i set JMS_TIBCO_COMPRESS to true before placing message on the queue.
I am able to send and receive the messages from the queue but I m not able to compress it

Did you figure out a solution for this? I have the same need and I'm investigating using JAAS configuration to accomplish.

9iAs / 10 g cmopatibility with TIBCO JMS 4.0.1

Similar Messages

Maybe you are looking for