This section outlines the details of wscservice.war deployment on Apache Tomcat (static files and all requests to engines are served) or binding only static files and the rest of the service requests such as spelling or grammar checking, directly connecting with AppServer. For direct connection with AppServer: 1. Modify Apache Tomcat configuration server.xml file. 2. Stop Apache Tomcat before modifying the configuration files. 3. Add the following paths to the server.xml file inside the <Host name=“localhost” appBase="webapps" unpackWARs="true" autoDeploy="true"> tag: Here are additional required steps when installing WebSpellChecker on Java Application Servers (Apache Tomcat): 1. Set and check the WSC_DIR environment variable: 2. Specify WSC_DIR environment variable. It must be pointed to the WebSpellChecker Server installation directory (for example, WSC_DIR=/opt/WSC). 3. Deploy WebSpellChecker Server on your Apache Tomcat Application Server. Note that the wscservice.war file should be unpacked automatically. Otherwise, unpack it manually.Step 8: Choose Web or Application Server type.
Select a particular web or application server which will be used for the WSC application server running.
1. Apache HTTP Server
2. Java Application Server (Apache Tomcat, Oracle WebLogic Server, Oracle GlassFish Server, etc.)
3. Other
Input the number from 1 to 3: 2
Option A: Binding of Static Files and Serving Service Requests by AppServer
<Context docBase="/opt/WSC/WebComponents/WebInterface" path="/wscservice" />
<Context docBase="/opt/WSC/WebComponents/Samples" path="/wscservice/samples" />
Option B: Serving both Static Files and Service Requests by Java Application Server (deployment of wscservice.war)
export WSC_DIR=/opt/WSC
echo @WSC_DIR