Specify a name for the
profile, or accept the default: click Next. Profile
naming guidelines: Double-byte characters are supported. The profile name
can be any unique name with the following restrictions. Do not use any of
the following characters when naming your profile:
- Spaces
- Illegal special characters that are not supported within the name of a
directory on your operating system, such as *&?
- Slashes (/) or (\)
The default profile
The first
profile that you create on a machine is the default profile. The default profile
is the default target for commands that are issued from the bin directory
in the product installation root. When only one profile exists on a machine,
every command works on the only server process in the configuration.
Addressing
a profile in a multiprofile environment
When two or
more profiles exist on a machine, certain commands require that you specify
the profile to which the command applies. These commands use the -profileName
parameter to identify which profile to address. You might find it easier to
use the commands that are in the bin directory of each profile.
The commands are found in the:
A command has two lines. The first line sets the WAS_USER_SCRIPT environment
variable for the command window. The variable sets up the command environment
to address the profile. The second line calls the actual command in the
The actual command queries the command shell to determine
the calling profile and to autonomically address the command to the calling
profile.
The
wizard then displays the Profile directory panel.
On the Node and host names panel, specify the characteristics
for the application server; click Next. Use unique names
for each application server that you create.
Reserved
names: Avoid using reserved folder names as field values. The use of reserved
folder names can cause unpredictable results. The following words are reserved:
- cells
- nodes
- servers
- clusters
- applications
- deployments
Field name |
Default value |
Constraints |
Description |
Node name |
Name of your machine
|
Avoid using the reserved words. |
Pick any name you want. To help organize your installation,
use a unique name if you plan to create more than one application server on
the machine. |
Host name |
DNS name of your machine
|
Addressable through your network. |
Use the actual DNS name or IP address of your machine
to enable communication with your machine. See additional information about
the host name following this table. |
Node name considerations: If
you plan to migrate an installation of V5.x Network Deployment to V6 and migrate
one of the managed nodes in the cell, use the same node name for the V6 application
server that you used for the V5.x managed node.
Directory path considerations: The installation
directory path must be less than or equal to 60 characters.
Host
name considerations:
The host name is the network name
for the physical machine on which the node is installed. The host name must
resolve to a physical network node on the server. When multiple network cards
exist in the server, the host name or IP address must resolve to one of the
network cards. Remote nodes use the host name to connect to and communicate
with this node. Selecting a host name that other machines can reach within
your network is extremely important. Do not use the generic identifier, localhost,
for this value. Also, do not attempt to install WebSphere Application Server
products on a machine with a host name that uses characters from the double-byte
character set (DBCS). DBCS characters are not supported when used in the host
name.
If you define coexisting nodes on the same computer
with unique IP addresses, define each IP address in a domain name server (DNS)
look-up table. Configuration files for stand-alone Application Servers do
not provide domain name resolution for multiple IP addresses on a machine
with a single network address.
The value that you specify
for the host name is used as the value of the hostName property in configuration
documents for the stand-alone Application Server. Specify the host name value
in one of the following formats:
- Fully qualified domain name server (DNS) host name string, such as xmachine.manhattan.ibm.com
- The default short DNS host name string, such as xmachine
- Numeric IP address, such as 127.1.255.3
The fully qualified DNS host name has the advantages
of being totally unambiguous and flexible. You have the flexibility of changing
the actual IP address for the host system without having to change the Application
Server configuration. This value for the host name is particularly useful
if you plan to change the IP address frequently when using Dynamic Host Configuration
Protocol (DHCP) to assign IP addresses. A format disadvantage is a dependency
on DNS. If DNS is not available, then connectivity is compromised.
The short host name is also dynamically resolvable. A short name
format has the added ability of being redefined in the local hosts file so
that the system can run the Application Server, even when disconnected from
the network. Define the short name to 127.0.0.1 (local loopback) in the hosts
file to run disconnected. A format disadvantage is a dependency on DNS for
remote access. If DNS is not available, then connectivity is compromised.
A numeric IP address has the advantage of not requiring name resolution
through DNS. A remote node can connect to the node that you name with a numeric
IP address without DNS being available. A format disadvantage is that the
numeric IP address is fixed. You must change the setting of the hostName property
in Express configuration documents whenever you change the machine IP address.
Therefore, do not use a numeric IP address if you use DHCP, or if you change
IP addresses regularly. Another format disadvantage is that you cannot use
the node if the host is disconnected from the network.
After
specifying application server characteristics, the wizard displays the Port
value assignment panel.