자동으로 독립형 서버 프로파일 작성

responsefile.pcaw.wps.standAloneProfile.txt 응답 파일을 사용하여 독립형 프로세스 서버 프로파일을 자동으로 작성할 수 있습니다.

자동으로 설치할 때 설치 프로그램은 이 파일을 읽고 프로파일 작성 옵션 값을 판별합니다. 초기 설치 후에 이 응답 파일을 사용하여 독립형 프로세스 서버 프로파일을 추가로 작성할 수도 있습니다. 기본값을 가진 응답 파일이 제공됩니다.

자동 설치에 관한 자세한 정보는 자동으로 제품 설치의 내용을 참조하십시오.

시작하기 전에

이 프로시저를 사용하기 전에 다음을 확인하십시오.
  • 독립형 서버 프로파일을 자동으로 작성하려고 하는지 확인하십시오. 대화식 인터페이스를 대신 사용하여 프로파일을 작성하려는 경우, 기타 프로파일 작성 프로시저에 대한 설명은 프로파일 마법사를 사용하여 프로파일 작성 및 기능 보강의 내용을 참조하십시오.
  • 원격 서버에서 WebSphere Process Server의 저장소를 찾으려는 경우 저장소를 작성한 후 이 프로시저를 시작하십시오. WebSphere Process Server 응답 파일의 옵션을 사용하여 로컬 서버에서 저장소를 작성하거나 원격 서버에서 기존 서버를 사용할 수 있습니다.
  • 새 프로파일을 작성할 수 있도록 디스크 및 임시 공간이 충분한지 확인하십시오. 필요한 최소 디스크 공간은 필수 디스크 공간의 내용을 참조하십시오.
  • WebSphere Process Server를 설치 중인 경우, 설치에 맞게 운영 체제를 준비했는지 확인하십시오. 지시사항은 설치를 위한 운영 체제 준비의 내용을 참조하십시오.
  • 글로벌 보안이 사용 가능한 WebSphere Application Server 또는 WebSphere Application Server Network Deployment 의 기존 설치에 WebSphere Process Server를 설치하는 경우, 글로벌 보안을 사용 불가능하게 한 후에 제품을 설치하십시오. WebSphere Process Server를 이미 설치했고 글로벌 보안을 사용 가능하게 한 경우, 이를 사용 불가능하게 한 후에 프로파일을 작성하십시오. 글로벌 보안 사용 가능 및 사용 불가능에 관한 정보는 http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/index.jsp의 WebSphere Application Server Network Deployment, 버전 6.0, Information Center를 참조하십시오.
  • Linux 또는 UNIX 시스템에서 루트 사용자로 Windows 시스템에서 관리자 그룹의 구성원으로 프로파일을 작성 중인지 확인하십시오.

응답 파일 내에서 -silent 옵션 사용하지 않기

응답 파일 내에서 -silent 옵션을 사용하지 마십시오. 이 옵션을 사용하면 프로파일 작성에 실패할 수 있습니다.

응답 파일 위치

다음 위치에서 예제 responsefile.pcaw.wps.standAloneProfile.txt 파일을 찾을 수 있습니다.

표 1. 응답 파일 위치
WebSphere Process Server CD 1 위치 설치 위치
WBI 디렉토리
  • Icon indicating Linux platforms Icon indicating UNIX platforms Linux 및 UNIX 플랫폼: install_root/bin/ProfileCreator_wbi 디렉토리
  • Icon indicating Windows platforms Windows 플랫폼: install_root\bin\ProfileCreator_wbi 디렉토리

설치 중에 독립형 서버 프로파일 작성

WebSphere Process Server 초기 설치 중 독립형 서버 프로파일을 작성하려면 다음을 수행하십시오.
  1. responsefile.pcaw.wps.standAloneProfile.txt 파일을 WebSphere Process Server CD 1WBI 디렉토리에서 시스템의 쉽게 식별할 수 있는 위치로 복사하고 새 이름(예: standaloneProfile_1.txt)으로 저장하십시오.
  2. 원하는 텍스트 파일 편집기로 대상 운영 체제에서 이 프로파일 응답 파일을 편집하고, 시스템의 매개변수를 사용하여 사용자 정의하십시오. 응답 파일의 지시에 따라 적절한 값을 선택하십시오.
  3. 프로파일 마법사에 대해 응답 파일에 -silent 옵션이 존재하지 않는지 확인하십시오. 옵션이 존재하면 프로파일이 작성되지 않습니다.
  4. 파일을 저장하십시오.
  5. 제품 설치 응답 파일 responsefile.wps.txtWebSphere Process Server CD 1WBI 디렉토리에서 시스템의 쉽게 식별할 수 있는 위치로 복사하고 새 이름(예: myoptionsfile)으로 저장하십시오.
  6. 원하는 텍스트 파일 편집기로 대상 운영 체제에서 이 파일을 편집하고, 시스템의 매개변수를 사용하여 사용자 정의하십시오. 응답 파일의 지시에 따라 적절한 값을 선택하십시오. 샘플 응답 파일은 자동으로 제품 설치의 내용을 참조하십시오.
  7. responsefile.wps.txt 사본 끝에 -W summaryPanel_InstallWizardBean.launchPCAW 옵션 값을 true로 변경하십시오. 예를 들면, 다음과 같습니다.
    -W summaryPanel_InstallWizardBean.launchPCAW="true"
  8. -W pcawResponseFileLocationQueryAction_InstallWizardBean.fileLocation 옵션 값을 (수정된) 프로파일 응답 파일의 절대 파일 경로를 식별할 수 있도록 "" 안의 값을 변경하십시오. 예를 들면, 다음과 같습니다.
    -W pcawresponsefilelocationqueryaction_InstallWizardBean.fileLocation=
    "/opt/IBM/WebSphere/MyOptionFiles/standaloneProfile_1.txt"
  9. responsefile.wps.txt 사본에 변경사항을 저장하십시오.
  10. 다음 명령 중 하나를 사용하여 WebSphere Process Server를 설치하고 독립형 서버 프로파일을 작성하십시오. 이 명령은 responsefile.wps.txt 파일을 임시 디렉토리에 복사하고 파일을 사용자 정의하기 전에 myoptions.txt로 이름을 바꾸었다고 가정합니다.
    • Icon indicating Linux platforms Icon indicating UNIX platforms Linux 및 UNIX 플랫폼:
      install -options /tmp/WBI/myoptions.txt -silent
    • Icon indicating Windows platforms Windows 플랫폼:
      install.exe -options "C:\temp\WBI\myoptions.txt" -silent
WebSphere Process Server 로그 파일을 검사하여 설치를 확인하십시오. 파일의 마지막 행에 INSTCONFSUCCESS라는 단어가 포함된 경우, 사용자가 선택한 WebSphere Process Server 기능 및 WebSphere Application Server Network Deployment가 설치되었습니다. 로그 파일 위치는 다음과 같습니다.
  • Icon indicating Linux platforms Icon indicating UNIX platforms Linux 및 UNIX 플랫폼: install_root/logs/wbi/log.txt
  • Icon indicating Windows platforms Windows 플랫폼: install_root\logs\wbi\log.txt
여기서 install_root는 WebSphere Process Server 설치 위치를 나타냅니다. 이 로그 파일의 마지막 행에 INSTCONFSUCCESS 문자열이 포함된 경우, 설치에 성공한 것입니다. 기타 항목(예: INSTCONFPARTIALSUCCESS 또는 INSTCONFFAILED)이 파일 내 기타 행에서 또는 마지막 행에서 발생할 수 있지만 INSTCONFSUCCESS가 마지막 행에 포함되어 있으면 설치에 성공한 것입니다. 설치에 실패한 경우, 기타 로그 파일을 검사하여 이유를 판별하십시오. 설치 문제점 해결에 관한 팁은 로그 파일에 나열된 관련 로그 파일, 오류 메시지: 설치 및 프로파일 작성 및 기능 보강의 오류 메시지에 대한 설명을 참조하고 설치 문제점 해결의 내용을 체크아웃하십시오. 또한 프로파일이 성공적으로 작성되지 않은 경우 문제점 해결 팁을 보려면 프로파일 작성 또는 기능 보강 장애 복구의 내용을 참조하십시오.

Icon indicating 6.0.1 content only WebSphere Process Server, 버전 6.0.1을 사용하는 경우, 설치 유효성 검증 도구를 사용하여 설치를 확인할 수도 있습니다. 자세한 정보는 WebSphere Process Server, 버전 6.0.1에서 설치 검증 도구 사용의 내용을 참조하십시오

설치 후 독립형 서버 프로파일 작성

초기 프로세스 서버 설치 후에 응답 파일을 사용하여 독립형 서버 프로파일을 자동으로 작성할 수도 있습니다. 이렇게 하려면 다음을 수행하십시오.
  1. responsefile.pcaw.wps.standAloneProfile.txt 파일을 Linux 및 UNIX 플랫폼에서는 install_root/bin/ProfileCreator_wbi 디렉토리에서 또는 Windows 플랫폼에서는 install_root\bin\ProfileCreator_wbi에서 시스템의 쉽게 식별할 수 있는 위치로 복사하고 새 이름(예: my_options_file.txt)으로 저장하십시오.
  2. 설치에 대한 값을 사용자 정의하기 위해 파일을 편집하십시오. 각 옵션에 대한 자세한 설명은 응답 파일의 설명 텍스트를 검토하십시오. 예 응답 파일은 responsefile.pcaw.wps.standAloneProfile.txt 파일 예에 있습니다.
  3. 파일을 저장하십시오.
  4. 운영 체제에 맞게 다음 명령 중 하나를 사용하여 프로파일 작성을 시작하십시오.
    주: Linux 또는 UNIX 플랫폼에서는 install_root/bin/ProfileCreator_wbi 이외의 다른 디렉토리에 또는 Windows 플랫폼에서는 install_root\bin\ ProfileCreator_wbi 이외의 다른 디렉토리에 응답 파일을 저장한 경우, 아래 표시된 명령의 완전한 경로 이름을 지정해야 합니다. 이 예에서는 운영 체제에 맞게 응답 파일이 이 디렉토리 중 하나에 있다고 가정합니다.
    • Icon indicating AIX platforms AIX 플랫폼: ./pcatAIX.bin -options my_options_file.txt -silent
    • Icon indicating HP-UX platforms HP-UX 플랫폼: ./pcatHPUX.bin -options my_options_file.txt -silent
    • Icon indicating Linux platforms Linux 플랫폼: ./pcatLinux.bin -options my_options_file.txt -silent
    • Icon indicating Linux platforms Linux 플랫폼: Power 플랫폼: ./pcatLinuxPPC.bin -options my_options_file.txt -silent
    • Icon indicating Solaris platforms Solaris 플랫폼: ./pcatSolaris.bin -options my_options_file.txt -silent
    • Icon indicating Windows platforms Windows 플랫폼: pcatWindows.exe -options my_options_file.txt -silent
  5. 로그를 검사하여 성공을 확인하십시오. 또한 프로파일이 성공적으로 작성되지 않은 경우 문제점 해결 팁을 보려면 프로파일 작성 또는 기능 보강 장애 복구의 내용을 참조하십시오.

로깅

로깅에 대한 정보는 로그 파일의 내용을 참조하십시오.

네이밍 고려사항

네이밍 고려사항에 대한 정보는 프로파일, 노드, 호스트 및 셀의 네이밍 고려사항의 내용을 참조하십시오.

responsefile.pcaw.wps.standAloneProfile.txt 파일 예

이 절에는 WebSphere Process Server, 버전 6.0.0 및 WebSphere Process Server, 버전 6.0.1에 대한 예제 응답 파일이 들어 있습니다. WebSphere Process Server의 버전과 일치하는 샘플 파일을 사용하는지 확인하십시오. 수정 전, 제품에서 제공하는 파일은 다음 중 하나와 비슷합니다.

WebSphere Process Server, 버전 6.0.0에 대한 pcaw.wps.standAloneProfile.txt 파일 예

수정 전에 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 stand alone 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.standAloneProfile.txt" -silent
#
################################################################################
################################################################################
# 
# Profile name
#
# Set the profile name for installing a stand alone profile. The profile 
# name must be unique for this WebSphere Application Server installation.  
#
-W profilenamepanelInstallWizardBean.profileName="ProcSrv01"
################################################################################
# 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\ProcSrv01"
################################################################################
# 
# 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"
################################################################################
# 
# 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 pctdefaultprofileportspanelInstallWizardBean.WC_defaulthost="9080"
-W pctdefaultprofileportspanelInstallWizardBean.WC_adminhost="9060"
-W pctdefaultprofileportspanelInstallWizardBean.WC_defaulthost_secure="9443"
-W pctdefaultprofileportspanelInstallWizardBean.WC_adminhost_secure="9043"
-W pctdefaultprofileportspanelInstallWizardBean.BOOTSTRAP_ADDRESS="2809"
-W pctdefaultprofileportspanelInstallWizardBean.SOAP_CONNECTOR_ADDRESS="8880"
-W pctdefaultprofileportspanelInstallWizardBean.SAS_SSL_SERVERAUTH_LISTENER_ADDRESS="9401"
-W pctdefaultprofileportspanelInstallWizardBean.CSIV2_SSL_SERVERAUTH_LISTENER_ADDRESS="9403"
-W pctdefaultprofileportspanelInstallWizardBean.CSIV2_SSL_MUTUALAUTH_LISTENER_ADDRESS="9402"
-W pctdefaultprofileportspanelInstallWizardBean.ORB_LISTENER_ADDRESS="9100"
-W pctdefaultprofileportspanelInstallWizardBean.DCS_UNICAST_ADDRESS="9353"
-W pctdefaultprofileportspanelInstallWizardBean.SIB_ENDPOINT_ADDRESS="7276"
-W pctdefaultprofileportspanelInstallWizardBean.SIB_ENDPOINT_SECURE_ADDRESS="7286"
-W pctdefaultprofileportspanelInstallWizardBean.SIB_MQ_ENDPOINT_ADDRESS="5558"
-W pctdefaultprofileportspanelInstallWizardBean.SIB_MQ_ENDPOINT_SECURE_ADDRESS="5578"
################################################################################
#
# 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"
################################################################################
#
# Common Event Infrastructure Configuration
#
# The following entries are used to create a sample Common Event Infrastructure
# configuration.  Uncomment the appropriate lines & fill in the values.
################################################################################
# Specify the userid for CEI sample configuration to create a sample
# Common Event infrastructure.  
#
-W wbiCEIConfigInputPanelBeanId.userId="YOUR_USER_ID_CEI"
################################################################################
# To create the sample Common Event Infrastructure configuration above
# specify the password for that sample configuration and confirm that password. 
# 
-W wbiCEIConfigInputPanelBeanId.password="YOUR_PASSWORD_CEI"
-W wbiCEIConfigInputPanelBeanId.passwordConfirmation="YOUR_PASSWORD_CEI"
################################################################################
# To create the sample Common Event Infrastructure configuration above
# specify the server name for that sample configuration.  By default, the
# server that is created for a standalone node is named "server1".
#
-W wbiCEIConfigInputPanelBeanId.serverName="server1"
################################################################################
# Database type
# 
# Choose the type of database you want to use/create for Common Event Infrastructure.
# The supported database types are as follows: CloudScape, DB2 UDB, Oracle.
# To select a particular database type, uncomment the appropriate line. 
#
-W wbiCEIConfigInputPanelBeanId.database="CLOUDSCAPE_V51_1"
# -W wbiCEIConfigInputPanelBeanId.database="DB2UDBNT_V8_1"
# -W wbiCEIConfigInputPanelBeanId.database="DB2UDBNT_V82_1"
# -W wbiCEIConfigInputPanelBeanId.database="ORACLE_V9_1"
# -W wbiCEIConfigInputPanelBeanId.database="ORACLE_V10_1"
# -W wbiCEIConfigInputPanelBeanId.database="DB2UDBOS390_V7_1"
# -W wbiCEIConfigInputPanelBeanId.database="DB2UDBOS390_V8_1"
################################################################################
# The following entries are used only if you selected DB2 as your preferred
# database type.
################################################################################
# Create database choice
#
# If you want to create a new database for Common Event Infrastructure then
# set the value as "yes". If you want to generate scripts to create new database
# then set the value as "no".
#
# -W wbiCEIDB2ConfigInfoBean.createDatabaseChoice="yes"
################################################################################
# Database Name
#
# The database name. By default the database is named "event". Database name
# cannot be more than 8 characters long.
#
# -W wbiCEIDB2ConfigInfoBean.databaseName="event"
################################################################################
# User ID
#
# User ID to authenticate with the database
#
# -W wbiCEIDB2ConfigInfoBean.userId="YOUR_USER_ID_DB"
################################################################################
# Password
#
# Specify the password for database authentication. Later confirm it.
#
# -W wbiCEIDB2ConfigInfoBean.password="YOUR_PASSWORD_DB"
# -W wbiCEIDB2ConfigInfoBean.passwordConfirmation="YOUR_PASSWORD_DB"
################################################################################
# JDBC Driver Classpath
#
# Specify a directory that contains the following files: 
#  db2jcc.jar, db2jcc_license_cu.jar, 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 wbiCEIDB2DriverInfo.driverClassPath="C:\Program Files\IBM\WebSphere\universalDriver_wbi\lib"
#
#
# -W wbiCEIDB2DriverInfo.driverClassPath=""
################################################################################
# Driver Type
#
# Specify the driver JDBC type. Valid values are "2" or "4".
#
# -W wbiCEIDB2DriverInfo.driverType="4"
################################################################################
# Database Server Name
#
# Specify the database server name only if your driver type selection was "4".
#
# -W wbiCEIDB2DriverInfo.databaseServerName="localhost"
################################################################################
# Server Port
#
# Specify the server port only if your driver type selection was "4".
#
# -W wbiCEIDB2DriverInfo.serverPort="50000"
################################################################################
# Database Node Name
# 
# Specify the database node name only if the DB2 server is remote.
#
# -W wbiCEIDB2DriverInfo.dbNodeName=""
################################################################################
# The following entries are used only if you selected Oracle V9.1 or Oracle V10.1
# as your preferred database type.
################################################################################
# Create database choice
#
# If you want to create a new database for Common Event Infrastructure then
# set the value as "yes". If you want to generate scripts to create new database
# then set the value as "no".
#
# -W wbiCEIOracleConfigInfoBean.createDatabaseChoice="yes"
################################################################################
# Database Name
#
# The database name. Database name cannot be more than 8 characters long.
#
# -W wbiCEIOracleConfigInfoBean.databaseName=""
################################################################################
# User ID
#
# User ID to create in the database.
#
# -W wbiCEIOracleConfigInfoBean.userId="YOUR_DB_USER_ID"
################################################################################
# Password
#
# Specify the password for the created user ID. Later confirm it.
#
# -W wbiCEIOracleConfigInfoBean.password="YOUR_DB_USER_PASSWORD"
# -W wbiCEIOracleConfigInfoBean.passwordConfirmation="YOUR_DB_USER_PASSWORD"
################################################################################
# User ID
#
# User ID with SYSDBA authority.
#
# -W wbiCEIOracleDriverInfo.userId="USER_ID_AUTH_SYSDBA"
################################################################################
# Password
#
# Specify the password for the user ID with SYSDBA authority. Later confirm it.
#
# -W wbiCEIOracleDriverInfo.password="USER_PASSWORD_AUTH_SYSDBA"
# -W wbiCEIOracleDriverInfo.passwordConfirmation="USER_PASSWORD_AUTH_SYSDBA"
################################################################################
# JDBC Driver Classpath
#
# Specify a directory that contains the following files: 
#
#  ORACLE_OCI8 - specify a directory that contains classes12.zip.
#
#  ORACLE_THIN - specify a directory that contains ojdbc14.jar.
# -W wbiCEIOracleDriverInfo.driverClassPath="<value>"
################################################################################
# Driver Type
#
# Specify the driver JDBC type only if you did not opt to create a new database. 
# Valid values are "oci" or "thin".
#
# -W wbiCEIOracleDriverInfo.driverType="oci"
################################################################################
# Database Server Name
#
# Specify the database server name only if your driver type selection was "thin".
#
# -W wbiCEIOracleDriverInfo.databaseServerName="localhost"
################################################################################
# Server Port
#
# Specify the server port only if your driver type selection was "thin".
#
# -W wbiCEIOracleDriverInfo.serverPort="1521"
################################################################################
#
# Business Process Choreographer Configuration
#
# The following entries are used to create a sample Business Process Choreographer
# configuration.  Set doConfigureSampleBPContainerCheckList="yes" if you want
# to configure a sample.  If you do not want a sample leave the value as "".  
# If you set the value to "yes" then the rest of the parameters must also be filled 
# out.
#
-W bpcConfigInputPanelBeanId.doConfigureSampleBPContainerCheckList=""
################################################################################
# If you chose to create a sample Business Process Choreographer configuration
# above then specify the userid for that sample configuration.  If not then 
# comment out this line.
#
-W bpcConfigInputPanelBeanId.userId="YOUR_USER_ID_BPC"
################################################################################
# If you chose to create a sample Business Process Choreographer configuration
# above then specify the password for that sample configuration and confirm that 
# password.  If not then comment out these lines.
#
-W bpcConfigInputPanelBeanId.password="YOUR_PASSWORD_BPC"
-W bpcConfigInputPanelBeanId.passwordConfirmation="YOUR_PASSWORD_BPC"
################################################################################
# If you chose to create a sample Business Process Choreographer configuration
# above then specify the security role for the business process system administrator.
# This is the security role used by the Business Process Choreographer to run a
# business process.  Below is an example of an LDAP security role.  Comment out 
# this line if a sample Business Process Choreographer configuration is not being 
# created.
#
-W bpcConfigInputPanelBeanId.securityRole="YOUR_SECURITY_ROLE_BPC"
################################################################################
#
# Application Scheduler configuration
#
# Application Scheduler is used to schedule migration application group events.
# If you choose to configure Application Scheduler, set the following property
# to "yes". Otherwise, leave it blank "".
#
-W wbiAppSchedulerConfigInputPanel.doAppSchedulerConfig=""
#-W wbiAppSchedulerConfigInputPanel.doAppSchedulerConfig="yes"
################################################################################
#
# Indicate the application server name on this node if you chose to configure
# it for Application Scheduler use. Usually, for a stand-alone profile the 
# server name is "server1".
#
-W wbiAppSchedulerConfigInputPanel.appSchedulerServer="server1"
################################################################################
#
# 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: CloudScape, 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.DBProductList="CLOUDSCAPE"
#-W wbiCommonDBConfigPanel.DBProductList="DB2_Universal"
#-W wbiCommonDBConfigPanel.DBProductList="DB2UDBOS390_V7_1"
#-W wbiCommonDBConfigPanel.DBProductList="DB2UDBOS390_V8_1"
#-W wbiCommonDBConfigPanel.DBProductList="DB2_CLI"
#-W wbiCommonDBConfigPanel.DBProductList="INFORMIX"
#-W wbiCommonDBConfigPanel.DBProductList="MSSQLSERVER_Embedded"
#-W wbiCommonDBConfigPanel.DBProductList="MSSQLSERVER_DataDirect"
#-W wbiCommonDBConfigPanel.DBProductList="ORACLE_OCI"
#-W wbiCommonDBConfigPanel.DBProductList="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_cu.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 "default" for installing a stand alone profile
# Do not change this!
#
-W wbiCreateProfileTypeSelectionPanelBeanId.selection="default"

WebSphere Process Server, 버전 6.0.1에 대한 pcaw.wps.standAloneProfile.txt 파일 예

Icon indicating 6.0.1 content only 수정 전에 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 stand alone 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.standAloneProfile.txt" -silent
#
################################################################################


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

################################################################################
# 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\ProcSrv01"


################################################################################
# 
# 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"


################################################################################
# 
# 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 pctdefaultprofileportspanelInstallWizardBean.WC_defaulthost="9080"
-W pctdefaultprofileportspanelInstallWizardBean.WC_adminhost="9060"
-W pctdefaultprofileportspanelInstallWizardBean.WC_defaulthost_secure="9443"
-W pctdefaultprofileportspanelInstallWizardBean.WC_adminhost_secure="9043"
-W pctdefaultprofileportspanelInstallWizardBean.BOOTSTRAP_ADDRESS="2809"
-W pctdefaultprofileportspanelInstallWizardBean.SOAP_CONNECTOR_ADDRESS="8880"
-W pctdefaultprofileportspanelInstallWizardBean.SAS_SSL_SERVERAUTH_LISTENER_ADDRESS="9401"
-W pctdefaultprofileportspanelInstallWizardBean.CSIV2_SSL_SERVERAUTH_LISTENER_ADDRESS="9403"
-W pctdefaultprofileportspanelInstallWizardBean.CSIV2_SSL_MUTUALAUTH_LISTENER_ADDRESS="9402"
-W pctdefaultprofileportspanelInstallWizardBean.ORB_LISTENER_ADDRESS="9100"
-W pctdefaultprofileportspanelInstallWizardBean.DCS_UNICAST_ADDRESS="9353"
-W pctdefaultprofileportspanelInstallWizardBean.SIB_ENDPOINT_ADDRESS="7276"
-W pctdefaultprofileportspanelInstallWizardBean.SIB_ENDPOINT_SECURE_ADDRESS="7286"
-W pctdefaultprofileportspanelInstallWizardBean.SIB_MQ_ENDPOINT_ADDRESS="5558"
-W pctdefaultprofileportspanelInstallWizardBean.SIB_MQ_ENDPOINT_SECURE_ADDRESS="5578"


################################################################################
#
# 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"


################################################################################
#
# Common Event Infrastruction Configuration
#
# The following entries are used to create a sample Common Event Infrastructure
# configuration.  Uncomment the appropriate lines & fill in the values.

################################################################################
# Specify the userid for CEI sample configuration to create a sample
# Common Event infrastructure.  
#
-W wbiCEIConfigInputPanelBeanId.userId="YOUR_USER_ID_CEI"


################################################################################
# To create the sample Common Event Infrastructure configuration above
# specify the password for that sample configuration and confirm that password. 
# 
-W wbiCEIConfigInputPanelBeanId.password="YOUR_PASSWORD_CEI"
-W wbiCEIConfigInputPanelBeanId.passwordConfirmation="YOUR_PASSWORD_CEI"


################################################################################
# To create the sample Common Event Infrastructure configuration above,
# a server name is needed for that sample configuration.  By default, the server 
# that is created for a standalone node is named "server1". This value should not
# be changed.
#
-W wbiCEIConfigInputPanelBeanId.serverName="server1"


################################################################################
# Database type
# 
# Choose the type of database you want to use/create for Common Event Infrastructure.
# The supported database types are as follows: CloudScape, DB2 UDB, Oracle.
# To select a particular database type, uncomment the appropriate line. 
#
-W wbiCEIConfigInputPanelBeanId.database="CLOUDSCAPE_V51_1"
# -W wbiCEIConfigInputPanelBeanId.database="DB2UDBNT_V8_1"
# -W wbiCEIConfigInputPanelBeanId.database="DB2UDBNT_V82_1"
# -W wbiCEIConfigInputPanelBeanId.database="ORACLE_V9_1"
# -W wbiCEIConfigInputPanelBeanId.database="ORACLE_V10_1"
# -W wbiCEIConfigInputPanelBeanId.database="DB2UDBOS390_V7_1"
# -W wbiCEIConfigInputPanelBeanId.database="DB2UDBOS390_V8_1"


################################################################################
# The following entries are used only if you selected DB2 as your preferred
# database type.

################################################################################
# Create database choice
#
# If you want to create a new database for Common Event Infrastructure then
# set the value as "yes". If you want to generate scripts to create new database
# then set the value as "no".
#
# -W wbiCEIDB2ConfigInfoBean.createDatabaseChoice="yes"


################################################################################
# Database Name
#
# The database name. By default the database is named "event". Database name
# cannot be more than 8 characters long.
#
# -W wbiCEIDB2ConfigInfoBean.databaseName="event"


################################################################################
# User ID
#
# User ID to authenticate with the database
#
# -W wbiCEIDB2ConfigInfoBean.userId="YOUR_USER_ID_DB"


################################################################################
# Password
#
# Specify the password for database authentication. Later confirm it.
#
# -W wbiCEIDB2ConfigInfoBean.password="YOUR_PASSWORD_DB"
# -W wbiCEIDB2ConfigInfoBean.passwordConfirmation="YOUR_PASSWORD_DB"


################################################################################
# JDBC Driver Classpath
#
# Specify a directory that contains the following files: 
#  db2jcc.jar, db2jcc_license_cu.jar, 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 wbiCEIDB2DriverInfo.driverClassPath="C:\Program Files\IBM\WebSphere\
#  universalDriver_wbi\lib"
#
#
# -W wbiCEIDB2DriverInfo.driverClassPath=""


################################################################################
# Driver Type
#
# Specify the driver JDBC type. Valid values are "2" or "4".
#
# -W wbiCEIDB2DriverInfo.driverType="4"


################################################################################
# Database Server Name
#
# Specify the database server name only if your driver type selection was "4".
#
# -W wbiCEIDB2DriverInfo.databaseServerName="localhost"


################################################################################
# Server Port
#
# Specify the server port only if your driver type selection was "4".
#
# -W wbiCEIDB2DriverInfo.serverPort="50000"


################################################################################
# Database Node Name
# 
# Specify the database node name only if the DB2 server is remote.
#
# -W wbiCEIDB2DriverInfo.dbNodeName=""


################################################################################
# The following entries are used only if you selected Oracle V9.1 or Oracle V10.1
# as your preferred database type.

################################################################################
# Create database choice
#
# If you want to create new database objects on an existing instance for Common
# Event Infrastructure then set the value as "yes". If you want to generate scripts 
# to create new objects then set the value as "no".
#
# -W wbiCEIOracleConfigInfoBean.createDatabaseChoice="yes"


################################################################################
# Database Name
#
# The database name. Database name cannot be more than 8 characters long.
#
# -W wbiCEIOracleConfigInfoBean.databaseName=""


################################################################################
# User ID
#
# User ID to create in the database.
#
# -W wbiCEIOracleConfigInfoBean.userId="YOUR_DB_USER_ID"


################################################################################
# Password
#
# Specify the password for the created user ID. Later confirm it.
#
# -W wbiCEIOracleConfigInfoBean.password="YOUR_DB_USER_PASSWORD"
# -W wbiCEIOracleConfigInfoBean.passwordConfirmation="YOUR_DB_USER_PASSWORD"


################################################################################
# User ID
#
# User ID with SYSDBA authority.
#
# -W wbiCEIOracleDriverInfo.userId="USER_ID_AUTH_SYSDBA"


################################################################################
# Password
#
# Specify the password for the user ID with SYSDBA authority. Later confirm it.
#
# -W wbiCEIOracleDriverInfo.password="USER_PASSWORD_AUTH_SYSDBA"
# -W wbiCEIOracleDriverInfo.passwordConfirmation="USER_PASSWORD_AUTH_SYSDBA"


################################################################################
# JDBC Driver Classpath
#
# Specify a directory that contains the following files: 
#
#  ORACLE_OCI8 - specify a directory that contains classes12.zip.
#
#  ORACLE_THIN - specify a directory that contains ojdbc14.jar.
# -W wbiCEIOracleDriverInfo.driverClassPath="<value>"


################################################################################
# Driver Type
#
# Specify the driver JDBC type only if you did not opt to create a new database. 
# Valid values are "oci" or "thin".
#
# -W wbiCEIOracleDriverInfo.driverType="oci"


################################################################################
# Database Server Name
#
# Specify the database server name only if your driver type selection was "thin".
#
# -W wbiCEIOracleDriverInfo.databaseServerName="localhost"


################################################################################
# Server Port
#
# Specify the server port only if your driver type selection was "thin".
#
# -W wbiCEIOracleDriverInfo.serverPort="1521"


################################################################################
#
# Business Process Choreographer Configuration
#
# The following entries are used to create a sample Business Process Choreographer
# configuration.  Set doConfigureSampleBPContainerCheckList="yes" if you want
# to configure a sample.  If you do not want a sample leave the value as "".  
# If you set the value to "yes" then the rest of the parameters must also be filled 
# out.
#
-W bpcConfigInputPanelBeanId.doConfigureSampleBPContainerCheckList=""

################################################################################
# If you chose to create a sample Business Process Choreographer configuration
# above then specify the userid for that sample configuration.  If not then 
# comment out this line.
#
-W bpcConfigInputPanelBeanId.userId="YOUR_USER_ID_BPC"

################################################################################
# If you chose to create a sample Business Process Choreographer configuration
# above then specify the password for that sample configuration and confirm that 
# password.  If not then comment out these lines.
#
-W bpcConfigInputPanelBeanId.password="YOUR_PASSWORD_BPC"
-W bpcConfigInputPanelBeanId.passwordConfirmation="YOUR_PASSWORD_BPC"

################################################################################
# If you chose to create a sample Business Process Choreographer configuration
# above then specify the security role for the business process system administrator.
# This is the security role used by the Business Process Choreographer to run a
# business process.  Below is an example of an LDAP security role.  Comment out 
# this line if a sample Business Process Choreographer configuration is not being 
# created.
#
-W bpcConfigInputPanelBeanId.securityRole="YOUR_SECURITY_ROLE_BPC"

################################################################################
#
# Application Scheduler configuration
#
# Application Scheduler is used to schedule migration application group events.
# If you choose to configure Application Scheduler, set the following property
# to "yes". Otherwise, leave it blank "".
#
-W wbiAppSchedulerConfigInputPanel.doAppSchedulerConfig=""
#-W wbiAppSchedulerConfigInputPanel.doAppSchedulerConfig="yes"


################################################################################
#
# Indicate the application server name on this node if you chose to configure
# it for Application Scheduler use. Usually, for a stand-alone profile the 
# server name is "server1".
#
-W wbiAppSchedulerConfigInputPanel.appSchedulerServer="server1"


################################################################################
#
# 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: CloudScape, 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.DBProductList="CLOUDSCAPE"
#-W wbiCommonDBConfigPanel.DBProductList="DB2_Universal"
#-W wbiCommonDBConfigPanel.DBProductList="DB2UDBOS390_V7_1"
#-W wbiCommonDBConfigPanel.DBProductList="DB2UDBOS390_V8_1"
#-W wbiCommonDBConfigPanel.DBProductList="DB2_CLI"
#-W wbiCommonDBConfigPanel.DBProductList="INFORMIX"
#-W wbiCommonDBConfigPanel.DBProductList="MSSQLSERVER_Embedded"
#-W wbiCommonDBConfigPanel.DBProductList="MSSQLSERVER_DataDirect"
#-W wbiCommonDBConfigPanel.DBProductList="ORACLE_OCI"
#-W wbiCommonDBConfigPanel.DBProductList="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_cu.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 "default" for installing a stand alone profile
# Do not change this!
#
-W wbiCreateProfileTypeSelectionPanelBeanId.selection="default"

이용약관 |


(c) Copyright IBM Corporation 2005, 2006.
이 Information Center는 Eclipse 기술을 기반으로 합니다. (http://www.eclipse.org)