manageprofiles command parameters

Use the following parameters with the manageprofiles command for WebSphere Process Server.

CAUTION:
Do not add any new parameters or change any existing parameter values other than those mentioned in this topic when creating or augmenting a WebSphere Process Server profile.
Some parameters listed below can also be used with the wasprofile command for WebSphere Application Server. For more information, refer to the descriptions of the parameters of the same names in the documentation for the wasprofile command in the WebSphere Application Server Network Deployment, version 6.0 information center.
Important: If a value contains any space characters or quotation marks, enclose the entire value in quotation marks. If a value includes a quotation mark, type a backslash in front of the quotation mark.
-appSchedulerServer server_name
If you are creating or augmenting a stand-alone profile then ensure that the server name you specify matches an existing server name under that profile. If you are creating a new profile, set server_name to "server1." If you are augmenting an existing profile, ensure that server_name matches an existing server name for the profile you are augmenting. In most cases, this name will be "server1."
-augment
This indicates to the manageprofiles command-line tool that you wish to augment an existing profile. Do not change this parameter if it is in your captured command line.
-bpcmqPwd password
If you are creating or augmenting a stand-alone profile and chose to configure a sample Business Process Choreographer, then change the corresponding value "MASKED_PARAMETER_VALUE" to the password you specified on the "Business Process Choreographer Configuration" panel in the Profile wizard for the user ID you had entered.
-ceiDbPwd password
If you are creating or augmenting a stand-alone profile and you chose to create a database for the Common Event Infrastructure configuration using a database type other than the Cloudscape(TM) value, then change the corresponding value "MASKED_PARAMETER_VALUE" to the password you specified on the "Additional Database Configuration Information for Common Event Infrastructure" panel in the Profile wizard for the user ID you had entered.
-ceiDbSysPwd password
If you are creating or augmenting a stand-alone profile and you chose to create an Oracle database for the Common Event Infrastructure configuration, then change the corresponding value "MASKED_PARAMETER_VALUE" to the password you specified on the "Additional Database Configuration Information for Common Event Infrastructure" panel in the Profile wizard for the user ID with SYSDBA authority you had entered.
-ceiSampleJmsPwd password
If you are creating or augmenting a stand-alone profile then change the corresponding value "MASKED_PARAMETER_VALUE" to the password you specified on the "Common Event Infrastructure Configuration" panel in the Profile wizard for the user ID you had entered.
-ceiSampleServerName server_name
If you are creating or augmenting a stand-alone profile then ensure that the server name you specify matches an existing server name under that profile. If you are creating a new profile, set server_name to "server1." If you are augmenting an existing profile, ensure that server_name matches an existing server name for the profile you are augmenting. In most cases, this name will be "server1."
-cellName cell_name
Specifies the cell name of the profile. Use a unique cell name for each profile. Use a unique name even though you plan to federate the custom profile into a deployment manager cell. Federation requires unique cell names before it can make the node part of the deployment manager cell. A cell name must be unique in any circumstance in which the product is running on the same physical machine or cluster of machines (such as a sysplex). Additionally, a cell name must be unique in any circumstance in which network connectivity between entities is required either between the cells or from a client that must communicate with each of the cells. Cell names also must be unique if their name spaces are going to be federated. Otherwise, you might encounter symptoms such as a javax.naming.NameNotFoundException, in which case, you will need to create uniquely named cells.
-create
This indicates to the manageprofiles command-line tool that you wish to create a new profile. Do not change this parameter if it is in your command line.
-dbPassword password
If you entered a user ID and password value on the "Additional Database Configuration Information" panel then change the corresponding value "MASKED_PARAMETER_VALUE" to the password you specified for the user ID you entered on that panel.
-dmgrHost host_name
Identifies the machine where the deployment manager is running. Specify this parameter and the -dmgrPort parameter to federate a custom profile as it is created.

The host name can be the long or short DNS name or the IP address of the deployment manager machine.

Specifying this optional parameter directs the manageprofiles command to attempt to federate the custom node into the deployment manager cell as it creates the custom profile. This parameter is ignored when creating a deployment manager profile or a stand-alone process server profile.

Federating when the deployment manager is not available

If you federate a custom node when the deployment manager is not running or is not available, the installation indicator in the logs is INSTCONFFAILED to indicate a complete failure. The resulting custom profile is unusable. You must move the custom profile directory out of the profile repository (the profiles installation root directory) before creating another custom profile with the same profile name.

If you have enabled security or changed the default JMX connector type, you cannot federate with the manageprofiles command. Use the addNode command instead.

-dmgrPort port_number
Identifies the SOAP port of the deployment manager. Specify this parameter and the dmgrHost parameter to federate a custom profile as it is created. The deployment manager must be running and accessible. If you have enabled security or changed the default JMX connector type, you cannot federate with the wasprofile command. Use the addNode command instead.
-federateLater true | false
If this is set to "true" a custom profile on a create will not be federated to the deployment manager even if -dmgrPort and -dmgrHost are specified. If it is set to "false" then both -dmgrPort and -dmgrHost must be specified.
-hostName host_name
Specifies the host name where you are creating the profile. This value must match the host name that you specified during installation of the initial product.
-nodeName node_name
Specifies the node name for the node that is created with the new profile. Use a unique value within the cell or on the machine. Each profile that shares the same set of product binaries must have a unique node name.
-portsFile file_path
If you are creating a new profile, you must add either the -startingPoint parameter or the -portsFile parameter to the end of your command line. The -portsFile parameter specifies the path to a file that defines port settings for the new profile. When omitted, the manageprofiles command looks for the file
install_root/profileTemplates/profile_type/actions/portsUpdate/bin  \
/portdef.props
-profileName profile_name
Profile name is the unique identifier for a given profile.
-profilePath profile_path

Icon indicating Windows platforms On Windows platforms: Specify the full path to avoid an ANT scripting limitation that can cause a failure when federating the profile into a cell. For example: -profilePath C:\IBM\WebSphere\ProcServer\profiles\profile01.

scaSecurityPassword password
If you are creating or augmenting a stand-alone server profile and chose to configure the Service Integration Bus in a secured mode, then change the corresponding value "MASKED_PARAMETER_VALUE" to the password you specified on the "Service Component Architecture configuration" panel in the Profile wizard for the user ID you had entered.
-startingPort startingPort
If you are creating a new profile, you must add either the -startingPort parameter or the -portsFile parameter to the end of your command line. This parameter specifies the starting port number for generating all ports for the profile. If not specified, the command uses default ports specified in the serverindex.xml file. Do not use this parameter with the -portsFile parameter.
-templatePath template_path
Specifies the directory path to the template files in the installation root directory. Change the value of template_path only if you are creating or augmenting a profile for a different WebSphere Process Server installation.
-winservicePassword password
Icon indicating Windows platforms On Windows platforms: This is a password value that will have been masked out. If you are running on Microsoft Windows and your command line has the parameter value for "true" for the parameter name -winserviceCheck, then change the corresponding value "MASKED_PARAMETER_VALUE" to the password you specified in the Profile wizard for the user or the local account that is to own the Windows service.

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