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-
Similar Messages
-
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 itDid you figure out a solution for this? I have the same need and I'm investigating using JAAS configuration to accomplish.
-
Connecting to Tibco JMS through SSL
Hi,
How to we connect to a Tibco JMS Provider using SSL through OAS 10.1.3. Is there a way to configure OAS to use SSL when connecting to Tibco JMS Provider.
ThanksDid you figure out a solution for this? I have the same need and I'm investigating using JAAS configuration to accomplish.
-
How to connect to a JMS queue from portal app
Hi everyone,
can someone help me. I need to connect to a JMS or MQ queue with the portal. I cannot seem to find any documentation on that.
I would appreciate any aid in this.
thanks
MarianaI am trying MessageDrivenBean j2ee example given in portalwhich uses EJB.
I am not able to connect with portal. I can see the available Queues and Topics from Visual Administrator. But How can I create my own topic?
I am getting following exception while running given example.
examplee is available at :http://portal/index.html->J2EE Engine Examples
-->Message-Driven Bean Example
Error occurred: com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Path to object does not exist at java:comp, the whole lookup name is java:comp/env/MessageSender. -
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,
- IanDid you tried running that main program on the same machine where Tibco is running ?
-
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 AdvanceWrong forum, please ask this on dedicated weblogic or soa forums
-
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. -
JMS adapter: JNDI not able to connect to TIBCO server.
Hi All,
We are facing a strange problem here related to JMS adapter. We are trying to connect to TIBCO using JMS adapter.
We have 3 different Business Services, all the three using JMS channels. All the JMS channels are connecting to the same server on same port 7222. We have every thing same in all the JMS channels except the Que Name and the queue/log on user.
All the channels under 1 particular services are working fine while under the other two are giving below error:
===========================================
Channel error occurred; detailed error description: com.sap.aii.adapter.jms.api.connector.ConnectorException: Error looking up connection factoryQueueConnectionFactory, for profile: ConnectionProfile of channel: <Interface name> on node: <server node> having object id:<Object ID>: javax.naming.ServiceUnavailableException: Failed to query JNDI: Failed to connect to any server at: tcp://<host1>:7222, tcp://<host2>:7222<br> at com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl.createConnectionFactory(JndiConnectorImpl.java:135)<br>
=============================================
Below are the basic JMS configuration:
1. QueueConnectionFactory
2. com.tibco.tibjms.naming.TibjmsInitialContextFactory
We are on PI 7.0 and working with both Sender and Receiver JMS adapters.
Looking for your help.
Regards,
RahulHI,
Please reply me for this question, or to the other one JNDI not able to connect . Both aer one and the other are same.
--Khaleel -
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
RubanHi 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!! -
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. -
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 GallistoHy, 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 -
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.
<br>
<b>My ejb-jar.xml:</b>
<br>
<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>
<br>
<b>weblogic-ejb-jar.xml:</b>
<br>
<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>
<br>
<b>Error:</b>
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
<br>
<u><b>Any help would be appreciated.</b></u>
<br>
Thanks,<br>
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 findout which Tibco adaptor is used in our system?
Hi All,
In our system ,which is a Java enterprise application ,Tibco adaptor is used to connect to the database.
That adaptor is going to be upgraded. I would like ot do a technical research on that. But im new to the system.
Could anyone help me ,how to findout which Tibco adaptor is used in our system?
Thanks in advance.
AmeenaThere's nothing stopping you from using the generated sequence for something else, however you can NOT override it when doing an insert (as long as you've specified ALWAYS which is the default).
SQL> create table t
2 (some_id number generated as identity
3 ,name varchar2(30)
4 );
Table created.
SQL> select * from user_sequences;
SEQUENCE_NAME
ISEQ$$_91970
SQL> select ISEQ$$_91970.nextval from dual;
NEXTVAL
1
SQL> select ISEQ$$_91970.nextval from dual;
NEXTVAL
2
SQL> insert into t values (99,'smith');
insert into t values (99,'smith')
ERROR at line 1:
ORA-32795: cannot insert into a generated always identity column -
Weblogic 10.3 not suporting for MDB to connect remote Weblogic JMS server
Hi,
I have a problem with MDB deployed on Weblogic 10.3.It's simple MDB which is communicating with remote weblogic JMS server. I am getting below exception. could some one help how to resolve this issue.
<Apr 14, 2009 11:28:52 AM PDT> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: ReceiverFromDocumentum is unable to con
nect to the JMS destination: FMAContractOutboundQueue. The Error was:
[EJB:011013]The Message-Driven EJB attempted to connect to the JMS connection factory with the JNDI name: FMAConnectionFacto
ry. However, the object with the JNDI name: FMAConnectionFactory is not a JMS connection factory. NestedException Message is
:weblogic.jms.client.JMSConnectionFactory cannot be cast to javax.jms.XAConnectionFactory>
-SreekanthI recall that this particular warning message is sometimes misleading about the root cause of the problem, an issue that I think has been fixed in a patch. The actual problem can be various:
* The MDB is configured to be transactional, the connection factory exists, but the connection factory isn't configured to be "XA enabled". (I think this is the most likely problem).
* The connection factory doesn't exist.
* The object in JNDI with the specified connection factory name isn't actually a connection factory.
* The dest object in JNDI with the specified name isn't actually a javax.jms.Destination
Note that its unusual to configure the connection factory name for an MDB that consumes from WebLogic JMS. The default name iis usually sufficient unless custom tuning is required on the connection factory. See the MDB section of the EJB developer guide for more information.
Tom -
Connection Problem To "JMS Queue XML"
Hi.
I can't connect to the JMS Queue XML.While Creating Data Server using the JMS XML Queue Technology pointing to WLS and the XML document type definition (dtd ) file books.dtd is provided from the local(C:\Documents and Settings\348773\Desktop\XML FILES) directory. The connection details are as below:-
Definition Tab:
Connection:
User: userXXX
Password: passYYY
These are user name and password for the application server
JNDI tab:
JNDI Authorization: None
JNDI User/password (same as above)
JNDI Protocol: Undefined
JNDI Driver: weblogic.jndi.WLInitialContextFactory
JNDI URL: http://172.18.41.47:7001?d=C:\Documents and Settings\348773\Desktop\XML FILES\books.dtd&JMS_DESTINATION=jms/demoQueue
JNDI Resource:eis/ConnFact/Queue
FYI:-I h'v just copy and pasted the value of JNDI Driver(weblogic.jndi.WLInitialContextFactory) from a document because I don't know how to find the JNDI drivers name for WLS.I think it is a default name.If I'm wrong then Please tell me how to find it.when I test the connection it shows an error like this:-
java.sql.SQLException: Cannot load connection class because of underlying exception: 'java.sql.SQLException: Cannot load connection class because of underlying exception: 'javax.jms.JMSException: ODI-40201: Cannot create the initial JNDI context)'.'.
at oracle.odi.jdbc.datasource.LoginTimeoutDatasourceAdapter.doGetConnection(LoginTimeoutDatasourceAdapter.java:133)
at oracle.odi.jdbc.datasource.LoginTimeoutDatasourceAdapter.getConnection(LoginTimeoutDatasourceAdapter.java:62)
at com.sunopsis.sql.SnpsConnection.testConnection(SnpsConnection.java:1118)
at com.sunopsis.graphical.dialog.SnpsDialogTestConnet.getLocalConnect(SnpsDialogTestConnet.java:420)
at com.sunopsis.graphical.dialog.SnpsDialogTestConnet.localConnect(SnpsDialogTestConnet.java:860)
at com.sunopsis.graphical.dialog.SnpsDialogTestConnet.jButtonTest_ActionPerformed(SnpsDialogTestConnet.java:806)
at com.sunopsis.graphical.dialog.SnpsDialogTestConnet.connEtoC1(SnpsDialogTestConnet.java:165)
at com.sunopsis.graphical.dialog.SnpsDialogTestConnet.access$1(SnpsDialogTestConnet.java:161)
at com.sunopsis.graphical.dialog.SnpsDialogTestConnet$IvjEventHandler.actionPerformed(SnpsDialogTestConnet.java:111)
at javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:1995)
at javax.swing.AbstractButton$Handler.actionPerformed(AbstractButton.java:2319)
at javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:387)
at javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:242)
at javax.swing.plaf.basic.BasicButtonListener.mouseReleased(BasicButtonListener.java:236)
at java.awt.AWTEventMulticaster.mouseReleased(AWTEventMulticaster.java:272)
at java.awt.Component.processMouseEvent(Component.java:6289)
at javax.swing.JComponent.processMouseEvent(JComponent.java:3268)
at java.awt.Component.processEvent(Component.java:6054)
at java.awt.Container.processEvent(Container.java:2042)
at java.awt.Component.dispatchEventImpl(Component.java:4652)
at java.awt.Container.dispatchEventImpl(Container.java:2101)
at java.awt.Component.dispatchEvent(Component.java:4483)
at java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4577)
at java.awt.LightweightDispatcher.processMouseEvent(Container.java:4238)
at java.awt.LightweightDispatcher.dispatchEvent(Container.java:4168)
at java.awt.Container.dispatchEventImpl(Container.java:2085)
at java.awt.Window.dispatchEventImpl(Window.java:2479)
at java.awt.Component.dispatchEvent(Component.java:4483)
at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:644)
at java.awt.EventQueue.access$000(EventQueue.java:85)
at java.awt.EventQueue$1.run(EventQueue.java:604)
at java.awt.EventQueue$1.run(EventQueue.java:601)
at java.security.AccessControlContext$1.doIntersectionPrivilege(AccessControlContext.java:87)
at java.security.AccessControlContext$1.doIntersectionPrivilege(AccessControlContext.java:98)
at java.awt.EventQueue$2.run(EventQueue.java:618)
at java.awt.EventQueue$2.run(EventQueue.java:615)
at java.security.AccessControlContext$1.doIntersectionPrivilege(AccessControlContext.java:87)
at java.awt.EventQueue.dispatchEvent(EventQueue.java:614)
at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:269)
at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:184)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:175)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:170)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:162)
at java.awt.EventDispatchThread.run(EventDispatchThread.java:122)
Caused by: java.sql.SQLException: Cannot load connection class because of underlying exception: 'java.sql.SQLException: Cannot load connection class because of underlying exception: 'javax.jms.JMSException: ODI-40201: Cannot create the initial JNDI context)'.'.
at oracle.odi.jdbc.datasource.LoginTimeoutDatasourceAdapter.doGetConnection(LoginTimeoutDatasourceAdapter.java:133)
at oracle.odi.jdbc.datasource.LoginTimeoutDatasourceAdapter.getConnection(LoginTimeoutDatasourceAdapter.java:62)
at oracle.odi.core.datasource.dwgobject.support.OnConnectOnDisconnectDataSourceAdapter.getConnection(OnConnectOnDisconnectDataSourceAdapter.java:74)
at oracle.odi.jdbc.datasource.LoginTimeoutDatasourceAdapter$ConnectionProcessor.run(LoginTimeoutDatasourceAdapter.java:217)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:442)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:139)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:909)
at java.lang.Thread.run(Thread.java:662)
Caused by: java.sql.SQLException: Cannot load connection class because of underlying exception: 'java.sql.SQLException: Cannot load connection class because of underlying exception: 'javax.jms.JMSException: ODI-40201: Cannot create the initial JNDI context)'.'.
at com.sunopsis.jdbc.driver.JMSXMLDriver.connect(JMSXMLDriver.java:113)
at oracle.odi.jdbc.datasource.DriverManagerDataSource.getConnectionFromDriver(DriverManagerDataSource.java:409)
at oracle.odi.jdbc.datasource.DriverManagerDataSource.getConnectionFromDriver(DriverManagerDataSource.java:385)
at oracle.odi.jdbc.datasource.DriverManagerDataSource.getConnectionFromDriver(DriverManagerDataSource.java:352)
at oracle.odi.jdbc.datasource.DriverManagerDataSource.getConnection(DriverManagerDataSource.java:331)
... 7 more
Caused by: java.sql.SQLException: Cannot load connection class because of underlying exception: 'javax.jms.JMSException: ODI-40201: Cannot create the initial JNDI context)'.
at com.sunopsis.jdbc.driver.JMSXMLConnection.<init>(JMSXMLConnection.java:295)
at com.sunopsis.jdbc.driver.JMSXMLDriver.connect(JMSXMLDriver.java:99)
... 11 more
So,
please advise
Thanks
AnindyaHi,
Hope till now you might have solved this problem.
If not lets do this below workout , we had same kind of problem.
in JNDI tab , you have JNDI authentication, this authentication is for JNDI resources, I am sure you might be using weblogic credentials.
Steps :
1. Clear JNDI User : Blank (No value)
2. Clear Password : Blank (No Value)
3. set JNDI Authentication as None, regenerate the scenario and check
For accessing JNDI responses , JMS XML Queue uses Connection parameters from Definition tab.
Hope this helps
Maybe you are looking for
-
My MacBook Pro cannot connect to wifi but iPhone can
My 2012 MacBook Pro won't connect to my wifi. My iPhone connects just fine, and my MacBook can connect perfectly to other wifi channels, just not mine. I have tried everything to get this to work! Can anyone help? It would be much appreciated!!
-
Can someone please send some key questions asked on SAP HR in interviews. I've an interview in a day's time so please help with the some important questions on following modules: PERSONNEL ADMINISTRATION, ORGANIZATIONAL MANAGEMENT AND CONFIGURATION O
-
DVD DRIVE GONE ON LOADING ITUNES
Dear All I had purchased Ipod and on loading Itune software my dvd drive is gone. On uninstalling DVD drive re appears. Again on loading Itunes DVD drive is not appearing. Error message in device manager is Code 10. Pl provide solution so that Itunes
-
How to make a whole table row be read at once?
Hi, I want to make a whole table row be read at once by screenreaders if the table is not editable? I tried to use "getAccessibleSelection" and return a own implementation which returns the number of columns at "getAccessibleSelectionCount". But if "
-
How do I escape from receiving unsolicited calls
How do I escape from receiving unsolicited calls from overseas females who want to connect,ShaneShane