- Intended Audience
- Deployment Assumptions
- How the Gateway Works
- Concepts of the Rewriter
- Adding and Removing Rewriter Rules
- Methodology for Rule Extraction
- Out-Of-Box Rule Set
- Rewriting HTML Attributes
- Rewriting FORM Tag Input
- Rewriting Applet Parameters
- Rewriting Cascading Style Sheets
- Rewriting XML
- Order Importance
- Third Party Application Cookbooks
- How to Get Hot Patches
There are several deployment assumptions made throughout this guide. The first is that the gateway and Portal Server components have been installed on physically different machines. While not a requirement, the gateway typically sits in the DMZ (demilitarized zone) with a firewall on either side, while the Portal Server Platform and Profile server sit in the corporate Intranet. The machine names referring to the respective components are ips-server and ips-gateway to avoid any ambiguity. Typically, the gateway also has the HTTP proxy enabled, but this guide makes no such distinction or assumption as to the presence and/or use of the proxy.
A variety of release streams are discussed throughout this document. This guide concentrates mostly on post Service Pack 3.0 (SP3) releases. Differences between SP3 and previous SPs are also briefly discussed where appropriate.
The last assumption is that the gateway is running with encryption enabled. As a result, all of the rewritten examples will have the https:// protocol identifier preceding the gateway name.