manageprofiles parameters

You can omit this parameter only when -enableAdminSecurity for WebSphere® ESB profiles is set to false.

The same password is set for all internal administrative accounts, including tw_admin and tw_user.

This parameter is a WebSphere Application Server parameter.

Valid settings include the following levels:

• standard
• production
• development

See information about tuning the application server in the WebSphere Application Server information center.

This parameter is not supported with IBM Business Process Manager.

This parameter replaces the -wbidbDesign that was used in previous versions of WebSphere Process Server and WebSphere ESB.

DB2® database

The default schema name is the value specified by the dbUserId parameter.

The -cdbSchemaName parameter is valid for all database types except for Oracle and Microsoft SQL Server.

Do not use this parameter if you are using -bpmdbDesign.

if (DMgr)
	shortHostNameCellCellNumber
else
	shortHostNameNodeNodeNumberCell

The value for this parameter must not contain spaces or any characters that are not valid such as the following characters: *, ?, ", <, >, ,, /, \, and |.

Specify manageprofiles -create -templatePath fully_qualified_path_to_template -help for specific information about creating a profile. See the templatePath parameter for a list of available templates. The template_path parameter is required when you are creating a profile.

Do not use this parameter if you are using -bpmdbDesign.

Do not use this parameter if you are using -bpmdbDesign.

Do not use this parameter if you are using -bpmdbDesign.

Do not use this parameter if you are using -bpmdbDesign.

Do not use this parameter if you are using -bpmdbDesign.

Do not use this parameter if you are using -bpmdbDesign.

Do not use this parameter if you are using -bpmdbDesign.

For any type of database, other than DB2 for z/OS, the value can be true.

Do not use this parameter if you are using -bpmdbDesign.

Do not use this parameter if you are using -bpmdbDesign.

• DB2
• SQLServer
• Oracle

Do not use this parameter if you are using -bpmdbDesign.

Do not use this parameter if you are using -bpmdbDesign.

The name of the database. By default, the value is set to orcl for Oracle databases and to CMNDB for all other supported databases.

Do not use this parameter if you are using -bpmdbDesign.

Do not use this parameter if you are using -bpmdbDesign.

Do not use this parameter if you are using -bpmdbDesign.

Do not use this parameter if you are using -bpmdbDesign.

Do not use this parameter if you are using -bpmdbDesign.

Do not use this parameter if you are using -bpmdbDesign.

Do not use this parameter if you are using -bpmdbDesign.

Do not use this parameter if you are using -bpmdbDesign.

Do not use this parameter if you are using -bpmdbDesign.

Do not use this parameter if you are using -bpmdbDesign.

Do not use this parameter if you are using -bpmdbDesign.

Do not use this parameter if you are using -bpmdbDesign.

Do not use this parameter if you are using -bpmdbDesign.

Do not use this parameter if you are using -bpmdbDesign.

Do not use this parameter if you are using -bpmdbDesign.

• DB2_DATASERVER for a DB2 Data Server database
• DB2UDBOS390 for a DB2 for z/OS database
• MSSQLSERVER_MICROSOFT for a Microsoft SQL Server database using Microsoft JDBC driver
• ORACLE for an Oracle database

Do not use this parameter if you are using -bpmdbDesign.

• A stand-alone profile when -bpmdbDesign was not specified.
• An advanced or ESB dmgr or managed profiles when -bpmdbDesign was not specified.

For DB2 databases, this parameter specifies the database user ID that will own the database tables. The default value is db2inst1. For DB2 for z/OS databases, it specifies the user ID that has privileges to create and drop the databases.

Important: The -dbUserId parameter value must be a valid database authorization ID. For more information about authorization IDs, see the Authorization IDs and authorization names section of the DB2 property restriction page.

Do not use this parameter if you are using -bpmdbDesign.

Do not use this parameter if you are using -bpmdbDesign.

Do not use this parameter when using the -startingPort or -portsFile parameter.

During profile creation, the manageprofiles command-line utility uses an automatically generated set of recommended ports if you do not specify the -startingPort parameter, the -defaultPorts parameter or the -portsFile parameter. The recommended port values can be different than the default port values based on the availability of the default ports.

Deleting a profile does not delete the profile directory. For example, if you create a profile in the /usr/WebSphere/ProcServer/profiles/managedProfile directory, the directory remains after you delete the profile.

You can delete or leave the directory. However, the profile_root/logs directory contains information about uninstalling the profile. For example, you might retain the _nodeuninst.log file to determine the cause of any problem during the uninstallation procedure.

If you delete a profile that has augmenting templates registered to it in the profile registry, then unaugment actions are performed automatically.

Deleting a profile does not delete the profile directory. For example, suppose that you create a profile in the /usr/WebSphere/ProcServer/profiles/managedProfile directory, the directory remains after you delete the profile.

You can delete or leave the directory. However, the profile_root/logs directory contains information about uninstalling the profile. For example, you might retain the _nodeuninst.log file to determine the cause of any problem during the uninstallation procedure.

If you delete a profile that has augmenting templates registered to it in the profile registry, then unaugment actions are performed automatically.

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

Specifying this optional parameter directs the manageprofiles command-line utility 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 stand-alone server profile.

If you federate a custom node when the deployment manager is not running, 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 installation root directory of the profile) before creating another custom profile with the same profile name.

If you change the default JMX connector type, you cannot federate with the manageprofiles command-line utility. Use the addNode command instead.

The default value for this parameter is localhost. The value for this parameter must be a properly formed host name and must not contain spaces or characters that are not valid such as the following characters: *, ?, ", <, >, , , /, \, and |. A connection to the deployment manager must also be available in conjunction with the dmgrPort parameter.

If you change the default JMX connector type, you cannot federate with the manageprofiles command-line utility. Use the addNode command instead.

The default value for this parameter is 8879. The port that you indicate must be a positive integer and a connection to the deployment manager must be available in conjunction with the dmgrHost parameter.

For IBM Business Process Manager omit this parameter. Administrative security is always enabled for IBM Business Process Manager profiles. You must also specify the parameters -adminUserName and -adminPassword along with the values for these parameters. Do not supply this parameter when augmenting an existing profile

When the manageprofiles command-line utility is run with the -enableService option set to true, the Linux service is created with the profile when the command is run by the root user. When a nonroot user runs the manageprofiles command-line utility, the profile is created, but the Linux service is not. The Linux service is not created because the nonroot user does not have sufficient permission to set up the service. An INSTCONPARTIALSUCCESS result is displayed at the end of the profile creation and the profile creation log install_root/logs/manageprofiles/profile_name_create.log contains a message indicating the current user does not have sufficient permission to set up the Linux service.

This parameter has no default value, and it must not be empty.

The environment type refers to how IBM Business Process Manager is used; for example, in a production, stage or test environment. Load testing might be done on a test server, while a stage environment type might be used as a temporary location to host changes before putting those changes into production. You might specify Stage as the Environment type if the server you are configuring will be accessed and used to review content and new functionality.

If the -dmgrHost, -dmgrPort, -dmgrAdminUserName, and -dmgrAdminPassword parameters are not set, the default value for this parameter is true.

You can use the -federateLaterBPM parameter when using the profileTemplates/managed.esbserver or theprofileTemplates/BPM/managed.templateName template.

If you use -federateLaterBPM, you must either omit the WebSphere Application Server-based parameter -federateLater or set it to true.

If the -dmgrHost, -dmgrPort, -dmgrAdminUserName, and -dmgrAdminPassword parameters are not set, the default value for this parameter is true.

You can use the -federateLaterWESB parameter when using the profileTemplates/managed.esbserver template.

If you use -federateLaterWESB, you must either omit the WebSphere Application Server-based parameter -federateLater or set it to true.

When you import a personal certificate as the default personal certificate, import the root certificate that signed the personal certificate. Otherwise, the manageprofiles utility adds the public key of the personal certificate to the trust.p12 file and creates a root signing certificate.

The -importPersonalCertKS parameter is mutually exclusive with the -personalCertDN parameter. If you do not specifically create or import a personal certificate, one is created by default.

If -isDeveloperServer is set when creating an IBM Business Process Manager profile, then a preconfigured VMM file repository is installed. This file repository contains a sample organization that can be used to test Business Process Choreographer people resolution, ready for you to use as is.

The default value for this parameter is based on the short host name, profile type, and a trailing number, for example:

if (DMgr)
	shortHostNameCellManagerNodeNumber
else
	shortHostNameNodeNodeNumber

where NodeNumber is a sequential number starting at 01.

The value for this parameter must not contain spaces or any characters that are not valid such as the following characters: *, ?, ", <, >, ,, /, \, and |, .

If you are using Oracle, the value specified for -perfDWDbName and -procSvrDbName can be the same.

If you are using any other supported database, the value specified for -perfDWDbName and -procSvrDbName must be different.

Do not use this parameter if you are using -bpmdbDesign.

Do not use this parameter when using the -startingPort or -defaultPorts parameter.

During profile creation, the manageprofiles command-line utility uses an automatically generated set of recommended ports if you do not specify the -startingPort parameter, the -defaultPorts parameter or the -portsFile parameter. The recommended port values can be different than the default port values based on the availability of the default ports.

If you are using Oracle, the value specified for -procSvrDbName and -perfDWDbName can be the same.

If you are using any other supported database, the value specified for -procSvrDbName and -perfDWDbName must be different.

Do not use this parameter if you are using -bpmdbDesign.

profileType ProfileNumber

The value for this parameter must not contain spaces or characters that are not valid such as the following characters: *, ?, ", <, >, ,, /, \, and |. The profile name that you choose must not be in use.

-profilePath profile_root

On Windows platforms: If the fully qualified path contains spaces, enclose the value in quotation marks.

The default value is based on the install_root directory, the profiles subdirectory, and the name of the file.

WS_WSPROFILE_DEFAULT_PROFILE_HOME/profileName

The value for this parameter must be a valid path for the target system and must not be currently in use.

You must have permissions to write to the directory.

create
profileName=testResponseFileCreate
profilePath=profile_root
templatePath=install_root/profileTemplates/default
nodeName=myNodeName
cellName=myCellName
hostName=myHostName
omitAction=myOptionalAction1, myOptionalAction2

On Windows platforms: The path statement in the Windows operating system can use either forward slashes (/) or back slashes (\). If the path statement uses back slashes, then the response file requires double back slashes for the response file to correctly understand the path. Here is an example of a response file for a create operation that uses the double back slashes:

create
templatePath=C:\\WebSphere\\ProcServer\\profileTemplates\\default

personalCertDN cn=machine_name.dnx_suffix.com\\,ou=machine_name
Node04Cell\\,ou=machine_nameNode04\\,o=IBM\\,c=US

To determine which input arguments are required for the various types of profile templates and action, use the manageprofiles command-line utility with the -help parameter.

manageprofiles(.bat)(.sh) -setDefaultName -profileName profile_name

Port values are assigned sequentially from the -startingPort value, omitting those ports that are already in use. The system recognizes and resolves ports that are currently in use and determines the port assignments to avoid port conflicts.

Do not use this parameter with the -defaultPorts or -portsFile parameters.

During profile creation, the manageprofiles command-line utility uses an automatically generated set of recommended ports if you do not specify the -startingPort parameter, the -defaultPorts parameter or the -portsFile parameter. The recommended port values can be different than the default port values based on the availability of the default ports.

Use absolute paths. This parameter must exist as a directory and point to a valid template directory.

default.procctr

For Process Center stand-alone profiles that define stand-alone servers for BPM Standard and Express configurations.

default.procctr.adv

For Process Center stand-alone profiles that define stand-alone servers for BPM Advanced configurations.

default.procsvr

For Process Server stand-alone profiles that define stand-alone servers for BPM Standard and Express configurations.

default.procsvr.adv

For Process Server stand-alone profiles that define stand-alone servers for BPM Advanced configurations.

default.esbserver

For WebSphere Enterprise Service Bus stand-alone server profiles that define stand-alone servers.

dmgr.procctr

For a Process Center deployment manager profile that defines a deployment manager for BPM Standard configurations. A deployment manager provides one administrative interface to a logical group of servers on one or more workstations.

dmgr.procctr.adv

For a Process Center deployment manager profile that defines a deployment manager for BPM Advanced configurations.

dmgr.procsvr

For a Process Server deployment manager profile that defines a deployment manager for BPM Standard configurations.

dmgr.procsvr.adv

For a Process Server deployment manager profile that defines a deployment manager for BPM Advanced configurations.

dmgr.esbserver

For a WebSphere Enterprise Service Bus deployment manager profile that defines a deployment manager.

managed.procctr

For a Process Center custom profile that, when federated to a deployment manager, defines a managed node for BPM Standard configurations. If you have decided that your solution requires a deployment environment, your runtime environment requires one or more managed nodes. A custom profile contains an empty node that you must federate into a deployment manager cell to make operational. Federating the custom profile changes it into a managed node. Do not federate a node unless the deployment manager you are federating to is at a release level the same or higher than that of the custom profile you are creating.

managed.procctr.adv

For a Process Center custom profile that, when federated to a deployment manager, defines a managed node for BPM Advanced configurations.

managed.procsvr

For a Process Server custom profile that, when federated to a deployment manager, defines a managed node for BPM Standard configurations. If you have decided that your solution requires a network deployment configuration, your runtime environment requires one or more managed nodes. A custom profile contains an empty node that you must federate into a deployment manager cell to make operational. Federating the custom profile changes it into a managed node. Do not federate a node unless the deployment manager you are federating to is at a release level the same or higher than that of the custom profile you are creating.

managed.procsvr.adv

For a Process Server custom profile that, when federated to a deployment manager, defines a managed node for BPM Advanced configurations. IBM Business Process Manager Advanced: Process Server profiles cannot use a WebSphere Enterprise Service Bus deployment manager, but WebSphere Enterprise Service Bus profiles can use a IBM Business Process Manager Advanced: Process Server deployment manager.

managed.esbserver

For a WebSphere Enterprise Service Bus custom profile that, when federated to a deployment manager, defines a managed node. Do not federate a node unless the deployment manager you are federating to is at a release level the same or higher than that of the custom profile you are creating. WebSphere Enterprise Service Bus profiles can use an Enterprise Service Bus or IBM Business Process Manager Process Server deployment manager.

When using the -templatePath parameter, specify the fully qualified file path for the parameter. Optionally, specify the -unaugmentDependents parameter with the -unaugmentAll parameter to unaugment all profiles that are prerequisites of the profiles that are being unaugmented.

Optionally, specify the -unaugmentDependents parameter with the -unaugmentAll parameter.

Valid values include specifieduser or localsystem. The localsystem value runs the Windows service under the local account of the user who creates the profile. The default value for this parameter is localsystem.

• manual
• automatic
• disabled

The default value for this parameter is manual.

• Act as part of the operating system
• Log on as a service