This page describes the MRM BI installation process, installer interface, product components, and configuration options.

Process Overview

The installation process is broken into five stages:

1. Database Creation

2. Product Installation

3. Post Configuration – Activation & Product Settings

4. Statistics update

5. Completion

Prior to installation, it is important to back up the routing databases (Route Planner or Route Planner On-demand) as they will be modified by the installer.

If a problem is encountered, the user may be prompted to abort, retry or ignore. This prompt provides an opportunity for the user to correct the installation problem before continuing.

Ignoring an error may result in the failure of subsequent steps. In the case of a failure (or abort), the installation progress will stop and display in red.

At any time, an installation can be stopped by clicking the Cancel button; the installer will terminate as soon as possible, usually within a few seconds.

Install Progress and Results

This window provides feedback on the progress of the installation.

There is also an installation log file in the installation folder: {ComputerName}_InstallLog.txt.

Toolbar

The installer has a toolbar to help with saving or loading deployment configurations.

• Open: Allows opening a previous deployment configuration.

• Save: Allows saving of the current deployment configuration to a user-defined file.

• Refresh: Refreshes the installer configuration file (advanced).

Installer Utility

Execute the MRMBI-Setup.exe installation utility to begin installation.

Install Window

The following screenshot shows the standard installation screen.

When installation begins, the system first attempts to detect which products are installed (Descartes Route Planner only at this time). Deployment Configuration files can be saved or opened, and the last deployment configuration is automatically loaded on start-up.

Product Components

Mobile Resource Management Business Intelligence (MRM BI) has five installable products:

• BIStaging: Includes the database components required to store the data extracted from one or more routing products.

• BIReporting: Includes the database components required to store the data that has been staged and formatted for reporting. At this time, it must be stored in the same database as BIStaging.

• BIRPS: Includes the LNOS reporting services template sources, caches, and reports.

• RoutePlanner: Includes the database components required to extract the routing information for Descartes Route Planner. These components will be deployed into the existing organization databases.

• OnDemand: Includes the database components required to extract the routing information for Descartes Route Planner On-demand. These components will be deployed into the existing organization databases.

Installation Actions

Install/Cancel: This action performs a new installation of the application. While the installation proceeds, the Install button will change to a Cancel button.

Config Only: This action updates the configuration elements and activates the products enabled, provided they have already been installed.

Product Configuration Components

Each product has its own configuration properties. Not all configuration fields or screens are applicable to all products. The components are divided into several sections as described below.

Component Configuration

This component provides product-specific configuration details.

BIStaging, BIReporting, RoutePlanner, and OnDemand provide basic connection details to the SQL Server:

• SQL Server Name: Database server to which the components should be deployed.

• Database Name:

  • BIStaging & BIReporting: the database to create

  • Route Planner: the DCF database containing the pointers to the organization databases

  • OnDemand: N/A, see organization database details

• Credentials: Windows® or SQL authentication details.

• Refresh Orgs:

  • BIStaging & BIReporting: N/A

  • Route Planner: refreshes the list of organization databases from the DCF database

  • OnDemand: N/A

BIRPS

This component includes a list of which RPS items to import.

BI DB Properties (BIStaging & BIReporting Only)

This component applies to BIStaging & BIReporting products only.

Initial Size: Default size (MB) used when creating files for the database. If unspecified, the size will default to 100 MB.

Grow Amount: Determines the growth rate for the database (Pct or MB).

Existing DB Action: Determines the action based on whether the MRM BI database already exists or not.

• Upgrade if DB Exists (DEFAULT)

  • Will either upgrade existing database or create a new database.

• Fail if exists

  • Will fail if the database already exists.

• Use existing database

  • Will treat as a new installation but where the database already exists.

• Drop Existing database

  • Will drop the existing database and recreate it as a new installation.

Org Databases (Route Planner & OnDemand Only)

This component contains the list of routing product databases to be installed.

• Only databases marked as Enabled will be installed.

• Databases can be deleted by highlighting the row and pressing the Delete key on the keyboard or by right-clicking.

• New databases can be added by moving to the final row and typing in the database name.

• Database names can also be edited.

RPS Config (BI RPS Only)

This component provides additional configuration properties for RPS.

• URL: URL to use for loading RPS items imports.

• Company/Login/Group/Password: LNOS credentials to use for imports.

Product Properties

When a product is selected, the most common properties will be listed with their default values. Additional advanced properties can also be configured.

Install — BIStaging & BIReporting only

• PrimarySQLFilePath: If not specified, will be determined automatically using SQL defaults.

• StagingSQLFilePath: SQL file for routing product staging tables. If not specified, will be determined automatically using SQL defaults.

• LogSQLFilePath: If not specified, will be determined automatically using SQL defaults.

SysValue — BIStaging

• LoadingDatabase: Name of the BIReporting database (presently must be the same as BIStaging).

• LoadingServerName: Target SQL Server hosting the BIReporting database (should not be used at this time).

• LoopbackServerName: SQL Server linked server name used for logging (will be automatically created if it does not exist).

SysValue — BIReporting

• MinPeriodToKeep: Maximum number of months to retain data (negative = past), default = 6.

• MaxPeriodToKeep: Maximum number of months to retain data (positive = future), default = 1.

• LoopbackServerName: SQL Server linked server name used for logging (will be automatically created if it does not exist).

SysValue — Route Planner & OnDemand

• StagingDatabase: Name of the BIStaging database.

• StagingServerName: Target SQL Server hosting the BIStaging database, if not the same server.

• LoopbackServerName: SQL Server linked server name used for logging (will be automatically created if it does not exist).

BIProductConfig — Route Planner

• TimeWindowJeopardyThresholdMin: Determines how many minutes before the end of the window will be used to determine "on time" (based on TimeWindowOnTimeMode), default = 15.

• CheckCapacityViolation: Determines whether capacity violations will be checked.

  • ON (1): capacity checks are enabled (Default)

  • OFF (0): capacity checks are NOT enabled

• TimeWindowOnTimeMode: Determines how late, jeopardy jobs or stops are calculated.

  • Arrive and Finish within (1): must arrive AND finish within the time window (Default)

  • Arrive Early, Finish within (2): can arrive early but must finish within the time window

  • Arrive or Finish On/Before (3): can arrive or finish early, must not be late

Advanced

This tab displays advanced installer settings (not product specific).

• BI DB Install Path: Overrides the location for install deployment files.

• Update SQL Statistics: When enabled, the system will recompute statistics after installation to maximize performance (on by default).

Back to top