You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 9 Next »

This instruction is for installing a fresh new instance of the DualShield backend server or all-in-one server.

To start the installation, execute "DualShieldSetup64-xxx.yyyy-signed.exe", where xxx is the version number and yyyy is the build number, e.g. "DualShieldSetup64-6.0.0.0228-signed.exe"


DualShield 6 supports multiple languages. However, in the first release, version 6.0.0, language translation has not yet been completed. Please select English for now.




You may install DualShield on a different drive, in a different folder. However, it is recommeded to use the default drive and folder as suggested, for the sake of simplicity and transparancy in future communications. 


Option 1: All-in-One ServerOption 2: Slim Backend Server

If you want to install a DualShield server that is to be used as both the backend and frontend, then you need to install all of its component. 

Select "All Components"

If you want to install a DualShield server as a pure backend server without the end-user services, then you can keep it slim.

Select "Back-end Components"

If you would like to install the legacy components, then select them.

If you select lthe lagacy management server and/or self-service server, then you must also select the legacy SSO server. 

If you would like to install the legacy components, then select them.

If you select lthe lagacy management server, then you must also select the legacy SSO server. 


Server FQDN

Enter here the FQDN to be used for this DualShield server. Please choose the FQDN wisely and correctly, as it would be difficult to change after the instalation. 

A DualShield server must be given a unique Fully Qualified Domain Name (FQDN) which is provided in the installation process.

The DualShield server includes several web consoles, including

  • Admin Console
  • User Console
  • Single Sign-On Console (mainly used for SAML SSSO)
  • Deployment Console (for device and tokens)

DualShield consoles are all web-based portals that can be accessed with a web browser. The FQDN is the web address of the DualShield consoles. 

If the DualShield server is a backend server located in the internal network and to be accessed from internal PCs and workstations, then the DualShield's FQDN must be added into the internal DNS server.

If the DualShield server is a frontend server located in the DMZ and to be accessed from external PCs and workstations, then the DualShield's FQDN must be added into the external DNS server.

If the DualShield server is an all-in-one server that is accessed from both internal & external PCs and workstations, then its FQDN must be added into both the internal & external DNS servers. 

Use SSL to access DualShieldYou can install a DualShield without SSL. However, it is highly recommended that you should select "Use SSL to access DualShield", particularly if this is going to be used as a production server.
Create a self-signed certificateA certificate is to be used for DualShield web consoles and portals. You may use a self-signed certificate, however it is highly recommended that you should provide a commercial SSL certificate, particularly if this is going to be used as a production server.










DualShield is a set of JAVA server applications. After the installation, upgrade or restart of the DualShield servers, The OS needs to initialise the JAVA virtual machine (JVM) and load the DualShield application into the JVM. This process can be slow and take a long time, depending on the speed and power of the machine. 


To wait for the DualShield server to be fully loaded and monitor the its initialisation progress, launch the Windows Task Manager and check the process called DualShield Server which is often a sub-process of Commons Daemon Service Runner, as shown below:

During the initialisation process, the CPU usage of the DualShield Server process will go up and down, and the Memory consumption will continue to increase.

When the CPU usage drops to zero or slightly above zero, and the memory consumption reaches close to 1.8GB for the backend or 550MB for the frontend, that's the indication that DualShield is fully loaded and ready for operation. 


















  • No labels