• Solution
  • Solution Overview
  • Approach
  • How it works
  • Technical Overview
• User Benefits
  • Business Benefits
  • Industry Verticals
  • Roles
    • Chief Information Officer
    • Chief Technical Officer
    • Business sponsors
    • The IT manager
    • The IT architect
    • Developer
    • Database administrator
    • Projects Office
• Tomorrow's World
  • SOA Approach
  • Current/Future Strategys
• Services
  • Integration Services
  • Consulting Services
  • SOA Training
• Resource Centre
  • Industry News
  • Analyst Watch
  • Events
  • Definitions
• The Latest Use Cases
• Partners

The IT manager

Today IT managers are charged with:

• Driving the cost out of IT projects
• Reducing maintenance fees
• Planning
• Delivering projects to the business on time and to budget
• Improving productivity
• Supporting new business projects.

The relevance of the SOA Gateway:

• Reduces the time developers and database administrators spend on legacy and data integration efforts
• Reduces maintenance fees and the cost of resourcing legacy and data integration specialists
• Reduces the risks involved in planning IT projects
• Ensures re-use, the same concept can be re-applied across projects
• Works across all platforms and is also database agnostic.

Relevant SOA Gateway features:

• Previously one or more developers would have been required to implement the bespoke server side of any solution to access legacy data. These resources can now be used more productively, developing applications to support the business instead of code to get at the data
• Once maintenance fees are paid, the organisation gets access to the latest versions of the SOA Gateway while existing services that have been implemented continue to be supported. This leads to less maintenance headaches that occur from bespoke implementations
• The SOA Gateway programmatically publishes how to access the data source and then manages access to the data source. This means programmers simply import the published interface into their applications and start to use it. There is absolutely no need for the developer to understand how the backend system works
• The SOA Gateway uses a common interface to the user and then maps this to whatever data source is in use at the backend. This common front end means the backend database can be changed at will as there is no dependency on it from the user’s perspective.

See also:

• How it works
• Technical overview.

<< back