This topic discusses reserved terms and issues you must consider when naming your profile, node, host and cell (if applicable).
Field name | Default value | Constraints | Description |
---|---|---|---|
Stand-alone server profiles | |||
Node name | On Linux®, UNIX®, and Windows® platforms: shortHostNameNodeNodeNumber where:
On i5/OS platforms: shortHostName_profileName where:
|
Avoid using the reserved names. | Pick any name you want. To help organize your installation, use a unique name if you plan to create more than one server on the system. |
Host name | On Linux, UNIX, and Windows platforms: The long form of the domain name server (DNS) name. On i5/OS platforms: The fully qualified machine name including the domain name suffix. |
The host name must be addressable through your network. | Use the actual DNS name or IP address of your workstation to enable communication with it. See additional information about the host name following this table. |
Cell name | On Linux, UNIX, and Windows platforms: shortHostNameNodeNodeNumberCell where:
On i5/OS platforms: shortHostName_profileName where:
|
Use a unique name for the deployment manager cell. A cell name must be unique in any circumstance in which the product is running on the same physical workstation or cluster of workstations, such as a Sysplex. Additionally, a cell name must be unique in any circumstance in which network connectivity between entities is required either between the cells or from a client that must communicate with each of the cells. Cell names also must be unique if their name spaces are going to be federated. Otherwise, you might encounter symptoms such as a javax.naming.Name NotFoundException exception, in which case, you need to create uniquely named cells. | All federated nodes become members of the deployment manager cell, which you name in the Node, host, and cell names panel of the Profile Management Tool. |
Deployment manager profiles | |||
Node name | On Linux, UNIX, and Windows platforms: shortHostNameCellManager NodeNumber where:
On i5/OS platforms: profileNameManager where profileName is the name of the profile. |
Use a unique name for the deployment manager. Avoid using the reserved names. | The name is used for administration within the deployment manager cell. |
Host name | On Linux, UNIX, and Windows platforms: The long form of the domain name server (DNS) name. On i5/OS platforms: The fully qualified machine name including the domain name suffix. |
The host name must be addressable through your network. Avoid using the reserved names. | Use the actual DNS name or IP address of your workstation to enable communication with it. See additional information about the host name following this table. |
Cell name | On Linux, UNIX, and Windows platforms: shortHostNameCellCellNumber where:
On i5/OS platforms: profileNameNetwork where profileName is the name of the profile. |
Use a unique name for the deployment manager cell. A cell name must be unique in any circumstance in which the product is running on the same physical workstation or cluster of workstations, such as a Sysplex. Additionally, a cell name must be unique in any circumstance in which network connectivity between entities is required either between the cells or from a client that must communicate with each of the cells. Cell names also must be unique if their name spaces are going to be federated. Otherwise, you might encounter symptoms such as a javax.naming.Name NotFoundException exception, in which case, you need to create uniquely named cells. | All federated nodes become members of the deployment manager cell , which you name in the Node, host, and cell names panel of the Profile Management Tool. |
Custom profiles | |||
Node name | On Linux, UNIX, and Windows platforms: shortHostNameNodeNodeNumber where:
On i5/OS platforms: shortHostName_profileName where:
|
Avoid using the reserved names. Use a unique name within the deployment manager cell. |
The name is used for administration within the deployment manager cell to which the custom profile is added. Use a unique name within the deployment manager cell. |
Host name | On Linux, UNIX, and Windows platforms: The long form of the domain name server (DNS) name. On i5/OS platforms: The fully qualified machine name including the domain name suffix. |
The host name must be addressable through your network. | Use the actual DNS name or IP address of your workstation to enable communication with it. See additional information about the host name following this table. |
Host name considerations:
The host name is the network name for the physical workstation 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 to communicate with this node.
WebSphere® ESB is compliant to both Internet Protocol version 4 (IPv4) and version 6 (IPv6). Wherever you can enter IP addresses in the administrative console, or elsewhere, you can do so in either format. Note that if IPv6 is implemented on your system you must enter the IP address in IPv6 format, and conversely, if IPv6 is not yet available to you, enter IP addresses in IPv4 format. For more information on IPv6 see the Official IPv6 Web site.
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 servers do not provide domain name resolution for multiple IP addresses on a workstation with a single network address.
The fully qualified DNS host name has the advantage of being totally unambiguous and also flexible. You have the flexibility of changing the actual IP address for the host system without having to change the stand-alone server configuration. This value for 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 being dependent 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 stand-alone 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 disadvantage of the short name format is being dependent 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 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 configuration documents whenever you change the workstation 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.