WebSphere Process Server supplies example response files to use in silent profile creation. Use this example response file as a starting point to creating a WebSphere Process Server custom profile.
################################################################################ # # Licensed Material - Property of IBM # 5724-L01, 5724-182, 5655-N53,5655-R15 # (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 Process Server v6.0 custom 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.managedProfile.txt" -silent # ################################################################################ ################################################################################ # # Profile name # # Set the name for this custom profile. The profile name must be unique for this # WebSphere Application Server installation. # # -W profilenamepanelInstallWizardBean.profileName="Custom01" ################################################################################ # 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\Custom01" ################################################################################ # # Node name # # Please select the node name for the Process Server. Node name under one cell # has to be unique. # # If you plan to migrate a V5 deployment manager cell, the V5 managed nodes are also # migrated to the V6 cell. To incrementally migrate an individual V5 managed node # to V6, you must use the same node name for the V6 Process Server profile. # # 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 nodehostnamepanelInstallWizardBean.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 nodehostnamepanelInstallWizardBean.hostName="YOUR_HOST_NAME" ################################################################################ # # Cell name # # You should not Modify this, unless absolutely necessary # # The Wizard would set this to short local host name + "Node##Cell" by default. # # If you would like to override the resolved cell name value, uncomment the line and # replace YOUR_CELL_NAME with <YOUR_OWN_VALUE> # # 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 setnondmgrcellnameinglobalconstantsInstallWizardBean.value="YOUR_CELL_NAME" ################################################################################ # # Ports 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 # # If you specify true for the value of the -W pctfederationpanelInstallWizardBean.federateLater # directive, port numbers are assigned automatically when you federate the # node with the addNode command. The following port numbers do not apply. # -W pctmanagedprofileportspanelInstallWizardBean.BOOTSTRAP_ADDRESS="2809" -W pctmanagedprofileportspanelInstallWizardBean.SOAP_CONNECTOR_ADDRESS="8878" -W pctmanagedprofileportspanelInstallWizardBean.SAS_SSL_SERVERAUTH_LISTENER_ADDRESS="9901" -W pctmanagedprofileportspanelInstallWizardBean.CSIV2_SSL_SERVERAUTH_LISTENER_ADDRESS="9201" -W pctmanagedprofileportspanelInstallWizardBean.CSIV2_SSL_MUTUALAUTH_LISTENER_ADDRESS="9202" -W pctmanagedprofileportspanelInstallWizardBean.ORB_LISTENER_ADDRESS="9100" -W pctmanagedprofileportspanelInstallWizardBean.NODE_DISCOVERY_ADDRESS="7272" -W pctmanagedprofileportspanelInstallWizardBean.NODE_MULTICAST_DISCOVERY_ADDRESS="5000" -W pctmanagedprofileportspanelInstallWizardBean.NODE_IPV6_MULTICAST_DISCOVERY_ADDRESS="5001" -W pctmanagedprofileportspanelInstallWizardBean.DCS_UNICAST_ADDRESS="9353" ################################################################################ # # Federation # # A custom profile contains an empty node that must be federated to a deployment # manager to become a functional managed node. Identify a running deployment # manager that will administer the node or choose to federate the node later # using the addNode command. # # Set to "true" if you want to federate this custom node later using the addNode # command. You must federate this node later if the deployment manager : # - is not running. # - has security enabled. # - has the SOAP connector disabled # - has not already been augmented for WebSphere Process Server # # If you want to federate it now, set to "" and fill in the entries for the host # and port of the deployment manager. # -W pctfederationpanelInstallWizardBean.federateLater="" ################################################################################ # Specify the host name of the deployment manager for federation. # -W pctfederationpanelInstallWizardBean.hostname="YOUR_DEPLOYMENT_MANAGER_HOST_NAME" ################################################################################ # Specify the port number where the deployment manager (DMGR) is reachable on the # above host. The default port value is "8879". # -W pctfederationpanelInstallWizardBean.port="YOUR_DEPLOYMENT_MANAGER_PORT_NUMBER" ################################################################################ # Database type # # Select a database product that matches the database product used # during the profile creation/augmentation of the Deployment Manager that this # Managed node will be federated to.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. # -W wbiCustomProfileDBConfigPanel.DBProductList="DB2_Universal" #-W wbiCustomProfileDBConfigPanel.DBProductList="DB2UDBOS390_V7_1" #-W wbiCustomProfileDBConfigPanel.DBProductList="DB2UDBOS390_V8_1" #-W wbiCustomProfileDBConfigPanel.DBProductList="DB2_CLI" #-W wbiCustomProfileDBConfigPanel.DBProductList="INFORMIX" #-W wbiCustomProfileDBConfigPanel.DBProductList="MSSQLSERVER_Embedded" #-W wbiCustomProfileDBConfigPanel.DBProductList="MSSQLSERVER_DataDirect" #-W wbiCustomProfileDBConfigPanel.DBProductList="ORACLE_OCI" #-W wbiCustomProfileDBConfigPanel.DBProductList="ORACLE_THIN" ################################################################################ # 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 wbiCustomProfileDBConfigPanel.DBjdbc="C:\Program Files\IBM\WebSphere\universalDriver_wbi\lib" # # DB2 UDB for z/OS and OS/390 V7 or DB2 UDB for z/OS V8 - 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 wbiCustomProfileDBConfigPanel.DBjdbc="" ################################################################################ # Profile type # # This must be set to "managed" for installing a custom profile. # Do not change this! # -W wbiCreateProfileTypeSelectionPanelBeanId.selection="managed"
Last updated: Wed 01 Nov 2006 07:47:12
(c) Copyright IBM Corporation 2005, 2006.
This information center is powered by Eclipse technology (http://www.eclipse.org)