+

Search Tips   |   Advanced Search

Set secure routing for a DMZ Secure Proxy Server for IBM WAS


The DMZ Secure Proxy Server for IBM WAS can be configured to route requests statically or dynamically.

Set the profiles and security properties before you configure routing. See the topic Tuning the security properties for the DMZ Secure Proxy Server for IBM WAS. Decide whether you want to configure static or dynamic routing.

Static routing is performed using a flat configuration file. Static routing is considered more secure than dynamic routing. With dynamic routing, requests are routed through a best match mechanism that determines the installed application or routing rule that corresponds to a specific request. The secure proxy server will dynamically discover the best route to a destination and distribute to servers with like protocols.

The secure routing options are:

Avoid trouble: Because the DMZ secure proxy server resides in a different cell from the appservers, it must be configured to trust the appserver cell in order for SSL to work properly. See the third bullet in this procedure.

Use the following procedure to configure static or dynamic secure routing.

 

 

Results

Completing this procedure results in configuring secure routing for a DMZ Secure Proxy Server for IBM WAS.

 

Next steps

We can now start and begin to use the DMZ Secure Proxy Server for IBM WAS.

 

Related tasks


Set communication with a core group residings on a DMZ Secure Proxy Server for IBM WAS
Use the retrieveSigners command to enable server to server trust
Tuning the security properties for the DMZ Secure Proxy Server for IBM WAS

 

Related


WebSphere DMZ Secure Proxy Server for IBM WAS
DMZ Secure Proxy Server for IBM WAS routing considerations
Set a DMZ Secure Proxy Server for IBM