A servlet is a Java program supporting a Web server or Web application server. Internally, Process Commander server code consists of several servlets, including these:

Servlet	Description
CustomPassword	Supports the optional password management facility.
DiagnosticData	Supports downloading logs and report files from the System Management application, and downloading log files with the Tools > Log Files menu item.
HeapDisplay	Diagnostics
prdbutil	Contains database utilities, and supports installation and upgrade processing.
PRHTTPService	Supports Service HTTP rules (Rule-Service-HTTP rule type)
PRImpExpServlet	Exports or imports rules, data, and other objects. Reserved for installation and support issues.
PRPortletService	Supports access from portlets.
PRServlet	Supports interactive users using HTTP and Internet Explorer; presents dynamic content such as the portal displays and forms.
PRServletContainerAuth	Supports interactive users using HTTP and Internet Explorer, when using J2EE context authentication, where users are authenticated by the application server.
PRServletLDAP1 to 5	Provides five working examples used by the Authentication wizard. See About the Authentication wizard.
PRServletProtected	Supports HTTP Basic Authentication over Secure Sockets Layer (SSL).
PRServletProtectedAuth	Supports HTTP Basic Authentication over SSL.
PRSOAPServlet	Responds to service requests from SOAP clients, uses packages of Service SOAP rules. By default, uses the same TCP/IP port as PRServlet.
PRSOAPServletContainerAuth	Responds to service requests from SOAP clients, uses packages of Service SOAP rules, when J2EE context authentication is in use. By default, uses the same TCP/IP port as PRServlet.
PRSOAPSimulator	Helps in testing a SOAP connector. See Testing Services and Connectors, a document on the Integration area of the Pega Developer Network.
PRStartup	Used briefly during system startup and to start agents and listeners.
PRTraceServlet	Implements the Tracer debugging tool.
RuleFileServlet	Serves static content through HTTP protocol messages, such as images, Cascading Style Sheets and JavaScript files. These are extracted to the file system from Rule-File-* rules upon first request.
SecManServlet	Diagnostics

(Technically, the above names are the URL patterns for the servlets, defined through the web.xml file for use with standard authentication. For example, the true servlet for the URL pattern PRServlet is WebStandard.) Ordinarily, a user accesses a servlet by entering its name in the Address line of a browser window. However, you can change settings in the in the web.xml file to mask or alter URLs associated with these servlets. See Pega Developer Network article PRKB-10032 How to control access to servlets with Tomcat's web.xml file.

Additional servlets support LDAP access, testing, diagnostics, and internal operations. Both the internal name and the external URL names of each servlet are defined in the web.xml file.

In version 4, an additional servlet named PRMonitorServlet supported the System Console. Beginning with version 5.1, the System Management application (prsysmgmt) replaces that servlet.

An external servlet can invoke Process Commander, itself a collection of servlets. For an example, see Pega Developer Network article PRKB-8783 How to invoke Process Commander from a servlet.

	Catalina, password management facility, static content
	About Authentication Service data instances About the System Management application About Service SOAP rules Debugging with the Tracer

Definitions — S