Considerations for Adding Web Engines

Consider the following information when you add web engines:

Directing clients to web engines—You can specify how web clients are directed to web engines. For example, consider two web directors that are being used, miko:1 and godzilla:1. miko:1 has four web engines assigned to it, godzilla:1, godzilla:2, godzilla:3, and primary:3. Any web client can request https:godzilla:8080/Caisd/ComputerAssociates.exe and be redirected to any of the four web engines in this group. If a web client enters http://localhost:8080/CAisd/pdmweb6.exe, the client is always directed to this web engine. Also, notice that some web engines are assigned to the object manager named domsrvr and others are set up to attach to ANY object manager.
Using CGI I/F values—Each web engine defined in pdm_edit.pl must have a unique CGI I/F value:
- If you are using an HTTP server like IIS or Apache, you must have a correctly named pdmweb[#].exe executable in the $NX_ROOT/bopcfg/www/wwwroot directory.
- If you are using a servlet server like Tomcat, a servlet replaces the CGI interface. These servers must have a web.xml.tpl file in the $NX_ROOT/bopcfg/www/CATALINA_BASE/webapps/CAisd/WEB-INF directory that describes each CGI interface. The pdm_edit.pl utility creates sample web.xml.tpl files named <hostname>-web.xml.tpl. Use these files to replace the web.xml.tpl file and reconfigure the server.