Augmenting deployment manager profiles using the manageprofiles command-line utility

You can use the manageprofiles command-line utility to augment an existing WebSphere® Application Server deployment manager profile.

Before you begin

Remember to shut down any servers associated with a profile you plan to augment.

Make sure that you are not already running the manageprofiles command-line utility on the same profile. If an error message is displayed when you run the command, determine if there is another profile creation or augmentation action in progress. If so, wait until it completes.

Restriction: You cannot augment a deployment manager profile where the default WebSphere VMM user registry has been changed, for example, to using LDAP. Also, you cannot augment a deployment manager profile unless administrative security has been enabled.

Procedure

Use the augment parameter to make changes to an existing profile with an augmentation template. The augment parameter causes the manageprofiles command-line utility to update or augment the profile identified in the -profileName parameter using the template in the -templatePath parameter. The file path for -templatePath need not be fully qualified; install_root/profileTemplates is automatically added as a prefix.
Note: Do not manually modify the files that are located in the install_root/profileTemplates/BPM directory.
Run the file from the command line. The user name specified for the -adminUserName parameter must already exist and it must have administrative privileges. The -adminAliasName parameter is optional. Do not supply a -profilePath parameter. For example:
```
manageprofiles -augment -profileName profileName -templatePath BPM/BpmDmgr -adminAliasName CellAdminAlias -adminUserName adminUserName -adminPassword adminPassword
```
The status is written to the console window when the command completes running.

What to do next

Add managed-node profiles to be managed by the deployment manager, and then configure the deployment environment.