XI JMS adapter after JMS provider reboot

Hi All,
I have problem with XI JMS adapter. Adapter is in a JMS client role and JMS provider is Tibco. After reboot of JMS service in JMS provider, XI JMS adapter loose username and pw in connection and try logon to queue as an anonymous user.
After deactivation + activation of XI JMS adapter, connection seems to work correctly with uname & pw.
In JMS adapter we have folloving settings and we are connected straight into queue:
Transport Protocol = SonicMQ JMS Provider
General JMS Settings:
Transactional JMS Session is in use
Delivery Mode of Message Producer = Persist JMS messages..
+ Queue user & pw
Error Handling Settings:
Wait After Message Error(msecs) = 60000
Wait Before Reconnect(msecs) = 60000
Does anyone ran into this earlier?
Thanks in advance.
-Kimmo

Hi Saravana,
It seems that no connection is available to queue. In JMS adapter are you using correct path for finding these provider specifig classes in front of class name. Example: javax.jms.QueueConnectionFactory
It is also possible that username of JMS provider which you configure to JMS adapter does not have correct rights for reading/writing or accessing to queue.
We are not using any additional settings for JMS adapter. For server name we have also added protocol which is tcp://<servername> and using transactional JMS session.
We had this same error when trying connect to queue via JNDI. Then we changed JMS adapter to connect straight to queue and it started to work.

Similar Messages

Problem with JMS Adapter after upgrade to 7.1

Hi All,
After an upgrade the JMS adapter connecting IBM Websphere MQ gives the following error:
Error connecting due to missing class: com.ibm.mq.jms.MQQueueConnectionFactory. Ensure that all resources required are present in the JMS provider library: aii_af_jmsproviderlib.sda
Since we are now on PI 7.1, the directory the JMS adapter should be looking for the libraries should be com.sap.aii.adapter.lib.sda. Has anyone else come across this problem after an upgrade? Should we remove the old aii_af_jmsproviderlib.sda?
Edited by: Luqman on Oct 31, 2008 5:39 PM

does following JAR files in place in aii_af_jmsproviderlib.sda.
●      com.ibm.mq.jar
●      com.ibm.mqbind.jar
●      com.ibm.mqjms.jar
●      connector.jar (use the JAR file from the J2EE client directory)
can u check n confirm.
i hopw u have followed the proper deployement process.
chirag

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?

JMS Adapter Configuration (Access JMS Provider Generically)

Hi Exports,
How can i configure JMS adapter Using Access JMS Provider Generically, where can we mentioned target server. there is Quename and username and password but there is no target server details field. could you please give me suggetion how to configure this.

Hi,
This will help you
JMS Adapter
/people/kan.th/blog/2007/02/05/exploring-jms-and-sap-xi-jms-adaper
http://help.sap.com/saphelp_nw2004s/helpdata/en/cd/d85a9d6fab7d4dbb7ae421f710626c/content.htm
Sender Jms Adapter
http://help.sap.com/saphelp_nw2004s/helpdata/en/f4/2d6189f0e27a4894ad517961762db7/content.htm
Receiver Jms Adapter
http://help.sap.com/saphelp_nw2004s/helpdata/en/10/b1b4c8575a6e47954ad63438d303e4/content.htm
Regards
Agasthuri Doss

How to integrate Websphere MQ as an external JMS Provider?

Hello to all!
I'm trying to integrate Websphere MQ in SAP Web AS 6.40 as an external JMS provider and I'm having some problems. As the use of SAP XI is impossible for me, I started using the built-in JMS Connector.
I've already read (and tried to follow) the documentation in http://help.sap.com/saphelp_nw04/helpdata/en/cd/4d4941abbb4c0de10000000a1550b0/frameset.htm, but unfortunately, it didn't help me that much.
It told me that the JMS Connector is the right place to start, and I already managed to deploy and define the Websphere MQ JMS implementation as a library. And from various examples I'm quite sure that Websphere MQ is an JNDI based JMS provider. But now the problems start.
According to the SAP library mentioned above, I have to enter the JNDI name to the ConnectionFactory in the "New ConnectionFactory" dialogue in the "Provider" tab. As an example there is the (existing) JNDI name "jmsfactory/default/TopicConnection". For doing the same with my Websphere MQ, I expect to need something alike.
Hoping that I'm getting the SAP library right at this point, I'm expecting to need a JNDI entry, like, let's say, "jmsfactory/WebsphereMQ/QueueConnection" connected to the class "com.ibm.mq.jms.MQConnectionFactory" (MQConnectionFactory is the class in the MQ JMS implementation that implements the JMS interface "Connection Factory"). How can I put those Websphere MQ classes, that are implementing the JMS interfaces like Connection Factory, QueueConnectionFactory and so on
in my JNDI tree? The point is, obviously, no JNDI entry was made during deploying Websphere MQ as a library.
Or am I totally wrong an misunderstood the SAP library completely? Any help on this topic would be highly appreciated.
Best greetings!
Bärbel

Integrating WebSphereMQ with SAP Web Application Server
Prerequisites
The native libraries of WebSphereMQ must be added to the environment variables of the host or hosts where the SAP Web AS is running. Typically, if MQ is installed on the same host, the required entries are added to the environment at installation. However, we recommend that you check the MQ documentation for details about the directory where the libraries are located, and make sure it is added to the environment on all hosts with SAP Web AS.
For example, for Windows OS the following libraries are required:
- amqmtmgr.dll
- amqvwaa2.dll
- amqxcs2.dll
- amqxcsn.dll
- amqzc.dll
- amqzsai.dll
- amqzst.dll
- amqztm.dll
- mqjbdf02.dll
- mqjbnd05.dll
- mqm.dll
- mqmvxd.dll
- mqmxa.dll
- MQXAi02.dll
Procedure
1) If the version of the SAP Web AS is SP 7 or lower, you must apply a patch for the JMS Connector Service. The required SDA is attached to this e-mail (jmsconnector.sda). To apply it:
a. Run the SDM Remote GUI tool. It is located in <SAP_install_dir>\SAPSID\<Instance_ID>\SDM\program.
b. In the Deployment tab, add the jmsconnector.sda to the deployment list. Choose Show Deployment Configuration. Select Update deployed SDAs/SCAs that have any version (this ensures that you will have the SDA deployed even if for some reason its timestamp is older than the one of the SP7 SDA that you already have deployed.)
c. Deploy the SDA following the standard deployment procedure. If prompted to choose if you want to delegate the control to the SDM server, choose Yes. The SDM shuts down the cluster, deploys the SDA, and then restarts the cluster.
2) Create the IBM MQ library. You can do it using either Visual Administrator or SAP NetWeaver Developer Studio.
a. Visual Administrator:
i. Go to Services -> JMS Connector.
ii. Select JMS Libraries, and choose New.
iii. Enter a name for the library, such as MQJMSLIB.
iv. Browse to select the following JAR files:
- com.ibm.mq.jar
- com.ibm.mqbind.jar
- com.ibm.mqjms.jar
- fscontext.jar
- ldap.jar
- postcard.jar
- provider.xml
- providerutil.jar
v. Deploy the library.
vi. Go to Services -> Configuration Adapter. In the configuration tree on the right-hand side of the screen browse to cluster_data -> server -> cfg -> ext -> MQJMSLIB-provider.xml. Switch to edit mode using . Open the XML for editing using . Add the following entry (after the reference entry for jms):
<reference type="library" strength="weak">j2eeca</reference>
Choose OK and restart the cluster to apply the changes.
b. SAP NetWeaver Developer Studio:
i. Create a J2EE Library project.
ii. Select the project and choose File -> Import -> File System. Browse to the MQ folder, which contains the JAR files listed above, and select to import them.
iii. Extend the tree of your library project and open server/provider.xml. Go to the Jars tab.
iv. Select Jars, and choose Add. Choose to add the JAR files that you have imported in the previous step.
v. Go to the References tab. Select References, and choose Add. Choose Select library/interface/service. In the list select jms and j2eeca.
vi. Save and close provider.xml. From the context menu of the library project choose Build Library Archive.
vii. Select the SDA in the project tree, open its context menu, and choose Deploy to J2EE Engine.
3) Create a JMS Connector Factory in Visual Administrator.
You can either enter the required values directly in the Visual Administrator (Services -> JMS Connector), or you can edit the following sample deployment descriptors and import them in Visual Administrator using .
a. Using JNDI:
This is example of factories.xml using JNDI based JMS provider.
<?xml version="1.0" encoding="UTF-8" ?>
<jms-factories>
 <application-name>
 IBM_Test_App
 </application-name>
 <connection-factory>
 <library-name>
 MQJMSLIB
 </library-name>
 <factory-name>
 IBM_Queue_Factory
 </factory-name>
 <context-factory-type>
<!This factory should already exist on WebSphereMQ.-->
 <link-factory-name>
 QCF_1
 </link-factory-name>
 <initial-context-factory>
 com.sun.jndi.fscontext.RefFSContextFactory
 </initial-context-factory>
 <provider-url>
 file:/C:/JNDI-Directory
 </provider-url>
 <security-principal>
 </security-principal>
 <security-credentials>
 </security-credentials>
 </context-factory-type>
 </connection-factory>
</jms-factories>
b. Using object factory JMS provider
<?xml version="1.0" encoding="UTF-8" ?>
<jms-factories>
 <application-name>
 IBM_Test_App
 </application-name>
 <connection-factory>
 <library-name>
 MQJMSLIB
 </library-name>
 <factory-name>
 IBM_Queue_Factory
 </factory-name>
 <object-factory-type>
 <object-factory-name>
 com.ibm.mq.jms.MQXAQueueConnectionFactoryFactory
 </object-factory-name>
 <class-name>
 com.ibm.mq.jms.MQXAQueueConnectionFactory
 </class-name>
 <properties>
 <property>
 <property-name>
 HOST
 </property-name>

 <property-value>
 localhost
 </property-value>
 </property>
 <property>
 <property-name>
 QMGR
 </property-name>

 <property-value>
 MQ_default
 </property-value>
 </property>
 <property>
 <property-name>
 PORT
 </property-name>

 <property-value>
 1414
 </property-value>
 </property>
 <property>
 <property-name>
 TRAN
 </property-name>

 <property-value>
 1
 </property-value>
 </property>
 </properties>
 </object-factory-type>
 </connection-factory>
</jms-factories>
4) Use the connection factory in an application:
Code:
Context ctx = new InitialContext();
Object ref = ctx.lookup("java:comp/env/IBM_Queue_Factory");
QueueConnectionFactory f = (QueueConnectionFactory)ref;
QueueConnection connection = f.createQueueConnection();
Resource references:
 <resource-ref>
 <res-ref-name>
 IBM_Queue_Factory
 </res-ref-name>
 <res-type>
 javax.jms.QueueConnectionFactory
 </res-type>
 <res-auth>
 Container
 </res-auth>
 </resource-ref>
If you are using 6.40 SP7 or below let me know to send you a patch.
Regards Nikola

JMS : Using SUN MQUEUE as a JMS Provider

Hi guys,
I'm having quite some trouble in configuring a JMS scenario...
I'm using SUN MQueue as a JMS Provider. I've installed the respective drivers, imq.jar, fscontext.jar and jms.jar.
I had no trouble in deploying this drivers on the SDM.
Now, after creating a receiver JMS communication channel, I get the following error on the RWB:
Error during channel initialization; exception trace: java.lang.NoSuchMethodException: com.sun.messaging.QueueConnectionFactory.(java.lang.String)
at java.lang.Class.getConstructor0(Class.java:1937)
at java.lang.Class.getConstructor(Class.java:1027)
at com.sap.aii.af.service.jms.WorkerJMSSender.init(WorkerJMSSender.java:474)
I've searched XI logs, in order of getting some light on the subject...This was what I've got:
#com.sap.aii.af.service.jms.WorkerJMSSender.init(WorkerHandler moduleHandler, Object para)#J2EE_GUEST#0####975a11b0c58b11dbce6700145e1855ec#SAPEngine_Application_Thread[impl:3]_19##0#0#Error##Java###Unable to create the QueueConnectionFactory due to #1#SUNMQUEUE_IP:SUNMQUEUE_Port#
My question is what is #1#....
I've read a few forum threads, but none of them can clarify my error....
I've tried the same scenario using Business Connector...Of course, in BC I had to create 2 JAVA services, one for sending and another for receiving messages...there was no problem with this, I did managed to send JMS Messages to SUN MQUEUE...
Can anyone give a hint....anything...?

Hi,
This is something related to JMS Adapter configuration settings and security ...
please check .. all your settings..
This is the SonicMQ implementation of the QueueConnectionFactory.
A JMS client, in this case the adapter, uses a QueueConnectionFactory object to generate QueueConnection objects of a JMS provider.
The default value for SonicMQ 3.0 is progress.message.jclient.QueueConnectionFactory
See also..below links
http://help.sap.com/saphelp_nw04/helpdata/en/c1/739c4186c2a409e10000000a155106/content.htm
Installation problem: Central Instance 6.40 Oracle on Linux 32
Regards
Chilla..

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

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

Problem in configuring third party JMS provider

Hi,
I am having a problem in configuring Sun MQ 4.4 JMS provider with weblogic 10.3.I tried the following method:-
1. Created a new outbound connection pool.
2.In the properties for the connection pool :-
ConnetionFactory Location :- myTestCF (this is the remote connection factory JNDI)
Factory properties :- java.naming.factory.initial=com.sun.jndi.fscontext.RefFSContextFactory;java.naming.provider.url=file:/C:/my_object_store;java.naming.security.principal=admin;java.naming.security.credentials=admin
3.Provided the username and password also.
But when I am testing it from a SOA composite through a JMS adapter, it is giving me an exception indicating it could not locate the connection factory.I am clueless why this is happening.I've also tried with putting the sun mq jar files inside the <%wl_home%>/user_projects/domains/<%my_domain%>/lib folder.But it did not work.Please help.
Thanks,
Rahul

In third party process SO / PR / PO should be in integrity. Your manual modification violates this I think (you are making one PO item from two SO item...).
http://help.sap.com/erp2005_ehp_04/helpdata/EN/dd/560287545a11d1a7020000e829fd11/frameset.htm
Processing Third-Party Orders in Purchasing
When you save a sales order that contains one or more third-party items, the system automatically creates a purchase requisition in Purchasing. Each third-party item in a sales order automatically generates a corresponding purchase requisition item. During creation of the requisition, the system automatically determines a vendor for each requisition item. If a sales order item has more than one schedule line, the system creates a purchase requisition item for each schedule line.
Purchase orders are created from purchase requisitions in the usual way. For more information about creating purchase orders, see the Purchasing documentation. During creation of the purchase order, the system automatically copies the delivery address of your customer from the corresponding sales order. In a sales order, you can enter purchase order texts for each third-party item. When you create the corresponding purchase order, the texts are automatically copied into the purchase order. The number of the purchase order appears in the document flow information of the sales order.
All changes made in the purchase order are automatically made in the sales order as well. For example, if the vendor confirms quantities and delivery dates different from those you request and enters them in the purchase order, the revised data is automatically copied into the sales order.
Regards,
Csaba

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

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

Latest Versions of SonicMQ JMS Provider supported by PI71

Hello Experts,
I have a query on PI-JMS Adapter, where SonicMQ-JMS Provider will be used. As per the below link :
http://help.sap.com/saphelp_nwpi71/helpdata/en/cd/d85a9d6fab7d4dbb7ae421f710626c/frameset.htm
I do know that the version of SonicMQ supported by PI7.1 is 3.0.
But can anyone please tell me which all are the versions of SonicMQ (uptoV7.5) been supported by PI7.1??
Thanks,
Santanu

Download Firefox 3.6.19 from here:
* http://www.mozilla.com/en-US/firefox/all-older.html
* Save the File on your Desktop
Uninstalling Firefox
* https://support.mozilla.com/en-US/kb/Uninstalling%20Firefox
Installing Firefox on Windows --- Install the Downloaded Firefox 3.6.19 version
* https://support.mozilla.com/en-US/kb/Installing%20Firefox%20on%20Windows
Check and tell if its working.

JMS Provider Responsibilities For Concurrent Message Delivery

Hi,
(This question pertains to the JMS api, outside a j2ee container)
Is it JMS-provider dependent on how concurrent message delivery is implemented? In other words, the code below sets up multiple consumers (on a topic), each with their own unique session and MessageListener and then a separate producer (with its own session) sends a message to the topic and I observer that only (4) onMessage() calls can execute concurrently. When one onMessage() method exits, that same thread gets assigned to execute another onMessage().
The only thing I could find on the matter in the spec was section in 4.4.15 Concurrent Message Delivery and it's pretty vague.
It's really important because of the acknowledgment mode. If it turns out that I need to delegate the real work that would be done in the onMessage() to another thread that I must manage (create, pool, etc), then once the onMessage() method completes (i.e., after it does the delegation to another thread), the message is deemed successfully consumed and will not be re-delivered again (and that's a problem if the custom thread fails for any reason). Of course, this assumes I'm using AUTO_ACKNOWLEDGE as the acknowledgment mode (which seems to make sense since using CLIENT_ACKNOWLEDGE mode will automatically acknowledge the receipt of all messages that have been consumed by the corresponding session and that's not good).
My JMS Provider is WL 9.1 and the trival sample code I'm using as my test follows below. I also show the ouput from running the example.
thanks for any help or suggestions,
mike
--- begin TopicExample.java ---
import java.io.*;
import java.util.*;
import javax.naming.*;
import javax.jms.*;
import javax.rmi.PortableRemoteObject;
class TopicExample {
public final static String JMS_PROVIDER_URL = "t3://localhost:8001";
public final static String JNDI_FACTORY="weblogic.jndi.WLInitialContextFactory";
public final static String JMS_FACTORY="CConFac";
public final static String TOPIC="CTopic";
public final static int NUM_CONSUMERS = 10;
public static void main(String[] args) throws Exception {
InitialContext ctx = getInitialContext(JMS_PROVIDER_URL);
ConnectionFactory jmsFactory;
Connection jmsConnection;
Session jmsReaderSession[] = new Session[10];
Session jmsWriterSession;
TextMessage jmsMessage;
Destination jmsDestination;
MessageProducer jmsProducer;
MessageConsumer jmsConsumer[] = new MessageConsumer[10];
MessageListener ml;
try
// Create connection
jmsFactory = (ConnectionFactory)
PortableRemoteObject.narrow(ctx.lookup(JMS_FACTORY), ConnectionFactory.class);
jmsConnection = jmsFactory.createConnection();
// Obtain topic
jmsDestination = (Destination) PortableRemoteObject.narrow(ctx.lookup(TOPIC), Destination.class);
// Reader session and consumer
for (int i=0; i<NUM_CONSUMERS; i++)
jmsReaderSession[i] = jmsConnection.createSession(false, Session.AUTO_ACKNOWLEDGE);
jmsConsumer[i] = jmsReaderSession.createConsumer(jmsDestination);
jmsConsumer[i].setMessageListener(
new MessageListener()
public void onMessage(Message msg) {
try {
String msgText;
if (msg instanceof TextMessage) {
msgText = ((TextMessage)msg).getText();
} else {
msgText = msg.toString();
System.out.println("JMS Message Received: "+ msgText );
System.out.println("press <return> to exit onMessage");
char c = getChar();
System.out.println("Exiting onMessage");
} catch (JMSException jmse) {
System.err.println("An exception occurred: "+jmse.getMessage());
// Writer session and producer
jmsWriterSession = jmsConnection.createSession(false, Session.AUTO_ACKNOWLEDGE);
jmsProducer = jmsWriterSession.createProducer(jmsDestination);
jmsMessage = jmsWriterSession.createTextMessage();
jmsMessage.setText("Hello World from Java!");
jmsConnection.start();
jmsProducer.send(jmsMessage);
char c = '\u0000';
while (!((c == 'q') || (c == 'Q'))) {
System.out.println("type q then <return> to exit main");
c = getChar();
for (int i=0; i<NUM_CONSUMERS; i++)
jmsReaderSession[i].close();
jmsWriterSession.close();
jmsConnection.close();
System.out.println("INFO: Completed normally");
} finally {
protected static InitialContext getInitialContext(String url)
throws NamingException
Hashtable<String,String> env = new Hashtable<String,String>();
env.put(Context.INITIAL_CONTEXT_FACTORY, JNDI_FACTORY);
env.put(Context.PROVIDER_URL, url);
return new InitialContext(env);
static public char getChar()
char ch = '\u0000';
try {
ch = (char) System.in.read();
System.out.flush();
} catch (IOException i) {
return ch;
--- end code --
Running the example:
prompt>java TopicExample
JMS Message Received: Hello World from Java!
JMS Message Received: Hello World from Java!
press <return> to exit onMessage
press <return> to exit onMessage
JMS Message Received: Hello World from Java!
press <return> to exit onMessage
JMS Message Received: Hello World from Java!
press <return> to exit onMessage
type q then <return> to exit main
[you see, only 4 onMessage() calls execute concurrently. Now I press <return>]
Exiting onMessage
JMS Message Received: Hello World from Java!
press <return> to exit onMessage
[now once the thread executing the onMessage() completes, the JMS providor assigns it to execute another onMessage() until all 10 onMessage() exections complete).

I am too facing the same issue. but in my case I start getting this problem when the message size is about 1 MB itself.
Any help is appraciated.
Regards,
ved

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.

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

XI JMS adapter after JMS provider reboot

Similar Messages

Maybe you are looking for