Deprecation of IBM App Connect on IBM Cloud service plans
Service plans for IBM® App Connect on IBM Cloud® have been deprecated, and any instances of App Connect on IBM Cloud plans that still exist on 30 November 2023 will be deleted. To continue using IBM App Connect, you should migrate to an alternative provision.
Overview
IBM has announced the deprecation of App Connect on IBM Cloud service plans (Lite, Professional, Enterprise). At 30 November 2023, any IBM App Connect on IBM Cloud instances will be permanently deleted and deprovisioned.
The service plans were made available to customers to provide IBM-managed instances of App Connect running on IBM Cloud Foundry, and have hosted thousands of integration flows over many years. But as technology moves on, newer and more sophisticated technologies have become available for our IBM Cloud users.
The following describes the details of the deprecation, possible migration targets, and additional information.
Timeline
The timeline for this deprecation is as follows:
| Stage | Date | Description |
|---|---|---|
| Announcement | 15 December 2022 | Announcement of the deprecation of IBM App Connect on IBM Cloud service plans. All current users of IBM App Connect on IBM Cloud as of early December 2022, will receive an email with information about the deprecation. Notifications will be put into the IBM App Connect on IBM Cloud service and documentation. |
| End-of-Marketing | 14 January 2023 | New instances of App Connect on IBM Cloud service plans cannot be created by any user. |
| Reminders | Ongoing | Periodic reminders will be sent to all users with running instances of IBM App Connect on IBM Cloud that the end-of-support date is coming, with increasing frequency as the date approaches. |
| End-of-Support | 30 November 2023 | All instances of IBM App Connect on IBM Cloud will be permanently disabled and deprovisioned. |
Migrating IBM App Connect to an alternative provision
Identify the App Connect instances affected
(Click the image to view full size.)
Preserve the artifacts that you want to migrate
- For each event-driven flow and API flow, preserve the flow definition file and app connection
details. An exported flow definition file preserves all the flow's configuration settings, other than the connection details for the apps used in the flow.
- If you created the flow in your App Connect instance, you can export the flow. For more information about exporting flow definition files, see Exporting a flow.
- If you imported the flow from somewhere else, make sure that the latest flow definition file has been preserved.
Tip: Make sure that you have preserved the connection details for the apps used in the flow. You can look at the nodes in the flow to see which connection account name is used for which you need to preserve the details. - For each policy created in App Connect on IBM Cloud
and applied to the integration server for an uploaded bar file, preserve the policy details.Tip: To see the policies that are applied to integration servers, you can use the Policies view. In that view, you can use the options menu for a policy to view the policy details.
For more information about using the Policies view to manage policies, see Configuring integration servers by using policies.
All other services you have been using in IBM Cloud, such as Db2® on IBM Cloud, are unaffected. If you move instances of IBM App Connect on IBM Cloud to another IBM Cloud compute service, you should be able to connect to those previous connected services and continue using them normally.
Migrate to an alternative provision of App Connect
The options for the alternative provision for App Connect depend on the licenses that you have and what you want to do. Generally, to migrate to an alternative provision of App Connect, you create an instance of App Connect, import the flows that you want to use, and connect the App Connect instance to the app accounts used in the flows.
- Migrate to an instance of IBM App Connect Enterprise as a
ServiceIBM App Connect Enterprise as a Service is a multi-tenant managed service that unlocks the value of your data by connecting business applications, integrating data, building APIs, and acting on events. It is fully managed, maintained, and operated by the IBM product team.
- For information about provisioning an instance of App Connect Enterprise as a Service, see IBM App Connect Enterprise as a Service overview.
- For information about migrating flows to App Connect as a Service, see Migrating your flows from App Connect on IBM Cloud.
- Work with IBM Expert Labs to provision and manage
instances of App Connect for you
If you feel your organization needs help migrating from App Connect on IBM Cloud, you can engage IBM Cloud Expert Labs. For more information and contacts to get started with IBM Expert Labs, see Migrate from Cloud Foundry with the help of IBM Cloud Expert Labs.
Note: IBM Cloud Expert Labs provides for-pay migration assistance. Similar for-pay options are available from third-party partners. For information about options for assistance with your IBM Cloud Foundry migration, see Migration assistance in the Cloud Foundry documentation. - Provision your own self-managed infrastructure to run IBM App Connect in containers
- You can provision an IBM Cloud compute service (IBM Cloud Code Engine, IBM Cloud Kubernetes Service, or Red Hat® Open Shift on IBM Cloud) and then deploy and run IBM App Connect certified container in that environment. For more information about this option for application hosting runtime platforms on IBM Cloud, see the migration checklist and supporting information for Deprecation of IBM Cloud Foundry.
- You can provision your own Red Hat OpenShift® Container Platform or Kubernetes cluster and then deploy and run IBM App Connect Enterprise certified container in that environment. For more information about this option, see IBM App Connect in containers (Long Term Support)
- You can deploy and run IBM App Connect as part of IBM Cloud Pak® for Integration. For more information about this option, see IBM Cloud Pak for Integration.