You can create a cell profile to group application server nodes for the deployment manager to mange. You can create the cell profile using the Profile Management tool on any machine where the core product files exist.
Before you use the Profile Management tool, install the core product files.
The Profile Management tool is the graphical user interface to the manageprofiles command. See the description of the manageprofiles command for more information.
You must provide enough system temporary space to create a profile. For information, read about the file system requirements for profiles.
After installing the core product files for the Network Deployment product, you must create a profile. The profile can be a deployment manager profile, a cell profile, an application server profile, or a custom profile.
This procedure describes how to create a cell profile with the Profile Management tool, which is a graphical user interface. A cell profile contains a deployment manager profile and a federated Application Server node profile. You can federate additional Application Server node profiles into this deployment manager profile after initial creation of the cell profile.
You can also use the manageprofiles command to create a cell profile. See the description of the manageprofiles for more information.
Select the Profile Management tool from the First steps console:
See the description of the firststeps command for more information.
Ways to start the wizard
Issue the command directly from a command prompt.
The wizard displays the Profile type selection panel.
The Profile creation options panel is displayed.
The Typical profile creation option creates a profile that uses default configuration settings. With the Advanced profile creation option, you can specify your own configuration values for a profile.
If you chose not to deploy the administrative console, then the administrative console ports are disabled on the Ports panel.
The wizard displays the Profile name and location panel.
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 one profile exists on a machine, every command works on the only server process in the configuration. You can make another profile the default profile when you create that profile by checking Make this profile the default on the Profile name and location panel of the Advanced profile creation path.
Addressing a profile in a multiprofile environment
When multiple 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.
Use the command to query the command shell to determine the calling profile and to autonomically address the command to the calling profile.
Default profile information
The
default profile directory is app_server_root/profiles,
where app_server_root is
the installation root.
The
default profile directory is app_server_root\profiles,
where app_server_root is
the installation root.
The wizard then displays the Node, host, and cell names panel.
The cell profile has the following characteristics:
Field Name | Default Value | Constraints | Description |
---|---|---|---|
Deployment manager node name | shortHostNameCellManagerNodeNumber where:
|
Use a unique name for the deployment manager. | The name is used for administration within the deployment manager cell. |
Application server node name | shortHostNameNodeNodeNumber where:
|
Use a unique name for the application server. | The name is used for administration within the deployment manager cell. |
Host name | The long form of the domain name server (DNS) name. |
The host name must be 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 that follows this table. |
Cell name | shortHostNameCellCellNumber where:
|
Use a unique name for the deployment manager cell.
If you plan to migrate a V5 deployment manager cell to this V6 deployment
manager, use the same cell name as the V5 deployment manager. A cell name must be unique whenever the product is running on the same physical machine or cluster of machines, such as a sysplex. Additionally, a cell name must be unique when 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 you want to federate their name spaces. Otherwise, you might encounter errors such as a javax.naming.NameNotFoundException exception. In which case, you need to create uniquely named cells. See the following note. |
All federated nodes become members of the deployment manager cell, which you name in this panel. |
Directory path considerations
The
number of characters in the profiles_directory_path\profile_name directory
must be less than or equal to 80 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 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 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 function 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 as the loopback address, 127.0.0.1, 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 displaying the cell characteristics, the wizard displays the Administrative security panel.
You can enable administrative security now during profile creation, or later from the console. If you enable administrative security now, then enter a user name and password to log onto the administrative console.
If you installed the Samples, and you chose to deploy them, then the Samples require an account under which to run. Supply the Samples password for the account. You cannot change the user name of the account.
After specifying security characteristics, the wizard displays the Port value assignment panel if you previously selected Advanced profile creation.
If you chose not to deploy the administrative console, then the administrative console ports are disabled on the Ports panel.
Port conflict resolution:
After specifying port assignments, the wizard displays
the Windows service definition panel, if you are installing on a Windows platform.
The service can be configured to automatically start on system reboot, or it can be manually started and stopped from the Windows Services panel after accepting the elevation prompt for Administrator privileges.
You cannot alter or control these service actions while running with standard user privileges. Administrator privileges are required.
If an application server is not configured to run as a service, then running these utilities from an elevation prompt for Administrator privileges is not required.
The product attempts to start Windows
services for application server processes that are started by a startServer
command. For example, if you configure an application server as a Windows
service, and issue the startServer command, then the wasservice command
attempts to start the defined service.
If you chose to install a local system service, then you do not have to specify your user ID or password. If you create a specified user type of service, then you must specify the user ID and the password for the user who runs the service. The user must have Log on as a service authority for the service to run properly. If the user does not have Log on as a service authority, then the Profile Management tool automatically adds the authority.
To perform this installation task, the user ID must not have spaces in its name. In addition to belonging to the administrator group, the ID must also have the advanced user right Log on as a service. The Installation wizard grants the user ID the advanced user right if it does not already have it and if the user ID belongs to the administrator group.
You can also create other Windows services after the installation is complete, to start other server processes. Read about automatically restarting server processes for more information.
You can remove the Windows service that is added during profile creation during profile deletion.
Profiles created to run as a Windows service fail to start when using Internet Protocol Version 6 (IPv6) if the service is configured to run as local system. Create a user-specific environment variable to enable IPv6. Since this environment variable is a user variable instead of a local system variable, only a Windows service that runs as that specific user can access this environment variable. By default, when a new profile is created and configured to run as a Windows service, the service is set to run as local system. When the Windows service for the product tries to run, the service is unable to access the user environment variable that specifies IPv6, and thus tries to start as IPv4. The server does not start correctly in this case. To resolve the problem, when creating the profile, specify that the Windows service for the product runs with the same user ID under which the environment variable that specifies IPv6 is defined, instead of as local system.
Default values for the Windows service
The Linux service definition panel is displayed if the current operating system is a supported version of Linux and the current user has the appropriate permissions.
The product attempts to start Linux services for application server processes that are started by a startServer command. For example, if you configure an application server as a Linux service and issue the startServer command, then the wasservice command attempts to start the defined service.
By default, the product is not selected to run as a Linux service.
To create the service, the user that runs the Profile Management tool must be the root user. If you run the Profile Management tool with a non-root user ID, then the Linux service definition panel is not displayed, and no service is created.
You must specify a user name under which the service runs.
To delete a Linux service, the user must be the root user or have appropriate privileges for deleting the service. Otherwise, a removal script is created that the root user can run to delete the service for the user.
The next wizard panel displays the Web server definition panel, if you previously selected Advanced profile creation.
If you use a Web server to route requests to the product, then you need to include a Web server definition. You can include the definition now, or define the Web server to the product later. If you define the Web server definition during the creation of this profile, then you can install the Web server and its plug-in after you create the profile. However, you must install both to the paths that you specify on the Web server definition panels. If you define the Web server to the product after you create this profile, then you must define the Web server in a separate profile.
The wizard displays the Profile Creation Summary panel.
The Profile creation progress panel, which shows the configuration commands that are running, is displayed.
When the profile creation completes, the wizard displays the Profile Creation Complete panel.
If you select Create another profile, then you go to the beginning of the Profile management tool so that you can create another profile. If you do not selection this option, then you exit the wizard.
You created a cell profile.
Refer to the description of the manageprofiles command to learn about creating a profile using a command instead of a wizard.
Deploy an application to get started.
Read about fast paths for the product to get started deploying applications.