Configuring the Web Interface › Web Directors and Web Engines Configuration › Make Changes Using pdm_edit.pl › Customization Installation Considerations

Customization Installation Considerations

Consider the following when you install customizations:

• pdm_edit.pl creates a pdm_startup.dat file. Keep this file so that you can edit your current selections.
• pdm_edit.pl creates pdm_startup.rmt file. This file is a replacement for the pdm_startup.tpl file found on the primary server in the $NX_ROOT/pdmconf directory.
• If you are using a servlet server like Tomcat, a servlet replaces the CGI interface. These servers need a web.xml.tpl file. pdm_edit.pl creates one <hostname>-web.xml.tpl file for each web server. Use the appropriate file to replace the web.xml.tpl file in the $NX_ROOT/bopcfg/www/CATALINA_BASE/webapps/CAisd/WEB-INF directory on each of the servlet servers.
• If you are using an HTTP server like IIS or Apache, create CGI interface executables in your NX_ROOT/bopcfg/www/wwwroot directory by copying and renaming the pdmweb.exe file. Do this copy and rename for every CGI interface for web engines and web directors on every server hosting a web client.
• Each web engine needs a web.cfg file. pdm_edit.pl lists web.cfg files and the names to use for saving them on the appropriate server. For example, on the primary server, six of these files exist. Name one web.cfg and name another primary-web2.cfg. pdm_edit.pl creates sample web.cfg files for each of the web engines. Copy them to the $NX_ROOT/bopcfg/www directory of the appropriate server.
• If you are using IIS and require server extensions added for each CGI interface, pdm_edit.pl creates <hostname>-site.dat files. Copy the files to the appropriate servers and rename them to site.dat in the $NX_ROOT/bopcfg/www directory.
• If you defined aliases, run the alias_install.sh or alias_install.bat file on the primary server.
• Reconfigure all secondary servers.
• Reconfigure the primary server without reinitializing the database.