Configuring the Web Interface › Web Directors and Web Engines Configuration › How to Create a System with a Primary Server Only

How to Create a System with a Primary Server Only

You can create a system that uses a primary server only.

Note: The primary server must be installed and configured to create the system.

To create a system with a primary server only, do the following:

1. Using pdm_edit.pl add, edit webdirector entries, or both, as you want. One web director can distribute load among several web engines. Assign all new web engines and web directors to the host named primary. This host is the primary 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 would be named pdmweb_d2.exe.
   • The third would be pdmweb_d3.exe, and so on.

   A secondary server could also have webdirectors with 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.

2. Read the following information that can apply depending on your CA SDM web engine environment:
   • Number of web engines to add—When implementing any web engine load-balancing scheme, SSL-Login, or both, at least two web engines must be assigned 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's protocol parameter value to https so that the webdirector constructs the correct redirecting URL value for the web client.
3. Save changes and exit pdm_edit.pl script, specifying 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. The user is prompted to specify a web.cfg file to be used as a template in the creation of the web configuration files. The customizations in the original web.cfg can be imported to the new web configuration files by specifying the original web.cfg as the desired template file.

4. Copy and save the following files, because a backup of these files is useful whenever you decide to restore the original environment:
   • $NX_ROOT/pdmconf/pdm_startup.tpl
   • $NX_ROOT/pdmconf/pdm_startup
   • $NX_ROOT/bopcfg/www/web.cfg file
   • Any existing primary-web[#].cfg files
   • $NX_ROOT/bopcfg/www/CATALINA_BASE/webapps/CAisd/WEB-INF/web.xml and web.xml.tpl
5. Move $NX_ROOT/samples/pdmconf/pdm_startup.rmt to $NX_ROOT/pdmconf and rename it to pdm_startup.tpl.
6. For each web engine that has been assigned to a webdirector, ensure that the web engine's ‘<Host_Name>-web[#].cfg’ “webdirector” parameters have been set correctly by examining the file in a text editor. If necessary, modify the ‘webdirector’ parameter values to reflect the web engine role you want. Then copy them to the directory: $NX_ROOT/bopcfg/www.
7. Move all $NX_ROOT/samples/pdmconf/primary-web[#].cfg files to the $NX_ROOT/bopcfg/www directory.
8. If using a servlet server like Tomcat, the pdm_edit.pl utility created web.xml.tpl files that can replace the web.xml.tpl file on each server hosting a webengine. These files are name primary-web.xml.tpl. Rename the files and copy them to the directory: $NX_ROOT/bopcfg/www/CATALINA_BASE/webapps/CAisd/WEB-INF directory.

   If using an HTTP server like IIS or Apache, 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 that has been defined in pdm_edit.pl. Verify that the ‘pdmweb[#].exe’ and ‘pdmweb_d[#].exe’ are named according to the correct CGI I/F values from the pdm_edit.pl script definitions (for example: ‘pdmweb1.exe’, ‘pdmweb2.exe’, pdmweb_d1.exe’, and so on).

9. If you are using IIS and want to add Server Extensions for each CGI interface, you can take the file primary-site.dat file and copy it to your $NX_ROOT/bopcfg/www directory as site.dat. When the system is reconfigured these sites is added to IIS.
10. Reconfigure the primary server without reinitializing the database and start services.
11. After reconfiguring verify that the current settings are valid. Start the CA SDM daemons. Verify that there are no errors in the stdlog files. Use pdm_status to view the daemons and their status. From a browser, you are able to access the system: http://localhost:8080/CAisd/pdmweb.exe.
12. For Knowledge Management to CA SDM integration, if SSL has been enforced for CA SDM, the CA SDM URL protocol value must be changed.
    1. From the Knowledge Tool Settings Manager, General, Integration, change the CA SDM URL protocol value from http to https.
    2. Save and exit.
13. Open a web browser to the CA SDM login page and verify that a user can log in and that the expected redirect/login behavior is observed.