- Using pdm_edit.pl, add or edit webdirector entries. One webdirector can distribute load among several web engines. Add webengines and webdirectors to other servers. When specifying a secondary server, use the same name with which the secondary server was configured. This name is the NX_LOCAL_HOST value in the NX.env file on the secondary server.
Note: Auto-Assignment of webdirector CGI I/F assigns names from within pdm_edit.pl: The first webdirector on the primary server is automatically assigned the name pdmweb_d1.exe. The second webdirector on the primary server is named pdmweb_d2.exe. The third is named pdmweb_d3.exe, and so on. A secondary server can also have webdirectors that have CGI I/F values of pdmweb_d1.exe, pdmweb_d2.exe, and pdmweb_d3.exe. No naming conflicts exist because the webdirector names are unique for the local computer on which the webdirectors are running.
- Each webengine must reference an object manager. An object manager named domsrvr always exists. You can add more object managers on the secondary server and then assign webengines to them as follows:
- Number of Web Engines to Add—When implementing any web engine load-balancing scheme, SSL-Login, or both, assign at least two web engines to the same webdirector.
- SSL-Login Environment—When defining the Secure-Login web engine in pdm_edit.pl, this web engine must be under the control of a webdirector. Set the Secure-Login web engine protocol parameter value to https. This setting causes the webdirector to construct the correct redirecting URL value for the web client.
- Save changes, exit the pdm_edit.pl script, and specify which file to use for a web.cfg template when prompted.
Note: Webdirectors do not use a <Host_Name>-web[#].cfg file. However, web engines require a unique <Host_Name>-web[#].cfg file. Sample web.cfg files are automatically generated using the pdm_edit.pl script when saving and exiting the script. You are prompted to specify a web.cfg file to be used as a template in the creation of the web configuration files. You can import the customizations in the original web.cfg to the new web configuration files by specifying the original web.cfg as the template file you want to use.
- On the primary server, save the following backup copies. They are useful if you want to restore the original environment:
$NX_ROOT/pdmconf/pdm_startup.tpl
$NX_ROOT/pdmconf/pdm_startup
$NX_ROOT/bopcfg/www/*web*.cfg
$NX_ROOT/bopcfg/www/CATALINA_BASE/webapps/CAisd/WEB-INF/web.xml*
- On the secondary server, save backup copies of any existing $NX_ROOT/bopcfg/www/web.cfg or <secondary_name>-web[#].cfg files.
$NX_ROOT/bopcfg/www/CATALINA_BASE/webapps/CAisd/WEB-INF/web.xml*
- On the primary server, move $NX_ROOT/samples/pdmconf/pdm_startup.rmt to $NX_ROOT/pdmconf and rename it to pdm_startup.tpl.
- For each web engine that is assigned to a webdirector, verify that the web engine <Host_Name>-web[#].cfg webdirector parameters are set correctly by examining the file in a text editor. If necessary, modify the webdirector parameter values to specify the web engine role you want.
- On the primary server; move all $NX_ROOT/samples/pdmconf/primary-web[#].cfg files to the $NX_ROOT/bopcfg/www directory.
- Move all $NX_ROOT/samples/pdmconf/’secondary_server_name-web[#].cfg’ from the primary server to the secondary server $NX_ROOT/bopcfg/www directory.
- (Servlet servers like Tomcat) Specify a web.xml.tpl in each $NX_ROOT/bopcfg/www/CATALINA_BASE/webapps/CAisd/WEB-INF directory. When you configure this server, the configuration process creates a web.xml file. The pdm_edit.pl utility created sample web.xml.tpl files. Each file is named <hostname>-web.xml.tpl. You can use these files as a sample: copy and rename them to web.xml.tpl for each of your servers.
- (HTTP servers like IIS or Apache) On each CA SDM server (primary, secondary, or both) that you want to host a web engine or webdirector, create copies of pdmweb.exe in the $NX_ROOT/bopcfg/www/wwwroot directory. A pdmweb[#].exe for each web engine and a pdmweb_d[#].exe for each webdirector is defined in pdm_edit.pl to run on that server. Verify that pdmweb[#].exe and pdmweb_d[#].exe are named with the CGI I/F values from the pdm_edit.pl script definitions (for example, pdmweb1.exe, pdmweb2.exe, pdmweb_d1.exe, and so on).
- If you are using IIS and want to add server extensions for each CGI interface, copy the file primary-site.dat file to your $NX_ROOT/bopcfg/www directory as site.dat. When the system is reconfigured these sites are added to IIS.
- Reconfigure the primary server without reinitializing the database, and start services.
- Reconfigure each secondary server.
- For Knowledge Management to CA SDM integration, if SSL has been enforced for CA SDM, the CA SDM URL protocol value must be changed.
- From the Knowledge Management, Settings Manager, General Integration, change the CA SDM URL protocol value from http to https.
- Save and exit.
- Open a web browser to the CA SDM login page and verify that a user can log in and that the expected redirect or login behavior is observed.
