cancel
Showing results for 
Search instead for 
Did you mean: 

JMS adapter(MQSeries): Authorization check for queue access

rahul_kharya
Participant
0 Kudos

Hi All,

We are getting the same error as mentioned in the note no.749743 now we are following the note but we are not able to figure out what specific SP level we need to apply as it is very generalised.

And From where we can get a newer version of the JMS Adapter.

How can we test our configuration directory object? I cant see any test configuration option under tools menu.

Please help me out.

Thanks in Advance

Regards

rahul

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Rahul

Which Service Pack are you using currently? You can upgrade to SP 14 or 15 or 16. You ask your basis guys to download the higher version. Once you are done with that your problem will be solved. Also you look at this url which might help you:

https://websmp207.sap-ag.de/~form/sapnet?_FRAME=CONTAINER&_OBJECT=012003146900000283572005

Regards,

---Mohan

rahul_kharya
Participant
0 Kudos

Hi Mohan,

Thanks a lot for replying. need few more details. Actually i have defined my Transport Protocol as Websphere MQ(non JMS)in communication channel. But in JMS Connector->Factories->com.sap.xi.ibresources->jms/Queue/xi/QueueConnectionFactory, My provider type is defined as JNDI and my user and password is blank. There are only two options for provider type, one is JNDI and other is Object Factory. If Object Factory has to be selected what should be entered in provider tab(Object Factory Settings)?

please help us out.

Regards

Rahul

Former Member
0 Kudos

Rahul

Since you are using transport protocol as WebSphereMQ(Non-JMS)you have to provide some of the JMS Provider specific settings as mentioned in:

http://help.sap.com/saphelp_nw04s/helpdata/en/c1/739c4186c2a409e10000000a155106/content.htm

http://help.sap.com/saphelp_nw04s/helpdata/en/cd/d85a9d6fab7d4dbb7ae421f710626c/content.htm

---Mohan

rahul_kharya
Participant
0 Kudos

Hi Mohan,

Thanks a lot, We had followed both the documents which u had suggested us to follow.But we think this error may be because of JMS Connector Configuration in Our Visual Administrator. So can you please let me know what what settings we need to do in our Visual Admin.

Best Regards

rahul

Answers (0)