When the Profile creation wizard is used (interactively or silently)
to initially create or augment a profile, a command-line version of the profile
creation or augmentation is written to a log file. You can extract this command
line from the log file, modify it, and use it to create or augment other profiles.
Before you begin
To use manageprofiles with WebSphere ESB,
you should have already used the Profile creation wizard (graphical user interface
or with silent response files) to create a new profile or augment an existing
profile with the options you desire. (Do not use manageprofiles to
initially construct an augmentation or creation command.)
Why and when to perform this task
The command line resulting from using the Profile creation 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.
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). Do not
switch these parameters in the command line. For example, do not substitute -create for -augment.
The resulting scripts will not work because other parameters and arguments
will be incorrect.
Note: WebSphere ESB does
not support augmenting a profile which is federated to a deployment manager.
You must first unfederate such a profile, then augment it, and then run the
addNode command line tool to re-federate it.
Steps for this task
- After you have created or augmented a profile using the Profile
creation 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.
- 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.
- Select the text starting with "CAPTURED COMMAND LINE"
until the end of the file.
- Copy this text to a new file.
- In the new file, remove from the copied string everything up
to and including the words "CAPTURED COMMAND LINE."
- Save the file. (Any unique valid file name can be used). You now have the command line equivalent of the prior Profile
creation wizard execution, saved in this file.
- 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.
.
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 want 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 template in the command line is of the same type (standalone,
deployment manager, or custom) of the profile you wish to augment. Failure
to ensure this can yield incorrect results. |
Creating a new profile |
Modify -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 creation wizard. The command line does not
include the ports that you defined when you originally used the Profile creation
wizard. Add either the -portsFile or the -startPort 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 at the WebSphere Application Server information center. |
Using this command line on another WebSphere ESB 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 ESB installation
and modify the qualified path to the directory location where this command
file will be found. |
- Use the modified command line file to create a new profile or augment
an existing profile..
- Make the file executable.
For UNIX and Linux systems, give the file a .sh extension
and give it execute permissions.
For Windows systems, give the file a .bat extension.
- Run the file from the command line. The command will
display status as it executes. Wait for it to finish.
Example
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 "ESB01" -profilePath
"/opt/o054 4.12/profiles/ESB01" -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" -scaSecurityPassword "MASKED_PARAMETER_VALUE"
Here
is an example of the command line, now modified to remove file header information
and replace masked passwords. 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 "rootPassword"
-winserviceStartupType "manual" -dbJDBCClasspath "null" -dbType "CLOUD SCAPE"
-ceiSampleJmsUser "root" -ceiSampleJmsPwd "myRootPwd"
-cei SampleServerName "server1" -ceiDbProduct "CLOUDSCAPE_V51_1" -ceiDbName ""
-ce iDbUser "" -ceiDbPwd "myPassword" -ceiDbSysUser "" -ceiDbSysPwd "myPassword"
-ceiDbJdbcDriverClasspath "" -ceiDbJdbcDriverType "" -ceiDbServerName ""
-ceiDbServerPort "" -ceiDbNodeName "" -ceiDbExecuteScript s "" -configureScaSecurity
"true" -scaSecurityUserId "root" -scaSecurityPassword "myRootPwd"

The following example shows such a script being executed
on a Unix system. In this case
"myCommandline.sh" is the
name of the script that has been created:
/opt/IBM/WebSphere/ESB/bin>myCommandline.sh
INSTCONFSUCCESS: The profile now exists.
INSTCONFSUCCESS: Profile augmentation succeeded.
INSTCONFSUCCESS: Profile augmentation succeeded.
/opt/IBM/WebSphere/ESB/bin>

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