Category Archives for "Integration"

Consume APIs from IBM i with Mule

Modern enterprise architectures shift from all-encompassing ERPs to a network of smaller components that address specific business capabilities and communicate via common integration channels such as APIs. In some cases migrating to new system or best of breed may work. For most companies, however, the complete replacement is a risky and expensive proposition. Most successful modernization initiatives use a hybrid approach. Core line of business ERP systems are revitalized while some non-differentiating components that run industry standard processes may be replaced with purpose built applications or services.

The ERP components typically communicate with each other via shared database, resulting in a complex web of bi-directional real time integrations. When migrating a part of such system, these implicit inter-process communications must now be brought to light. The success of the project often depends on the speed of implementing these use cases. Comprehensive integration platforms such as Mulesoft Anypoint help delivering integrations at scale.

In this post I will show how to implement a real time external API call from IBM i (AS400) application using Mulesoft Anypoint, AS/400 connector, and Web Transaction Framework.

Continue reading

IBM i Business Logic API with Mule


Unlocking IBM i business logic and data is a priority for many companies. There is a number of IBM i (AS400, iSeries) tools and technologies that can be used to expose existing back-end programs as APIs. In this post we will use Mulesoft Anypoint integration platform and Infoview Web Transaction Framework to create a RESTful API that calls RPG program. This is a continuation of IBM i (AS400, iSeries) integration with Mulesoft Anypoint series. Previous articles can be found here: 

IBM i integration use cases
Building IBM i Data API with Mule

In the previous post we created Mule API that retrieves IBM i business data directly from DB2 for i database. The approach works great for simple data structures and normalized models. In most legacy applications, however, the stored data must first be processed through a complex business logic, which is typically a part of the existing back-end system, for example RPG program. API implementation must execute the business logic programs and handle the request / response data mapping. 

Continue reading

Building IBM i Data API with Mulesoft Anypoint


The common IBM i (AS400, iSeries) use case is to share the application data with other systems. In this article I will show how easy it is to build IBM i Data API with Mulesoft Anypoint. We will define our RAML API first then add the code to pull data directly from DB2 database using standard Database connector and IBM i database driver. Depending on complexity and design of IBM i application, the persistent data must be transformed through complex business rules first before it can be used by consuming applications. In this case, API implementation must execute IBM i programs that implement such business logic – we will do it in the follow up post.

It may appear at first that creating API adds more work and operational overhead compared to point to point integrations. Based on our experience, however, building out API layers is one of the most efficient ways to promote the reuse and secure, govern and monitor the access to application data and logic. Relatively small upfront investment results in greatly improved delivery speed, especially as the number of interfaces grows.

Continue reading

IBM i Integration Use Cases



Google “Digital Transformation” and you’ll get a lot of diagrams, white papers and dire predictions for companies not fully embracing it. The common theme is business must innovate at ever increasing speed. The limitations of the traditional IT delivery model make it difficult to evolve the systems at this pace. The recipe is to let business teams rapidly deliver their own projects, by reusing core business data and logic packaged as APIs. Modern low code development tools further democratize the delivery of new UI and process layers. The result is a network of applications that address specific business capabilities, evolve rapidly and independent of other components, and communicate through common integration fabric.

It’s a great model for startups that can get up and running in no time with modern cloud-based applications such as Salesforce, Netsuite, Workday, ServiceNow (extra shot of readily available capital never hurts either). Most modern SaaS applications have been built from the ground up around core APIs, and can be easily plugged into an integration platform. By contrast, established companies are saddled with a number of applications that have been developed over time with limited or no pre-built APIs or other out of the box integration methods.

In this post I discuss typical IBM i integration use cases and summarize the technology options for plugging into application network. As we all know, for any given IT problem there is always at least a half dozen tools and methods, and often many more.  Below I list the tools our team used or evaluated. Don’t see your tool or technique of choice listed here? I appreciate if you send it to me!

Continue reading

Traits of Modern IBM i Application

I’ve read somewhere a long time ago that the secret to success is to always start visualizing it in a great many details before thinking about how to achieve it. Otherwise we risk losing sight of the end goal, and waste time and resources fighting windmills. Sure, we’ll still get somewhere, and with some practice can even convince others that this is exactly the result we’ve planned for all along. How does it apply to IBM i modernization initiatives? Before diving into discussions about modernize vs migrate, RPG or SQL, screen scrapers vs RPG Open Access vs JavaScript, DDS or DDL etc, let’s pause for a moment and think about what would the modern IBM i application look like if it were built now, with all the knowledge accumulated over the years of maintaining and enhancing it. This would be our golden standard, very helpful when deciding on the best architecture or technology choices.

Continue reading

Securely connect Mule to IBM i / AS400

Anyone who has been on the receiving end of a PCI audit knows that encrypting data in transit is a sensible thing to do. It’s a must have requirement for sensitive customer data, personally identifiable information and as a general rule should be applied by default unless there’s a compelling reason not to. In this article I will show how to securely connect Mule to IBM i (AS/400, iSeries, System i).

Mule flows typically communicate with IBM i data and business logic via the following transports:

  • AS400 connector – works with Data queues and system commands
  • Database connector – facilitates direct access to application data and calls to DB2 stored procedures
  • Other TCP based protocols (HTTP, FTP etc)

In this article, I will show how to setup IBM i server encryption and secure Mule Database and Data queue communications.

Continue reading

Consuming and Producing APIs on IBM i / AS400 with Mulesoft Anypoint and Web Transaction Framework

In this demo I show how to connect IBM i (AS400, iSeries, System i) data and processes with Mule and Infoview’s AS400 connector and Web Transaction Framework.

Connecting, modernizing and migrating off of legacy systems is a complex undertaking. We are a capable cross-functional team of seasoned integration and IBM i professionals focused on customer care and business outcomes. Contact us to find out how we can help making your Digital Transformation initiatives a success. 

Send data to IBM i / AS400 multi member files with MuleSoft Anypoint

On a recent call with a prospect I ran into a use case where they needed to send data to AS400 multi member files with MuleSoft Anypoint. IBM i (AS/400, iSeries, System i) operating environment includes an integrated DB2 database that is widely used as an application data store. Remote clients can access IBM i data via DB2 SQL Query Engine, JDBC or ODBC interfaces, and this works well for regular files and DB2 tables. There is a special file type widely used in older IBM i applications that supports partitioning content into multiple “members” and provides methods for isolating the data for traditional programs. The challenge of interfacing with multi-member files is that they cannot be easily accessed via standard SQL clients.

There are several “brute force” options for remotely creating and working with multi-member files in Mule, including:

Continue reading

MuleSoft IBM i AS/400 Connector

Livonia, MI – 12/28/2015 – Infoview Systems Inc. today announces the release of the Certified MuleSoft Connector for the IBM® AS/400®. The connector works seamlessly with the MuleSoft Anypoint platform allowing companies to unlock the data and functionality within their AS/400 environments.

IBM Connector

The IBM AS/400 Connector is a comprehensive solution, integrating applications and data between the AS/400 and external systems, both on-premises and in the cloud.

The IBM AS/400 Connector, coupled with Infoview Systems IBM® AS/400® Web Transaction Framework provides for a unified integration experience.

The Connector for the IBM AS/400 has been certified by MuleSoft, the company that makes it easy to connect applications, data and devices by using its Anypoint Platform™.

Continue reading

MuleSoft adds Infoview Systems as Partner

Infoview Systems Inc. to Provide MuleSoft Anypoint Platform™ and Services for Connecting Applications in the Cloud and On-Premises

Livonia, MI – 8/28/2015 – Infoview Systems Inc. today announced its partnership with MuleSoft, the company that makes it easy to connect applications, data and devices, to provide consulting and services for the MuleSoft Anypoint Platform™. The platform is a complete solution for API-led connectivity that integrates applications and data both on-premises and in the cloud, unleashing the value of that data through the design, implementation and management of APIs.

Continue reading