Creating profiles using the manageprofiles command

When you use the Profile wizard (interactively or silently) to initially create a profile, a command-line version of the profile creation is written to a log file. You can extract this command line from the log file, modify it, and use it to create other profiles.

Before you begin

Before using this procedure, ensure that you have reviewed the list of prerequisites for creating or augmenting a profile at Prerequisites for creating or augmenting profiles.
Important: You cannot run the manageprofiles command on one set of core product files concurrently with an instance of the WebSphere Process Server Profile wizard or WebSphere Application Server or WebSphere Application Server Network Deployment Profile creation wizard. Attempts to create profiles concurrently result in a warning. If a warning panel is displayed, determine if there is another profile creation or augmentation action occurring.
  • If there is, you must wait until it completes.
  • If there is not, delete the file profileRegistry.xml_LOCK in the directory install_root/properties if it exists. You can then run the manageprofiles command.

Why and when to perform this task

To use the manageprofiles command with WebSphere Process Server, you must have already used the Profile wizard interactively or silently to create a new profile with the options you desire. (Do not use the manageprofiles command to initially construct a create command.) The wizard writes the command line used to create the profile to a log file. You can modify this command and then execute it from the command line to create a similar profile.
A captured command line that was used to create a profile will have the parameter -create within it (usually in the form manageprofiles -create).
Important: Never replace the parameter -create with the parameter -augment. If you do this, the resulting scripts will not work because other parameters and arguments will be incorrect.

Steps for this task

  1. After you have created a profile using the Profile wizard or silently with response files, open the log file that was generated. The file path and name are 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 manageprofiles command that was used to create this profile.
  3. Using a text editor, modify the command line you saved to reflect the new profile creation you wish to perform. Do not change any other values or add any extra parameters that are not already in the command line or specified in manageprofiles command parameters. Some parameters might appear that are not applicable to your operating system. They can remain and will not result in errors.
    Be sure to address the following when you modify the command line:
    • Modify the values of the parameters -profileName, -profilePath, -cellName, and -nodeName to make sure they are unique.
    • The command line does not include the ports that you defined when you originally used the Profile wizard. Add either the -portsFile or the -startingPort parameter and an appropriate port value to the end of the command line.

      For more information on specifying these ports, refer to the topic wasprofile command in the WebSphere Application Server Network Deployment, version 6.0 information center.

    • For security reasons, the string "MASKED_PARAMETER_VALUE" has been inserted instead of any specified passwords. You must replace all instances of this string with valid passwords. Refer to manageprofiles command parameters for more information.
    • If you are going to run this command to create a profile for a different installation of WebSphere Process Server, check all the path name values, including the qualified path of the manageprofiles.sh or manageprofiles.bat file, and modify them if necessary.
  4. Use the modified command line file to create a new 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 displays status as it runs. Wait for it to finish.

Example

Here is an example of a captured (unmodified) command line for creating a new profile, as indicated by the -create parameter:


(Oct 12, 2006 9:42:58 AM), Install, com.ibm.ws.install.wbiserver.ismp.actions.
CalculateManagedProfileInvocationAction, msg1, CAPTURED_COMMAND_LINE_DESC: 
The following line is the command line equivalent of your run of the Profile Wizard. 
It is different in that the ports (-portsFile) you have selected are not included. 
Also this command line will not federate the profile. Parameter values you may want 
to change are profileName, profilePath, nodeName, cellName, hostName, dmgrHost, dmgrPort, 
and any password values which have been masked out .


(Oct 12, 2006 9:42:58 AM), Install, com.ibm.ws.install.wbiserver.ismp.actions.
CalculateManagedProfileInvocationAction, msg1, CAPTURED_COMMAND_LINE: 
"/BUILD1/ProcServer01/bin/manageprofiles.sh" -create -profileName "ProcSrv02" 
-profilePath "/BUILD1/ProcServer01/profiles/ProcSrv02" -templatePath 
"/BUILD1/ProcServer01/profileTemplates/default.wbiserver" -hostName "mohawkvalley.site" 
-nodeName "mohawkvalleyNode09" -cellName "mohawkvalleyNode16Cell" -dmgrHost "localhost" 
-dmgrPort "8879" -OS_NAME "Linux" -winserviceCheck "true" -winserviceAccountType "localsystem" 
-winserviceUserName "root" -winservicePassword "MASKED_PARAMETER_VALUE" 
-winserviceStartupType "manual" -dbJDBCClasspath "null" -dbType "CLOUDSCAPE" 
-ceiSampleJmsUser "root" -ceiSampleJmsPwd "MASKED_PARAMETER_VALUE" -ceiSampleServerName "server1" 
-ceiDbProduct "CLOUDSCAPE_V51_1" -ceiDbName "" -ceiDbUser "" -ceiDbPwd "MASKED_PARAMETER_VALUE" 
-ceiDbSysUser "" -ceiDbSysPwd "MASKED_PARAMETER_VALUE" -ceiDbJdbcDriverClasspath "" 
-ceiDbJdbcDriverType "" -ceiDbServerName "" -ceiDbServerPort "" -ceiDbStorageGroup "" 
-ceiDbNodeName "" -ceiDbConnectionLocation "" -ceiDbExecuteScripts "" -configureScaSecurity "true" 
-scaSecurityUserId "root" -scaSecurityPassword "MASKED_PARAMETER_VALUE" -bpcadminUsers "root" 
-bpcmqUser "root" -bpcmqPwd "MASKED_PARAMETER_VALUE" -dbName "WPRCSDB01" -dbLocation "" 
-dbUserId "" -dbPassword "MASKED_PARAMETER_VALUE" -dbServerPort "null" -dbHostName "localhost" 
-dbInstance "ol_" -dbCreateNew "true" -dbDelayConfig "false" -dbStorageGroup "" 
-dbConnectionLocation "" -configureAppScheduler "true" -appSchedulerServer "server1" 

(Oct 12, 2006 9:42:58 AM), Install, com.ibm.ws.install.ni.ismp.actions.ISMPLogSuccessMessageAction, msg1, INSTCONFSUCCESS

Here is an example of the command line, now modified to remove file header and result information. Before using, you would also have to replace all values of "MASKED_PARAMETER_VALUE" with the appropriate passwords for your configuration:
/BUILD1/ProcServer01/bin/manageprofiles.sh -create -profileName "ProcSrv02" 
-profilePath "/BUILD1/ProcServer01/profiles/ProcSrv02" -templatePath 
"/BUILD1/ProcServer01/profileTemplates/default.wbiserver" -hostName "mohawkvalley.site" 
-nodeName "mohawkvalleyNode09" -cellName "mohawkvalleyNode16Cell" -dmgrHost "localhost" 
-dmgrPort "8879" -OS_NAME "Linux" -winserviceCheck "true" -winserviceAccountType "localsystem" 
-winserviceUserName "root" -winservicePassword "MASKED_PARAMETER_VALUE" 
-winserviceStartupType "manual" -dbJDBCClasspath "null" -dbType "CLOUDSCAPE" 
-ceiSampleJmsUser "root" -ceiSampleJmsPwd "MASKED_PARAMETER_VALUE" -ceiSampleServerName "server1" 
-ceiDbProduct "CLOUDSCAPE_V51_1" -ceiDbName "" -ceiDbUser "" -ceiDbPwd "MASKED_PARAMETER_VALUE" 
-ceiDbSysUser "" -ceiDbSysPwd "MASKED_PARAMETER_VALUE" -ceiDbJdbcDriverClasspath "" 
-ceiDbJdbcDriverType "" -ceiDbServerName "" -ceiDbServerPort "" -ceiDbStorageGroup "" 
-ceiDbNodeName "" -ceiDbConnectionLocation "" -ceiDbExecuteScripts "" -configureScaSecurity "true" 
-scaSecurityUserId "root" -scaSecurityPassword "MASKED_PARAMETER_VALUE" -bpcadminUsers "root" 
-bpcmqUser "root" -bpcmqPwd "MASKED_PARAMETER_VALUE" -dbName "WPRCSDB01" -dbLocation "" 
-dbUserId "" -dbPassword "MASKED_PARAMETER_VALUE" -dbServerPort "null" -dbHostName "localhost" 
-dbInstance "ol_" -dbCreateNew "true" -dbDelayConfig "false" -dbStorageGroup "" 
-dbConnectionLocation "" -configureAppScheduler "true" -appSchedulerServer "server1" 

Icon indicating Linux platforms Icon indicating UNIX platforms On Linux and UNIX platforms: The following example shows such a script being executed on a Solaris system. In this case, "myCommandline.sh" is the name of the script that has been created. The default installation directory shown (/opt/IBM/WebSphere/ProcServer/) will differ depending on platform.
/opt/IBM/WebSphere/ProcServer/bin>myCommandline.sh
INSTCONFSUCCESS: The profile now exists.
INSTCONFSUCCESS: Profile creation succeeded.
INSTCONFSUCCESS: Profile creation 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 creation succeeded.
INSTCONFSUCCESS: Profile creation succeeded.


C:\Program Files\IBM\WebSphere\ProcServer\bin>


Last updated: Wed 01 Nov 2006 07:47:12

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