If the messaging queue is listening to a tcp url, what will be the possibility of Service Virtualization ?
From an architectural standpoint, Service Virtualization relies on the existing MOM platform/infrastructure, so if you're virtualizing a service that uses queues then a prerequisite to virtualization is to duplicate the inbound/outbound queues with the same properties (and the queue names are typically prefixed with "devtest" or some other meaningful/descriptive prefix. These queues will be used during recording and playback of the virtual service. A link to the documentation for virtualizing IBM MQ was provided in an earlier post, please refer to that.
Here is the information for TCP Virtualization:Virtualize TCP And this is information related IBM MQ VirtualizationIBM WebSphere MQ Transport Protocol
Here is the search URL from DevTest Documentation:https://docops.ca.com/devtest-solutions/10-3/en/docops-search-tips
If you cannot get the suitable information, then could you please explain in detail?
I am a little bit unclear if you are asking about TCP or MOM-based configurations.
If you are asking about connecting to MOM-based (i.e., JMS, Tibco, IBM, RabitMQ, etc.) queuing technologies, DevTest provides configurations for the Server URL in the form of what DevTest calls Connection Assets. Within these configurations a connection URL can be specified and these could be things like: tcp://serverName:port, t3://serverName:port, jnp://serverName:port, etc. The configuration required will be specific to the provider DevTest is connecting and you will need to ensure the provider technology's JAR files have been placed in LISA_HOME/lib/shared.
- Open the LISA_HOME/examples project in Workstation.
- Navigate to the Tests directory and open the jms.tst test case and you can see an example of a JMS configuration.
Retrieving data ...