New in Version 6

If upgrading from or have had exposure to a previous version, here are some of the highlights that were introduced in version 6.

Significant new features

The following are a list of major new features since version 5.0

Product consolidation

The console server and universal appliance have been consolidated into a single deployment. Only one installation will be shipped. If a feature is not desired from the deployment it can be deleted.

Easy rename of console files

A console file can now be renamed (configuration, rule set etc.), by giving it a new name and saving it.

New rules wizard

A new rules wizard now helps to build an initial collection of rule sets and a matching configuration based on collected test data.

Ability to add new console features via rules

The console itself is now protected with OctopusV8 and in addition it is now possible to add new features to the console itself as custom functions. An example showing how to maintain an IP address block list and how to add additional password rules is included in the default deployment.

Built in forwarding proxy configuration from the console

Any built in forwarding proxy (forwarder) can now be configured from the console instead of using the web.xml file. This configuration is performed at server level.

Built in appliance and web proxy

The server now ships with a built in forwarding proxy and web proxy deployed by default. Both the appliance and web proxy are available from the local host only unless configured otherwise.

Zero installation rules testing

The addition of a web proxy allows for easy initial testing of rules for any given website without any additional installation. To test rules against any site anywhere, simply configure the browser used to access the web proxy of the built in forwarding proxy.

Built in proxy redirection

It is now possible to redirect an incoming request to a different server or host, based on the virtual host

Same server built in forwarding proxy

The ability to redirect the virtual host of the incoming request now allows the installation of the built in forwarding proxy on the same server as the site being protected. This requires port changes to the existing application, but is otherwise transparent.

Ability to create database aliases

It is now possible to create an alias for a given database name. This allows stock rules to be written using a generic database name that can be aliased using the configuration.

Ability to configure database pool

It is now possible to set database pool size limits, pool full conditions and other database level parameters.

Security audit log

The console now contains a security audit log that contains an audit trail for all major changes to administrative items.

Backup and restore for extensions and user roles

Extension and user roles are now automatically backed up when changes occur and can be restored using the normal restore features.

New user types

Two new user types have been added: Super User and User Administrator. Super users can perform all administrative functions except user maintenance. User administrators can only perform user maintenance. This change was made to facilitate workflow inside large organizations.

Performance management and reporting

It is now possible to set a performance monitoring level in the configuration (Input Source). The options are to just collect transaction counts, collect transaction counts and timings (giving individual rule delays) or collect transaction counts, timing and individual URI response times. A comprehensive reporting framework has been added to analyze the results.

Auto documentation

It is now possible to automatically document the entire extent of a configuration deployed to a given server. Documentation includes server information, configuration settings, rule sets, data files, content files, JDBC driver settings and more.

Quick configuration

The demo console can now be configured and restructured to one of four different production scenarios directly from with the console itself. Many settings can also be changed without requiring a restart.

Important support changes

The following is a list of new/changed environments supported since version 5.0.

Single platform install

From version 6, non-Jetty installations are no longer supported. The server must be deployed using Jetty. To most users this is a transparent issue and does not affect functionality in any way.

Shared Configuration Vertical scaling support

This feature allows a single OctopusV8 configuration to be deployed to more than one server on the same piece of hardware. The rules engine detects the conflict and does an automatic resolution by selecting an alternate management port and moving its home folder to a sub-directory below the main home folder.

Deprecation of Universal Appliance and feed server images

As of version 6, there will only be one download and installation image covering all OctopusV8 installation variations. The Universal appliance and feed server equivalents can be created using this one image.

Built in proxy runtime shipped as extension

The built in proxy (formerly Universal Appliance) now ships as an extension (BIP Runtime) allowing the entire proxy to be updated using the update server.

Support for JNDI data sources

JNDI data sources can now be used to access databases defined within the target application server's JNDI name space.

Support for custom logging

Custom logging (other than System Out) is now supported. Logging options include system out logging, file logging and logging through Apache commons logging (which supports Log4J, Avalon LogKit and basic JDK 1.4 logging).