If upgrading from a previous version, here are some of the highlights and new features.
The following is a list of new features that directly affect most users and administrators.
Support for Input/Output variables definitions for rule sets. This enables included rule sets to work with variable names in isolation from its parent rule set.
You can now specify which rule groups can be used by the rules editor in a given repository. This allows for the segmentation between basic and advanced users.
The console now allows the administrator to assign one of two UIs (Classic or Portal) to a user. Users in portal mode will get a more limited view of options, but also a better ability to customize and save their preferred desktops.
The console now allows a single console to contain all extensions separated by version, the definition of a version against a repository and can control the deployment of rules so that the correct version of extensions are deployed only to servers that support that extension.
Version 8 rules engines are now capable of registering their own protocol support and can deploy network listeners on one or more network ports at start-up time. In addition, a new protocol analysis and breakdown feature has been added to facilitate rules writing against arbitrary network protocols. This is known as Outerware. Network transport supported includes TCP, SSL and UDP.
A new multi-protocol input adaptor has been introduced to assist with managing non-HTTP protocols.
The rules engine now supports "chatty" protocols (such as SMTP). This enables OctopusV8 support for protocols that have multiple interactions on the same network stream before an actual transaction occurs.
Constants provided to any rule may now include special characters escaped using the Java escape syntax ("\r" = CR, "\n"= LF etc.).
A number of new rules have been added including list management rules, stress testing rules and rules to deal specifically with protocols.
Repositories can now be closed so that they no longer appear in the administration tree. This is an alternative to deleting repositories, as closed repositories can be re-opened with a single click
A new Rules Wizard configuration and a new stress testing input adaptor allow for the capture of the flow of a web application and the play back of that flow in many threads, including customization with multiple users, semi-random wait times, ramp up time and the full set of rules to validate output.
It is now possible to switch modes (starting point rule sets), and set global variables specified in configurations, whilst a configuration is deployed and running.
When working with a large number of repositories and servers within a single console, this feature allows the user to cut down the number of visible repositories and servers at any given time.
The product now allows a single user to have more than one role.
A new debug mode is available for all input adapters. This replaces the previous debug mode used in test input adapters. The most significant use of this feature is the ability to make Exit rules list all variables in debug mode only. Exiting rules relying on test debug mode have also been updated to use the universal mode.
New built in project wizards can assist in creating project template with To Do lists for all parties involved and call also keep project sponsors and owners updated on the progress of a project.
The following is a list of major changes that are relevant to administrators and extension programmers.
The browser proxy now provides the ability to create on-the-fly valid certificates so that sites with HTTP Strict Transport Security still functions through the browser proxy and shows up as having a valid certificate. After installing the latest BIP Runtime extension, please refer to the Browser Certificate Installation Guide in the Certificates folder.
A new secondary rules engine designed specifically for breaking down network protocols has been introduced. This rules engine is only configurable by administrators, and even though extended through the normal extension process, carries a completely new programming model to facilitate the more technical aspect of protocol disassembly and assembly.
This new server type is specifically designed to handle implementations of OctopusV8 that are living outside an application server. It is effectively an extension of the feed server used in earlier versions.
Multi-protocol servers are capable of running and proxying SSL based protocols using the traditional Tomcat crt & key certificate files combination.
The VAO object now supports the use of keyed lists that can be accessed via key, enumerated, sorted and manipulated with add/delete/update.
Data sets represent a collection of variables that can be located with a key. Data sets are capable of being created into databases or into lists.
The update server can now be accessed using the user browser as a relay via cross-origin resource sharing. This allows consoles with no internet access to follow the usual update path.
Rule sets will now be locked to the first user that opens a rule set for editing. Users trying to access an already opened rule set will receive a notification that the rule set is locked and the save option will be disabled until an exclusive lock can be obtained.
Extensions are now provided to interact with LEDs, relays on switches using Raspberry Pi and the PiFace Digital board.
New wizards can now be delivered via extensions in the console UI. This allows wizards for a wide range of assistance functions in the console to be dynamically plugged in.