Arcturus AutoPilot WL Release Notes
 |
 |
 |
 |
JDK Support On Server
AutoPilot WL sp1 support JDK 1.4.1_01 onwards for Server side AutoPilot deployment. You can read more on Platform Support here.
Java Browser Plugin Support
With AutoPilot WL sp1 support for JDK 1.5 plugin is added. Now AutoPilot WL WebLogic Console extension works with JDK 1.4 and JDK 1.5 browser plugins.
Enhanced Load Runner Support
With AutoPilot WL sp1 we have improved our integration with Load Runner.
* Location of Load Runner directory can now be specified in autopilot.props file in case Load Runner is intalled in a directory other than the default directory.
* AutoPilot completly controls the load runner scenario including starting and stoping at the appropriate timings.
Simplified Initialization process for very large deployments
With AutoPilot WL sp1 we have improved intialization process for AutoPilot WL. Previous version encountered slowness in introspection process for RuntimeMBeans in case a WebLogic domain had more than 30 managed servers.
Support for Tuning Custom WebLogic Thread Queues
We have added support for Auto Tuning of custom WebLogic Thread queues with AutoPilot WL sp1. In case you are using custom weblogic thread queues you can define the WebLogic thread queue you want to tune in AutoPilot configuration.
Simplified Deployment
AutoPilot WL sp1 doesn't require any change to the classpath of the WebLogic where it is installed. All AutoPilot WL sp1 components are j2ee components and encapsulate all the required classes within.
Enhanced Knowledge Base
We have made more additions to our knowledge base since our previous release and AutoPilot WL with SP1 checks for more best practices.
Database Schema Change
If you are upgrading from previous version of AutoPilot, you will need to either recreate the database or add the new tables/indexes to the existing schema. Changes needed to the schema would depend on what version of AutoPilot you are upgrading from.