Category Archives for "Integration"

Key To Successful M&A Integration Strategy

Judging by the number of memes, 2020 is shaping up to be one of the most turbulent and unpredictable years in modern history, mainly due to the unprecedented convergence of global health, political, and climate crises. Industry consolidation is a likely response to these challenges across many verticals and geographies. Mergers and Acquisitions (M&A) are a great way for companies to rapidly expand their product and service portfolio, increase market share, and expand the sales, supply, and partner channels.

Continue reading

AS400 Connector for Mulesoft v2.1.2 is released

We are happy to announce the new version of IBM i (AS400) connector for Mulesoft Anypoint Platform has been certified and available on Mulesoft Exchange. The AS400 connector simplifies integrating legacy applications running on IBM i (AS/400, iSeries, System i). 

Infoview developers are working hard to continuously innovate, deliver new features based on customer feedback, and ensure the connector is aligned with the latest Mulesoft features and certification requirements.  

This release includes the following features: 

  • Added socket timeout, number of retries, and max time to live to connection configuration. 
  • Enabled standard reconnection strategy and notifications in case of connection failed events. 
  • Added explicit Data Queue entry and key length to support writing into remote (DDM) keyed Data Queue. 

To take advantage of these new features, update the connector version in your Mule applications to 2.1.2. To learn about the new version, view our on-demand webinar

Support & License / Trial License: Please email: , Call: +1 (734) 293-2160  or +91-40-42707110 

IBM i (AS400) Connector for Mulesoft Release Announcement

Today, we are happy to announce the release of IBM i (AS400) Connector for Mulesoft Anypoint platform. In response to the feedback from our customers and prospects, we added support for calling Service Program Procedures and ability to define external format for data queue entries. These enhancements further reduce or eliminate the back-end development for integrating the IBM i (AS400) based applications into modern application landscape. The new features are released for both Mule 3 and Mule 4 versions of the Connector.

Continue reading

Infoview Systems announces the IBM i (AS400) Connector for Mulesoft Titan release

Infoview Systems announces the general availability of Certified IBM i (AS400) Connector for the latest Titan release of Mulesoft Anypoint platform

The IBM i (AS400) connector further expands legacy modernization capabilities of the leading integration platform.

Livonia, MI – June 20 2018

Infoview Systems, a provider of innovative integration modernization and infrastructure services and products, announced the general availability of the IBM i (AS400) Connector for Mulesoft Titan release.

Enterprises running on legacy ERPs and Line of business applications realize it is critical for business success to rapidly unlock legacy data and business logic, while also connecting to an ever-increasing number of cloud and third party services.

The new Mulesoft Anypoint Platform enables enterprises to innovate at scale and rapidly build flexible and secure application networks. With the addition of the IBM i (AS400) connector, enterprises can now accelerate the delivery of the most challenging legacy modernization initiatives.

Infoview Systems, a Mulesoft Partner and global service provider, is a highly efficient cross-platform Professional Services and product company with a strong focus on customer business outcomes and long-term care.

How to debug IBM i Program called from Mule

In the previous post we wrapped an IBM i business logic program into an easy to consume API with Mulesoft Anypoint platform and IBM i Connector. Took just under 15 minutes to build and works like a charm at the first try. Right… in real life there are quite a few things that could go wrong with remote program call. Most commonly the issues are caused by the incorrect parameter definitions, where parameter mode, data type or length or sequence mismatch cause the program to bomb.  The connector logs the exception and the trace, however in some cases it’s really useful to take a look at what’s going on during program execution. In this article, contributed by Vivek Gupta, we show how to debug IBM i program called from Mule API. Vivek is one of very few people in the whole world (and most of them are on our team!) who develops both Mulesoft and IBM i components for the same project.

Continue reading

How to Build an IBM i (AS400) API in 15 Minutes

One of the biggest IT challenges is the growing IT delivery gap and the ever increasing pace of business changes. This is especially true for established companies saddled with a mix of older applications. In order to efficiently connect these systems to other business components at scale, the application business logic and data must be be packaged as easy-to-consume reusable assets.

Due to the monolithic nature, most legacy applications span multiple business domains. As a result, the number of required integrations is typically high. When we consider the complexity of integrating with legacy systems, the shortage of specialized skills, and tight budgets, it’s easy to see why unlocking ERP data and logic is a constant concern for IT leaders.

Technically, this problem boils down to the question: how fast can you build an API that calls the backend business logic, and how much of that work depends on the legacy team? In this how-to guide, I’ll show you how to use the latest version of MuleSoft’s Anypoint Connector for IBM i (AS400) to accelerate wrapping business logic program into a REST API without any IBM i tools or development required. Once the IBM i (AS400) API is developed, it can be plugged into Anypoint Platform for added security, governance, and operational insight.

Continue reading

How to Run Mule on IBM i

For companies running their ERPs and Line of business applications on IBM i or mainframe, ability to rapidly connect the applications to ever increasing number of cloud and third party services is critical for business success. IBM i (AS400, iSeries) is a modern, powerful and secure platform optimized for running complex and diverse workloads. The recent versions of the system have several integration options available out of the box, including Integrated Web Services, Apache HTTP server, XMLSERVICES, as well as a host of available Node.js, PHP, and Java based options. And we all know that having a choice always always beats the alternative, right? In this article I present one more option and show how to run Mule on IBM i.

Continue reading

Join Infoview and Mulesoft webinar on Legacy modernization and APIs

mememe-cafeFrom Mainframe to Microservices: Leveraging APIs to Accelerate Legacy Modernization

It’s a well-known fact that business requirements and underlying software systems change at different speeds. Over time, most legacy systems become misaligned. Business and IT have to compensate with workarounds, often at a price of IT agility and increased process overhead. Legacy Modernization is a low-risk approach that enables a continuous realignment of the applications with business outcomes, while preserving the investments into intellectual property accumulated over the years. The key recipes are reuse, self-service, governance and security.

I would like to invite you to watch the recording of our latest webinar:  From Mainframe to Microservices where we showcase how APIs can power modernization initiatives in your organization. Mike O’Meara, Dmitriy Kuznetsov, together with Matt Serna at Mulesoft, discussed how an API-led strategy and Anypoint platform help accelerate Legacy Modernization initiatives. Dmitriy demonstrated typical integration use cases for the IBM i platform using Anypoint, AS/400 connector and Web Transaction Framework.

The webinar was held on Tuesday February 7, 2017 at 8 AM PST / 11 AM EST.

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