Cisco Cisco Unified IP Interactive Voice Response (IVR) 8.0(1) Leaflet

Use the Http Forward step to forward an HTTP request to an internal URI 
deployed under the document repository \default\webapps\ROOT (the default 
web applications folder) or \default\webapps\<your web apps> folder. The URI 
can be a JSP page, which would permit dynamic content generation, or any other 
resource like an HTML page for static content generation.

Internal URI paths are defined starting at the \default\webapps\ROOT folder. For 
example, a JSP page stored as: 

\default\webapps\ROOT\hello.jsp would be referenced using the URI path 
hello.jsp. 

\default\webapps\ROOT\help\help.jsp would be referenced using the URI 
path \help\help.jsp.

It is also possible to store war files under \default\webapps\ folder which would 
be automatically expanded by the internal web server and define new web 
applications that would be referenced using the URI path <war file 
name>\<resource filename>.

Use the HTTP Forward step to use Java Server Pages to generate dynamic output 
to a browser.

The HTTP Forward step lets you define local variables that you can pass to the 
JSP. When the HTTP Forward step executes, these variables are passed as 
parameters to the JSP. The JSP uses these parameters to format the output that is 
sent to the user.

You can use the HTTP Forward step instead of the Keyword Transform Document 
step (see the 

) if you 

are already using JSP or if you need the full capabilities of the Java programming 
language.

A script should use only one of the following steps from the Http Contact palette 
to respond to an HTTP request: 

Http Redirect

Http Forward 

Http Include

Send Http Response