--- title: "Deploy DIGIPASS Gateway using web application files" slug: "dpgw-gsg-deploy-digipass-gateway-using-web-application-files-5-11" updated: 2025-07-04T10:05:55Z published: 2025-07-07T16:28:37Z canonical: "docs.onespan.com/dpgw-gsg-deploy-digipass-gateway-using-web-application-files-5-11" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.onespan.com/llms.txt > Use this file to discover all available pages before exploring further. # 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 a web server or Java application server installed that supports Jakarta EE 10 and JDK 17 and is working properly. - To deploy on Open Liberty or WebSphere Liberty, ensure that you choose a version that supports Jakarta EE 10 and JDK 17. Note that by default, Java EE 8 is used, and you need to explicitly enable Jakarta EE 10 in the web application server configuration file (server.xml): ```xml  jakartaee-10.0 ``` - To deploy on Eclipse Jetty, ensure that you choose a version that supports Jakarta EE 10 and JDK 17, and include the following modules: To add these modules, you can use the following command: java -jar "$JETTY_HOME/start.jar" --add-modules=ee10-deploy,ee10-cdi,ee10-websocket-jakarta - ee10-deploy - ee10-cdi - ee10-websocket-jakarta ## 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](/sec/docs/dpgw-gsg-configure-digipass-gateway-5-11)). 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. ## Additional considerations > Proxies that require Basic authentication will not work out of the box, since this authentication scheme is disabled by default. If required, basic authentication can be activated 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](/sec/docs/dpgw-gsg-post-installation-tasks-and-considerations-5-11)).