Appboard/2.4/admin/enabling cgi: Difference between revisions

imported>Jason.nicholls
No edit summary
imported>Jason.nicholls
No edit summary
Line 5: Line 5:
{{Warning|Enabling CGI can introduce additional load on the AppBoard server and raises it's own security concerns. This document simply covers enabling CGI but thought should go into the issues mentioned.}}
{{Warning|Enabling CGI can introduce additional load on the AppBoard server and raises it's own security concerns. This document simply covers enabling CGI but thought should go into the issues mentioned.}}


To enable CGI follow these steps:
=== Steps to Enable CGI ===


# Edit <tt>[INSTALL_HOME]/server/conf/web.xml</tt>
# Edit <tt>[INSTALL_HOME]/server/conf/web.xml</tt>
Line 14: Line 14:
## add the parameter <tt>privileged="true"</tt> to the <Context ... > tag on line 19.
## add the parameter <tt>privileged="true"</tt> to the <Context ... > tag on line 19.
## save changes.
## save changes.
## create the directory <tt>[INSTALL_HOME]/server/webapps/enportal/WEB-INF/'''cgi'''</tt>
# Restart AppBoard.
# Restart AppBoard.


{{Note|Changes to <tt>web.xml</tt> and <tt>context.xml</tt> are '''not''' archived by default. While it's possible to change the archive properties files and include these files they are considered systems files and may change release to release. In other words, on upgrade it must be verified the there are no changes to these files (beyond enabling CGI).}}


{{Note|Changes to web.xml and context.xml are '''not''' archived by default. While it's possible to change the archive properties files and include these files they are considered systems files and may change release to release. In other words, on upgrade it must be verified the there are no changes to these files (beyond enabling CGI).}}
=== Additional Information ===
 
Enabling CGI with default options

Revision as of 05:51, 19 September 2013


AppBoard runs on an Apache Tomcat server that can be configured to run CGI scripts.

Template-warning.png
Enabling CGI can introduce additional load on the AppBoard server and raises it's own security concerns. This document simply covers enabling CGI but thought should go into the issues mentioned.

Steps to Enable CGI

  1. Edit [INSTALL_HOME]/server/conf/web.xml
    1. uncomment the CGI servlet section, lines 333 through 347
    2. uncomment the CGI servlet-mapping section, lines 381 through 386
    3. save changes.
  2. Edit [INSTALL_HOME]/server/conf/context.xml
    1. add the parameter privileged="true" to the <Context ... > tag on line 19.
    2. save changes.
    3. create the directory [INSTALL_HOME]/server/webapps/enportal/WEB-INF/cgi
  3. Restart AppBoard.
Template-note.png
Changes to web.xml and context.xml are not archived by default. While it's possible to change the archive properties files and include these files they are considered systems files and may change release to release. In other words, on upgrade it must be verified the there are no changes to these files (beyond enabling CGI).

Additional Information

Enabling CGI with default options