How FMT Octopus fits into a system architecture

FMT Octopus and Service Oriented Architecture

FMT Octopus™ fits easily within a SOA environment. Through its unique one-touch capability, it manages and deploys new or edited security policies and business functions across multiple applications from a single console. Just as easily, it can remove policies across all connected applications.

FMT Octopus extracts real-time information from every Web Service transaction by turning XML information into data elements. It examines information (some of which would formerly would have gone undetected) and can:

• Deliver competitive differentiation
• Enhance operational efficiency
• Improve application security
• Mitigate fraud and risk
• Adhere to compliance regulations
• Build trust and confidence in the online channel

In an SOA deployment, FMT Octopus wraps itself around applications to measure, manage and manipulate a Web Service request. It also serves as a broker that injects real-time agility and control at any time throughout the service initiation and interaction.

Support for large server clusters

Regardless of the rules engine installation into the infrastructure itself (inline filter, stand-alone or universal appliance), there may also be a requirement to handle a large number of servers in one or more clusters. You may for example have two server clusters in two different physical locations to provide redundancy and high availability. Under those circumstances, it may not be practical to manage individual server instances one by one.

FMT Octopus solves this problem by assigning slave consoles to each managed cluster unit. A slave console (or cluster node as it is referred to in the console itself), is a cut down version of the main console. It has automated single sign-on affinity with the master console so you can easily drill down from the master console to a slave console. It also has an assigned repository, which will automatically be propagated and applied to all nodes and servers in a given console, whenever a change occurs in that repository.

A typical cluster configuration is shown below:

FMT Octopus and enhancing the MVC design pattern

In today's fast moving climate, developers are busy keeping up to date with the latest features and technologies, and many are also unreasonably expected to become security experts at the same time.

The Model-View-Controller architectural design pattern regularly used for development is not proving to be efficient for e-business security.

With FMT Octopus, you can implement an additional security layer and manage business rules and policies without impact to your existing application. Turn your MVC design into MVCS!

Developers can get back to doing what they do best - building applications.