Cell profiles are created using two different manageprofiles command-line invocations.
To create the cell profile using the manageprofiles command, you must create both the cell deployment manager profile and the cell node profile 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: cell_dmgr and cell_node. 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. After you create the cell, the cell contains a deployment manager and a federated node.
app_server_root/bin/manageprofiles.sh -create -templatePath app_server_root/profileTemplates/cell/dmgr -help
app_server_root\bin\manageprofiles.bat -create -templatePath app_server_root\profileTemplates\cell\dmgr -help
app_server_root/bin/manageprofiles -create -templatePath app_server_root/profileTemplates/cell/dmgr -helpor
app_server_root/bin/manageprofiles.sh -create -templatePath app_server_root/profileTemplates/cell/default -help
app_server_root\bin\manageprofiles.bat -create -templatePath app_server_root\profileTemplates\cell\default -help
app_server_root/bin/manageprofiles -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 path must be available when you create the deployment manager and node portions of the cell as subdirectories are added for each portion.
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 federated_node_name
app_server_root\bin\manageprofiles.bat -create -templatePath app_server_root\profileTemplates\cell\dmgr -nodeProfilePath app_server_root\profiles\AppSrv01 -profileName Dmgr001 -cellName Default01Cell -nodeName Default01Node -appServerNodeName federated_node_name
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 federated_node_name
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 federated_node_name
app_server_root\bin\manageprofiles.bat -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
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 federated_node_name
After the creation of the deployment manager and node portions of the cell profile, a synchronization between the two servers must occur. By default, synchronization occurs automatically between the two servers at some specified interval. However, if synchronization is disabled, the interval is too long, or some problem occurs that keeps the synchronization from occurring in a timely manner, run the syncNode command to synchronize the deployment manager and the node.
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 that you want to be the default.
If you federate an application server node as part of cell
profile creation using the -appServerNodeName parameter, the node does not
have an original configuration. If you use the -removeNode command
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.