Before we delve into the details of migration, let’s define the two platforms
API management offering provides us a platform that let us manage and control the set of APIs and expose to application developers.
API management platform makes it simple to deploy APIs, easy to define the structure, to understand how we will access it and control those APIs with security.
IBM API Connect is an integrated offering, which provides customers an end to end API life-cycle (Create, Run, Secure and Manage) experience. It provides capabilities to build model-driven API’s, micro-services using Node.js loopback framework, run them either on-premise or on-cloud, secure and manage the same using management, gateway server and developer portal.
It presents a tailorable self-service web-based portal to application developers to take a look at, uncover, and subscribe to APIs.
It provides tools to interface with various servers and holds the data. It runs Cloud Management Console (utilized by cloud administrator to create, manage and monitor the cloud and other admin tasks) and API Manager Portal (used by API developers, Product managers, admins etc.)
Following are the approaches that we can take to upgrade to API Connect.
Below is the comparison to see what will change after the upgrade.
To successfully upgrade the IBM API Management solution, we need to perform operations on both the Management cluster(s) and Gateway cluster(s). The following diagram illustrates how the sequence of events unfold as we apply maintenance to the various servers in the API Management solution.
User invokes command on each server in turn
In the diagram above, there are four Management servers in the Management cluster and two Gateway servers in the Gateway cluster.
Steps 1-6 illustrate the upgrade sequence for the Management cluster. Upgrade the Management servers one at a time. The management server is momentarily disconnected from the cloud after the upgrade and remains idle till the last server is updated. We can begin with any non-primary Management server in the Management cluster–upgrade the Primary Management server last. Substantiate that the upgrade is successful before starting the upgrade for the next Management server. When the last Management server (Primary) upgrade happens, the Primary Management server automatically activates and reactivates all the other upgraded servers in the Management cluster. The role of the server (for example, Primary, RSS) can be viewed under server details for each server in the Clusters tab of the Cloud Management Console (CMC).
Steps 7-10 illustrate the sequence in which the Gateway cluster should be refreshed after upgrading the Management clusters.
It is important to test the upgrade process as it helps us in validating the upgrade path without jeopardizing our active API management installation.
Below is the procedure to test the upgrade process: