OpenLegacy Connectors

The invocation of IMS transaction is a simple task using the standard OpenLegacy IMS RPC solution. (PL1, COBOL)

The OpenLegacy Mainframe MQ Integration Adapter has many benefits as an integration tool working with MF MQ banking software. With our solution, IBM MQ transactions can now be delivered as digital services – as output to Web and mobile devices, including smart phones and tablets. Our solution can be used for integration with other environments such as distributed technologies and cloud services. 

IBM MQ is currently used by several banks around the world, and OpenLegacy sees a real integration problem in this sector. For this reason we want to provide an easy, simple, and familiar experience to OpenLegacy clients who want to expose their IBM MQ based systems to cloud native, modern architectures. (PCML, COBOL)

The standard OpenLegacy Mainframe Screens solution makes integration with mainframe terminal screens a simple task.
The goal is to create an SDK which contains Java models (Screen entities) that mirrors the host's screens and flow (navigation between screens).

The OpenLegacy Screens connector holds a stateful session based on the tn3270 protocol (telnet based protocol). Each time an action is performed through the SDK using the doAction or the getEntity methods, the connector navigates to the relevant screen according to the navigation metadata available on each entity, identifies the screen based on its identifiers, and sends the data from/to the entity fields, together with the specified terminal action (ENTER, ESC, F1, F12, etc.). The returned screen is then checked against all the project entities to find a match based on the identifiers. The screen is then serialized into the matched entity and returns it in response.

The invocation of AS/400 programs (PGM) is a simple task using the standard OpenLegacy AS/400 RPC solution.

To invoke programs on the AS/400, a Java model is required that describes the parameters that the program receives and returns. These are the parameters defined in the "linkage section" when working with COBOL or "entry" in RPG.

While it is possible with OpenLegacy to parse source code like COBOL to build these models, a more generic and accurate way to get a description of these parameters is using a PCML.
PCML is a file in XML format created by the AS/400 compiler, that describe the program parameters.

AS/400 COBOL

RPC calls to IBM i based on Cobol

RPC calls to IBM i based on PCML

Data queues are a type of system object that you can create, to which one high-level language (HLL) program can send data, and from which another HLL program can receive data. The receiving program can be waiting for the data, or can receive the data later

Messages can be pushed into an As/400 queue. Developers can setup the SDK project to either just push the message into the queue and return a success message ,or wait for a response from a different queue and return that response to the user.

The standard OpenLegacy AS/400 Screens solution makes integration with AS/400 terminal screens a simple task.
The goal is to create an SDK which contains Java models (Screen entities) that mirrors the host's screens and flow (navigation between screens).

The OpenLegacy Screens connector holds a stateful session based on the tn3270 protocol (telnet based protocol). Each time an action is performed through the SDK using the doAction or the getEntity methods, the connector navigates to the relevant screen according to the navigation metadata available on each entity, identifies the screen based on its identifiers, and sends the data from/to the entity fields, together with the specified terminal action (ENTER, ESC, F1, F12, etc.). The returned screen is then checked against all the project entities to find a match based on the identifiers. The screen is then serialized into the matched entity and returns it in response.

The OpenLegacy Temenos Integration Adapter has many benefits as an integration tool working with Temenos banking software. With our solution, Temenos transactions can now be delivered as digital services – as output to Web and mobile devices, including smart phones and tablets. Our solution can be used for integration with other environments such as distributed technologies and cloud services. 

There are two variations of Temenos T24: TAFC and TAFJ (Temenos Application Framework C version or Java version).

Using the OpenLegacy SQL parser, it is possible to parse a stored procedure SQL and generate entities from it to some degree.

The OpenLegacy Stored Procedure parser utilizes the sections describing the IN and OUT parameters of the procedure statement.
The output structure of Stored Procedures which returns values based on internal queries is not supported by the OpenLegacy SQL parser.

OData (Open Data Protocol) is an ISO/IEC approved, OASIS standard that defines a set of best practices for building and consuming RESTful APIs. There are four OData versions.
OpenLegacy supports OData v2 and OData v4. 

SOAP (originally Simple Object Access Protocol) is a messaging protocol specification for exchanging structured information in the implementation of web services in computer networks. Its purpose is to induce extensibility, neutrality and independence. It uses XML Information Set for its message format, and relies on application layer protocols, most often Hypertext Transfer Protocol (HTTP) or Simple Mail Transfer Protocol (SMTP), for message negotiation and transmission.

SOAP allows processes running on disparate operating systems (such as Windows and Linux) to communicate using Extensible Markup Language (XML). Since Web protocols like HTTP are installed and running on all operating systems, SOAP allows clients to invoke web services and receive responses independent of language and platforms.

REST API is the most commonly used method to produce and consume digital services in the modern age. Either as an on-premise solution or on the cloud, REST API is the way to go if you want your organization to work in the most standard and light-weight way available.

In addition to creating new REST APIs from scratch in the platform, OpenLegacy REST API allows the customer to consume already created REST APIs to modify, orchestrate, add caching layers, and more.(REST JSON, REST OpenAPI, REST XML, REST XSD)

 Tuxedo encapsulates the original source code of its services, therefore we do not parse the service logic by its original language. 

Tuxedo exposes the service interface through a text file with the information about input and output parameters. 

The data is placed in a file with ".jolt" extension to generate an entity. 

Currently, only version 8.1 of the Jolt client is supported (newer versions might work as well).

The File Connector is different from other OpenLegacy connectors. It is a one-way connector that, when invoked, produces files in either XML or SWIFT payment format.

To produce these files, an SDK with Java models that describe these files' formats is required. These models can be created manually or generated by providing an XSD  (XML Schema Definition) that can be parsed.

Kafka is an  event streaming platform . OpenLegacy allows organizations to publish messages to Kafka by creating a creating a Java model either manually or by parsing JSON files that describe the model. Then in runtime, messages are pushed to a specified Kafka topic.

This is a Kafka message producer , it does not wait for a Kafka response.  If the project is required to listen to a Kafka message , it is possible to create a Kafka consumer VIA OpenLegacy API project.

TCP based communication with Card systems over ISO-8583