Deploy DIGIPASS Gateway using web application files

If you want to just deploy the DIGIPASS Gateway web application to an existing web or Java application server, you can deploy one of the respective application files.

DIGIPASS Gateway is shipped in two different formats:

  • A web archive file (WAR) to be deployed to standalone web containers, e.g. Apache Tomcat.
  • An enterprise application archive file (EAR) to be deployed to regular Java application servers.

Before you begin

Make sure that you have either a Java application server supporting Java EE 7 or a web server installed and that it is working properly.

Deploy DIGIPASS Gateway using web application files

To deploy DIGIPASS Gateway using the web application file

  1. Deploy the web application file of the DIGIPASS Gateway web service, i.e. either dpgateway.war to the web server or dpgateway.ear to the Java application server accessible by the respective mobile application.

  2. Configure your web or Java application server to set the following Java system property on server (or web application) startup:

    -Dcom.onespan.dpgateway.config.file=properties_file

    where:

    • properties_file is the path and file name of the OneSpan Web Configuration Tool properties file, i.e. admintool.properties.
  3. Configure the DIGIPASS Gateway web service accordingly using the OneSpan Web Configuration Tool (see Configure DIGIPASS Gateway).
  4. Restart your web server or Java application server.

Upgrade DIGIPASS Gateway

When DIGIPASS Gateway is already installed and you deploy the web application file provided with the new version of the DIGIPASS Gateway package, the product is upgraded automatically once the installation process is completed. The existing configuration settings of the product are preserved.

Supported upgrade path

The current supported upgrade path is from version 5.7 or 5.8 to version 5.9.0 on the supported operating systems.

Additional considerations

Since Java 8 Update 111, proxies requiring Basic authentication will no longer work, since this authentication scheme is disabled by default. If required, Basic authentication can be reactivated by adding the following parameter when starting the Java web application:

‑Djdk.http.auth.tunneling.disabledSchemes="" ...

This is the default behaviour of the Java Runtime Environment (JRE) running the Apache Tomcat web server deployed by the DIGIPASS Gateway installation packages.

Next steps

If required, verify and perform any post-installation task necessary to complete the installation (see Post-installation tasks and considerations).