Customizing the Sametime Meeting Server installation response file for IBM i

Customize the IBM® Sametime® Meeting Server installation response file on IBM i as part of preparing to install the Sametime Meeting Server on IBM i. Pre-populate installation values in the installation response file.

About this task

Customize the meeting installation response file.

Procedure

  1. Log in to the server using a profile with *ALLOBJ and *SECADM special authorities.
  2. Change to the /responseFiles directory in the location where you extracted the Sametime Meeting Server package; for example:

    cd /STM_package/STMeetings/responseFiles

  3. Make a copy of the IMS_ssc_i.rsp file, using a name of your choosing. Store the copy in a location that the installation program can access.
  4. Customize your copy of the IMS_ssc_i.rsp file with the settings appropriate for your specific installation, as described in Table 1.
    Table 1. Sametime Meeting Server installation response file parameters and values
    Parameters Values 
    <agent-input temporary='true'
 clean='true' acceptLicense='true'>
    		 Change the value of acceptLicense to 'true': to indicate your agreement with the license terms. 
    <repository location='../STMeeting'/>
    		 The repository file location in the installation package. 
    <profile installLocation='/qibm/
userdata/lotus/SametimeMeetingCell'
 id='IBM Sametime Server Platform Meeting'>
    		 The installLocation is the directory in which you are installing the Sametime Meeting Server. The id must be consistent with the profile setting in the offering tag in this response file. 
    <data key='user.installlocation'
 value='/qibm/userdata/lotus/
SametimeMeetingCell'/>
    		 Same as the installLocation. 
    <data key='user.com.ibm.lotus.sametime.
meetingserver.existingWAS'
 value='TRUE'/>
    		 Set this value to 'TRUE' because you must install WebSphere® Network Deployment before you install Sametime Meeting Server. 
    <data key='user.was.installlocation'
 value='/QIBM/ProdData/WebSphere/
AppServer/v85'/>
    		 Specifies where the WebSphere Application Server is already installed. 
    <data key='user.was.profilelocation'
 value='/QIBM/UserData/WebSphere/
AppServer/v85'>
    		 The WebSphere Application Server profiles will be stored in a profiles subdirectory of this location. 
    <data key='user.com.ibm.lotus.sametime.
meetingserver.SSChostname' value=
'SSCHOSTNAME'/>
    		 The fully qualified hostname of the Sametime System Console that you are using to install IBM Sametime Meeting Server. 
    <data key='user.com.ibm.lotus.sametime.
meetingserver.SSCportnumber' value=
'9085'/>
    		 Specify a port for connecting to the Sametime System Console server. 
    <data key='user.com.ibm.lotus.sametime.
meetingserver.SSCusername' value=
'wasadmin'/>
    <data key='user.com.ibm.lotus.sametime.
meetingserver.SSCpassword' value=
'zN39fpCc9SqIryGJM7+02A=='/>
    		 Use the generateEncodedPassword utility contained in the install kit to generate an encoded form of the password.

    For example, zN39fpCc9SqIryGJM7+02A==

    is equivalent to a password of wasadmin

    		 
    <offering profile='IBM Sametime Server
 Platform Meeting' features='CEMain,
nossc,meeting,ssc' id='com.ibm.lotus.
sametime.meetingserver'/>
    		 The name of the deployment plan that you created for installing the Sametime Meeting Server. 
    <offering profile='IBM Sametime Server
 Platform' features='CEMain,nossc,
meeting,ssc' id='com.ibm.lotus.sametime.
meetingserver'/>
    		 The value of offering profile must be same as the profile's id (see row 3 in this table).
    Note: The Sametime Meeting Server can also be installed without the Sametime System Console deployment. The response file, IMS_i.rsp is designed to allow for installation without the Sametime System Console, but installation with the Sametime System Console deployment is recommended.

    There are special considerations if you are planning to install both the Sametime Meeting Server and the Sametime Proxy Server on the same server. Define a separate host name and IP address in addition to the default system host name and IP address. After both servers are installed, you are directed to update the Host Alias table for the Sametime Proxy Server so that it does not use the same host name and IP address as the Sametime Meeting Server. This is necessary for live names to work correctly in a meeting room.