Cloning Micro-Integrations in Solace Cloud

You can clone an existing Micro-Integration to create a copy of an existing Micro-Integration that includes:

  • The configuration to the specified event broker service.

  • The configuration of the external system.

  • The header mappings you have created between your external system and the event broker service for that Micro-Integration.

Prerequisites

Before you clone a Micro-Integration, ensure that you have:

  • An existing Micro-Integration. To ensure you have a valid configuration, we recommend that the Micro-Integration you clone be in the Running state.

  • The connection details and credentials for your external system and event broker service if they are different from the Micro-Integration you are cloning. For more information about retrieving the information for an event broker service, see Detailed Event Broker Service Information.

  • Your user account must have the Mission Control Manager assigned to it.

Considerations for Cloning Micro-Integrations

Consider the following information when you are cloning Micro-Integrations:

  • You may find it useful to clone an existing Micro-Integration to save time and reduce errors during the configuration process for Micro-Integrations. For example, you can copy the configuration to the same external system and modify the queue and the event broker service details.

  • When you create a clone of an Micro-Integration, it can be in any state, such as Running, Not deployed, or Down. Regardless of the state of the Micro-Integration that you are copying, the cloned Micro-Integration starts in the Not Deployed state when you clone it. No validation checks are performed on the configuration of the clone, which may be useful if you don't have all the configuration details and want to put in placeholder values temporarily.

    Alternatively, you can choose to clone and deploy the Micro-Integration, which performs validation checks of the configuration prior to creating and deploying the clone. In this case, the Micro-Integration starts in the Deploying state and moves to the Running state after it successfully deploys.

  • If you are using environments, you cannot clone a Micro-Integration from one environment to another environment. If you have migrated the event broker service, you must manually re-create the Micro-Integration. For more information about environments, see Creating and Managing Environments.

Clone a Micro-Integration

To clone (or copy) an existing Micro-Integration, perform these steps:

  1. Log in to the Solace Cloud Console if you have not done so yet. The URL to access the Cloud Console differs based on your authentication scheme. For more information, see Logging In to the Solace Cloud Console.

  2. On the navigation bar, select Micro-Integrations.

  3. If your organization uses multiple environments, on the Micro-Integrations page, select the environment where you want to create the Micro-Integration.

  4. Click the name of the Micro-Integration you want to clone.

  5. On the Micro-Integration Details page, in the top-right corner, click the ellipsis () and select Clone.

  6. On the Clone Micro-Integration page, a copy of the Micro-Integration you are cloning is created. You can optionally:

    • Modify the Name field. By default, the name is the same as the original Micro-Integration but with - Clone appended.

    • Modify the Description.

    • Click the Source Connection, Target Header Mapping, or Target Connection tabs to modify the fields for the source connection, header mappings, or target connection fields. For example, you can change the event broker service or even remove it if you are not ready to deploy the Micro-Integration.

  7. Click one of the following to clone the Micro-Integration:

    • Clone to only create a copy of the Micro-Integration. No validation checks are performed. You can later modify the details and deploy Micro-Integration.

    • Clone and Deploy to clone and deploy the Micro-Integration. Validation checks are made on the configuration prior to cloning and deploying. If validation checks are not successful, the clone will not be created.