A servlet is a Java program supporting a Web server or Web application server. Internally, PRPC server code consists of several servlets, including these:
Servlet |
Description |
DiagnosticData
|
Supports downloading logs and report files from the System Management application, and downloading log files with the> System >Operations > Logs > Log Files menu item. |
HeapDisplay
|
Diagnostics |
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 a web browser; presents dynamic content such as the portal displays and forms. PRServlet is no longer required in a Pega 7 URL as of Pega 7.1.6. |
PRServletContainerAuth
|
Supports interactive users using HTTP and a web browser, when using Java EE context authentication, where users are authenticated by the application server. |
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 Java EE 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 PDN. |
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.
PRServlet is no longer required in a Pega 7 URL as of Pega 7.1.6.
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 5.X, a servlet named prdbutil
supports installation, upgrade and archive operations. This servlet is not available in version 6.X.
An external servlet can invoke PRPC, itself a collection of servlets. For an example, see PDN article How to invoke Process Commander from a servlet.