Test & Monitor you APEX app. Part 1 : Monitor your APEX app using Jenkins
- Get link
- X
- Other Apps
This is the first of a series of posts where I will show you how you can use Jenkins, Selenium, JMeter and Maven to test, monitor and create a continuous integration pipeline for your APEX application.
This is part 1, Set-up Jenkins to monitor your APEX app and get alerted when your app is unavailable.
Creating a simple Jenkins job that takes 5 minutes to set up, your APEX application will be monitored 24 hours a day, and you will get alerted as soon as it becomes unavailable. You can then build on this using free open source software to run web (Selenium) and database (JMeter) tests on your APEX app controlled by Jenkins, which will I describe in upcoming posts.
In upcoming posts, I will show you how to set up Jenkins to;
Run web (Selenium) tests on your APEX application. Schedule web tests logging into your APEX app running tests using Selenium and Maven and get notified of any failures.
Schedule deployment of your APEX dev env nightly to a test env. Deploy your APEX app from your development environment to a test environment nightly, then run a suite of Selenium web tests and get notified of any failures.
Monitor your APEX DB. Run scheduled database checks on your APEX database using JMeter and get notified of any failures.
Load test your APEX app. Stress test your APEX application, logging in with thousands of users using JMeter distributed testing.
In this post I will also create a job to monitor our Apex Office Print server and get alerted if it's unavailable. These are the 2 Jenkins monitoring jobs I am going to set-up;
Prerequisite: Install Jenkins and the site monitor plugin. Jenkins is simple to set up and there are lots of online guides, so I won't go into it here.
Let's set up the monitor APEX application job. Log into Jenkins and press New Item (top left);
name it "Monitor APEX application", select Freestyle project and press OK;press configure;
set-up how often we want to monitor our APEX app, which will be every 5 minutes;
H/5 * * * *
(press the blue ? beside to the right of schedule to get help on setting up the schedule cron)
You can leave Success Response Codes empty, where it will check for 2XX codes by default.
Lastly, set up the email recipients who will get emailed if the app is unavailable;
Exactly the same steps for the Monitor AOP job, replacing the APEX URL with our AOP Server address.
It's free and took about 5 minutes to set the jobs up, my team now get alerted as soon as our APEX app or AOP server is unavailable. I have found this invaluable, as we now get alerted if there is an issue with our application, so we can try and fix it before any users report it.
Comments
Very good information on apex testing
ReplyDelete