Expere Engine 2016.3 Release

The 2016.3 release contains several enhancements, including a new <SignerEmail/> element; a new </eSignatureWKES> acroform field used with fillable text fields; logging enhancements; and the ability to configure DPI for PDF417 Ancillary Barcodes. For detailed information, see the Current Release Change Log Entries section below and Expere Engine and Tools Change Log Entries.

*** Expere Engine 2016.2.2 Release ***

Important: This Expere Engine 2016.2.2 release impacts all users who received the Expere Engine release shipped on August 4th and September 1st. Users should install 2016.2.2 to implement the change outlined below.

The 2016.2.1 Expere Engine release update is reestablishing Expere processing of XML using XPath 1.0 compatibility mode. The 2016.2 Expere Engine release changed the processor to Xpath 2.0, this release update is to reintroduces the previous behavior that enabled XPath 1.0 compatibility mode and makes it the default. Users should install the 2016.2.2 Expere Engine release rather than the 2016.2. Expere Engine update provided on August 4th and September 1st.

The 2016.2.2 release also includes the latest version of the Organizational Policy and Product Setup Application (OPPSA).

.NET Installation Enhancement

For .NET Expere Implementations, users must download and install vcredist_x64.exe available from Microsoft Visual C++ 2010 Service Pack 1 Redistributable Package MFC Security Update before installing the Expere Engine and related components. After installing this file, users must restart IIS.

For more information, refer to Before Installing - .NET Users: Java 8 Requirement in the Expere Implementation Guide.

***Expere 2016.2 Engine Release - Important update regarding Java 8 and Saxon upgrade: DB and File System script process***

We have recently implemented Java 8, Saxon, and stylesheet upgrades; with these upgrades, users must run a script to remove duplicate imports for the database and file system.

Note: The following scripts are available on your release media in the Scripts folder. The supporting installation documents are available on our webhelp server; click the appropriate link for more information:
  • RemoveDuplicateImports.ps1: for File System users using a Powershell script.
  • Process-for-file-system-ps.pdf
  • RemoveDuplicateImportsOracle.ps1: for Oracle SQL users who prefer to use a Powershell script.
  • Process-for-Oracle-ps.pdf
  • RemoveDuplicateImportsOracle.sql: for Oracle SQL users who prefer to use a SQL script rather than a Powershell script.
  • RemoveDuplicateImportsSQL.sql: for Microsoft SQL server users who prefer to use a SQL script rather than a Powershell script.
  • Process-for-SQL-scripts.pdf; this procedure applies to both Oracle and Microsft SQL server users.
  • RemoveDuplicateImportsSQL.ps1: for Microsoft SQL server users who prefer to use a Powershell script.
  • Process-for-SQL-ps.pdf

Important update regarding the Expere Config Tool

It was reported that there is an issue with running Expere Config Tool utility. We are currently working on the fix and will make it available soon. In the meantime, the following Expere Config Tool utility configuration files can be updated manually using a text editor:

  • bsi.properties: located at: "C:\inetpub\wwwroot\Expere\bin\bsi.properties"
  • web.config.xml: located at "C:\inetpub\wwwroot\Expere\Web.Config"
  • log4j.xml: located at "C:\inetpub\wwwroot\Expere\bin\log4j.xml"

To update the Database Settings, navigate to the bsi.properties file; update the following database settings:

  • (Hostname) com.bankerssystems.expere.db.Host=""
  • (Port) com.bankerssystems.expere.db.Port=""
  • (Database) com.bankerssystems.expere.db.Sid=""
  • (Username) com.bankerssystems.expere.db.User=""
  • (Password) com.bankerssystems.expere.db.Pass=""

To update logging, navigate to log4j.xml file; update the following:

  • (Filepath) <param name="File" value="Expere/ExpereIEServicesRequests.log"/>
  • (Level) Uncomment out the following: 
     <logger name="com.bankerssystems">
 <level value="info" />
 </logger>
    Available options for level value include:
    • info
    • error
    • fatal
    • debug
    Attention: Only one value can be set.

To update the Performance Options, navigate to web.config file, update the following:

  • (Min JVM Heap Size - MB) <java.option value="-Xms256m" />
  • (Max JVM Heap Size - MB) <java.option value="-Xmx512m" />:
Note: Max Cached Object is no longer applicable.

To update the following Certificate Settings, navigate to the bsi.properties.xml file; update the following settings:

  • (Key Store Type) keystore.type=""
  • (Key Store Provider) keystore.provider=""
  • (Key Store URL) keystore.url=""
  • (Key Store Password URL) keystore.password.url=""
  • (Private Key Password URL) keystore.privatekey.password.url=""
  • (Certificate Alias) tamperseal.certificate.alias=""

Current Release Change Log Entries

DocViewer release notes

DocViewer Release Notes: PDF compilation of current and previous release notes.

WKFS