Configuring the Web Interface › Web Directors and Web Engines Configuration › SSL Login Environment Verification

SSL Login Environment Verification

You can verify the SSL login environment for web engines as follows:

• The secure-login web engines must reside in the physical directory mapped to the SSL-enforced virtual directory (CAisdsec in this example).

  For secure-login web engines, create instances of pdmweb.exe in the $NX_ROOT/bopcfg/www/ wwwrootsec directory with the name of pdmweb[#].exe. The executable name must match the CGI I/F value for each secure-login web engine defined in pdm_edit.pl.

  Example: If pdm_edit.pl is assigned the CGI I/F value of the secure-login web engine to pdmweb2, create a physical copy of pdmweb.exe, and rename it pdmweb2.exe.

• The non-secure web engines and web directors must reside in the physical directory mapped to the non-SSL virtual directory CAisd.

  For non-secure web engines and web directors, create instances of pdmweb.exe in the $NX_ROOT/bopcfg/www/wwwroot directory. A copy of pdmweb.exe must exist for each non-secure web engine and webdirector that has been defined in pdm_edit.pl. Rename the copies so that the new names of the executables match the CGI I/F values that have been defined for the web engines and web directors in pdm_edit.pl.

  Example: If pdm_edit.pl is assigned the CGI I/F value of pdmweb3 to the non-secure web engine and the value of pdmweb_d1 to the web director, then create two copies of pdmweb.exe. Rename the first copy to pdmweb3.exe, and then rename the second copy to pdmweb_d1.exe.