This content has been marked as final.
Show 4 replies
-
1. Re: SAP as a JMS provider
lightguard Dec 9, 2008 4:21 PM (in response to lightguard)Oops... ignore that user name and password. Looks like I can't edit the message.
-
2. Re: SAP as a JMS provider
adrian.brock Dec 16, 2008 10:26 AM (in response to lightguard)I doubt you can access the SAP jndi server using jnp?
jnp is the jboss jndi protocol name. -
3. Re: SAP as a JMS provider
adrian.brock Dec 16, 2008 10:28 AM (in response to lightguard)"adrian@jboss.org" wrote:
I doubt you can access the SAP jndi server using jnp?
jnp is the jboss jndi protocol name.
I also doubt SAP call their jms ConnectionFactory binding UIL2XA...
that's the jbossmq name. -
4. Re: SAP as a JMS provider
lightguard Dec 22, 2008 10:00 PM (in response to lightguard)Thanks for the reply Adrian. No, I can't access the SAP queues or Connection factory that way, I had to use their JNDI lookups:
<mbean code="org.jboss.jms.jndi.JMSProviderLoader" name="jboss.mq:service=JMSProviderLoader,name=RemoteSAPJMSProvider,server=sdaxipi.octanner.com"> <attribute name="ProviderName">RemoteSAPJMSProvider</attribute> <attribute name="ProviderAdapterClass">org.jboss.jms.jndi.JNDIProviderAdapter</attribute> <attribute name="QueueFactoryRef">jmsfactory/default/XAQueueConnectionFactory</attribute> <attribute name="TopicFactoryRef">jmsfactory/default/XATopicConnectionFactory</attribute> <attribute name="Properties"> java.naming.factory.initial=com.sap.engine.services.jndi.InitialContextFactoryImpl java.naming.provider.url=sdaxipi.octanner.com:50204 java.naming.security.principal=xxx java.naming.security.credentials=yyy </attribute> </mbean>
But then it comes back with a JMSSecurityException: You do not have consume permission... The more I've dug into this over the weeks it seems like it's SAP's problem.