Installing the Web Interface › The Web Interface Response File

The Web Interface Response File

The Web Interface response file, harweb.rsp, is a text file created by the installation wizard. You can also create this file manually. The response file contains parameters you set using the required information during the installation. Create the response file for your installation using any text editor.

Example: Web Interface Response File (JBoss Application Server with an Oracle Database)

This example illustrates a Web Interface response file to install the Web Interface for the first time under JBoss Application Server using an Oracle database. In this example, comments are preceded with a hash mark (#), parameters appear in boldface, and parameters left blank do not apply to the installation. For example, if you are installing the Web Interface under Oracle Iplanet Web Server on UNIX or Linux, you must supply a domain name. Otherwise, you should leave the DOMAIN parameter blank. In addition, when specifying directory paths, you must use double backslashes (for example, TEMP=D\:\\temp).

Important! When you specify the name of the context root (the .war file name), you can enter non-English characters (such as Japanese or accented characters). If your .WAR filename contains non-English characters, Tomcat and other application servers may not be able to generate a context with a matching name. Therefore, you should use only single-byte, English characters when you name the .WAR file you are creating, especially for Tomcat.

#/n
#Wed Jan 30 14:59:54 GMT+05:30 2008
#Broker
BROKER=scm0321
#domain name (Example ca.com)
DOMAIN=
#Appserver Home directory
APPHOME=D\:\\jboss-4.2.2.GA
#Location of JDBC driver or drivers for Microsoft SQL Server
SJDBCLOC=
#Temp directory
TEMP=C\:\\Temp
#Context root
APPNAME=harweb
#Harweb Home Directory
HARWEBHOME=
#Jboss configuration (all, default). This value must be lowercase.
JBOSSCONFIGURATION=default
#SQL Server Authentication Mode (Windows/SQL Server)
SAUTHMODE=
#Oracle Port
OPORT=1521
#App Server Type (Tomcat 5.x, WebSphere Application Server, Sun Java System Web Server, JBoss Application Server 4.x, JBoss Application Server 5.x)
APP_SERVER=JBoss Application Server
##Location of JDBC driver for Oracle
OJDBCLOC=C\:\\oracle\\product\\11.2.0\\db_1\\jdbc\\lib
#Oracle JDBC Driver version (11g or 12c)
OJDBCVERSION=11g
#Oracle Host Name
OHOSTNAME=mycomp-xp1
#Installation Type (New/Upgrade)
INSTALL_TYPE=New
#Package war file only (no deployment)
WEBPACKAGEONLY=false
#Database Password
DBPASSWORD=cascm
#Microsoft SQL Server JDBC Driver Version (2008)
SJDBCVERSION=
#Database User Name
DBUSER=smith156
# For WebSphere only-Path name of WebSphere node on which to deploy the Web Interface. Defines the path name of the WebSphere node. For details about these path names, see Path Names for WebSphere Nodes.
NODE_TO_DEPLOY_LOC=
#SQL Server Database Name
SDBNAME=
#Database Type (Oracle or SQLServer)
DBTYPE=Oracle
#CA SCM Authentication Mode (internal or openldap or mixed)
AUTHMODE=Internal
# SQL Server server name
SSERVERNAME=
#Oracle Service Name
OSERVICE=VM817

$RTHOME

This variable points to the directory where PEC is installed.

$CAPKIHOME

This variable points to the directory where CAPKI is installed.