Creating a deployment manager profile silently

The response file responsefile.pcaw.wps.dmgrProfile.txt can be used to silently create a deployment manager profile.

The installation program reads this file to determine the characteristics of a deployment manager profile when you install silently. You can also create additional deployment manager profiles by using this response file after initial installation. The response file is shipped with default values.

Refer to Installing the product silently for more information on silent installation.

Before you start

Before using this procedure, ensure that:
  • You want to create a deployment manager profile and that you want to do so silently. If you want to create the profile with an interactive interface instead, see Creating and augmenting profiles by using the Profile Wizard for descriptions of other profile creation procedures.
  • If you plan to locate the repository for WebSphere Process Server on a remote server, that you create it before beginning this procedure. Options in the WebSphere Process Server response file will let you create a repository on the local server or use an existing one on a remote server.
  • You have enough disk and temporary space to create the new profile. See Required disk space for the minimum disk space required.
  • If you are installing WebSphere Process Server, you have prepared your operating system for installation. See Preparing the operating system for installation for instructions.
  • If you are installing WebSphere Process Server over an existing installation of WebSphere Application Server or WebSphere Application Server Network Deployment that has global security enabled, that you disable it before installing the product. If you have already installed WebSphere Process Server and you have enabled global security, ensure you disable it before creating the profile. For information on enabling and disabling global security, see the WebSphere Application Server Network Deployment, version 6.0 information center at http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/index.jsp.
  • You are creating the profile as the root user on a Linux or UNIX system, or as a member of the Administrator group on a Windows system.

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

Do not use the -silent option in the file. Doing so can cause the profile creation to fail.

Response file locations

The example file responsefile.pcaw.wps.dmgrProfile.txt can be found in two locations:

Table 1. Response file locations
WebSphere Process Server CD 1 location Installed location
WBI directory
  • Icon indicating Linux platforms Icon indicating UNIX platforms On Linux and UNIX platforms: install_root/bin/ProfileCreator_wbi directory
  • Icon indicating Windows platforms On Windows platforms: install_root\bin\ProfileCreator_wbi directory

Creating a deployment manager profile during installation

To create a deployment manager profile during initial installation of WebSphere Process Server, do the following:
  1. Copy the responsefile.pcaw.wps.dmgrProfile.txt file from the WBI directory on WebSphere Process Server CD 1 to a place that you can easily identify on your machine and save it with a new name, such as dmgrProfile_1.txt.
  2. Edit this profile response file using a flat file editor of your choice, on the target operating system, to customize it with the parameters for your system. Read the directions within the response file to choose appropriate values.
  3. Verify that no -silent option exists in the response file for the Profile Wizard. If the option exists, the profile is not created.
  4. Save the file.
  5. Copy the product installation response file responsefile.wps.txt from the WBI directory on WebSphere Process Server CD 1 to a place that you can easily identify on your machine and save it with a new name, such as myoptionsfile.
  6. Edit this file using a flat file editor of your choice, on the target operating system, to customize it with the parameters for your system. Read the directions within the response file to choose appropriate values. Refer to Installing the product silently for a sample response file.
  7. At the end of your copy of responsefile.wps.txt, change the value of the option -W summaryPanel_InstallWizardBean.launchPCAW to true. For instance,
    -W summaryPanel_InstallWizardBean.launchPCAW="true"
  8. Change the value of the option -W pcawResponseFileLocationQueryAction_InstallWizardBean.fileLocation from "" to identify the absolute file path of the (modified) profile response file. For instance,
    -W pcawResponseFileLocationQueryActionInstallWizardBean.fileLocation=
    "/opt/IBM/WebSphere/MyOptionFiles/dmgrProfile_1.txt"
  9. Save your changes in your copy of responsefile.wps.txt.
  10. Use one of the following commands to install WebSphere Process Server and create a deployment manager profile. These commands assume that you have copied the responsefile.wps.txt file into a temporary directory and renamed it as myoptions.txt before customizing the file.
    • Icon indicating Linux platforms Icon indicating UNIX platforms On Linux and UNIX platforms:
      install -options /tmp/WBI/myoptions.txt -silent
    • Icon indicating Windows platforms On Windows platforms:
      install.exe -options "C:\temp\WBI\myoptions.txt" -silent
Verify the success of the installation by examining the WebSphere Process Server log file. If the last line of the file contains the word INSTCONFSUCCESS, the WebSphere Process Server features you selected and WebSphere Application Server Network Deployment were installed successfully. The log file is located as follows:
  • Icon indicating Linux platforms Icon indicating UNIX platforms On Linux and UNIX platforms: install_root/logs/wbi/log.txt
  • Icon indicating Windows platforms On Windows platforms: install_root\logs\wbi\log.txt
where install_root represents the location of the WebSphere Process Server installation. If this log file contains the string INSTCONFSUCCESS on the last line, then the installation was successful. Note that other terms such as INSTCONFPARTIALSUCCESS or INSTCONFFAILED can occur on other lines within the file, or even on the last line, but as long as INSTCONFSUCCESS is included in the last line, the installation was successful. If the installation was not successful, examine other log files to determine why. See the descriptions of relevant log files listed in Log files, of error messages in Error messages: installation and profile creation and augmentation, and check out Troubleshooting installation for tips on troubleshooting your installation. Also refer to Recovering from profile creation or augmentation failure for troubleshooting tips if the profile did not create successfully.

Icon indicating 6.0.1 content only If you are using WebSphere Process Server, version 6.0.1, you can also use the installation verification tools to verify your installation. See Using the installation verification tools with WebSphere Process Server, version 6.0.1 for more information.

Creating a profile after installation

You can also use the response file to silently create a deployment manager profile after initial process server installation. To edit and use the appropriate response file for creating a profile, perform the following procedure:
  1. Copy the responsefile.pcaw.wps.dmgrProfile.txt file from the install_root/bin/ProfileCreator_wbi directory on Linux and UNIX platforms or install_root\bin\ProfileCreator_wbi on Windows platforms to a place that you can easily identify on your machine and save it with a new name such as my_options_file.txt.
  2. Edit the file to customize the values for your installation. Review the explanatory text in the response file for detailed explanations of each option. Example response files exist in Example responsefile.pcaw.wps.dmgrProfile.txt files.
  3. Save the file.
  4. Start profile creation with one of the following commands, as appropriate for your operating system.
    Note: If you have saved your response file in a directory other than install_root/bin/ProfileCreator_wbi on Linux or UNIX platforms or install_root\bin\ProfileCreator_wbi on Windows platforms, you must fully qualify the path name of the commands shown below. These examples assume that the response file is in one of these directories, as appropriate for the operating system.
    • Icon indicating AIX platforms On AIX platforms: ./pcatAIX.bin -options my_options_file.txt -silent
    • Icon indicating HP-UX platforms On HP-UX platforms: ./pcatHPUX.bin -options my_options_file.txt -silent
    • Icon indicating Linux platforms On Linux platforms: ./pcatLinux.bin -options my_options_file.txt -silent
    • Icon indicating Linux platforms On Linux platforms: Power platforms: ./pcatLinuxPPC.bin -options my_options_file.txt -silent
    • Icon indicating Solaris platforms On Solaris platforms: ./pcatSolaris.bin -options my_options_file.txt -silent
    • Icon indicating Windows platforms On Windows platforms: pcatWindows.exe -options my_options_file.txt -silent
  5. Examine the logs for success. Also refer to Recovering from profile creation or augmentation failure for troubleshooting tips if the profile did not create successfully.

Logging

See Log files for more information.

Naming considerations

Refer to Naming considerations for profiles, nodes, hosts, and cells for information.

Example responsefile.pcaw.wps.dmgrProfile.txt files

This section contains example response files for WebSphere Process Server, version 6.0.0 and WebSphere Process Server, version 6.0.1. Make sure to use the sample file that matches your version of WebSphere Process Server.

Example responsefile.pcaw.wps.dmgrProfile.txt file for WebSphere Process Server, version 6.0.0

Icon indicating 6.0.0 content only The response file provided with WebSphere Process Server, version 6.0.0, before modification, will be similar to the following:

################################################################################
#
# Licensed Material - Property of IBM
# 5724-L01
# (C) Copyright IBM Corporation 2005. All Rights Reserved.
# US Government Users Restricted Rights- Use, duplication or disclosure
# restricted by GSA ADP Schedule Contract with IBM Corp.
#
################################################################################
################################################################################
#
# Response file for Websphere Server 6.0 dmgr profile creation
#
# This options file is located in the CD_ROOT\WBI\ directory and in the
# install_root\bin\ProfileCreator_wbi directory. 
#
# To use the options file under CD_ROOT\WBI\ directory, follow the instructions
# in CD_ROOT\WBI\responsefile.wps.txt. The WebSphere Process Server 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_wbi for silent 
# profile creation, you must change various values in the file and use the 
# following command line arguments:
# 
#    -options "responsefile.pcaw.wps.dmgrProfile.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="Dmgr01"
################################################################################
# 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="<WBI_HOME>\profiles\<PROFILE_NAME>"
#
-P installLocation="C:\Program Files\IBM\WebSphere\ProcServer\profiles\Dmgr01"
################################################################################
# 
# Node name
#
# Please select the node name for the Process 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 Process 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 Process 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 numbers 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 Process 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 Process Server on Windows.
# Valid values are "automatic", "manual", and "disabled".
#
-W winservicepanelInstallWizardBean.startupType="manual"
################################################################################
#
# Service Component Architecture Configuration
#
# The following entries are used to create a Service Component Architecture
# configuration.  Set doConfigureSCACheckList="true" if you want
# to configure a Service Component Architecture.  If you do not want a 
# Service Component Architecture leave the value as "".  
# If you set the value to "true" then the rest of the parameters must also be filled 
# out.
#
-W wbiSCAConfigInputPanelBeanId.doConfigureSCACheckList=""
################################################################################
# If you chose to create a Service Component Architecture configuration above
# then specify the userid for that configuration.  If not then comment out
# this line.
#
-W wbiSCAConfigInputPanelBeanId.userId="YOUR_USER_ID_SCA"
################################################################################
# If you chose to create a Service Component Architecture configuration above
# then specify the password for that configuration and confirm that password. 
# If not then comment out these lines.
#
-W wbiSCAConfigInputPanelBeanId.password="YOUR_PASSWORD_SCA"
-W wbiSCAConfigInputPanelBeanId.passwordConfirmation="YOUR_PASSWORD_SCA"
################################################################################
#
# Configure Database Authentication
#
# Various WebSphere Process Server components use a database connection. 
# Choose a database type and enter the database configuration information 
# based on that type.
#
################################################################################
# Create new or use existing database
# 
# You can choose to use an existing database for WebSphere Process Server or
# you can create a new database. To use an existing database, set the following 
# property to "existing". To create a new database set the following property
# to "create".
#
-W wbiCommonDBConfigPanel.radioButtons="create"
#-W wbiCommonDBConfigPanel.radioButtons="existing"
################################################################################
# Database type
# 
# Choose the type of database you want to use/create for WebSphere Process
# Server. The supported database types are as follows: DB2 UDB,
# DB2 CLI, Informix, MSSQL Server Embedded, MSSQL Server Data Direct, 
# Oracle OCI, and Oracle Thin. To select a particular database type, 
# uncomment/comment the appropriate lines. 
# 
# NOTE:  DB2UDBOS390_V7_1, DB2UDBOS390_V8_1, ORACLE_OCI, ORACLE_THIN
#        databases are only supported for when using an existing database.
#        DO NOT select these databases if you choose to create a new database.
#
-W wbiCommonDBConfigPanel.DBProductListDmgr="DB2_Universal"
#-W wbiCommonDBConfigPanel.DBProductListDmgr="DB2UDBOS390_V7_1"
#-W wbiCommonDBConfigPanel.DBProductListDmgr="DB2UDBOS390_V8_1"
#-W wbiCommonDBConfigPanel.DBProductListDmgr="DB2_CLI"
#-W wbiCommonDBConfigPanel.DBProductListDmgr="INFORMIX"
#-W wbiCommonDBConfigPanel.DBProductListDmgr="MSSQLSERVER_Embedded"
#-W wbiCommonDBConfigPanel.DBProductListDmgr="MSSQLSERVER_DataDirect"
#-W wbiCommonDBConfigPanel.DBProductListDmgr="ORACLE_OCI"
#-W wbiCommonDBConfigPanel.DBProductListDmgr="ORACLE_THIN"
################################################################################
# Database name
# 
# If you chose to use an existing database, set the following property to the
# name of the existing database. Otherwise, specify a name for the new database.
#
-W wbiCommonDBConfigPanel.DBNameValue="WPRCSDB"
################################################################################
# Location of database server (database product installation root)
# 
# If you chose to create a new database, this property is required unless you
# also chose CLOUDSCAPE for the database type. The database server location is 
# the installation root for the database product (e.g. C:\SQLLIB).
# 
-W wbiAdditionalDBConfigPanel.DBServerLocation=""
################################################################################
# Database User ID (to authenticate with the database)
# 
# This property is required for all database types except CloudScape.
# 
-W wbiAdditionalDBConfigPanel.DBUserID=""
################################################################################
# Database password (to authenticate with the database)
# 
# This property is required for all database types except CloudScape. If you
# selected a database type other than CloudScape, enter the database password
# and confirm it by entering it again for DBPassWordConf.
#
-W wbiAdditionalDBConfigPanel.DBPassWord=""
-W wbiAdditionalDBConfigPanel.DBPassWordConf=""
################################################################################
# Location of JDBC driver classpath files
#
# This property is required for all database types except CLOUDSCAPE and 
# MSSQLSERVER_Embedded. Unless you selected one of these database types
# set the following property to a specific directory, as directed below, 
# depending on the database type.
#
# DB2_Universal - specify a directory that contains the following files: 
# db2jcc.jar and db2jcc_license_cu.jar or db2jcc_license_cisuz.jar.
# These files should be located in the follow directory:
#  
#      "<WBI_HOME>\universalDriver_wbi\lib"
#  
#  So, if using DB2_Universal, an acceptable JDBC classpath might be
#  -W wbiAdditionalDBConfigPanel.DBjdbc="C:\Program Files\IBM\WebSphere\universalDriver_wbi\lib"
#
# DB2_Universal OS/390 V7.1 or DB2_Universal OS/390 V8.1  - specify a directory 
# that contains the following files: 
#  db2jcc.jar,  db2jcc_license_cisuz.jar
#
# DB2_CLI - specify a directory that contains db2java.zip.
#
# INFORMIX - specify a directory that contains the following files: 
#  ifxjdbc.jar, ifxjdbcx.jar
#
# MSSQLSERVER_DataDirect - specify a directory that contains the following files:
#  sqlserver.jar, base.jar, util.jar
#  Also make sure the following file is available in the following location 
#  relative to the specified directory:  ../spy/spy.jar 
#
# ORACLE_OCI - specify a directory that contains classes12.zip.
#
# ORACLE_THIN - specify a directory that contains ojdbc14.jar.
#
# -W wbiAdditionalDBConfigPanel.DBjdbc=""
################################################################################
# Database host name
#
# This property is required for all database types except CLOUDSCAPE and 
# DB2 CLI. If you chose to use an existing database and the database is located 
# on a remote database server, specify the hostname for the remote server.
# Otherwise, specify "localhost".  If the database type is DB2_Universal OS/390 V7.1 
# or DB2_Universal OS/390 V8.1 specify instead the value for "DBHostNameOS390" below.
#
-W wbiAdditionalDBConfigPanel.DBHostName="localhost"
# -W wbiAdditionalDBConfigPanel.DBHostNameOS390=""
################################################################################
#
# Database server port
#
# This property is required for all database types except CLOUDSCAPE and 
# DB2 CLI. Unless you selected one of these databases, set the following 
# property to the appropriate server port for the selected database.
#
-W wbiAdditionalDBConfigPanel.DBPort=""
################################################################################
# Database storage group name (DB2_Universal OS/390 V7.1 or DB2_Universal OS/390 V8.1)
#
# This property is required for DB2_Universal OS/390 V7.1 or DB2_Universal OS/390 V8.1
#
# -W wbiAdditionalDBConfigPanel.DBStorageName=""
################################################################################
# Database server connection location name (DB2_Universal OS/390 V7.1 or DB2_Universal OS/390 V8.1)
#
# This property is required for DB2_Universal OS/390 V7.1 or DB2_Universal OS/390 V8.1
#
# -W wbiAdditionalDBConfigPanel.DBServerConnection=""
################################################################################
# Database instance name (Informix)
#
# This property is required for INFORMIX and should always start with "ol_"
#
# -W wbiAdditionalDBConfigPanel.DBInstance=""
################################################################################
# Profile type
#
# This must be set to "dmgr" for installing a deployment manager profile.
# Do not change this!
#
-W wbiCreateProfileTypeSelectionPanelBeanId.selection="dmgr"

Example responsefile.pcaw.wps.dmgrProfile.txt file for WebSphere Process Server, version 6.0.1

Icon indicating 6.0.1 content only The response file provided with WebSphere Process Server, version 6.0.1, before modification, will be similar to the following:

################################################################################
#
# Licensed Material - Property of IBM
# 5724-L01
# (C) Copyright IBM Corporation 2005. All Rights Reserved.
# US Government Users Restricted Rights- Use, duplication or disclosure
# restricted by GSA ADP Schedule Contract with IBM Corp.
#
################################################################################

################################################################################
#
# Response file for Websphere Server 6.0 dmgr profile creation
#
# This options file is located in the CD_ROOT\WBI\ directory and in the
# install_root\bin\ProfileCreator_wbi directory. 
#
# To use the options file under CD_ROOT\WBI\ directory, follow the instructions
# in CD_ROOT\WBI\responsefile.wps.txt. The WebSphere Process Server 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_wbi for silent 
# profile creation, you must change various values in the file and use the 
# following command line arguments:
# 
#    -options "responsefile.pcaw.wps.dmgrProfile.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="Dmgr01"

################################################################################
# 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="<WBI_HOME>\profiles\<PROFILE_NAME>"
#
# NOTE: The Windows operating system limits the length of a fully qualified path to
#       256 characters. A long pathname for the profile root directory makes it more 
#       likely that this limit will be exceeded when files are created during normal
#       product use. IBM recommends that you keep the pathname of the profile root
#       directory as short as possible.

-P installLocation="C:\Program Files\IBM\WebSphere\ProcServer\profiles\Dmgr01"


################################################################################
# 
# Node name
#
# Please select the node name for the Process Server. Node name under one cell
# has to be unique. 
#
# Replace YOUR_NODE_NAME with the actual node name. 
#
# Note: The Windows operating system limits the length of a fully qualified path 
#       to 256 characters. A long node name make it more likely that this limit
#       will be exceeded when files are created during normal product use. IBM 
#       recommends that you specify a maximum of eight characters for this name.

-W nodehostandcellnamepanelInstallWizardBean.nodeName="YOUR_NODE_NAME"

################################################################################
#
# Host name
#
# Specify the host name for the Process 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.
# 
# Note: The Windows operating system limits the length of a fully qualified path 
#       to 256 characters. A long host name make it more likely that this limit
#       will be exceeded when files are created during normal product use. IBM 
#       recommends that you specify a maximum of eight characters for this name.

-W nodehostandcellnamepanelInstallWizardBean.hostName="YOUR_HOST_NAME"

################################################################################
#
# Cell name
#
# Specify the cell name for the Process 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. 
#
# Note: The Windows operating system limits the length of a fully qualified path 
#       to 256 characters. A long cell name make it more likely that this limit
#       will be exceeded when files are created during normal product use. IBM 
#       recommends that you specify a maximum of eight characters for this 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 values will be used if they are unique, but a better guess at unique values
# will be used if the values are deemed to already be in use.
# Port numbers 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 Process 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 Process Server on Windows.
# Valid values are "automatic", "manual", and "disabled".
#
-W winservicepanelInstallWizardBean.startupType="manual"


################################################################################
#
# Service Component Architecture Configuration
#
# The following entries are used to create a Service Component Architecture
# configuration.  Set doConfigureSCACheckList="true" if you want
# to configure a Service Component Architecture.  If you do not want a 
# Service Component Architecture leave the value as "".  
# If you set the value to "true" then the rest of the parameters must also be filled 
# out.
#
-W wbiSCAConfigInputPanelBeanId.doConfigureSCACheckList=""


################################################################################
# If you chose to create a Service Component Architecture configuration above
# then specify the userid for that configuration.  If not then comment out
# this line.
#
-W wbiSCAConfigInputPanelBeanId.userId="YOUR_USER_ID_SCA"


################################################################################
# If you chose to create a Service Component Architecture configuration above
# then specify the password for that configuration and confirm that password. 
# If not then comment out these lines.
#
-W wbiSCAConfigInputPanelBeanId.password="YOUR_PASSWORD_SCA"
-W wbiSCAConfigInputPanelBeanId.passwordConfirmation="YOUR_PASSWORD_SCA"


################################################################################
#
# Configure Database Authentication
#
# Various WebSphere Process Server components use a database connection. 
# Choose a database type and enter the database configuration information 
# based on that type.
#

################################################################################
# Create new or use existing database
# 
# You can choose to use an existing database for WebSphere Process Server or
# you can create a new database. To use an existing database, set the following 
# property to "existing". To create a new database set the following property
# to "create".
#
-W wbiCommonDBConfigPanel.radioButtons="create"
#-W wbiCommonDBConfigPanel.radioButtons="existing"


################################################################################
# Database type
# 
# Choose the type of database you want to use/create for WebSphere Process
# Server. The supported database types are as follows: DB2 UDB,
# DB2 CLI, Informix, MSSQL Server Embedded, MSSQL Server Data Direct, 
# Oracle OCI, and Oracle Thin. To select a particular database type, 
# uncomment/comment the appropriate lines. 
# 
# NOTE:  DB2UDBOS390_V7_1, DB2UDBOS390_V8_1, ORACLE_OCI, ORACLE_THIN
#        databases are only supported for when using an existing database.
#        DO NOT select these databases if you choose to create a new database.
#

-W wbiCommonDBConfigPanel.DBProductListDmgr="DB2_Universal"
#-W wbiCommonDBConfigPanel.DBProductListDmgr="DB2UDBOS390_V7_1"
#-W wbiCommonDBConfigPanel.DBProductListDmgr="DB2UDBOS390_V8_1"
#-W wbiCommonDBConfigPanel.DBProductListDmgr="DB2_CLI"
#-W wbiCommonDBConfigPanel.DBProductListDmgr="INFORMIX"
#-W wbiCommonDBConfigPanel.DBProductListDmgr="MSSQLSERVER_Embedded"
#-W wbiCommonDBConfigPanel.DBProductListDmgr="MSSQLSERVER_DataDirect"
#-W wbiCommonDBConfigPanel.DBProductListDmgr="ORACLE_OCI"
#-W wbiCommonDBConfigPanel.DBProductListDmgr="ORACLE_THIN"

################################################################################
# Database name
# 
# If you chose to use an existing database, set the following property to the
# name of the existing database. Otherwise, specify a name for the new database.
#
-W wbiCommonDBConfigPanel.DBNameValue="WPRCSDB"


################################################################################
# Location of database server (database product installation root)
# 
# If you chose to create a new database, this property is required unless you
# also chose CLOUDSCAPE for the database type. The database server location is 
# the installation root for the database product (e.g. C:\SQLLIB).
# 
-W wbiAdditionalDBConfigPanel.DBServerLocation=""


################################################################################
# Database User ID (to authenticate with the database)
# 
# This property is required for all database types except CloudScape.
# 
-W wbiAdditionalDBConfigPanel.DBUserID=""


################################################################################
# Database password (to authenticate with the database)
# 
# This property is required for all database types except CloudScape. If you
# selected a database type other than CloudScape, enter the database password
# and confirm it by entering it again for DBPassWordConf.
#
-W wbiAdditionalDBConfigPanel.DBPassWord=""
-W wbiAdditionalDBConfigPanel.DBPassWordConf=""


################################################################################
# Location of JDBC driver classpath files
#
# This property is required for all database types except CLOUDSCAPE and 
# MSSQLSERVER_Embedded. Unless you selected one of these database types
# set the following property to a specific directory, as directed below, 
# depending on the database type.
#
# DB2_Universal - specify a directory that contains the following files: 
# db2jcc.jar and db2jcc_license_cu.jar or db2jcc_license_cisuz.jar.
# These files should be located in the follow directory:
#  
#      "<WBI_HOME>\universalDriver_wbi\lib"
#  
#  So, if using DB2_Universal, an acceptable JDBC classpath might be
#  -W wbiAdditionalDBConfigPanel.DBjdbc="C:\Program Files\IBM\WebSphere\
# universalDriver_wbi\lib"
#
# DB2_Universal OS/390 V7.1 or DB2_Universal OS/390 V8.1  - specify a directory 
# that contains the following files: 
#  db2jcc.jar,  db2jcc_license_cisuz.jar
#
# DB2_CLI - specify a directory that contains db2java.zip.
#
# INFORMIX - specify a directory that contains the following files: 
#  ifxjdbc.jar, ifxjdbcx.jar
#
# MSSQLSERVER_DataDirect - specify a directory that contains the following files:
#  sqlserver.jar, base.jar, util.jar
#  Also make sure the following file is available in the following location 
#  relative to the specified directory:  ../spy/spy.jar 
#
# ORACLE_OCI - specify a directory that contains classes12.zip.
#
# ORACLE_THIN - specify a directory that contains ojdbc14.jar.
#
# -W wbiAdditionalDBConfigPanel.DBjdbc=""



################################################################################
# Database host name
#
# This property is required for all database types except CLOUDSCAPE and 
# DB2 CLI. If you chose to use an existing database and the database is located 
# on a remote database server, specify the hostname for the remote server.
# Otherwise, specify "localhost".  If the database type is DB2_Universal OS/390 V7.1 
# or DB2_Universal OS/390 V8.1 specify instead the value for "DBHostNameOS390" below.
#
-W wbiAdditionalDBConfigPanel.DBHostName="localhost"
# -W wbiAdditionalDBConfigPanel.DBHostNameOS390=""


################################################################################
#
# Database server port
#
# This property is required for all database types except CLOUDSCAPE and 
# DB2 CLI. Unless you selected one of these databases, set the following 
# property to the appropriate server port for the selected database.
#
-W wbiAdditionalDBConfigPanel.DBPort=""

################################################################################
# Database storage group name (DB2_Universal OS/390 V7.1 or DB2_Universal OS/390 V8.1)
#
# This property is required for DB2_Universal OS/390 V7.1 or DB2_Universal OS/390 V8.1
#
# -W wbiAdditionalDBConfigPanel.DBStorageName=""


################################################################################
# Database server connection location name (DB2_Universal OS/390 V7.1 or DB2_Universal
# OS/390 V8.1)
#
# This property is required for DB2_Universal OS/390 V7.1 or DB2_Universal OS/390 V8.1
#
# -W wbiAdditionalDBConfigPanel.DBServerConnection=""



################################################################################
# Database instance name (Informix)
#
# This property is required for INFORMIX and should always start with "ol_"
#
# -W wbiAdditionalDBConfigPanel.DBInstance=""



################################################################################
# Profile type
#
# This must be set to "dmgr" for installing a deployment manager profile.
# Do not change this!
#
-W wbiCreateProfileTypeSelectionPanelBeanId.selection="dmgr"
</WBI_HOME></node></cell></profile></PROFILE_NAME></WBI_HOME>

Terms of use |

Last updated: Thu Apr 27 15:20:06 2006

(c) Copyright IBM Corporation 2006.
This information center is powered by Eclipse technology (http://www.eclipse.org)