manageprofiles command

manageprofiles command

+
Search Tips | Advanced Search

The manageprofiles command line tool creates profiles, which are sets of files that define the run-time environment for...

deployment manager
custom profile
stand-alone appservers

The manageprofiles command creates the run-time environment for a WAS process in a set of files called a profile. The profile defines the run-time environment and includes all of the files that the server processes in the run-time environment can change.
The manageprofiles command and its graphical user interface, the Profile Management tool, are the only ways to create run-time environments.
The command file is located in...
app_server_root/bin

The command file is a script named manageprofiles.
The manageprofiles command creates a log for every profile that it creates...
app_server_root/logs/manageprofiles/profilename_create.log

The command also creates a log for every profile that it deletes. The logs are in...
app_server_root/logs/manageprofiles/profilename_delete.log

If you use this command with the managed profile template, appservers are not created. However, ports are still used if you are federating a node.

Syntax
The manageprofiles command is used to perform the following:

create a profile -create
delete a profile -delete
augment a profile -augment
unaugment a profile -unaugment
delete all profiles -deleteAll
list all profiles -listProfiles
get a profile name -getName
get a profile path -getPath
validate a profile registry -validateRegistry
validate and update a profile registry -validateAndUpdateRegistry
get the default profile name -getDefaultName
set the default profile name -setDefaultName
backup a profile -backupProfile
restore a profile -restoreProfile

For detailed help including the required parameters for each of the tasks accomplished with the manageprofiles command, use the -help parameter. The following is an example of using the help parameter with the manageprofiles -augment command on Windows operating systems:
app_server_root\bin\manageprofiles.bat -augment -help

The output from the help command will specify which parameters are required and which are optional.
Depending on the operation to perform with the manageprofiles command, you will need to provide one or more of the following parameters. The command line profile management tool validates that the required parameters are provided and the values entered for those parameters are valid. Be sure to type the name of the parameters with the correct upper and lower case as the command line profile management tool does not validate the case of the parameter name. Incorrect results can occur when the parameter case is not typed correctly.

-profileName profile_name
-profilePath profile_root
-templatePath template_path
-nodeName node_name
-cellName cell_name
-hostName host_name
-adminUserName adminUser_ID
-adminPassword adminPassword
-backupFile backupFile_name
-dmgrProfilePath dmgr_profile_path
-dmgrHost dmgr_host_name
-dmgrPort dmgr_port_number
-debug
-enableAdminSecurity true | false
-federateLater true | false
-isDefault
-isDeveloperServer
-omitAction feature1 feature2... featureN
-response reponse_file
-samplesPassword samplesPassword
-startingPort starting_port | -portsFile file_path | -defaultPorts
-validatePorts
-webServerCheck true | false
-webServerHostnamewebserver_host_name
-webServerInstallPath webserver_installpath_name
-webServerName webserver_name
-webServerOS webserver_operating_system
-webServerPluginPath webserver_plugin_path
-webServerPort webserver_port
-webServerType webserver_type
-enableService true | false
-serviceUserName service_user_ID

-winserviceCheck true | false

-winserviceAccountType specifieduser | localsystem

-winservicePassword winservice_password

-winserviceStartupType manual | automatic | disabled

-winserviceUserName winservice_user_ID

The following is an example of using the manageprofiles -create command on operating systems such as AIX or Linux:
app_server_root/bin/manageprofiles.sh -create 
              -profileName profile_name 
              -profilePath profile_root                
              -templatePath template_path 
Parameters

The following options are available for the manageprofiles command:
-adminUserName adminUser_ID

Specify the user ID that is used for administrative security.

-adminPassword adminPassword

Specify the password for the administrative security user ID specified with the -adminUserName parameter.

-augment

Make changes to an existing profile with an augmentation template. Causes manageprofiles to update or augment the profile identified in the -profileName parameter using the template in the -templatePath parameter. The augmentation templates used to are determined by which IBM products and versions are installed in your environment.
The templates that are included with WAS should only be used to create profiles and not to augment existing profiles. Also, do not manually modify the files that are located in...
install_dir/profileTemplates

For example, if you are changing the ports during profile creation, use the Profile Creation Wizard or the -startingPort or -portsFile arguments to the manageprofiles command instead of modifying the file in the profile template
Specify the fully qualified file path for -templatePath. For example:
manageprofiles.bat(sh) -augment -profileName profile -templatePath fully_qualified_template_path

Specifying a relative file path for the -templatePath parameter results in the specified profile not being fully augmented.
See also the -unaugment parameter.

-backupProfile

Performs a file system back up of a profile folder and the profile metadata from the profile registry file. Any servers using the profile to back up must first be stopped prior to invoking the manageprofiles command with the -backupProfile option. The -backupProfile parameter must be used with the -backupFile and -profileName parameters, for example:
manageprofiles.bat(sh) -backupProfile -profileName profile -backupFile backupFile_name

When you back up a profile using the -backupProfile option, first stop the server and the running processes for the profile that you want to back up.

-backupFile backupFile_name

Backs up the profile registry file to the specified file. You must provide a fully qualified file path for the backupFile_name.

-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 or stand alone 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 exception, in which case, create uniquely named cells. The default value for this parameter is based on a combination of the short host name, the constant cell, and a trailing number...
 if (DMgr)
    shortHostNameCellCellNumber else
    shortHostNameNodeNodeNumberCell
where CellNumber is a sequential number starting at 01 and NodeNumber is the node number that you used to define the node name.
The value for this parameter must not contain spaces or any characters that are not valid such as the following: *, ?, ", <, >, ,, /, \, |, and so on.
-create

Creates the profile.
Specify...
manageprofiles -create -templatePath /path/to/template -help

...for specific information about creating a profile. Available templates include:

cell Deployment manager cell (dmgr and default)
dmgr Deployment manager
default Application server
managed Custom

-debug

Turns on the debug function of the Ant utility, which the manageprofiles command uses.

-defaultPorts

Assigns the default or base port values to the profile.
Do not use this parameter when using the -startingPort or -portsFile parameter.
During profile creation, the manageprofiles command uses an automatically generated set of recommended ports if you do not specify any of the following parameters...

-startingPort
-defaultPorts
-portsFile

The recommended port values can be different than the default port values based on the availability of the default ports.
Do not use this parameter if you are using the managed profile template.

-delete

Deletes the profile. Deleting a profile does not delete the profile
For example, suppose that you create a profile in...
/usr/WebSphere/AppServer/profiles/managedProfile

The directory remains after you delete the profile.
You can delete or leave the directory. However,...
profile_root/logs

...contains information about uninstalling the profile. For example, you might retain the _nodeuninst.log file to determine the cause of any problem during the uninstall procedure.
If you delete a profile that has augmenting templates registered to it in the profile registry, then unaugment actions are performed automatically.

-deleteAll

Deletes all registered profiles. Deleting a profile does not delete the profile directory. For example, suppose that you create a profile in...
/usr/WebSphere/AppServer/profiles/managedProfile

The directory remains after you delete the profile.
You can delete or leave the directory. However,...
profile_root/logs

...contains information about uninstalling the profile. For example, you might retain the _nodeuninst.log file to determine the cause of any problem during the uninstall procedure.
If you delete a profile that has augmenting templates registered to it in the profile registry, then unaugment actions are performed automatically.

-dmgrHost dmgr_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 an Application Server profile.
If you federate a custom node when the deployment manager is not running or is not available because of security being enabled or for other reasons, the installation indicator in the logs is INSTCONFFAIL to indicate a complete failure. The resulting custom profile is unusable. You must move...
custom profile

...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.
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: *, ?, ", <, >, ,, /, \, |, and so on. A connection to the deployment manager must also be available in conjunction with the dmgrPort parameter.

-dmgrPort dmgr_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 manageprofiles command. 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.

-dmgrProfilePath dmgr_profile_path

Profile path to the deployment manager portion of the cell. Specify this parameter when you create the appserver portion of the cell.

-enableAdminSecurity true | false

Enables administrative security. Valid values include true or false. The default value is false.

When enableAdminSecurity is set to true, also specify the parameters -adminUserName and -adminPassword along with the values for these parameters. If samples were installed during the appserver install, also specify the -samplesPassword parameter when creating a profile for which administrative security is enabled. If the -samplesPassword parameter is not specified when administrative security is enabled, the profile is created successfully, but when you attempt to run the samples, exceptions and failures will be put in the server system out log.

-enableService true | false

Enables the creation of a Linux service. Valid values include true or false. The default value for this parameter is false.
When the manageprofiles command 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 non-root user runs the manageprofiles command, the profile is created, but the Linux service is not. The Linux service is not created because the non-root 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 app_server_root/logs/manageprofiles_create_profilename.log contains a message indicating the current user does not have sufficient permission to set up the Linux service.

-federateLater true | false

Indicates if the managed profile will be federated during profile creation or if you will federate it later using the addNode command. If the dmgrHost, dmgrPort, dmgrAdminUserName and dmgrAdminPassword parameters have values, the default value for this parameter is true. Valid values include true or false.

-getDefaultName

Returns the name of the default profile.

-getName

Gets the name for a profile registered at a given -profilePath parameter.

-getPath

Gets the file system location for a profile of a given name. Requires the –profileName parameter.

-help

Displays command syntax.

-hostName host_name

Specifies the host name where you are creating the profile. This should match the host name specified during installation of the initial product. The default value for this parameter is the long form of the domain name system. The value for this parameter must be a valid IPv6 host name and must not contain spaces or any characters that are not valid such as the following: *, ?, ", <, >, ,, /, \, |, and so on.

-isDefault

Specifies that the profile identified by the accompanying -profileName parameter is to be the default profile once it is registered. When issuing commands that address the default profile, it is not necessary to use the -profileName attribute of the command.

-isDeveloperServer

Specifies whether the server is intended for development purposes only. This parameter is useful when creating profiles to test applications on a non-production server prior to deploying the applications on their production appservers.

-listProfiles

Lists all defined profiles.

-nodeDefaultPorts

Defines a set of ports when creating a profile in conjunction with a cell template. If you specify this option, you cannot specify the -nodePortsFile or nodeStartingPort options at the same time.

-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. The default value for this parameter is based on the short host name, profile type, and a trailing number...
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: *, ?, ", <, >, ,, /, \, |, and so on.
-omitAction feature1 feature2... featureN

An optional parameter that excludes profile features. Each profile template comes predefined with certain optional features. The samplesInstallAndConfig option is only available when WAS is installed with samples applications selected. The following optional features can be used with the -omitAction parameter for the following profile templates:

default - Application server

deployAdminConsole
samplesInstallAndConfig
defaultAppDeployAndConfig

dmgr - Deployment manager

deployAdminConsole

cell - Deployment manager cell which is composed of both a dmgr and a default profile template

cell_dmgr (dmgr created during cell profile creation)

deployAdminConsole
samplesInstallAndConfig
defaultAppDeployAndConfig

-portsFile file_path

An optional parameter that specifies the path to a file that defines port settings for the new profile.
Do not use this parameter when using the -startingPort or -defaultPorts parameter.
During profile creation, the manageprofiles command 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.

-profileName profile_name

Name of the profile. Use a unique value when creating a profile. Each profile that shares the same set of product binaries must have a unique name. The default profile name is based on the profile type and a trailing number...
profileTypeProfileNumber
where profileType is a value such as...

AppSrv
Dmgr
Custom

...and ProfileNumber is a sequential number that creates a unique profile name. For example, profile01
The value for this parameter must not contain spaces or characters that are not valid such as the following: *, ?, ", <, >, ,, /, \, |, and so on. The profile name that you choose must not be in use.

-profilePath profile_root

Fully qualified path to the profile, which is referred to throughout the information center as the profile_root. 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 profile_root

If the fully qualified path contains spaces, enclose the value in quotation marks. The default value is based on the location of the WAS installation, the profiles subdirectory, and the name of the file...
WAS_HOME/profiles/profileName

where WAS_HOME is defined in the manageprofile.properties file.
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.

-response reponse_file
Accesses all API functions from the command line using the manageprofiles command.The command line interface can be driven by a response file that contains the input arguments for a given command in the properties file in key and value format. The following is an example response file for a create operation:
create profileName=testResponseFileCreate profilePath=profile_root templatePath=app_server_root/profileTemplates/default nodeName=myNodeName cellName=myCellName hostName=myHostName omitAction=myOptionalAction1, myOptionalAction2
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\\AppServer\\profileTemplates\\default
To determine which input arguments are required for the various types of profile templates and action, use the manageprofiles command with the -help parameter.
-restoreProfile
Restores a profile backup. Must be used with the -backupFile parameter, for example:
manageprofiles.bat(sh) -restoreProfile -backupFile file_name
To restore a profile, perform the following steps:

Manually delete the directory for the profile from file system.

Run the -validateAndUpdateRegistry option of the manageprofiles command.

Stop the server and the running processes for the profile to restore.

Restore the profile by using the -restoreProfile option of the manageprofiles command.
-samplesPassword samplesPassword

Creates a password to be used for samples. The password is used to restrict access to web application samples installed during the install of the appserver.

-serviceUserName service_user_ID

User ID that is used during the creation of the Linux service so that the Linux service will run under this user ID. The Linux service runs whenever the user ID is logged on.

-setDefaultName
Sets the default profile to one of the existing profiles. Must be used with the -profileName parameter...
manageprofiles.bat(sh) -setDefaultName -profileName profile
-startingPort startingPort

Starting port number for generating and assigning all ports for the profile.
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 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.
Do not use this parameter if you are using the managed profile template.

-templatePath template_path

Specifies the directory path to the template files in the installation root directory. Within the profileTemplates directory are various directories that correspond to different profile types and that vary with the type of product installed. The profile directories are the paths that you indicate while using the -templatePath option. You can specify profile templates that lie outside the installation root, if you happen to have any.
Use absolute paths. This parameter must exist as a directory and point to a valid template directory.

-unaugment

Augmentation is the ability to change an existing profile with an augmentation template. When you unaugment an existing profile that has been augmented, the changes are backed out according to the previously specified profile template. If a series of manageprofiles augmentations were performed, then the unaugment action will undo the last augment action first.
When the unaugment action is invoked, the manageprofiles command attempts to access the deleteRegistry.xml file in the template path that was specified in the augment command. The operations defined in the Config Actions stanza in the delete registry file are then applied against the specified profile.
Specify the fully qualified file path for -templatePath.
See also the augment parameter.

-validateAndUpdateRegistry

Checks all of the profiles that are listed in the profile registry to see if the profiles are present on the file system. Removes any missing profiles from the registry. Returns a list of the missing profiles that were deleted from the registry.

-validateRegistry

Checks all of the profiles that are listed in the profile registry to see if the profiles are present on the file system. Returns a list of missing profiles.

-validatePorts

Ports should be validated to ensure they are not reserved or in use. This parameter helps you to identify ports that are not being used. If a port is determined to be in use, the profile creation stops and an error message displays. You can use this parameter at any time on the create command line. IBM recommends to use this parameter with the –portsFile parameter.

-webServerCheck true | false

Indicates if you want to set up Web server definitions. Valid values include true or false. The default value for this parameter is false.

-webServerHostname webserver_host_name

The host name of the server. The default value for this parameter is the long host name of the local machine.

-webServerInstallPath webserver_installpath_name
The installation path of the Web server, local or remote. The default value for this parameter is dependent on the operating system of the local machine and the value of the webServerType parameter. For example:
webServerType=IHS: webServerInstallPath defaulted to “C:\Program Files\IBM\HTTPServer” webServerType=IIS: webServerInstallPath defaulted to “C:\” webServerType=SUNJAVASYSTEM: webServerInstallPath defaulted to “C:\” webServerType=DOMINO: webServerInstallPath defaulted to “” webServerType=APACHE: webServerInstallPath defaulted to “” webServerType=HTTPSERVER_ZOS: webServerInstallPath defaulted to “n/a”
webServerType=IHS: webServerInstallPath defaulted to “/opt/IBM/HTTPServer” webServerType=IIS: webServerInstallPath defaulted to “n\a” webServerType=SUNJAVASYSTEM: webServerInstallPath defaulted to “/opt/sun/webserver” webServerType=DOMINO: webServerInstallPath defaulted to “” webServerType=APACHE: webServerInstallPath defaulted to “” webServerType=HTTPSERVER_ZOS: webServerInstallPath defaulted to “n/a”
webServerType=IHS: webServerInstallPath defaulted to “/usr/IBM/HTTPServer” webServerType=IIS: webServerInstallPath defaulted to “n\a” webServerType=SUNJAVASYSTEM: webServerInstallPath defaulted to “/opt/sun/webserver” webServerType=DOMINO: webServerInstallPath defaulted to “?” webServerType=APACHE: webServerInstallPath defaulted to “?” webServerType=HTTPSERVER_ZOS: webServerInstallPath defaulted to “n/a”
webServerType=IHS: webServerInstallPath defaulted to “/opt/IBM/HTTPServer” webServerType=IIS: webServerInstallPath defaulted to “n\a” webServerType=SUNJAVASYSTEM: webServerInstallPath defaulted to “/opt/sun/webserver” webServerType=DOMINO: webServerInstallPath defaulted to “” webServerType=APACHE: webServerInstallPath defaulted to “” webServerType=HTTPSERVER_ZOS: webServerInstallPath defaulted to “n/a”
webServerType=IHS: webServerInstallPath defaulted to “/opt/IBM/HTTPServer” webServerType=IIS: webServerInstallPath defaulted to “n\a” webServerType=SUNJAVASYSTEM: webServerInstallPath defaulted to “/opt/sun/webserver” webServerType=DOMINO: webServerInstallPath defaulted to “” webServerType=APACHE: webServerInstallPath defaulted to “” webServerType=HTTPSERVER_ZOS: webServerInstallPath defaulted to “n/a”
-webServerName webserver_name

The name of the Web server. The default value for this parameter is webserver1.

-webServerOS webserver_operating_system

The operating system from where the Web server resides. Valid values include: windows, linux, solaris, aix, hpux, os390, and os400. Use this parameter with the webServerType parameter.

-webServerPluginPath webserver_pluginpath

The path to the plug-ins that the Web server uses. The default value for this parameter is WAS_HOME/plugins.

-webServerPort webserver_port

Indicates the port from where the Web server will be accessed. The default value for this parameter is 80.

-webServerType webserver_type

The type of the Web server. Valid values include: IHS, SUNJAVASYSTEM, IIS, DOMINO, APACHE, and HTTPSERVER_ZOS. Use this parameter with the webServerOS parameter.

-winserviceAccountType specifieduser | localsystem

The type of the owner account of the Windows service created for the profile. 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 system.

-winserviceCheck true | false

The value can be either true or false. Specify true to create a Windows service for the server process that is created within the profile. Specify false to not create the Windows service. The default value for this parameter is false.

-winservicePassword winservice_password

Password for the specified user or the local account that is to own the Windows service.

-winserviceStartupType manual | automatic | disabled

Possible startup_type values are:

manual

automatic

disabled

See WASService command for more information about Windows services.
The default value for this parameter is automatic.

-winserviceUserName winservice_user_ID

Specify your user ID so that the Windows operating system can verify you as an ID that is capable of creating a Windows service. Your user ID must belong to the administrator group and have the following advanced user rights:

Act as part of the operating system

Log on as a service

The default value for this parameter is the current user name. The value for this parameter must not contain spaces or characters that are not valid such as the following:
* ? " < > , / \ |
The user specified must have the proper permissions to create a windows service. You must specify the correct password for the user name that you choose.
Usage scenario

The following examples demonstrate correct syntax. Issue the command in any of the following examples on one line. Each example shows the command on more than one line to increase clarity.
Creating a deployment manager profile The following example uses the dmgr template to create a deployment manager profile named Dmgr001. The deployment manager ports start at port 20000.
app_server_root/bin/manageprofiles.sh -create 
   -profileName Dmgr001
   -profilePath profile_root    
   -templatePath app_server_root/profileTemplates/dmgr
   -nodeName Dmgr001Node
   -cellName Dmgr001NodeCell
   -hostName localhost
   -isDefault
   -startingPort 20000
app_server_root\bin\manageprofiles.bat -create 
   -profileName Dmgr001
   -profilePath profile_root    
   -templatePath app_server_root\profileTemplates\dmgr
   -nodeName Dmgr001Node
   -cellName Dmgr001NodeCell
   -hostName localhost
   -isDefault
   -startingPort 20000
Creating a custom profile

Federate a custom profile to customize the profile with the deployment manager.
Create a custom profile for federating into a deployment manager cell with the following command:
c:\WebSphere\AppServer\bin manageprofiles -create
                -profileName Custom01
                -profilePath profile_root                 
                -templatePath app_server_root\profileTemplates\managed
                -nodeName CustomNode01
                -cellName CustomNodeCell01
                -hostName myhost.mycity.mycompany.com
                -isDefault 
                -dmgrHost myhost.mycity.mycompany.com
                -dmgrPort 8879
                -startingPort 22000
app_server_root/bin/manageprofiles.sh -create 
   -profileName Custom01
   -profilePath profile_root    
   -templatePath app_server_root/profileTemplates/managed
   -nodeName Custom01Node
   -cellName Custom01Cell
   -hostName myhost.mycity.mycompany.com
   -isDefault
   -startingPort 22000
Creating an appserver profile

Create an appserver profile named Default01 with the following command:
app_server_root\bin manageprofiles -create 
                -profileName Default01 
                -profilePath profile_root                 
                -templatePath app_server_root\profileTemplates\default 
                -nodeName Default01Node
                -cellName Default01Cell
                -hostName myhost.mycity.mycompany.com
                -isDefault 
                -winserviceCheck true
                -winserviceAccountType specifieduser
                -winserviceUserName my_user_id
                -winservicePassword my_password
                -winserviceStartupType manual
                -startingPort 21000
app_server_root/bin/manageprofiles.sh -create 
   -profileName Default01
   -profilePath profile_root    
   -templatePath app_server_root/profileTemplates/default
   -nodeName Default01Node
   -cellName Default01Cell
   -hostName myhost.mycity.mycompany.com
   -isDefault
   -startingPort 21000
Create a cell profile

Creating a cell profile requires the creation of both the deployment manager and the appserver portion of the cell profile. The two profiles are linked and some parameters must match between the creation parameters of the deployment manager and the appserver portion of the cell profile. For more detailed information regarding creating a cell profile, see Example: Creating a cell profile with the manageprofiles command.
The following example shows the creation of a cell profile named Dmgr001 having a cell name of Default01Cell and a node name of Default01Node. To create a full working cell, the -nodeProfilePath, -cellName, -appServerNodeName, -nodeName parameters are required to match between the cell_dmgr profile and the cell_node profile.
Create the deployment manager portion of the cell profile.
app_server_root\bin\manageprofiles -create
        -templatePath app_server_root\profileTemplates\cell\dmgr
        -nodeProfilePath app_server_root\profiles\AppSrv01
        -profileName Dmgr001
        -cellName Default01Cell
        -nodeName Default01Node
        -appServerNodeName Default01Node
app_server_root/bin/manageprofiles.sh -create 
        -templatePath app_server_root/profileTemplates/cell/dmgr
        -nodeProfilePath app_server_root/profiles/AppSrv01
        -profileName Dmgr001
        -cellName Default01Cell
        -nodeName Default01Node
        -appServerNodeName Default01Node
Create the appserver portion of the cell profile.
app_server_root\bin\manageprofiles -create
        -templatePath app_server_root\profileTemplates\cell\default
        -dmgrProfilePath app_server_root\profiles\Dmgr001
        -portsFile app_server_root\profiles\Dmgr001\properties\portdef.props
        -nodePortsFile app_server_root\profiles\Dmgr001\properties\nodeportdef.props
        -profileName AppSrv01
        -cellName Default01Cell
        -nodeName Default01Node
        -appServerNodeName Default01Node
app_server_root/bin/manageprofiles.sh -create
        -templatePath app_server_root/profileTemplates/cell/default
        -dmgrProfilePath app_server_root/profiles/Dmgr001
        -portsFile app_server_root/profiles/Dmgr001/properties/portdef.props
        -nodePortsFile app_server_root/profiles/Dmgr001/properties/nodeportdef.props
        -profileName AppSrv01
        -cellName Default01Cell
        -nodeName Default01Node
        -appServerNodeName Default01Node
Sub-topics
Example: Create a deployment manager profile
Example: Create a deployment manager profile in a multiuser environment
Example: Create a cell profile with the manageprofiles command
Example: Delete profiles
Example: Use predefined port numbers
Example: Increment default port numbers from a starting point

Related tasks
Create and delete profiles
Set up the profile environment through commands
Create customized CIP profiles

Related information
Use command line tools

create a profile	-create
delete a profile	-delete
augment a profile	-augment
unaugment a profile	-unaugment
delete all profiles	-deleteAll
list all profiles	-listProfiles
get a profile name	-getName
get a profile path	-getPath
validate a profile registry	-validateRegistry
validate and update a profile registry	-validateAndUpdateRegistry
get the default profile name	-getDefaultName
set the default profile name	-setDefaultName
backup a profile	-backupProfile
restore a profile	-restoreProfile

cell	Deployment manager cell (dmgr and default)
dmgr	Deployment manager
default	Application server
managed	Custom