Beginning with Enterprise Security 6.0, you can integrate an SWP into Enterprise Portal as a portlet. First deploy the SWP into EAServer as a standalone Web application—see “Installing and configuring a Secure Web Proxy”.
Once you verify that the SWP is working correctly as a standalone Web application, use Portal Studio to create a portlet that includes a JSP element with the SWP content you want. For complete information about creating and configuring portlets, see the Enterprise Portal Developer’s Guide.
To configure the JSP element:
In Portal Studio, set the following parameters in the JSP Element Definition window:
WAR File – webproxy.war.
Web App Display Name – webproxy.
Initial Resource – proxy/[application_name]/.
Replace [application_name] with the name of the configured application from swp.properties that you want to display in the portlet.
Single Sign On Required – select this option.
302 Redirect – select this option.
In swp.properties, verify that these properties are commented out:
ApplicationServer.java.naming.provider.url
ApplicationServer.java.naming.security.principal
ApplicationServer.java.naming.security.credentials
Once this configuration is complete, you should see the appropriate content display in the preview window. See the Security/security.log and the server log file—for EAServer, this is typically $JAGUAR/bin/Jaguar.log—for error and diagnostic information.
