The difficulty is that (I am assuming) you have the SSC which manages your STProxy/Meeting/Community in your internal network and the Gateway in the DMZ. This means that you probably do not have all the ports open so that the SSC can communicate with the Gateway.
It's nice to have the Gateway managed by the SSC but opening more points to have that luxury isn't really warranted IMHO. I personally skip all references to the SSC and install it stand alone. If you want to manage it via the SSC then you're goign to have to work out what ports need opening.
The "server is not available" may be a ports issue. You should check the SystemOut.log for the deployment manager and STConsoleServer for obvious clues.
If your install went fine and it's purely a ports issue then you may need to re-register the Gateway with the SSC and hey presto it works obviously after opening ports.
If you want to install it stand alone then the installer will prompt you for LDAP and DB2 information. Below is the response file that comes with the media.
################################################################################
#
# Response File for IBM Sametime Gateway Installation
#
# Before you can begin the installation of Sametime Gateway you
# will want to first edit this response file with the values appropriate for your
# environment.
#
# Refer to the comments to learn how to use the response file and understand
# the various options. You must carefully complete or change the various values.
# If the values are not completed properly, the install may be unsuccessful.
#
# See the install log for any errors during installation.
#
# IMPORTANT: ALL VALUES MUST BE ENCLOSED IN DOUBLE QUOTES ( "" ).
#
# To use this response file with the installation, specify -options <file-name>
# as a command line argument to the install script, where <file-name> is the
# full path name of this response file:
#
# install -options <file-name>
#
# A common use of a response file is to run the wizard in silent mode. This lets
# the response file author specify wizard settings without having to run the
# wizard in graphical or console mode. To use this response file for silent mode
# execution, use the following command line arguments when running the wizard:
#
# install -options <file-name> -silent
#
################################################################################
################################################################################
#
# Has the license been accepted?
#
# The license must be accepted before installation so this value must be true
# for the install to be successful. Example: -V licenseAccepted=true
#
-V licenseAccepted=true
################################################################################
#
# Upgrade Choice
#
# If this is an upgrade, set Upgrade=true. Example: -V Upgrade="true"
#
#
-V Upgrade="false"
################################################################################
#
# Upgrade Location
#
# If this is an upgrade, set the value of Upgrade Location to the absolute path
# of the server to upgrade.
# Example: -V UpgradeLocation="C:\IBM\WebSphere\RTCGateway"
#
# This value is ignored if -V Upgrade="false"
#-V UpgradeLocation=""
################################################################################
#
# Gateway Cluster Name
#
# If this is an upgrade, set the value of the cluster that runs the Gateway apps.
#
# Example: -V ClusterToUpgrade="GWCluster"
#
# NOTE: This value is ignored unless -VUpgrade="true"
# -V ClusterToUpgrade=""
################################################################################
#
# Coexist Choice
#
# If an existing installation exists and you want to install an additional
# server on this system in order to create a vertical cluster, set this
# value to true.
# Example: -V Coexist="true"
#
# This value cannot be true if -V Upgrade="true"
# NOTE: For i5/OS set this value to "true" if another gateway has been installed on the system
-V Coexist="false"
###############################################################################
#
# Existing Server Location
#
# If Coexist="true", the absolute install location of the existing Sametime
# Gateway server must be entered.
#
# Example: -V InstalledServerLocation="C:\IBM\WebSphere\STgateway"
#
# This value is ignored unless -V Coexist="true"
# NOTE: This value is not needed for i5/OS
#-V InstalledServerLocation=""
################################################################################
#
# Select the type of installation.
#
# Possible values: primary, dm or secondary
#
# standalone = Single server deployment
# primary = Primary node for network deployment
# dm = Deployment manager
# secondary = Secondary node
# proxy = SIP and XMPP Proxy server
#
# Example = -V WasEnvType="primary"
#
# NOTE: -V Upgrade="true", this value will be loaded from the installed server
-V WasEnvType="standalone"
################################################################################
#
# CD location: WebSphere Application Server Network Deployment V6.1
#
# Example = -V CD_LOCATION="D:\"
#
# NOTE: This value is not needed for i5/OS
-V CD_LOCATION="<path to WebSphere CD>"
################################################################################
#
# WebSphere Application Server Install Location
#
# Example = -V WASLocation="C:\Program Files\IBM\WebSphere\AppServer"
#
# NOTE: If -V Coexist="true" or -V Upgrade="true", this value will be chosen
# for you.
-V WASLocation="C:\Program Files\IBM\WebSphere\AppServer"
################################################################################
#
# Enter the properties for this instance of the WebSphere Application Server.
#
# Node name: -V NodeName="rtcgwNode"
# Cell name: -V CellName="rtcgwCell"
# Host name: -V HostName="rtcgwHostName.yourco.com"
#
# NOTE: These values are ignored if -V Upgrade="true"
-V NodeName="stgwNode"
-V CellName="stgwCell"
-V HostName="stgwHostName.yourco.com"
################################################################################
#
# WebSphere Application Server Administrative User
#
# Create the administrative user id and password for the WebSphere Application Server.
#
# User Id: -V WasAdminId="<AdminId>"
# Password: -V WasAdminPwd="<AdminPwd>"
#
# NOTE: These values are ignored if -V Upgrade="true"
-V WasAdminId="<AdminId>"
-V WasAdminPwd="<AdminPwd>"
################################################################################
#
# IBM Sametime Gateway Install Location
#
# The install location of the product. Specify a valid directory into which the
# product should be installed. If the directory contains spaces, enclose it in
# double-quotes. For example, to install the product to C:\Program Files\My
# Product, use
#
# -P installLocation="C:\Program Files\My Product"
#
# NOTE: This value is ignored if -V Upgrade="true".
# NOTE: This value is not needed for i5/OS
-P installLocation="C:\Program Files\IBM\WebSphere\STgateway"
################################################################################
#
# Specify the DB2 database properties:
#
# Database Host Name: -V DBHostName="<dbHostName>"
# Database Server Port: -V DBPort="<dbPort>"
# Database name: -V DatabaseName="<dbName>"
# Schema owner user ID: -V SchemaId="<schemaId>"
# Schema owner password: -V SchemaPwd="<schemaPwd>"
# Application user ID: -V AppUserId="<appUserId>"
# Application password: -V AppPwd="<appUserPwd>"
#
# NOTE: SchemaId and SchemaPwd are ignored unless -V WasEnvType="primary" or -V WasEnvType="standalone"
-V DBHostName="<dbHostName>"
-V DBPort="<dbPort>"
-V DatabaseName="<dbName>"
-V AppUserId="<appUserId>"
-V AppPwd="<appUserPwd>"
-V SchemaId="<schemaId>"
-V SchemaPwd="<schemaPwd>"
################################################################################
#
# LDAP Specific properites:
#
# Value is either true or false
# -V ldap_configuration_flag="<ldap_configuration_flag>"
#
# LDAP server host name and port, for example: host name: 9.33.22.65, port: 389
# -V ldap_host="<hostName>"
# -V ldap_port="<port>"
#
# If your LDAP server allows anonymous access, if you want anonymous access, value is true;
# if you want authenticated access, value is false. If your LDAP server only allows authenticated access
# value must be false
# -V ldap_pass_anonymous="<ldap_pass_anonymous>"
#
# If your LDAP server allows anonymous access, user name and password can be ingored, but you can
# still choose authenticated access by providing the credentials. If your LDAP server only allows authenticated
# access, you must provide the credentials.
# Example for a user name: cn=John Smith, ou=Product Development, o=Acme, st=Minnesota, c=US.
# Replace "=" with "@", the user name should be filled with this:
# cn@John Smith, ou@Product Development, o@Acme, st@Minnesota, c@US
# -V ldap_username="<userName>"
# -V ldap_password="<password>"
#
# This is for non-Domino LDAP, for example: dc=acme,dc=com.
# Replace "=" with "@", the base dn should be filled with this:
# dc@acem,dc@com
# -V ldap_searchbase="<baseDN>"
#
#
-V ldap_configuration_flag="<ldap_configuration_flag>"
-V ldap_host="<hostName>"
-V ldap_port="<port>"
-V ldap_pass_anonymous="<ldap_pass_anonymous>"
-V ldap_username="<userName>"
-V ldap_password="<password>"
-V ldap_searchbase="<baseDN>"
################################################################################
################################################################################
#
# i5OS Specific properites:
#
# ProfileName="RTCGW_Profile"
# StartingPort="10000"
# DefaultSchema="RTCGW"
#
#
-V ProfileName="RTCGW_Profile"
-V StartingPort="10000"
-V DefaultSchema="RTCGW"
################################################################################
9.0
Return to top
. . . . . . RE: Installing 9.0 Gateway - any do... (~Kim Opniman 9.Jul.15) 
Print this page
