responsefile.pcaw.wps.managedProfile.txt 응답 파일을 사용하여 사용자 정의 프로파일을 자동으로 작성할 수 있습니다. 사용자 정의 프로파일을 Deployment Manager 셀에 연합해야 작동합니다. 관리 대상 노드가 되는 이 강한 종속성 때문에 프로파일을 종종 관리 프로파일이라고 합니다.
자동으로 설치할 때 설치 프로그램은 이 파일을 읽고 프로파일 작성 옵션 값을 판별합니다. 초기 설치 후에 이 응답 파일을 사용하여 사용자 정의 프로파일을 추가로 작성할 수도 있습니다. 기본값을 가진 응답 파일이 제공됩니다.
자동 설치에 관한 자세한 정보는 자동으로 제품 설치의 내용을 참조하십시오.
Deployment Manager가 실행 중이 아니거나 연합의 다음 설명에서 임의의 이유로 액세스 가능하지 않으면 이 값을 true로 설정하십시오.
Deployment Manager가 실행 중인 시스템으로 해석되는 값을 지정하십시오. 호스트 네이밍 고려사항은 프로파일, 노드, 호스트 및 셀의 네이밍 고려사항의 내용을 참조하십시오.
Deployment Manager SOAP 포트의 값을 지정하십시오. 올바른 값을 지정해야 합니다. 잘못된 값은 노드 연합을 방해하며 결국 INSTCONFFAILED 표시기에서 전체 장애가 발생합니다. Deployment Manager에 대한 기본 SOAP 포트는 8879입니다.
프로파일 작성 중 또는 작성 후에 노드를 연합합니까?
Deployment Manager가 실행 중이 아니거나 다른 이유로 사용할 수 없을 때 사용자 정의 노드를 연합하려고 시도하면, 프로파일 작성에 실패하고 결과 사용자 정의 프로파일을 사용할 수 없습니다. 그러면 프로파일 이름이 동일한 다른 사용자 정의 프로파일을 작성하기 전에 프로파일 저장소(기본적으로, install_root의 profiles 디렉토리. 여기서 install_root는 WebSphere Process Server 설치 디렉토리임) 외부로 이 사용자 정의 프로파일 디렉토리를 이동해야 합니다.
응답 파일 내에서 -silent 옵션을 사용하지 마십시오. 이 옵션을 사용하면 프로파일 작성에 실패할 수 있습니다.
다음 위치에서 예제 responsefile.pcaw.wps.managedProfile.txt 파일을 찾을 수 있습니다.
-W summaryPanel_InstallWizardBean.launchPCAW="true"
-W pctresponsefilelocationqueryactionInstallWizardBean.fileLocation= "/opt/IBM/WebSphere/MyOptionFiles/customProfile_1.txt"
install -options /tmp/WBI/myoptions.txt -silent
install.exe -options "C:\temp\WBI\myoptions.txt" -silent
WebSphere Process Server, 버전 6.0.1을 사용하는 경우,
설치 유효성 검증 도구를 사용하여 설치를 확인할 수도 있습니다.
자세한 정보는 WebSphere Process Server, 버전 6.0.1에서 설치 검증 도구 사용의 내용을 참조하십시오
로깅에 대한 정보는 로그 파일의 내용을 참조하십시오.
네이밍 고려사항에 대한 정보는 프로파일, 노드, 호스트 및 셀의 네이밍 고려사항의 내용을 참조하십시오.
물론 노드를 셀로 연합할 때까지 노드는 관리되지 않습니다.
다음의 응답 파일은 다수의 지정문 이름에서 custom 항목 대신에 managed 항목을 참조합니다. 그럼에도 불구하고, 이 응답 파일의 모든 지정문은 사용자 정의 프로파일의 정의에 도움이 됩니다.
수정 전에 WebSphere Process Server, 버전 6.0.0에서 제공된 응답 파일은 다음과 비슷합니다.
################################################################################ # # 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 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>" # -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. # -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. # -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> # # -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 numbers for each profile can be find 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_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 wbiCustomProfileDBConfigPanel.DBjdbc="" ################################################################################ # Profile type # # This must be set to "managed" for installing a custom profile. # Do not change this! # -W wbiCreateProfileTypeSelectionPanelBeanId.selection="managed"
수정 전에
WebSphere Process Server, 버전 6.0.1에서 제공된 응답 파일은 다음과 비슷합니다.
################################################################################ # # 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 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_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 wbiCustomProfileDBConfigPanel.DBjdbc="" ################################################################################ # Profile type # # This must be set to "managed" for installing a custom profile. # Do not change this! # -W wbiCreateProfileTypeSelectionPanelBeanId.selection="managed"
최종 갱신: 2006년 4월 13일
(c) Copyright IBM Corporation 2005, 2006.
이 Information Center는 Eclipse 기술을 기반으로 합니다. (http://www.eclipse.org 웹 사이트 참조)