Before Installing

Guidelines to follow before installing all Expere Engine components.

Attention: Read the following before beginning the implementation process.

Perform a clean installation

If you have previously installed the Expere Engine, you will need to remove any old version files before beginning the implementation process. Perform the following:

If installing using the same folder as the previous version:

  1. Make a copy of the following files as these files contain settings that likely should be preserved with the new install:
    • bsi.properties
    • log4j2.xml
    • Web.Config
  2. Navigate to Add/Remove programs and uninstall Expere Components.
  3. Navigate to the install location and manually remove any remaining files.
    • If some files cannot be deleted you many need to stop the Expere application pool. Do not install the new version of Expere until you have deleted the remaining files.
  4. Install the new Expere.
  5. Copy the files that were saved above, after confiriming that the new Expere does not add new properties that require changing.
  6. Restart the Expere application pool.

If installing in a new folder:

  1. Stop the old application pool.
  2. Copy the following files from the previous Expere instance after verifying the new Expere does not add new properties that require changing.
    • bsi.properties
    • log4j2.xml
    • Web.Config
  3. Restart the new Expere application pool.
Note: Consider the following:
  • A disadvantage exists if installing in a new folder: the URL used to access Expere includes the name of the folder Expere is installed in. This install method therefore changes the Expere URL. However, you have the option of stopping the new Expere application pool and starting the old Expere application pool if you need to test or rollback to the old Expere.

Database Information

The Expere Knowledge Base can either be stored on Microsoft SQL Server or referenced directly on the file system. Licensing requirements for the database system are dependent upon the middleware and application layer configuration specific to the implementation. If applicable: a review of the contractual licensing terms and conditions governing use of SQL Server database is warranted prior to installing Expere.

The implementation of the data structure and creation of the required tables, accounts, and permissions is accomplished via packaged scripts provided with the Expere installation media.

.NET Uers: SQL Server DSL Installer Requirement

When running the SQL Server DSL installer, it will not function unless the client on which the installer is being run has the SQLCMD.exe (even when using the installer GUI). The SQLCMD.exe prerequisite can be obtained by installing the SQL Server Express tools (no need for the actual database) on the client machine.

Installing a C++ Library

Before installing all Expere components, users must download and install the latest version of vcredist_x64.exe for Visual C++ Redistributable Packages for Visual Studio 2013.

Upon installing this file, users must restart IIS.

Step 1: Assemble all components required for installation

  • If installing the Expere Authoring Environment, assemble the Expere Installation Package for the Expere Authoring Environment (located on the Expere installation media. Consult the Expere Authoring Guide for further information).
  • Workstation from which to perform installation and content load
  • .NET Users: SQL Server Express, Standard, or Enterprise or File System
  • Java Users: SQL Server Express, Standard, or Enterprise or File System

Installing multiple Expere .NET or WildFly versions on the same server

If installing multiple Expere .NET or WildFly versions on the same server, you must modify the following files:
  • log4j2.xml: this file controls the following log files:
    • ExpereServices.log
    • ExpereIEServicesRequests.log
    • Erl.log

    Ensure that if multiple Expere versions are installed on the same server, the logging file locations are unique.

  • ehcache.xml: by default this file contains “<diskStore path="java.io.tmpdir"/>”. Ensure that this location is unique if multiple Expere versions are installed on the same server.