With LegaSuite Integration, you have the flexibility to publish microflows that contain exising application functionality as the SOA interface of your choice: XML, SOAP (WSDL) J2EE (JavaBeans, portlets), and .NET assemblies. These interfaces describe how to execute the microflow residing at runtime on a LegaSuite Integration engine.
How it works.
LegaSuite Integration separates the host functionality from the service interface. The runtime integration engines form a universal interface layer for storing information about screen navigation, transaction mapping, and business logic mapped in the microflows. This architecture eases change management and allows for a true service-oriented approach. LegaSuite Integration runtime engines execute application services which communicate with the host application, and manage communication with the other applications that consume enterprise business services.
Choose Your Runtime.
You have a choice of runtimes to meet your performance and flexibility needs.
LegaSuite Distributed Integration Engine (LDE).
The LegaSuite Distributed Integration Engine processes requests and responses, executes microflows, and invokes the host application using the appropriate host connecter: TN3270, TN5250, VTxxx, VME/ICL 7561, ICL Forms, DFP, CICS or IMS.
The LDE’s session management capabilities facilitate communication between the session-based, enterprise business applications and the request/response-based business functions incorporated into a composite application, enabling the delivery of live, real-time host processes and content to other “consuming” applications.
A built-in XML transformation manager offers an XML module for mapping over 120 different formats, including dozens of XML dialects such as XSD, XSLT, XPATH, ebXML BPML, SOAP, WSDL, UDDI and .NET, as well as industry-specific data formats approved for the healthcare and financial transaction communities, among others. Requests and responses can be mapped using a choice of XSLT or the GoXML Transform Engine.
LegaSuite CICS Integration Engine(LCE).
The LegaSuite CICS Integration Engine runs inside of a CICS Transaction Server and processes requests and responses encoded in XML, SOAP, or via an MQSeries interface. The CICS engine invokes CICS application microflows via COMMAREA (DPL), 3270 Bridge/FEPI, or VSAM.
For optimal performance while reducing MIPS usage on the mainframe, the LegaSuite hybrid architecture lets mainframe organizations combine the benefits of the distributed and native engines to maintain performance while off-loading XML and SOAP handling. This offers you the advantage of saving on MIPs while keeping a high throughput threshold.
LegaSuite Windows Integration Engine (LWE).
The LegaSuite Windows Integration Engine contains an efficient microflow engine. Microflows simplify the process of performing the navigational and data extraction functions, enabling multiple Windows dialogs to be fused as a single callable service, part of a composite application or simply refaced as a new Web-enabled application or Web service. The result is the functionality of a re-engineered application by altering the application granularity without affecting the original target source.
A requesting program or user (i.e., clients) can communicate with the LWE using Web services or XML via HTTP/SOAP or sockets, using XUL for thin client integration or direct via the COM/.NET-based programmatic interface.
Publishing, Testing, and Monitoring.
LegaSuite Integration's publishing and monitoring features allow you to publish, manage, and monitor integration engine configuration files, microflows, and the back-end connections to the host systems.
The server console allows for real-time monitoring of running microflows, log file information, and also provides runtime statistics. There's also a microflow tester to test published microflows in XML or as Web services using SOAP.
User Authorization and Security.
The LegaSuite Server Security is based on the Sun Java Authentication and Authorization Service framework (JAAS) to allow for authentication of users to reliably and securely determine who is currently executing and for authorization of users to ensure they have access control rights (permissions) required to execute the requested function.