0
votes

I am following an example to do the following: "Create an API with the JMS backend endpoint – Let’s now create an API within the API manager. You can follow the regular process when creating the API. As shown below, make sure you enable ‘POST’ HTTP verb when defining the resources.

Once this has been done, let’s add the JMS URL as the production endpoint. Select the endpoint type as ‘Address Endpoint’ from the endpoint type drop-down menu. The production URL would be the actual JMS endpoint. The JMS URL for an ActiveMQ message queue should something like this:

jms:/DataFeed?transport.jms.ConnectionFactoryJNDIName=QueueConnectionFactory&java.naming.factory.initial=org.apache.activemq.jndi.ActiveMQInitialContextFactory&java.naming.provider.url=tcp://localhost:61616&transport.jms.DestinationType=queue

In this case, the queue name is ‘DataFeed’, and Queue URL is localhost with port number 61616."

When I use the "Test" button to verify the URL. I get "invalid" but not sure what's not valid. I have DataFeed queue created in activeMQ and assume other variables are standard by using default values in activeMQ. Any idea how to get more meaningful message?

1

1 Answers

0
votes

AFIK this is the current behavior, URL tests only available for the http/https endpoints and for the other transport (like jms,RabbitMQ) seems this option not correctly work.

Even though, test option giving the "invalid" message you can check the URL functionality by sending a message using the API, then check whether the message correctly enqueue.