Mule Flow only for Integration Testing - mule

I have got the Mule 4 application which is driven by Scheduler to schedule every 30 minutes. I have added http listener under the file test-listener.xml just for invoking it for building the integration testing.
I want the test-listener.xml to be deployed only into non-production environment. How can I achieve it in Mule 4.3.0 Runtime
Thanks

Adding an HTTP Listener to test the flow is not a good practice. If you are interested on just testing the flow just use MUnit to implement tests of the flow. If you are interested on testing the scheduler execution you can use this method with MUnit: https://docs.mulesoft.com/munit/2.3/test-flow-with-scheduler-cookbook

Related

Any REST endpoint which prioritize/update the bamboo build queue?

Any REST endpoint which prioritize/update the bamboo build queue?
http://host:8085/rest/api/latest/queue?expand=queuedBuilds
want to automate this process using python for release builds to reduce the waiting time.
Checked above endpoint , but it only add/delete builds from queue. want to move up the bamboo builds which has high priority.
Per the latest Bamboo REST API documentation (6.10.3) there is not a way to do this without creating something custom or using a third party plugin.

Is it Possible to use RPC while writing Test cases for flows in corda?

Not able to access RPC client while writing test cases for flows in corda
To test node RPC calls, you need to create integration tests using the node driver. See an example here: https://github.com/corda/cordapp-example/blob/release-V3/java-source/src/integrationTest/java/com/example/DriverBasedTests.java.

Spring boot websocket test

I have a spring boot project with websocket and I want to test the project sending multiple request to the socket from different users. I want to use threads to imitate the users that send data from the web app but I don't know exactly how to make the test. Can anyone help me, and show one simple test for an websocket using threads?
You can use JMeter for testing your websocket project.
For further reading:
https://www.blazemeter.com/blog/websocket-testing-apache-jmeter
http://www.baeldung.com/websockets-spring
Good example:
https://github.com/Fyro-Ing/JMeter-WebSocket-StompSampler
When writing a Spring Boot application using STOMP on websockets, I struggled a lot to find out how to configure a test client.
I ended up writing a little library called Jackstomp to make it easier to create type-safe tests for STOMP WS applications using JSON as message body.
I haven't used it with multiple threads, but you should be able to easily use it within each thread to create independent clients for each user and perform basic operations. (Please note that a different client should be used in each thread).
The point is that you can really express a synchronous flow for each client, including actively querying for received events.
Even if you don't use this library, you can look at the code to get a grasp of the different things to setup.

Footprint of integration applications in Mule ESB

I want to have a shared Mule ESB server where I'm going to deploy many integration apps. Most of them are similar but with different parameters and they have to be independent from each other.
I want to know how many integration applications can a deploy in one Mule ESB container. I'm not so worried about CPU usage because that's easily balanced having many servers, but I'm more concerned about memory usage or any other Mule ESB limitation.
I understand that memory usage of integration apps depends on the integration you are deploying to Mule ESB, but would be good to understand the overhead of deploying of a new app. Does it load all Mule classes again? Does it reuse what's already loaded? All applications are active all the time consuming memory or they are put to sleep while they are inactive?
For example, deploying Mule ESB without apps consumes 100MB, then deploying one app consumes 120MB, can I conclude that each integration application of the same type will consume 20MB?

Mule ESB integration with web applications

We have more than 5 corporate applications running on different servers with technologies like spring, struts communication between these application is point to point. We are planning to migrate this to ESB using Mule.
I didnt quite understand how mule works i have few doubts,
Mule is running in a different server do i need to deploy all my 5 aplications into the mule server.
I have spring application delployed on a tomcat server how this application is going to receive messages through mule or what are the configuration changes i need to do in my server or mule server.
Any advice or tutorials.
You need not deploy all you 5 applications in the Mule Server.
You said that all your application are currently point to point (which means that all are talking/communicating now through http protocol), similarly you can also use mule's http endpoints to communicate with all the 5 applications.
I.e. the spring application talking to another spring application can be modified to Spring application talking to Mule and Mule in turn talking to another Spring application .
You must learn the basics from the Documentation
http://www.mulesoft.org/documentation/display/current/Mule+Fundamentals --> browse through the navigation on the lefthand side.
Mule is an integration tool. you no need to change any of your existing applications. All you need is to develop an mule application which can do the mediation/orchestration.
For connecting with your spring application you no need to change any configuration you need to use http:outbound connector inside your mule flow
Just go through http://www.mulesoft.org/documentation/display/current/HTTP+Transport+Reference
So mule is based on SOA principle, so your 5 corporate service need not to be their in a single system. so if you want to consume the service/functionality of any of your 5 application, expose those service as web service, cloud be soap or rest. And you can call those service inside your mule. so in this case you have to create only 5 connection and where ever required you can refer to those connection inside mule configuration file.
#saravanan shanmugavel you need to use Mule ESB to orchestrate the communication between these application...ESB came into the picture to remove your point to point communication...you can create a proxy service for each of your service and one flow which will orchestrate communication between all...
All you need to do is change the application that is configurable according to mule server.
Please refer below link that will be helpful for understanding of mule that helps you better orchestrate communication between all.
https://docs.mulesoft.com/