Use the Profile creation wizard to create a deployment manager

Use the Profile creation wizard to create a deployment manager

+
Search Tips | Advanced Search

Overview

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.
After installing the core product files, create one of the following profiles to have an operational run-time environment:

An application server that is described in this topic.
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. We can federate the application server or use it as a stand-alone application server.
A deployment manager.
The deployment manager provides a single administrative interface to a logical group of application servers on one or more machines.
A custom profile that federate to make operational.
A custom profile is an empty node that one 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. We 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.
We can also use the wasprofile command to create a deployment manager.

Procedure

Start the Profile creation wizard to create a new run-time environment.
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.
The command is in...
install_root/bin/ProfileCreator

The name of the command varies per platform:

pctAIX.bin
pctHPUX.bin
64-bit platforms: pctHPUXIA64.bin
pctLinux.bin
64-bit platforms: pct.bin S/390 platforms: pctLinux390.bin
Power platforms: pctLinuxPPC.bin
pctSolaris.bin
pctWindows.exe
64-bit platforms: pctWindowsIA64.exe

Another way to start the Profile creation wizard is to select the wizard from the First steps console.

Open a command window.
Change directories to the firststeps directory in the installation root directory: The installation root varies by platform:

/usr/IBM/WebSphere/AppServer/firststeps
/opt/IBM/WebSphere/AppServer/firststeps
C:\Program Files\IBM\WebSphere\AppServer\firststeps

Issue the firststeps command to start the console:

./firststeps.sh
firststeps.bat

Select the Profile creation wizard option on the console.
The Profile creation wizard is an InstallShield for Multiplatforms application. The wizard loads the Java 2 SDK and then displays its Welcome panel.

Click Next on the Welcome panel.
The wizard displays the Profile type selection panel.
Select the type of profile to create and click Next. In this example, select the option for creating a deployment manager and click Next.
The wizard displays the Profile name panel.
Specify a name for the profile, then click Next.
Profile naming guidelines: 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 allowed within the name of a directory on your operating system, such as *&?
Slashes (/) or (\)
Double-byte characters are allowed.
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 directory...
profiles/profile/bin

...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.
Accept the default directory, specify a non-default location, or click Browse to select a different location. Click Next.
If you click Back and change the name of the profile, manually change the name on this panel when it displays again.
The wizard displays the Node, host, and cell name panel.
Specify a unique node name, the actual host name of the machine, and a unique cell name. Click Next.
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.

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

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 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 servers (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 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 one 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.
Verify that the ports specified for the deployment manager are unique and click Next.
The wizard displays the Windows service definition panel.
Choose whether to run the dmgr process as a Windows service on a Windows platform and click Next.
V6 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, 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.
We can also create other Windows services after the installation is complete, to start other server processes.
The wizard displays the Profile summary panel.
Click Next to create the deployment manager or click Back to change the characteristics of the deployment manager.
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.
Click Finish to exit and then click Profile creation wizard on the First steps console to start the wizard again, if you intend to create an application server profile.

Result

We can create a deployment manager profile. The node within the profile has a deployment manager named dmgr.

What to do next

Create an application server profile and add the node into the cell. Then you are ready to deploy an application.

See also

responsefile.pct.NDdmgrProfile.txt
wasprofile command

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.