Removing a managed node profile from a deployment environment

You can remove a managed node profile from a IBM® Business Process Manager deployment environment by removing the node from the environment and then deleting the profile. No database updates are required.

Before you begin

For more information about the manageprofiles command-line utility, see manageprofiles command-line utility.


  1. Stop the deployment manager and all the running server processes in the managed node, including the node agent process.
  2. On the deployment manager, run the following command to remove the cluster members from the IBM BPM deployment environment:
    BPMConfig -delete -profile dmgr_profile_name -de de_name -node node_name

    Running this command does not delete the node. It ensures that REST endpoints and JMS connection factory provider endpoints that refer to the cluster members are updated. For more information about the command, see BPMConfig -delete.

  3. Restart the deployment manager.
  4. On the managed node machine, run the following command:
    manageprofiles -delete -profileName node_profile_name
    By default, a prompt for the credentials to connect to the running deployment manager is displayed. This prompt times out after 1 minute and there are no manageprofiles parameters to specify the credentials on the command line. To avoid the prompt, set the following properties in node_profile/properties/soap.client.props:

    Running this command deletes all servers that are not IBM BPM servers, including web servers, and all application module mappings that refer to those servers. It also deletes the node itself from the WebSphere® Application Server cell.

  5. Optional: If the removed node hosted a web server, you must update the web server plugin. For instructions, see the Plug-ins configuration documentation.
  6. Optional: Manually remove any virtual host aliases that are no longer needed. In the administrative console, go to Environment > Virtual hosts > default_host > Host Aliases and delete aliases that you no longer need.
  7. Optional: If you have errors, complete the managed node removal by running the cleanupNode command and removing references from the registry.
    • If the manageprofiles command fails to connect to the deployment manager, the following message is displayed: INSTCONFPARTIALSUCCESS: The profile no longer exists, but errors occurred. The node_profile/logs/_nodeuninst.log file contains the following error: ADMU0040E: Exception on MBean invocation WebSphere:name=AdminOperations,process=dmgr.
    • If the deployment manager was not running at all, the following message is displayed: INSTCONFSUCCESS: Success: The profile no longer exists. The node_profile/logs/_nodeuninst.log file contains the following error: ADMU0006E: Exception creating Deployment Manager connection.
    1. Confirm that the deployment manager is running, then run the following command on the deployment manager to complete the managed node removal:
      cleanupNode node_name -profileName dmgr_profile_name -username admin_user -password admin_password
      For more details, see cleanupNode command.
    2. On the computer where the node was deleted, run the following command to remove references in the registry to deleted profiles:
      • For Linux operating systemFor UNIX operating system./ -validateAndUpdateRegistry
      • For Windows operating systemmanageprofiles.bat -validateAndUpdateRegistry
  8. Remove the managed node profile directory manually using operating system commands. The manageprofiles command does not entirely remove the directory because it still contains log files.