Install > Install ITBA > Silent Installation

Silent Installation

You can install ITBA using a silent installation (see below), a console installation, or a GUI installation.

Install ITBA using a silent installation

Important Save the values of the parameters in this page. The Glassfish Administrator password is also used to log on to the ITBA Maintenance tool. The Application authentication password is also used as your ITBA logon credentials.

To install ITBA using the silent installation, proceed as follows:

  1. Create a user or use an existing user.

    Important Make sure you are not using the root user to perform the installation.

  2. Log on to the Linux server where you want to install ITBA.

  3. Download the ITBA-10.10.XXX.tar.gz file from the Support Site (https://softwaresupport.hpe.com/group/softwaresupport/home?lang=en-US) and save it in your Linux target directory.

    Download the ITBA-10.10.XXX.tar.gz file from the Support Site (https://softwaresupport.hpe.com/group/softwaresupport/home?lang=en-US) and save it in your Linux target directory.

    • Make sure the installation target directory has adequate disk space. For details, see ..
    • Make sure that the owner of the Extractor directory is ITBA installer account.

    Make sure that the path to the target directory does not include blank spaces, brackets (or), or single quotes (').

  4. Run the tar -zxvf ITBA-10.20.XXX.tar.gz command to unzip the ITBA-10.20.XXX.tar.gz file.

  5. Run the tar -zxvf ITBA-10.10.XXX.tar.gz command to unzip the ITBA-10.10.XXX.tar.gz file.

  6. Go to the Linux user path directory where you unzipped the installation file, and run ./install.sh -a or sh install.sh -a to generate the ba-answer.xml file.

    Go to that folder and run install.sh -a to generate the answer file.

    <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<config>
    <section name="PreCheck" description="This section is responsible for filling in the pre-condition values">
        <field id="install.PRODUCT_AGREEMENT" description="Use 'Yes' to accept the product announcement. Otherwise, use 'No'. 'No' aborts the installation">
            <name>ProductAgreement</name>
            <value>Yes</value>
        </field>
        <field id="install.LICENSE_IS_EVALUATION" description="The product license type. Use 'true' when you don't have a valid license and you want to get an evaluation license. Use 'false' to load your Power Named User License or to use a temporary license">
            <name>productTypeFlag</name>
            <value>true</value>
        </field>
        <field id="install.LICENSE_POWERUSER_FILE_PATH" description="The path to the license file of the power user for the installation. It only take effect only if LICENSE_IS_EVALUATION is 'false'">
            <name>LicenseFilePathOfPowerUser</name>
            <value></value>
        </field>
        <field id="install.LICENSE_VIEWER_FILE_PATH" description="The path to the viewer license file. Note that your Power User license must be valid. It only take effect only if LICENSE_IS_EVALUATION is 'false'">
            <name>LicenseFilePathOfViewer</name>
            <value></value>
        </field>
    </section>
    <section name="DWH" description="This section is responsible for filling in the property values for DWH">
        <field id="bo.cms.import.xs.license" description="To import the XS license to SAP BOE use 'true'. Otherwise, use 'false'">
            <name>importBALicenseToSAPBOE</name>
            <value>false</value>
        </field>
        <field id="bo.engine.is.installed" description="If BOE is installed, input 'true'. Otherwise, input 'false'. Note: only BOE version BOE4.0SP6 or later is currently supported">
            <name>boe install status</name>
            <value>false</value>
        </field>
        <field id="bo.engine.logon.auth.type" description="Indicates the BOE logon auth type:[secEnterprise,secLDAP,secWinAD,secSAPR3,secPSE1,secOraApps,secpsenterprise,secSiebel7]">
            <name>boe logon auth type</name>
            <value>secEnterprise</value>
        </field>
        <field id="bo.cms.host.name" description="The name of the BOE server on which the that you want to connect with is installed">
            <name>boe HostName</name>
            <value></value>
        </field>
        <field id="bo.cms.host.port" description="The port number of the CMS listener">
            <name>boe port</name>
            <value></value>
        </field>
        <field id="bo.cms.sso.shared.secret" description="The path to the file that contains BOE shared secret">
            <name>boe shared secret</name>
            <value></value>
        </field>
        <field id="bo.cms.admin.userName" description="The user name for the SAP BusinessObjects Enterprise administrator">
            <name>boe username</name>
            <value></value>
        </field>
        <field id="bo.cms.admin.user.pw" description="The password of the BOE admin user">
            <name>boe password</name>
            <value></value>
        </field>
        <field id="bo.cms.opendoc.port" description="The BOE Tomcat port used to display the BOE reports in Scorecard (usually 8080)">
            <name>Tomcat port</name>
            <value></value>
        </field>
        <field id="install.dwh.HOST_NAME" description="The DWH server host name">
            <name>HostName</name>
            <value>HostName</value>
        </field>
        <field id="install.dwh.PORT" description="The DWH server port number">
            <name>Port</name>
            <value>5433</value>
        </field>
        <field id="install.dwh.DATABASE_NAME" description="The name of the Vertica database instance that is used as the data warehouse">
            <name>VerticalDatabaseName</name>
            <value>xsvertica</value>
        </field>
        <field id="install.dwh.LOGIN_NAME" description="The DWH logon name which should have schema creation permissions">
            <name>LoginName</name>
            <value>vertica</value>
        </field>
        <field id="install.dwh.PASSWORD" description="The DWH password name">
            <name>Password</name>
            <value></value>
        </field>
        <field id="install.dwh.SOURCE_STAGING_SCHEMA_NAME" description="The source staging schema name of the DWH">
            <name>SourceStagingSchemaName</name>
            <value>dws</value>
        </field>
        <field id="install.dwh.TARGET_STAGING_SCHEMA_NAME" description="The target staging schema name of the DWH">
            <name>TargetStagingSchemaName</name>
            <value>dwst</value>
        </field>
        <field id="install.dwh.TARGET_SCHEMA_NAME" description="The target schema name of the DWH">
            <name>TargetSchemaName</name>
            <value>dwt</value>
        </field>
        <field id="install.dwh.RESULT_SCHEMA_NAME" description="The result schema name of the historical result">
            <name>ResultSchemaName</name>
            <value>dbo</value>
        </field>
        <field id="install.dwh.EXTENSION_SCHEMA_NAME" description="The extension schema name of the imported external xls,xlxs,and csv tables">
            <name>ExtensionSchemaName</name>
            <value>ext</value>
        </field>
        <field id="install.dwh.APPLICATION_SCHEMA_NAME" description="The application schema name of the DWH">
            <name>ApplicationSchemaName</name>
            <value>BA</value>
        </field>
        <field id="install.dwh.TIMEZONE" description="The timezone value. Use the international standard TimeZone name">
            <name>AppTimeZone</name>
            <value>Asia/Shanghai</value>
        </field>
        <field id="install.dwh.CURRENCY" description="The default currency for DWH. Use the standard of ISO 4217">
            <name>currency</name>
            <value>USD</value>
        </field>
        <field id="install.dwh.period_dim.FIRST_YEAR" description="The first year for the initial period dimension loading">
            <name>FirstYear</name>
            <value>2005</value>
        </field>
        <field id="install.dwh.period_dim.LAST_YEAR" description="The last year for the initial period dimension loading">
            <name>LastYear</name>
            <value>2025</value>
        </field>
        <field id="install.dwh.period_dim.FIRST_DAY_OF_WEEK" description="The first day of week.[Sunday,Monday,Tuesday,Wednesday,Thursday,Friday,Saturday]">
            <name>FirstDayOfWeek</name>
            <value>Monday</value>
        </field>
        <field id="install.dwh.period_dim.FISCAL_YEAR_START_MONTH" description="The fiscal month offset for the initial period dimension loading. Use the 1-12 format">
            <name>FiscalYearStartMonth</name>
            <value>1</value>
        </field>
    </section>
    <section name="Application" description="This section is responsible for filling in the property values for the application">
        <field id="install.app.webserver.HTTP_PORT" description="The http port number for the web server">
            <name>HttpPort</name>
            <value>2024</value>
        </field>
        <field id="install.app.webserver.HTTPS_PORT" description="The https port number for the web server">
            <name>HttpsPort</name>
            <value>8443</value>
        </field>
        <field id="install.app.xs.USER_NAME" description="The user name for the administrator. Use this user to log on to IT Business Analytics for the first time">
            <name>UserName</name>
            <value>administrator</value>
        </field>
        <field id="install.app.xs.PASSWORD" description="This password that is used only to log on to BA">
            <name>Password</name>
            <value>Admin111</value>
        </field>
        <field id="install.app.glassfish.PASSWORD" description="The password to log on to the Glassfish admin console">
            <name>Password</name>
            <value>Admin111</value>
        </field>
        <field id="USAGE_TRACKING_SETTINGS" description="Use Usage Hub to track license usage or not">
            <name>UsageTrackingSettings</name>
            <value>true</value>
        </field>
        <field id="USAGE_HUB_URL" description="Usage Hub Host/IP">
            <name>Usage_Hub_Host</name>
            <value></value>
        </field>
    </section>
</config>

    Enter, in the ba-answer.xml file, the relevant values between the <value> and </value> tags. The values are listed below:

    <Name> <Value>
    install.PRODUCT_AGREEMENT
    • Yes - to accept the product announcement.
    • No - to abort the installation.
    install.LICENSE_IS_EVALUATION

    true - when you don't have a valid license and you want to get an evaluation license.

    false - to load your Power Named User License or to use a temporary license.
    install.LICENSE_POWERUSER_FILE_PATH The path to the license file of the power user for the installation. It takes effect only if LICENSE_IS_EVALUATION is 'false'.
    install.LICENSE_VIEWER_FILE_PATH

    The path to the viewer license file. Note that your Power User license must be valid.

    It takes effect only if LICENSE_IS_EVALUATION is 'false'
    bo.cms.import.xs.license

    true - to import the ITBA BOE license to SAP BOE server.

    false - use otherwise.
    bo.engine.is.installed

    true - If BOE is already installed.

    false - if BOE is not already installed.

    Note Only BOE version BOE4.1SP3 or later is currently supported.
    bo.engine.logon.auth.type

    The authentication method for the SAP Business Objects BI platform: secEnterprise, secLDAP, secWinAD, secSAPR3, secPSE1, secOraApps, secpsenterprise, secSiebel7.

    Default: [secEnterprise].
    bo.cms.host.name

    The name of the BOE server to which you want to connect.
    bo.cms.host.port The port number of the CMS listener (usually 6400).
    bo.cms.sso.shared.secret The absolute file path that includes the SSO shared secret password of BOE.
    bo.cms.admin.userName The user name for the SAP BusinessObjects Enterprise administrator.
    bo.cms.admin.user.pw The SAP BusinessObjects Enterprise Administrator password.
    bo.cms.opendoc.port The BOE Tomcat port used to display the BOE reports in Scorecard (usually 8080).
    install.dwh.HOST_NAME

    The fully qualified domain name (FQDN) or IP address of the vertica server.

    If you setup ITBA with a multiple nodes Vertica database, enter the FQDN or IP address of any one permanent node if load balancing isn't configured, or if load balancing is configured with a native connection. If load balancing is configured using IPVS, enter the Virtual IP address.
    install.dwh.PORT The Vertica port.
    install.dwh.DATABASE_NAME The Vertica database name.
    install.dwh.LOGIN_NAME The Vertica user name.
    install.dwh.PASSWORD The Vertica password.
    install.dwh.SOURCE_STAGING_SCHEMA_NAME The name of the source staging schema
    install.dwh.TARGET_STAGING_SCHEMA_NAME The name of the target staging schema.
    install.dwh.TARGET_SCHEMA_NAME The name of the target schema.
    install.dwh.RESULT_SCHEMA_NAME The name of the result schema.
    install.dwh.EXTENSION_SCHEMA_NAME The name of the extension schema.
    install.dwh.APPLICATION_SCHEMA_NAME The name of the application schema
    install.dwh.TIMEZONE The Data Warehouse time zone used when consolidating the data extracted from the data sources.
    install.dwh.CURRENCY The default currency for DWH. Use the standard of ISO 4217.
    install.app.webserver.HTTP_PORT The http port number for the web server.
    install.app.webserver.HTTPS_PORT The https port number for the web server.
    install.app.xs.USER_NAME The ITBA administrator user name. Use this user to logon to ITBA.
    install.app.xs.PASSWORD The ITBA administrator password.
    install.app.glassfish.PASSWORD The password to log on to the Glassfish admin console.
    USAGE_TRACKING_SETTINGS

    true - To use Usage Hub to track license usage or not.

    false - To not use Usage Hub to track license usage.
    USAGE_HUB_URL The Usage Hub server Host/IP

    Tip Make sure to save securely the glassfish password and application username and password for further use.

    Note First day of the week

    In Data Warehouse, the first day of the week is set during the installation, and the Period tool is using it as an input to build PERIOD_DIM days, weeks, months, and more, as well as relevant hierarchies.

    After the administrator has installed Data Warehouse, the administrator selects the designated first-day-of-week. If a data source has a different first-day-of-week definition, the administrator should be aware that for weekly periodicity, the linkage to the period key uses the Data Warehouse week definition and not the data source week definition.

    For details about currency, see Currency.

    For details about the time zone, see Time Zones.

  7. Run./install.sh -s or sh install.sh -s to start the ITBA installation.

Tip Make sure to install the Supervisor. For details, see Install the Supervisor After the Installation

Send Help Center feedback