Instead
of using the Profile Management Tool, you can use the manageprofiles
command-line utility to augment existing WebSphere® Application
Server V8.0 custom
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.
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
install_root\bin directory:
runas /env /user:MyAdminName "manageprofiles.bat -response myResponseFile"
Non-administrative
users are prompted for the administrator password.
Procedure
- Determine the template that was used to create
the existing profile that you want to augment. You
must augment a deployment manager profile. You can determine the template by viewing the profile
registry in the install_root\properties\profileRegistry.xml file.
Do not modify this file; use it only to view the templates.
- Find the appropriate template to use
for the augmentation.
Templates for each profile are located
in the install_root\profileTemplates\BPM directory
for BPM templates.
The following templates are available:- dmgr.procctr: for a Process
Center deployment manager profile for IBM BPM Standard.
- dmgr.procsvr:
for a Process Server deployment manager profile for IBM BPM Standard.
- 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 augmentation templates that you can use are determined by which IBM® products and versions are installed
in your environment. Make sure that you specify the fully qualified
file path for -templatePath, because a relative
file path for the -templatePath parameter results
in the specified profile not being fully augmented.
Note: Do not manually modify the files that are
located in the install_dir/profileTemplates/BPM directory.
- To use the -responseFile parameter,
look at the provided sample response files and create a response file
that is specific to your environment.
Important: Ensure that you do not
leave blank spaces after the values; for example 'personalCertValidityPeriod=1
' or 'winserviceCheck=false '. Spaces will
cause profile creation to fail.
The samples are located in
the install_root\BPM\samples\manageprofiles directory.
Choose an appropriate response file based
on the database and type of profile (stand-alone or network, Process Center or Process Server).
The following sample files are available:- PC_Std_DMgr_DB2.response
- PC_Std_DMgr_DB2zOS.response
- PC_Std_DMgr_Oracle.response
- PC_Std_DMgr_SQLServer.response
- PC_Std_Managed_DB2.response
- PC_Std_Managed_DB2zOS.response
- PC_Std_Managed_Oracle.response
- PC_Std_Managed_SQLServer.response
- PC_Std_Standalone_DB2.response
- PC_Std_Standalone_DB2zOS.response
- PC_Std_Standalone_Oracle.response
- PC_Std_Standalone_SQLServer.response
- PS_Std_DMgr_DB2.response
- PS_Std_DMgr_DB2zOS.response
- PS_Std_DMgr_Oracle.response
- PS_Std_DMgr_SQLServer.response
- PS_Std_Managed_DB2.response
- PS_Std_Managed_DB2zOS.response
- PS_Std_Managed_Oracle.response
- PS_Std_Managed_SQLServer.response
- PS_Std_Standalone_DB2.response
- PS_Std_Standalone_DB2zOS.response
- PS_Std_Standalone_Oracle.response
- PS_Std_Standalone_SQLServer.response
Copy one of the sample response files to your working directory. Edit the parameters in the response file as
appropriate to your configuration and save the edited response file.
Make sure that the templatePath property path
matches your specific installation directory.
- Run the file from the command line.
Do not supply a -profilePath parameter. For example:
manageprofiles.bat -augment -templatePath install_root/profileTemplates/BPM/dmgr.procctr -profileName MyProfileName
If you have created a response
file, specify the
-response parameter without
any other parameters. For example:
manageprofiles.sh -response myResponseFile
What to do next
- Add custom (managed nodes) profiles to be managed by the deployment
manager and then configure the deployment environment.