29.01.2013 Views

WebSphere Application Server V7.0: Concepts ... - IBM Redbooks

WebSphere Application Server V7.0: Concepts ... - IBM Redbooks

WebSphere Application Server V7.0: Concepts ... - IBM Redbooks

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

SIP proxy<br />

The SIP proxy design is based on the HTTP proxy architecture. The SIP proxy<br />

extends the HTTP proxy features. It can be considered a peer to the HTTP proxy.<br />

Both the SIP and the HTTP proxy are designed to run within the same proxy<br />

server and both rely on a similar filter-based architecture for message processing<br />

and routing.<br />

The SIP proxy server initiates communication and data sessions between users.<br />

It delivers a high performance SIP proxy capability that you can use at the edge<br />

of the network to route, load balance, and improve response times for SIP<br />

dialogs to back end SIP resources. The SIP proxy provides a mechanism for<br />

other components to extend the base function and support additional deployment<br />

scenarios.<br />

The SIP proxy is responsible for establishing outbound connections to remote<br />

domains on behalf of the back end SIP containers and clients that reside within<br />

the domain that is hosted by the proxy. Another important feature of the SIP<br />

proxy is its capability to protect the identity of the back end SIP containers from<br />

the SIP clients.<br />

<strong>WebSphere</strong> <strong>Application</strong> <strong>Server</strong> Proxy provides many functions that Web server<br />

and plug-in have but it is not a full replacement because it does not have Web<br />

serving capabilities. (Static content can be served from the proxy cache) If the<br />

Web server is used only for load balancing and routing with session affinity,<br />

<strong>WebSphere</strong> <strong>Application</strong> <strong>Server</strong> Proxy can take the place of the Web server.<br />

<strong>WebSphere</strong> <strong>Application</strong> <strong>Server</strong> Proxy is not considered a secure proxy for<br />

demilitarized zone (DMZ) deployments. For example, it cannot bind to protected<br />

ports without being a privileged user on most operating systems and users<br />

cannot be switched after binding. <strong>WebSphere</strong> <strong>Application</strong> <strong>Server</strong> Proxy must stay<br />

in the intranet/secure zone.<br />

DMZ Secure Proxy <strong>Server</strong><br />

As the <strong>WebSphere</strong> <strong>Application</strong> <strong>Server</strong> Proxy is not ready for a DMZ, <strong>WebSphere</strong><br />

<strong>Application</strong> <strong>Server</strong> <strong>V7.0</strong> ships a DMZ-hardened version of <strong>WebSphere</strong><br />

<strong>Application</strong> <strong>Server</strong> Proxy. The DMZ Secure Proxy <strong>Server</strong> comes in a separate<br />

install package that contains a subset of <strong>WebSphere</strong> <strong>Application</strong> <strong>Server</strong> Network<br />

Deployment and provides new security enhancements to allow deployments<br />

inside of a demilitarized zone (Figure 3-11 on page 69).<br />

68 <strong>WebSphere</strong> <strong>Application</strong> <strong>Server</strong> <strong>V7.0</strong>: <strong>Concepts</strong>, Planning, and Design

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!