MicroStrategy ONE
Concluindo uma instalação silenciosa
Para executar a instalação silenciosa, você deve criar um arquivo de opções e, em seguida, execute-o com o MicroStrategy Assistente de instalação. Salve o arquivo de opções como options.txt
. Um exemplo de options.txt
arquivo é fornecido em Exemplo de um arquivo de opções abaixo. Você pode usar o exemplo como modelo e substituir o texto em itálico por suas próprias informações.
Este arquivo de opções ou arquivo de resposta é usado com o argumento da linha de comando -options
para modificar as configurações do assistente. As configurações que podem ser especificadas para o assistente estão listadas na próxima seção, Parâmetros para uma instalação silenciosa.
- Faça logon no computador onde você está instalando um ou mais MicroStrategy produtos.
- Você pode acessar os arquivos de instalação solicitando ao administrador do sistema que compartilhe os arquivos em um local de rede.
- Navegue até o
MicroStrategyInstallation/QueryReportingAnalysis_Linux
diretório. - Abrir
options.txt
em um editor de texto. - Especifique um valor para uma configuração substituindo o caractere
Value
. Para obter informações detalhadas sobre os parâmetros e valores que podem ser fornecidos com ooptions.txt
arquivo para uma instalação silenciosa, consulte Parâmetros para uma instalação silenciosa. - Salve as alterações no
options.txt
arquivo. -
Para usar o arquivo de opções em uma instalação silenciosa, especifique
-silent -options
<FileName>
como um argumento de linha de comando para o assistente, onde<FileName>
é o nome deste arquivo de opções, por exemplo,options.txt
.Por exemplo, digite o comando:
Copiar./setup.sh -silent -options <path of the options.txt file>
Exemplo de um arquivo de opções
Copie e cole este exemplo para criar um options.txt
arquivo. Certifique-se de verificar os espaços corretos e as novas linhas em todos os caminhos de arquivo.
Para obter descrições de cada uma das opções listadas neste exemplo, consulte Parâmetros para uma instalação silenciosa.
O exemplo abaixo pressupõe que você esteja usando o conjunto completo de arquivos de instalação para suportar o MicroStrategy instalação. Se você baixou apenas um subconjunto dos arquivos .tzp necessários para o MicroStrategy instalação, você deve definir onde esses arquivos serão armazenados, utilizando os parâmetros descritos em Opções de instalação sob demanda.
## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ##
#
# Options File Template
#
# This file is a options file (i.e., response file) for the MicroStrategy
# Installer. The options file is loaded by default if it is named "options.txt"
# and it is located in the same directory as setup.sh.
# An alternative options file can be specified by using "-options" on
# the command line.
#
# The settings that can be specified for the wizard are listed below. To use
# this template, follow these steps:
#
# 1. Enable a setting below by removing leading '###' characters from the
# line (search for '###' to find settings you can change).
#
# 2. Specify a value for a setting by replacing the character's '<value>'.
# Read each setting's documentation for information on how to specify its
# value.
#
# 3. Save the changes to the file.
#
# 4. Launch the installation using the setup.sh script
#
#
# We are working to improve our Silent and Automated installation use-cases. Feedback on
# Silent or Automated installations is welcomed via the MicroStrategy Community (Platform
# Services > Platform > Secure Enterprise - Linux) or via Technical Support to the Deployment Team.
#
# Here is a direct link (as of June 2017) to the Community sub-section on platform deployment:
# https://success.microstrategy.com/s/topic/0TO44000000FlkIGAS/Secure%20Enterprise%20-%20Linux%20-%20U092?tabset-215d6=1
#
#
## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ##
#
# Silent Installation.
#
# The options file is required for silent installations, specify -silent
# -options <file-name> as a command line arguments to the wizard, where
# <file-name> is the name of this options file.
#
# For example:
#
# setup.sh -silent -options options.txt
#
## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ##
#
# System Requirements Warnings
#
# The silent installation will install MicroStrategy even if some system
# requirements are not completely meet.
# Please read the release notes file and configure your system so it meets the
# requirements before running this setup and check the installation log after
# the installation is complete.
#
## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ##
#
# Installation Properties
#
# Please specify general installation properties.
## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ##
#
# MicroStrategy License Agreement Default Selection
#
# In the MicroStrategy Installation Wizard, it is legally required to accept the
# MicroStrategy License Agreement in order to proceed with the desired installation
# operation.
# Use this option to specify the default selected option selected for the License
# Agreement Dialog. Legal values are:
#
# true - Accept the License Agreement
# false - Do not accept the License Agreement
#
# If no option is provided, 'reject' is used as default.
### licenseAgreement.accept=<value>
## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ##
#
# Customer Information
#
# Please specify your name, the name of the company for which you work and the
# license key.
# User
### userRegistration.user=<value>
# Company
### userRegistration.company=<value>
# License Key
### userRegistration.cdKey=<value>
## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ##
#
# MicroStrategy Installation Selection
#
# For a new Installation, use "new" (i.e. install.Instance=new)
#
# For an existing Installation, specify its home path.
# Home path is a directory that identifies an installation and stores
# configuration files and application launchers (suite.homeDirectory in
# MicroStrategy Install Locations section). You may refer to <home> tag under
# <suite>MstrSuite</suite> in mstrinstall.xml.
#
# For example
#
# install.Instance=/home/user/MicroStrategy
#
### install.Instance=<value>
## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ##
#
# MicroStrategy Operation to perform on instance
#
# For a new Installation, Legal values are:
# FRESH_INSTALL - Indicates a new installation will be performed
#
# For an existing Installation, Legal values are:
# MODIFY - Indicates the installation will be modified.
# REPAIR - Indicates the installation will be repaired.
# UNINSTALL - Indicates the installation will be uninstalled.
# UPGRADE - Indicates the installation will be upgraded
# REMOVE_UPDATE - Indicates a update package will be removed
#
# For example
#
# install.Operation=MODIFY
#
### install.Operation=<value>
## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ##
#
# MicroStrategy Install Locations
#
# The install locations of the product. Specify a valid directories into which
# the product should be installed.
# It is recommended to specify a different directory for each one of the install
# locations:
#
# Home - This directory will store configuration files and application launchers
# Install - This directory will store all the binaries and other static files
# Log - Application logs will be created here.
#
# NOTE: Special characters (!,%,$,^,\,?,#) and space characters are not valid. All
# special characters will be ignored.
### suite.homeDirectory=<value>
### suite.installDirectory=<value>
### suite.logDirectory=<value>
## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ##
#
# MicroStrategy Product Selection State
#
# A selection state setting is available for every MicroStrategy product.
# Legal values are:
#
# true - Indicates that the product is selected for installation
# false - Indicates that the product is not selected for installation
#
# The default value for Selection state settings is "true".
#
# For example, to select "MicroStrategy Intelligence Universal Edition"
# for installation use
#
# Intelligence.active=true
#
# All licensed products are selected by default, so in case you want to prevent
# them from being installed make sure they are unselected too.
## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ##
#
# MicroStrategy Intelligence Universal Edition
#
# MicroStrategy Intelligence Universal Edition will be automatically
# selected for installation if any of the following products are selected for
# installation:
# "MicroStrategy Report Services Universal",
# "MicroStrategy OLAP Services Universal"
# "MicroStrategy Distribution Services"
# "MicroStrategy Transaction Services"
# MicroStrategy Intelligence Universal Edition
### Intelligence.active=<value>
# MicroStrategy Report Services Universal
### ReportServices.active=<value>
# MicroStrategy OLAP Services Universal
### OLAPServices.active=<value>
# MicroStrategy Distribution Services
### DistributionServices.active=<value>
# MicroStrategy Transaction Services
### TransactionServices.active=<value>
## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ##
# MicroStrategy Web Universal
#
# MicroStrategy Web Universal Reporter will be automatically selected for
# installation if MicroStrategy Web Universal Analyst is selected.
#
# MicroStrategy Web Universal Reporter & Analyst will be automatically selected
# for installation if MicroStrategy Web Universal Professional is selected.
# MicroStrategy Web Universal Reporter
### WebReporter.active=<value>
# MicroStrategy Web Universal Analyst
### WebAnalyst.active=<value>
# MicroStrategy Web Universal Professional
### WebProfessional.active=<value>
# MicroStrategy Portlets
### Portlets.active=<value>
# MicroStrategy GIS Connectors
### GISConnectors.active=<value>
## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ##
#
# MicroStrategy Web Services J2EE
### WebServices.active=<value>
## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ##
#
# MicroStrategy Mobile Server JSP
### MobileServer.active=<value>
## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ##
#
# MicroStrategy Community Connectors
#
### CommunityConnectors.active=<value>
## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ##
#
# MicroStrategy Command Manager
### CommandManager.active=<value>
## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ##
#
# MicroStrategy System Manager
### SystemManager.active=<value>
## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ##
#
# MicroStrategy Platform Analytics
### PlatformAnalytics.active=<value>
## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ##
#
# MicroStrategy Enterprise Manager
### EnterpriseManager.active=<value>
## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ##
#
# MicroStrategy Integrity Manager
### IntegrityManager.active=<value>
## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ##
#
# MicroStrategy Telemetry Server
### TelemetryServer.active=<value>
## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ##
#
# New in 10.9
# MicroStrategy Library Web & Mobile
### LibraryWebMobile.active=<value>
## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ##
#
# New in 10.9
# MicroStrategy Collaboration
### Collaboration.active=<value>
## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ##
#
# New in 11.0
# MicroStrategy Certificate Store
### CertificateStore.active=<value>
## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ##
#
# New in 11.2
# MicroStrategy Export
### Export.active=<value>
## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ##
#
# New in 11.2
# MicroStrategy Repository
### Repository.active=<value>
## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ##
#
# New in 11.3
# MicroStrategy Cloud Object Connector
### CloudObjectConnector.active=<value>
## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ##
#
# Product Install Location.
# Use the following values to specify the install location for individual products.
#
# Warning: Special (!,%,$,^,\,?,#) and space characters are not valid. All special
# characters will be ignored.
# Web Universal
### WebUniversal.deployDirectory=<value>
# MicroStrategy Portlets
### Portlets.installDirectory=<value>
# MicroStrategy GIS Connectors
### GISConnectors.installDirectory=<value>
# MicroStrategy Community Data Connectors
### CommunityConnectors.installDirectory=<value>
# MicroStrategy Web Services J2EE
### WebServices.installDirectory=<value>
# MicroStrategy Mobile Server JSP
### MobileServer.installDirectory=<value>
# MicroStrategy Command Manager
### CommandManager.installDirectory=<value>
# MicroStrategy System Manager Install Location
### SystemManager.installDirectory=<value>
# MicroStrategy Platform Analytics Install Location
### PlatformAnalytics.installDirectory=<value>
## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ##
#
# CPU License Information
#
# This value should be specified when the license being used for MicroStrategy
# Intelligence Universal Edition is based on CPUs. Legal values are integers
# between 1 and either the number of CPUs allowed by the license or the number of
# CPUs in the machine, whichever is lower.
#
# For example to set the number of CPUs to 2, use:
#
# cpuCount.number=2
#
# To set this options to the maximum value allowed, use:
#
# cpuCount.number=maximum
#
# The default value for this setting is "maximum"
### cpuCount.number=<value>
## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ##
#
# Remote Repository Connection
#
# A repository is required for the following components:
# Collaboration Server
# Platform Analytics
#
# To use a remote repository, provide the connectivity information to be used.
# https://www2.microstrategy.com/producthelp/2021/InstallConfig/en-us/Content/repository_overview.htm
### RemoteRepository.DBHost=<value>
### RemoteRepository.DBPort=<value>
### RemoteRepository.DBUser=<value>
### RemoteRepository.DBPassword=<value>
# For new installations use this option to indicate if platform_analytics_wh
# should be dropped or preserved if it exists.
# true - Drop the schema and create a fresh configuration.
# false - Preserve the schema and upgrade it if necessary.
# The default value is false.
### PlatformAnalytics.overrideDb=<value>
# For new installations use this option to indicate if mstr_collab
# should be dropped or preserved.
# true - Drop the schema and create a fresh configuration.
# false - Preserve the schema and upgrade it if necessary.
# The default value is false.
### Collaboration.overrideDb=<value>
## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ##
#
# MicroStrategy Telemetry Server Configuration
#
# This step allows you to cluster the Telemetry Servers that will be used to send usage data to
# Platform Analytics.
#
# If you plan to install three or more Telemetry Servers in your environment, you must check the
# box below during the installation of each Telemetry Server. Failing to do so will result in
# manual configuration to create the cluster after the installation.
#
# For more information refer to the online help.
#
# Please note that Telemetry Server is installed by default when you install and Intelligence
# or Platform Analytics.
# Create a cluster of three or more Telemetry Servers
# true - Creates a Telemetry Server cluster
# false - Configures Telemetry Server as a single node.
# The default value is false.
### TelemetryServer.cluster.enable=<value>
# Provide the Fully Qualified Domain Name of the local Telemetry Server (do not use "localhost"
# or the loopback IP address "127.0.0.1")
### TelemetryServer.cluster.localnode=<value>
# Provide the Fully Qualified Domain Name of all the remote Telemetry Servers that you have
# installed or will install. Separate the Fully Qualified Name using semicolons.
# For example: node.mydomain.com; othernode.mydomain.com
### TelemetryServer.cluster.remotenodes=<value>
## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ##
#
# Topology Configuration
#
# The Workstation Topology helps administrators to monitor and manage services
# in a MicroStrategy environment.
# Indicate cluster environment.
# SINGLE - Choose this option if this is the only machine where the MicroStrategy
# services including Intelligence, Web Universal, Library, Mobile, Telemetry
# Server, Platform Analytics, Certificate Store will be
# installed for this environment. No other machines will have any of these
# services installed.
# MULTIPLE - Choose this option if the MicroStrategy services listed above will
# be installed on multiple machines in this environment.
#
# The default value for this setting is "SINGLE"
### ServicesRegistration.machine.environment=<value>
# Enter the fully qualified domain name for one Intelligence machine below.
# To setup a fault tolerant configuration during this installation or later,
# review the online help.
# https://www2.microstrategy.com/producthelp/current/InstallConfig/WebHelp/Lang_1033/Content/topology_install.htm
#
# Note: This machine must be able to communicate with other machines in this
# environment on ports 8300 & 8301.
#
# Important: During the installation of a multiple machine environment, the value
# above needs to be entered exactly the same for each machine in the environment.
### ServicesRegistration.serverHosts=<value>
## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ##
# Registering as a service
#
# Register MicroStrategy processes as a service so that processes automatically
# start up after system startup.
# Legal values are:
# true
# false
# Note: Only root users may register processes as a service.
### RegisterServices=<value>
## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ##
# Registering as a service
#
# Use this user to start the services (optional)
### RegisterServices.user=<value>
### RegisterServices.group=<value>
## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ##
#
# Hide Select Components dialog box
#
# Use this option to completely hide the product selection dialog during the
# execution of the MicroStrategy Installation Wizard. This option can be used
# in combination with individual product visibility/state options to have better
# control on the products to be installed/removed. If the dialog is not visible,
# and no specific visibility/state options have been specified, default values
# will be used.
# Legal values for this option are:
#
# true - Indicates that the Select Components dialog box will be visible
# false - Indicates that the Select Components dialog box will be hidden
#
# The default value for this setting is "true".
# SelectComponents.visible=<value>
## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ##
#
# MicroStrategy Product Visibility
#
# In the MicroStrategy Installation Wizard, the Select Components dialog box
# contains check boxes to select or clear for products to be installed. You
# can specify whether you want the following products to be visible to the user.
# Legal values are:
#
# true - Indicates that the product is selected for installation
# false - Indicates that the product is not selected for installation
#
# The default value for Selection state settings is "true".
#
# If a product is not visible, it will not be installed,
# independently of the value specified for its selection state (see the
# Product Selection State section).
#
# MicroStrategy Intelligence Universal Edition
### Intelligence.visible=<value>
# MicroStrategy Report Services Universal
### ReportServices.visible=<value>
# MicroStrategy OLAP Services Universal
### OLAPServices.visible=<value>
# MicroStrategy Distribution Services
### DistributionServices.visible=<value>
# MicroStrategy Transaction Services
### TransactionServices.visible=<value>
# MicroStrategy Web Universal Reporter
### WebReporter.visible=<value>
# MicroStrategy Web Universal Analyst
### WebAnalyst.visible=<value>
# MicroStrategy Web Universal Professional
### WebProfessional.visible=<value>
# MicroStrategy Portlets
### Portlets.visible=<value>
# MicroStrategy GIS Connectors
### GISConnectors.visible=<value>
# MicroStrategy Web Services J2EE
### WebServices.visible=<value>
# MicroStrategy Mobile Server JSP
### MobileServer.visible=<value>
# MicroStrategy Community Data Connectors
### CommunityConnectors.visible=<value>
# MicroStrategy Command Manager
### CommandManager.visible=<value>
# MicroStrategy Integrity Manager
### IntegrityManager.visible=<value>
# MicroStrategy System Manager
### SystemManager.visible=<value>
# MicroStrategy Platform Analytics
### PlatformAnalytics.visible=<value>
# MicroStrategy Enterprise Manager
### EnterpriseManager.visible=<value>
# MicroStrategy Telemetry Server
### TelemetryServer.visible=<value>
# New in 10.9
# MicroStrategy Library Web & Mobile
### LibraryWebMobile.visible=<value>
# New in 10.9
# MicroStrategy Collaboration
### Collaboration.visible=<value>
# New in 11.0
# MicroStrategy Certificate Store
### CertificateStore.visible=<value>
# New in 11.2
# MicroStrategy Export
### Export.visible=<value>
# New in 11.2
# MicroStrategy Repository
### Repository.visible=<value>
# New in 11.3
# MicroStrategy Cloud Object Connector
### CloudObjectConnector.visible=<value>
## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ##
#
# Install On Demand Options
#
## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ##
# The kind of remote location. The valid values are "FileSystem", "HTTP" or "HTTPS"
### InstallOnDemand.style=<value>
# The path to the remote location. Set this value if InstallOnDemand.style is set to "FileSystem"
### InstallOnDemand.sourceLocation=<value>
# The URL for HTTP or HTTPS styles. Set this value if InstallOnDemand.style is set to HTTP or HTTPS
### InstallOnDemand.url=<value>
# Use this setting to skip the certificate checking when using HTTPS. Valid values are "true" or "false"
### InstallOnDemand.bypassCertificateChecking=<value>
# The user name for HTTP or HTTPS styles. Set this value if InstallOnDemand.style is set to HTTP or HTTPS
# and the connection requires user name and password
### InstallOnDemand.user=<value>
# The password for HTTP or HTTPS styles. Set this value if InstallOnDemand.style is set to HTTP or HTTPS
# and the connection requires user name and password
### InstallOnDemand.password=<value>
# Configuration and Deployment Guide: http://www2.microstrategy.com/producthelp/2020/InstallConfig/en-us/Content/configuration_and_deployment.htm