This topic describes creating a run-time environment for a deployment manager.
Before you begin
Before using the Profile creation wizard, install the core product files.
The Profile creation wizard is the wizard interface to the profile creation tool, wasprofile. See the description of the wasprofile command for more information.
An error can occur when you have not provided enough system temporary space to create a profile. Verify that you have a minimum of 40 MB of temp space available before creating a profile.
You must have 200 MB of available disk space in the directory where you create an Application Server profile.
You must have 30 MB of available disk space in the directory where you create a deployment manager profile.
You must have 10 MB of available disk space in the directory where you create a custom profile.
Manually verify
that the required space for creating a profile is available on AIX. A known
problem in the underlying InstallShield for Multiplatforms (ISMP) code prevents
proper space checking on AIX systems at the time that the product disc was
created.
Why and when to perform this task
An application server profile has a default server (which is server1), the default application that includes the snoop servlet and the hitcount servlet, and application Samples. You can federate the application server or use it as a stand-alone application server.
See Using the Profile creation wizard to create a deployment manager. The deployment manager provides a single administrative interface to a logical group of application servers on one or more machines.
See Using the Profile creation wizard to create a custom profile. A custom profile is an empty node that you can customize to include application servers, clusters, or other Java processes, such as a messaging server.
This procedure describes creating a deployment manager profile. The procedure uses the graphical user interface provided by the Profile creation wizard. You can use the Profile creation wizard in silent mode with a response file, without the graphical user interface. See responsefile.pct.NDdmgrProfile.txt for examples of using the Profile creation wizard in silent mode.
You can also use the wasprofile command to create a deployment manager. See the description of the wasprofile command for more information.
Steps for this task
Several ways exist to start the wizard. The initial way to start the wizard is at the end of installation by selecting the check box to launch the Profile creation wizard.
One way to start the wizard is to issue the command directly from a command line.
Another way to start the Profile creation wizard is to select the wizard from the First steps console.
The Profile creation wizard is an InstallShield for Multiplatforms application. The wizard loads the Java 2 SDK and then displays its Welcome panel.
See the description of the firststeps command for more information.
The wizard displays the Profile type selection panel.
The wizard displays the Profile name 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 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 multi-profile 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 in the bin directory of each profile.
A command in the profiles/profile_name/bin directory 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 install_root/bin directory.
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.
If you click Back and change the name of the profile, you must manually change the name on this panel when it displays again.
The wizard displays the Node, host, and cell name panel.
The deployment manager node has the following characteristics.
Field name | Default value | Constraints | Description |
---|---|---|---|
Node name | The name of your machine, or a unique derivation of the machine name. | Use a unique name for the deployment manager. See the following note. |
The name is used for administration within the deployment manager cell. |
Host name | The DNS name of your machine. | The host name must be addressable through your network. See the following note. |
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 | The arbitrary name of the deployment manager cell. The cell is a logical grouping of managed nodes, under the control of the deployment manager. | 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. See the following note. |
All federated nodes become members of the deployment manager cell, which you name in this panel. |
Node and cell name considerations
The
profiles directory path must be no longer than 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 to communicate with this node. Selecting a host name that other machines can reach within your network is extremely important. Do not use the generic localhost identifier for this value.
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 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 Application 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 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 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 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 deployment manager characteristics, the wizard displays the Port value assignment panel.
The
wizard displays the Windows service definition panel.
Version 6 attempts to start Windows services for dmgr processes started by a startManager command. For example, if you configure a deployment manager as a Windows service and issue the startManager command, the wasservice command attempts to start the defined service.
If you chose to install a local system service, you do not have to specify your user ID or password. If you create a specified user type of service, you must specify the user ID and the password for the user who is to run the service. The user must have Log on as a service authority for the service to run properly.
To perform this installation task, the user ID must not have spaces in its name. The ID must also belong to the administrator group and must have the advanced user rights Act as part of the operating system and Log on as a service. The Installation wizard grants the user ID the advanced user rights if it does not already have them, 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. See Automatically restarting server processes for more information.
The wizard displays the Profile summary panel.
The wizard displays a Status panel during the creation of the profile. When the installation is complete, the wizard displays the Profile creation is complete panel.
Result
You can create a deployment manager profile. The node within the profile has a deployment manager named dmgr.
Refer to the description of the wasprofile command to learn about creating this type of profile using a command instead of a wizard.
What to do next
Create an application server profile and add the node into the cell. Then you are ready to deploy an application.
Deploy an application to get started!
See Fast paths for WebSphere Application Server to get started deploying applications.
Related tasks
wasprofile command