XI to IBM Websphere Default JMS Provider with JNDI

Hello everybody!
We face a problem with connecting SAP XI to IBM WebSphere Default JMS Provider (need to send a message from XI to WebSphere JMS and receive the response).
We have the following versions installed:
 SAP XI: 7.0 SP8 , Sun JDK 1.4.2
 IBM WebSphere: IBM WebSphere Application Server ND, 6.0.2.17, J2RE 1.4.2 IBM
We cannot set the JMS adapter of SAP XI for conecting with IBM WebSphere Default JMS Provider. The Communication Channel has erroneous state (at runtime) and the Communication Channel Monitoring tool displays the error message as described below (under "Variant 1" and "Variant 2" sub-headings) depending on the settings performed.
For connecting, the following JMS-provider settings were used at IBM WebSphere side:
 JMS Providers: Default Messaging Provider
 Queue Connection Factories: name:QueueConnectionFactory, jndi:jms/QueueConnectionFactory, provider: Default Messaging Provider
 Queues: name Queue, jndi: jms/Queue, provider: Default Messaging Provider
The XI communication channel (and associated JMS-adapter) was set as Variants 1 and 2 show. Settings for both cases and received error messages were the following:
Variant 1.
 Adapter type: JMS
 Type: Receiver
 JMS Provider: Access JMS Provider with JNDI (Java Naming and Directory Interface)
 JNDI Lookup Name of QueueConnectionFactory: jms/QueueConnectionFactory
 JNDI Lookup Name of JMS Queue: jms/Queue
 Name of JNDI Initial Context Factory: com.sap.engine.services.jndi.InitialContextFactoryImpl
 JNDI Server Address: iiop://WEBSPHERE.HOST:2809/
 As the result, the Communication Channel Monitoring displays that the channel has erroneous state and the following error message is written:
 "Error during channel initialization; exception trace: com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Object not found in lookup of jms/QueueConnectionFactory.
at com.sap.engine.services.jndi.implserver.ServerContextImpl.lookup(ServerContextImpl.java:649)"
Variant 2
 The same settings as in Variant 1 above, were used and additionally the following settings were done:
 - Name of JNDI Initial Context Factory: com.ibm.websphere.naming.WsnInitialContextFactory
 - The archive aii_af_jmsproviderlib.sda containing libraries required by WsInitialContextFactory, was deployed to the SAP WebAS where the XI is running. Those libraries were taken from WebSphere Application Server Pluggable Application Client installation package (described in the article "WebSphere Application Server Pluggable Application Client" located at http://www-128.ibm.com/developerworks/websphere/library/techarticles/0409_bhogal/0409_bhogal.html)
 - Also, as it is recommended in the referred article, the files required by IBM's iiop protocol (ibmext.jar ibmorb.jar ibmorbapi.jar) were put to the folder jre/lib/endorsed of the server(Sun JVM 1.4.2 is used by SAP WebAS / XI).
 As the result, the Communication Channel Monitoring displays that the channel has erroneous state as well and the following error message is written:
 "No adapter registered for this channel"
We have not found the recommended solution either in SDN forums or in Internet in general. Is it yet possible to connect SAP XI to IBM WebSphere Default JMS Provider having mentioned product versioning? If yes, what settings have to be performed?

IBM Websphere Default JMS Provider which is installed alongwith the application server is nothing but a scaled down version of the IBM WebSphere MQSeries. you should be able to connect to it with the same settings that can be used for a separate MQSeries server connectivity from XI.

Similar Messages

Error while using webmethod JMS provider with JNDI

Hi,
I am using webmethod JMS provider (not SAP JMS) with JNDI to connect to webmethod with XI. Central J2EE adapter engine is used and the comm chaneel is configured in with appropriate Provider JNDI Server address, initial context factory, Name of queue connection factory etc.
While activated the adapter short log shows: Adapter has not provided any status information about this channel"
In the detailed log following error message is displayed: "Obtained connection factory: null#"
#1.5 #001A4BAC31000052000001520000152200045090BF28DACA#1214482519514#com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl##com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl.createConnectionFactory()#J2EE_GUEST#0##n/a##8b16bd50437911ddc9f2001a4bac3100#SAPEngine_Application_Thread[impl:3]_16##0#0#Path##Plain###Entering method#
#1.5 #001A4BAC31000052000001530000152200045090BF28DB65#1214482519514#com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl##com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl.createConnectionFactory()#J2EE_GUEST#0##n/a##8b16bd50437911ddc9f2001a4bac3100#SAPEngine_Application_Thread[impl:3]_16##0#0#Debug##Plain###Looking up connection factory under name NAIP_XIQueueConnectionFactory#
#1.5 #001A4BAC31000052000001540000152200045090BF28E42E#1214482519516#com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl##com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl.createConnectionFactory()#J2EE_GUEST#0##n/a##8b16bd50437911ddc9f2001a4bac3100#SAPEngine_Application_Thread[impl:3]_16##0#0#Debug##Plain###Obtained connection factory: null#
#1.5 #001A4BAC31000052000001550000152200045090BF28E4B3#1214482519516#com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl##com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl.createConnectionFactory()#J2EE_GUEST#0##n/a##8b16bd50437911ddc9f2001a4bac3100#SAPEngine_Application_Thread[impl:3]_16##0#0#Path##Plain###Exiting method#
#1.5 #001A4BAC31000052000001560000152200045090BF28E528#1214482519516#com.sap.aii.adapter.jms.core.connector.ConnectorImpl##com.sap.aii.adapter.jms.core.connector.ConnectorImpl.executeConnectionFactoryInvocations()#J2EE_GUEST#0##n/a##8b16bd50437911ddc9f2001a4bac3100#SAPEngine_Application_Thread[impl:3]_16##0#0#Path##Plain###Entering method#
#1.5 #001A4BAC31000052000001570000152200045090BF28E5A9#1214482519517#com.sap.aii.adapter.jms.core.connector.ConnectorImpl##com.sap.aii.adapter.jms.core.connector.ConnectorImpl.executeConnectionFactoryInvocations()#J2EE_GUEST#0##n/a##8b16bd50437911ddc9f2001a4bac3100#SAPEngine_Application_Thread[impl:3]_16##0#0#Info##Java###Sucessfully executed CF invocations for connection factory object: for profile: #2#<null>#ConnectionProfile of channel: CC_RCV_JMS_SAPJNDIon node: 3010950 having object id: e4413a5265a436459e271d5e0dd4859b#
#1.5 #001A4BAC31000052000001580000152200045090BF28E64E#1214482519517#com.sap.aii.adapter.jms.core.connector.ConnectorImpl##com.sap.aii.adapter.jms.core.connector.ConnectorImpl.executeConnectionFactoryInvocations()#J2EE_GUEST#0##n/a##8b16bd50437911ddc9f2001a4bac3100#SAPEngine_Application_Thread[impl:3]_16##0#0#Path##Plain###Exiting method#
#1.5 #001A4BAC31000052000001590000152200045090BF28E6CA#1214482519517#com.sap.aii.adapter.jms.core.connector.ConnectorImpl##com.sap.aii.adapter.jms.core.connector.ConnectorImpl.buildConnection()#J2EE_GUEST#0##n/a##8b16bd50437911ddc9f2001a4bac3100#SAPEngine_Application_Thread[impl:3]_16##0#0#Path##Plain###Entering method#
#1.5 #001A4BAC310000520000015A0000152200045090BF28E741#1214482519517#com.sap.aii.adapter.jms.core.common.StringUtils##com.sap.aii.adapter.jms.core.common.StringUtils.isBlank(String str)#J2EE_GUEST#0##n/a##8b16bd50437911ddc9f2001a4bac3100#SAPEngine_Application_Thread[impl:3]_16##0#0#Path##Plain###Entering method#
#1.5 #001A4BAC310000520000015B0000152200045090BF28E7C3#1214482519517#com.sap.aii.adapter.jms.core.connector.ConnectorImpl##com.sap.aii.adapter.jms.core.connector.ConnectorImpl.buildConnection()#J2EE_GUEST#0##n/a##8b16bd50437911ddc9f2001a4bac3100#SAPEngine_Application_Thread[impl:3]_16##0#0#Debug##Plain###Creating connection...#
#1.5 #001A4BAC310000520000015C0000152200045090BF28EB51#1214482519518#com.sap.aii.adapter.jms.core.channel.AdapterImpl##com.sap.aii.adapter.jms.core.channel.AdapterImpl.addOrReplaceChannel(Channel cpaChannel)#J2EE_GUEST#0##n/a##8b16bd50437911ddc9f2001a4bac3100#SAPEngine_Application_Thread[impl:3]_16##0#0#Warning##Java###Catching #1#java.lang.NullPointerException
at com.sap.aii.adapter.jms.core.connector.ConnectorImpl.buildConnection(ConnectorImpl.java:198)
at com.sap.aii.adapter.jms.core.connector.ConnectorImpl.doConnect(ConnectorImpl.java:166)
at com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl.doConnect(JndiConnectorImpl.java:186)
at com.sap.aii.adapter.jms.core.connector.ConnectorImpl.connect(ConnectorImpl.java:151)
at com.sap.aii.adapter.jms.core.channel.ChannelImpl.doStart(ChannelImpl.java:235)
at com.sap.aii.adapter.jms.core.channel.ChannelImpl.start(ChannelImpl.java:154)
at com.sap.aii.adapter.jms.core.channel.AdapterImpl.doAddUpdateChannel(AdapterImpl.java:404)
at com.sap.aii.adapter.jms.core.channel.AdapterImpl.addOrReplaceChannel(AdapterImpl.java:376)
at com.sap.aii.adapter.jms.core.channel.ChannelLifecycleCallbackImpl$1.run(ChannelLifecycleCallbackImpl.java:51)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
#1.5 #001A4BAC310000520000015D0000152200045090BF28EC6A#1214482519518#com.sap.aii.adapter.jms.core.channel.AdapterImpl##com.sap.aii.adapter.jms.core.channel.AdapterImpl.addOrReplaceChannel(Channel cpaChannel)#J2EE_GUEST#0##n/a##8b16bd50437911ddc9f2001a4bac3100#SAPEngine_Application_Thread[impl:3]_16##0#0#Error##Plain###[[ChannelName:CC_RCV_JMS_SAPJNDI,ChannelId: e4413a5265a436459e271d5e0dd4859b]] Error adding/updating channel.#
#1.5 #001A4BAC310000520000015E0000152200045090BF28ECF8#1214482519518#com.sap.aii.adapter.jms.core.channel.AdapterImpl##com.sap.aii.adapter.jms.core.channel.AdapterImpl.addOrReplaceChannel(Channel cpaChannel)#J2EE_GUEST#0##n/a##8b16bd50437911ddc9f2001a4bac3100#SAPEngine_Application_Thread[impl:3]_16##0#0#Path##Plain###Exiting method#
#1.5 #001A4BAC310000520000015F0000152200045090BF28ED76#1214482519519#com.sap.aii.adapter.jms.core.channel.ChannelLifecycleCallbackImpl##com.sap.aii.adapter.jms.core.channel.ChannelLifecycleCallbackImpl.channelAdded().run()#J2EE_GUEST#0##n/a##8b16bd50437911ddc9f2001a4bac3100#SAPEngine_Application_Thread[impl:3]_16##0#0#Path##Plain###Exiting method#
#1.5 #001A4BAC3100005F000000660000152200045090BF65478A#1214482523474#com.sap.aii.adapter.jms.core.channel.ChannelLifecycleCallbackImpl#sap.com/com.sap.xi.mdt#com.sap.aii.adapter.jms.core.channel.ChannelLifecycleCallbackImpl.channelAdded(Channel channel)#AAAAAAAAA#108##n/a##002ee500437911dd99cf001a4bac3100#SAPEngine_Application_Thread[impl:3]_29##0#0#Path##Plain###Exiting method#
Please let me know anyone has come accross the problem or has idea how to solve it. Thanks.

Hi,
Ask ur basis admin to restart JMS adpater From Vis administrator and try again to activate the comm channel.
Hope this will solve ur problem and once again check connection fatcory and Queue name provided by Webmethod admin.
Regards,
Srini

SSL connectivity for IBM WebSphere MQ to integrate with XI

Any information of SSL connectivity for IBM WebSphere MQ to integrate with XI???

Ravi,
Have you gone thru this SAP Note - 912314 - SSL support for IBM Websphere MQ/ MQ Series
raj.
[Give Support|http://www.sapfeedingknowledge.com/show_your_support|I'm Working here for Global cause]

Configuring WL JMS as a foreign JMS provider with security scope (WLS 8.1)

Hello, i have a problem accessing a queue from a foreign jms provider, if the queue has a security policy. I have the following scenario:
 1) Server server1 in domain1 (WLS81) has a JMS Server with one queue queue1 with a security policy "Caller is a member of the group GROUP_QUEUE". There is also a user USER_QUEUE user defined, which belongs to the this group.
 There is also a ConnectionFactory with "XA Connection Factory Enabled = true" configured.
 The queue and the connection factory are visible in the jndi tree of this server.
 2) Server server2 has a foreign jms server. Foreign JMSConnectionFactory and foreign JMSDestination refer to the jndi entries of server 1. For Foreign JMS Connection Factory username is set to USER_QUEUE. JNDI entries for foreign references are visible in jndi tree of this server.
 I wrote a standalone client to store messages in the queue accessing server1 with USER_QUEUE sucessfully.
 Now I try to deploy a MDB on server2 accessing the queue on server 1. I tried different versions of ejb-jar.xml/weblogic-ejb-jar.xml to access the queue, but with no luck.
 scenario a): no security entries in both descriptors; weblogic-descr has entries <destination-jndi-name> and <connection-factory-jndi-name> pointing to the local jndi names. REsult:
 <11.02.2005 19.16 Uhr CET> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB:
 CancelEasyMoneyBean is unable to connect to the JMS destination: prepaid.Cancel
 EasyMoneyQueue. The Error was:
 [EJB:010196]'weblogic.jms.common.JMSSecurityException: Access denied to resource
 : type=<jms>, application=, destinationType=queue, resource=CancelEasyMoneyQueue
 , action=receive' Linked exception = 'weblogic.jms.common.JMSSecurityException:
 Access denied to resource: type=<jms>, application=, destinationType=queue, reso
 urce=CancelEasyMoneyQueue, action=receive'
 So entering username and password for ForeignJMSConnectionFactory doesn't do the trick.
 scenario b:) trying to set additional security entries in both descriptors. I added a role queueUser to my mdb and to weblogic-descr a
 <security-role-assignment>
 <role-name>queueUser</role-name>
 <principal-name>USER_QUEUE<principal-name>
 </security-role-assignment>
 I added the user USER_QUEUE and the group GROUP_QUEUE to server2.
 Now server 1 throws exception after redeployment on server 2:
 java.lang.SecurityException: [Security:090398]Invalid Subject: principals=[USER_QUEUE, GROUP_QUEUE].
 java.lang.SecurityException: [Security:090398]Invalid Subject: principals=[USER_QUEUE, GROUP_QUEUE]
 at weblogic.security.service.SecurityServiceManager.seal(SecurityService
 Manager.java:680)
 Has anybody an idea or a pointer how to define access from a mdb to a foreign queue using security ?
 Thanks in advance,
 Rainer

Hello, i have a problem accessing a queue from a foreign jms provider, if the queue has a security policy. I have the following scenario:
 1) Server server1 in domain1 (WLS81) has a JMS Server with one queue queue1 with a security policy "Caller is a member of the group GROUP_QUEUE". There is also a user USER_QUEUE user defined, which belongs to the this group.
 There is also a ConnectionFactory with "XA Connection Factory Enabled = true" configured.
 The queue and the connection factory are visible in the jndi tree of this server.
 2) Server server2 has a foreign jms server. Foreign JMSConnectionFactory and foreign JMSDestination refer to the jndi entries of server 1. For Foreign JMS Connection Factory username is set to USER_QUEUE. JNDI entries for foreign references are visible in jndi tree of this server.
 I wrote a standalone client to store messages in the queue accessing server1 with USER_QUEUE sucessfully.
 Now I try to deploy a MDB on server2 accessing the queue on server 1. I tried different versions of ejb-jar.xml/weblogic-ejb-jar.xml to access the queue, but with no luck.
 scenario a): no security entries in both descriptors; weblogic-descr has entries <destination-jndi-name> and <connection-factory-jndi-name> pointing to the local jndi names. REsult:
 <11.02.2005 19.16 Uhr CET> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB:
 CancelEasyMoneyBean is unable to connect to the JMS destination: prepaid.Cancel
 EasyMoneyQueue. The Error was:
 [EJB:010196]'weblogic.jms.common.JMSSecurityException: Access denied to resource
 : type=<jms>, application=, destinationType=queue, resource=CancelEasyMoneyQueue
 , action=receive' Linked exception = 'weblogic.jms.common.JMSSecurityException:
 Access denied to resource: type=<jms>, application=, destinationType=queue, reso
 urce=CancelEasyMoneyQueue, action=receive'
 So entering username and password for ForeignJMSConnectionFactory doesn't do the trick.
 scenario b:) trying to set additional security entries in both descriptors. I added a role queueUser to my mdb and to weblogic-descr a
 <security-role-assignment>
 <role-name>queueUser</role-name>
 <principal-name>USER_QUEUE<principal-name>
 </security-role-assignment>
 I added the user USER_QUEUE and the group GROUP_QUEUE to server2.
 Now server 1 throws exception after redeployment on server 2:
 java.lang.SecurityException: [Security:090398]Invalid Subject: principals=[USER_QUEUE, GROUP_QUEUE].
 java.lang.SecurityException: [Security:090398]Invalid Subject: principals=[USER_QUEUE, GROUP_QUEUE]
 at weblogic.security.service.SecurityServiceManager.seal(SecurityService
 Manager.java:680)
 Has anybody an idea or a pointer how to define access from a mdb to a foreign queue using security ?
 Thanks in advance,
 Rainer

Using SJS MQ 4.0 as JMS provider with JBoss or Apache Geronimo

Is it possible to integrate SMS MQ 4.0 as the JMS provider for JBoss and / or Apache Geronimo ?
For JBoss, the only info that I can find is this:
http://swforum.sun.com/jive/thread.jspa?threadID=45414&messageID=127657
... but not too much detail on how to actual configured JBoss.
Any step-by-step info ?

Hmm... I installed the client (5.3) and did not get the jmsadmin tool. To me it seems like jmsadmin only comes with the server installation. What is the content of the .bindings file? Is it enough to copy the one from the MQ server or is this something I must create on the server running the Oracle application server? I would guess .bindings is the JNDI bindigs for the queues / factories etc. and will have to match the way queues are configured on the server.
So far I've found two "useful" resources:
http://download-west.oracle.com/docs/cd/B10464_01/web.904/b10326/jms.htm#1020231
http://www.oracle.com/technology/tech/java/oc4j/1003/how_to/jcajmsmq/doc/Install.html
The last resource states that MQ server has to be installed on the same server as Oracle Appserver.

Using JBOSS JMS provider with XI

Hi,
I am connecting XI to a custom Java application developed on JBOSS app server. The custom application is developed with connectivity using JMS. I was told that JBOSS has a JMS provider used by the custom app. Has anyone done this before? Is it possible for XI to use JBOSS JMS provider? How difficult is this going to be for synchronous interface? Any information is greatly appreciated.
thanks.
James Chang

hi,
first deploy jboss-j2ee.jar,jms.jar,dom4j-full.jar..for deploying these jars into the xi follow this link
http://help.sap.com/saphelp_nw04s/helpdata/en/33/e6fb40f17af66fe10000000a1550b0/frameset.htm
then to make use of the JMS adapter follow this link,
http://help.sap.com/saphelp_nw04s/helpdata/en/4d/a3bc97ff55c742af7faed661635baf/frameset.htm
hope this will be useful.....
regards,
Sundararamaprasad

Link between WebSphere Default Messaging provider/SIBus and JCAPS JMS

Our goal is to put messages using JMS from an application running in a WebSphere Application Server, to a JCAPS JMS message server, stcms.
Our developers are suggesting the application to connect directly to the receiving JMS-server.
However, as an administrator, I want the infrastructure to handle failover and routing of the messages to the receiving message servers.
One alternative is to make use of the integrated SIBus in WAS and make a link to the foreign JMS-server.
Anyone tried this and made it working?
Jonas

hi jonas,
we have tried this out with WAS(5) but never suceeded. since configuration is a bit complicated we have only spent 2 days trying it. maybe you have better knowledge as we do and the product as such has changed in lots of details .... if you manage to do so please inform this newsgroup about it.
i would love to see a solution to this.
regards chris

Jms provider with SSL transport : connectException

I have a jmsprovider that is connecting to a remote server(another domain) over SSl transport. I have trust and identity keystore created and configured. Looks like I have passed the SSL handshale stage and client side accepted trust certificate successfully.
After that it is doing JNDI look up on connection factory and failing there
The invocation resulted in an error: [JMSPool:169803]JNDI lookup of the JMS connection factory synergyConnectionFactory1 failed: javax.naming.CommunicationException [Root exception is java.net.ConnectException: t3s://10.100.104.153:7002: Destination unreachable; nested exception is:
*java.net.ConnectException: Connection refused: connect; No available router to destination].*
i have SSL listener port is 7002. Do I need to do any other setup on the remote server side to make the JNDI lookup success in this port? I am able to access the queue with no-ssl on 7001 port.
I am not using any service account here. Will that be required to make this work? If I do not provide any, then will be the default account (guest) used? And according to the default security policy on the jms resource side , this account will have access to the resource and JNDI lookup too.
Please suggest
Edited by: 818591 on Mar 1, 2011 12:36 PM

From the error it looks like a network connectivity issue .. r u able to telnet to port 7002 from the source box? some firewalls may allow only messages of certain protocol e.g. https to 7002 may work, but not t3s to 7002 .. make sure you are not dealing with a network/firewall issue..
I am not using any service account here. Will that be required to make this work?Service account will not be required unless the queue on the remote destination has been secured. By default, weblogic jms resources are unsecured meaning will allow anonymous access.

IBM websphere 6.1 integration with OAM

Hi,
1) Is the "interceptorClassName" Clases Name important? can i name it as other thing rather than what is stated in the documentation?
example:
According to the WAS integtraion guide the Interceptor classname is as: com.oblix.tai.was5.WebGate2TrustAssociationInterceptor
Can i change it to com.oblix.tai.was5.WebGateTrustAssociationInterceptor
2) Is there anywhere to verify that TAI is loaded properly and how do i test it?
================================================================================
Interceptor classname is under WAS, Secure administration -> applications, and infrastructure -> Trust association -> Interceptors
Thanks and Regards,
Grey

Thanks! i got the figure out. but i encouter something else while integrating with WAS
im trying to integrate OAM with WAS without reverse proxy and i followed the documentation religiously. in the documentation
Defining an Oracle Access Manager Policy Domain for WebSphere without Reverse Proxy_
Without reverse proxy, disabling SSO in WAS is required. I will need to protect the WebSphere Administrative Console SSL URL. Otherwise, I will not be able to access the console after disabling SSO in WAS. I have create the policy domain as the documentation.
■ Resource Type: http
■ Host Identifier: xxx
■ URL Prefix: _/ibm/console; and /admin_
■ Description: Used by NetPointWASRegistry TAI component.
Authorization Rules: Click the Authorization Rules tab, click Add, and then create and save an authorization rule to allow access to WebSphere Administrative
Console resources. For example:
a. Click General, then enter and save:
* Name: Allow Administrator.
* Description: Allow access to WebSphere Administrative Console resources.
* Enabled: Yes
* Allow takes Precedence: Yes
Without Reverse Proxy: Click Actions, then enter and save the following WebSphere Administrative Console SSL URL for Authentication Success. For example:
Redirect to: https://hostname:port/ibm/console *<- i found out that once I had this implemented. I will be going in an authentication cycle (keep getting authenticated and redirected back to the same page) because it is part of the resources I had it declare previously to be protected.*
Is there a work around or is it due to documentation error?

Configuration of JMS receiver Using Jboss JMS provider

Hi all..
I am configuring JMS adapter as receiver.
I am using JMS provider JBOSS .
I hav done configuration as
Transport protocol :Acess JMS provider with JNDI
JNDI lookUp Name of q connection factory: org.jboss.naming.LinkRefPairService
Name of JNDI initial Context factory :org.jnp.interfaces.NamingContextFactory
in sxmb_moni I am getting blak&white flag
IN Run time work bench In adapter monitoring I am getting
Receiver channel. Details: Cannot instantiate class: org.jnp.interfaces.NamingContextFactory.
Can anybody plz tell me why this haapend?

Did you deploy the JMS client jars to the J2EE Engine?
Cannot instantiate class: org.jnp.interfaces.NamingContextFactory sounds like the Framework can't find the class.
Take a look here:
Re: Using JBOSS JMS provider with XI
Greetz
Sebastian
Message was edited by: Sebastian Simon

Error in Access JMS with JNDI

Hi all,
I am trying DB>XI>TIBCO (EMS).
I have included tibjms.jar library in aii_af_jmsproviderlib.sda and deployed using SDM.
In JMS receiver adapter I am using the following:-
Transport protocol: Access JMS Provider with JNDI.
JNDI Lookup Name of Queue connection factory: com.tibco.tibjms.TibjmsQueueConnectionFactory
JNDI Lookup Name of JMS Queue: com.tibco.tibjms.TibjmsQueue
Name of JNDI Initial Context Factory:
com.tibco.tibjms.naming.TibjmsInitialContextFactory
In RWB i am getting the following for this scenario:
2005-04-17 19:55:05 Success Using connection AFW. Trying to put the message into the receive queue.
2005-04-17 19:55:05 Success The message was successfully retrieved from the receive queue.
2005-04-17 19:55:05 Success The message status set to DLNG.
2005-04-17 19:55:05 Success Deliver to channel: TIB_Receiver_JNDI
2005-04-17 19:55:05 Error Exception caught by adapter framework: Object not found in lookup of XIJMSService.
2005-04-17 19:55:05 Success XI message converted to binary format successfully
2005-04-17 19:55:05 Error Delivery of the message to the application using connection AFW failed, due to: Object not found in lookup of XIJMSService..
2005-04-17 19:55:05 Success The asynchronous message was successfully scheduled to be delivered at Sun Apr 17 20:00:05 GMT+05:30 2005.
2005-04-17 19:55:05 Success The message status set to WAIT.
Kindly help what other configurations are required.
Regards,
Arpit Seth

Hi all,
Me too have the same problem.
I am trying to integrate XI with OpenJms (server) using JMS adapter.
But the error that i am getting is similar to yours:
Error Exception caught by adapter framework: Object not found in lookup of XIJMSService.
I am very interested to the solution.
Thanks in advence.
Best regards.
Lemin
Message was edited by: lemine ould-cheikh

Sender JMS Adapter error: The JMS provider gave the error message as Not permitted, and the error code is null

I am trying to connect tibcoems with PI using a Sender jms adapter.After successfully installing the drivers , the sender adapter goes into error.
"The JMS Provider gave the error message as Not permitted, and the error code is null"
The Transport protocol is 'Access JMS Provider with JNDI' and i have been given the required parameters from the tibco guys.
Your input are highly appreciated.
Shyam

Hi AQmit,
Thanks for the reply.
Please find the screenshots of what i am trying to do.
Also, Can u direct me how to check the right logs?

Can't discover IBM Websphere target with OEM 12c

Hi, guys!
I am tryin to config my OEM CC 12c to monitor IBM Websphere 7.0.0.11(win2003R2 x64).
My OMS with BP1 applied is runnin OEL 6.1(x64), DB 11.2.0.3 - SLES11 SP1(x64) for vmware
Monitoring agent is runnin on the same server with WAS, i deployed 12.1.0.2.0_oracle.sysman.emas(27/04/2012) plugin on OMS and agent successfully.
and on first step of discovery process i face an unknown error with no explanation.
agent log:
+2012-06-05 13:12:41,578 [31869:A1B8C06B:HTTP Listener-31869 - /emd/main/] INFO - (begin processing requests for OMS@14957@Cloud=>[133888751270001])+
+2012-06-05 13:12:41,578 [31869:A1B8C06B] INFO - >>> Dispatching request: GetTargetsRequest (host. (include host and TZ)) <<<+
+2012-06-05 13:12:41,594 [31869:A1B8C06B] INFO - >>> Reporting response: GetTargetsResponse (request id 1) <<<+
+2012-06-05 13:12:41,594 [31869:A1B8C06B] INFO - (end processing requests for OMS@14957@Cloud=>[133888751270001])+
+2012-06-05 13:12:41,609 [31869:E0918418:HTTP Listener-31869 - /emd/main/ (DispatchRequests)] INFO - (begin processing requests for OMS@14957@Cloud=>[133888751270002])+
+2012-06-05 13:12:41,609 [31869:E0918418] INFO - >>> Dispatching request: GetMetricDataRequest (DiscoverNow@host.*0.*1.*1.*6 {pluginId=oracle.sysman.emas, userProps=SERVER_TYPE,websphere_as,HOST,*0.*1.*1.*6,PORT,8880,USERNAME,wsadmin,TRUSTED_KEY_STORE,,AS_DEPLOYMENT_HOME,,VERSION,7.0.x, stdinProps=******, discCategory=WEBLOGIC_8_X, onDemand=true, __gcagent__.isOutputSensitive=true}) <<<+
+2012-06-05 13:12:41,875 [31869:E0918418] INFO - >>> Reporting response: GetMetricDataResponse (***OUTPUT IS SENSITIVE***) (request id 1) <<<+
+2012-06-05 13:12:41,875 [31869:E0918418] INFO - (end processing requests for OMS@14957@Cloud=>[133888751270002])+
Any ideas how can i solve this problem?
thx in advance, Gleb.
Edited by: user7104913 on 05.06.2012 2:34

thx for you reply, Eric
this is the main problem - i cant understand what i am doing wrong - there are no errors in logs: add target manually --> ibm websphere app serever --> provide all necessary params (server ip, was version, soap port, usr/pass) --> push next and get an error message(literally - "ERROR") over inserted params.
and yes, agent's targets.xml contains only standart targets:
<Targets AGENT_TOKEN="57ABE5B075FA49EFCD2F934D8DFB0EDD2E71DB922D7BDFA8A72561F0B9A07D3C">
 <Target TYPE="+host+" NAME="*0.*1.*1.*6" DISPLAY_NAME="*0.*1.*1.*6" ON_HOST="" EMD_URL="https://*0.*1.*1.*6:3872/emd/main/" TIMEZONE_REGION="" IDENTIFIER="TARGET_GUID=607374AD1C0DE71201A9BF1C047CBCE4"/>
 <Target TYPE="+oracle_emd+" NAME="*0.*1.*1.*6:3872" DISPLAY_NAME="*0.*1.*1.*6:3872" ON_HOST="" EMD_URL="*0.*1.*1.*6:3872/emd/main/" TIMEZONE_REGION="" IDENTIFIER="TARGET_GUID=9DE64263B01A068653D7ECBD07C42803"/>
 <Target TYPE="+oracle_home+" NAME="agent12c1_1_* " DISPLAY_NAME="agent12c1_*" ON_HOST="" EMD_URL="https://*0.*1.*1.*6:3872/emd/main/" TIMEZONE_REGION="" IDENTIFIER="TARGET_GUID=29D8E2A2B09883CA7E4C53161F8E9F86">
 <Property NAME="HOME_TYPE" VALUE="O"/>
 <Property NAME="INVENTORY" VALUE="C:\Program Files\Oracle\Inventory"/>
 <Property NAME="INSTALL_LOCATION" VALUE="c:/oracle/agentHome\core\12.1.0.1.0"/>
 </Target>
</Targets>
it seems to me that discovery process haven't even been started, wizard just doesn't like params that i inserted but i tried different combinations - same result...
mb its some kind of bug?
Edited by: user7104913 on 07.06.2012 0:38

MDB behavior with Foreign JMS Provider

 I am experiencing some MDB behavior which I do not quite understand. I would appreciate
 if someone could tell me what might be happening.
 An application on WebLogic 8.1 SP1 (also tried it with SP2) has MDB's which listen
 on a MQ Queue. If I put a large XML message on the MQ Queue (say around 600 KB),
 the onMessage execution is very random, For the large messages only 1 MDB gets
 invoked and the other messages just sit on the MQ Queue. Even though I have defined
 an weblogic execute queue for the MDB's and they have 15 threads allocated.
 The other messages get picked up after the first one gets completed. The problem
 is the whole transaction (which is XA) can take a while (upto 10 minutes). This
 is not intended, but for some reason it takes that long.
 Also, while monitoring the MDB execute queues, I noticed that none of the threads
 from that queue are performing the work and a thread dump shows that the weblogic.ejb20.internal.JMSPoller
 thread has invoked the MDB and is currently waiting for the database to finish
 some processing.
 When the message size is smaller, the MDB's fire concurrently and are executed
 on the MDB execute queue.
 Thanks,
 Ketan.


When we're using MDBs against a foreign JMS provider with XA, the EJB
 container tries to reduce the number of threads that are blocked waiting for
 a message. You should see lots of threads working when there are lots of
 messages on the queue, a few threads (or only one) working when the queue is
 empty or nearly so, and there should be some ramp-up and ramp-down time in
 between. It sounds like the ramp-up takes longer in your case because
 receiving the very first message takes a long time.
 If this behavior is causing big problems for you, you might want to contact
 product support and file an enhancement request.
 greg
 "Ketan" <[email protected]> wrote in message
 news:[email protected]...
 >
 > Here is some more information regarding this issue.
 >
 > When I place sufficiently large messages (such that the parsing and
 processing
 > of these messages takes longer than it does for normal size messages), I
 notice
 > the following behavior.
 >
 > Lets say I put 6 large messages on the MQ Queue. The server immediately
 picks
 > up 1 message and starts processing it. The other 5 messages are sitting on
 the
 > MQ Queue, while the MDB execute queue has all 15 idle threads.
 >
 > After the processing of the message is done, 2 messages get picked up.
 This time,
 > 1 thread in the MDB execute queue gets the message and the other is
 processed
 > by the JMSPoller thread. After these 2 messages are processed, 3 Messages
 get
 > picked up and this time 2 messages are on the MDB execute queue and 1 is
 processed
 > by the JMSPoller.
 >
 > So based on this the question is ..Is this the expected behavior? I was
 under
 > the impression that the poller would simply dispatch messages to the
 execute queue,
 > and as a result, I was expecting all the messages would get picked up from
 the
 > MQ queue pretty fast and would not have to wait for 1 or more MDB's to
 finish
 > processing.
 >
 > I would really appreciate any suggestions anyone may have for me.
 >
 > Again the environment is WLS 8.1 SP2, MQ 5.3
 >
 > thanks,
 > Ketan

JMS Connector WebSphere MQ JMS Problems

I'm having problems configuring and using Oracle's JMS Connector with IBM WebSphere MQ JMS, as explained in the following Oracle How-to:
http://www.oracle.com/technology/tech/java/oc4j/1013/how_to/how-to-connect-to-mqseries/doc/how-to-connect-to-mqseries.html
by Jeff Steidl
When trying to deploy the application to the oc4j (wich is done as part of the default ant target), I get the following error in the oc4j console:
2006-07-20 12:04:29.859 ERROR J2EE EJB3027 [how-to-connect-to-mqseries] An error
occured deploying EJB module: java.lang.InstantiationException: Resource except
ion(MQJMSRAInstanceName) for MessageDrivenBean DealerEjbName during endpoint act
ivation: failure looking up resource provider factory for XAConnectionFactoryWra
pper [XA Unified]-OracleGJRA.XAConnectionFactoryWrapper.pedroec.-7b007002:10c88d
48c98:-7fff.171 []: javax.resource.spi.ResourceAdapterInternalException: Looking
up java:comp/resource/MQJMSReference/mqxacf: javax.naming.NameNotFoundException
: No resource named 'MQJMSReference/mqxacf'found
I assume the problem is that I don't have an appropriate WebShpere binding for the resource.
Before going through the mentioned How-to, I followed the install instructions in:
http://www.oracle.com/technology/tech/java/oc4j/1003/how_to/jcajmsmq/doc/Install.html
In order to create a queue manager, a queue, a topic and the appropriate bindings.
After following the previous document, I end up with the following bindings (listing obtained using JMSAdmin console):
InitCtx> dis ctx
Contents of InitCtx
.bindings java.io.File
a MQXAQCF com.ibm.mq.jms.MQXAQueueConnectionFactory
a MQTCF com.ibm.mq.jms.MQTopicConnectionFactory
a MQQCF com.ibm.mq.jms.MQQueueConnectionFactory
a MQQ com.ibm.mq.jms.MQQueue
a MQT com.ibm.mq.jms.MQTopic
a MQXATCF com.ibm.mq.jms.MQXATopicConnectionFactory
7 Object(s)
0 Context(s)
7 Binding(s), 6 Administered
And as you can see there is no mqxacf binding.
So the question is, should I define a new binding with that name? If so, what would be the command (def xacf(mqxacf) ?)
As you can see, ther is a MQXAQCF binding so Instead of defining a new mqxacf (which I really don't know how to do...) I thought that maybe I could use this one, being a xa queue connection factory instead of a plain xa connection factory.
This is used by the MDB, so I modified orion-ejb-jar.xml changing:
<resource-ref-mapping
location = "MQJMSRASubcontext/MyXACF"
name = "jms/DealerConnectionFactory"/>
<config-property>
<config-property-name>ConnectionFactoryJndiName
</config-property-name>
<config-property-value>MQJMSRASubcontext/MyXACF
</config-property-value>
</config-property>
for this:
<resource-ref-mapping
location = "MQJMSRASubcontext/MyXAQCF"
name = "jms/DealerConnectionFactory"/>
<config-property>
<config-property-name>ConnectionFactoryJndiName
</config-property-name>
<config-property-value>MQJMSRASubcontext/MyXAQCF
</config-property-value>
</config-property>
I changed MyXACF with MyXAQCF because oc4j-ra.xml defines a jndi location of mqxacf (which is not beign found in the bindings) for MyXACF while it defines a jndi location of MQXAQCF for MyXAQCF, which is defined in the bindings.
With this change, the application deploys ok ... but when I run the client (ant larry) I get the following error (from the client console, not the oc4j console... in the oc4j console, nothing is reported):
run-demo:
[exec] java.lang.NullPointerException
[exec] at oracle.j2ee.ra.jms.generic.RAUtils.lookupUsingResourceProvide
r(RAUtils.java:254)
[exec] at oracle.j2ee.ra.jms.generic.CommonManagedConnectionFactoryImpl
.getFactory(CommonManagedConnectionFactoryImpl.java:605)
[exec] at oracle.j2ee.ra.jms.generic.CommonFactoryWrapper.localCreateCo
nnection(CommonFactoryWrapper.java:121)
[exec] at oracle.j2ee.ra.jms.generic.ConnectionFactoryWrapper.createCon
nection(ConnectionFactoryWrapper.java:62)
[exec] at MyChannel.<init>(MyChannel.java:46)
[exec] at Player.play(Player.java:242)
[exec] at Player.main(Player.java:30)
Since MyCF is bound to the jndi location mqcf (in oc4j-ra.xml) which does not exist in my MQ bindings I decided to modify orion-ejb-jar.xml as I did for the MyXACF of the MDB.
I changed
<resource-ref-mapping
location = "MQJMSRASubcontext/MyCF"
name = "jms/PlayerConnectionFactory"/>
with this:
<resource-ref-mapping
location = "MQJMSRASubcontext/MyQCF"
name = "jms/PlayerConnectionFactory"/>
I changed MyCF to MyQCF, which has a jndi location of MQQCF (specified inside of oc4j-ra.xml) which has a valid MQ binding.
.... but I get the following error:
run-demo:
[exec] Exception in thread "main" java.lang.AbstractMethodError: com.ibm.mq
.jms.MQQueueConnectionFactory.createConnection()Ljavax/jms/Connection;
[exec] at oracle.j2ee.ra.jms.generic.CommonManagedConnectionFactoryImpl
.createManagedConnection(CommonManagedConnectionFactoryImpl.java:261)
[exec] at com.evermind.server.connector.ApplicationConnectionManager.cr
eateManagedConnection(ApplicationConnectionManager.java:1333)
[exec] at oracle.j2ee.connector.ConnectionPoolImpl.createManagedConnect
ionFromFactory(ConnectionPoolImpl.java:324)
[exec] at oracle.j2ee.connector.ConnectionPoolImpl.access$800(Connectio
nPoolImpl.java:95)
[exec] at oracle.j2ee.connector.ConnectionPoolImpl$NonePoolingScheme.ge
tManagedConnection(ConnectionPoolImpl.java:1209)
[exec] at oracle.j2ee.connector.ConnectionPoolImpl.getManagedConnection
(ConnectionPoolImpl.java:782)
[exec] at com.evermind.server.connector.ApplicationConnectionManager.ge
tConnectionFromPool(ApplicationConnectionManager.java:1532)
[exec] at com.evermind.server.connector.ApplicationConnectionManager.ac
quireConnectionContext(ApplicationConnectionManager.java:1477)
[exec] at com.evermind.server.connector.ApplicationConnectionManager.al
locateConnection(ApplicationConnectionManager.java:1423)
[exec] at oracle.j2ee.connector.OracleConnectionManager.unprivileged_al
locateConnection(OracleConnectionManager.java:244)
[exec] at oracle.j2ee.connector.OracleConnectionManager.allocateConnect
ion(OracleConnectionManager.java:198)
[exec] at oracle.j2ee.ra.jms.generic.CommonFactoryWrapper.localCreateCo
nnection(CommonFactoryWrapper.java:130)
[exec] at oracle.j2ee.ra.jms.generic.QueueConnectionFactoryWrapper.crea
teConnection(QueueConnectionFactoryWrapper.java:84)
[exec] at MyChannel.<init>(MyChannel.java:46)
[exec] at Player.play(Player.java:242)
[exec] at Player.main(Player.java:30)
[exec] Result: 1
So as you can see I'm stuck.
Maybe it is just a simple matter of defining the appropriate objects and bindigs for mqxacf and mqcf, but I don't know how to do that.
I would appreciate any help.
Message was edited by:
pablokrause

Thanks again for your quick and useful response Jeff.
Regarding the extra administration steps to get topic consumers working in MQ, I had already executed them a few days ago as part of the MQ setup as is described in another JMS resource adapter demo (see references at bottom of this reply) but I thought that doing it once was enough. Well, it seems that you have to execute those commands each time you start MQ!
I executed them (again), as you kindly suggested in your last response and voila, it worked!... well sort of.
After starting the clients, I get the following random error in oc4j:
06/07/21 15:39:18 Got message: PING
06/07/21 15:39:18 randomly testing rollback:
06/07/21 15:39:18 sending a junk message
06/07/21 15:39:18 Sent message: Invalid junk message
06/07/21 15:39:18 marking transaction for rollback
06/07/21 15:39:18 sending a junk message
06/07/21 15:39:18 Sent message: Invalid junk message
2006-07-21 15:39:18.921 WARNING J2EE JTA0107 Error in resource driver during rol
lback: javax.transaction.xa.XAException: XA operation failed, see errorCode
2006-07-21 15:39:18.921 WARNING J2EE JTA0104 Failed to add the resource due to e
rror in the resource : javax.transaction.xa.XAException: Attempt to start transa
ction while transaction Xid( Global Id c0.a7.ff.20.b0.22.00.00.0c.00.00.00.00.00
.00.00.00.00.00.00.00.00.00.00, Format Id 4660, Branch Id 7d.20.c6.d9.00.00.00.0
0.00.00.00.00.00.00.00.00) is active. errorcode : -6 : Enlistment of resource fa
iled. Attempt to start transaction while transaction Xid( Global Id c0.a7.ff.20.
b0.22.00.00.0c.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00, Format Id 4660, Bra
nch Id 7d.20.c6.d9.00.00.00.00.00.00.00.00.00.00.00.00) is active.
followed, after a few seconds, by the following stack trace:
06/07/21 16:13:30 Got message: PING
06/07/21 16:13:30 MQJMS3011: Failed to publish message to MQ queue
06/07/21 16:13:30 javax.jms.JMSException: MQJMS3011: Failed to publish message t
o MQ queue
06/07/21 16:13:30 at com.ibm.mq.jms.services.ConfigEnvironment.newExceptio
n(ConfigEnvironment.java:553)
06/07/21 16:13:30 at com.ibm.mq.jms.MQMessageProducer.publish(MQMessagePro
ducer.java:1855)
06/07/21 16:13:30 at com.ibm.mq.jms.MQMessageProducer.send(MQMessageProduc
er.java:976)
06/07/21 16:13:30 at com.ibm.mq.jms.MQMessageProducer.send(MQMessageProduc
er.java:1056)
06/07/21 16:13:30 at oracle.j2ee.ra.jms.generic.CommonProducerWrapper.send
(CommonProducerWrapper.java:121)
06/07/21 16:13:30 at MyChannel.send(MyChannel.java:73)
06/07/21 16:13:30 at Dealer.onMessage(Dealer.java:210)
06/07/21 16:13:30 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native M
ethod)
06/07/21 16:13:30 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMet
hodAccessorImpl.java:39)
06/07/21 16:13:30 at sun.reflect.DelegatingMethodAccessorImpl.invoke(Deleg
atingMethodAccessorImpl.java:25)
06/07/21 16:13:30 at java.lang.reflect.Method.invoke(Method.java:585)
06/07/21 16:13:30 at com.evermind.server.ejb.interceptor.joinpoint.EJBJoin
PointImpl.invoke(EJBJoinPointImpl.java:35)
06/07/21 16:13:30 at com.evermind.server.ejb.interceptor.InvocationContext
Impl.proceed(InvocationContextImpl.java:69)
06/07/21 16:13:30 at com.evermind.server.ejb.interceptor.system.DMSInterce
ptor.invoke(DMSInterceptor.java:52)
06/07/21 16:13:30 at com.evermind.server.ejb.interceptor.InvocationContext
Impl.proceed(InvocationContextImpl.java:69)
06/07/21 16:13:30 at com.evermind.server.ejb.interceptor.system.SetContext
ActionInterceptor.invoke(SetContextActionInterceptor.java:34)
06/07/21 16:13:30 at com.evermind.server.ejb.interceptor.InvocationContext
Impl.proceed(InvocationContextImpl.java:69)
06/07/21 16:13:30 at oracle.j2ee.connector.messageinflow.MessageEndpointIm
pl.invokeMessageInflowCallbacks(MessageEndpointImpl.java:294)
06/07/21 16:13:30 at MessageListener_MessageEndpoint1.onMessage(MessageLis
tener_MessageEndpoint1.java:39)
06/07/21 16:13:30 at oracle.j2ee.ra.jms.generic.WorkConsumer.run(WorkConsu
mer.java:237)
06/07/21 16:13:30 at oracle.j2ee.connector.work.WorkWrapper.runTargetWork(
WorkWrapper.java:242)
06/07/21 16:13:30 at oracle.j2ee.connector.work.WorkWrapper.doWork(WorkWra
pper.java:215)
06/07/21 16:13:30 at oracle.j2ee.connector.work.WorkWrapper.run(WorkWrappe
r.java:190)
06/07/21 16:13:30 at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worke
r.run(PooledExecutor.java:814)
06/07/21 16:13:30 at java.lang.Thread.run(Thread.java:595)
In the Dealer code, I found a piece of code that randomly generating a junk message and marking the transaction for rollback. If I comment out this code, everything works fine.
So, even when I managed to make the demo work, the transactional stuff is not working.
It would be really nice to know what is going on, but I'm tired, its fiday and I'm clueless...
Now, for the "Unable to load message properties file - mqji(xx).properties", it is still showing up, but as you said, MQ seems to work fine.
Thank you very much again Jeff for your invaluable and extremely responsive help.
References:
I can't seem to find an demo that was very useful for me for setting up MQ in the Oracle site, but the direct links seem to still be working:
http://www.oracle.com/technology/tech/java/oc4j/1003/how_to/jcajmsmq/doc/readme.html
http://www.oracle.com/technology/tech/java/oc4j/1003/how_to/jcajmsmq/doc/Install.html
and the sample code and scripts:
http://otn.oracle.com/tech/java/oc4j/1003/how_to/jcajmsmq.zip
Message was edited by:
pablokrause

XI to IBM Websphere Default JMS Provider with JNDI

Similar Messages

Maybe you are looking for