This topic describes the 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 Linux or UNIX platform, 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.
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 options response file for Network Deployment 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.
Location:
Product disc location | Installed location |
---|---|
/WAS directory | install_root/bin/ProfileCreator directory |
Use the file on the product disc 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
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 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 |
-W pctresponsefilelocationqueryactionInstallWizardBean.fileLocation= "/opt/IBM/WebSphere/MyOptionFiles/customProfile.txt"
install -options "myresponsefile.txt" -silent
Creating a profile after installation
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.
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
Logging
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
-W profilenamepanelInstallWizardBean.profileName
Avoiding reserved names
-W nodehostnamepanelInstallWizardBean.nodeName="" -W nodehostnamepanelInstallWizardBean.hostName="" -W setnondmgrcellnameinglobalconstantsInstallWizardBean.value=""
-W nodehostandcellnamepanelInstallWizardBean.nodeName="" -W nodehostandcellnamepanelInstallWizardBean.hostName="" -W nodehostandcellnamepanelInstallWizardBean.cellName=
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.
Example responsefile.pct.NDdmgrProfile.txt file
################################################################################ # # 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 # install_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 install_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"