×
 
 
  •  
$helper.renderConfluenceMacro('{bmc-global-announcement:$space.key}')
BMC Virtual Chat 9.1 Installing

Installing silently

If you want to install or upgrade BMC Virtual Chat in a large environment with multiple servers, you can run the installer in silent mode to allow for installation without user intervention.

To install silently on the AR and Mid Tier servers

  1. From the examples.zip file in the \Disk1\files\ folder, extract the silent_install.txt file.

  2. Modify the silent_install.txt file with the parameters for your environment. 

    Note

    The installer can only configure the BMC Knowledge Management integration if installed on a Mid Tier-only-server or on any server when load-balancing settings are provided. Otherwise, the installer does not know the Tomcat path and cannot define the protocol type (HTTP or HTTPS). Thus, it cannot configure the Knowledge Management Integration.

    When you install Virtual Agent on the Mid Tier server, it automatically configures the Knowledge Management integration.

    1. Modify the location where to install BMC Virtual Chat:
      Example:  -P installLocation=d:\deployment\installpath\BMCVirtualAgent
    2. In the Installing Features section, comment out the feature that you do not want to install. 
      1. To install on a Mid Tier-only server, comment out -A VA_AR.
      2. To install on an AR Server server that is not also a Mid Tier server, comment out -A VA_MT.
      3. If you are not installing in a load balanced environment, comment out -A VA_LB.
  3. Run the silent installer, and specify the absolute path to the file. 
    • Windows: setup.exe -i silent -DOPTIONS_FILE=C:\silent_install.txt
    • Linux: setup.bin -i silent -DOPTIONS_FILE=silent_install.txt

Example code to install silently 

Example code 
###############################################################################
# Options File
#
# Product: Virtual Chat 9.1
#
# To invoke in silent mode with options file:
#  Windows:
#   setup.exe -i silent -DOPTIONS_FILE=C:\Options.txt (absolute path MUST be used)
#   or java -jar setup.jar -i silent -DOPTIONS_FILE=Options.txt
#  Linux:
#   setup.bin -i silent -DOPTIONS_FILE=Options.txt (absolute path MUST be used)
###############################################################################
###############################################################################
# Product Install Location
#
# The install location of the product. Specify a valid directory into which
# the product should be installed of the form:
#   -P installLocation=directory
# where "directory" is the install location.
###############################################################################
-P installLocation=d:\deployment\installpath\BMCVirtualAgent
###############################################################################
#
# Installing Features
#
# Comment out whole string for feature you don`t want to install
###############################################################################
# Install Virtual Chat for AR Server
-A VA_AR
# Install Virtual Chat for MidTier
-A VA_MT
# (OPTIONAL) Install files for Chat Alerts
-A VA_CHAT_ALERTS
# (OPTIONAL) Configure Knowledge Management Integration while installation
# Requires the next properties to be set: IS_RKM_INTEGRATION_USER_CREATED, RKM_USER_NAME_VALUE, RKM_USER_PASSWORD_VALUE, RKM_USER_PASSWORD_REPEAT_VALUE
-A VA_RKM
# (OPTIONAL) Configure ITSM Integration while installation
# It is available only for ITSM version higher than 8.1.00.
# Important! MANUAL STEP is required after ITSM integration: After ITSM integration is configured by the Virtual Chat Installer and the installation has finished you need either to reboot the server or to Refresh all the Servlets in Virtual Chat Administration Console.
# Requires
-A VA_ITSM
# (OPTIONAL) Configure Load balancing settings (LoadBalancing SSP AR Settings) while installation
# LB configuration is also performed when IS_MULTI_TENANT_CONFIGURATION_NEEDED is set to true
# Requires the next properties to be set: LB_SERVER_NAME_ALIAS_VALUE, LB_SERVER_PORT_VALUE, LB_SERVER_PROTOCOL_VALUE, MT_SERVERS_NAMES_AND_PORTS_VALUE, MT_SERVERS_PORT_VALUE, MT_SERVER_PROTOCOL_VALUE
-A VA_LB

###############################################################################
#
# User Input Properties
#
# The format for entering user input properties is:
#   -J name=value
# where "name" is the name of the property and "value" is the value.
# ATTENTION! ALL FIELDS ARE MANDATORY!
# BMC_AR_USER - AR Administrator login
# BMC_AR_PASSWORD - AR Administrator password
# BMC_AR_SERVER_NAME - AR Server name
# (tend not to use it) BMC_AR_SERVER_INFO_HOSTNAME - AR Server full name to be resolved to IP address
# BMC_AR_PORT - AR Server port
# PROXY_LOGIN_NAME - Remedy user to be created for Virtual Agent to AR Server communications = Chat Proxy User  # BMC_VIRTUAL_CHAT_USER
# PROXY_PASSWORD - Chat Proxy User password
# IS_AR_PRIMARY_SELECTED & IS_AR_SECONDARY_SELECTED - mutually exclusive. Set Pimary for main server in group. Set Secondary for all others.
# IS_PROXY_USER_NEEDED - must be always set to true
# IS_PROXY_USER_CREATED - set to true if the appropriate user is already created and has "Administrator" the user's Group List.
# IS_NEED_TO_CREATE_PROXY - must have opposite value to IS_PROXY_USER_CREATED
# PROXY_LOGIN_NAME - Virtual Chat Proxy User name - will be specified in eschat_config.properties and is used by BMC Virtual Chat to work on AR Server
# PROXY_PASSWORD - Virtual Agent Proxy User password
# PROXY_PASSWORD_REPEAT_VALUE - must be equal to PROXY_PASSWORD
# IS_RKM_INTEGRATION_USER_CREATED - Set it to true is special user for RKM integration is already created
# RKM_USER_NAME_VALUE - name of the special user for RKM integration
# RKM_USER_PASSWORD_VALUE - password of the special user for RKM integration
# RKM_USER_PASSWORD_REPEAT_VALUE - password of the special user for RKM integration
# MIDTIER_WEB_SERVER - should be set to 'tomcat'
# MIDTIER_WEB_SERVER_HOME - Tomcat home directory
# MIDTIER_JRE_HOME - Path to Tomcat JRE. Needed for tomcat restart while VA upgrade.
# VAR_PATH - Path to folder where ProgramD data files will be installed. 
# BMC_USER_SELECTED_VIEW_LANGUAGES - enumeration of user languages to be installed to AR server. Comma separated, no spaces.
# BMC_VA_VIEW_LANGUAGES - should not be changed.
# LB_SERVER_NAME_ALIAS_VALUE - Load Balancer server name
# LB_SERVER_PORT_VALUE - Load Balancer server port
# LB_SERVER_PROTOCOL_VALUE - Load Balancer server protocol - http or https
# MT_SERVERS_NAMES_AND_PORTS_VALUE - Mid-Tier Servers separated with semicolon. Example: server1;server2;server3
# MT_SERVERS_PORT_VALUE - Mid-Tier Servers port
# MT_SERVER_PROTOCOL_VALUE - Mid-Tier Servers protocol - http or https
# IS_MULTI_TENANT_CONFIGURATION_NEEDED - set to true to enable Multy-Tenancy configuration and generation of correct "bots.xml" and "core.xml" files. It contains LoadBalancing SSP AR Settings.
# DEST_VALUE - Existing Destination Directory Path for configuration files to be generated by CongigsGenerator
# PROGRAM_D_USER_CONF_VALUE - Path to folder where "bots.xml" and "core.xml" will be located. By default, after installing BMC Virtual Chat on Windows they will be located in C:\Program Files\BMC Software\BMCVirtualAgent\VirtualAgentComponents\var\programd\conf
# PROGRAM_D_AIML_VALUE - Path to ProgramD AIML folder. By default, after installing BMC Virtual Chat on Windows the folder has the next path C:\Program Files\BMC Software\BMCVirtualAgent\VirtualAgentComponents\var\programd\aiml
# TENANTS_DATA - semicolon separated data for each Tenent. One Tenant should be described in the next way:
#   tars <Tenant Name>,<Tenant LoadBalancer Server Name or IP>,<Tenant Main AR Server0 Name or IP>,<Tenant other AR Server1 Name or IP>,<Tenant other AR Server2 Name or IP...> tarport <Tenant Main AR Server port> tarl <Tenant Main AR Server administrator Login> tarp <Tenant Main AR Server administrator Password>
#   Example for 2 tenants: tars hondaitsm,hondaitsm.bmc.com,arserver1.bmc.com,arserver2.bmc.com,arserver3.bmc.com tarport 12345 tarl HondaAdmin tarp password1; tars dellitsm,dellitsm.bmc.com,arservera.bmc.com,arserverb.bmc.com,arserverc.bmc.com tarport 10001 tarl DellAdmin tarp password2
###############################################################################
-J BMC_AR_USER=admin
-J BMC_AR_PASSWORD=password
-J BMC_AR_SERVER_NAME=KBP1-LHP-F54604
-J BMC_AR_PORT=42626
-J IS_AR_PRIMARY_SELECTED=true
-J IS_AR_SECONDARY_SELECTED=false
-J MIDTIER_WEB_SERVER=tomcat
-J MIDTIER_WEB_SERVER_HOME=C:/Program Files/apache-tomcat-7.0.50 
-J MIDTIER_JRE_HOME=D:/java/jdk1.7.0_25/jre
-J VAR_PATH=d:/deployment/installpath/var
-J BMC_USER_SELECTED_VIEW_LANGUAGES=en,es,fr,ko,de,it,ja,zh_CN,pt_BR
-J BMC_VA_VIEW_LANGUAGES=en,es,fr,ko,de,it,ja,zh_CN,pt_BR
-J IS_PROXY_USER_NEEDED=true
-J IS_PROXY_USER_CREATED=false
-J IS_NEED_TO_CREATE_PROXY=true
-J PROXY_LOGIN_NAME=ESChatProxy
-J PROXY_PASSWORD=password
-J PROXY_PASSWORD_REPEAT_VALUE=password
-J IS_RKM_INTEGRATION_USER_CREATED=false
-J RKM_USER_NAME_VALUE=RKMUser
-J RKM_USER_PASSWORD_VALUE=password
-J RKM_USER_PASSWORD_REPEAT_VALUE=password
-J LB_SERVER_NAME_ALIAS_VALUE=loadbalancer1.bmc.com
-J LB_SERVER_PORT_VALUE=8080
-J LB_SERVER_PROTOCOL_VALUE=http
-J MT_SERVERS_NAMES_AND_PORTS_VALUE=midtier1.bmc.com,midtier2.bmc.com,midtier3.bmc.com
-J MT_SERVERS_PORT_VALUE=8080
-J MT_SERVER_PROTOCOL_VALUE=http
-J IS_MULTI_TENANT_CONFIGURATION_NEEDED=false
-J DEST_VALUE=C:\myes_conf
-J PROGRAM_D_USER_CONF_VALUE=C:\Program Files\BMC Software\BMCVirtualAgent\VirtualAgentComponents\var\programd\conf
-J PROGRAM_D_AIML_VALUE=C:\Program Files\BMC Software\BMCVirtualAgent\VirtualAgentComponents\var\programd\aiml
-J TENANTS_DATA=tasrs tenantA,LoadBalancerA,primaryARseverA,secondaryARsever1A,secondaryARsever2A tarport 12345 tarl Allen tarp password tasrs tenantB,LoadBalancerB,primaryARseverB,secondaryARsever1B,secondaryARsever2B tarport 54321 tarl Administrator tarp password1



Was this page helpful? Yes No Submitting... Thank you
Last modified by Aaditi Lakade on Aug 05, 2019
task installation

Comments

  1. Abhijeet Anand

    Hi,

    It is not clear, which parameters should be used for Virtual Agent installation on Mid-tier and which parameters should be used for Virtual Agent installation with AR Server.

    Aug 04, 2019 11:56
  2. Abhijeet Anand

    Hi Aaditi Lakade,

    Did you get a chance work on it?

    Best Regards,

    Abhijeet

    Aug 27, 2019 11:34

Log in or register to comment.

Post-installation fixes for BMC Virtual Chat
Verifying the installation
© Copyright 2010 - 2020 BMC Software, Inc.
Legal notices

Powered by Atlassian Confluence and Scroll Viewport

© Copyright 2005-2024 BMC Software, Inc. Use of this site signifies your acceptance of BMC’s Terms of Use . BMC, the BMC logo, and other BMC marks are assets of BMC Software, Inc. These trademarks are registered and may be registered in the U.S. and in other countries.