responsefile.pct.NDdmgrProfile.txt

The responsefile.pct.NDdmgrProfile.txt file is a sample response file for creating a deployment manager profile.

Create a deployment manager profile with an options response file after logging on as root on a platform such as AIX or Linux, or as a user that belongs to the administrator group on a Windows platform. Some steps of the installation procedure on a Windows platform require the user to belong to the administrator group and to have the advanced user rights Act as part of the operating system and Log on as a service.

The response file is shipped with default values.

A common use for an options file is to run the Installation wizard in silent mode, which is referred to as installing silently. The wizard reads the options file to determine responses and does not display the graphical user interface. Issue the following command to use a copy of the options file named myresponsefile.txt for a silent installation:
pctWindows.exe -options "myresponsefile.txt" -silent

Avoiding the use of the -silent option within the options response file

A problem occurs when the -silent option exists in the file. The file works with the option during a direct call to the Profile Creation wizard, but fails when called from a silent product installation. See Customizing the response file for information about creating a profile silently during a silent product installation.

The option is unnecessary. Avoid using the option to avoid problems.

Response file locations

The example options response files are in two locations.

Example files:
  • responsefile.pct.NDdmgrProfile.txt
  • responsefile.pct.NDmanagedProfile.txt
  • responsefile.pct.NDstandAloneProfile.txt

Location:

Table 1. Option response file locations
Product disk location Installed location
/WAS directory app_server_root/bin/ProfileCreator directory

Use the file on the product disk to install the Network Deployment product silently and create a profile.

After installing the Network Deployment product, you can use the installed response file with the -options parameter on the Profile Creation wizard command.

Required disk space

Profile Required disk space Required temp space
Deployment manager profile 30 MB 40 MB
Custom profile 10 MB 40 MB
Application server profile 200 MB 40 MB

Creating an operational environment during product installation

Version 6 installation of the Network Deployment product is a two-step process:
  1. Installing the core product files and feature files.
  2. Creating a deployment manager profile, a custom profile, or an application server profile.

The sample options response file, responsefile.nd.txt, controls the first part of the installation and can also start the second part of the installation. To create a profile as part of installing the core product files, use the option in the responsefile.nd.txt file that identifies the response file for creating a profile. The profile response file lets you use the Profile Creation wizard silently.

To edit and use the appropriate response file for creating a profile, perform the following procedure:
  1. Copy the appropriate file from the WAS directory on the product disk to a place that you can easily identify on your machine. The example files are:
    To create a: Copy the following response file:
    Deployment manager profile responsefile.pct.NDdmgrProfile.txt
    Custom profile responsefile.pct.NDmanagedProfile.txt
    Application server profile responsefile.pct.NDstandAloneProfile.txt
  2. Edit the file to customize the values for your installation.
  3. Verify that no -silent option exists in the response file for the Profile creation wizard. If the option exists, the profile is not created.
  4. Save the file.
  5. Edit the responsefile.nd.txt file to identify the location and name of the profile response file. Change the value of the -W pctresponsefilelocationqueryactionInstallWizardBean.fileLocation option to identify the file. For example:
    -W pctresponsefilelocationqueryactionInstallWizardBean.fileLocation=
    "/opt/IBM/WebSphere/MyOptionFiles/customProfile.txt"
  6. Start the installation. For example:
    install -options "myresponsefile.txt" -silent
    
  7. After the installation, examine the logs for success.

Creating a profile after installation

Version 6 installation of the Network Deployment product is a two-step process:
  1. Installing the core product files and feature files
  2. Creating a deployment manager profile, a custom profile, or an application server profile

When the core product files exist, create a profile at any time using the Profile Creation wizard. Start the wizard from the First steps console or directly using the Profile Creation wizard command.

You can also use one of the following sample options response files for profiles to create a profile silently using the Profile Creation wizard in silent mode. To edit and use the appropriate response file for creating a profile, perform the following procedure:
  1. Copy the appropriate file from the app_server_root/bin/ProfileCreator directory to a place that you can easily identify on your machine. The example files are:
    To create a profile for a: Copy the following response file:
    Deployment manager responsefile.pct.NDdmgrProfile.txt
    Managed node responsefile.pct.NDmanagedProfile.txt
    Stand-alone application server responsefile.pct.NDstandAloneProfile.txt

    For example, copy the file as my_options_file.txt

  2. Edit the file to customize the values for your installation.
  3. Save the file.
  4. Start the installation.
    For example:
    • [AIX] ./pctAIX.bin -options my_options_file.txt -silent
    • [HP-UX] ./pctHPUX.bin -options my_options_file.txt -silent
    • [HP-UX] 64-bit platforms: ./pctHPUXIA64.bin -options my_options_file.txt -silent
    • [Linux] ./pctLinux.bin -options my_options_file.txt -silent
    • [Linux] 64-bit platforms: ./pct.bin -options my_options_file.txt -silent
    • [Linux] Power platforms: ./pctLinuxPPC.bin -options my_options_file.txt -silent
    • [Linux] S/390 platforms: ./pctLinux390.bin -options my_options_file.txt -silent
    • [Solaris] ./pctSolaris.bin -options my_options_file.txt -silent
    • [Windows] pctWindows.exe -options my_options_file.txt -silent
    • [Windows] 64-bit platforms: pctWindowsIA64.exe -options my_options_file.txt -silent
  5. After using the Profile Creation wizard, examine the logs for success.

Logging

The following log files record information about profile creation:
  • The app_server_root/logs/log.txt file records installation status.
  • The profile_root/logs/pctLog.txt file records installation events that occur when creating profiles with the Profile creation wizard.
  • The app_server_root/logs/wasprofile/wasprofile_create_profile_name.log file records installation events that occur when creating profiles.
  • The app_server_root/logs/wasprofile/wasprofile_delete_profile_name.log file records installation events that occur when deleting profiles.

See Troubleshooting installation for more information.

Usage notes

Naming considerations

Consider the following recommendations when supplying names for the profile and other objects.

Naming the profile

Use the following guidelines when supplying a value for the profile name directive:
-W profilenamepanelInstallWizardBean.profileName
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.

Avoiding reserved names

Avoid the following reserved folder names as values for the directives in the responsefile.pct.NDstandAloneProfile.txt file and in the responsefile.pct.NDmanagedProfile.txt file:

-W nodehostnamepanelInstallWizardBean.nodeName=""
-W nodehostnamepanelInstallWizardBean.hostName=""
-W setnondmgrcellnameinglobalconstantsInstallWizardBean.value=""
Avoid the following reserved folder names as values for the directives in the responsefile.pct.NDdmgrProfile.txt file:

-W nodehostandcellnamepanelInstallWizardBean.nodeName=""
-W nodehostandcellnamepanelInstallWizardBean.hostName=""
-W nodehostandcellnamepanelInstallWizardBean.cellName=
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

[Windows] The number of characters in the profile_root must be no more than 80 characters.

See Host name values for more information.

Example

################################################################################
#
# Response file for Websphere Application Server 6.0 dmgr profile creation
#
# This options file is located in the CD_ROOT\WAS\ directory and in the 
# app_server_root\bin\ProfileCreator directory. 
#
# To use the options file under CD_ROOT\WAS\ directory, follow the instructions 
# in CD_ROOT\WAS\responsefile.nd.txt. The WebSphere Application Server
# Network Deployment installer locates this file during silent installation
# and automatically runs the silent profile creation at the end of installation.
# 
# To use the options file under app_server_root\bin\ProfileCreator for silent profile
# creation, you must change various values in the file and use the following  
# command line arguments:
# 
#    -options "responsefile.pct.NDdmgrProfile.txt" -silent
#
################################################################################


################################################################################
# 
# Profile name
#
# Set the profile name for installing a deployment manager profile. The profile 
# name must be unique for this WebSphere Application Server installation.  
#
-W profilenamepanelInstallWizardBean.profileName="profileDmgr"

################################################################################
# If you want to set this profile to be your default profile, set to "true".
# Otherwise set to "false". If this is the first profile being created, the profile  
# automatically is the default. 
#
-W profilenamepanelInstallWizardBean.isDefault="false"


################################################################################
# 
# Profile location
#
# Specify a directory to contain the files that define the run-time environment, 
# such as commands,configuration files, and log files. If the directory contains 
# spaces, enclose it in double-quotes as shown in the Windows example below. 
#
# Note that spaces in the install location is only supported on Windows
# operating systems.
#
# Default Install Location:
#
#    -P installLocation="<WAS_HOME>\profiles\<PROFILE_NAME>"
#
-P installLocation="C:\Program Files\IBM\WebSphere\AppServer\profiles\profileDmgr"


################################################################################
# 
# Node name
#
# Please select the node name for the Application Server. Node name under one cell 
# has to be unique. 
#
# Replace YOUR_NODE_NAME with the actual node name. 
#
-W nodehostandcellnamepanelInstallWizardBean.nodeName="YOUR_NODE_NAME"

################################################################################
#
# Host name
#
# Specify the host name for the Application Server. The host name is the domain 
# name system (DNS) name (short or long) or the IP address of this computer. 
# 
# Replace YOUR_HOST_NAME with the actual host name. Comment the line to use 
# the default value.
# 
-W nodehostandcellnamepanelInstallWizardBean.hostName="YOUR_HOST_NAME"

################################################################################
#
# Cell name
#
# Specify the cell name for the Application Server. 
#
# If you plan to migrate a V5 deployment manager cell to this V6 deployment 
# manager, specify the same cell name as the V5 cell. 
#
# Replace YOUR_CELL_NAME with the actual cell name. 
#
-W nodehostandcellnamepanelInstallWizardBean.cellName="YOUR_CELL_NAME"


################################################################################
# 
# Port value assignment
# 
# The following entries are used to reset port numbers used in the configuration
#
# They are currently set to the defaults. 
# Please check to make sure there are no Port Conflicts.
# Port nubmers for each profile can be found in: 
# <profile>/config/cells/<cell name>/nodes/<node name>/serverindex.xml
#
-W pctdmgrprofileportspanelInstallWizardBean.WC_adminhost="9060"
-W pctdmgrprofileportspanelInstallWizardBean.WC_adminhost_secure="9043"
-W pctdmgrprofileportspanelInstallWizardBean.BOOTSTRAP_ADDRESS="9809"
-W pctdmgrprofileportspanelInstallWizardBean.SOAP_CONNECTOR_ADDRESS="8879"
-W pctdmgrprofileportspanelInstallWizardBean.SAS_SSL_SERVERAUTH_LISTENER_ADDRESS="9404"
-W pctdmgrprofileportspanelInstallWizardBean.CSIV2_SSL_SERVERAUTH_LISTENER_ADDRESS="9406"
-W pctdmgrprofileportspanelInstallWizardBean.CSIV2_SSL_MUTUALAUTH_LISTENER_ADDRESS="9405"
-W pctdmgrprofileportspanelInstallWizardBean.ORB_LISTENER_ADDRESS="9101"
-W pctdmgrprofileportspanelInstallWizardBean.CELL_DISCOVERY_ADDRESS="7277"
-W pctdmgrprofileportspanelInstallWizardBean.DCS_UNICAST_ADDRESS="9352"


################################################################################
# 
# Windows service
#
# The following directives are to install services for WebSphere Application Server 
# on Windows.  
# Using Services, you can start and stop services, 
# and configure startup and recovery actions. 
# Set winServiceQuery="false" will turn off the function on windows system.
# You can ignore these or comment them out for other Operating Systems.
#
-W winservicepanelInstallWizardBean.winServiceQuery="true"

################################################################################
# Specify account type of the service. Legal values are:
#   
#    localsystem   - Indicates that you choose to use Local System account.
#    specifieduser - Indicates that you choose to use specified user account.
#
-W winservicepanelInstallWizardBean.accountType="localsystem"

################################################################################
# If you chose to install a service above with the accountType="localsystem",
# the userName and password below can be ignored. If the accountType was set to:
# accountType="specifieduser", then you must specify the User Name and Password 
# which are required to install the Services. The current user must be admin or must 
# have admin authority to install a Service. Also the username
# which is given here must have "Log On as a Service " authority 
# for the service to run properly.
#
# Replace YOUR_USER_NAME with your username.
#
-W winservicepanelInstallWizardBean.userName="YOUR_USER_NAME"

################################################################################
# Replace YOUR_PASSWORD with your valid password.
#
-W winservicepanelInstallWizardBean.password="YOUR_PASSWORD"

################################################################################
# Set the startup type of the WebSphere Application Server on Windows.
# Valid values are "automatic", "manual", and "disabled".
#
-W winservicepanelInstallWizardBean.startupType="manual"



################################################################################
# Profile type
#
# Must be set to  "dmgr" for installing a deployment manager Profile.
# Do not change this!
#
-W profiletypepanelInstallWizardBean.selection="dmgr"



Related tasks
Customizing the response file
Installing silently
Installing the product and additional software
Reference topic    

Terms of Use | Feedback

Last updated: Aug 29, 2010 10:43:27 PM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=v602web&product=was-nd-mp&topic=rins_dmgrprofile
File name: rins_responsefile_pct_dmgrprofile.html