The smartWeb platform is implemented as an application for the Java EE application server Tomcat running on the Java platform. This application server is also part of the D2000 installation and runs on Java delivered with the D2000 version. In the first step, it is necessary to decide whether we want to install Smart Web. On a Tomcat server supplied within the D2000 or on the separately managed Tomcat server independent of the D2000. Both alternatives have their advantages and disadvantages, which can be summarized as follows:
Feature | Tomcat within the D2000 | Standalone Tomcat Server |
---|---|---|
Easy to deploy | Tomcat does not need to be installed and managed separately from the D2000 because it runs as a D2000 process with a .WSC extension | Tomcat must be installed and managed independently of the D2000 |
Deployment flexibility in the DMZ | Deployment in a DMZ is not appropriate due to the need to install and configure a separate instance of D2000 | Ideal for stand-alone installation in DMZ |
Ad-hoc upgrade Tomcat Server | upgrade Tomcat is tied with the D2000 | Tomcat can be upgraded ad-hoc independently of the D2000 |
The installation procedure is as follows:
D2000_EXE/templates/config/proc/_.wsc
in to the folder D2000_APP/<application name>/config/proc/
_.wsc
to the self.wsc
D2000_EXE/web/smartWeb.war
to the folder D2000_APP/<application name>/config/proc/self.wsc/base/webapps/
D2000_EXE/web/tutorial-application.zip
to the folder D2000_APP/<application name>/config/proc/self.wsc
d2connector.exe
from D2000_EXE/bin folder
wssc.exe
from D2000_EXE/bin folder
The installation procedure is as follows:
D2000_EXE/web/smartWeb.war
in to the webapps
Tomcat folderD2000_EXE/web/tutorial-application.zip
to the Tomcat parent folderd2connector.exe
from D2000_EXE/bin folder
To change the context directory of a URL link from http://localhost:8080/smartweb to the, for example, http://localhost:8080/myApp you need to do the following: