Remove an organization

To remove an Apigee Edge for Private Cloud organization from your API hub integration, follow these steps:

  1. Configure the message processors:

    Finally, update the message processors to disable dual-write capability for the organization you are removing. This configuration change must be applied on each message processor (MP) node in your Apigee Edge for Private Cloud installation.

    • Edit the file /opt/apigee/customer/application/message-processor.properties on each MP node.
    • Find the property conf_message-processor-communication_uapim.enabled.environments and remove all entries related to the organization and its environments that you are deleting.

      For example, if you are removing new_org and its environments dev and staging:

      This is a comma separated list of all the environments for which the Apigee API Hub for Private Cloud connector runtime data on-ramp has to be disabled. conf_message-processor-communication_uapim.enabled.environments=acme~prod,acme~dev,noncps~prod

      path to the network file system (NFS) mount which isconf_message-processor-communication_uapim.runtime.data.path=/the/nfs

  2. Configure the Apigee API Hub for Private Cloud connector:

    Next, update the Apigee API hub connector's configuration by removing the entry for the organization you are deleting.

    • Edit the file /opt/apigee/customer/application/uapim-connector.properties.
    • Locate the connectorConfig section under the conf_uapim_connector.uapim.settings.json section and remove the entire JSON block corresponding to the organization you wish to delete.

      For example, if you are deleting new_org:

      conf_uapim_connector.uapim.settings.json={
          "connectorConfig" : {
            "org1" : {
              "runtimeDataPubsub" : "",
              "metadataPubsub":"",
              "serviceAccount": "mysa1@in.myfirstProject",
              "pluginInstanceId":"aaaa"
            }
          },
          "runtimeDataPath":"/the/nfs/mounted/path",
          "managementServer": "hostname"
        }
    • After modifying the file, restart the Apigee API Hub for Private Cloud connector for the changes to take effect: 
      apigee-service edge-uapim-connector restart
  3. Delete plugin instance on API hub:

    First, delete the Plugin Instance associated with the organization you wish to remove from API hub. This action will stop the flow of metadata and runtime data for that specific organization.

  4. After updating this file on all relevant MP nodes, perform a rolling restart of your message processors to ensure the configuration is applied.