Configuring the Web Interface › Web Directors and Web Engines Configuration

Web Directors and Web Engines Configuration

Become familiar with the following information to add and configure web directors and web engines, based on server and component types:

SSL

Specifies the Secure Socket Layer Protocol.

pdm_edit.pl

Specifies the CA SDM Perl script used to add and modify web engines, web directors, object managers, and other components.

CGI I/F

Specifies the script name for web engines and web directors assigned by pdm_edit.pl. This value is the name of an actual CGI executable when IIS or Apache is used as the HTTP server; it is a servlet parameter when Tomcat is used as the HTTP server.

Examples: (web engines) pdmweb1, pdmweb2, (web directors) pdmweb_d1, and pdmweb_d2

Systems that use servlet servers like Tomcat do not need CGI/IF executables. The CGI/If is simulated by a servlet running on the servlet server, instead these systems require a web.xml file in the directory: $NX_ROOT/bopcfg/CATALINA_BASE/webapps/CAisd/WEB-INF

Pdm_edit.pl creates sample web.xml files that are named <hostname>-web.xml.tpl. You copy these files to the appropriate server in the WEB-INF directory so they replace the web.xml.tpl file on each server, and then reconfigure the secondary server.

SSL Login

Specifies the CA SDM configuration in which one or more web engines reside in an SSL-enforced virtual directory and exclusively handles all web-client login requests using encrypted HTTP communication. After user authentication is complete, a web director redirects the web client to an eligible web engine residing in a non-SSL-enforced virtual directory for the remainder of the client session, using unencrypted HTTP communication.

Secure Login Web Engine

Specifies the web engine in the SSL login environment that exclusively handles all CA SDM web-client user authentication requests.

Non Secure Web Engine

Specifies the web engine in the SSL login environment that handles all web client nonuser authentication requests after user authentication has taken place through the secure login web engine.

Web Engine Role

Specifies the duties performed by a web engine after it has been assigned to a web director. These roles include the following:

• Only Process web client login requests.
• Process everything but web client login requests.
• Process all web client requests.

More information:

How to Implement an SSL Login Environment with a Primary Server Only

Server Configuration

Web Engines