[AIX HP-UX Linux Solaris Windows]

Creating a deployment manager profile

You can create a deployment manager profile so that you use the deployment manager server to manage application servers. Use the Profile Management tool to create the profile.

Before you begin

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.

[This information only applies to Version 6.1.0.9 and later running on the Microsoft Windows Vista operating system.] [Fix Pack 9 or later] Running the Profile Management tool on Microsoft Windows Vista™ and Windows 2008 operating systems: After installing WebSphere® Application Server Version 6.1, install a service pack containing Version 6.1.0.9 or later on your Microsoft® Windows® Vista operating system before you attempt to create any profiles using the Profile Management tool. If you are running Windows 2008, install a service pack containing Version 6.1.0.17 or later before you attempt to create any profiles using the Profile Management tool.
Supported configurations [AIX HP-UX Linux Solaris Windows] Supported configurations: You cannot use the Profile Management tool to create profiles on the following platforms:
  • 64-bit platforms
  • Linux for zSeries platform
sptcfg

About this task

New or updated for this feature pack After installing the core product files for the Network Deployment product, you must create a profile. The profile can be a Network Deployment deployment manager profile, a deployment manager profile enabled for the Feature Pack for EJB 3.0, a Network Deployment application server profile, an application server profile enabled for Feature Pack for EJB 3.0, a cell profile, or a custom profile.

This procedure describes creating a deployment manager profile using the graphical user interface that is provided by the Profile Management tool. The deployment manager provides a single administrative interface for a logical group of application servers on one or more machines.

You can also use the manageprofiles command to create a deployment manager. See the description of the manageprofiles command for more information.

Procedure

  1. Start the Profile Management tool to create a new runtime environment.

    Select the Profile Management tool from the First steps console:

    1. Open a command prompt.
    2. Change directories to the firststeps directory in the profile root directory.
      The profile root varies by the following platforms:
    3. Issue one of the following firststeps command to start the console:
      • [Linux] [HP-UX] [Solaris] [AIX] ./firststeps.sh
      • [Windows] firststeps.bat
    4. Select the Profile Management tool option from the console.

    See the description of the firststeps command for more information.

    Ways to start the wizard

    Several ways exist to start the wizard:
    • At the end of installation, select the check box to launch the Profile Management tool.
    • Issue the command directly from a command prompt.

      The command is in the following directory: The name of the command varies per platform:
      • [Linux] [HP-UX] [Solaris] [AIX] pmt.sh
      • [Windows] pmt.bat
    • Select the Profile Management tool from the First steps console.
    • [Windows] Use the Start menu to access the Profile Management tool. For example, click Start > Programs or All Programs > IBM WebSphere > your_product > Profile Management tool.
      [This information only applies to Version 6.1.0.9 and later running on the Microsoft Windows Vista operating system.] [Fix Pack 9 or later] Running the Profile Management tool on the Microsoft Windows Vista™ operating system:
      • If the product is installed in the Users directory on the Windows Vista operating system, as recommended, then you can use the standard user privileges of the administrator account to create new profiles without requiring administrator elevation.
      • If the product is installed in the Program Files directory, then launch the Profile Management tool by performing the following actions:
        1. Perform one of the following actions:
          • Right-click a Profile Management tool shortcut.
          • In Windows Explorer, right-click the pmt.bat file that is located in the app_server_root/bin/ProfileManagement directory.
        2. Click Run As Administrator.
    • [Linux] Use the Linux operating system menus that you use to start programs to start the Profile Management tool. For example, click the_operating_system_menus_to_access_programs > IBM WebSphere > your_product > Profile Management tool.
  2. New or updated for this feature pack Click Create to create a new profile.
  3. Click Next on the Welcome panel.

    New or updated for this feature pack The wizard displays the Environment Selection panel.

  4. Select the type of deployment manager profile that you want to create, and click Next.
    New or updated for this feature pack
    • Choose Deployment manager if you want to create a deployment manager profile that is not enabled for the Feature Pack for EJB 3.0.
    • Choose Feature Pack for EJB 3.0 if you want to create a deployment manager profile that is enabled for the Feature Pack for EJB 3.0.
      The Profile type selection panel is displayed.
      • Select Deployment manager with Feature Pack for EJB 3.0. Click Next.

    The Profile creation options panel is displayed.

  5. Select either Typical profile creation or Advanced profile creation, and click Next.

    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.

  6. If you selected Typical profile creation, go to the step on administrative security.
  7. If you selected Advanced profile creation, optionally select to deploy the administrative console, then click Next.

    The wizard displays the Profile name and location panel.

  8. Specify a name for the profile and the directory path for the profile directory, or accept the defaults. Then, 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
    • 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 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.

    The commands are found in the following location: A command has two lines. Set the WAS_USER_SCRIPT environment variable on the first line for the command prompt. You use the variable to set up the command environment to address the profile. Use the second line to call the command in the following location:

    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 name is profileTypeProfileName, where:
    • profileType is a value of AppSrv, DMgr, or Custom.
    • ProfileName is a sequential number that is used to create a unique profile name.

    [AIX] [HP-UX] [Linux] [Solaris] The default profile directory is app_server_root/profiles, where app_server_root is the installation root.

    [Windows] The default profile directory is app_server_root\profiles, where app_server_root is the installation root.

  9. On the Node, host, and cell names 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
    shortHostNameCellManagerNodeNumber where:
    • shortHostName is the short host name.
    • NodeNumber is a sequential number starting at 01.
    Use a unique name for the deployment manager. 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.

    Read about Host name considerations.

    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:
    • shortHostName is the short host name.
    • CellNumber is a sequential number starting at 01.
    Use a unique name for the deployment manager cell. If you plan to migrate a Version 5 deployment manager cell to this Version 6 deployment manager, use the same cell name as the Version 5 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. 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 terms are reserved folder names:
    • cells
    • nodes
    • servers
    • clusters
    • applications
    • deployments

    Directory path considerations

    [Windows] 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 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 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 deployment manager characteristics, the wizard displays the Administrative security panel.

  10. Optionally enable administrative security, and click Next.

    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.

    After specifying security characteristics, the wizard displays the Port value assignment panel if you previously selected Advanced profile creation.

  11. If you selected Typical profile creation at the beginning of these steps, then go to the step that displays the Profile summary panel.
  12. Verify that the ports specified for the deployment manager are unique, and click Next.

    If you chose not to deploy the administrative console, then the administrative console ports are disabled on the Ports panel.

    Port conflict resolution:

    Ports are recognized as being in use if one of the following conditions exists:
    • The ports are assigned to a profile created under an installation performed by the current user.
    • The port is currently in use.
    Validation of ports occurs when you access the Port value assignment panel. Conflicts can still occur between the Port value assignment panel and the Profile Creation Complete panel because ports are not assigned until profile creation completes.
    If you suspect a port conflict, then you can investigate the port conflict after the profile is created. Determine the ports that are used during profile creation by examining the following files: Included in this file are the keys and values used in setting the ports. If you discover ports conflicts, then you can reassign ports manually. To reassign ports, run the updatePorts.ant file by using the ws_ant script.

    [Windows] [Linux] The wizard displays the Windows service definition panel if you are installing on a Windows platform and the installation ID has the administrative group privilege. The wizard displays the Linux service definition panel if you are installing on a supported Linux platform and the ID that runs the Profile Management tool is the root user.

  13. Choose whether to run the dmgr process as a Windows service on a Windows platform or as a Linux Service on a Linux platform, and click Next.
    The Windows service definition panel is displayed for the Windows platform only if the ID that installs the Windows service has the administrator group privilege. However, you can run the WASService.exe command to create the Windows service as long as the installer ID belongs to the administrator group. Read about automatically restarting server processes for more information.
    [This information only applies to Version 6.1.0.9 and later running on the Microsoft Windows Vista operating system.] [Fix Pack 9 or later] Running an application server as a service on the Microsoft Windows Vista™ operating system:
    • An application server that is running as a service needs to run with Administrator privileges if it is to be started or stopped on the Microsoft Windows Vista operating system.

      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.

    • Using the WASService.exe utility to change the characteristics of the service or to create a new service also requires running with Administrator privileges.
      To do this, run WASService.exe from a command prompt that is launched by performing the following actions:
      • Right-click the command file or its shortcut.
      • Click Run As Administrator.
    • The following .bat files can run to create service actions:
      • startServer.bat
      • stopServer.bat
      • startNode.bat
      • stopNode.bat
      • startManager.bat
      • stopManager.bat

      You cannot alter or control these service actions while running with standard user privileges. Administrator privileges are required.

      If an application server is installed as a service, then the service can be controlled by running the .bat files from a command prompt that is launched by performing the following actions:
      • Right-click a command prompt shortcut.
      • Click Run As Administrator.

      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.

    [Windows] The product attempts to start Windows services for dmgr processes that are started by a startManager command. For example, if you configure a deployment manager as a Windows service and issue the startManager 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.

    IPv6 considerations

    Profiles created to run as a Windows service fail to start when using 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 dmgr process 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 dmgr process runs as the same user ID under which the environment variable that specifies IPv6 is defined, instead of as Local System.

    Default Windows service information

    [Windows] The default values for the Windows service definition panel are as follows:
    • The default is to run as a Windows service.
    • The service process is selected to run as a system account.
    • The user account is the current user name. User name requirements are the requirements that the Windows operating system imposes for a user ID.
    • The startup type is automatic. The values for the startup type are those values that the Windows operating system imposes. If you want a startup type other than automatic, you can either select another available option from the drop down list or change the startup type after you create the profile. You can also remove the created service after profile creation, and add it later with the desired startup type. You can choose not to create a service at profile creation time and optionally create it later with the desired startup type.

    [Linux] 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 wizard displays the Profile Creation Summary panel.

  14. Click Create to create the deployment manager, or click Back to change the characteristics of the deployment manager.

    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.

  15. Optionally, select Create another profile, and click Finish to exit.
  16. Optionally, select Launch the First steps console, Create another profile, or both. Click Finish to exit.

    With the First steps console, you can create additional profiles and start the application server. Use the Create another profile option to create additional profiles.

Results

You created a deployment manager profile.

Refer to the description of the manageprofiles command to learn about creating a profile using a command instead of a wizard.

What to do next

Create an application server profile, and add the node into the cell.

Deploy an application to get started.

Read about fast paths for the product to get started deploying applications.




In this information ...


IBM Redbooks, demos, education, and more

(Index)

Use IBM Suggests to retrieve related content from ibm.com and beyond, identified for your convenience.

This feature requires Internet access.

Task topic Task topic    

Terms and conditions for information centers | Feedback

Last updatedLast updated: Aug 31, 2013 2:56:59 AM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=pix&product=was-nd-dist&topic=tpro_instancesdmgr
File name: tpro_instancesdmgr.html