You may need to make additional configuration changes to your Apache Web Agent if you have any of the following situations or conditions in your environment:
If you have applications that perform load balancing by redirecting traffic to specific web servers without modifying the actual HTTP headers, you should configure the Web Agent to redirect users back to the proper external port (instead of the port used by the load balancer) with the following parameter:
Directs the Web Agent to obtain the port number from the HTTP HOST request header instead of obtaining it from the web server service structures.
Default: No
Note: This parameter is required for Apache Web Agents.
To use the port number in the HTTP HOST request header, set the GetPortFromHeaders parameter to yes.
If you have legacy applications (that do not support HTTP 1.1), and you want to run them on an Apache Web Server, you can set the following parameter:
Specifies the type of message encoding used by the Web Agent. When the value of this parameter is set to no, transfer-encoding is supported.
When the value of this parameter is set to yes, content encoding is used. The transfer-encoding header is ignored and only the content-length header is supported.
Default: No
To use legacy applications with an Apache Web Server, set the value of the LegacyTransferEncodingBehavior parameter to yes.
Important! If you set the value of this parameter to yes, these features will not work: Federation; preservation of POST data longer than 4 KB; and large certificates may not be recognized.
If you are using an Apache web server, you can control how content is transferred to the server during POST requests with the following parameter:
Specifies how content will be transferred to the server during POST requests. When the value of this parameter is set to yes, all content types are streamed, except for the following:
When the value of this parameter is set to no, all content types are spooled.
Default: No
To stream most types of content in POST requests, change the value of the LegacyStreamingBehavior parameter to yes.
By default the Apache Web Agent logs all levels (informational and error) of IPC semaphore-related messages to the Apache error log, regardless of the configured Apache logging level.
To restrict the verbosity of Web Agent IPC semaphore-related output to the Apache error log, add the following parameter in the trace.conf file located in web _agent_home/config:
Specifies the level of IPC semaphore-related messages the Web Agent logs to the Apache error log. Accepts the following values:
The Web Agent logs no IPC semaphore-related messages to the Apache error log.
The Web Agent logs only IPC semaphore-related error messages to the Apache error log.
(Default) The Web Agent logs IPC semaphore-related error and informational messages to the Apache error log.
Example: Define the nete.stderr.loglevel parameter in trace.conf
In the following snippet from trace.conf, the nete.stderr.loglevel parameter is configured to restrict the Web Agent to log only IPC semaphore-related error messages to the Apache error log:
# CA Web Agent IPC logging levels # nete.stderr.loglevel=error
To help ensure that users who try to browse the directories of a Oracle iPlanet web server are challenged by SiteMinder, you can set the following parameter:
Specifies whether the Web Agent allows a user to view or browse the contents of a directory without challenging them first. This occurs when all of the following conditions are true:
Default: No
To restrict directory browsing on a Oracle iPlanet server
Directory browsing is restricted. SiteMinder challenges users who try to browse directories.
|
Copyright © 2012 CA.
All rights reserved.
|
|