DMZ Secure Proxy Server for IBM WAS routing considerations
This page summarizes some of the security implications that must be considered when choosing how the DMZ Secure Proxy Server for IBM WAS will match incoming HTTP requests to an application or routing rule.
The DMZ Secure Proxy Server for IBM WAS can be configured to route requests either statically or dynamically. Using static routing specifies routing is performed using a flat configuration file using routing precedence that is inherent to the ordering of the directives. Requests can also be routed dynamically using a best match mechanism that determines the installed application or routing rule that corresponds to a specific request. The DMZ Secure Proxy Server for IBM WAS will dynamically discover the best route to a destination and distribute to servers with like protocols. It is considered more secure to use static routing than dynamic routing. This is because dynamic routing requires the secured proxy server to communicate with the application server to map requests where as static routing is self contained by the secure proxy server requiring no additional communication.
Table 1. Routing options
Static Routing This is considered a high security level setting. Dynamic Routing This is considered a low and medium security level setting.
Related concepts
DMZ Secure Proxy Server for IBM WAS start up user permissions
DMZ Secure Proxy Server for IBM WAS administration options
Error handling security considerations for the DMZ Secure Proxy Server for IBM WAS
Related tasks
Set secure routing for a DMZ Secure Proxy Server for IBM WAS
Tuning the security properties for the DMZ Secure Proxy Server for IBM WAS
Related
WebSphere DMZ Secure Proxy Server for IBM WAS
ProxyManagement