OATS–Oracle Application Testing Suite–Performance testing JDE

OTS can be found here http://www.oracle.com/technetwork/oem/app-test/index.html

Full download here http://www.oracle.com/technetwork/oem/app-test/index-084446.html

This is the version 9.3 complete install.  Wow, only 1.4GB download!

The installer is pretty big, it’s going to install WebLogic 10.3.3 and also a XE database locally – so probably best to put it on a separate machine and it might have to be chunky (see specs below).  If you are using Oracle as your thick client local database, you might want to consider using a different machine also.

openscript is the first thing that you will run.  This gives you the ability to create scripts and test them.  I created a simple “load testing” HTML script:

This logged into JDE, did some address book queries and logged out again, nice and simple.

I was able to run this in the openscript console – all great. Note that this was using a weblogic 11G web server and tools release 8.98.4.5.

I tend to model core transactions for my clients, and try to create “a day in the life of X”.  I create different scenarios that stress different areas of the architecture.  Data manipulation, master BSFNs and UBEs for the back end.  Looking at lots of data and large grids, traversing menus for the web server and finally complex queries for the database.

I tend to stress the different tiers to get the low hanging fruit in the beginning.  Ensure that I have the correct JVM sizes and ensure that all logging is at a minimum.  It’s quite common that you’ll need to revise the concurrent connections in the jdbj.ini file for high usage.  I try and execute the “day in the life”

My favourite stress test / performance test for JDE is a “2 hours of power”.  Smash the machine with as many concurrent users (20% more than they anticipate) for 2 hours.  Ensure that the performance metrics are evan.  Check the JVM sizes and ensure they have not gone bad.  Ensure that ALL your transactions have hit the database (reconcile your load test).  Ensure that there is NO errors in the JAS logs and the enterprise server logs.  Too often a load test is “successful”, but has not completed properly at the back end.

Next thing you need to do is run some load testing, this is done within the web interface that runs within weblogic.

You need to start weblogic using startweblogic.cmd from within E:\oracleATS\oats dir – or where ever yours installed to:

The default URL is http://localhost:8088/olt/LoginSubmit.do

Oracle Application Automated Testing Suite default username is Administrator.  Why is this type of information very hard to find…

Login into the Test Manager or Admin console as Administrator with the password that you typed into the installation wizard.

Create a new scenario.  This is where you choose one or more of your “Tests”, as created within openscript. 

You choose concurrent VUs (virtual users), wait time options etc.  You can also choose where the script is going to run (system).  Then goto your “setup autopilot” tab:

By default the test will complete when you press STOP, you might want to change that… Run the test and watch the users in server manager.  You should see all of the screens changing when monitoring users.

This is the basics of OATS.  I know that it works with weblogic and 8.98.4.2 and 8.98.4.5.

I did some much more complicated load testing and OATS was a pleasure to use.  The remote agents were easy to configure too.  I used an underpowered test machine, I would recommend using a machine with a couple of processors, 8GB of memory and ensure that it’s GB LAN for the local load testing.