• 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

Integration possibilities

This technology enables legacy data to fit into the new frameworks that are SOA-based and emerging from all of the big players.

By providing a Web Services Interface to legacy data and business logic, integration occurs automatically using configuration tools and removes the requirement to write specialised code for accessing data. The legacy data becomes a ‘plug in’ rather than something that requires a large development effort to fit into the framework.

Integration with BEA Web Logic
The BEA Web Logic platform pulls in the WSDL from the Risaris SOA Gateway service.

Web Logic then enables the application programmer to generate various objects, such as Web Logic Service Controls and JPD files, from the WSDL interface. These objects can then be used naturally by the Web Logic programmer without any knowledge of the structure of the legacy database or language of the business logic.

All legacy data to be accessed can simply be included in the same way.

As the Web Logic programmer will understand WSDL, each integration steps can be made once they know where the Risaris SOA Gateway server resides.

Integration with IBM’s Web Sphere
The Web Sphere platform enables the programmer to integrate the WSDL from the SOA Gateway service into the current work space.

Web Sphere then enables the programmer to generate Enterprise Java Bean Skeletons for access to the legacy data. These Java Beans can then be used naturally by the Web Sphere programmer without any knowledge of the structure of the legacy database or language of the business logic.

The programmer can opt to use the Java Beans as they are or they can be modified with business logic if necessary. As the Web Sphere programmer will understand WSDL, all of the integration steps can be made once they know where the Risaris SOA Gateway server resides.

<< back