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.

Before you begin

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

Procedure

Stop the deployment manager and all the running server processes in the managed node, including the node agent process.
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 ensures that REST endpoints and JMS connection factory provider endpoints that refer to those cluster members are updated accordingly. For more information about the command, see BPMConfig -delete.
Restart the deployment manager.
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:
- com.ibm.SOAP.loginUserid=admin_user
- com.ibm.SOAP.loginPassword=admin_password
Optional: If you have errors, complete the managed node removal.
- 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.
```
  and 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.
```
  but the node_profile/logs/_nodeuninst.log file contains the following error:
```
ADMU0006E: Exception creating Deployment Manager connection
```
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.
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.