Creating deployment manager profiles using the Profile Management Tool
You can create a deployment manager profile using the Profile Management Tool.
About this task
You cannot select the name of the IBM BPM CellAdmin authentication alias when using the Profile Management Tool. The name automatically defaults to CellAdminAlias. (Using the BPMConfig command, you can set the bpm.cell.authenticationAlias.1.name property in the configuration properties file. And using the manageprofiles command, you can supply the -adminAliasName parameter with a customized authentication alias name.)
Restrictions:
- To run the Profile Management Tool on Windows 7, Windows Vista,
or Windows Server 2008, you
must elevate your Microsoft Windows user account privileges.
Whether you are an administrative user or a non-administrative user,
right-click the pmt.bat file and select Run
as administrator. Alternatively, use the runas command
at the command line. For example, the following command can be run
from the installation_root\bin\ProfileManagement directory:
Non-administrative users are prompted for the administrator password.runas /user:MyAdminName /env pmt.bat
- If you install multiple instances of IBM® Business Process Manager as the root user and give a nonadministrative user access to only a subset of those instances, the Profile Management Tool does not function correctly for the nonadministrative user. In addition, a com.ibm.wsspi.profile.WSProfileException or Access is denied message occurs in the installation_root\bin\ProfileManagement\pmt.bat file. By default, nonadministrative users do not have access to the Program Files directory, which is the default installation location for the product. To resolve this issue, nonadministrative users must either install the product by themselves or be given permission to access the other product instances.
Procedure
What to do next
- Add managed-node profiles to be managed by the deployment manager, and then configure the deployment environment.