WebSphere Application Server V7.0: Concepts ... - IBM Redbooks

Often a naming convention for cell names will include the name of the stage
(such as integration test, acceptance test, production) and the name of the
department or project owning it, if appropriate.
► Naming nodes
In a stand-alone environment, you will have a single node with a single
application server. A naming convention is not really a concern. However, you
can specify a node name during profile creation. If you take the default, the
node name is in the following format:
NODE
The will increment, starting with “01,” with every new node, for
example, server1Node01, server1Node02, and so on.
In a distributed server environment, the node must be unique within a cell.
Nodes generally represent a system and will often include the host name of
the system. You can have multiple nodes on a system. Keep this in mind
when planning your WebSphere names.
Naming conventions for nodes often include the physical machine name
where they are running, such as NodexxAP010 if the server name is
ServerAP010 and a running number to enable growth if additional nodes
need to be created.
► Naming application servers
In stand-alone environments, the default server name is “server1,” but can be
overridden through the manageprofiles.bat(sh) command, or using the
advances profile creation options in the PMT.
Note: When you federate multiple stand-alone application servers that
were created using the default naming schema to a cell, you will have a
unique combination of node name and server1, thus ending up with
multiple server1s in the cell.
In a distributed server environment, it is more likely that new application
servers are created on a federated node using the Integrated Solutions
Console or another administrative tool. In this case, the server can be named
and a meaningful name should be assigned. Whether you choose to name
servers based on their location, function, membership in a cluster, or some
other scheme will largely depend on how you anticipate your servers being
used and administered.
Note: The server name must be unique within the node.
Chapter 6. Installation 221