Register or Login to Your Account
Hi webMethods Experts,
I am trying to create a SOAP over JMS web service.
1.Created Destination (queue) called "ClientQueue" with group "SOAP_JMS_Group"
2.Created JMS Connection Alias with the following properties.
-->Transaction Type: No Transaction
-->NATIVE WEBMETHODS API
-->Client Group :SOAP_JMS_Group
3.Created SOAP-JMS trigger, specified the above JMS Connection alias and Destination "ClientQueue" in that trigger.
4.Created Endpoint Alias for Provider with Transport Type JMS.
Type : Provider
Transport Type : JMS
JMS Trigger Name :Architect.SOAP_JMS:soap_jms_trigger
Delivery Mode : PERSISTENT
Time to Live :0
Reply To Name :
Reply To Type :
5.Created Provider for a flow service with SOAP 1.1 and JMS
6.With that provider WSDL created Consumer
when i am trying to run the connector of consumer i am getting the following error.
Exception --> org.apache.axis2.AxisFault: Unable to send SOAP-JMS message: [ISS.0134.9009] Unable to send message to JMS provider "DEFAULT_IS_JMS_CONNECTION": com.wm.app.b2b.server.jms.JMSSubsystemException: javax.jms.JMSSecurityException: [BRM.10.5001] JMS: No send permissions for event type "JMS::Queues::wseQueue_SOAP_JMS_Alias" in client group "IS-JMS"
This error will come when you don't have topics defined for document types at the broker, which you want to publish the doc. I think you have to add a topic to that broker.
For Adding a Topic-[/b]
Go to My webMethods Server and log in as Administrator
- Enter into Administration -> Messaging -> Broker Servers -> Document Type->Add Topic.
then you should:
- Go to My webMethods Server and log in as Administrator
- Enter into Administration -> Messaging -> Broker Servers -> Client Groups
- Locate the "IntegrationServer" client group and enter into its details
- In its "Can Publish" and "Can Subscribe", add the document types you will be handling.
Please precise the provider name, the Queue Lookup Name and the Connection Factory Lookup Name.
If you already done with that, then check all configuration onec again.
[b]Check for your errors at SAG Error documentation:[/b]
Hope this helps