WebSphere Application Server Network Deployment, Version 6.1
             Operating Systems: AIX, HP-UX, i5/OS, Linux, Solaris, Windows

             Personalize the table of contents and search results

Example: Creating a cell profile with the manageprofiles command

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.

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 -nodeProfilePath, -cellName, -appServerNodeName, -nodeName 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 -portsFile and -nodePortsFile arguments with references to the following 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 at the following location:
For detailed help in creating a cell profile, use [Linux] [HP-UX] [Solaris] [AIX]
app_server_root/bin/manageprofiles.sh -create         
      -templatePath
app_server_root/profileTemplates/cell/dmgr  	
      -help 
[Windows]
app_server_root\bin\manageprofiles.bat -create         
      -templatePath
app_server_root\profileTemplates\cell\dmgr  	
      -help 
[i5/OS]
app_server_root/bin/manageprofiles -create         
      -templatePath
app_server_root/profileTemplates/cell/dmgr  
      -help 
or [Linux] [HP-UX] [Solaris] [AIX]
app_server_root/bin/manageprofiles.sh -create         
      -templatePath
app_server_root/profileTemplates/cell/default 	
      -help 
[Windows]
app_server_root\bin\manageprofiles.bat -create         
      -templatePath 
app_server_root\profileTemplates\cell\default 	
      -help 
[i5/OS]
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 following example creates a cell profile named Dmgr001 having a cell name of Default01Cell and a node name of Default01Node.
  1. Verify that the following path is available for use:

    The path must be available when you create the deployment manager and node portions of the cell as subdirectories are added for each portion.

  2. Create the deployment manager portion of the cell profile.[Linux] [HP-UX] [Solaris] [AIX]
    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
    [Windows]
    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
    [i5/OS]
    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
  3. Verify that the Dmgr001 profile exists as it must exist before you create the application server portion of the cell profile.
  4. Create the application server portion of the cell profile.
    Note: 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, you must use the default name that was assigned in the first command-line invocation.
    [Linux] [HP-UX] [Solaris] [AIX]
    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
    [Windows]
    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
    [i5/OS]
    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.

[AIX HP-UX Linux Solaris Windows] 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.




Related tasks
Using command line tools
[AIX HP-UX Linux Solaris Windows] Creating a cell profile
Related reference
manageprofiles command
removeNode command
Reference topic    

Terms of Use | Feedback

Last updated: Feb 25, 2009 9:32:38 AM CST
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websphere.nd.multiplatform.doc/info/ae/ae/rxml_celltemplates.html