Icon indicating 6.0.1 content only

Using the manageprofiles command to create and augment profiles

Extract an existing manageprofiles command line from a log file to repeat or perform a similar profile creation or augmentation on the same or another system.

Before you begin

To use manageprofiles with WebSphere Process Server, you should have already used the Profile Wizard (graphical user interface or with silent response files) to create a new profile or augment an existing profile with the options you desire. (Using manageprofiles to initially construct an augmentation or creation process is not recommended.)

Why and when to perform this task

The command line resulting from using the Profile Wizard or silent installation will have been captured in a log file. You will use the contents of this log file to create a similar command line to be used in subsequent profile creation or augmentation using the manageprofiles command.
Important: A captured command line that was used to create a profile will have the parameter -create within it (usually in the form manageprofiles -create). A captured command line that was used to augment a profile will have the parameter -augment within it (usually in the form manageprofiles -augment). The command line will have either the parameter -create or the parameter -augment, not both. Never switch these; that is never substitute -create for -augment or replace -augment with -create. If you do this, the resulting scripts will most likely not work because other parameters and arguments will be incorrect.
Restriction: WebSphere Process Server does not support augmenting a profile which is federated to a deployment manager by using the Profile Wizard. You must first unfederate such a profile, then augment it, and then run the addNode command-line tool to refederate it. See Augmenting a federated profile manually for more information.

Steps for this task

  1. After you have created or augmented a profile using the Profile Wizard or silent installation, open the log file that was generated. The file path and name is as follows: profile_root/logs/pcatLogNNNNNNNNNNNNN.txt, where profile_root is the directory in which the profile was created and NNNNNNNNNNNNN is a timestamp value.
  2. In the log file, search for the line that starts with "CAPTURED_COMMAND_LINE:" and save this line (including any wrapped text beneath it) to a new file.
    1. Select the text starting with "CAPTURED_COMMAND_LINE" until the end of the file.
    2. Copy this text to a new file.
    3. In the new file, remove from the copied string everything up to and including the words "CAPTURED_COMMAND_LINE."
    4. Save the file. (Any unique valid file name can be used.) You now have the command-line equivalent of the prior Profile Wizard execution, saved in this file.
  3. Modify the command line to reflect any changes. Using a text editor, you must now modify the command you saved to reflect the new profile creation or augmentation you wish to perform. The following values must or can be modified.
    Note: Do not change any other values or add any extra parameters that are not already in the command line or specified in manageprofiles parameters. Some parameters might appear that are not applicable to your operating system but they can remain and will not result in an error.
    If you are... Then...
    Creating or augmenting a profile You must replace occurrences of the string "MASKED_PARAMETER_VALUE" anywhere in the file with valid passwords. The string "MASKED_PARAMETER_VALUE" has been inserted instead of the specified password for security reasons. You will need to replace these strings. Refer to manageprofiles parameters for more information.
    Augmenting an existing profile Make sure the values of the parameters -profileName, -profilePath, -cellName, and -nodeName exactly match those of the profile you wish to augment. You might or might not have to modify the values, depending on the origin of the command line and which profile you will be modifying.
    Augmenting an existing profile Make sure the profile in the command line is of the same type (stand-alone, deployment manager, or custom) of the profile you wish to augment. Failure to ensure this can yield unpredictable results.
    Creating a new profile Modify the values of -profileName, -profilePath, -cellName, and -nodeName to make sure they are unique.
    Creating a new profile Re-specify the ports that you defined in the Profile Wizard. The command line does not include the ports that you defined when you originally used the Profile Wizard. Add either the -portsFile or the -startPoint parameter and an appropriate port value to the end of the command line.
    For more information on specifying these ports, refer to the information on the wasprofile command in the WebSphere Application Server Network Deployment, version 6.0 information center at

     http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/index.jsp
    Using this command line on another WebSphere Process Server installation (either on the same computer for which the original profile was created or another) If necessary, modify the path name values to reflect the location of the different WebSphere Process Server installation and modify the qualified path to the directory location where this command file will be found.
  4. Use the modified command-line file to create a new profile or augment an existing profile.
    1. Make the file executable.
      • Icon indicating Linux platforms Icon indicating UNIX platforms On Linux and UNIX platforms: Give the file a .sh extension and give it execute permissions.
      • Icon indicating Windows platforms On Windows platforms: Give the file a .bat extension.
    2. Run the file from the command line. The command will display status as it executes. Wait for it to finish.

Here is an example of a captured (unmodified) command line for creating a new profile. In this case the command was used to create a new profile, as indicated by the -create parameter:

(Nov 3, 2005 9:24:08 AM), Install, com.ibm.ws.install.wbiserver.ismp.actions.
CalculateManagedProfileInvocationAction, msg1, CAPTURED_COMMAND_LINE:
 /opt/o0544.1 2/bin/manageprofiles.sh -create -profileName "ProcSrv01" -profilePath 
"/opt/o054 4.12/profiles/ProcSrv01a" -templatePath "/opt/o0544.12/profileTemplates/default wbiserver"
 -federateLater "true" -hostName  "eexfvt99.rchland.ibm.com" -nodeName "eexfvt99Node28"
 -cellName  "eexfvt99Node26Cell" -dmgrHost  "localhost" -dmgrP ort  "8879" -OS_NAME  "Linux" 
-winserviceCheck  "true" -winserviceAccountType  " localsystem" -winserviceUserName  "root"
 -winservicePassword  "MASKED_PARAMETER_ VALUE" -winserviceStartupType  "manual" -dbJDBCClasspath 
 "null" -dbType  "CLOUD SCAPE" -ceiSampleJmsUser  "root" -ceiSampleJmsPwd  "MASKED_PARAMETER_VALUE"
 -cei SampleServerName  "server1" -ceiDbProduct  "CLOUDSCAPE_V51_1" -ceiDbName  "" 
-ce iDbUser  "" -ceiDbPwd  "MASKED_PARAMETER_VALUE" -ceiDbSysUser  ""
 -ceiDbSysPwd "MASKED_PARAMETER_VALUE" -ceiDbJdbcDriverClasspath  "" 
-ceiDbJdbcDriverType  "" -ceiDbServerName  "" -ceiDbServerPort  ""
 -ceiDbNodeName  "" -ceiDbExecuteScript s  "" -configureScaSecurity  "true" -scaSecurityUserId 
 "root" -scaSecurityPassw ord  "MASKED_PARAMETER_VALUE" -adminBFMGroups  "sadday" 
-mqUser  "root" -mqPwd "MASKED_PARAMETER_VALUE" -dbName  "WPRCSDB" -dbLocation  "" 
-dbUserId  "" -dbPas sword  "MASKED_PARAMETER_VALUE" -dbServerPort  "null" 
-dbHostName  "localhost" - dbInstance  "ol_" -dbCreateNew  "true" -dbStorageGroup  ""
 -dbConnectionLocation "" -configureAppScheduler  "true" -appSchedulerServer  "server1" 
Here is an example of the command line, now modified to remove file header information and replace masked passwords.
/opt/o0544.1 2/bin/manageprofiles.sh -create -profileName "myProfile"
 -profilePath "/opt/o054 4.12/profiles/myProfile" -templatePath "/opt/o0544.12/profileTemplates/default
  wbiserver" -federateLater "true" -hostName  "eexfvt99.rchland.ibm.com"
 -nodeName "myNodeName" -cellName  "myCellName" -dmgrHost  "localhost" 
-dmgrPort  "8879" -OS_NAME  "Linux" -winserviceCheck  "true" -winserviceAccountType 
 " localsystem" -winserviceUserName  "root" -winservicePassword  "MASKED_PARAMETER_VALUE" 
-winserviceStartupType  "manual" -dbJDBCClasspath  "null" -dbType  "CLOUD SCAPE"
 -ceiSampleJmsUser  "root" -ceiSampleJmsPwd  "myRootPwd" 
-cei SampleServerName  "server1" -ceiDbProduct  "CLOUDSCAPE_V51_1" -ceiDbName  "" -ce iDbUser  "
" -ceiDbPwd  "MASKED_PARAMETER_VALUE" -ceiDbSysUser  "" -ceiDbSysPwd "MASKED_PARAMETER_VALUE"
 -ceiDbJdbcDriverClasspath  "" -ceiDbJdbcDriverType  "" -ceiDbServerName  ""
 -ceiDbServerPort  "" -ceiDbNodeName  "" -ceiDbExecuteScript s  "" -configureScaSecurity
  "true" -scaSecurityUserId  "root" -scaSecurityPassword  "myRootPwd" 
-adminBFMGroups  "sadday" -mqUser  "root" -mqPwd "myRootPwd" -dbName  "WPRCSDB"
 -dbLocation  "" -dbUserId  "" -dbPassword  "MASKED_PARAMETER_VALUE" -dbServerPort 
 "null" -dbHostName  "localhost" - dbInstance  "ol_" -dbCreateNew  "true" 
-dbStorageGroup  "" -dbConnectionLocation "" -configureAppScheduler  "true" -appSchedulerServer  
"server1" 
Icon indicating AIX platforms On AIX platforms: The following example shows such a script being executed on an AIX system. In this case "myCommandline.sh" is the name of the script that has been created:
/usr/IBM/WebSphere/ProcServer/bin>myCommandline.sh
INSTCONFSUCCESS: The profile now exists.
INSTCONFSUCCESS: Profile augmentation succeeded.
INSTCONFSUCCESS: Profile augmentation succeeded.
INSTCONFSUCCESS: Profile augmentation succeeded.

/usr/IBM/WebSphere/ProcServer/bin>
Icon indicating HP-UX platforms Icon indicating Solaris platforms On HP-UX and Solaris platforms: The following example shows such a script being executed on a WebSphere Process Server HP-UX or Solaris system. In this case "myCommandline.sh" is the name of the script that has been created:
/opt/IBM/WebSphere/ProcServer/bin>myCommandline.sh
INSTCONFSUCCESS: The profile now exists.
INSTCONFSUCCESS: Profile augmentation succeeded.
INSTCONFSUCCESS: Profile augmentation succeeded.
INSTCONFSUCCESS: Profile augmentation succeeded.

/opt/IBM/WebSphere/ProcServer/bin>
Icon indicating Linux platforms Icon indicating 6.0.1 content only On Linux platforms: The following example shows such a script being executed on a WebSphere Process Server, version 6.0.1 Linux system. In this case "myCommandline.sh" is the name of the script that has been created:
/opt/ibm/WebSphere/ProcServer/bin>myCommandline.sh
INSTCONFSUCCESS: The profile now exists.
INSTCONFSUCCESS: Profile augmentation succeeded.
INSTCONFSUCCESS: Profile augmentation succeeded.
INSTCONFSUCCESS: Profile augmentation succeeded.

/opt/ibm/WebSphere/ProcServer/bin>
Icon indicating Linux platforms Icon indicating 6.0.0 content only On Linux platforms: The following example shows such a script being executed on a WebSphere Process Server, version 6.0.0 Linux system. In this case "myCommandline.sh" is the name of the script that has been created:
/opt/IBM/WebSphere/ProcServer/bin>myCommandline.sh
INSTCONFSUCCESS: The profile now exists.
INSTCONFSUCCESS: Profile augmentation succeeded.
INSTCONFSUCCESS: Profile augmentation succeeded.
INSTCONFSUCCESS: Profile augmentation succeeded.

/opt/IBM/WebSphere/ProcServer/bin>
Icon indicating Windows platforms On Windows platforms: The following example shows such a script being executed on a Windows system. In this case "myCommandline.bat" is the name of the script that has been created:
C:\Program Files\IBM\WebSphere\ProcServer\bin>myCommandline.bat
INSTCONFSUCCESS: The profile now exists.
INSTCONFSUCCESS: Profile augmentation succeeded.
INSTCONFSUCCESS: Profile augmentation succeeded.
INSTCONFSUCCESS: Profile augmentation succeeded.

C:\Program Files\IBM\WebSphere\ProcServer\bin>
Related reference
manageprofiles command for use with WebSphere Process Server, version 6.0.1
manageprofiles parameters

Terms of use |

Last updated: Tue Feb 21 17:47:11 2006

(c) Copyright IBM Corporation 2005.
This information center is powered by Eclipse technology (http://www.eclipse.org)