Augmenting managed-node profiles using the manageprofiles command-line utility

Instead of using the Profile Management Tool, you can use the manageprofiles command-line utility to augment existing WebSphere® Application Server profiles.

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.

Note: The deployment manager profile for this managed-node profile must already be augmented with IBM BPM.

Restriction: You cannot augment a managed-node profile where the default WebSphere VMM user registry has been changed, for example, to using LDAP. Also, you cannot augment a managed-node profile unless administrative security has been enabled. If the managed-node profile is not yet federated, you cannot federate it as part of IBM BPM augmentation. You will need to federate the managed-node profile after augmentation, as described in the topic "Federating nodes to the deployment manager."

Restriction: To run the manageprofiles command on Windows 7, Windows Vista, or Windows Server 2008, you must elevate your Microsoft Windows user account privileges using the runas command. Remember to put double quotation marks around the manageprofiles command and all parameters. For example, the following command can be run from the installation_root\bin directory:

runas /env /user:MyAdminName "manageprofiles.bat"

Non-administrative users are prompted for the administrator password.

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/BpmNode -adminAliasName CellAdminAlias -adminUserName adminUserName -adminPassword adminPassword
```
The status is written to the console window when the command completes running.

What to do next

After you have finished adding managed-node profiles, configure the deployment environment.