SOA Gateway Product Overview
The SOA Gateway delivers access to your data across multiple platforms
with no additional custom programming.
The solution enables access to all data and applications on those
platforms using:
- Industry Service Oriented Architecture (SOA) standards
- A unique back-to-front approach
to SOA legacy integration.
The solution has been developed to:
- Reduce time to access legacy data
- Increase re-use of legacy data and information across organisations
- Eliminate the need for custom code development every time the
business needs to access a new piece of data
- Avoid the expense of replicating legacy data and business logic.
Leading industry analysts, such as Datamonitor
and the Standish
Group , describe the time to access and use legacy data as the
Achilles heel of current SOA initiatives.
"The chasm between data and logic explains why 70% of integration
project costs stem from manually implementing data manipulation."
- Enabling the SOA Enterprise, Datamonitor 2004.
By exposing existing data and business logic using industry SOA
standards (SOAP, WSDL and REST) the SOA Gateway offers 'out of the
box' connectivity to legacy resources.
The SOA gateway can be installed within hours. This assumes programming
languages used (Java, .net-based languages on Windows, PHP, Perl,
Ruby on rails, XML-SPY) can consume a Web Service.
The SOA Gateway makes legacy data available using a standard URL.
You can view a technical overview of this here.
This enables browsers, Word, Excel, etc, to access resources without
any additional programming.
Once granted permission, the user has the ability to send a URL
to business colleagues who can then click on the URL to retrieve
real-time data directly from the legacy resource.
The SOA Gateway also enables BPM suites to access and use data
and information resources directly from the Enterprise Services
Bus (ESB). These include:
- Websphere BPM from IBM
- CrossVision from Software AG
- AquaLogic from BEA
- BizzTalk from Microsoft
- CapeClear.
There is no additional custom programming required. This is achieved
with no client installation or footprint where the BPM software
is running. This means:
- Less testing
- Less maintenance
- Less time to install.
See also:
<< back
|