Example: Create a cell profile with the manageprofiles command

 

+

Search Tips   |   Advanced Search

 

Cell profiles are created using two different manageprofiles command-line invocations.

To create the cell profile using the manageprofiles command, create both...

...using two different manageprofiles command-line invocations. The combination of these two profiles is the cell profile.

Two templates are used to create the cell profile...

The templates are linked and some parameters must match between the creation parameters in these two invocations. Verify that the invocations match.

From the command line, you can create the two halves of the cell in any order or at any time. It is a best practice to create the deployment manager portion of the profile first. On a distributed system, the cell_dmgr profile and the cell_node profile are created with a app_server_root path unless the -profilePath parameter is specified when the cell_dmgr profile and the cell_node profile are created. The deployment manager portion and the node portion are in separate directories.

The two templates that compose a cell profile have dependencies between one another which requires some parameter values to match between the two create invocations. To create a full working cell, the parameters...

...are required to have the same values for both the cell_dmgr profile and the cell_node profile.

In the case of ports, and especially in the case of dynamically allocated ports, the creation of the second half of the cell must reference the ports that are used in the first half of the cell. Use the arguments...

...with references to the files...

...of the profile that represents the first half of the cell. This approach ensures that the ports in the second half of the cell are created with the correct correlation to the first half of the cell. Additional information regarding the required and default values for both cell_dmgr and cell_node is located at...

app_server_root\profiles\profile_name/logs/AboutThisProfile.txt

For detailed help in creating a cell profile, use 

    manageprofiles.[bat|sh] -create 
                            -templatePath app_server_root\profileTemplates\cell\dmgr
                            -help

...or... 

    manageprofiles.[bat|sh] -create
                            -templatePath app_server_root\profileTemplates\cell\default
                            -help

The output from the -help parameter specifies which parameters are required and which are optional when creating the cell deployment manager profile and the cell node profile.

The following example creates a cell profile named Dmgr001 having a cell name of Default01Cell and a node name of Default01Node.

  1. Create the deployment manager portion of the cell profile. 

        manageprofiles.bat(sh) -create
                           -templatePath app_server_root\profileTemplates\cell\dmgr
                           -nodeProfilePath app_server_root\profiles\AppSrv01
                           -profileName Dmgr001
                           -cellName Default01Cell
                           -nodeName Default01Node
                           -appServerNodeName federated_node_name

  2. Create the appserver portion of the cell profile.

    You must use the same values for the cellName, nodeName, and appServerNodeName parameters that you used in the deployment manager portion of the cell profile. If you did not specify names for these parameters when you created the deployment manager portion of the cell profile, use the default name that was assigned in the first command-line invocation. 

        manageprofiles.bat(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 federated_node_name

You must either use the portsFile or the nodePortsFile parameter and the startingPort or the nodeStartingPort parameter.

If you use the manageprofiles command, you can choose the profile to be the default.

If you federate an appserver node as part of cell profile creation using the parameter...

-appServerNodeName

...the node does not have an original configuration.

If you use the command...

-removeNode

...on a node that was created during cell profile creation, the command will indicate that the node removal utility is unable to remove the node and restore the node to a base configuration.

To successfully remove a node that was federated as part of a cell profile creation, use the manageprofiles command to delete the profile for the node. Once the profile for the node is deleted, use the -cleanupNode command on Deployment Manager to remove the node configuration from the cell repository. A new profile can be created using the Profile Management Tool or the manageprofiles command.

 

Related tasks

Use command line tools
Creating a cell profile

 

Related Reference

manageprofiles command removeNode command