LLAWP Process in CA Access Gateway (AKA Secure Proxy Server).
search cancel

LLAWP Process in CA Access Gateway (AKA Secure Proxy Server).


Article ID: 194331


Updated On:


CA Single Sign On Secure Proxy Server (SiteMinder) CA Single Sign On Agents (SiteMinder) CA Single Sign On Federation (SiteMinder) CA Single Sign On SOA Security Manager (SiteMinder) SITEMINDER


LLAWP Process in CA Access Gateway (AKA Secure Proxy Server).


Release : Any Supported Broadcom/CA Access Gateway Server (AKA Secure Proxy Servers)



Kindly note that In Secure Proxy Server (Aka CA Access Gateway) by default we DON'T see the " LLAWP " process details.

But kindly note that we have a setting in CA Access Gateway to start Secure Proxy Server in multiprocess mode so that all Agents used in different virtual hosts could use the same shared process of Agent so that If we set the " singleprocessmode="no" in " server.conf " file the LLAWP will come up and we can GREP the LLAWP process using ps -ef | grep -i llawp command.

If you would like to grep the LLAWP process then kindly go ahead and change the " singleprocessmode to "no" in " server.conf " file.

For detailed Information regrading the singleprocessmode and Multiple-Process Mode please review below:

The modes operate as follows:

- Single-Process Mode

This mode causes the Web Agent to use local resources rather than shared operating system resources offered by the LLAWP to operate. No separate LLAWP processes are started in single-process mode. When multiple virtual hosts run, single-process mode results in an increase in the memory footprint of the SPS Java process.

Note: Single-process mode is supported only for host servers that run as a single server process.

- Multiple-Process Mode

This mode causes the LLAWP framework to spawn a process for every virtual host. Because multiple-process mode uses shared memory, SPS uses shared operating system resources for logging, caching, and monitoring of multiple web server processes.