Kbase 18441: HTTP Tunneling Support In Apptivity 2.1 - Using A Firewall
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
10/16/2008 |
|
Status: Unverified
FIX:
1) If you are running the Apptivity Server on a separate machine from the Web server, you must install the Apptivity Server on both machines, but only the Connection Manager (abConnectionMgr) and the Monitor need to be running on the Apptivity Server machine.
2) Copy the Apptivity Servlet files
(abHttpServlet, abHttpServlet$httpPipe and parameters.txt)
from the \Apptivity21\redist\servlet directory to the servlet directory on your Web server. Ensure that the Apptivity runtime classes are in the servlet classpath.
3) If the Monitor is installed on a different machine than the Web server, you must modify the parameters.txt file to specify the host, servicepath and serviceport as follows:
host = Monitor_HostName
<Monitor_HostName> is the name of the machine on which the Monitor is running
servicepath = Web_server_alias
<Web_server_alias> is the Web server alias to the Apptivity.Port file
serviceport = Monitor_Port
<Monitor_Port> is the Monitor port number (if the servicepath parameter does not point to the location of the Apptivity.Port file)
4) Configure the Apptivity Servlet startup options using your third party Web servlet configuration tool. Set the init arguments for abHttpServlet to:
abServletRoot = parameters.txt_path
<parameters.txt_path> is the path to the parameters.txt file
5) Deploy your Apptivity application to the Web server as explained in Chapter 19, "Deploying Applications," in the Apptivity Developer's Guide. Additionally, modify your Apptivity applet HTML page to include the following PARAM NAME and VALUE:
<PARAM NAME=connection VALUE=http_only>
You can use http_fallback as the VALUE if you want your application to connect using HTTP in case of a socket connect failure. socket_only is another option and this is the default.
6) If the Apptivity Server and the Web server are on different machines, you need to move the .qry file and any server event classes to the Apptivity Server machine, and modify the qrypath parameter for the applet.
NOTE: HTTP tunneling should only be used if the applet cannot be deployed using the default socket configuration.
FIX:
References to Written Documentation:
Apptivity 2.1 Release Notes