WebSphere brand IBM WebSphere Presence Server, Version 7.0

Editing the response file

A silent installation uses a response file to inform the installer which actions to perform. This file must be customized before attempting a silent installation

About this task

Customizing the response file, presenceServer_install.rsp, involves setting the values of variables. The installer uses these variables during the silent installation process to determine what actions are required for the installation process.

Customize the response file precisely so that the installation program can read the option values accurately. For example, always enclose values in double quotation marks. When the installer encounters an incorrect parameter, it stops and writes an explanation of the problem to the installer log file: presenceServerInstall.log.

  1. Open the installation response file, presenceServer_install.rsp, in a text editor. After the first installation, the response file can be found in the directory was_root/installableApps/presence.
    Note: As an alternative to the default response file, you can build a response file using the template found on the Presence Server CD in the /response_files directory: presenceServer_install_template.rsp. To use this file for silent installation, copy it to each cluster member and each deployment manager, then modify it.
  2. Edit the response file, modifying the following values as needed. The following tables list the response file parameters.
    Note: Most of the response file parameters are used only on a deployment manager node or a stand-alone server. When you are installing on a clustered node that is not a deployment manager, only the following parameters are required:
    • LICENSE_ACCEPTED
    • MODE
    • WAS_HOME
    • WAS_PROFILE
    Table 1. License and mode properties for silent installation
    Property Valid values Example value
    LICENSE_ACCEPTED= Must equal true to use installer true
    MODE= Install for an initial installation; Modify for an update. Install
    Table 2. WebSphere properties for silent installation
    Property Valid values Example value
    WAS_HOME= Path to the WebSphere® Application Server root directory on this node. /opt/IBM/WebSphere/AppServer
    WAS_PROFILE= Path to the WebSphere Application Server profile directory on this node. /opt/IBM/WebSphere/AppServer/profiles/Appsrv01
    WAS_ADMIN_USER= Administrative user name for WebSphere Application Server was_admin
    WAS_ADMIN_PASSWORD= Password for the WebSphere Application Server administrative user waspass
    IS_CLUSTER Indicates whether the installation is on a WebSphere cluster or a single server. Required only for deployment manager installations. true or false
    WAS_SERVER_NAME, WAS_NODE_NAME The WebSphere server and node that will be used for the installation. Used when IS_CLUSTER=false and this is a Dmgr installation. Required when installing or modifying a deployment manager on a server scope.

    PS_Server

    node1

    WAS_CLUSTER_NAME, WAS_PROXY_NAME, WAS_PROXY_NODE_NAME The WebSphere cluster name, proxy name and proxy node name. Used when IS_CLUSTER=true and this is a Dmgr installation. Required when installing or modifying a deployment manager on a cluster scope.

    PS_Cluster

    PS_Proxy

    node1

    Table 3. CSCF configuration properties for silent installation
    Property Valid values Example value
    CONFIGURE_CSCF If true, the CSCF address is set in the WebSphere proxy configuration. If false, the CSCF address configuration is not set. Required when installing or modifying a deployment manager on a cluster scope. true or false
    CSCF_ADDRESS Any valid CSCF address string. In a clustered configuration with CONFIGURE_CSCF=true, this is a semicolon-delimited list of hosts (IP addresses or host names) for which the proxy server will not remove the P-asserted identity headers that are added by the CSCF. Required when installing or modifying a deployment manager on a cluster scope. The use of a mask (*) is permitted. Do not include spaces in the input string. 192.0.2.21;*.*.*.*
    Table 4. TAI configuration properties for silent installation
    Property Valid values Example value
    CONFIGURE_TAI 1 to set the IMS Trust Association Interceptor (TAI) configuration in WebSphere Application Server. 0 to not set the configuration. Required only for deployment manager installations. 0 or 1
    TAI_ALLOWED_SENDERS Required when installing or modifying a deployment manager with the IMS TAI configured (CONFIGURE_TAI=1), this field assigns the value for the allowed senders configuration parameter. It is a comma-delimited list of hosts (IP addresses or host names) that the interceptor considers to be trusted. The use of a mask (x for the TAI) is permitted. Do not include spaces in the input string. x.example.com,x.x.x.x,2002:92A:8F7A:0:0:20:0:1
    Table 5. General database properties for silent installation
    Property Valid values Example value
    DATABASE_VENDOR Database type for the Presence Server database–either DB2 or Oracle db2
    DB_JDBC_DIR Path to the database client driver jars on the WebSphere Application Server host /opt/ibm/db2/V9.5/java
    Table 6. Presence Server database properties for silent installation
    Property Valid values Example value
    DB_HOST_NAME Host name of the database server to be used for the store localhost
    DB_NAME Name of the database to be used for the store PSDB
    DB_PORT Port number on the database server to be used for the store 50000
    DB_ADMIN_NAME User with permissions for the database dbAdmin
    DB_ADMIN_PASSWORD Password of the user with permissions for the database dbAdminPass
    UPDATE_PS_DB 1 indicates that the configuration table should be deleted. 0 indicates that the configuration table should remain the same as it was before the process. If the configuration is empty, the default configuration will be loaded. 0 or 1
    Table 7. Content indirection database properties for silent installation
    Property Valid values Example value
    CI_DB_HOST_NAME Host name of the database server to be used for the content indirection database localhost
    CI_DB_NAME Name of the database to be used for the store PSCIDB
    CI_DB_PORT Port of the database server to be used for the store 50000
    CI_DB_ADMIN_NAME User with permissions for the database dbAdmin
    CI_DB_ADMIN_PASSWORD Password of the user with permissions for the database dbAdminPass
    Table 8. Usage record database properties for silent installation
    Property Valid values Example value
    UR_DB_HOST_NAME Host name of the database server to be used for the Usage Records database localhost
    UR_DB_NAME Name of the database to be used for the store PSURDB
    UR_DB_PORT Port of the database server to be used for the store 50000
    UR_DB_ADMIN_NAME User with permissions for the database dbAdmin
    UR_DB_ADMIN_PASSWORD Password of the user with permissions for the database dbAdminPass
    UR_UPDATE_PS_DB 1 indicates that the configuration table should be deleted. 0 indicates that the configuration table should remain the same as it was before the process. If the configuration is empty, the default configuration will be loaded. 0 or 1
    CREATE_UR_TABLES 1 indicates that the USAGERECORDS table should be recreated. 0 indicates that the table should not be recreated. Used to prevent the deletion of existing usage records data. 0 or 1
    Table 9. Data store database properties for silent installation
    Property Valid values Example value
    BUS_DATASTORE 1 indicates that the SIBus database will use Data Store; 0 indicates that the SIBus database will use File Store.

    Used if you want to preserve the Usage Records database tables after a modification.

    0 or 1
    BUS_DB_HOST_NAME Host name of the database server to be used for the store localhost
    BUS_DB_NAME Name of the database to be used for the store PSSIBUS
    BUS_DB_PORT Port number on the database server to be used for the store 50000
    BUS_DB_ADMIN_NAME User with permissions for the database dbAdmin
    BUS_DB_ADMIN_PASSWORD Password of the user with permissions for the database dbAdminPass
  3. Save the edited file.
  4. Copy the edited files to each cluster member and deployment manager where you plan to install the Presence Server product.
What to do next
You are ready to run the installation response file using the -i silent -f path options. For details, see the topic Installing silently.



Terms of use
(C) Copyright IBM Corporation 2009. All Rights Reserved.