SOA Interfaces in No Time flat.
If you're creating a Web application or SOA architecture, chances are high that you'll have to integrate with critical enterprise applications. But some enterprise systems were not designed to be integration-friendly. With LegaSuite Integration that's not a problem. You can bring existing applications into the worlds of Web services, SOA, and Web applications, quickly and easily.
LegaSuite Integration is an Eclipse-based development tool that lets you rapidly create SOA interfaces from critical business logic and processes residing on mainframe, IBM i, client/server, VMS DEC/UNIX, and Windows client/server systems.
Low Risk, Automated Development.
LegaSuite Integration is completely non-invasive, so you don't have to touch or have access to underlying source code for SOA interfaces. This speeds development and drastically cuts down risk.
LegaSuite Integration facilitates the full cycle of development from deployment, testing, and debugging all the way to integrating with your existing change management infrastructure.
Designing SOA Interfaces from existing Apps.
Screen Service Building.
Let Web and mobile clients access application logic embedded in green-screens applications via TN3270, FEPI, TN5250 or any VT-like terminal emulation. Building services from screens lets you capture screen definitions directly from map definitions, DDS definitions or live screens. Includes wizard driven list collection and built-in error handlers.
CICS and IMS Service Building.
Windows client/server service building.
Database Service Building.
Provide transactional access to any database and enable Web and mobile clients to read and update data via direct SQL queries or stored procedures.
All that, and then some.
Quick and Easy.
Creating SOA interfaces from your existing apps is quick and easy and directly impacts a development team’s productivity. It eliminates the need for specialized training and allows for a separation of development skills. Enterprise application experts are freed from having to know anything about SOA, Web services, Java or .NET, and can focus on capturing and automating key business functions. At the same time, the SOA interfaces created from host applications can be reused by application developers who have no knowledge of enterprise host systems.
record it. package it. publish it.
Developing SOA interfaces couldn't be easier. You use LegaSuite Integration to record the way a user would complete a key business process and then it packages those steps into a microflow—a series of steps which contain the application navigation as well as input and output application mappings.
After you develop your microflows, you publish it to a high-performance runtime integration engines. Now it can be called by any type of client—Web applications, mobile apps, portals, and BPM and ESB suites.
Microflows: Encapsulate Legacy Navigation and Logic.
The first step in creating SOA interfaces from your existing applications is choosing the key processes to automate. You use the wizard in LegaSuite Integration to record navigation logic and identify the input and output fields of the host application. So you simply navigate through the host application as an end-user would, and record the steps with LegaSuite Integration. The tool packages the navigation sequence as a microflow, and the developer publishes it as an SOA interface. This completely eliminates the need for programming or accessing source code or database structures.
After you record a microflow, you can modify it by editing, inserting, or deleting recorded actions and editing input and output variables. Input and output values for business functions consist of any combination of single data values and repeating data sets (arrays of data). Screens attributes can also be utilized in data for variables (such as color, field, and length).
LegaSuite Integration generates two types of service-oriented interfaces: a microflow and an SOA interface. A microflow contains information about how to access and execute a function on the existing host application which is deployed on a LegaSuite Integration engine. An SOA interface is a function published as XML, WSDL, a JavaBean or .NET component, or published as a portlet.
Sorry, No Screen Scraping Here.
Older and traditional methods to access enterprise application UIs use screen scraping, which is based upon row/column coordinates. But screen scraping has inherent disadvantages that can cause slow performance, poor error handling, and a heavy maintenance burden. Rather than rely on screen scraping, LegaSuite Integration uses screen metadata to automatically identify screens and map fields.
You can collect information needed to build host screen definitions either by screen collection or host field mapping. Screen collection automatically collects map files and generates a repository with unique screen identifiers and host field names for BMS, MFS, ISPF, ESF and ADSO, and iSeries DDS (display files). If there are no maps available, the host field mapping can be created from a live connection without requiring the underlying map definitions.
LegaSuite Integration stores screen metadata, screen identification, and mapping information in a repository separate from the microflow or interface services (XML, J2EE, .NET, WSDL, SOAP, portlets.)
Host Screen Changes? Not a Problem.
The screen collection and host field mapping tools in LegaSuite Integration dramatically reduce maintenance requirements and greatly simplify change management. If a map files changes, you only need to make a change in the screen repository, which has no effect on the microflow or SOA interface. Only in cases where a new field is added or a field is deleted as part of a service is there a need to change the service accordingly.
For error handling, our LegaSuite Workbench facilitates the recording of custom application errors and exception handlers. As a fail-safe, if error handling cannot be pre-defined in the microflow, the error message generated by the host application will be returned to the client application. The client application developer then has the choice to display this message to the end user, display a custom message, or take appropriate steps to handle the message.