Create a cell profile


 

+

Search Tips   |   Advanced Search

 

Overview

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:

From the command line, we 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. After you create the cell, the cell contains a dmgr and a federated node. The deployment manager portion and the node portion are in separate directories.

For each of the two profiles that you create, we can specify the fully qualified path to the resulting profile using the parameter -profilePath. If we do not specify the parameter, the default value for each profile path is based on the $WAS_HOME directory, the profiles subdirectory, and the name of the profile.

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 following 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 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.

Create a cell profile

The following example creates a cell profile named Dmgr001 having a cell name of BldSrvCell and a node name of BldSrvNode.

  1. Verify that the following path exists...

      $WAS_HOME/profiles

  2. Create the dmgr portion of the cell profile.

     cd $WAS_HOME/bin/
    
    ./manageprofiles.sh -create 
                        -templatePath $WAS_HOME/profileTemplates/cell/dmgr 
                        -nodeProfilePath $WAS_HOME/profiles/BldSrv 
                        -profileName Dmgr001 
                        -cellName BldSrvCell 
                        -nodeName BldSrvNode 
                        -appServerNodeName BldSrvNode01
    

  3. Verify that the Dmgr001 profile exists.

  4. Create the appserver portion of the cell profile.

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

     cd $WAS_HOME/bin/
    ./manageprofiles.sh -create 
                        -templatePath $WAS_HOME/profileTemplates/cell/default 
                        -dmgrProfilePath $WAS_HOME/profiles/Dmgr001 
                        -portsFile $WAS_HOME/profiles/Dmgr001/properties/portdef.props 
                        -nodePortsFile $WAS_HOME/profiles/Dmgr001/properties/nodeportdef.props 
                        -profileName BldSrv 
                        -cellName BldSrvCell 
                        -nodeName BldSrvNode 
                        -appServerNodeName BldSrvNode01
    

After the creation of the dmgr 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 syncNode to synchronize the dmgr and the node.

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

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

If we federate an appserver node as part of cell profile creation using the -appServerNodeName parameter, the node does not have an original configuration. If we use the -removeNode command on a node 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
Create a cell profile

 

Related


manageprofiles
removeNode